ADDR_CONVERT_COMPLETE_3_TO_2 SAP Function module

ADDR_CONVERT_COMPLETE_3_TO_2 is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name ADDR_CONVERT_COMPLETE_3_TO_2 into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: SZAE
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM ADDR_CONVERT_COMPLETE_3_TO_2 - ADDR CONVERT COMPLETE 3 TO 2

CALL FUNCTION 'ADDR_CONVERT_COMPLETE_3_TO_2' "
* EXPORTING
*   address_handle =            " addr3_sel-addrhandle  Address handle (temporary key)
*   address_number =            " addr3_sel-addrnumber  Address Number (Key of Database Table)
*   person_handle =             " addr3_sel-pershandle
*   person_number =             " addr3_sel-persnumber
  IMPORTING
    addr2_complete =            " szadr_addr2_complete
  EXCEPTIONS
    PARAMETER_ERROR = 1         "               Incorrect parameter values
    PERSON_NOT_EXIST = 2        "
    ADDRESS_NOT_EXIST = 3       "               Address does not exist
    INTERNAL_ERROR = 4          "
    .  "  ADDR_CONVERT_COMPLETE_3_TO_2

ABAP code example for Function Module ADDR_CONVERT_COMPLETE_3_TO_2

The ABAP code below is a full code listing to execute function module ADDR_CONVERT_COMPLETE_3_TO_2 including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_addr2_complete  
 
 TYPE SZADR_ADDR2_COMPLETE
.



DATA(ld_address_handle) = some text here


DATA(ld_address_number) = some text here


DATA(ld_person_handle) = some text here


DATA(ld_person_number) = some text here
.

CALL FUNCTION 'ADDR_CONVERT_COMPLETE_3_TO_2'
* EXPORTING
*   address_handle =             ld_address_handle
*   address_number =             ld_address_number
*   person_handle =              ld_person_handle
*   person_number =              ld_person_number
  IMPORTING
    addr2_complete =             ld_addr2_complete
  EXCEPTIONS
    PARAMETER_ERROR =            1
    PERSON_NOT_EXIST =           2
    ADDRESS_NOT_EXIST =          3
    INTERNAL_ERROR =             4
    .  "  ADDR_CONVERT_COMPLETE_3_TO_2

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 4. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_addr2_complete
 
 TYPE SZADR_ADDR2_COMPLETE ,
ld_address_handle
 
 TYPE ADDR3_SEL-ADDRHANDLE ,
ld_address_number
 
 TYPE ADDR3_SEL-ADDRNUMBER ,
ld_person_handle
 
 TYPE ADDR3_SEL-PERSHANDLE ,
ld_person_number
 
 TYPE ADDR3_SEL-PERSNUMBER .



ld_address_handle = some text here

ld_address_number = some text here

ld_person_handle = some text here

ld_person_number = some text here