1 / 45

Deployment & ATP CTP Modules in SCM

Deployment & Available-to-promise (ATP) in SCM EGN 5623 Enterprise Systems Optimization Fall, 2012. Deployment & Available-to-promise (ATP) in SCM Theories & Concepts EGN 5623 Enterprise Systems Optimization Fall, 2012. Review Deployment Deployment setting Deployment strategy

mara-leach
Download Presentation

Deployment & ATP CTP Modules in SCM

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Deployment & Available-to-promise (ATP)in SCMEGN 5623 Enterprise Systems OptimizationFall, 2012

  2. Deployment & Available-to-promise (ATP)in SCM Theories & ConceptsEGN 5623 Enterprise Systems OptimizationFall, 2012

  3. Review • Deployment • Deployment setting • Deployment strategy • Available-to-deploy (ATD) • Available-to-receipts (ATR) • Available-to-issues (ATI) • Transport Load Builder (TLB) • 3. Available-to–promise (ATP) • Capable-to-promise (CTP) • Multi-level ATP (ML-ATP) check Deployment & ATP CTP Modules in SCM

  4. Deployment and ATP CTP Modules in SCM (Review)

  5. Basic Components of SAP SCM SAPECCERP SAP SCM(includes SAP BW) Core Interface (CIF) • Demand Planning • Supply Network Planning and optimization • Production Planning with capacity considerations • ATP • CTP • Detailed Scheduling • Deployment • Transportation planning • Vehicle routing and scheduling • Mater data • Materials • Locations • Partner • Plants • Info records • Transactional data • Customer orders • Production orders • Purchasing orders • Execution Planning with SAP ERP & SCM

  6. Alternative Scenario Base Scenario 7.0 Two planning Scenarios for SAP SCM

  7. Work Flow in SAP SCM

  8. Level of Detail and Time Horizon for SAP APO Modules

  9. After mid to long term SNP planning and after detailed PP/DS planning for production, deployment determines which distribution requirements of the distribution centers or VMI customers can be covered by the existing supply. Deployment

  10. Deployment Setting

  11. If the available quantities are not sufficient to meet demand or if they exceed the demand, deployment makes adjustments to the stock transfers created by the SNP run. • The system reduces the stock transfer and decides how much will be deployed to each distribution center. • The deployment heuristic reaches this decision using the defined rules. Deployment Setting

  12. If the quantities that are actually produced, procured and the demands match the Supply Network Planning (SNP) planning quantities, deployment merely confirms the stock transfers. • The quantities of different products confirmed by deployment can be combined into stock transport orders by the Transport Load Builder (TLB). • Deployment and TLB are used to confirm stock transfers. Deployment Setting

  13. Deployment Strategies • Pull deployment • Pull horizon

  14. There are several rules available for the deployment heuristic: • Fair share deployment • Push deployment • Pull push deployment Deployment Strategies

  15. Fair share deployment is used if demand exceeds supply. • Rule A: the quantities are deployed in proportion to the original demands in the distribution centers. • Rule B: increase the stock on hand at all demand locations to the same percentage of the target stock level. • Rule C: distribute the Available-to-promise (ATD) quantity at the demand location according to the outgoing quota arrangements. • Rule D: distribute the stock according to the priorities of the outbound transportation lanes of the source location. Fair Share Deployment

  16. Quota Arrangement

  17. Incoming quota arrangement: • Use an incoming quota arrangement to specify which proportion of a requirement is to be procured from which source location (e.g. vendor). • Outgoing quota arrangement: • Use an outgoing quota arrangement to determine which proportion of the receipts is to be delivered onward to which destination location (e.g. one of your distribution centers). Incoming/Outgoing Quota Arrangement

  18. Push deployment determines which supplies are taken into account during the deployment calculation. • The push rules are used if supply exceeds demand, and the surplus needs to be distributed as soon as possible. Push Deployment

  19. Pull deployment determines which demands are taken into account during the deployment calculation. • Stock is distributed according to the due dates specified at the individual demand locations. • No supply is distributed to the demand source in advance of the demand date. Pull Deployment

  20. When procurement and production are finished, the system checks which product quantities are actually available in the source location (location with stock). • The total of these product quantities is referred to as the available to deploy quantity (ATD quantity). Available-to-deployment (ATD)

  21. In standard category group ATR (available-to-receipts), you group together all the ATP (available-to-promise) categories that are to be taken into account as receipts for deployment. • Receipts include stock, production orders, and purchase orders. Available-to-receipts (ATR)

  22. In standard category group ATI (available-to-issues), you group together all the ATP categories that are to be taken into account as issues for deployment. • Issues include sales orders and reservations. • The ATD (available-to-deploy) quantity is calculated from category groups ATR and ATI. Available-to-issues (ATI)

  23. The different deployment horizons are: • The push horizonspecifies the number of days from today’s date, over which you want to take into account the receipts for today’s deployment (ATD quantity). • The deployment horizonspecifies the number of days from today’s date, over which you want to confirm stock transfers during today’s deployment. • The pull horizon specifies the number of days from today’s date, over which you want to take into account demands for today’s deployment. • Deployment is always done from one delivery location to the receiving location (DCs or Customers). Available-to-deployment (ATD)

  24. Horizons – SCM (APO) versus ECC (ERP, R/3)

  25. Transport Load Builder (TLB)

  26. The system groups transportation recommendations for individual products together until the minimum values for volume, weight, and number of pallets specified in the TLB profile for creating a load have been reached. • If transportation recommendations cannot be converted, the system generates an alert and the planner can convert the transfers manually. • In the TLB profile, the minimum and maximum values for volume, weight, and pallets are defined per load. Transport Load Builder (TLB)

  27. In Customizing, you define if you want deployment to create stock transport orders or VMI sales orders. • Alternatively, you can use TLB to group together stock transfer of different products and generate stock transport orders or VMI sales orders with many items for different products. Available-to-deployment (ATD)

  28. TLB groups plan stock transfers into practical freight units. The system can create full pallets with mixed products. You can also define flexible rule relationships for linking the upper and lower limits. Transport Load Builder (TLB)

  29. Connecting upper limits with “and”, lower limits with “or”: The TLB cannot exceed the defined upper limits when the shipments are built. In addition, at least one of the lower limits must be reached or exceeded in line with how you defined the rule. • Connecting upper limits with “and”, lower limits with “and”: The TLB cannot exceed any of the defined upper limits. In addition, all defined lower limits must be reached or exceeded. • 3. As well as the standard connections, you can also establish user-defined relationship between the rules. Using the AND and OR operators as well as brackets, you can define which combination of these rules the TLB should use when building the shipments. TLB Rules

  30. Summary • Deployment determines which distribution requirements of the distribution centers or VMI customers can be covered by the existing supply. If quantities are sufficient to match demand, Deployment merely confirms the plan. If not it will adjust the stock transfer to take in account the missing quantities. • The TLB, ensure that the means of transport are loaded close to their full capacity or, at least, over their minimum capacity Deployment and Transport Load Builder (TLB)

  31. ATP check – also known as the availability check – represents an online search that should ensure that a company can provide the requested product at the requested time in the quantity requested by the customer. • The ATP check can use the basic methods to determine if a requirement can be confirmed. • Basic methods: • Capable-to-Promise (CTP) • Multilevel ATP Check Available-to-promise (ATP)

  32. CTP allows to check for free capacity, which normally performs at finished goods level. • There are two options to make CTP check: • Bucket-oriented CTP • Time-continuous CTP • Bucket-oriented CTP is to check the capacity based on a finite bucket capacity and doesn’t regard the detailed sequence of orders within the bucket. • CTP triggers the creation of planned orders by ATP check. Capable-to-promise (CTP)

  33. Triggering Events

  34. Procedure of Capable-to- promise (CTP)

  35. ML-ATP checks components according to ATP setting. It confirms a customer request if components for the product are available in time, i.e. taking the lead time to produce the finished product into account. If the components have a late availability, the availability of the finished product is recalculated in ATP using correlations. Multi-level-ATP (ML-ATP)

  36. Multi-level ATP (ML-ATP)

  37. Deployment & Available-to-promise (ATP)in SCM SAP Implementation EGN 5623 Enterprise Systems OptimizationFall, 2012

  38. Define SNP Deployment Profile

  39. Transport Load Builder (TLB)

  40. Assign the TLB profile to the transportation lane

  41. Transport Load Builder (TLB)

  42. Transport Load Builder (TLB)

  43. Transport Load Builder (TLB)

  44. ATP Categories

  45. Review PPM with type “S” • Define selection of profile • Finished products • Raw materials • Resources • Review forecast values for production • Create supply network plan using heuristic-multilevel. • Capacity leveling • Review production plan in product view SCM Homework

More Related