SAP BBP_APO_CTR_PD_TO_CRM_MAP Function Module for
BBP_APO_CTR_PD_TO_CRM_MAP is a standard bbp apo ctr pd to crm map SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for bbp apo ctr pd to crm map FM, simply by entering the name BBP_APO_CTR_PD_TO_CRM_MAP into the relevant SAP transaction such as SE37 or SE38.
Function Group: BBP_BD_APO_CTR
Program Name: SAPLBBP_BD_APO_CTR
Main Program: SAPLBBP_BD_APO_CTR
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BBP_APO_CTR_PD_TO_CRM_MAP pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'BBP_APO_CTR_PD_TO_CRM_MAP'".
EXPORTING
IV_APO_LOGSYS = "
* IT_HEADER_PD = "
* IT_ORGDATA_PD = "
* IT_ITEM_PD = "
* IT_PARTNER_PD = "
IMPORTING
ET_ORDERADM_H = "
ET_ORDERADM_I = "
ET_ORGMAN = "
ET_PRODUCT_I = "
ET_APPOINTMENT = "
ET_PARTNER = "
ET_ORDPRP_I = "
ET_ITEMS_DEL = "
IMPORTING Parameters details for BBP_APO_CTR_PD_TO_CRM_MAP
IV_APO_LOGSYS -
Data type: LOGSYSOptional: No
Call by Reference: Yes
IT_HEADER_PD -
Data type: BBPT_PDS_CTR_HEADER_DOptional: Yes
Call by Reference: Yes
IT_ORGDATA_PD -
Data type: BBPT_PDS_ORGOptional: Yes
Call by Reference: Yes
IT_ITEM_PD -
Data type: BBPT_PD_CTR_ITEM_DOptional: Yes
Call by Reference: Yes
IT_PARTNER_PD -
Data type: BBPT_PDS_PARTNEROptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for BBP_APO_CTR_PD_TO_CRM_MAP
ET_ORDERADM_H -
Data type:Optional: No
Call by Reference: Yes
ET_ORDERADM_I -
Data type:Optional: No
Call by Reference: Yes
ET_ORGMAN -
Data type:Optional: No
Call by Reference: Yes
ET_PRODUCT_I -
Data type:Optional: No
Call by Reference: Yes
ET_APPOINTMENT -
Data type:Optional: No
Call by Reference: Yes
ET_PARTNER -
Data type:Optional: No
Call by Reference: Yes
ET_ORDPRP_I -
Data type:Optional: No
Call by Reference: Yes
ET_ITEMS_DEL -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for BBP_APO_CTR_PD_TO_CRM_MAP Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lv_et_orderadm_h | TYPE STRING, " | |||
| lv_iv_apo_logsys | TYPE LOGSYS, " | |||
| lv_it_header_pd | TYPE BBPT_PDS_CTR_HEADER_D, " | |||
| lv_et_orderadm_i | TYPE BBPT_PDS_CTR_HEADER_D, " | |||
| lv_et_orgman | TYPE BBPT_PDS_CTR_HEADER_D, " | |||
| lv_it_orgdata_pd | TYPE BBPT_PDS_ORG, " | |||
| lv_it_item_pd | TYPE BBPT_PD_CTR_ITEM_D, " | |||
| lv_et_product_i | TYPE BBPT_PD_CTR_ITEM_D, " | |||
| lv_it_partner_pd | TYPE BBPT_PDS_PARTNER, " | |||
| lv_et_appointment | TYPE BBPT_PDS_PARTNER, " | |||
| lv_et_partner | TYPE BBPT_PDS_PARTNER, " | |||
| lv_et_ordprp_i | TYPE BBPT_PDS_PARTNER, " | |||
| lv_et_items_del | TYPE BBPT_PDS_PARTNER. " |
|   CALL FUNCTION 'BBP_APO_CTR_PD_TO_CRM_MAP' " |
| EXPORTING | ||
| IV_APO_LOGSYS | = lv_iv_apo_logsys | |
| IT_HEADER_PD | = lv_it_header_pd | |
| IT_ORGDATA_PD | = lv_it_orgdata_pd | |
| IT_ITEM_PD | = lv_it_item_pd | |
| IT_PARTNER_PD | = lv_it_partner_pd | |
| IMPORTING | ||
| ET_ORDERADM_H | = lv_et_orderadm_h | |
| ET_ORDERADM_I | = lv_et_orderadm_i | |
| ET_ORGMAN | = lv_et_orgman | |
| ET_PRODUCT_I | = lv_et_product_i | |
| ET_APPOINTMENT | = lv_et_appointment | |
| ET_PARTNER | = lv_et_partner | |
| ET_ORDPRP_I | = lv_et_ordprp_i | |
| ET_ITEMS_DEL | = lv_et_items_del | |
| . " BBP_APO_CTR_PD_TO_CRM_MAP | ||
ABAP code using 7.40 inline data declarations to call FM BBP_APO_CTR_PD_TO_CRM_MAP
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.Search for further information about these or an SAP related objects