SAP CM_DI_READ_LIST_DATA Function Module for NOTRANSL: Lesen der Material-, Klassen-, Dokumentdaten bzw. Texte
CM_DI_READ_LIST_DATA is a standard cm di read list 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: Lesen der Material-, Klassen-, Dokumentdaten bzw. Texte 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 cm di read list data FM, simply by entering the name CM_DI_READ_LIST_DATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: CMDI
Program Name: SAPLCMDI
Main Program: SAPLCMDI
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CM_DI_READ_LIST_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 'CM_DI_READ_LIST_DATA'"NOTRANSL: Lesen der Material-, Klassen-, Dokumentdaten bzw. Texte.
EXPORTING
OBJTY = "Object type (BOM item)
* KLART = "Class Type
* SPRAS = "ABAP System Field: Language Key of Text Environment
* IDNRK = "BOM component
* POTX1 = "BOM Item Text (Line 1)
* DOKAR = "Document Type
* DOKNR = "Document number
* DOKTL = "Document Part
* DOKVR = "Document Version
* CLASS = "Class number
IMPORTING
RETURN = "
MATDATEN = "
TABLES
* SEQMAT01 = "
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_SAPLCMDI_001 Determine explosion control via user exit
IMPORTING Parameters details for CM_DI_READ_LIST_DATA
OBJTY - Object type (BOM item)
Data type: STPOB-OBJTYOptional: No
Call by Reference: No ( called with pass by value option)
KLART - Class Type
Data type: STPO-KLARTOptional: Yes
Call by Reference: No ( called with pass by value option)
SPRAS - ABAP System Field: Language Key of Text Environment
Data type: SY-LANGUOptional: Yes
Call by Reference: No ( called with pass by value option)
IDNRK - BOM component
Data type: STPO-IDNRKOptional: Yes
Call by Reference: No ( called with pass by value option)
POTX1 - BOM Item Text (Line 1)
Data type: STPO-POTX1Optional: Yes
Call by Reference: No ( called with pass by value option)
DOKAR - Document Type
Data type: STPO-DOKAROptional: Yes
Call by Reference: No ( called with pass by value option)
DOKNR - Document number
Data type: STPO-DOKNROptional: Yes
Call by Reference: No ( called with pass by value option)
DOKTL - Document Part
Data type: STPO-DOKTLOptional: Yes
Call by Reference: No ( called with pass by value option)
DOKVR - Document Version
Data type: STPO-DOKVROptional: Yes
Call by Reference: No ( called with pass by value option)
CLASS - Class number
Data type: STPO-CLASSOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CM_DI_READ_LIST_DATA
RETURN -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
MATDATEN -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for CM_DI_READ_LIST_DATA
SEQMAT01 -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CM_DI_READ_LIST_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: | ||||
| lv_objty | TYPE STPOB-OBJTY, " | |||
| lv_return | TYPE STPOB, " | |||
| lt_seqmat01 | TYPE STANDARD TABLE OF STPOB, " | |||
| lv_klart | TYPE STPO-KLART, " | |||
| lv_spras | TYPE SY-LANGU, " | |||
| lv_matdaten | TYPE SY, " | |||
| lv_idnrk | TYPE STPO-IDNRK, " | |||
| lv_potx1 | TYPE STPO-POTX1, " | |||
| lv_dokar | TYPE STPO-DOKAR, " | |||
| lv_doknr | TYPE STPO-DOKNR, " | |||
| lv_doktl | TYPE STPO-DOKTL, " | |||
| lv_dokvr | TYPE STPO-DOKVR, " | |||
| lv_class | TYPE STPO-CLASS. " |
|   CALL FUNCTION 'CM_DI_READ_LIST_DATA' "NOTRANSL: Lesen der Material-, Klassen-, Dokumentdaten bzw. Texte |
| EXPORTING | ||
| OBJTY | = lv_objty | |
| KLART | = lv_klart | |
| SPRAS | = lv_spras | |
| IDNRK | = lv_idnrk | |
| POTX1 | = lv_potx1 | |
| DOKAR | = lv_dokar | |
| DOKNR | = lv_doknr | |
| DOKTL | = lv_doktl | |
| DOKVR | = lv_dokvr | |
| CLASS | = lv_class | |
| IMPORTING | ||
| RETURN | = lv_return | |
| MATDATEN | = lv_matdaten | |
| TABLES | ||
| SEQMAT01 | = lt_seqmat01 | |
| . " CM_DI_READ_LIST_DATA | ||
ABAP code using 7.40 inline data declarations to call FM CM_DI_READ_LIST_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 OBJTY FROM STPOB INTO @DATA(ld_objty). | ||||
| "SELECT single KLART FROM STPO INTO @DATA(ld_klart). | ||||
| "SELECT single LANGU FROM SY INTO @DATA(ld_spras). | ||||
| "SELECT single IDNRK FROM STPO INTO @DATA(ld_idnrk). | ||||
| "SELECT single POTX1 FROM STPO INTO @DATA(ld_potx1). | ||||
| "SELECT single DOKAR FROM STPO INTO @DATA(ld_dokar). | ||||
| "SELECT single DOKNR FROM STPO INTO @DATA(ld_doknr). | ||||
| "SELECT single DOKTL FROM STPO INTO @DATA(ld_doktl). | ||||
| "SELECT single DOKVR FROM STPO INTO @DATA(ld_dokvr). | ||||
| "SELECT single CLASS FROM STPO INTO @DATA(ld_class). | ||||
Search for further information about these or an SAP related objects