SAP BUA_CHECK_EXT_ADDRNUMBER Function Module for









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

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



Function BUA_CHECK_EXT_ADDRNUMBER 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_CHECK_EXT_ADDRNUMBER'"
EXPORTING
I_PARTNER = "
I_ADEXT = "
* I_VALDT = SY-DATLO "Validity Date

EXCEPTIONS
ADEXT_EXIST = 1
.



IMPORTING Parameters details for BUA_CHECK_EXT_ADDRNUMBER

I_PARTNER -

Data type: BU_PARTNER
Optional: No
Call by Reference: Yes

I_ADEXT -

Data type: BU_ADEXT
Optional: No
Call by Reference: Yes

I_VALDT - Validity Date

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

EXCEPTIONS details

ADEXT_EXIST -

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

Copy and paste ABAP code example for BUA_CHECK_EXT_ADDRNUMBER 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 BU_PARTNER, "   
lv_adext_exist  TYPE BU_PARTNER, "   
lv_i_adext  TYPE BU_ADEXT, "   
lv_i_valdt  TYPE SY-DATLO. "   SY-DATLO

  CALL FUNCTION 'BUA_CHECK_EXT_ADDRNUMBER'  "
    EXPORTING
         I_PARTNER = lv_i_partner
         I_ADEXT = lv_i_adext
         I_VALDT = lv_i_valdt
    EXCEPTIONS
        ADEXT_EXIST = 1
. " BUA_CHECK_EXT_ADDRNUMBER




ABAP code using 7.40 inline data declarations to call FM BUA_CHECK_EXT_ADDRNUMBER

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 DATLO FROM SY INTO @DATA(ld_i_valdt).
DATA(ld_i_valdt) = SY-DATLO.
 


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!