A product availability check or a check against the forecast can be carried out at component level. Scope of check, shortage checks inclusion of checking horizons are taken into account and the rules-based ATP check is supported.

An availability check, which should not be compared with the ATP check, is carried out at component level using the pegging functions. In the pegging structure all receipt and requirement categories are handled in the same way. No distinction is therefore made according to ATP categories. Scopes of check, shortage checks, use of a checking horizon and the rules-based ATP check are not supported.

In the multilevel ATP check, characteristics-dependent planning (CDP) is not possible. The reason for this is that CDP works with characteristic value assignments on the receipt and requirement elements of orders. These do not exist in the ATP time series.

Characteristics-dependent planning (CDP) can be fully implemented for CTP.

ATP tree structures are not taken into account in planning. In other words, no orders exist at the time of the check. A dependent requirement of a component is only visible when the ATP tree structure has been converted into PP/DS orders . If a very large scheduling horizon is selected, PP/DS orders are generated immediately for each multilevel ATP check. The dependent requirements are then covered immediately.

PP/DS orders always appear immediately in CTP. Even if the planned orders are temporary, they are order objects on which resources can be utilized directly.

For more information, see Standard Planning Procedure 3 .

The dates are determined using a simple lead time scheduling.

A simple lead time scheduling has the following properties:

It does not take account of resource schedules

It is based exclusively on the production calendar of the location and is thus location-dependent.

It does not take account of any lot size specifications, but rather always uses the lot-for-lot order quantity.

It is not aligned to bucket limits.

No blocks are taken into account

For more information, see Determination of Component Quantities and Component Requirement Dates in MATP .

The dates are determined using Detailed Scheduling (in SAP liveCache).

The results overview offers an integrated display of the check results for the sales order item and all components checked. A missing parts list displays the components and characteristic values there that have lead to a delay or reduction in the confirmation.

You can check the results of the CTP processing in a PP planning log .

The product availability check at component level promises improved performance since the check is made against ATP time series.

The scheduling of complete planned orders can lead to a poorer performance.

No special logic has been implemented for checking the availability of resources.

A type of “daily production rate“ can be represented by a product allocation and a check is carried out against this allocation. This check is only for exact days.

The product allocation is reduced during the check. The advantage of this is that no sequencing is anticipated through the check. The disadvantage of this method is that the assignment of the real resources and the corresponding product allocation can diverge. If a planned order that results from a multilevel ATP check is rescheduled, the assignment of the product allocation is not adjusted.

The planned order can be scheduled finitely on the resources immediately. This can be configured.

The order data, cumulated in days, is contained in the ATP time series’ used for the multilevel ATP check. A receipt can cover a requirement if the receipt is made on the same day. However, the receipt can lie temporally after the requirement, depending on the Customizing settings.

If no suitable receipt exists for a requirement and a multilevel ATP check is carried out for the product, a receipt element is created according to the Customizing settings for bucket parameters.

CTP works to the exact second.

Block planning is not supported in the multilevel ATP check since block planning works with functions from CDP. It is therefore not possible to immediately assign planned orders, which result from the multilevel ATP check, to specific blocks automatically.

Setup problems can be solved using block planning .

Neither minimum nor maximum lot sizes are considered in the multilevel ATP check. Rounding quantities and fixed lots are not taken into account either. Weekly lots are not possible. ATP does not have lot sizes. The lot-for-lot order quantity is always used.

Order quantities are adopted from ATP. An order split or an order combination is only possible manually in PP/DS and only then if neither configuration nor product substitutions exist.

A lot size calculation is carried out; in other words, fixed, minimum, and maximum lot sizes are taken into account.