EKCOM SAP (Communications Work Area for Purchasing Document Accesses) Structure details
Description: Communications Work Area for Purchasing Document Accesses
Structure field list including key, data, relationships and ABAP select examples
EKCOM 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 "Communications Work Area for Purchasing Document Accesses" 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_EKCOM TYPE EKCOM.
The EKCOM table consists of various fields, each holding specific information or linking keys about Communications Work Area for Purchasing Document Accesses data available in SAP. These include MATKL (Material Group), OMATN (Select only documents without material), EKORG (Purchasing Organization), EKGRP (Purchasing Group).. 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)
SAP EKCOM 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 |
| MATNR | Material Number | MATNR | CHAR | 18 | MARA | MATN1 | MATNR | MAT | S_MAT1 |
| MATKL | Material Group | MATKL | CHAR | 9 | T023 | MATKL | MKL | S_WBWG | |
| OMATN | Select only documents without material | OMATN | CHAR | 1 | XFELD | ||||
| EKORG | Purchasing Organization | EKORG | CHAR | 4 | T024E | EKORG | EKO | ||
| EKGRP | Purchasing Group | EKGRP | CHAR | 3 | T024 | EKGRP | EKG | ||
| LIFNR | Vendor Account Number | ELIFN | CHAR | 10 | LFA1 | ALPHA | LIFNR | LIF | KRED_C |
| BEDAT_AB | Document date from | BEDAT_AB | DATS | 8 | DATUM | ||||
| BEDAT_BIS | Document date to | BEDAT_BIS | DATS | 8 | DATUM | ||||
| ZUART | Access type | DZUART_VB | CHAR | 1 | ZUART_VB | ||||
| TRVOG | Transaction group | TRVOG | CHAR | 1 | TRVOG | VTV | |||
| KOPF_DAZU | Indicator: Read purchasing document header also | EKOPF_DAZU | CHAR | 1 | XFELD | ||||
| NAME_DAZU | Indicator: Read vendor name also | LNAME_DAZU | CHAR | 1 | XFELD | ||||
| MANDT | Client | MANDT | CLNT | 3 | T000 | MANDT | |||
| BSTYF | Indicator: Also display purchase orders | BSTYF | CHAR | 1 | XFELD | ||||
| BSTYK | Indicator: Also display contracts | BSTYK | CHAR | 1 | XFELD | ||||
| BSTYL | Indicator: Also display scheduling agreements | BSTYL | CHAR | 1 | XFELD | ||||
| BSTYA | Indicator: Also display RFQs | BSTYA | CHAR | 1 | XFELD |
| Key field | Non-key field |
How do I retrieve data from SAP structure EKCOM using ABAP code?
As EKCOM 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 EKCOM as there is no data to select.How to access SAP table EKCOM
Within an ECC or HANA version of SAP you can also view further information about EKCOM 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