SAP ADDR_LANGUAGE_MAP_TO_VERSION Function Module for









ADDR_LANGUAGE_MAP_TO_VERSION is a standard addr language map to version 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 language map to version FM, simply by entering the name ADDR_LANGUAGE_MAP_TO_VERSION into the relevant SAP transaction such as SE37 or SE38.

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



Function ADDR_LANGUAGE_MAP_TO_VERSION 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_LANGUAGE_MAP_TO_VERSION'"
EXPORTING
IV_LANGUAGE = "Language Key
IV_APPLICATION_COMPONENT = "

IMPORTING
EV_NATION = "International address version ID

EXCEPTIONS
PARAMETER_ERROR = 1 INTERNAL_ERROR = 2
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLSADR_001

IMPORTING Parameters details for ADDR_LANGUAGE_MAP_TO_VERSION

IV_LANGUAGE - Language Key

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

IV_APPLICATION_COMPONENT -

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

EXPORTING Parameters details for ADDR_LANGUAGE_MAP_TO_VERSION

EV_NATION - International address version ID

Data type: AD_NATION
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: Yes

INTERNAL_ERROR - Serious internal error (MESSAGE A...)

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ADDR_LANGUAGE_MAP_TO_VERSION 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_ev_nation  TYPE AD_NATION, "   
lv_iv_language  TYPE SPRAS, "   
lv_parameter_error  TYPE SPRAS, "   
lv_internal_error  TYPE SPRAS, "   
lv_iv_application_component  TYPE AD_DTEL. "   

  CALL FUNCTION 'ADDR_LANGUAGE_MAP_TO_VERSION'  "
    EXPORTING
         IV_LANGUAGE = lv_iv_language
         IV_APPLICATION_COMPONENT = lv_iv_application_component
    IMPORTING
         EV_NATION = lv_ev_nation
    EXCEPTIONS
        PARAMETER_ERROR = 1
        INTERNAL_ERROR = 2
. " ADDR_LANGUAGE_MAP_TO_VERSION




ABAP code using 7.40 inline data declarations to call FM ADDR_LANGUAGE_MAP_TO_VERSION

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!