mySAP SCMGlobal Available To Promise

Method: Multi-Level Available To Promise

Patti KimlerProduct Manager PTU ApplicationsSAP Labs, LLC

SAP AG 2003, Title of Presentation, Speaker Name / 2

Multi-Level ATP: Process

Delivery Proposal /

Order Conf.

Execution of ATP methods according tocheck instructions

Order entry viaSAP R/3, SAP CRM, Internet, other systems

DeliveryGroup

Global ATP on Component

level

Bill of Material explosion

Planning (dependent on

horizon)

Inquiry / Sales Order entry

Transportation & Shipment

Scheduling

Creation of receipt elements (planned orders,purchase requ.)

Iterative loop

Result explanation with display of „constraining item(s)“

Global ATP on Finished

Good level

Execution of ATP methods according tocheck instructions

SAP AG 2003, Title of Presentation, Speaker Name / 3

Multi-Level-ATP: Checking Sequence

R/3, CRM, Internet etcR/3, CRM, Internet etc APO 3.1APO 3.1

ATP PP/DS

Order entry Check of Finished Good(s)

Bill Of Material ExplosionCheck of Components

Display (optional)

Transfer of ResultsDisplay of Results (optional)

Saving of Results Creation of ATP-Trees

Aggregation of qunatity reservations.

AT

P-B

AP

Is

Planning (optional –

dependent on Horizon)

SAP AG 2003, Title of Presentation, Speaker Name / 4

Multi-Level ATP: Functionality

Multi-level BOM explosion

ATP-Check on component level

Rules based ATP on component level and with stock transfer orders

Possibility to exclude components from the check

Capacity check on daily buckets (capacity allocation)

Receipts can be created at a later point of time with a planning run or immediately if the order is within a certain horizon

Delivery Groups supported

Presentation of „constraining“ items/characteristics

SAP AG 2003, Title of Presentation, Speaker Name / 5

BOM Explosion / Rules / ATP Tree Structure

Bill of Material(PPM, iPPE, RTO)

Rules Based ATP

BOM Explosion

BOM ExplosionC2

2

1 3

Alternative

Component Change of Source Location

Customer Order End Item

2

1 3

Alternative

Component Change of Source Location

ATP Tree Structure

2

1 3

Alternative

Component Change of Source Location

C1

SAP AG 2003, Title of Presentation, Speaker Name / 6

Planning

The ATP Tree Structure is created in the APO-DB during the saving of the sales order and represents the BOM Structure, enhanced with Material/Location substitutions

Every node of the ATP Tree Structure will be translated into an order (receipt element) dependent on the horizon

Configuration and delivery priorities are taken over from the sales order The confirmed quantities of the dependent demands are equal to the

requested quantities for unchecked components

SAP AG 2003, Title of Presentation, Speaker Name / 7

Effectivity Interval / Confirmation

The Multi-Level ATP-Check is a „two step check“. The second check is responsible for solving eventually effectivity date problems.

Configuration possibilities:

Confirmation of possible quantities at the requested date

Confirmation of quantities at the earliest possible date

Confirmation of full quantities

In case there are still remaining requirements, the system can be configured to either create the demand on end-item level or on component level:

End-item level:

Without rules: one unconfirmed sales order item

With rules: depending on settings of remaining requirements

Component-level: sales order fully confirmed, Alert situation on component

SAP AG 2003, Title of Presentation, Speaker Name / 8

Capacities

Daily capacities per product, location and configuration characteristics

Realization with allocations (capacity allocations) possible on every BOM level

Creation of capacity allocations by ... ... DP (CBF) ... SNP-Planning

Capacity allocation reservation is assigned to sales order items (also in case of multi-level BOMs)

Scheduling based on average duration of activity relationships

SAP AG 2003, Title of Presentation, Speaker Name / 9

Change of Sales Documents / Backorder Processing

Multi-level ATP before translation into receipt elements The existing ATP Tree Structure will be replaced by a new one

Multi-level ATP after translation into receipt elements The exisiting order network for the sales order itme is internally

deleted (only for make to order production)

Enhanced Filter for Backorder Processing: Selection of sales order items by a component (reading of ATP-Tree

Structures)

Item by Item or mass ATP check during Backorder Processing

SAP AG 2003, Title of Presentation, Speaker Name / 10

Restrictions

The configuration has to be passed on by the calling system.

Configuration model and RBA substitutions have to be consistent

Material substitution on component level does not lead to a new product or to a new configuration on finished good level

Determination of characteristic values which are leading to a delay is not always possible

Multi-level configuration is possible only with iBase but not with CDP

Only exact lot sizes are supported by Mulit-level ATP

Phantom levels are not known by the ATP check

SAP AG 2003, Title of Presentation, Speaker Name / 11

Restrictions

No automatic synchronization of capacity allocations and resource reservations

Location substitution with cross system stock transfers is not possible

References between Sales Documents which have ATP Tree Structures are not possible

Mixing of CTP and Multi-level ATP for one product is not supported

Sales document changes with new explosion of BOMs can only be used for „make to order production“

Only planned orders with specific statuses can be deleted during change of sales documents