SAP BUPA_CREATE_FROM_DATA_ADDON Function Module for
BUPA_CREATE_FROM_DATA_ADDON is a standard bupa create from data addon 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 create from data addon FM, simply by entering the name BUPA_CREATE_FROM_DATA_ADDON into the relevant SAP transaction such as SE37 or SE38.
Function Group: BUBA_4_ADDON
Program Name: SAPLBUBA_4_ADDON
Main Program: SAPLBUBA_4_ADDON
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BUPA_CREATE_FROM_DATA_ADDON 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_CREATE_FROM_DATA_ADDON'".
EXPORTING
* IV_PARTNER = "Business Partner Number
IV_CATEGORY = "Business Partner Category
* IV_GROUP = "Business Partner Grouping
IS_DATA = "SAP BP: BAPI Structure for Central Data
* IS_DATA_PERSON = "SAP BP: BAPI Structure for Personal Data
* IS_DATA_ORGAN = "SAP BP: BAPI Structure for Organization Data
* IS_DATA_GROUP = "SAP BP: BAPI Structure for Group Data
IV_PARTNER_GUID = "Business Partner GUID
* IV_X_SAVE = 'X' "
IMPORTING
EV_PARTNER = "Business Partner Number
TABLES
* ET_RETURN = "Return Parameters
IMPORTING Parameters details for BUPA_CREATE_FROM_DATA_ADDON
IV_PARTNER - Business Partner Number
Data type: BU_PARTNEROptional: Yes
Call by Reference: No ( called with pass by value option)
IV_CATEGORY - Business Partner Category
Data type: BAPIBUS1006_HEAD-PARTN_CATOptional: No
Call by Reference: No ( called with pass by value option)
IV_GROUP - Business Partner Grouping
Data type: BAPIBUS1006_HEAD-PARTN_GRPOptional: Yes
Call by Reference: No ( called with pass by value option)
IS_DATA - SAP BP: BAPI Structure for Central Data
Data type: BAPIBUS1006_CENTRALOptional: No
Call by Reference: No ( called with pass by value option)
IS_DATA_PERSON - SAP BP: BAPI Structure for Personal Data
Data type: BAPIBUS1006_CENTRAL_PERSONOptional: Yes
Call by Reference: No ( called with pass by value option)
IS_DATA_ORGAN - SAP BP: BAPI Structure for Organization Data
Data type: BAPIBUS1006_CENTRAL_ORGANOptional: Yes
Call by Reference: No ( called with pass by value option)
IS_DATA_GROUP - SAP BP: BAPI Structure for Group Data
Data type: BAPIBUS1006_CENTRAL_GROUPOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_PARTNER_GUID - Business Partner GUID
Data type: BU_PARTNER_GUIDOptional: No
Call by Reference: No ( called with pass by value option)
IV_X_SAVE -
Data type: BAPI4001_1-SAVE_ADDRDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BUPA_CREATE_FROM_DATA_ADDON
EV_PARTNER - Business Partner Number
Data type: BU_PARTNEROptional: No
Call by Reference: Yes
TABLES Parameters details for BUPA_CREATE_FROM_DATA_ADDON
ET_RETURN - Return Parameters
Data type: BAPIRET2Optional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BUPA_CREATE_FROM_DATA_ADDON 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_et_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_ev_partner | TYPE BU_PARTNER, " | |||
| lv_iv_partner | TYPE BU_PARTNER, " | |||
| lv_iv_category | TYPE BAPIBUS1006_HEAD-PARTN_CAT, " | |||
| lv_iv_group | TYPE BAPIBUS1006_HEAD-PARTN_GRP, " | |||
| lv_is_data | TYPE BAPIBUS1006_CENTRAL, " | |||
| lv_is_data_person | TYPE BAPIBUS1006_CENTRAL_PERSON, " | |||
| lv_is_data_organ | TYPE BAPIBUS1006_CENTRAL_ORGAN, " | |||
| lv_is_data_group | TYPE BAPIBUS1006_CENTRAL_GROUP, " | |||
| lv_iv_partner_guid | TYPE BU_PARTNER_GUID, " | |||
| lv_iv_x_save | TYPE BAPI4001_1-SAVE_ADDR. " 'X' |
|   CALL FUNCTION 'BUPA_CREATE_FROM_DATA_ADDON' " |
| EXPORTING | ||
| IV_PARTNER | = lv_iv_partner | |
| IV_CATEGORY | = lv_iv_category | |
| IV_GROUP | = lv_iv_group | |
| IS_DATA | = lv_is_data | |
| IS_DATA_PERSON | = lv_is_data_person | |
| IS_DATA_ORGAN | = lv_is_data_organ | |
| IS_DATA_GROUP | = lv_is_data_group | |
| IV_PARTNER_GUID | = lv_iv_partner_guid | |
| IV_X_SAVE | = lv_iv_x_save | |
| IMPORTING | ||
| EV_PARTNER | = lv_ev_partner | |
| TABLES | ||
| ET_RETURN | = lt_et_return | |
| . " BUPA_CREATE_FROM_DATA_ADDON | ||
ABAP code using 7.40 inline data declarations to call FM BUPA_CREATE_FROM_DATA_ADDON
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_iv_category). | ||||
| "SELECT single PARTN_GRP FROM BAPIBUS1006_HEAD INTO @DATA(ld_iv_group). | ||||
| "SELECT single SAVE_ADDR FROM BAPI4001_1 INTO @DATA(ld_iv_x_save). | ||||
| DATA(ld_iv_x_save) | = 'X'. | |||
Search for further information about these or an SAP related objects