MCEKESB SAP (EKS communication structure for EKES) Structure details
Description: EKS communication structure for EKES
Structure field list including key, data, relationships and ABAP select examples
MCEKESB 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 "EKS communication structure for EKES" 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_MCEKESB TYPE MCEKESB.
The MCEKESB table consists of various fields, each holding specific information or linking keys about EKS communication structure for EKES data available in SAP. These include MANDT (Client), EBELN (Purchasing Document Number), EBELP (Item Number of Purchasing Document), ETENS (Sequential Number of Vendor Confirmation).. 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 MCEKESB 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 |
| SUPKZ | Statistics update indicator (post in/post out) | SUPKZ | CHAR | 1 | SUPKZ | ||||
| MANDT | Client | MANDT | CLNT | 3 | T000 | MANDT | |||
| EBELN | Purchasing Document Number | EBELN | CHAR | 10 | EKKO | ALPHA | EBELN | BES | MEKK_C |
| EBELP | Item Number of Purchasing Document | EBELP | NUMC | 5 | EKPO | EBELP | BSP | ||
| ETENS | Sequential Number of Vendor Confirmation | ETENS | NUMC | 4 | NUM04 | ||||
| EBTYP | Confirmation Category | EBTYP | CHAR | 2 | T163E | EBTYP | |||
| EINDT | Delivery Date of Vendor Confirmation | BBEIN | DATS | 8 | DATUM | ||||
| LPEIN | Date category of delivery date in vendor confirmation | BBLPE | CHAR | 1 | TPRG | PRGBZ | |||
| UZEIT | Delivery Date Time-Spot in Vendor Confirmation | BBUZE | TIMS | 6 | UZEIT | ||||
| MENGE | Quantity as Per Vendor Confirmation | BBMNG | QUAN | 13(3) | MENGE | ||||
| DABMG | Quantity Reduced (MRP) | DABMG | QUAN | 13(3) | MENGE | ||||
| ESTKZ | Creation Indicator: Vendor Confirmation | BBEST | CHAR | 1 | BBEST | ||||
| KZDIS | Indicator: Confirmation is Relevant to Materials Planning | KZDIS | CHAR | 1 | XFELD | ||||
| VBELN | Delivery | VBELN_VL | CHAR | 10 | VBUK | ALPHA | VBELN | VL | |
| VBELP | Delivery Item | POSNR_VL | NUMC | 6 | VBUP | POSNR | |||
| DIBMG | MRP-relevant confirmed quantity | DIBMG | QUAN | 13(3) | MENGE | ||||
| WEMNG | Quantity of Goods Received | WEMNG | QUAN | 13(3) | MENG13 | ||||
| BELTYP | Document category: rough workload estimate | MCL_BELTYP | CHAR | 3 | MCL_BELTYP | VLT | |||
| DUMMY | Dummy function in length 1 | DUMMY | CHAR | 1 | DUMMY |
| Key field | Non-key field |
How do I retrieve data from SAP structure MCEKESB using ABAP code?
As MCEKESB 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 MCEKESB as there is no data to select.How to access SAP table MCEKESB
Within an ECC or HANA version of SAP you can also view further information about MCEKESB 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