SAP BUA_ADDRESS_READ Function Module for

Search SAP Function Modules

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

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

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

 IMPORTING
   E_ADDRESS =  "BP: Addresses with Addr. Data (Read)

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

.

IMPORTING Parameters details for BUA_ADDRESS_READ

I_PARTNER - Partner Number

Data type: BUT000-PARTNER
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_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_D
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_XWA -

Data type: BOOLE_D
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)

I_VALDT_SEL -

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

I_BUFFER_REFRESH -

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

EXPORTING Parameters details for BUA_ADDRESS_READ

E_ADDRESS - BP: Addresses with Addr. Data (Read)

Data type: BUS020_EXT
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)

WRONG_PARAMETERS - Wrong parameter passed

Data type:
Optional: No
Call by Reference: Yes

INTERNAL_ERROR - An internal error has occurred

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_NOT_FOUND -

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

ABAP code using 7.40 inline data declarations to call FM BUA_ADDRESS_READ

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.

Search for further information about these or an SAP related objects