VECM_REQ SAP (Change Document Structure; Generated by RSSCD000) Structure details
Description: Change Document Structure; Generated by RSSCD000
Structure field list including key, data, relationships and ABAP select examples
VECM_REQ 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 "Change Document Structure; Generated by RSSCD000" 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_VECM_REQ TYPE VECM_REQ.
The VECM_REQ table consists of various fields, each holding specific information or linking keys about Change Document Structure; Generated by RSSCD000 data available in SAP. These include MANDT (Client), GUID_ECM (GUID for Engineering Change Request), AENNR (Change Order), AETYP (Category of Engineering Change Order).. 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 VECM_REQ 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 |
| MANDT | Client | MANDT | CLNT | 3 | Assigned to domain | MANDT | |||
| GUID_ECM | GUID for Engineering Change Request | ECMREQGUID | RAW | 16 | |||||
| AENNR | Change Order | ECMNR | CHAR | 12 | CHAR12 | ||||
| AETYP | Category of Engineering Change Order | ECMTYP | CHAR | 1 | ECMTYP | ||||
| ECMGROUP | User Group | ECMGRP | CHAR | 30 | CHAR30 | ||||
| AEUSER | Person Responsible | ECMUSERB | CHAR | 12 | SYCHAR12 | ||||
| LVORM | Deletion Indicator | ECMDEL | CHAR | 1 | FLAG | ||||
| ENDDAT | Planned Release Date | ECMENDDAT | DATS | 8 | SYDATS | ||||
| AEKND | Change Type | ECMKND | CHAR | 10 | CHAR10 | ECMKND | |||
| REF_REQ | GUID for Engineering Change Request | ECMREQGUID | RAW | 16 | |||||
| GUID_REQ_WORK | GUID for Scope of Engineering Change Request | ECMREQWORKGUID | RAW | 16 | |||||
| REASON | Reason for Triggering | ECMREAS | CHAR | 12 | CHAR12 | ||||
| PRIO | Priority of Change | ECMPRIO | CHAR | 12 | ECMPRIO | ||||
| STSMA | Status Profile | J_STSMA | CHAR | 8 | Assigned to domain | J_STSMA | |||
| SUBMITTER | Business Partner Number | BU_PARTNER | CHAR | 10 | Assigned to domain | ALPHA | BU_PARTNER | BPA | BUPA |
| COST_OVV | Total Estimated Costs | COST_OVV | DEC | 15(2) | COST_ECMREQ | ||||
| CURRENCY | Currency Unit for Estimated Costs | ECM_WAE | CUKY | 5 | ECM_WAE | ||||
| KZ | Change Type (U, I, S, D) | CDCHNGIND | CHAR | 1 | CDCHNGIND |
| Key field | Non-key field |
How do I retrieve data from SAP structure VECM_REQ using ABAP code?
As VECM_REQ 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 VECM_REQ as there is no data to select.How to access SAP table VECM_REQ
Within an ECC or HANA version of SAP you can also view further information about VECM_REQ 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