Show TOC

 Constraints

Planned Order Integration

The following constraints apply to planned order integration:

  • Pegging

    Because no mapping with the planned order components takes place in APO inbound, fixed pegging may be lost as a result of integration with SAP R/3.

  • Mode Change in SAP APO and Adoption in SAP R/3

    There is no integration for capacity requirements of planned orders, in other words, SAP R/3 cannot tell which resource a planned order occupies. The price calculation in SAP R/3 is always carried out using the PP/PI master data. The current routing with the valid standard sequence is always exploded here too, to determined the actual prices.

Sequence Change and Mode Change

  • Sequence change in SAP R/3

    A sequence change in SAP R/3 leads to the loss of the alternative modes in the APO order.

  • Mode change and alternative modes

    If alternative modes – possibly with mode linkage - have been created for alternative sequences of the R/3 routing in the APO PPM then a mode change carried out in SAP APO does not lead to a sequence change in SAP R/3 but only to a work center change. This leads to deviations in the standard cost estimate and, in the confirmation, to incorrect default values as regards the activity to be confirmed.

    For more information about mapping of alternative and parallel sequences in APO integration see the SAP Note 437400 - Alternative and parallel sequences in APO integration.

Master Recipe

In the master recipe, it is possible to carry out the classification of an operation with the class type Resource in order to define alternative work centers. The system then generates alternative modes for the corresponding activities from this information when the PPMs are transferred.

Work Center Change in SAP R/3

A work center change in an R/3 operation or an R/3 phase does not always lead to a change to the resource schedule in SAP APO.

A work center change from SAP R/3 is only adopted in SAP APO in the following instances:

  • The order has no PPM in SAP APO.

  • The order has a PPM in SAP APO and work center sent from SAP R/3 with the operation is defined as an alternative work center in the PPM. Therefore, there is a mode for the work center in the PPM.

For more information about constraints in the work center change of the production order in SAP R/3 see the SAP Note 399386 – Changing Work Center in R/3 to APO .

Integration of Order Reservations and Dependent Requirements

The transfer or dependent reservations for manufacturing orders and dependent requirements for planned orders from SAP R/3 to SAP APO is only carried out together with the orders, in other words, the orders must be transferred if you want SAP APO to have access to the requirements.

Regardless of orders, only manual reservations can be transferred from SAP R/3 to SAP APO.

Phantom Assembly and Multiple Phantoms in the PPM

When the PPM is transferred the phantom assemblies are also exploded, the phantoms themselves are not transferred. There is also no hierarchy information for the components of a phantom assembly. The PPM in SAP APO has a flat structure.

If phantom assemblies occur more than once in an R/3 BOM there may be mapping problems in order integration. This means that unique mapping using BOM information is not possible and incorrect component adjustments may be made. Therefore, you should not use the same phantom assembly more than once in integrated orders.

For more information see the SAP Note 436395 - SAP R/3-> SAP APO Transfer of Dummy Assemblies.

APO Planned Orders from Characteristics-Dependent Planning (CDP)

APO planned orders that you have created via characteristics-dependent planning SAP APO are automatically converted into manufacturing orders (production or process orders) when the first transfer to SAP R/3 takes place.

It is not possible to generated R/3 planned orders for CDP planned orders.

Discontinuation and Production Interchangeability

R/3 discontinuation is not supported in SAP APO. It is replaced by product interchangeability(PAT)

Background documentation 

SAP APO does not recognize the discontinuation used in SAP R/3.

For in-house production orders with components with discontinuation only the part to be discontinued or the follow-up part is transferred from SAP R/3 to SAP APO. The entire requirement quantity is also transferred to the part to be discontinued or the follow-up part.

In the case of manufacturing orders , as soon as the requirement can no longer be covered by the part to be discontinued the entire requirement quantity is diverted to the follow-up part. Only the follow-up part is then transferred to SAP APO, the components for the part to be discontinued are deleted in SAP APO.

In the case of planned orders, the part to be discontinued is transferred with the entire quantity in this situation.

For more information see the SAP Note -487127 - SAP R/3-> SAP APO Terminate Planned Order with Simple Discontinuation.

There are also special constraints as of SAP APO 3.1 when using the multi-level ATP for processing alternatives and discontinuation.

For more information, see the SAP Note 510313 – ATP Product Substitution and Integration with R/3 .

For more information, see the section Product Interchangeability .

External Processing Operations and Subcontracting

The following constraints apply to external processing with scheduling via work center:

  • The work center must be in the same plant as the PPM in SAP APO only recognizes one plant.

  • Subcontracting with subcontracting components is not supported because the order reservations in SAP APO would never be reduced and the purchase order cannot be integrated into SAP APO (as it has no material reference).