SAP SX_ADDRESS_TRANSLATE Function Module for









SX_ADDRESS_TRANSLATE is a standard sx address translate 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 sx address translate FM, simply by entering the name SX_ADDRESS_TRANSLATE into the relevant SAP transaction such as SE37 or SE38.

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



Function SX_ADDRESS_TRANSLATE 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 'SX_ADDRESS_TRANSLATE'"
  EXPORTING
   ADDRESS_IN =  "
   TO_STRING =  "
*  SIMPLE_FAX =  "
*  EXPLAIN =  "
*  APPLOG =  "

 IMPORTING
   ADDRESS_OUT =  "

EXCEPTIONS
   ERR_WRONG_FORMAT = 1    ERR_ADDRESS_NOT_SPECIFIED = 2    ERR_ADDRESS_TYPE = 3    ERR_ADDRESS_TOO_LONG = 4    ERR_FAX_COUNTRY_INVALID = 5    ERR_FAX_NUMBER_INVALID = 6    ERR_X400_INCOMPLETE = 7
.



IMPORTING Parameters details for SX_ADDRESS_TRANSLATE

ADDRESS_IN -

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

TO_STRING -

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

SIMPLE_FAX -

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

EXPLAIN -

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

APPLOG -

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

EXPORTING Parameters details for SX_ADDRESS_TRANSLATE

ADDRESS_OUT -

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

EXCEPTIONS details

ERR_WRONG_FORMAT -

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

ERR_ADDRESS_NOT_SPECIFIED -

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

ERR_ADDRESS_TYPE -

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

ERR_ADDRESS_TOO_LONG -

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

ERR_FAX_COUNTRY_INVALID -

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

ERR_FAX_NUMBER_INVALID -

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

ERR_X400_INCOMPLETE -

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

Copy and paste ABAP code example for SX_ADDRESS_TRANSLATE 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_address_in  TYPE SX_ADDRESS, "   
lv_address_out  TYPE SX_ADDRESS, "   
lv_err_wrong_format  TYPE SX_ADDRESS, "   
lv_to_string  TYPE SX_BOOLEAN, "   
lv_err_address_not_specified  TYPE SX_BOOLEAN, "   
lv_simple_fax  TYPE SX_BOOLEAN, "   
lv_err_address_type  TYPE SX_BOOLEAN, "   
lv_explain  TYPE SX_BOOLEAN, "   
lv_err_address_too_long  TYPE SX_BOOLEAN, "   
lv_applog  TYPE BALLOGHNDL, "   
lv_err_fax_country_invalid  TYPE BALLOGHNDL, "   
lv_err_fax_number_invalid  TYPE BALLOGHNDL, "   
lv_err_x400_incomplete  TYPE BALLOGHNDL. "   

  CALL FUNCTION 'SX_ADDRESS_TRANSLATE'  "
    EXPORTING
         ADDRESS_IN = lv_address_in
         TO_STRING = lv_to_string
         SIMPLE_FAX = lv_simple_fax
         EXPLAIN = lv_explain
         APPLOG = lv_applog
    IMPORTING
         ADDRESS_OUT = lv_address_out
    EXCEPTIONS
        ERR_WRONG_FORMAT = 1
        ERR_ADDRESS_NOT_SPECIFIED = 2
        ERR_ADDRESS_TYPE = 3
        ERR_ADDRESS_TOO_LONG = 4
        ERR_FAX_COUNTRY_INVALID = 5
        ERR_FAX_NUMBER_INVALID = 6
        ERR_X400_INCOMPLETE = 7
. " SX_ADDRESS_TRANSLATE




ABAP code using 7.40 inline data declarations to call FM SX_ADDRESS_TRANSLATE

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!