/PLMI/S_GSS_RCP_HEAD_VTX SAP (GSS Vertex: Recipe Header) Structure details
Description: GSS Vertex: Recipe Header
Related tables to /PLMI/S_GSS_RCP_HEAD_VTX
Access table /PLMI/S_GSS_RCP_HEAD_VTX
Structure field list including key, data, relationships and ABAP select examples
/PLMI/S_GSS_RCP_HEAD_VTX 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 "GSS Vertex: Recipe 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_/PLMI/S_GSS_RCP_HEAD_VTX TYPE /PLMI/S_GSS_RCP_HEAD_VTX.
The /PLMI/S_GSS_RCP_HEAD_VTX table consists of various fields, each holding specific information or linking keys about GSS Vertex: Recipe Header data available in SAP. These include KEY_V (), ASPECT (Data Format of a Vertex Header (DDIC Structure)), ID (Identifier of Vertex (Forms Unique Key With Aspect)), KEY_V_PRED ().. 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: Cannot Be Enhanced
SAP /PLMI/S_GSS_RCP_HEAD_VTX 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 |
| KEY_V | 0 | ||||||||
| ASPECT | Data Format of a Vertex Header (DDIC Structure) | /PLMB/GSS_ASPECT_VERTEX | CHAR | 2 | /PLMB/GSS_ASPECT | ||||
| ID | Identifier of Vertex (Forms Unique Key With Aspect) | /PLMB/GSS_ID_VERTEX | SSTR | 90 | /PLMB/GSS_ID | ||||
| KEY_V_PRED | 0 | ||||||||
| ASPECT | Data Format of a Vertex Header (DDIC Structure) | /PLMB/GSS_ASPECT_VERTEX | CHAR | 2 | /PLMB/GSS_ASPECT | ||||
| ID | Identifier of Vertex (Forms Unique Key With Aspect) | /PLMB/GSS_ID_VERTEX | SSTR | 90 | /PLMB/GSS_ID | ||||
| R_APPL_ENHANCE | 0 | ||||||||
| SUBID | Specification ID | /PLMB/RCP_SUBID | CHAR | 12 | CHAR12 | /PLMB/RSP_CMP_DMZ_WO_MATNR | |||
| ALT_NO | Alternative Recipe Identifier | /PLMB/RCP_ALT_NO | CHAR | 3 | CHAR3 | ||||
| VERS_NO | Recipe Version | /PLMB/RCP_VERS_NO | CHAR | 3 | CHAR3 | ||||
| CREATED_BY | User Who Created Object (Item) | /PLMB/RCP_CREATED_BY | CHAR | 12 | USNAM | /PLMB/SEA_COLLECTIVE_USERNAME | |||
| CREATED_TIMESTMP | UTC Time Stamp in Short Form (YYYYMMDDhhmmss) | /PLMB/RCP_TIMESTAMP | DEC | 15 | TZNTSTMPS | ||||
| CHANGED_BY | User Who Last Changed Object | /PLMB/RCP_CHANGED_BY | CHAR | 12 | USNAM | /PLMB/SEA_COLLECTIVE_USERNAME | |||
| CHANGED_TIMESTMP | UTC Time Stamp in Short Form (YYYYMMDDhhmmss) | /PLMB/RCP_TIMESTAMP | DEC | 15 | TZNTSTMPS | ||||
| CREATED_ON | Date on Which Object (Item) Was Created | /PLMB/RCP_CREATED_ON | DATS | 8 | DATUM | ||||
| CREATED_TIME | Time at Which Object (Item) Was Created | /PLMB/RCP_CREATED_TIME | TIMS | 6 | TIME | ||||
| CHANGED_ON | Date on Which Object (Item) Was Last Changed | /PLMB/RCP_CHANGED_ON | DATS | 8 | DATUM | ||||
| CHANGED_TIME | Time at Which Object (Item) Was Changed | /PLMB/RCP_CHANGED_TIME | TIMS | 6 | TIME | ||||
| RCP_GUID | Common Recipe GUID | /PLMB/RCP_GUID | RAW | 16 | SYSUUID | ||||
| DESCR | Recipe Description | /PLMB/RCP_DESC | CHAR | 132 | TEXT132 |
| Key field | Non-key field |
How do I retrieve data from SAP structure /PLMI/S_GSS_RCP_HEAD_VTX using ABAP code?
As /PLMI/S_GSS_RCP_HEAD_VTX 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 /PLMI/S_GSS_RCP_HEAD_VTX as there is no data to select.How to access SAP table /PLMI/S_GSS_RCP_HEAD_VTX
Within an ECC or HANA version of SAP you can also view further information about /PLMI/S_GSS_RCP_HEAD_VTX 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