SAP ISU_BUPA_MAP_EXT2OBJDATA Function Module for Mapping Module of External Structure to Object Data BP
ISU_BUPA_MAP_EXT2OBJDATA is a standard isu bupa map ext2objdata SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Mapping Module of External Structure to Object Data BP processing and below is the pattern details for this FM, 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 isu bupa map ext2objdata FM, simply by entering the name ISU_BUPA_MAP_EXT2OBJDATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: ECVI_COM_BUPA
Program Name: SAPLECVI_COM_BUPA
Main Program: SAPLECVI_COM_BUPA
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISU_BUPA_MAP_EXT2OBJDATA 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 'ISU_BUPA_MAP_EXT2OBJDATA'"Mapping Module of External Structure to Object Data BP.
EXPORTING
X_BP_STRUCT = "Com. Interface of a Business Partner
* X_CENTRAL = "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
* X_ADDRESS = "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
* X_TAX = "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
* X_BANK = "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
* X_INDUSTRIES = "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
* X_IDS = "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
* X_ROLES = "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
CHANGING
XY_PARTNER_DATA = "
IMPORTING Parameters details for ISU_BUPA_MAP_EXT2OBJDATA
X_BP_STRUCT - Com. Interface of a Business Partner
Data type: BUS_EI_COM_EXTERNOptional: No
Call by Reference: Yes
X_CENTRAL - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
Data type: BOOLE-BOOLEOptional: Yes
Call by Reference: Yes
X_ADDRESS - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
Data type: BOOLE-BOOLEOptional: Yes
Call by Reference: Yes
X_TAX - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
Data type: BOOLE-BOOLEOptional: Yes
Call by Reference: Yes
X_BANK - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
Data type: BOOLE-BOOLEOptional: Yes
Call by Reference: Yes
X_INDUSTRIES - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
Data type: BOOLE-BOOLEOptional: Yes
Call by Reference: Yes
X_IDS - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
Data type: BOOLE-BOOLEOptional: Yes
Call by Reference: Yes
X_ROLES - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
Data type: BOOLE-BOOLEOptional: Yes
Call by Reference: Yes
CHANGING Parameters details for ISU_BUPA_MAP_EXT2OBJDATA
XY_PARTNER_DATA -
Data type: ISU01_PARTNER_DATAOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISU_BUPA_MAP_EXT2OBJDATA 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_x_bp_struct | TYPE BUS_EI_COM_EXTERN, " | |||
| lv_xy_partner_data | TYPE ISU01_PARTNER_DATA, " | |||
| lv_x_central | TYPE BOOLE-BOOLE, " | |||
| lv_x_address | TYPE BOOLE-BOOLE, " | |||
| lv_x_tax | TYPE BOOLE-BOOLE, " | |||
| lv_x_bank | TYPE BOOLE-BOOLE, " | |||
| lv_x_industries | TYPE BOOLE-BOOLE, " | |||
| lv_x_ids | TYPE BOOLE-BOOLE, " | |||
| lv_x_roles | TYPE BOOLE-BOOLE. " |
|   CALL FUNCTION 'ISU_BUPA_MAP_EXT2OBJDATA' "Mapping Module of External Structure to Object Data BP |
| EXPORTING | ||
| X_BP_STRUCT | = lv_x_bp_struct | |
| X_CENTRAL | = lv_x_central | |
| X_ADDRESS | = lv_x_address | |
| X_TAX | = lv_x_tax | |
| X_BANK | = lv_x_bank | |
| X_INDUSTRIES | = lv_x_industries | |
| X_IDS | = lv_x_ids | |
| X_ROLES | = lv_x_roles | |
| CHANGING | ||
| XY_PARTNER_DATA | = lv_xy_partner_data | |
| . " ISU_BUPA_MAP_EXT2OBJDATA | ||
ABAP code using 7.40 inline data declarations to call FM ISU_BUPA_MAP_EXT2OBJDATA
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.| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_x_central). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_x_address). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_x_tax). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_x_bank). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_x_industries). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_x_ids). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_x_roles). | ||||
Search for further information about these or an SAP related objects