SAP BBP_CTR_MAP_PD_TO_DB Function Module for
BBP_CTR_MAP_PD_TO_DB is a standard bbp ctr map pd to db 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 ctr map pd to db FM, simply by entering the name BBP_CTR_MAP_PD_TO_DB into the relevant SAP transaction such as SE37 or SE38.
Function Group: BBP_PDMAP
Program Name: SAPLBBP_PDMAP
Main Program: SAPLBBP_PDMAP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BBP_CTR_MAP_PD_TO_DB 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_CTR_MAP_PD_TO_DB'".
EXPORTING
IS_HEADER = "
* IT_ATTACH = "
IMPORTING
ES_HDRADM = "
ES_HDRHGP = "
ET_ATTACH = "
TABLES
IT_ITEM = "
* ET_BUP = "
* ET_ORGDATA = "
* ET_LONGTEXT = "
* ET_STATUS = "
IT_PARTNER = "
* IT_LONGTEXT = "
IT_ORGDATA = "
IT_ACTVAL = "
IT_STATUS = "
* ET_ITMADM = "
* ET_ITMIGP = "
* ET_PARTNER = "
IMPORTING Parameters details for BBP_CTR_MAP_PD_TO_DB
IS_HEADER -
Data type: BBP_PDS_HEADEROptional: No
Call by Reference: No ( called with pass by value option)
IT_ATTACH -
Data type: BBPT_PDS_ATT_TOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BBP_CTR_MAP_PD_TO_DB
ES_HDRADM -
Data type: BBP_PDS_HDR_ICOptional: No
Call by Reference: No ( called with pass by value option)
ES_HDRHGP -
Data type: BBP_PDS_HGP_ICOptional: No
Call by Reference: No ( called with pass by value option)
ET_ATTACH -
Data type: BBPT_PDS_ATT_T_ICOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BBP_CTR_MAP_PD_TO_DB
IT_ITEM -
Data type: BBP_PDS_ITEMOptional: No
Call by Reference: Yes
ET_BUP -
Data type: BBP_PDS_BUP_ICOptional: Yes
Call by Reference: Yes
ET_ORGDATA -
Data type: BBP_PDS_ORG_ICOptional: Yes
Call by Reference: No ( called with pass by value option)
ET_LONGTEXT -
Data type: BBP_PDS_LONGTEXTOptional: Yes
Call by Reference: No ( called with pass by value option)
ET_STATUS -
Data type: CRM_JESTOptional: Yes
Call by Reference: Yes
IT_PARTNER -
Data type: BBP_PDS_PARTNEROptional: No
Call by Reference: No ( called with pass by value option)
IT_LONGTEXT -
Data type: BBP_PDS_LONGTEXTOptional: Yes
Call by Reference: Yes
IT_ORGDATA -
Data type: BBP_PDS_ORGOptional: No
Call by Reference: No ( called with pass by value option)
IT_ACTVAL -
Data type: BBP_PDS_ACTVALOptional: No
Call by Reference: No ( called with pass by value option)
IT_STATUS -
Data type: BBP_PDS_STATUSOptional: No
Call by Reference: No ( called with pass by value option)
ET_ITMADM -
Data type: BBP_PDS_ITM_ICOptional: Yes
Call by Reference: Yes
ET_ITMIGP -
Data type: BBP_PDS_IGP_ICOptional: Yes
Call by Reference: No ( called with pass by value option)
ET_PARTNER -
Data type: BBP_PDS_PARTNEROptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BBP_CTR_MAP_PD_TO_DB 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: | ||||
| lt_it_item | TYPE STANDARD TABLE OF BBP_PDS_ITEM, " | |||
| lv_es_hdradm | TYPE BBP_PDS_HDR_IC, " | |||
| lv_is_header | TYPE BBP_PDS_HEADER, " | |||
| lt_et_bup | TYPE STANDARD TABLE OF BBP_PDS_BUP_IC, " | |||
| lt_et_orgdata | TYPE STANDARD TABLE OF BBP_PDS_ORG_IC, " | |||
| lt_et_longtext | TYPE STANDARD TABLE OF BBP_PDS_LONGTEXT, " | |||
| lt_et_status | TYPE STANDARD TABLE OF CRM_JEST, " | |||
| lv_es_hdrhgp | TYPE BBP_PDS_HGP_IC, " | |||
| lv_it_attach | TYPE BBPT_PDS_ATT_T, " | |||
| lt_it_partner | TYPE STANDARD TABLE OF BBP_PDS_PARTNER, " | |||
| lv_et_attach | TYPE BBPT_PDS_ATT_T_IC, " | |||
| lt_it_longtext | TYPE STANDARD TABLE OF BBP_PDS_LONGTEXT, " | |||
| lt_it_orgdata | TYPE STANDARD TABLE OF BBP_PDS_ORG, " | |||
| lt_it_actval | TYPE STANDARD TABLE OF BBP_PDS_ACTVAL, " | |||
| lt_it_status | TYPE STANDARD TABLE OF BBP_PDS_STATUS, " | |||
| lt_et_itmadm | TYPE STANDARD TABLE OF BBP_PDS_ITM_IC, " | |||
| lt_et_itmigp | TYPE STANDARD TABLE OF BBP_PDS_IGP_IC, " | |||
| lt_et_partner | TYPE STANDARD TABLE OF BBP_PDS_PARTNER. " |
|   CALL FUNCTION 'BBP_CTR_MAP_PD_TO_DB' " |
| EXPORTING | ||
| IS_HEADER | = lv_is_header | |
| IT_ATTACH | = lv_it_attach | |
| IMPORTING | ||
| ES_HDRADM | = lv_es_hdradm | |
| ES_HDRHGP | = lv_es_hdrhgp | |
| ET_ATTACH | = lv_et_attach | |
| TABLES | ||
| IT_ITEM | = lt_it_item | |
| ET_BUP | = lt_et_bup | |
| ET_ORGDATA | = lt_et_orgdata | |
| ET_LONGTEXT | = lt_et_longtext | |
| ET_STATUS | = lt_et_status | |
| IT_PARTNER | = lt_it_partner | |
| IT_LONGTEXT | = lt_it_longtext | |
| IT_ORGDATA | = lt_it_orgdata | |
| IT_ACTVAL | = lt_it_actval | |
| IT_STATUS | = lt_it_status | |
| ET_ITMADM | = lt_et_itmadm | |
| ET_ITMIGP | = lt_et_itmigp | |
| ET_PARTNER | = lt_et_partner | |
| . " BBP_CTR_MAP_PD_TO_DB | ||
ABAP code using 7.40 inline data declarations to call FM BBP_CTR_MAP_PD_TO_DB
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