Function documentationDeployment Modes Locate this document in the navigation structure

 

Deployment enables the distribution of goods within a bill of distribution (BOD). There are two modes, push, and pull deployment. At push deployment, a goods receipt at a parent location triggers distribution. At pull deployment, the current demand at a child location during the replenishment lead time triggers distribution. Push deployment thus distributes newly arrived goods to child locations, while pull deployment reports demand at child locations to parent locations.

Features

Pull Deployment

You can schedule pull deployment as a planning service in the Planning Service Manager that the system executes in the background. The following events also set a trigger for a pull deployment run:

  • The fixed demands of a child location change.

  • The stock of a child location decreases.

  • The replenishment indicator changes.

If, for one of these reasons, the system has set a trigger for a location product, pull deployment checks if the respective child location has a current demand during the replenishment lead time that is not covered. If so, the system determines the net demands of all child locations of the corresponding sub-BOD so that it considers each child location with demand during the distribution process. The quantity to be distributed that the system uses is either the available stock at the parent location, as calculated using a Global ATP check, or the quantity that distribution requirements planning (DRP) has calculated in the DRP Matrix as the initial warehouse stock. The option that the system chooses depends on your entry in Customizing in the ATP: Business Event (Pull Depl.) field. If you specify a business event that you have created in Customizing for the ATP check, the system calculates the quantity to be distributed using the ATP check. If you leave the field blank, the system uses the values for the initial warehouse stock in the DRP Matrix as the quantity to be distributed. The system deducts the respective distribution demands from both the quantity that the global ATP check determined as available stock, and from the initial warehouse stock, to determine the distributable quantity.

For more information about Customizing settings for deployment, see Customizing for Advanced Planning and Optimization under   Supply Chain Planning   Service Parts Planning (SPP)   Deployment   Make General Settings for Deployment  .

For information about the settings you must make in Customizing for the ATP check so that you can fill the ATP: Business Event (Pull Depl.) field in Customizing for deployment, see Settings for Pull Deployment Based on the ATP Check.

If the net demand of all child locations during the replenishment lead time is covered, the system does not execute pull deployment. The decision about which quantities the system distributes to which child locations is made on the basis of priority tiers, fair-share distribution, and rounding rules. If a parent location does not have sufficient goods to cover the current demands of the child location during the replenishment lead time, the system checks in the BOD if the next highest parent location can cover the demands. It then triggers a new pull deployment.

Push Deployment

If the ATP quantity increases, it can trigger the event-driven quantity assignment (EDQA) process. The EDQA triggers push deployment under the following conditions:

  • During the EDQA process, the system does not need the total quantity to be distributed for the quantity assignment to order due lists (QODL). In other words, the system does not need the total quantity to be distributed for backorders.

  • In Customizing for Advanced Planning and Optimization, you have activated the quantity release for push deployment in one of the following ways:

    • In the Define Process Category for Quantity Assignment to Order Due Lists (QODL) Customizing activity, you have defined a process category with the event EDQA Quantity Assignment to ODL and have set the Push Deployment indicator. For more information, see Customizing for Advanced Planning and Optimization under   Global Available-to-Promise (Global ATP)   Event-Driven Quantity Assignment   Quantity Assignment to Order Due Lists (QODL)   Define Process Category for Quantity Assignment to Order Due Lists (QODL)  .

    • You have defined a process category for push deployment. For more information, see Customizing for Advanced Planning and Optimization under   Global Available-to-Promise (Global ATP)   Event-Driven Quantity Assignment   Other Process Categories   Define Process Category for Push Deployment  .

During push deployment, the system only distributes newly arrived goods, and the stock of the parent location remains untouched. During the distribution of the goods the system creates stock transport requisitions for all child locations with the deployment indicator Planned as Push. The system only considers child locations with the deployment indicator Planned as Pull during planning if the corresponding child location has a current net demand during the replenishment lead time. The decision about which quantities the system distributes to which child locations is made, as during pull deployment, on the basis of priority tiers, fair-share distribution, and rounding rules.

During distribution in both pull and push deployment, the system ensures that the quantity of a product in the warehouse of a child location does not exceed the time-related supply limit (TSL). Remaining quantities, which the system does not distribute because of rounding or the TSL, either remain at the parent location, or are distributed to the destination location according to special rules. For more information about the distribution of remaining quantities during deployment, see Customizing under   Advance Planning and Optimization   Supply Chain Planning   Service Parts Planning (SPP)   Deployment   Define Service Profile for Deployment   Distribution of Remaining Quantity: Maximum Number Pull Locations  .

There are the following variants of standard push deployment: