The logic that underlies the assignment of fields between R/3 and APO means that the values for the data fields in APO are built based on information in R/3. This logic can be queried directly at the corresponding point within function modules and Includes. Access is gained using transaction SE37 for function modules, and transaction SE38 for Includes.

The following list contains all the Includes and function modules from the objects in question that are relevant for APO-R/3 mapping and from which the relevant information can be extracted.

The following function modules are relevant for stocks:

• CIF_STOCK_APO001_MAP (APO 2.0A)
• CIF_STOCK_APO001_MAP_2 (APO 3.0A)

For the current release PI 2000.1, mapping of the APO structures in R/3 is carried out in the function module ME_APO_GENERATE_REQ_PO in the form ONVERT_TABLES_FROM_APO.

The following function modules are relevant for production orders and process orders in R/3:

• CIF_ORDER_CONVERT (R/3 outbound)
• CIF_APOORDER_CONVERT_TO_R3 (R/3 inbound)

All function modules required for integrating the campaign into R/3 are located in the function group CPCM1. The following function modules are relevant for the campaign:

• PCM_DATA_SELMAP
• PCM_DATA_SELMAP_PUSH
• BAPI_PCM_SAVE_MULTIPLE
• BAPI_PCM_DELETE_MULTIPLE

In APO, the corresponding function group is called PCM_BAPI and has the following function modules:

• BAPI_PCM_ADD_POSTIONS
• BAPI_PCM_DELETE_MULTIPLE
• BAPI_PCM_REMOVE_POSTIONS
• BAPI_PCM_SAVE_MULTIPLE

Product allocation is transferred via ATP testing (online). When updating, it is transferred via the standard SD module.

The transactions used for the transfer are QTSP (customizing) and QTSA (product allocation). These can be used as an example for the transfer. The CIF modules are called up in these transactions.

The APO function modules are /SAPAPO/QUOTA_PROCEDURE_GET and /SAPAPO/QUOTA_ALLOCATION_GET.

The table /SAPAPO/PRODFLOW describes how orders and storage resources interact. The table is filled in by the function module /SAPAPO/PFLOW_PPM_MAINTAIN.

Delivery documents are transferred to APO by means of the function group V45V. The following Includes are relevant for this:

• Include LV45VF0V FORM VB_APO_CREATE (Structuring of the requirement interface to APO. Structuring is based on R/3 application data which is transferred to the R/3 update task.)
• Include LV45VF0V FORM VB_APO_CREATE_ORD. (Structuring of the document interface to APO. Structuring is based on R/3 application data which is transferred to the R/3 update task.)
• Include LV45VF0V FORM VB_APO_PUT (calling up the BTE, which transfers the qRFC to APO)

The following function modules are relevant for mapping in CIF:

• /SAPAPO/CIF_CD_MAPEXT (delete confirmation message: generated mapping module for PUB type CD)
• /SAPAPO/CIF_RP_MAPEXT (reporting points: generated mapping module for PUB type RP)
• /SAPAPO/CIF_RP_MAPEXT (confirmation message: generated mapping module for PUB type CF)

The following list contains function modules and Includes (and the relevant subprograms within the Includes) for the object planned order.

• CONVERT_APO_TO_R3_MDPA (data conversion APO -> R/3. MDPA order header for order_inbound)
• CONVERT_APO_TO_R3_PLAF (data conversion APO -> R/3. PLAF order header for order_inbound)
• CONVERT_APO_TO_R3_PLAF (data conversion APO -> R/3. Planned order for order_inbound)
• APO_CONVERT_PLORD_MDPA (converts BOM explosion result into CIF-R/3 format using mdpa)
• CONVERT_R3_TO_APO_COMP (converts planned order component data into APO-CIF format)
• CONVERT_R3_TO_APO_COMP (converts planned order header data into APO-CIF format)
• APO_CONVERT_PLANNED_ORDER (converts planned order into APO-CIF structures, including header data and component data)

• CIF_APOORDER_CONVERT_TO_R3 (converts planned order data from APO to APO-CIF format)
• CIF_ORDER_CONVERT (converts planned order data from APO-CIF to APO format)

The following function modules and data fields are relevant for the transfer of master data from the R/3 System to create a PPM in SAP APO:

The corresponding function module in R/3 is CIF_MATERIAL_PRODUCT_MAP

The following function modules are relevant for R/3 capacity and APO resources

/SAPAPO/CIF_RES_INBOUND (mapping the inbound structures onto BAPI structures)

BAPI_RSSRVAPS_SAVEMULTI_30A (BAPI for creating and changing model-independent resources and for assigning to model 000)

The following function modules are relevant for transferring planning file entries (APO -> R/3):

• RPM_PLAN_FILE_SEND (APO)
• MMRP_CIF_PLAN_FILE_INBOUND (R/3)

The following function modules are relevant for transferring dependent requirements (APO -> R/3):

• MMRP_CIF_REQ_FOR_MAT_OUTBOUND (APO)
• MMRP_CIF_REQS_GET (R/3)

Consumption data is sent from R/3 to APO (initial transfer)

Function modules come under the E-class CIF. In the function group, the following function modules are relevant to the usage scenario:

• cif_salfig_create (read the MVER data Output structure CIF_SALFIG {R3-Struktur})
• cif_sermsl_create (mapping CIF_SALFIG ® CIF_SERMSL (APO structure)

The CIF_SERMSL is a transfer structure and is received by the VMI interface in APO.

Because location in APO and R/3 are not identical, the mapping fields are executed individually. The following data fields are relevant for the transfer of location data from the R/3 System to APO:

Location: Supplier Description

Location: Mrparea

Location: Carrier

Location: Transportation Zone