SAP EAN_GLN_MAPPING Function Module for Re-coding of object on GLN
EAN_GLN_MAPPING is a standard ean gln mapping SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Re-coding of object on GLN processing and below is the pattern details for this FM, 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 ean gln mapping FM, simply by entering the name EAN_GLN_MAPPING into the relevant SAP transaction such as SE37 or SE38.
Function Group: EAN_GLN_FUNCS
Program Name: SAPLEAN_GLN_FUNCS
Main Program: SAPLEAN_GLN_FUNCS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EAN_GLN_MAPPING 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 'EAN_GLN_MAPPING'"Re-coding of object on GLN.
IMPORTING
E_GLN = "Field length 18
TABLES
I_TAB_FIELD_VALUES = "Interface Structure for Generic Transfer of Values
EXCEPTIONS
INCONSISTENT_INTERFACE = 1 NO_GLN_FOUND = 2
EXPORTING Parameters details for EAN_GLN_MAPPING
E_GLN - Field length 18
Data type: CHAR18Optional: No
Call by Reference: Yes
TABLES Parameters details for EAN_GLN_MAPPING
I_TAB_FIELD_VALUES - Interface Structure for Generic Transfer of Values
Data type: EANS_FIELDS_VALUEOptional: No
Call by Reference: Yes
EXCEPTIONS details
INCONSISTENT_INTERFACE - Interface table does not match Customizing table
Data type:Optional: No
Call by Reference: Yes
NO_GLN_FOUND - No GLN found for current interface data
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for EAN_GLN_MAPPING 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_e_gln | TYPE CHAR18, " | |||
| lt_i_tab_field_values | TYPE STANDARD TABLE OF EANS_FIELDS_VALUE, " | |||
| lv_inconsistent_interface | TYPE EANS_FIELDS_VALUE, " | |||
| lv_no_gln_found | TYPE EANS_FIELDS_VALUE. " |
|   CALL FUNCTION 'EAN_GLN_MAPPING' "Re-coding of object on GLN |
| IMPORTING | ||
| E_GLN | = lv_e_gln | |
| TABLES | ||
| I_TAB_FIELD_VALUES | = lt_i_tab_field_values | |
| EXCEPTIONS | ||
| INCONSISTENT_INTERFACE = 1 | ||
| NO_GLN_FOUND = 2 | ||
| . " EAN_GLN_MAPPING | ||
ABAP code using 7.40 inline data declarations to call FM EAN_GLN_MAPPING
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