Show TOC

Function documentationIntegration of Purchase Orders and Purchase Requisitions

 

In this section, you can read about how data for purchase orders and purchase requisitions is exchanged between SAP Advanced Planning and Optimization (SAP APO) and the ERP system through Core Interface (CIF).

Prerequisites

You have created an active integration model for purchase orders and purchase requisitions.

Features

You have the following options for external procurement in SAP APO:

  • Standard purchase order/purchase requisition

  • Subcontracting purchase order/purchase requisition

  • Stock transport order/stock transport requisition

  • Consignment order/requisition

  • Purchase order/purchase requisition for make-to-order production and engineer-to-order production

  • Third-party purchase requisition (see Third-Party Order Planning)

To use third-party purchase requisitions, you have activated the business function Outsourced Manufacturing 2 in ERP Operations (LOG_MM_OM_2) for Enhancement Package 5 for SAP ERP 6.0 and the business function SCM-APO, Third-Party Order Planning in APO (SCM_APO_DRS_PLAN).

Only these types of purchase orders and purchase requisitions are integrated through CIF.

You can differentiate between two cases of integration:

  1. The purchase order or purchase requisition is generated in SAP ERP and is transferred to SAP APO. The target system performs rescheduling.

    Note Note

    In case of third-party purchase requisitions, the target system does not perform rescheduling. Scheduling of third-party purchase requisitions takes place in SAP ERP. The material availability date of the third-party purchase requisition at the distribution center, which is used for forecast consumption, is taken from the third-party order. The material availability date of the third-party purchase requisition at the supplier location is determined by the BAdI: Integration of External Third-Party Order Planning. For more information, see Customizing for SAP ERP under Start of the navigation path Sales and Distribution Next navigation step Sales Next navigation step Sales Documents Next navigation step Sales Document Item Next navigation step BAdI: Integration of External Third-Party Order Planning End of the navigation path.

    Third-party purchase requisitions, as opposed to other kinds of purchase requisitions, are not changed or rescheduled in SAP APO and are not sent back to SAP ERP. However, you can release the third party purchase requisitions that were covered completely by planned orders in SAP APO by using the Third-Party Demand and Supply Comparison function in Capable-to-Match (CTM). This removes the block for these third-party purchase requisitions in the SAP ERP system, so that the ordering process in SAP ERP can continue. For more information, see Third-Party Demand and Supply Comparison.

    End of the note.

  2. The purchase order or purchase requisition is generated in SAP APO and is transferred to SAP ERP. The target system performs rescheduling. For more information, see Creation of Purchase Orders and Purchase Requisitions from SAP APO.

Customer Exits

For more information about enhancements to the interface, see Customizing in the relevant system:

  • In SAP SCM under Start of the navigation path Integration with SAP Components Next navigation step Integration via APO Core Interface (CIF) Next navigation step Application-Specific Settings and Enhancements Next navigation step Settings and Enhancements for External Procurement End of the navigation path.

  • In SAP ERP under Start of the navigation path Integration with Other mySAP.com Components Next navigation step Advanced Planning and Optimization Next navigation step Application-Specific Settings and Enhancements Next navigation step Settings and Enhancements for External Procurement End of the navigation path.