Setting Up and Implementing Sourcing Strategies

A sourcing strategy allows a supply chain planner to gather all possible replenishment scenarios and apply them globally, or to any item, category of items, or organization. This allows the enterprise, or an individual organization, to adopt the most efficient method of fulfilling net requirements. Oracle Supply Chain Planning minimizes the effort required to set up, implement, and maintain this strategy with sourcing rules and bills of distribution.

Sourcing Rules and Bills of Distribution

Sourcing rules and bills of distribution determine the movement of materials between organizations in your global enterprise; these organizations include your suppliers and the materials include those items made at the manufacturing organizations. They both describe sourcing supply; for any organization, they answer the question "where do I get part A from?". (They never say "where do I send part A to".) Sourcing rules answer this question for one organization or for all organizations in the enterprise. Bills of distribution can define a strategy for multiple organizations. Sourcing rules and bills of distribution both specify date-effective sourcing strategies, combining replenishment sources with split allocation percentages and rankings. A replenishment source is:
o o o

an inter-organization transfer (Transfer From) the replenished organization that manufactures the item (Make At) an external supplier (Buy From)

In a sourcing rule, time-phasing applies only to the shipping organizations; the receiving organization remains static for the life of the sourcing rule. In a bill of distribution, timephasing applies both to shipping and receiving organizations. Rank and Allocation You can rank the sources of supply named in the rules and bills, giving one priority over another when the planning process generates recommendations. You can also assign sourcing percentages to these sources, allowing you to allocate a portion of the total orders to each source. Control over Make/Buy Attributes In Oracle Master Scheduling/MRP, three item attributes determine if planned orders can be implemented as discrete jobs, repetitive schedules, or purchase requisitions. Supply Chain Planning users can supplement and refine this behavior with sourcing rules and bills of distribution. For each item in a rule or bill, you can define effectivity dates to switch sourcing between make and buy, and set intransit lead times. If an item does not appear in a rule or bill, the item attribute determines the status; when these attributes conflict with a sourcing rule or bill of distribution, the rule or bill takes precedence. (See: Item and Bill of Material Attributes, and Defining Items.)

Sourcing Rules
Sourcing rules define inventory replenishment methods for either a single organization or all organizations in your enterprise. Time-phasing in a sourcing rule determines when each group of shipping method - ship org combinations is in effect, as in this example:

In the first phase of SR-C01, SAC is replenished equally by AUS and NYC. From 01-JUL1997, AUS no longer supplies SAC, which receives all transfers from NYC:

This sourcing rule can apply to one org (SAC, in this example), or to all your organizations. However, you cannot choose a single organization in one phase and all organizations in another phase. That would require two sourcing rules, with consecutive effectivity dates. If you assign the sourcing rule to one receiving organization (SAC in this example), it is a local sourcing rule; if you assign it to multiple organizations, it is a global sourcing rule. You cannot apply sourcing rules and bills of distribution (make them Planning Active) until the sum of the allocation percentages equals 100. Secondly, sourcing rules and bills of distribution do not take effect until they are assigned to a part or a range of parts. (See: Assigning Sourcing Rules and Bills of Distribution.)

Bills of Distribution
Bills of distribution define the sourcing strategies of several organizations. In other words, a bill of distribution is library of sourcing strategies. For instance, the sourcing strategy described in SR-C01 could apply to different organizations at different periods. You cannot do this with sourcing rules because you have to apply the strategy to one org or all orgs. In another example, an item is made in a manufacturing center and supplied to a distribution center, which in turn supplies three sales offices. Instead of using five different local sourcing rules, you could set up a three-level replenishment hierarchy with a bill of distribution for the item. This bill would specify how the item is sourced at each level. Both sourcing rules and bills of distribution have effective dates, periods during which the scheme is valid. For each period, you can specify a list of sources, type, allocation percentage, rank, shipping method, and intransit time. You cannot apply sourcing rules and bills of distribution (make them Planning Active) until the sum of the allocation percentages equals 100. Secondly, sourcing rules and bills of distribution do not take effect until they are assigned to a part or a range of parts. (See: Assigning Sourcing Rules and Bills of Distribution.)

Example
In the following scenario, distribution centers SFD and NYD receive finished goods from manufacturing plan SAC:

Sourcing rule SR-C02 describes the replenishment of SFD by SAC. Since no other plants supply the part (which is assigned to this rule separately), the allocation is 100%. SR-C02 is a local sourcing rule because it applies to SFD only. Similarly, SR-C03 describes the replenishment of NYD by SAC. The bill of distribution (BR-E01 in this example) can define a specific set of receiving organizations, and for each organization it can define any number of shipping organizations each with its own allocation percentage, ranking, and shipping method. Bills of distribution are more flexible than sourcing rules because, for each organization you list in the bill, you define a range of dates and a sourcing strategy to apply within those dates. Sourcing rules can only define the dates and strategy for one organization or all the organizations in your enterprise. The following scenario illustrates this flexibility:

