• Difference between the Bill of distribution and sourcing rule.


      •  
         
        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.

  • 相关阅读:
    Redis常见的应用场景解析
    技术知识和稳定的系统之间,可能还差这些?
    学会数据库读写分离、分表分库——用Mycat,这一篇就够了!
    程序员也是弱势群体?——从WePhone开发者事件说起
    系统日志管理那点事
    我的Markdown的利器——Markdown Here、有道云笔记、iPic
    推荐几本产品类的书
    华为云的API调用实践(python版本)
    阿里云 API调用实践(python语言)
    HA总结:AWS 网络连接
  • 原文地址:https://www.cnblogs.com/xiaoL/p/3146819.html
Copyright © 2020-2023  润新知