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

Function BUPA_CREATE_FROM_DATA 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'".
EXPORTING
* IV_PARTNER = "Business Partner Number
* IV_TESTRUN = ' ' "Indicator: Test Run
* IV_DUPLICATE_MESSAGE_TYPE = "Message Type Control
* IV_ACCEPT_ERROR = ' ' "Accept Regional Structure Check Errors with Warnings
* IV_X_SAVE = 'X' "Indicator
* IV_CONSIDER_CONSNUMBER_FOR_INS = ' ' "
* IV_CHECK_ADDRESS = 'X' "
* IV_PARTNER_GUID = "
IV_CATEGORY = "Business Partner Category
* IV_GROUP = "Business Partner Grouping
IS_DATA = "Central Data
* IS_DATA_PERSON = "Central Data, Person
* IS_DATA_ORGAN = "Central Data, Organization
* IS_DATA_GROUP = "Central Data, Group
* IS_ADDRESS = "Address
IMPORTING
EV_PARTNER = "Partner Number
EV_PARTNER_GUID = "Business Partner GUID
EV_ADDRNUMBER = "Address Number
EV_ADDRGUID = "GUID of a Business Partner Address
TABLES
* IT_ADTEL = "Telephone Numbers
* IT_ADSSF = "SSF Addresses
* IT_ADURI = "URI Addresses
* IT_ADPAG = "Pager Numbers
* IT_ADREM = "Remarks for Address
* IT_ADCOMREM = "
* IT_ADCOMUSE = "
* IT_ADTEL_ADDR_IND = "BAPI Structure for Telephone Numbers (Bus. Address Services)
* IT_ADFAX_ADDR_IND = "BAPI Structure for Fax Numbers (Business Address Services)
* IT_ADTTX_ADDR_IND = "BAPI Structure for Teletex Numbers (Bus. Address Services)
* IT_ADTLX_ADDR_IND = "BAPI Structure for Telex Numbers (Business Address Services)
* IT_ADFAX = "Telefax Numbers
* IT_ADSMTP_ADDR_IND = "BAPI Structure for E-Mail Addresses (Bus. Address Services)
* IT_ADRML_ADDR_IND = "BAPI Structure for RML Addresses (Business Address Services)
* IT_ADX400_ADDR_IND = "BAPI Structure for X.400 Addresses (Bus. Address Services)
* IT_ADRFC_ADDR_IND = "BAPI Structure for RFC Addresses (Business Address Services)
* IT_ADPRT_ADDR_IND = "BAPI Structure for PRT Addresses (Business Address Services)
* IT_ADSSF_ADDR_IND = "BAPI Structure for SSF Addresses (Business Address Services)
* IT_ADURI_ADDR_IND = "BAPI Structure for URI Addresses (Business Address Services)
* IT_ADPAG_ADDR_IND = "BAPI Structure for Pager Numbers (Business Address Services)
* IT_ADCOMREM_ADDR_IND = "BAPI Structure for Communication Type Comments
* IT_ADCOMUSE_ADDR_IND = "
* IT_ADTTX = "Teletex Numbers
* ET_RETURN = "Messages
* ET_ADDR_DUPLICATES = "Address Duplicates
* IT_ADTLX = "Telex Numbers
* IT_ADSMTP = "
* IT_ADRML = "RML Addresses
* IT_ADX400 = "X.400 Addresses
* IT_ADRFC = "RFC Addresses
* IT_ADPRT = "PRT Addresses
IMPORTING Parameters details for BUPA_CREATE_FROM_DATA
IV_PARTNER - Business Partner Number
Data type: BU_PARTNEROptional: Yes
Call by Reference: No ( called with pass by value option)
IV_TESTRUN - Indicator: Test Run
Data type: BOOLE-BOOLEDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_DUPLICATE_MESSAGE_TYPE - Message Type Control
Data type: BAPIBUS1006_HEAD-CONTROLDUPLICATEMESSAGEOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_ACCEPT_ERROR - Accept Regional Structure Check Errors with Warnings
Data type: BAPI4001_1-ACCEPT_ERRDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_X_SAVE - Indicator
Data type: BAPI4001_1-SAVE_ADDRDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_CONSIDER_CONSNUMBER_FOR_INS -
Data type: SZAD_FIELD-FLAGDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_CHECK_ADDRESS -
Data type: SZAD_FIELD-FLAGDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_PARTNER_GUID -
Data type: BU_PARTNER_GUIDOptional: 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 - Central Data
Data type: BAPIBUS1006_CENTRALOptional: No
Call by Reference: No ( called with pass by value option)
IS_DATA_PERSON - Central Data, Person
Data type: BAPIBUS1006_CENTRAL_PERSONOptional: Yes
Call by Reference: No ( called with pass by value option)
IS_DATA_ORGAN - Central Data, Organization
Data type: BAPIBUS1006_CENTRAL_ORGANOptional: Yes
Call by Reference: No ( called with pass by value option)
IS_DATA_GROUP - Central Data, Group
Data type: BAPIBUS1006_CENTRAL_GROUPOptional: Yes
Call by Reference: No ( called with pass by value option)
IS_ADDRESS - Address
Data type: BAPIBUS1006_ADDRESSOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BUPA_CREATE_FROM_DATA
EV_PARTNER - Partner Number
Data type: BU_PARTNEROptional: No
Call by Reference: No ( called with pass by value option)
EV_PARTNER_GUID - Business Partner GUID
Data type: BU_PARTNER_GUIDOptional: No
Call by Reference: No ( called with pass by value option)
EV_ADDRNUMBER - Address Number
Data type: AD_ADDRNUMOptional: No
Call by Reference: No ( called with pass by value option)
EV_ADDRGUID - GUID of a Business Partner Address
Data type: BU_ADDRESS_GUIDOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BUPA_CREATE_FROM_DATA
IT_ADTEL - Telephone Numbers
Data type: BAPIADTELOptional: Yes
Call by Reference: Yes
IT_ADSSF - SSF Addresses
Data type: BAPIADSSFOptional: Yes
Call by Reference: Yes
IT_ADURI - URI Addresses
Data type: BAPIADURIOptional: Yes
Call by Reference: Yes
IT_ADPAG - Pager Numbers
Data type: BAPIADPAGOptional: Yes
Call by Reference: Yes
IT_ADREM - Remarks for Address
Data type: BAPIAD_REMOptional: Yes
Call by Reference: Yes
IT_ADCOMREM -
Data type: BAPICOMREMOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_ADCOMUSE -
Data type: BAPIADUSEOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_ADTEL_ADDR_IND - BAPI Structure for Telephone Numbers (Bus. Address Services)
Data type: BAPIADTELOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_ADFAX_ADDR_IND - BAPI Structure for Fax Numbers (Business Address Services)
Data type: BAPIADFAXOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_ADTTX_ADDR_IND - BAPI Structure for Teletex Numbers (Bus. Address Services)
Data type: BAPIADTTXOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_ADTLX_ADDR_IND - BAPI Structure for Telex Numbers (Business Address Services)
Data type: BAPIADTLXOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_ADFAX - Telefax Numbers
Data type: BAPIADFAXOptional: Yes
Call by Reference: Yes
IT_ADSMTP_ADDR_IND - BAPI Structure for E-Mail Addresses (Bus. Address Services)
Data type: BAPIADSMTPOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_ADRML_ADDR_IND - BAPI Structure for RML Addresses (Business Address Services)
Data type: BAPIADRMLOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_ADX400_ADDR_IND - BAPI Structure for X.400 Addresses (Bus. Address Services)
Data type: BAPIADX400Optional: Yes
Call by Reference: No ( called with pass by value option)
IT_ADRFC_ADDR_IND - BAPI Structure for RFC Addresses (Business Address Services)
Data type: BAPIADRFCOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_ADPRT_ADDR_IND - BAPI Structure for PRT Addresses (Business Address Services)
Data type: BAPIADPRTOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_ADSSF_ADDR_IND - BAPI Structure for SSF Addresses (Business Address Services)
Data type: BAPIADSSFOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_ADURI_ADDR_IND - BAPI Structure for URI Addresses (Business Address Services)
Data type: BAPIADURIOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_ADPAG_ADDR_IND - BAPI Structure for Pager Numbers (Business Address Services)
Data type: BAPIADPAGOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_ADCOMREM_ADDR_IND - BAPI Structure for Communication Type Comments
Data type: BAPICOMREMOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_ADCOMUSE_ADDR_IND -
Data type: BAPIADUSEOptional: Yes
Call by Reference: Yes
IT_ADTTX - Teletex Numbers
Data type: BAPIADTTXOptional: Yes
Call by Reference: Yes
ET_RETURN - Messages
Data type: BAPIRET2Optional: Yes
Call by Reference: No ( called with pass by value option)
ET_ADDR_DUPLICATES - Address Duplicates
Data type: BAPIBUS1006_ADDRESS_DUPLICATESOptional: Yes
Call by Reference: Yes
IT_ADTLX - Telex Numbers
Data type: BAPIADTLXOptional: Yes
Call by Reference: Yes
IT_ADSMTP -
Data type: BAPIADSMTPOptional: Yes
Call by Reference: Yes
IT_ADRML - RML Addresses
Data type: BAPIADRMLOptional: Yes
Call by Reference: Yes
IT_ADX400 - X.400 Addresses
Data type: BAPIADX400Optional: Yes
Call by Reference: Yes
IT_ADRFC - RFC Addresses
Data type: BAPIADRFCOptional: Yes
Call by Reference: Yes
IT_ADPRT - PRT Addresses
Data type: BAPIADPRTOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BUPA_CREATE_FROM_DATA 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_adtel | TYPE STANDARD TABLE OF BAPIADTEL, " | |||
| lv_ev_partner | TYPE BU_PARTNER, " | |||
| lv_iv_partner | TYPE BU_PARTNER, " | |||
| lt_it_adssf | TYPE STANDARD TABLE OF BAPIADSSF, " | |||
| lv_iv_testrun | TYPE BOOLE-BOOLE, " ' ' | |||
| lt_it_aduri | TYPE STANDARD TABLE OF BAPIADURI, " | |||
| lv_iv_duplicate_message_type | TYPE BAPIBUS1006_HEAD-CONTROLDUPLICATEMESSAGE, " | |||
| lt_it_adpag | TYPE STANDARD TABLE OF BAPIADPAG, " | |||
| lv_iv_accept_error | TYPE BAPI4001_1-ACCEPT_ERR, " SPACE | |||
| lt_it_adrem | TYPE STANDARD TABLE OF BAPIAD_REM, " | |||
| lv_iv_x_save | TYPE BAPI4001_1-SAVE_ADDR, " 'X' | |||
| lt_it_adcomrem | TYPE STANDARD TABLE OF BAPICOMREM, " | |||
| lv_iv_consider_consnumber_for_ins | TYPE SZAD_FIELD-FLAG, " SPACE | |||
| lt_it_adcomuse | TYPE STANDARD TABLE OF BAPIADUSE, " | |||
| lv_iv_check_address | TYPE SZAD_FIELD-FLAG, " 'X' | |||
| lt_it_adtel_addr_ind | TYPE STANDARD TABLE OF BAPIADTEL, " | |||
| lt_it_adfax_addr_ind | TYPE STANDARD TABLE OF BAPIADFAX, " | |||
| lt_it_adttx_addr_ind | TYPE STANDARD TABLE OF BAPIADTTX, " | |||
| lt_it_adtlx_addr_ind | TYPE STANDARD TABLE OF BAPIADTLX, " | |||
| lt_it_adfax | TYPE STANDARD TABLE OF BAPIADFAX, " | |||
| lv_ev_partner_guid | TYPE BU_PARTNER_GUID, " | |||
| lv_iv_partner_guid | TYPE BU_PARTNER_GUID, " | |||
| lt_it_adsmtp_addr_ind | TYPE STANDARD TABLE OF BAPIADSMTP, " | |||
| lt_it_adrml_addr_ind | TYPE STANDARD TABLE OF BAPIADRML, " | |||
| lt_it_adx400_addr_ind | TYPE STANDARD TABLE OF BAPIADX400, " | |||
| lt_it_adrfc_addr_ind | TYPE STANDARD TABLE OF BAPIADRFC, " | |||
| lt_it_adprt_addr_ind | TYPE STANDARD TABLE OF BAPIADPRT, " | |||
| lt_it_adssf_addr_ind | TYPE STANDARD TABLE OF BAPIADSSF, " | |||
| lt_it_aduri_addr_ind | TYPE STANDARD TABLE OF BAPIADURI, " | |||
| lt_it_adpag_addr_ind | TYPE STANDARD TABLE OF BAPIADPAG, " | |||
| lt_it_adcomrem_addr_ind | TYPE STANDARD TABLE OF BAPICOMREM, " | |||
| lt_it_adcomuse_addr_ind | TYPE STANDARD TABLE OF BAPIADUSE, " | |||
| lt_it_adttx | TYPE STANDARD TABLE OF BAPIADTTX, " | |||
| lv_iv_category | TYPE BAPIBUS1006_HEAD-PARTN_CAT, " | |||
| lv_ev_addrnumber | TYPE AD_ADDRNUM, " | |||
| lt_et_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lt_et_addr_duplicates | TYPE STANDARD TABLE OF BAPIBUS1006_ADDRESS_DUPLICATES, " | |||
| lt_it_adtlx | TYPE STANDARD TABLE OF BAPIADTLX, " | |||
| lv_iv_group | TYPE BAPIBUS1006_HEAD-PARTN_GRP, " | |||
| lv_ev_addrguid | TYPE BU_ADDRESS_GUID, " | |||
| lv_is_data | TYPE BAPIBUS1006_CENTRAL, " | |||
| lt_it_adsmtp | TYPE STANDARD TABLE OF BAPIADSMTP, " | |||
| lt_it_adrml | TYPE STANDARD TABLE OF BAPIADRML, " | |||
| lv_is_data_person | TYPE BAPIBUS1006_CENTRAL_PERSON, " | |||
| lt_it_adx400 | TYPE STANDARD TABLE OF BAPIADX400, " | |||
| lv_is_data_organ | TYPE BAPIBUS1006_CENTRAL_ORGAN, " | |||
| lt_it_adrfc | TYPE STANDARD TABLE OF BAPIADRFC, " | |||
| lv_is_data_group | TYPE BAPIBUS1006_CENTRAL_GROUP, " | |||
| lt_it_adprt | TYPE STANDARD TABLE OF BAPIADPRT, " | |||
| lv_is_address | TYPE BAPIBUS1006_ADDRESS. " |
|   CALL FUNCTION 'BUPA_CREATE_FROM_DATA' " |
| EXPORTING | ||
| IV_PARTNER | = lv_iv_partner | |
| IV_TESTRUN | = lv_iv_testrun | |
| IV_DUPLICATE_MESSAGE_TYPE | = lv_iv_duplicate_message_type | |
| IV_ACCEPT_ERROR | = lv_iv_accept_error | |
| IV_X_SAVE | = lv_iv_x_save | |
| IV_CONSIDER_CONSNUMBER_FOR_INS | = lv_iv_consider_consnumber_for_ins | |
| IV_CHECK_ADDRESS | = lv_iv_check_address | |
| IV_PARTNER_GUID | = lv_iv_partner_guid | |
| 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 | |
| IS_ADDRESS | = lv_is_address | |
| IMPORTING | ||
| EV_PARTNER | = lv_ev_partner | |
| EV_PARTNER_GUID | = lv_ev_partner_guid | |
| EV_ADDRNUMBER | = lv_ev_addrnumber | |
| EV_ADDRGUID | = lv_ev_addrguid | |
| TABLES | ||
| IT_ADTEL | = lt_it_adtel | |
| IT_ADSSF | = lt_it_adssf | |
| IT_ADURI | = lt_it_aduri | |
| IT_ADPAG | = lt_it_adpag | |
| IT_ADREM | = lt_it_adrem | |
| IT_ADCOMREM | = lt_it_adcomrem | |
| IT_ADCOMUSE | = lt_it_adcomuse | |
| IT_ADTEL_ADDR_IND | = lt_it_adtel_addr_ind | |
| IT_ADFAX_ADDR_IND | = lt_it_adfax_addr_ind | |
| IT_ADTTX_ADDR_IND | = lt_it_adttx_addr_ind | |
| IT_ADTLX_ADDR_IND | = lt_it_adtlx_addr_ind | |
| IT_ADFAX | = lt_it_adfax | |
| IT_ADSMTP_ADDR_IND | = lt_it_adsmtp_addr_ind | |
| IT_ADRML_ADDR_IND | = lt_it_adrml_addr_ind | |
| IT_ADX400_ADDR_IND | = lt_it_adx400_addr_ind | |
| IT_ADRFC_ADDR_IND | = lt_it_adrfc_addr_ind | |
| IT_ADPRT_ADDR_IND | = lt_it_adprt_addr_ind | |
| IT_ADSSF_ADDR_IND | = lt_it_adssf_addr_ind | |
| IT_ADURI_ADDR_IND | = lt_it_aduri_addr_ind | |
| IT_ADPAG_ADDR_IND | = lt_it_adpag_addr_ind | |
| IT_ADCOMREM_ADDR_IND | = lt_it_adcomrem_addr_ind | |
| IT_ADCOMUSE_ADDR_IND | = lt_it_adcomuse_addr_ind | |
| IT_ADTTX | = lt_it_adttx | |
| ET_RETURN | = lt_et_return | |
| ET_ADDR_DUPLICATES | = lt_et_addr_duplicates | |
| IT_ADTLX | = lt_it_adtlx | |
| IT_ADSMTP | = lt_it_adsmtp | |
| IT_ADRML | = lt_it_adrml | |
| IT_ADX400 | = lt_it_adx400 | |
| IT_ADRFC | = lt_it_adrfc | |
| IT_ADPRT | = lt_it_adprt | |
| . " BUPA_CREATE_FROM_DATA | ||
ABAP code using 7.40 inline data declarations to call FM BUPA_CREATE_FROM_DATA
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_iv_testrun). | ||||
| DATA(ld_iv_testrun) | = ' '. | |||
| "SELECT single CONTROLDUPLICATEMESSAGE FROM BAPIBUS1006_HEAD INTO @DATA(ld_iv_duplicate_message_type). | ||||
| "SELECT single ACCEPT_ERR FROM BAPI4001_1 INTO @DATA(ld_iv_accept_error). | ||||
| DATA(ld_iv_accept_error) | = ' '. | |||
| "SELECT single SAVE_ADDR FROM BAPI4001_1 INTO @DATA(ld_iv_x_save). | ||||
| DATA(ld_iv_x_save) | = 'X'. | |||
| "SELECT single FLAG FROM SZAD_FIELD INTO @DATA(ld_iv_consider_consnumber_for_ins). | ||||
| DATA(ld_iv_consider_consnumber_for_ins) | = ' '. | |||
| "SELECT single FLAG FROM SZAD_FIELD INTO @DATA(ld_iv_check_address). | ||||
| DATA(ld_iv_check_address) | = 'X'. | |||
| "SELECT single PARTN_CAT FROM BAPIBUS1006_HEAD INTO @DATA(ld_iv_category). | ||||
| "SELECT single PARTN_GRP FROM BAPIBUS1006_HEAD INTO @DATA(ld_iv_group). | ||||
Search for further information about these or an SAP related objects