SAP MS_FILL_TABS_FROM_EXT_DATA Function Module for NOTRANSL: Erzeugung der internen Tabellen wenn von extern eingelesen wird
MS_FILL_TABS_FROM_EXT_DATA is a standard ms fill tabs from ext data SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Erzeugung der internen Tabellen wenn von extern eingelesen wird 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 ms fill tabs from ext data FM, simply by entering the name MS_FILL_TABS_FROM_EXT_DATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: MLSP
Program Name: SAPLMLSP
Main Program: SAPLMLSP
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MS_FILL_TABS_FROM_EXT_DATA 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 'MS_FILL_TABS_FROM_EXT_DATA'"NOTRANSL: Erzeugung der internen Tabellen wenn von extern eingelesen wird.
EXPORTING
* REF_PACKNO = "
TABLES
* EXT_ESUH = "
* EXT_ESLL = "Change Document Structure: Generated by RSSCD000
* EXT_ESUC = "
* EXT_ESKL = "
* EXT_ESKN = "
* EXT_SRV_TEXT = "
EXCEPTIONS
EXT_DATA_NOT_VALID = 1 FATAL_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_SAPLMLSP_001 *** As of 4.0 in Standard SAP System *** Formula Calculation
EXIT_SAPLMLSP_002 ** As of 4.0 in Std. SAP System ** User Exit: Query Whether Formula Exists
EXIT_SAPLMLSP_010 Query Whether Selection of Services from Other Systems is Allowed
EXIT_SAPLMLSP_011 Call Foreign Selection for Services
EXIT_SAPLMLSP_020 *** As of 3.1G in Standard SAP System *** Unplanned Portion/Entry Sheet
EXIT_SAPLMLSP_030 User Exit: Fill ESLL Structure Before Checks (After Entry)
EXIT_SAPLMLSP_031 Check ESLL Datat After Checking
EXIT_SAPLMLSP_040 Transfer of Data to Detail User Screen
EXIT_SAPLMLSP_041 Adoption of Data from User Screen
EXIT_SAPLMLSP_043
IMPORTING Parameters details for MS_FILL_TABS_FROM_EXT_DATA
REF_PACKNO -
Data type: ESLH-PACKNOOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for MS_FILL_TABS_FROM_EXT_DATA
EXT_ESUH -
Data type: ESUHOptional: Yes
Call by Reference: No ( called with pass by value option)
EXT_ESLL - Change Document Structure: Generated by RSSCD000
Data type: ESLLOptional: Yes
Call by Reference: Yes
EXT_ESUC -
Data type: ESUCOptional: Yes
Call by Reference: No ( called with pass by value option)
EXT_ESKL -
Data type: ESKLOptional: Yes
Call by Reference: No ( called with pass by value option)
EXT_ESKN -
Data type: ESKNOptional: Yes
Call by Reference: No ( called with pass by value option)
EXT_SRV_TEXT -
Data type: SRV_TEXTOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
EXT_DATA_NOT_VALID -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
FATAL_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MS_FILL_TABS_FROM_EXT_DATA 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: | ||||
| lt_ext_esuh | TYPE STANDARD TABLE OF ESUH, " | |||
| lv_ref_packno | TYPE ESLH-PACKNO, " | |||
| lv_ext_data_not_valid | TYPE ESLH, " | |||
| lt_ext_esll | TYPE STANDARD TABLE OF ESLL, " | |||
| lv_fatal_error | TYPE ESLL, " | |||
| lt_ext_esuc | TYPE STANDARD TABLE OF ESUC, " | |||
| lt_ext_eskl | TYPE STANDARD TABLE OF ESKL, " | |||
| lt_ext_eskn | TYPE STANDARD TABLE OF ESKN, " | |||
| lt_ext_srv_text | TYPE STANDARD TABLE OF SRV_TEXT. " |
|   CALL FUNCTION 'MS_FILL_TABS_FROM_EXT_DATA' "NOTRANSL: Erzeugung der internen Tabellen wenn von extern eingelesen wird |
| EXPORTING | ||
| REF_PACKNO | = lv_ref_packno | |
| TABLES | ||
| EXT_ESUH | = lt_ext_esuh | |
| EXT_ESLL | = lt_ext_esll | |
| EXT_ESUC | = lt_ext_esuc | |
| EXT_ESKL | = lt_ext_eskl | |
| EXT_ESKN | = lt_ext_eskn | |
| EXT_SRV_TEXT | = lt_ext_srv_text | |
| EXCEPTIONS | ||
| EXT_DATA_NOT_VALID = 1 | ||
| FATAL_ERROR = 2 | ||
| . " MS_FILL_TABS_FROM_EXT_DATA | ||
ABAP code using 7.40 inline data declarations to call FM MS_FILL_TABS_FROM_EXT_DATA
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 PACKNO FROM ESLH INTO @DATA(ld_ref_packno). | ||||
Search for further information about these or an SAP related objects