Select language:

Object documentationIntegration of Planned Orders


A planned order is a procurement proposal that is generated manually or automatically during planning and that is converted into a purchase requisition or a manufacturing order. Planned orders can be generated in both the ERP system and in SAP APO.


Create Planned Orders in the ERP System

A planned order (PP-MRP) can be generated in the ERP system in the following way:

  • Manual creation

  • In the MRP planning run

A planned order that is manually created or changed in the ERP system is automatically fixed for MRP. That is, it can no longer be changed by the planning run. However, if a planned order is changed within the context of the planning run (for example, because of a change to the bill of material), it is not fixed.

The planned order is either converted to a manufacturing order or a purchase requisition, depending on the order type (for example, warehouse order or standard purchase order), procurement type (external procurement or in-house procurement) and special procurement type of external procurement (consignment, subcontracting, or stock transfer). For more information, see Convertibility of Planned Orders.

Routing and Bill of Material Selection

When creating a planned order in the ERP system, the system uses the production version to select the bill of material (BOM). A production version must exist in the ERP system and the indicator for selecting alternative BOMs (Selection by Production Version) must be set in the material master on the MRP 4 tab page.

A production version must exist in the ERP system so that SAP APO is able to generate a production process model (PPM). The production version in the ERP system is a prerequisite for carrying out planning in SAP APO.

For lead-time scheduling (PP-MRP) or manual scheduling of the planned order, the system selects the routing for scheduling. The data for routing is not maintained in the planned order. In the planned order, only those detailed capacity requirements are saved from which the system calculates the scheduling data.


There are two scheduling types: Basic date determination and lead-time scheduling. The basic start and end dates are determined using the in-house production time in the material master on the Work Scheduling tab page. Lead-time scheduling is carried out using the operation duration in the routing. For lead-time scheduling, the buffer times (float before and after production) maintained in the scheduling margin key are relevant for calculating the production start and end dates.

Note Note

For performance reasons, we do not recommend using lead-time scheduling.

End of the note.
Create Planned Orders in SAP APO

A planned order (SCM-APO-PPS) can be generated in SAP APO in the following ways:

  • Manual creation

  • In Production Planning and Detailed Scheduling (PP/DS)

    • Immediately using automatic planning

    • In the planning run using automatic planning

  • In Supply Network Planning (SNP) in the SNP planning run

  • In Capable-to-Match (CTM) in the CTM planning run

  • By converting an SNP planned order to a PP/DS planned order

Routing and Bill of Material Selection

When creating a planned order in SAP APO, the system uses lot size and costs to select the valid PPM. The PPM contains only the BOM data and routing data that is relevant at the time it is transferred. That is, there is no validity-period-dependent selection of BOM and routing or validity-period-dependent selection of operation or BOM item.

For more information on planning with limited validities of BOMs and routings, see Documentation Note 385602.


For the SNP planned order, the system schedules the start and end dates using the duration of activities in the SNP PPM. For the PP/DS planned order, the system schedules the start and end dates using the duration of activities in the PP/DS PPM.

Transfer Planned Orders from ERP to SAP APO

Planned orders that are generated in SAP APO can either be assigned to Supply Network Planning (SNP) or Production Planning and Detailed Scheduling (PP/DS). Planned orders that are created in the ERP system and transferred to SAP APO can be mapped as either PP/DS or SNP planned orders. For more information, see Controlling the Initial Transfer of Planned Orders and Creating SNP Planned Orders from SAP R/3.

The following prerequisites must be met so that planned orders can be transferred from ERP to SAP APO and vice versa.

  • The material masters must be transferred to SAP APO. PPMs must exist for planning in SAP APO. The relevant integration models must be active.

  • An active integration model for planned orders must exist in the ERP system.

  • An active integration model must also exist for materials, so that the components of the planned order are transferred.

  • The relevant distribution definitions must be maintained in SAP APO, so that planning results can be transferred from SAP APO to ERP.

    Caution Caution

    Publishing planned orders from SAP APO to ERP can lead to a loss of performance. Therefore, you should check whether the planned orders are really needed in the ERP system.

    End of the caution.

The possibility of retaining activity dates allows SAP APO avoid performing a rescheduling when orders are transferred from ERP to SAP APO. The operations of production orders must have the status DSEX in ERP to retain their activity dates in SAP APO. The activity dates of planned orders are generally retained as long as the PPM or PDS is not re-exploded. Limitations include:

  • Goods receipt time-processing activities are always scheduled. However, with correct and unchanged settings at the handling resource and with an unchanged goods receipt processing time, this should not have an impact on the dates of the goods receipt time-processing activity.

  • Not all finite strategies are supported with this function. For some finite strategies, the system switches to infinite scheduling if the activity dates are retained. However, we recommend infinite strategies in the strategy profile for CIF integration in any case.

  • Retaining activity dates overrules the settings for synchronization for a resource. If activity dates are retained in SAP APO, existing violations of other boundary conditions in SAP APO are not removed, for example, violations of pegging relationships and relationships between operations.

Customer Exits and Business Add-Ins (BAdIs)

Customer Exits for Planned Orders and Manufacturing Orders

  • APOCF004 ‑ Enhancement for Inbound Processing of Planned Orders and Manufacturing Orders

  • APOCF020 - Order Interface for Customer-Specific Fields (After Posting in SAP liveCache or to the Database)

  • APOCFPIP - Enhancement for the Publication of In-House Production Orders (Planned Orders, Manufacturing Orders)

Business Add-In

  • /SAPAPO/CL_EXCIF_IP - Comparison of APO Data and CIF Data

    This BAdI controls if and when the activity dates planned in SAP APO should be rescheduled, or if a change to the order quantity in the ERP system leads to a proportional change to receipt and requirement quantities.

In the ERP System

Customer Exits for Planned Orders and Manufacturing Orders

  • CIFORD01 - Enhancement for Order Inbound Interface (SAP APO — ERP)

  • CIFORD02 - Enhancement for the Transfer of Customer-Specific Order Fields (ERP — SAP APO)

  • CIFORD03 - Enhancement for Inbound Customer-Specific Fields in the In-House Production Order (SAP APO — ERP)

    For more information, see Customizing for Integration with Other SAP Components under Start of the navigation path Advanced Planning and Optimization Next navigation stepApplication-Specific Settings and Enhancements Next navigation stepSettings and Enhancements for In-House Production End of the navigation path.

More Information

  • Questions About Integrating Planned Orders

  • Planned Order (PP-MRP)

  • Lead-time Scheduling (PP-MRP)

  • Planned Order (SCM-APO-PPS)

  • For more information on planning with limited validities of BOMs and routings, also see Documentation Note 385602Information published on SAP site.