SAP BUA_ADDRESS_GET Function Module for









BUA_ADDRESS_GET is a standard bua address get 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 bua address get FM, simply by entering the name BUA_ADDRESS_GET into the relevant SAP transaction such as SE37 or SE38.

Function Group: BUA1
Program Name: SAPLBUA1
Main Program: SAPLBUA1
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function BUA_ADDRESS_GET 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 'BUA_ADDRESS_GET'"
EXPORTING
* I_PARTNER = "Partner Number
* I_VALDT_SEL = SY-DATLO "
* IV_REQ_BLK_MSG = ' ' "
* I_PARTNERGUID = "
* I_OPERATION = "
* I_ADRKIND = "Address Type
* I_ADDRNUMBER = "Address Number
* I_ADDRGUID = "Address GUID
* I_XMEMORY = ' ' "
* I_XWA = ' ' "
* I_VALDT = '00000000' "Validity Date

IMPORTING
E_ADDRNUMBER = "Address Number
E_ADDRGUID = "Address GUID
E_ADDRESS = "Address Data
E_ADDRUSE = "Address Usage
E_ADDRUSE_FS = "Address Usage
E_ADDRTYPE = "
E_STNDADDR_INSTEAD = "

EXCEPTIONS
NO_ADDRESS_FOUND = 1 INTERNAL_ERROR = 2 WRONG_PARAMETERS = 3 DATE_INVALID = 4 NOT_VALID = 5 PARTNER_BLOCKED = 6
.



IMPORTING Parameters details for BUA_ADDRESS_GET

I_PARTNER - Partner Number

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

I_VALDT_SEL -

Data type: SY-DATLO
Default: SY-DATLO
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_REQ_BLK_MSG -

Data type: BOOLE-BOOLE
Default: SPACE
Optional: No
Call by Reference: Yes

I_PARTNERGUID -

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

I_OPERATION -

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

I_ADRKIND - Address Type

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

I_ADDRNUMBER - Address Number

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

I_ADDRGUID - Address GUID

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

I_XMEMORY -

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

I_XWA -

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

I_VALDT - Validity Date

Data type: SY-DATLO
Default: '00000000'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for BUA_ADDRESS_GET

E_ADDRNUMBER - Address Number

Data type: BUT020-ADDRNUMBER
Optional: No
Call by Reference: No ( called with pass by value option)

E_ADDRGUID - Address GUID

Data type: BUT020-ADDRESS_GUID
Optional: No
Call by Reference: No ( called with pass by value option)

E_ADDRESS - Address Data

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

E_ADDRUSE - Address Usage

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

E_ADDRUSE_FS - Address Usage

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

E_ADDRTYPE -

Data type: BUS000FLDS-CHAR1
Optional: No
Call by Reference: No ( called with pass by value option)

E_STNDADDR_INSTEAD -

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

EXCEPTIONS details

NO_ADDRESS_FOUND -

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

INTERNAL_ERROR - An internal error has occurred

Data type:
Optional: No
Call by Reference: Yes

WRONG_PARAMETERS - Wrong parameter passed

Data type:
Optional: No
Call by Reference: Yes

DATE_INVALID - Invalid Date

Data type:
Optional: No
Call by Reference: Yes

NOT_VALID -

Data type:
Optional: No
Call by Reference: Yes

