Planned orders and stock transfer orders cannot be split, no partial delivery

The splitting of planned orders or stock transfer orders is not possible in the CTP process. During the CTP check, ATP transfers the control over to PP/DS. Thus, PP/DS receives the control over the process at component level if a multi-level check is executed according to the planning procedure defined in the product master. This applies to the standard planning procedure 3 (cover dependent requirements immediately) and to the standard planning procedure 1 (manual planning with check). In these two procedures, the planning algorithm is not able to split quantities. That is, it is not possible to confirm a partial quantity according to the available component quantity. A sales order is only confirmed if the desired quantity can be produced completely. If not enough components are available, the system cannot create the planned order for the finished product due to the missing quantity. The sales order is not confirmed.

Scope of check cannot be set for planning procedure Manual Planning with Check

This availability check in PP/DS is based on pegging and not on the ATP check. For this reason, the scope of the check cannot be set.

The pegging network is used for the check. All the receipt and requirement elements of a pegging network are treated equally. A differentiation between the various ATP categories is, therefore, not necessary. The same applies to the multi-level scheduling that you can execute in the CTP process. It is also not possible to use the scope of the check here to define whether or not a new receipt element should be created at a lower level.

You cannot set the scope of check when using configuration or CDP characteristics

In a CTP check, you can also take CDP characteristics into account. A prerequisite here is that you have selected the setting Characteristics Evaluation in the Production Type field in the check mode. In this case, the pegging network in the liveCache is also evaluated. The ATP categories from the scope of the check are not taken into account.

Stock search with CDP characteristics is not possible (comparable with the batch search in R/3)

CTP is not suitable for SD delivery schedules

The CTP process is only suitable for the item-based procedure. On the other hand, SD scheduling agreements represent a schedule line-based procedure. This form of processing causes performance problems as one scheduling agreement item may have a lot of schedule lines that have to be checked. If, for example, you create, change or delete a schedule line in a scheduling agreement item, all the schedule lines in this item have to be rechecked.

Another disadvantage is that confirmed schedule lines loose the confirmed desired date if you insert new schedule lines in between these schedule lines or if you increase or move these schedule lines.

Use of period lot sizes not possible

If you use a period lot size, an additional requirement in a particular period increases the planned order quantity. This generally also increases the lead time of the planned order in the period in question. This, in turn, brings forward the dependent requirements dates. Therefore, for period lot sizes, there is a danger that an already confirmed sales order is confirmed on the basis of a production plan that is now no longer feasible. For this reason, you cannot use any period lot sizes in the CTP process. (CTP and period lot size are mutually exclusive)

CTP combined with safety stocks or safety days' supply is not supported in SAP APO.

Use of the requirements strategy Planning without final assembly not possible

In the strategy, Planning without Final Assembly, the procurement elements of the finished product (planned orders with the order category VP) reserve resources and components in the planning segment. However, the actual final assembly is not triggered until the sales order has been received. Here, a planned order is created for the sales order in the make-to-stock segment and the procurement elements in the planning segment are reduced accordingly. If you now use CTP with the strategy planning without final assembly, the system has to delete procurement elements from the planning segment during the check to ensure free capacity and available components for the planned orders to be created in the make-to-stock segment. The deletion of orders by a termination of the sales order creation using /N can no longer be reversed by the activated task handler. See also: Canceling Sales Order Creation Using /n

Therefore, the strategy planning without final assembly cannot be used in the CTP process.

You cannot use CTP for backorder processing. The main reason for this is the poor performance of the procedure. In backorder processing, all selected sales order items are checked individually. Then the system has to recreate the corresponding procurement elements individually. Here, the usual measures (for example, net change planning, parallelization and mass accesses to the database) available in production planning to improve performance cannot be used. If backorder processing is performed for products that use CTP, existing receipts are considered but no new receipts are created.

A combination of backorder processing and the process, Capable-to-Match (CTM) that is very similar to CTP, is possible.

For more information, seebackorder processing and Capable-to-Match .

CTP cannot be used in the availability check of dependent requirements, reservations or requirements from stock transport requisitions.

You cannot use CTP in the above-mentioned cases. In the check instructions, you can define that production is to be accessed for the corresponding business events. However, the process cannot be executed completely as temporary orders remain in the system.

See also: Check Instructions

Limitations of Bucket-Oriented Capacity Check:

The CTP heuristic (SAP_CTG_DLG), which interactively carries out an availability check for the sales order in the APO Product View, does not cover all the functions of the online CTP check performed out of a sales order in SAP ERP.

Delete-switch and redistribution are not handled by the CTP heuristic, while the fixed pegging is also not altered by it.

As CTP uses the order liveCache and not the ATP time series, the use of CTP in combination with other rules within a rules-based ATP check might undermine the purpose of the ATP rules. For example, if a maximum allowed delay is used in a first rule to prevent the usage of stock on hand for demands in the future, CTP (production directly) is called with the complete required quantity (though there is stock available). In this case, CTP performs a net requirement calculation and does not create any additional receipts.

The combination of CTP and co-products (when more than one output product of a planned order is planned with CTP) is not supported in SAP APO.

Due to capacity restrictions, a planned order may be scheduled after the requirement date (which is the explosion date). If the scheduled date is outside the validity horizon for the order, a new order explosion is required with probably different components or operations, which would lead to time-consuming calculations or even loops. The CTP algorithm therefore supports only one new order explosion and terminates with an error if it is not successful.

The planning strategies Planning Without Final Assembly and Planning Product are not supported with CTP. The planning strategy Planning With Final Assembly is only supported with CTP if the ATP time series are used for the ATP check (production type standard in the check mode). If not, the forecast demands reduce the available quantity.