SAP table PNODID (iPPE Node: Identification)
SAP table PNODID has 2 primary key fields being MANDT,PNGUID.
If you're only analyzing data from a single SAP instance you may omit field MANT in your relationships as it will we the same across the entire dataset. On the other hand, if you're combining data from multiple SAP instances you need to take MANDT into account.
| Field | Description | Data Type | Length | Decimals | Checktable | Data Element | |
|---|---|---|---|---|---|---|---|
| MANDT | Client | CLNT | 3 | 0 | T000 | MANDT | |
| PNGUID | Internal Number of iPPE Node | RAW | 16 | 0 | PVS_PNGUID | ||
| PNAME | iPPE Node Description | CHAR | 40 | 0 | PVS_PNODE | ||
| NAMEID | ID of the Context-Providing Node Object | CHAR | 40 | 0 | PPE_NAMEID | ||
| NAMEID_OTYPE | Technical Type of Context-Providing Object | CHAR | 1 | 0 | PPE_NAMEID_OTYPE | ||
| NAMEID_APPLOBJ | Application of Object that Provides the Context | CHAR | 4 | 0 | PPE_NAMEID_APPLOBJ | ||
| CLINT | Internal Class Number | NUMC | 10 | 0 | KLAH | CLINT | |
| PNTYPE | iPPE Node Type | CHAR | 8 | 0 | CPNTYPE | PVS_PNODE_TYPE | |
| APPLOBJ_TYPE | iPPE Application Object Type | CHAR | 4 | 0 | PPE_APPLOBJ_TYPE | ||
| TIMSTMP | UTC Time Stamp in Long Form (YYYYMMDDhhmmss,mmmuuun) | DEC | 21 | 7 | PVS_TIMSTMP | ||
| CREADAT | Date of Application | DATS | 8 | 0 | PVS_ANDAT | ||
| CREABY | User who created record | CHAR | 12 | 0 | PVS_ANNAM | ||
| CHNGDAT | Date of Last Change | DATS | 8 | 0 | PVS_AEDAT | ||
| CHNGBY | Name of Person Who Changed Object | CHAR | 12 | 0 | PVS_AENAM | ||
| LOGSYS | Logical system | CHAR | 10 | 0 | * | LOGSYS | |
| HISTFLG | PVS Object Changed with History | CHAR | 1 | 0 | PVS_HISTFLG |
PNODID foreign key relationships
| Table | Field | Check Table | Check Field | |
|---|---|---|---|---|
| 0 PNODID | CLINT | KLAH | Class Header Data | MANDT |
| 0 PNODID | CLINT | KLAH | Class Header Data | CLINT |
| 1 PNODID | MANDT | T000 | Clients | MANDT |
| 0 PNODID | PNTYPE | CPNTYPE | Customizing Table for iPPE Node Type | MANDT |