IEKEH SAP (Change Structure for EKEH) Structure details
Description: Change Structure for EKEH
Structure field list including key, data, relationships and ABAP select examples
IEKEH is a standard SAP Structure so does not store data like a database table does. It can be used to define the fields of other actual tables or to process "Change Structure for EKEH" Information within sap ABAP programs.
This is done by declaring abap internal tables, work areas or database tables based on this Structure. These can then be used to store and process the required data appropriately.
i.e. DATA: wa_IEKEH TYPE IEKEH.
The IEKEH table consists of various fields, each holding specific information or linking keys about Change Structure for EKEH data available in SAP. These include MANDT (Client), EBELN (Purchasing Document Number), EBELP (Item Number of Purchasing Document), ABART (Scheduling agreement release type).. See below for full list along with technical details, documentation, text table, check tables, foreign key relationships, conversion routines, relevant tcodes and example ABAP select code etc. .
Delivery Class:Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Can be enhanced (character-type or numeric)
SAP IEKEH structure fields - Full list of fields found in SAP data dictionary
Field | Description | Data Element | Data Type | length (Dec) | Check table | Conversion Routine | Domain Name | MemoryID | SHLP |
MANDT | Client | MANDT | CLNT | 3 | Assigned to domain | MANDT | |||
EBELN | Purchasing Document Number | EBELN | CHAR | 10 | Assigned to domain | ALPHA | EBELN | BES | MEKK_C |
EBELP | Item Number of Purchasing Document | EBELP | NUMC | 5 | Assigned to domain | EBELP | BSP | ||
ABART | Scheduling agreement release type | MEABART | CHAR | 1 | ABART | SAGA | |||
ABRUF | Release Number | MEABRUF | NUMC | 10 | ABRUF | SAGN | |||
ETENR | Delivery Schedule Line Counter | EETEN | NUMC | 4 | Assigned to domain | EETEN | |||
EINDT | Item Delivery Date | EINDT | DATS | 8 | DATUM | ||||
LPEIN | Category of Delivery Date | LPEIN | CHAR | 1 | Assigned to domain | PRGBZ | |||
UZEIT | Delivery Date Time-Spot | LZEIT | TIMS | 6 | UZEIT | ||||
MENGE | Scheduled Quantity | ETMEN | QUAN | 13(3) | MENGE | ||||
ETART | Schedule line type (backlog, immed. requirement, forecast) | MEETART | CHAR | 1 | MEETART | ||||
SERNR | BOM explosion number | SERNR | CHAR | 8 | Assigned to domain | SERNR | |||
ESTKZ | Creation Indicator (Purchase Requisition/Schedule Lines) | ESTKZ | CHAR | 1 | ESTKZ | ||||
AMENG | Previous Quantity (Delivery Schedule Lines) | VOMNG | QUAN | 13(3) | MENG13V | ||||
WEMNG | Quantity of Goods Received | WEEMG | QUAN | 13(3) | MENG13 | ||||
UPDKZ | Change Type (U, I, S, D) | CDCHNGIND | CHAR | 1 | CDCHNGIND | ||||
DABMG | Quantity Reduced (MRP) | DABMG | QUAN | 13(3) | MENGE |
Key field | Non-key field |
How do I retrieve data from SAP structure IEKEH using ABAP code?
As IEKEH is a database structure and not a table it does not store any data in the SAP data dictionary. The ABAP SELECT statement is therefore not appropriate and can not be performed on IEKEH as there is no data to select.How to access SAP table IEKEH
Within an ECC or HANA version of SAP you can also view further information about IEKEH and the data within it using relevant transactions such asSE11 (ABAP Dictionary Maintenance)
SM30 (Maintain Table Data)
SE80 (Object Navigator)
SE16 (Data Browser).
Search for further information about these or an SAP related objects