IEKEK SAP (Change Structure for EKEK) Structure details
Description: Change Structure for EKEK
Structure field list including key, data, relationships and ABAP select examples
IEKEK 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 EKEK" 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_IEKEK TYPE IEKEK.
The IEKEK table consists of various fields, each holding specific information or linking keys about Change Structure for EKEK 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: Not classified
SAP IEKEK 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 | |||
| ABEFZ | Cumulative Received Quantity for Scheduling Agreement | MEAWEFZ | QUAN | 13(3) | MENG13 | ||||
| ABRDT | Date of Scheduling Agreement Release (Transmission Date) | MEABRDT | DATS | 8 | DATUM | ||||
| LFDKD | Date of Delivery Note | MELFDKD | DATS | 8 | DATUM | ||||
| LFNKD | Number of Delivery Note | MELFNKD1 | CHAR | 16 | XBLNR1 | ||||
| LWEDT | Date of Last Goods Receipt | MELWEDT | DATS | 8 | DATUM | ||||
| LWEMG | Quantity of Last Goods Receipt | MELWEMG | QUAN | 13(3) | MENG13 | ||||
| ABLLI | External release number | MEABLLI | CHAR | 20 | ABLLI | ||||
| ERDAT | Date Release was Created | MEERDAT | DATS | 8 | DATUM | ||||
| ABSFZ | Agreed Cumulative Quantity | ABFTZ | QUAN | 13(3) | MENG13 | ||||
| ABFDE | End of Production Go-Ahead Period | MEABFDE | DATS | 8 | DATUM | ||||
| ABMDE | End of Material Go-Ahead Period | MEABMDE | DATS | 8 | DATUM | ||||
| ERUHR | Time of Creation | MEERUHR | TIMS | 6 | TIME | ||||
| ABRZT | Time | MEABRZT | TIMS | 6 | TIME | ||||
| ABHZT | Release Horizon | ABHZT | DATS | 8 | DATUM | ||||
| RUSKZ | Backlog and/or immediate requirement exist(s) | RUSKZ | CHAR | 1 | RUSKZ | ||||
| STAAB | Status of release | STAAB | CHAR | 1 | STAAB | ||||
| WEBRL | Internet release | WEBRL | CHAR | 1 | WEBRL | ||||
| VENCF | Acknowledgment of Internet SA release by vendor | VENCF | CHAR | 1 | XFELD | ||||
| .INCLU--AP | 0 | ||||||||
| CPUDT | Date Release was Created | MEERDAT | DATS | 8 | DATUM | ||||
| CPUTM | Time of Creation | MEERUHR | TIMS | 6 | TIME | ||||
| STPIN | Stop Status for FRC/JIT | STPIN | CHAR | 1 | STPIN | ||||
| BRSVZ | Backlog/Immediate Requirement Brought Forward | BRSVZ | CHAR | 1 | XFELD | ||||
| ERSGR | Reasons for creation of release | ERSGR | CHAR | 2 | ERSGR | ||||
| LGBZO | (Automotive) Unloading Point | UNLPT | CHAR | 10 | Assigned to domain | LGBZO | ME_SH_UNLOADING_POINT | ||
| INIDT | Date of First Creation of a Scheduling Agreement Release | INIDT | DATS | 8 | DATUM | ||||
| INITM | Time of First Creation of a Scheduling Agreement Release | INITM | TIMS | 6 | UZEIT | ||||
| WEFZMIT | 2nd. Cumulative Received Quantity (2nd CRQ) | WEFZMIT | QUAN | 13(3) | MENG13 | ||||
| DISPO | MRP Controller (Materials Planner) | DISPO | CHAR | 3 | Assigned to domain | DISPO | DGR | HS_T024D | |
| .INCLU--AP | 0 | ||||||||
| LOADCARR | Load carrier | PL_LOADCARR | CHAR | 18 | Assigned to domain | MATN1 | MATNR | MAT1 | |
| T_TRGQTY | Cumulated target quantity | PL_T_TRGQTY | QUAN | 15(3) | MENG15 | ||||
| BASEUNIT | Base Unit of Measure | MEINS | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
| LCTXT | Description of load carrier | PL_CONTENT_LC | CHAR | 40 | TEXT40 | ||||
| .INCLU--AP | 0 | ||||||||
| AKSTOPGR | Stop Reasons for Current Release | AKSTOPGR | CHAR | 20 | CHAR20 | ||||
| UPDKZ | Change Type (U, I, S, D) | CDCHNGIND | CHAR | 1 | CDCHNGIND |
| Key field | Non-key field |
How do I retrieve data from SAP structure IEKEK using ABAP code?
As IEKEK 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 IEKEK as there is no data to select.How to access SAP table IEKEK
Within an ECC or HANA version of SAP you can also view further information about IEKEK 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