SAP BUPA_ADDRESS_ADD Function Module for









BUPA_ADDRESS_ADD is a standard bupa address add 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 address add FM, simply by entering the name BUPA_ADDRESS_ADD 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_ADDRESS_ADD 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_ADDRESS_ADD'"
  EXPORTING
*  IV_PARTNER =  "Business Partner Number
*  IV_PARTNER_GUID =  "Business Partner GUID
   IS_ADDRESS =  "Address Data
*  IV_DUPLICATE_MESSAGE_TYPE =  "Message Type Control
*  IV_ACCEPT_ERROR = ' ' "Accept Regional Structure Check Errors with Warnings
*  IV_ADDRGUID =  "For internal use only
*  IV_X_SAVE = 'X' "Indicator
*  IV_CONSIDER_CONSNUMBER_FOR_INS = ' ' "
*  IV_CHECK_ADDRESS = 'X' "

 IMPORTING
   EV_ADDRNUMBER =  "Address Number
   EV_ADDRGUID =  "Address GUID

TABLES
*  IT_ADTEL =  "Telephone Numbers
*  IT_ADSSF =  "SSF Addresses
*  IT_ADURI =  "URI Addresses
*  IT_ADPAG =  "Pager Numbers
*  IT_ADREM =  "Remarks for Address
*  IT_ADCOMREM =  "Remarks for Communication Types
*  IT_ADUSE =  "Address Usages
*  IT_ADDR_COMM_USE =  "
*  ET_ADDR_DUPLICATES =  "
*  ET_RETURN =  "Messages
*  IT_ADFAX =  "Telefax Numbers
*  IT_ADTTX =  "Teletex Numbers
*  IT_ADTLX =  "Telex Numbers
*  IT_ADSMTP =  "E-Mail Addresses
*  IT_ADRML =  "RML Addresses
*  IT_ADX400 =  "X400 Addresses
*  IT_ADRFC =  "RFC Addresses
*  IT_ADPRT =  "PRT Addresses
.



IMPORTING Parameters details for BUPA_ADDRESS_ADD

IV_PARTNER - Business Partner Number

Data type: BU_PARTNER
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_PARTNER_GUID - Business Partner GUID

Data type: BU_PARTNER_GUID
Optional: Yes
Call by Reference: No ( called with pass by value option)

IS_ADDRESS - Address Data

Data type: BAPIBUS1006_ADDRESS
Optional: No
Call by Reference: No ( called with pass by value option)

IV_DUPLICATE_MESSAGE_TYPE - Message Type Control

Data type: BAPIBUS1006_HEAD-CONTROLDUPLICATEMESSAGE
Optional: 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_ERR
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_ADDRGUID - For internal use only

Data type: BU_ADDRESS_GUID
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_X_SAVE - Indicator

Data type: BAPI4001_1-SAVE_ADDR
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_CONSIDER_CONSNUMBER_FOR_INS -

Data type: SZAD_FIELD-FLAG
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_CHECK_ADDRESS -

Data type: SZAD_FIELD-FLAG
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for BUPA_ADDRESS_ADD

EV_ADDRNUMBER - Address Number

Data type: AD_ADDRNUM
Optional: No
Call by Reference: No ( called with pass by value option)

EV_ADDRGUID - Address GUID

Data type: BU_ADDRESS_GUID
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for BUPA_ADDRESS_ADD

IT_ADTEL - Telephone Numbers

Data type: BAPIADTEL
Optional: Yes
Call by Reference: Yes

IT_ADSSF - SSF Addresses

Data type: BAPIADSSF
Optional: Yes
Call by Reference: Yes

IT_ADURI - URI Addresses

Data type: BAPIADURI
Optional: Yes
Call by Reference: Yes

IT_ADPAG - Pager Numbers

Data type: BAPIADPAG
Optional: Yes
Call by Reference: Yes

IT_ADREM - Remarks for Address

Data type: BAPIAD_REM
Optional: Yes
Call by Reference: Yes

IT_ADCOMREM - Remarks for Communication Types

Data type: BAPICOMREM
Optional: Yes
Call by Reference: Yes

IT_ADUSE - Address Usages

Data type: BAPIBUS1006_ADDRESSUSAGE
Optional: Yes
Call by Reference: Yes

IT_ADDR_COMM_USE -

Data type: BAPIADUSE
Optional: Yes
Call by Reference: Yes

ET_ADDR_DUPLICATES -

Data type: BAPIBUS1006_ADDRESS_DUPLICATES
Optional: Yes
Call by Reference: Yes

ET_RETURN - Messages

