PALTID_DB SAP (Identification for an Alternative Segment) Structure details
Description: Identification for an Alternative Segment
Structure field list including key, data, relationships and ABAP select examples
PALTID_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 "Identification for an Alternative Segment" 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_PALTID_DB TYPE PALTID_DB.
The PALTID_DB table consists of various fields, each holding specific information or linking keys about Identification for an Alternative Segment data available in SAP. These include MANDT (Client), PAGUID (Internal Identification for PVS Objects), OTYPE (iPPE Object Type), PGUID (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: Cannot Be Enhanced
SAP PALTID_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 | T000 | MANDT | |||
PAGUID | Internal Identification for PVS Objects | PVS_GUID | RAW | 16 | SYSUUID | ||||
OTYPE | iPPE Object Type | PVS_OTYPE | CHAR | 1 | PVS_OTYPE | ||||
PGUID | Internal Identification for PVS Objects | PVS_GUID | RAW | 16 | PNODID | SYSUUID | |||
ALTNUM | Alternative of an iPPE Node | PVS_ALTNUM | CHAR | 2 | ALPHA | PVS_ALTNR | ALTN | ||
PATYPE | iPPE Alternative Type | PVS_PALT_TYPE | CHAR | 8 | CPATYPE | PVS_PALT_TYPE | |||
APPLOBJ_TYPE | iPPE Application Object Type | PPE_APPLOBJ_TYPE | CHAR | 4 | CHAR4 | ||||
TIMSTMP | UTC Time Stamp in Long Form (YYYYMMDDhhmmss,mmmuuun) | PVS_TIMSTMP | DEC | 21(7) | TZNTSTMPL | ||||
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 | ||
DBOP | Update indicator | PVS_DBOP | CHAR | 1 | PVS_VERBUCHER |
Key field | Non-key field |
How do I retrieve data from SAP structure PALTID_DB using ABAP code?
As PALTID_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 PALTID_DB as there is no data to select.How to access SAP table PALTID_DB
Within an ECC or HANA version of SAP you can also view further information about PALTID_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