PHIN_T_MSG_PI SAP (Phin Message Table Structure including Posting Indicator) Structure details
Description: Phin Message Table Structure including Posting Indicator
Related tables to PHIN_T_MSG_PI
Access table PHIN_T_MSG_PI
Structure field list including key, data, relationships and ABAP select examples
PHIN_T_MSG_PI 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 "Phin Message Table Structure including Posting Indicator" 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_PHIN_T_MSG_PI TYPE PHIN_T_MSG_PI.
The PHIN_T_MSG_PI table consists of various fields, each holding specific information or linking keys about Phin Message Table Structure including Posting Indicator data available in SAP. These include MANDT (Client), PHIN_GUID (Generic Key for Takeover/Handover), TL_KEY (Key (Numc 8) for Table PHINT), MSGID (Message Class).. 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 (Deep)
SAP PHIN_T_MSG_PI 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 | |||
| PHIN_GUID | Generic Key for Takeover/Handover | PHIN_D_PHINGUID | CHAR | 32 | SDOK_DOCID | ||||
| TL_KEY | Key (Numc 8) for Table PHINT | PHIN_D_GUID | NUMC | 8 | PHIN_DOM_GUID | ||||
| MSGID | Message Class | SYMSGID | CHAR | 20 | Assigned to domain | ARBGB | |||
| MSGNO | Message Number | SYMSGNO | NUMC | 3 | SYMSGNO | ||||
| TIMESTAMP | UTC Time Stamp in Long Form (YYYYMMDDhhmmssmmmuuun) | TIMESTAMPL | DEC | 21(7) | TZNTSTMPL | ||||
| MSGTY | Message Type | SYMSGTY | CHAR | 1 | SYCHAR01 | ||||
| MSGV1 | Message Variable | SYMSGV | CHAR | 50 | SYCHAR50 | ||||
| MSGV2 | Message Variable | SYMSGV | CHAR | 50 | SYCHAR50 | ||||
| MSGV3 | Message Variable | SYMSGV | CHAR | 50 | SYCHAR50 | ||||
| MSGV4 | Message Variable | SYMSGV | CHAR | 50 | SYCHAR50 | ||||
| CONTEXT | Message Variable | SYMSGV | CHAR | 50 | SYCHAR50 | ||||
| VBKZ | Takeover / Handover Update Indicator | PHIN_VBKZ | CHAR | 1 | PHIN_VBKZ | ||||
| PHIN_VIEW | PHIN_MSG_VIEW | PHIN_MSG_VIEW | CHAR | 2 | PHIN_MSG_VIEW | ||||
| FUNCTION | PHIN_MSG_FUNCTION | PHIN_MSG_FUNCTION | CHAR | 2 | PHIN_MSG_FUNCTION | ||||
| OBJNR | Object number | J_OBJNR | CHAR | 22 | Assigned to domain | J_OBJNR | ONR | ||
| CAT_ERROR | PHIN_MSG_CAT | PHIN_MSG_CAT | CHAR | 1 | PHIN_MSG_CAT | ||||
| CHG_FLAG | Change Indicator for Takeover / Handover Object | PHIN_D_CHGFLAG | CHAR | 1 | PHIN_DOM_CHGFLAG |
| Key field | Non-key field |
How do I retrieve data from SAP structure PHIN_T_MSG_PI using ABAP code?
As PHIN_T_MSG_PI 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 PHIN_T_MSG_PI as there is no data to select.How to access SAP table PHIN_T_MSG_PI
Within an ECC or HANA version of SAP you can also view further information about PHIN_T_MSG_PI 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