EREVDATA SAP (DCM Version in Purchasing: Data) Structure details
Description: DCM Version in Purchasing: Data
Structure field list including key, data, relationships and ABAP select examples
EREVDATA 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 "DCM Version in Purchasing: 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_EREVDATA TYPE EREVDATA.
The EREVDATA table consists of various fields, each holding specific information or linking keys about DCM Version in Purchasing: Data data available in SAP. These include ERDAT (Date on Which Record Was Created), ERUHR (Entry time), FGNAM (Name of person effecting release), FGDAT (Date of release).. 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 EREVDATA 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 |
| ERNAM | Name of Person who Created the Object | ERNAM | CHAR | 12 | USNAM | ||||
| ERDAT | Date on Which Record Was Created | ERDAT | DATS | 8 | DATUM | ||||
| ERUHR | Entry time | ERZET | TIMS | 6 | UZEIT | ||||
| FGNAM | Name of person effecting release | FGNAM | CHAR | 12 | USNAM | ||||
| FGDAT | Date of release | FGDAT | DATS | 8 | DATUM | ||||
| FGUHR | Time of release | FGUHR | TIMS | 6 | UZEIT | ||||
| OKNAM | Name of approving buyer | OKNAM | CHAR | 12 | USNAM | ||||
| OKDAT | Date of buyer approval | OKDAT | DATS | 8 | DATUM | ||||
| OKUHR | Time of buyer approval | OKUHR | TIMS | 6 | UZEIT | ||||
| RSCOD | Reason for change | RSCOD | CHAR | 4 | T16CC | RSCOD | |||
| TXZ01 | Description of version | TXZ01_DCM | CHAR | 60 | TEXT60 | ||||
| EXTNR | External Change Number of Version | DCM_EXTNR | CHAR | 20 | CHAR20 | ||||
| CRNAM | Person requesting change | DCM_AFNAM | CHAR | 12 | AFNAM | ||||
| NETWR | Net Order Value in PO Currency | BWERT | CURR | 13(2) | WERT7 | ||||
| DIFWR | Value change due to version | DCM_DIFWR | CURR | 13(2) | WERTV7 | ||||
| WAERS | Currency Key | WAERS | CUKY | 5 | Assigned to domain | WAERS | FWS | ||
| BUDAT | Posting date of version | DCM_BUDAT | DATS | 8 | DATUM | ||||
| REVOK | Status 'version completed' | DCM_REVOK | CHAR | 1 | XFELD | ||||
| STREV | Version status | STREV | CHAR | 1 | STREV | ||||
| LOEKZ | Deletion Indicator in Purchasing Document | ELOEK | CHAR | 1 | ELOEK | ||||
| BANPR | Old processing state in purchasing document before version | BANPR_OLD | CHAR | 2 | BANPR |
| Key field | Non-key field |
How do I retrieve data from SAP structure EREVDATA using ABAP code?
As EREVDATA 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 EREVDATA as there is no data to select.How to access SAP table EREVDATA
Within an ECC or HANA version of SAP you can also view further information about EREVDATA 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