Data type: BAPIRET2
Optional: Yes
Call by Reference: Yes

IT_ADFAX - Telefax Numbers

Data type: BAPIADFAX
Optional: Yes
Call by Reference: Yes

IT_ADTTX - Teletex Numbers

Data type: BAPIADTTX
Optional: Yes
Call by Reference: Yes

IT_ADTLX - Telex Numbers

Data type: BAPIADTLX
Optional: Yes
Call by Reference: Yes

IT_ADSMTP - E-Mail Addresses

Data type: BAPIADSMTP
Optional: Yes
Call by Reference: Yes

IT_ADRML - RML Addresses

Data type: BAPIADRML
Optional: Yes
Call by Reference: Yes

IT_ADX400 - X400 Addresses

Data type: BAPIADX400
Optional: Yes
Call by Reference: Yes

IT_ADRFC - RFC Addresses

Data type: BAPIADRFC
Optional: Yes
Call by Reference: Yes

IT_ADPRT - PRT Addresses

Data type: BAPIADPRT
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for BUPA_ADDRESS_ADD 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_iv_partner  TYPE BU_PARTNER, "   
lv_ev_addrnumber  TYPE AD_ADDRNUM, "   
lt_it_adssf  TYPE STANDARD TABLE OF BAPIADSSF, "   
lt_it_aduri  TYPE STANDARD TABLE OF BAPIADURI, "   
lt_it_adpag  TYPE STANDARD TABLE OF BAPIADPAG, "   
lt_it_adrem  TYPE STANDARD TABLE OF BAPIAD_REM, "   
lt_it_adcomrem  TYPE STANDARD TABLE OF BAPICOMREM, "   
lt_it_aduse  TYPE STANDARD TABLE OF BAPIBUS1006_ADDRESSUSAGE, "   
lt_it_addr_comm_use  TYPE STANDARD TABLE OF BAPIADUSE, "   
lt_et_addr_duplicates  TYPE STANDARD TABLE OF BAPIBUS1006_ADDRESS_DUPLICATES, "   
lt_et_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lt_it_adfax  TYPE STANDARD TABLE OF BAPIADFAX, "   
lv_ev_addrguid  TYPE BU_ADDRESS_GUID, "   
lv_iv_partner_guid  TYPE BU_PARTNER_GUID, "   
lt_it_adttx  TYPE STANDARD TABLE OF BAPIADTTX, "   
lv_is_address  TYPE BAPIBUS1006_ADDRESS, "   
lt_it_adtlx  TYPE STANDARD TABLE OF BAPIADTLX, "   
lv_iv_duplicate_message_type  TYPE BAPIBUS1006_HEAD-CONTROLDUPLICATEMESSAGE, "   
lt_it_adsmtp  TYPE STANDARD TABLE OF BAPIADSMTP, "   
lv_iv_accept_error  TYPE BAPI4001_1-ACCEPT_ERR, "   SPACE
lt_it_adrml  TYPE STANDARD TABLE OF BAPIADRML, "   
lv_iv_addrguid  TYPE BU_ADDRESS_GUID, "   
lt_it_adx400  TYPE STANDARD TABLE OF BAPIADX400, "   
lv_iv_x_save  TYPE BAPI4001_1-SAVE_ADDR, "   'X'
lt_it_adrfc  TYPE STANDARD TABLE OF BAPIADRFC, "   
lv_iv_consider_consnumber_for_ins  TYPE SZAD_FIELD-FLAG, "   SPACE
lt_it_adprt  TYPE STANDARD TABLE OF BAPIADPRT, "   
lv_iv_check_address  TYPE SZAD_FIELD-FLAG. "   'X'

  CALL FUNCTION 'BUPA_ADDRESS_ADD'  "
    EXPORTING
         IV_PARTNER = lv_iv_partner
         IV_PARTNER_GUID = lv_iv_partner_guid
         IS_ADDRESS = lv_is_address
         IV_DUPLICATE_MESSAGE_TYPE = lv_iv_duplicate_message_type
         IV_ACCEPT_ERROR = lv_iv_accept_error
         IV_ADDRGUID = lv_iv_addrguid
         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
    IMPORTING
         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_ADUSE = lt_it_aduse
         IT_ADDR_COMM_USE = lt_it_addr_comm_use
         ET_ADDR_DUPLICATES = lt_et_addr_duplicates
         ET_RETURN = lt_et_return
         IT_ADFAX = lt_it_adfax
         IT_ADTTX = lt_it_adttx
         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_ADDRESS_ADD




ABAP code using 7.40 inline data declarations to call FM BUPA_ADDRESS_ADD

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 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'.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!