SAP ILM_READ_KEY_FIELDS Function Module for NOTRANSL: Lesen der Felddefinition mit Hilfe der AS Indizierung
ILM_READ_KEY_FIELDS is a standard ilm read key fields 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 Felddefinition mit Hilfe der AS Indizierung 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 ilm read key fields FM, simply by entering the name ILM_READ_KEY_FIELDS into the relevant SAP transaction such as SE37 or SE38.
Function Group: ILM_GEN
Program Name: SAPLILM_GEN
Main Program: SAPLILM_GEN
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ILM_READ_KEY_FIELDS 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 'ILM_READ_KEY_FIELDS'"NOTRANSL: Lesen der Felddefinition mit Hilfe der AS Indizierung.
EXPORTING
IV_ORIG_SYSTEM = "Name of the SAP System
IV_ORIG_CLIENT = "Client ID of Current User
IV_TABNAME = "Table Name
IMPORTING
ET_KEY_TABLE = "
EXCEPTIONS
READ_FROM_ARCHIVE_FAILS = 1 NO_INSTRUCTURE_DEFINED = 2 NOT_IN_INFOSTRUCTURE = 3
IMPORTING Parameters details for ILM_READ_KEY_FIELDS
IV_ORIG_SYSTEM - Name of the SAP System
Data type: SYSYSIDOptional: No
Call by Reference: Yes
IV_ORIG_CLIENT - Client ID of Current User
Data type: SY-MANDTOptional: No
Call by Reference: Yes
IV_TABNAME - Table Name
Data type: TABNAMEOptional: No
Call by Reference: Yes
EXPORTING Parameters details for ILM_READ_KEY_FIELDS
ET_KEY_TABLE -
Data type: KECB_FIELD_TABLEOptional: No
Call by Reference: Yes
EXCEPTIONS details
READ_FROM_ARCHIVE_FAILS - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
NO_INSTRUCTURE_DEFINED - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
NOT_IN_INFOSTRUCTURE - Does not exist in the info structure
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ILM_READ_KEY_FIELDS 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_et_key_table | TYPE KECB_FIELD_TABLE, " | |||
| lv_iv_orig_system | TYPE SYSYSID, " | |||
| lv_read_from_archive_fails | TYPE SYSYSID, " | |||
| lv_iv_orig_client | TYPE SY-MANDT, " | |||
| lv_no_instructure_defined | TYPE SY, " | |||
| lv_iv_tabname | TYPE TABNAME, " | |||
| lv_not_in_infostructure | TYPE TABNAME. " |
|   CALL FUNCTION 'ILM_READ_KEY_FIELDS' "NOTRANSL: Lesen der Felddefinition mit Hilfe der AS Indizierung |
| EXPORTING | ||
| IV_ORIG_SYSTEM | = lv_iv_orig_system | |
| IV_ORIG_CLIENT | = lv_iv_orig_client | |
| IV_TABNAME | = lv_iv_tabname | |
| IMPORTING | ||
| ET_KEY_TABLE | = lv_et_key_table | |
| EXCEPTIONS | ||
| READ_FROM_ARCHIVE_FAILS = 1 | ||
| NO_INSTRUCTURE_DEFINED = 2 | ||
| NOT_IN_INFOSTRUCTURE = 3 | ||
| . " ILM_READ_KEY_FIELDS | ||
ABAP code using 7.40 inline data declarations to call FM ILM_READ_KEY_FIELDS
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 MANDT FROM SY INTO @DATA(ld_iv_orig_client). | ||||
Search for further information about these or an SAP related objects