EREVHEADER SAP (Version in Purchasing: Header) Structure details
Description: Version in Purchasing: Header
Structure field list including key, data, relationships and ABAP select examples
EREVHEADER 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 "Version in Purchasing: Header" 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_EREVHEADER TYPE EREVHEADER.
The EREVHEADER table consists of various fields, each holding specific information or linking keys about Version in Purchasing: Header data available in SAP. These include EDOKN (Object Number in Purchasing), EDOKP (Purchasing object: item), BSART (Purchasing Document Type), EKORG (Purchasing Organization).. 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 EREVHEADER 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 |
| BSTYP | Purchasing Document Category | BSTYP_DCM | CHAR | 1 | BSTYP_DCM | ||||
| EDOKN | Object Number in Purchasing | EDOKN | CHAR | 10 | ALPHA | EDOKN | |||
| EDOKP | Purchasing object: item | EDOKP | NUMC | 5 | Assigned to domain | EBELP | |||
| BSART | Purchasing Document Type | ESART | CHAR | 4 | Assigned to domain | BSART | BSA | ||
| EKORG | Purchasing Organization | EKORG | CHAR | 4 | Assigned to domain | EKORG | EKO | ||
| ACTIV | Version Management in Purchasing Active | ACTIV_DCM | CHAR | 1 | XFELD | ||||
| EXIST | DCM Purchasing document exists in database | EXIST_DCM | CHAR | 1 | CHAR1 | ||||
| ACTIVITY | Activity category in SAP transaction | AKTYP | CHAR | 1 | AKTYP | ||||
| PREISANZ | Indicator: Authorization to display price data | PREISANZ | CHAR | 1 | X | ||||
| COMPLETE | Version always completed | COMPLETE_DCM | CHAR | 1 | XFELD | ||||
| REVNO | Version number in Purchasing | REVNO | CHAR | 8 | ALPHA | REVNO | |||
| EXTREQ | Externally Generated Purchase Requisition | EXTREQ | CHAR | 1 | XFELD | ||||
| ESTKZ | Creation Indicator (Purchase Requisition/Schedule Lines) | ESTKZ | CHAR | 1 | ESTKZ |
| Key field | Non-key field |
How do I retrieve data from SAP structure EREVHEADER using ABAP code?
As EREVHEADER 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 EREVHEADER as there is no data to select.How to access SAP table EREVHEADER
Within an ECC or HANA version of SAP you can also view further information about EREVHEADER 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