Difference between the Bill of distribution and sourcing rule.
2013-06-20 19:11
561 查看
https://forums.oracle.com/thread/936768
This is from a users guide
Oracle Supply Chain Planning does this with sourcing rules and bills of distribution. Sourcing rules and bills of distribution both describe sourcing supply; i.e., 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 apply the answer to one organization or all the organizations in your enterprise. Bills of distribution define this behavior across multiple organizations (not just one or all).
Bills of Distribution Specifies a multilevel replenishment network of warehouses, distribution centers, and manufacturing centers (plants).
Sourcing rule Specifies how to replenish items in an organization, such as purchased items in plants. You can also use sourcing rules to override sourcing that is specified in the bill of distribution assigned to an item
While these 2 entities overlap each other significantly and may be used as a replacement of other at times, there are still a few basic differences outlined below:
1. Sourcing Rules (SR) specify how an item (or group of items) are sourced for replenishment by an entity (say customer/ organization etc). Please note that its expressed in terms of receiving entity.
2. Bill of Distribution (BOD) specify how an item is supplied by an entity (say organization). This is expressed in terms of supplying entity
3. While BOD can only be assigned to internal organizations (could be CM or suppliers if modelled as an organization), Souricng Rule can be assigned to any type of entity including customers, suppliers, organizations and even regions & zones.
4. Typically usage of BOD vs. SR may be dependent on you supply chain structure. If a make organization is supplying to multiple distribution centers etc, BOD may help reduce data setup volume. Instead if a distribution center is sourcing from multiple organizations, SR may be a better choice.
5. If you're using regions & zones or customer locations to model how ATP/ ASCP selects a ship-from organization for Sales Orders, SR is only supported mechanism (unless these customers are modelled as organization)
6. For suppliers (not modelled as Org), SR is only option.
http://docs.oracle.com/cd/A60725_05/html/comnls/us/mrp/srbod.htm
This is from a users guide
Oracle Supply Chain Planning does this with sourcing rules and bills of distribution. Sourcing rules and bills of distribution both describe sourcing supply; i.e., 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 apply the answer to one organization or all the organizations in your enterprise. Bills of distribution define this behavior across multiple organizations (not just one or all).
Bills of Distribution Specifies a multilevel replenishment network of warehouses, distribution centers, and manufacturing centers (plants).
Sourcing rule Specifies how to replenish items in an organization, such as purchased items in plants. You can also use sourcing rules to override sourcing that is specified in the bill of distribution assigned to an item
While these 2 entities overlap each other significantly and may be used as a replacement of other at times, there are still a few basic differences outlined below:
1. Sourcing Rules (SR) specify how an item (or group of items) are sourced for replenishment by an entity (say customer/ organization etc). Please note that its expressed in terms of receiving entity.
2. Bill of Distribution (BOD) specify how an item is supplied by an entity (say organization). This is expressed in terms of supplying entity
3. While BOD can only be assigned to internal organizations (could be CM or suppliers if modelled as an organization), Souricng Rule can be assigned to any type of entity including customers, suppliers, organizations and even regions & zones.
4. Typically usage of BOD vs. SR may be dependent on you supply chain structure. If a make organization is supplying to multiple distribution centers etc, BOD may help reduce data setup volume. Instead if a distribution center is sourcing from multiple organizations, SR may be a better choice.
5. If you're using regions & zones or customer locations to model how ATP/ ASCP selects a ship-from organization for Sales Orders, SR is only supported mechanism (unless these customers are modelled as organization)
6. For suppliers (not modelled as Org), SR is only option.
http://docs.oracle.com/cd/A60725_05/html/comnls/us/mrp/srbod.htm
相关文章推荐
- String and some of the difference between StringBuffer
- The difference between equals and == of Java
- The Difference Between Big Data and a Lot of Data
- the differences of DataRelation class between 1.1 and 2.0
- Project Manager - the Differences of the Role between Western Countries Company and Chinese Company
- The difference of SE Detail UI between 2.4 and 4.0
- the differences of DataRelation class between 1.1 and 2.0
- the difference between ClientID and ID of web control
- What is the difference between SVD and matrix factorization in context of recommendation engine?
- The difference of overriding between C# and Java
- What is the difference between /dev/ttyUSB and /dev/ttyACM?
- The difference between GDI+ and GDI
- The Difference Between @Helpers and @Functions In WebMatrix
- What is the difference between NoClassDefFoundError and ClassNotFoundException?
- the differences between Crystal and Oscillator
- In Linux, what is the difference between “buffers” and “cache” reported by the free command?
- The difference of the type of DB type property such char,varchar,nchar and nvarchar
- The difference between film faced plywood and wood I joist beam
- The balance between the number of specs and the rate of coverage
- the difference between the version and build fields