ESO_S_EKKO_SA SAP (Extraction Structure for Scheduling Agreement Header Data) Structure details
Description: Extraction Structure for Scheduling Agreement Header Data
Related tables to ESO_S_EKKO_SA
Access table ESO_S_EKKO_SA
Structure field list including key, data, relationships and ABAP select examples
ESO_S_EKKO_SA 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 "Extraction Structure for Scheduling Agreement Header Data" 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_ESO_S_EKKO_SA TYPE ESO_S_EKKO_SA.
The ESO_S_EKKO_SA table consists of various fields, each holding specific information or linking keys about Extraction Structure for Scheduling Agreement Header Data data available in SAP. These include BUKRS (Company Code), BSTYP (Purchasing Document Category), BSART (Purchasing Document Type), ERNAM (Name of Person who Created the Object).. 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 ESO_S_EKKO_SA 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 |
| EBELN | Purchasing Document Number | EBELN | CHAR | 10 | Assigned to domain | ALPHA | EBELN | BES | MEKK_C |
| BUKRS | Company Code | BUKRS | CHAR | 4 | Assigned to domain | BUKRS | BUK | C_T001 | |
| BSTYP | Purchasing Document Category | EBSTYP | CHAR | 1 | EBSTYP | ||||
| BSART | Purchasing Document Type | ESART | CHAR | 4 | Assigned to domain | BSART | BSA | ||
| ERNAM | Name of Person who Created the Object | ERNAM | CHAR | 12 | USNAM | ||||
| LIFNR | Vendor Account Number | ELIFN | CHAR | 10 | Assigned to domain | ALPHA | LIFNR | LIF | KRED_C |
| ZTERM | Terms of Payment Key | DZTERM | CHAR | 4 | ZTERM | ||||
| EKORG | Purchasing Organization | EKORG | CHAR | 4 | Assigned to domain | EKORG | EKO | ||
| EKGRP | Purchasing Group | BKGRP | CHAR | 3 | Assigned to domain | EKGRP | EKG | ||
| WAERS | Currency Key | WAERS | CUKY | 5 | Assigned to domain | WAERS | FWS | ||
| BEDAT | Purchase Order Date | BEDAT | DATS | 8 | DATUM | ||||
| KDATB | Start of Validity Period | KDATB | DATS | 8 | DATUM | ||||
| KDATE | End of Validity Period | KDATE | DATS | 8 | DATUM | ||||
| ANGNR | Quotation Number | ANGNR | CHAR | 10 | ANGNR | ||||
| PROCSTAT | Purchasing document processing state | MEPROCSTATE | CHAR | 2 | MEPROCSTATE |
| Key field | Non-key field |
How do I retrieve data from SAP structure ESO_S_EKKO_SA using ABAP code?
As ESO_S_EKKO_SA 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 ESO_S_EKKO_SA as there is no data to select.How to access SAP table ESO_S_EKKO_SA
Within an ECC or HANA version of SAP you can also view further information about ESO_S_EKKO_SA 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