SAP REBP_API_MULTI_ADDR_GET Function Module for
REBP_API_MULTI_ADDR_GET is a standard rebp api multi addr 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 rebp api multi addr get FM, simply by entering the name REBP_API_MULTI_ADDR_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: REBP_BAPI_MULTI_ADDR
Program Name: SAPLREBP_BAPI_MULTI_ADDR
Main Program: SAPLREBP_BAPI_MULTI_ADDR
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function REBP_API_MULTI_ADDR_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 'REBP_API_MULTI_ADDR_GET'".
EXPORTING
IO_HAS_MULTI_ADDRESS = "
IMPORTING
ET_MULTI_ADDR = "
IMPORTING Parameters details for REBP_API_MULTI_ADDR_GET
IO_HAS_MULTI_ADDRESS -
Data type: IF_REBP_HAS_MULTI_ADDRESSOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for REBP_API_MULTI_ADDR_GET
ET_MULTI_ADDR -
Data type: BAPI_RE_T_MULTI_ADDR_INTOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for REBP_API_MULTI_ADDR_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_et_multi_addr | TYPE BAPI_RE_T_MULTI_ADDR_INT, " | |||
| lv_io_has_multi_address | TYPE IF_REBP_HAS_MULTI_ADDRESS. " |
|   CALL FUNCTION 'REBP_API_MULTI_ADDR_GET' " |
| EXPORTING | ||
| IO_HAS_MULTI_ADDRESS | = lv_io_has_multi_address | |
| IMPORTING | ||
| ET_MULTI_ADDR | = lv_et_multi_addr | |
| . " REBP_API_MULTI_ADDR_GET | ||
ABAP code using 7.40 inline data declarations to call FM REBP_API_MULTI_ADDR_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.Search for further information about these or an SAP related objects