SAP BUPA_ADDRESS_GET_NUMBERS Function Module for









BUPA_ADDRESS_GET_NUMBERS is a standard bupa address get numbers 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 get numbers FM, simply by entering the name BUPA_ADDRESS_GET_NUMBERS 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_GET_NUMBERS 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_GET_NUMBERS'"
  EXPORTING
*  IV_PARTNER =  "Business Partner Number
*  IV_PARTNER_GUID =  "Business Partner GUID
*  IV_ADDRNUMBER =  "Address Number
*  IV_ADDRGUID =  "GUID of a Business Partner Address
*  IV_ADDREXTERNAL =  "Address Number in External System
*  IV_VALDT_OF_STANDARD_ADDR =  "

 IMPORTING
   EV_ADDRNUMBER =  "Address Number
   EV_ADDRGUID =  "GUID of a Business Partner Address
   EV_ADDREXTERNAL =  "Address Number in External System

TABLES
*  ET_RETURN =  "Messages
.



IMPORTING Parameters details for BUPA_ADDRESS_GET_NUMBERS

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)

IV_ADDRNUMBER - Address Number

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

IV_ADDRGUID - GUID of a Business Partner Address

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

IV_ADDREXTERNAL - Address Number in External System

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

IV_VALDT_OF_STANDARD_ADDR -

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

EXPORTING Parameters details for BUPA_ADDRESS_GET_NUMBERS

EV_ADDRNUMBER - Address Number

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

EV_ADDRGUID - GUID of a Business Partner Address

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

EV_ADDREXTERNAL - Address Number in External System

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

TABLES Parameters details for BUPA_ADDRESS_GET_NUMBERS

ET_RETURN - Messages

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

Copy and paste ABAP code example for BUPA_ADDRESS_GET_NUMBERS 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_et_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_iv_partner  TYPE BU_PARTNER, "   
lv_ev_addrnumber  TYPE AD_ADDRNUM, "   
lv_ev_addrguid  TYPE BU_ADDRESS_GUID, "   
lv_iv_partner_guid  TYPE BU_PARTNER_GUID, "   
lv_iv_addrnumber  TYPE AD_ADDRNUM, "   
lv_ev_addrexternal  TYPE BU_ADEXT, "   
lv_iv_addrguid  TYPE BU_ADDRESS_GUID, "   
lv_iv_addrexternal  TYPE BU_ADEXT, "   
lv_iv_valdt_of_standard_addr  TYPE BAPI_BUPA_VALID_DATE. "   

  CALL FUNCTION 'BUPA_ADDRESS_GET_NUMBERS'  "
    EXPORTING
         IV_PARTNER = lv_iv_partner
         IV_PARTNER_GUID = lv_iv_partner_guid
         IV_ADDRNUMBER = lv_iv_addrnumber
         IV_ADDRGUID = lv_iv_addrguid
         IV_ADDREXTERNAL = lv_iv_addrexternal
         IV_VALDT_OF_STANDARD_ADDR = lv_iv_valdt_of_standard_addr
    IMPORTING
         EV_ADDRNUMBER = lv_ev_addrnumber
         EV_ADDRGUID = lv_ev_addrguid
         EV_ADDREXTERNAL = lv_ev_addrexternal
    TABLES
         ET_RETURN = lt_et_return
. " BUPA_ADDRESS_GET_NUMBERS




ABAP code using 7.40 inline data declarations to call FM BUPA_ADDRESS_GET_NUMBERS

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



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!