SAP BUPA_BUT000_MAP_TO_EXTERNAL Function Module for
BUPA_BUT000_MAP_TO_EXTERNAL is a standard bupa but000 map to external 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 bupa but000 map to external FM, simply by entering the name BUPA_BUT000_MAP_TO_EXTERNAL into the relevant SAP transaction such as SE37 or SE38.
Function Group: BUPA_READ
Program Name: SAPLBUPA_READ
Main Program: SAPLBUPA_READ
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function BUPA_BUT000_MAP_TO_EXTERNAL 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 'BUPA_BUT000_MAP_TO_EXTERNAL'".
EXPORTING
IS_BUT000 = "BP: General data I
IMPORTING
ES_DATA = "SAP BP: BAPI Structure for Central Data
ES_DATA_PERSON = "SAP BP: BAPI Structure for Personal Data
ES_DATA_ORGAN = "SAP BP: BAPI Structure for Organization Data
ES_DATA_GROUP = "SAP BP: BAPI Structure for Group Data
ES_DATA_INFO = "SAP BP: BAPI Structure for Central Data
ES_CENTRAL_VALIDITY = "
EV_CATEGORY = "Business Partner Category
EV_GROUP = "Business Partner Grouping
EXCEPTIONS
UNKNOWN_LANGUAGE = 1 UNKNOWN_COUNTRY = 2
IMPORTING Parameters details for BUPA_BUT000_MAP_TO_EXTERNAL
IS_BUT000 - BP: General data I
Data type: BUT000Optional: No
Call by Reference: Yes
EXPORTING Parameters details for BUPA_BUT000_MAP_TO_EXTERNAL
ES_DATA - SAP BP: BAPI Structure for Central Data
Data type: BAPIBUS1006_CENTRALOptional: No
Call by Reference: Yes
ES_DATA_PERSON - SAP BP: BAPI Structure for Personal Data
Data type: BAPIBUS1006_CENTRAL_PERSONOptional: No
Call by Reference: Yes
ES_DATA_ORGAN - SAP BP: BAPI Structure for Organization Data
Data type: BAPIBUS1006_CENTRAL_ORGANOptional: No
Call by Reference: Yes
ES_DATA_GROUP - SAP BP: BAPI Structure for Group Data
Data type: BAPIBUS1006_CENTRAL_GROUPOptional: No
Call by Reference: Yes
ES_DATA_INFO - SAP BP: BAPI Structure for Central Data
Data type: BAPIBUS1006_CENTRAL_INFOOptional: No
Call by Reference: Yes
ES_CENTRAL_VALIDITY -
Data type: BAPIBUS1006_CENTRAL_VALIDITYOptional: No
Call by Reference: Yes
EV_CATEGORY - Business Partner Category
Data type: BAPIBUS1006_HEAD-PARTN_CATOptional: No
Call by Reference: Yes
EV_GROUP - Business Partner Grouping
Data type: BAPIBUS1006_HEAD-PARTN_GRPOptional: No
Call by Reference: Yes
EXCEPTIONS details
UNKNOWN_LANGUAGE -
Data type:Optional: No
Call by Reference: Yes
UNKNOWN_COUNTRY -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for BUPA_BUT000_MAP_TO_EXTERNAL 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_es_data | TYPE BAPIBUS1006_CENTRAL, " | |||
lv_is_but000 | TYPE BUT000, " | |||
lv_unknown_language | TYPE BUT000, " | |||
lv_es_data_person | TYPE BAPIBUS1006_CENTRAL_PERSON, " | |||
lv_unknown_country | TYPE BAPIBUS1006_CENTRAL_PERSON, " | |||
lv_es_data_organ | TYPE BAPIBUS1006_CENTRAL_ORGAN, " | |||
lv_es_data_group | TYPE BAPIBUS1006_CENTRAL_GROUP, " | |||
lv_es_data_info | TYPE BAPIBUS1006_CENTRAL_INFO, " | |||
lv_es_central_validity | TYPE BAPIBUS1006_CENTRAL_VALIDITY, " | |||
lv_ev_category | TYPE BAPIBUS1006_HEAD-PARTN_CAT, " | |||
lv_ev_group | TYPE BAPIBUS1006_HEAD-PARTN_GRP. " |
  CALL FUNCTION 'BUPA_BUT000_MAP_TO_EXTERNAL' " |
EXPORTING | ||
IS_BUT000 | = lv_is_but000 | |
IMPORTING | ||
ES_DATA | = lv_es_data | |
ES_DATA_PERSON | = lv_es_data_person | |
ES_DATA_ORGAN | = lv_es_data_organ | |
ES_DATA_GROUP | = lv_es_data_group | |
ES_DATA_INFO | = lv_es_data_info | |
ES_CENTRAL_VALIDITY | = lv_es_central_validity | |
EV_CATEGORY | = lv_ev_category | |
EV_GROUP | = lv_ev_group | |
EXCEPTIONS | ||
UNKNOWN_LANGUAGE = 1 | ||
UNKNOWN_COUNTRY = 2 | ||
. " BUPA_BUT000_MAP_TO_EXTERNAL |
ABAP code using 7.40 inline data declarations to call FM BUPA_BUT000_MAP_TO_EXTERNAL
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 PARTN_CAT FROM BAPIBUS1006_HEAD INTO @DATA(ld_ev_category). | ||||
"SELECT single PARTN_GRP FROM BAPIBUS1006_HEAD INTO @DATA(ld_ev_group). | ||||
Search for further information about these or an SAP related objects