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

Function BBP_CON_MAP_PD 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_CON_MAP_PD'".
IMPORTING
E_HEADER = "
TABLES
* E_ITEM = "
* E_PARTNER = "
* E_ORGDATA = "
* E_LONGTEXT = "
* E_STATUS = "
* E_ACTVAL = "
* E_MESSAGES = "
EXPORTING Parameters details for BBP_CON_MAP_PD
E_HEADER -
Data type: BBP_PDS_HEADEROptional: No
Call by Reference: Yes
TABLES Parameters details for BBP_CON_MAP_PD
E_ITEM -
Data type: BBP_PDS_ITEMOptional: Yes
Call by Reference: Yes
E_PARTNER -
Data type: BBP_PDS_PARTNEROptional: Yes
Call by Reference: Yes
E_ORGDATA -
Data type: BBP_PDS_ORGOptional: Yes
Call by Reference: Yes
E_LONGTEXT -
Data type: BBP_PDS_LONGTEXTOptional: Yes
Call by Reference: Yes
E_STATUS -
Data type: BBP_PDS_STATUSOptional: Yes
Call by Reference: Yes
E_ACTVAL -
Data type: BBP_PDS_ACTVALOptional: Yes
Call by Reference: Yes
E_MESSAGES -
Data type: BBP_PDS_MESSAGESOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BBP_CON_MAP_PD 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_e_item | TYPE STANDARD TABLE OF BBP_PDS_ITEM, " | |||
| lv_e_header | TYPE BBP_PDS_HEADER, " | |||
| lt_e_partner | TYPE STANDARD TABLE OF BBP_PDS_PARTNER, " | |||
| lt_e_orgdata | TYPE STANDARD TABLE OF BBP_PDS_ORG, " | |||
| lt_e_longtext | TYPE STANDARD TABLE OF BBP_PDS_LONGTEXT, " | |||
| lt_e_status | TYPE STANDARD TABLE OF BBP_PDS_STATUS, " | |||
| lt_e_actval | TYPE STANDARD TABLE OF BBP_PDS_ACTVAL, " | |||
| lt_e_messages | TYPE STANDARD TABLE OF BBP_PDS_MESSAGES. " |
|   CALL FUNCTION 'BBP_CON_MAP_PD' " |
| IMPORTING | ||
| E_HEADER | = lv_e_header | |
| TABLES | ||
| E_ITEM | = lt_e_item | |
| E_PARTNER | = lt_e_partner | |
| E_ORGDATA | = lt_e_orgdata | |
| E_LONGTEXT | = lt_e_longtext | |
| E_STATUS | = lt_e_status | |
| E_ACTVAL | = lt_e_actval | |
| E_MESSAGES | = lt_e_messages | |
| . " BBP_CON_MAP_PD | ||
ABAP code using 7.40 inline data declarations to call FM BBP_CON_MAP_PD
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