As the demand from NYD expands and exceeds SAC's capacity to meet the demand, the enterprise decides to build a new plant, called NYC. While NYC is brought online, SAC continues to meet 100% of demand from NYD. From 1-JUL, however, NYC begins to supply a small percentage of this demand, taking some of the burden away from SAC. The planning process can quickly and easily support this transition. Sourcing rule SR-C04 can define the dates during which the transition will occur, include NYC, and split the demand replenishment between it and SAC. Bill of distribution BR-E01 can accomplish this as well, but the bill can incorporate it into an enterprise-wide sourcing strategy.

ORACLE ASL -SOURCING -------------------------------------------------

For this topic, presuming you already aware of sourcing module of Purchasing family of Oracle EBS footprints.If you hear this first time, then next paragraph is meant for you. Sourcing is a function with strategic importance within the broader context of procurement. Infact it is a subset of procurement with strategic context. Sourcing sets thestage for the entire companys purchase for direct and indirect materials, and involveshighlevel, company-wide approaches to obtaining materials and services, identifying andevaluating potential suppliers to meet those needs, negotiating and implementingcontracts with selected suppliers, monitoring and improving ongoing supplier relationships.

Two important concept , sourcing rule and ASL . Sourcing Rule Sourcing rules define inventory replenishment method for either a single organization or all organizations in the enterprise. They describe sourcing supply; for any organization,[Adopted user Documentation]

they answer the question where do I get part A from? User defines rankings and % allocation for replenishment sources in the form of Sourcing Rules.

Assign sourcing Rules typically follow prioritity from Global to Item Orgnization sepecfic as below: Global->Organization->Item Category->Item->Item Category-Organization->Item Organization ASL All procurement organizations maintain lists that associate the items and services they buy from supplier organization. Data stored in a global repository containing relevant details about each item/supplier/supplier site relationship, is known as an Approved Supplier List (ASL). This repository includes information about all suppliers with business statuses ranging from Approved (the supplier has demonstrated the ability to satisfy rigorous quality, cost, and delivery requirements over a sustained period) to Debarred (the supplier is temporarily/permanently disallowed on purchase orders due to performance failure, ethics violations, etc.) or 'New' if you have never placed a purchase rorder with the supplier. Why do we use ASL-Sourcing This is because of three simple great reason, as

Automatically default supplier and pricing information onto Document Lines Source the item from negotiated purchase agreements Reduce manual intervention

Which Other Products use Sourcing Rules

Purchasing Planning Supplier Scheduling Supply Chain Planning

How to start to utilize this function In order to utilize this you have to perform these setup steps:

Define Item or category Define Supplier/Supplier Site Create Quote or Blanket Purchase agreement Define ASL Define Sourcing Rule Assign Sourcing Rule to Assignment Set

Conversion. Migratioon, Integration If you are implementing First time, need to do conversion and other activity, What should be the best strategy for mass upload of Approved Supplier List and Sourcing Rule.Is there any API or interface to do the same? This capability exists through the Purchasing Document Open Interface (PDOI).You can import Global Approved Supplier List(ASL) through the Purchasing Document Open Interface (PDOI) Read this Approved Supplier Lists (ASL) Table Used in ASL-Sourcing Object Name Object Detail Description Type This table stores the relationship between an item orcommodity; a supplier, distributor, or manufacturer; ship-to organizations; and approval/certification status This table stores all information for thesupplier/item/organization relationship defined inPO_APPROVED_SUPPLIER_LIST. This informationis maintained separately to allow each organization to define its ownattributes, even if using a Global ASL entry for the supplier/item relationship and approval status This table stores sourcing references to supply agreements,blanket agreements, and catalog quotations associated with particular suppliers and items in PO_APPROVED_SUPPLIER_LIST This table stores the user-defined approval/certification statuses forthe ASLs This table stores the business rules associated with each defined ASL status This table stores sourcing rule names and

PO_APPROVED_SUPPLIER_LIST Table

PO_ASL_ATTRIBUTES

Table

PO_ASL_DOCUMENTS

Table

PO_ASL_STATUSES PO_ASL_STATUS_RULES MRP_SOURCING_RULES

Table Table Table

descriptions. The Define Sourcing Rule form populates this table MRP_ASSIGNMENT_SETS Table This table stores information about Sourcing Assignment Sets.The Define Assignment Sets form populates this table This table stores the assignment of sourcing rulesor bills of distribution to items, organizations, category, orat the global level. The Assign Sourcing Rules Form populates this table This view used by the Create Documentsworkflow that is created from table PO_ASL_ATTRIBUTES and tablePO_APPROVED_SUPPLIER_LIST

MRP_SR_ASSIGNMENTS

Table

PO_ASL_ATTRIBUTES_VAL_V

wiew