PRELID_DB SAP (Component Node Relationship in the Database Layer) Structure details
Description: Component Node Relationship in the Database Layer
Structure field list including key, data, relationships and ABAP select examples
PRELID_DB 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 "Component Node Relationship in the Database Layer" 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_PRELID_DB TYPE PRELID_DB.
The PRELID_DB table consists of various fields, each holding specific information or linking keys about Component Node Relationship in the Database Layer data available in SAP. These include MANDT (Client), PRGUID (Internal Number for PVS Relationship), OTYPE1 (iPPE Object Type), GUID1 (Internal Identification for PVS Objects).. 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 PRELID_DB 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 | |||
| PRGUID | Internal Number for PVS Relationship | PVS_PRGUID | RAW | 16 | SYSUUID | ||||
| OTYPE1 | iPPE Object Type | PVS_OTYPE | CHAR | 1 | PVS_OTYPE | ||||
| GUID1 | Internal Identification for PVS Objects | PVS_GUID | RAW | 16 | SYSUUID | ||||
| APPLOBJ_TYPE1 | iPPE Application Object Type | PPE_APPLOBJ_TYPE | CHAR | 4 | CHAR4 | ||||
| OTYPE2 | iPPE Object Type | PVS_OTYPE | CHAR | 1 | PVS_OTYPE | ||||
| GUID2 | Internal Identification for PVS Objects | PVS_GUID | RAW | 16 | SYSUUID | ||||
| APPLOBJ_TYPE2 | iPPE Application Object Type | PPE_APPLOBJ_TYPE | CHAR | 4 | CHAR4 | ||||
| PRTYPE | iPPE Relationship Type | PVS_PNREL_TYPE | CHAR | 8 | Assigned to domain | PVS_PNREL_TYPE | |||
| APPLREL_TYPE | Relationship Application Type | PVS_RELOBJ_TYPE | CHAR | 4 | PVS_RELOBJ_TYPE | ||||
| HISTFLG | PVS Object Changed with History | PVS_HISTFLG | CHAR | 1 | XFELD | ||||
| CREADAT | Date of Application | PVS_ANDAT | DATS | 8 | DATUM | ||||
| CREABY | User who created record | PVS_ANNAM | CHAR | 12 | USNAM | ||||
| CHNGDAT | Date of Last Change | PVS_AEDAT | DATS | 8 | DATUM | ||||
| CHNGBY | Name of Person Who Changed Object | PVS_AENAM | CHAR | 12 | USNAM | ||||
| LOGSYS | Logical system | LOGSYS | CHAR | 10 | Assigned to domain | ALPHA | LOGSYS | ||
| TIMSTMP | Time Stamp - Short Format | PVS_TIMSTMP_SHORT | DEC | 15 | TZNTSTMPS | ||||
| SORT | Sort Field for iPPE Relationships | PPE_PRELID_SORT | NUMC | 6 | |||||
| DBOP | Update indicator | PVS_DBOP | CHAR | 1 | PVS_VERBUCHER |
| Key field | Non-key field |
How do I retrieve data from SAP structure PRELID_DB using ABAP code?
As PRELID_DB 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 PRELID_DB as there is no data to select.How to access SAP table PRELID_DB
Within an ECC or HANA version of SAP you can also view further information about PRELID_DB 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