PARTNER_BLOCKED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BUA_ADDRESS_GET 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_i_partner  TYPE BUT000-PARTNER, "   
lv_e_addrnumber  TYPE BUT020-ADDRNUMBER, "   
lv_no_address_found  TYPE BUT020, "   
lv_i_valdt_sel  TYPE SY-DATLO, "   SY-DATLO
lv_iv_req_blk_msg  TYPE BOOLE-BOOLE, "   SPACE
lv_e_addrguid  TYPE BUT020-ADDRESS_GUID, "   
lv_i_partnerguid  TYPE BUT000-PARTNER_GUID, "   
lv_internal_error  TYPE BUT000, "   
lv_e_address  TYPE BUS020_EXT, "   
lv_i_operation  TYPE TB008S-OPERATION, "   
lv_wrong_parameters  TYPE TB008S, "   
lv_e_addruse  TYPE BUT021, "   
lv_i_adrkind  TYPE BUT021-ADR_KIND, "   
lv_date_invalid  TYPE BUT021, "   
lv_not_valid  TYPE BUT021, "   
lv_e_addruse_fs  TYPE BUT021_FS, "   
lv_i_addrnumber  TYPE BUT020-ADDRNUMBER, "   
lv_e_addrtype  TYPE BUS000FLDS-CHAR1, "   
lv_i_addrguid  TYPE BUT020-ADDRESS_GUID, "   
lv_partner_blocked  TYPE BUT020, "   
lv_i_xmemory  TYPE BOOLE-BOOLE, "   SPACE
lv_e_stndaddr_instead  TYPE BOOLE-BOOLE, "   
lv_i_xwa  TYPE BOOLE-BOOLE, "   SPACE
lv_i_valdt  TYPE SY-DATLO. "   '00000000'

  CALL FUNCTION 'BUA_ADDRESS_GET'  "
    EXPORTING
         I_PARTNER = lv_i_partner
         I_VALDT_SEL = lv_i_valdt_sel
         IV_REQ_BLK_MSG = lv_iv_req_blk_msg
         I_PARTNERGUID = lv_i_partnerguid
         I_OPERATION = lv_i_operation
         I_ADRKIND = lv_i_adrkind
         I_ADDRNUMBER = lv_i_addrnumber
         I_ADDRGUID = lv_i_addrguid
         I_XMEMORY = lv_i_xmemory
         I_XWA = lv_i_xwa
         I_VALDT = lv_i_valdt
    IMPORTING
         E_ADDRNUMBER = lv_e_addrnumber
         E_ADDRGUID = lv_e_addrguid
         E_ADDRESS = lv_e_address
         E_ADDRUSE = lv_e_addruse
         E_ADDRUSE_FS = lv_e_addruse_fs
         E_ADDRTYPE = lv_e_addrtype
         E_STNDADDR_INSTEAD = lv_e_stndaddr_instead
    EXCEPTIONS
        NO_ADDRESS_FOUND = 1
        INTERNAL_ERROR = 2
        WRONG_PARAMETERS = 3
        DATE_INVALID = 4
        NOT_VALID = 5
        PARTNER_BLOCKED = 6
. " BUA_ADDRESS_GET




ABAP code using 7.40 inline data declarations to call FM BUA_ADDRESS_GET

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 PARTNER FROM BUT000 INTO @DATA(ld_i_partner).
 
"SELECT single ADDRNUMBER FROM BUT020 INTO @DATA(ld_e_addrnumber).
 
 
"SELECT single DATLO FROM SY INTO @DATA(ld_i_valdt_sel).
DATA(ld_i_valdt_sel) = SY-DATLO.
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_iv_req_blk_msg).
DATA(ld_iv_req_blk_msg) = ' '.
 
"SELECT single ADDRESS_GUID FROM BUT020 INTO @DATA(ld_e_addrguid).
 
"SELECT single PARTNER_GUID FROM BUT000 INTO @DATA(ld_i_partnerguid).
 
 
 
"SELECT single OPERATION FROM TB008S INTO @DATA(ld_i_operation).
 
 
 
"SELECT single ADR_KIND FROM BUT021 INTO @DATA(ld_i_adrkind).
 
 
 
 
"SELECT single ADDRNUMBER FROM BUT020 INTO @DATA(ld_i_addrnumber).
 
"SELECT single CHAR1 FROM BUS000FLDS INTO @DATA(ld_e_addrtype).
 
"SELECT single ADDRESS_GUID FROM BUT020 INTO @DATA(ld_i_addrguid).
 
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_xmemory).
DATA(ld_i_xmemory) = ' '.
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_e_stndaddr_instead).
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_xwa).
DATA(ld_i_xwa) = ' '.
 
"SELECT single DATLO FROM SY INTO @DATA(ld_i_valdt).
DATA(ld_i_valdt) = '00000000'.
 


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!