SAP ADDR_CONVERT_TO_BAPIADDR3_V2 Function Module for









ADDR_CONVERT_TO_BAPIADDR3_V2 is a standard addr convert to bapiaddr3 v2 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 addr convert to bapiaddr3 v2 FM, simply by entering the name ADDR_CONVERT_TO_BAPIADDR3_V2 into the relevant SAP transaction such as SE37 or SE38.

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



Function ADDR_CONVERT_TO_BAPIADDR3_V2 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 'ADDR_CONVERT_TO_BAPIADDR3_V2'"
  EXPORTING
   ADDR3_COMPLETE =  "

 IMPORTING
   ADDR3_COMPLETE_BAPI =  "

TABLES
*  T_BAPIADTEL =  "
*  T_BAPIADSSF =  "
*  T_BAPIADURI =  "
*  T_BAPIADPAG =  "
*  T_BAPICOMREM =  "
*  RETURN =  "
*  T_BAPIADFAX =  "
*  T_BAPIADTTX =  "
*  T_BAPIADTLX =  "
*  T_BAPIADSMTP =  "
*  T_BAPIADRML =  "
*  T_BAPIADX400 =  "
*  T_BAPIADRFC =  "
*  T_BAPIADPRT =  "
.



IMPORTING Parameters details for ADDR_CONVERT_TO_BAPIADDR3_V2

ADDR3_COMPLETE -

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

EXPORTING Parameters details for ADDR_CONVERT_TO_BAPIADDR3_V2

ADDR3_COMPLETE_BAPI -

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

TABLES Parameters details for ADDR_CONVERT_TO_BAPIADDR3_V2

T_BAPIADTEL -

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

T_BAPIADSSF -

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

T_BAPIADURI -

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

T_BAPIADPAG -

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

T_BAPICOMREM -

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

RETURN -

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

T_BAPIADFAX -

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

T_BAPIADTTX -

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

T_BAPIADTLX -

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

T_BAPIADSMTP -

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

T_BAPIADRML -

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

T_BAPIADX400 -

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

T_BAPIADRFC -

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

T_BAPIADPRT -

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

Copy and paste ABAP code example for ADDR_CONVERT_TO_BAPIADDR3_V2 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_t_bapiadtel  TYPE STANDARD TABLE OF BAPIADTEL, "   
lv_addr3_complete  TYPE SZADR_ADDR3_COMPLETE, "   
lv_addr3_complete_bapi  TYPE BAPIADDR3, "   
lt_t_bapiadssf  TYPE STANDARD TABLE OF BAPIADSSF, "   
lt_t_bapiaduri  TYPE STANDARD TABLE OF BAPIADURI, "   
lt_t_bapiadpag  TYPE STANDARD TABLE OF BAPIADPAG, "   
lt_t_bapicomrem  TYPE STANDARD TABLE OF BAPICOMREM, "   
lt_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lt_t_bapiadfax  TYPE STANDARD TABLE OF BAPIADFAX, "   
lt_t_bapiadttx  TYPE STANDARD TABLE OF BAPIADTTX, "   
lt_t_bapiadtlx  TYPE STANDARD TABLE OF BAPIADTLX, "   
lt_t_bapiadsmtp  TYPE STANDARD TABLE OF BAPIADSMTP, "   
lt_t_bapiadrml  TYPE STANDARD TABLE OF BAPIADRML, "   
lt_t_bapiadx400  TYPE STANDARD TABLE OF BAPIADX400, "   
lt_t_bapiadrfc  TYPE STANDARD TABLE OF BAPIADRFC, "   
lt_t_bapiadprt  TYPE STANDARD TABLE OF BAPIADPRT. "   

  CALL FUNCTION 'ADDR_CONVERT_TO_BAPIADDR3_V2'  "
    EXPORTING
         ADDR3_COMPLETE = lv_addr3_complete
    IMPORTING
         ADDR3_COMPLETE_BAPI = lv_addr3_complete_bapi
    TABLES
         T_BAPIADTEL = lt_t_bapiadtel
         T_BAPIADSSF = lt_t_bapiadssf
         T_BAPIADURI = lt_t_bapiaduri
         T_BAPIADPAG = lt_t_bapiadpag
         T_BAPICOMREM = lt_t_bapicomrem
         RETURN = lt_return
         T_BAPIADFAX = lt_t_bapiadfax
         T_BAPIADTTX = lt_t_bapiadttx
         T_BAPIADTLX = lt_t_bapiadtlx
         T_BAPIADSMTP = lt_t_bapiadsmtp
         T_BAPIADRML = lt_t_bapiadrml
         T_BAPIADX400 = lt_t_bapiadx400
         T_BAPIADRFC = lt_t_bapiadrfc
         T_BAPIADPRT = lt_t_bapiadprt
. " ADDR_CONVERT_TO_BAPIADDR3_V2




ABAP code using 7.40 inline data declarations to call FM ADDR_CONVERT_TO_BAPIADDR3_V2

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!