SAP ADDR_CONVERT_COMPLETE_3_TO_1 Function Module for









ADDR_CONVERT_COMPLETE_3_TO_1 is a standard addr convert complete 3 to 1 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 complete 3 to 1 FM, simply by entering the name ADDR_CONVERT_COMPLETE_3_TO_1 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_COMPLETE_3_TO_1 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_COMPLETE_3_TO_1'"
EXPORTING
* ADDRESS_HANDLE = "Address handle (temporary key)
* ADDRESS_NUMBER = "Address Number (Key of Database Table)
* PERSON_HANDLE = "
* PERSON_NUMBER = "

IMPORTING
ADDR1_COMPLETE = "
FIELD_FOR_PERSON_NAME = "

EXCEPTIONS
PARAMETER_ERROR = 1 PERSON_NOT_EXIST = 2 ADDRESS_NOT_EXIST = 3 INTERNAL_ERROR = 4
.



IMPORTING Parameters details for ADDR_CONVERT_COMPLETE_3_TO_1

ADDRESS_HANDLE - Address handle (temporary key)

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

ADDRESS_NUMBER - Address Number (Key of Database Table)

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

PERSON_HANDLE -

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

PERSON_NUMBER -

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

EXPORTING Parameters details for ADDR_CONVERT_COMPLETE_3_TO_1

ADDR1_COMPLETE -

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

FIELD_FOR_PERSON_NAME -

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

EXCEPTIONS details

PARAMETER_ERROR - Incorrect parameter values

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

PERSON_NOT_EXIST -

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

ADDRESS_NOT_EXIST - Address does not exist

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

INTERNAL_ERROR -

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

Copy and paste ABAP code example for ADDR_CONVERT_COMPLETE_3_TO_1 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_addr1_complete  TYPE SZADR_ADDR1_COMPLETE, "   
lv_address_handle  TYPE ADDR3_SEL-ADDRHANDLE, "   
lv_parameter_error  TYPE ADDR3_SEL, "   
lv_address_number  TYPE ADDR3_SEL-ADDRNUMBER, "   
lv_person_not_exist  TYPE ADDR3_SEL, "   
lv_field_for_person_name  TYPE AD_FLDNAM, "   
lv_person_handle  TYPE ADDR3_SEL-PERSHANDLE, "   
lv_address_not_exist  TYPE ADDR3_SEL, "   
lv_person_number  TYPE ADDR3_SEL-PERSNUMBER, "   
lv_internal_error  TYPE ADDR3_SEL. "   

  CALL FUNCTION 'ADDR_CONVERT_COMPLETE_3_TO_1'  "
    EXPORTING
         ADDRESS_HANDLE = lv_address_handle
         ADDRESS_NUMBER = lv_address_number
         PERSON_HANDLE = lv_person_handle
         PERSON_NUMBER = lv_person_number
    IMPORTING
         ADDR1_COMPLETE = lv_addr1_complete
         FIELD_FOR_PERSON_NAME = lv_field_for_person_name
    EXCEPTIONS
        PARAMETER_ERROR = 1
        PERSON_NOT_EXIST = 2
        ADDRESS_NOT_EXIST = 3
        INTERNAL_ERROR = 4
. " ADDR_CONVERT_COMPLETE_3_TO_1




ABAP code using 7.40 inline data declarations to call FM ADDR_CONVERT_COMPLETE_3_TO_1

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 ADDRHANDLE FROM ADDR3_SEL INTO @DATA(ld_address_handle).
 
 
"SELECT single ADDRNUMBER FROM ADDR3_SEL INTO @DATA(ld_address_number).
 
 
 
"SELECT single PERSHANDLE FROM ADDR3_SEL INTO @DATA(ld_person_handle).
 
 
"SELECT single PERSNUMBER FROM ADDR3_SEL INTO @DATA(ld_person_number).
 
 


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!