PHIN_S_PHINT SAP (Table Line of Phint) Structure details
Dictionary Type: Structure
Description: Table Line of Phint
Description: Table Line of Phint
Structure field list including key, data, relationships and ABAP select examples
PHIN_S_PHINT 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 "Table Line of Phint" 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_S_PHINT TYPE PHIN_S_PHINT.
The PHIN_S_PHINT table consists of various fields, each holding specific information or linking keys about Table Line of Phint data available in SAP. These include MANDT (Client), PHIN_GUID (Generic Key for Takeover/Handover), TL_KEY (Key (Numc 8) for Table PHINT), KTX01 (Description of technical object).. 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 PHIN_S_PHINT 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 | ||||
| KTX01 | Description of technical object | KTX01 | CHAR | 40 | TEXT40 | ||||
| QUANT | Quantity | PHIN_D_QTY | QUAN | 13(3) | MENGV13 | ||||
| QUNIT | Unit of Measure | PHIN_D_QUNIT | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
| IDATE | Installation Date (UTC Timestamp) | PHIN_D_ID_TSTAMP | DEC | 15 | TZNTSTMPS | ||||
| BAUJJ | Year of construction | BAUJJ | CHAR | 4 | GJAHR | CJAHR | |||
| BAUMM | Month of Construction | PHIN_D_BAUMM | CHAR | 2 | PHIN_DOM_BAUMM | ||||
| PHIN_LOC | Additional Information (Example: ATA) | PHIN_D_LOC | CHAR | 30 | PHIN_DOM_LOC | ||||
| DOCNUM | IDoc number | EDI_DOCNUM | NUMC | 16 | EDI_DOCNUM | DCN | |||
| EXTEQUI | External Equipment Number | PHIN_D_EXTEQUI | CHAR | 30 | CHAR30 | ||||
| H_EXTEQUI | Superior External Equipment Number | PHIN_D_HEXTEQUI | CHAR | 30 | CHAR30 | ||||
| TO_TYP | Type Takeover / Handover Object | PHIN_D_TYPE | CHAR | 1 | PHIN_DOM_TOTYPE | ||||
| DD_TSTAMP | Dismantle Date (UTC Timestamp) | PHIN_D_DD_TSTAMP | DEC | 15 | TZNTSTMPS | ||||
| FUNCID | FID (Function Identifier) | PHIN_D_FUNCID | CHAR | 40 | CHAR40 | ||||
| VALID_ON | Valid Date | PHIN_D_VALID_DATE | DATS | 8 | DATUM | ||||
| EQUNR | Equipment Number | EQUNR | CHAR | 18 | Assigned to domain | ALPHA | EQUNR | EQN | EQUI |
| MATNR | Material Number | MATNR | CHAR | 18 | Assigned to domain | MATN1 | MATNR | MAT | S_MAT1 |
| SERNR | Serial Number | GERNR | CHAR | 18 | GERNR | GERNR | SER | ||
| REF_EQUNR | 'Copy Reference' for Equipment | PHIN_D_REFE | CHAR | 18 | Assigned to domain | ALPHA | EQUNR | EQUI | |
| HEQUI | Superordinate Equipment | HEQUI | CHAR | 18 | Assigned to domain | ALPHA | EQUNR | ||
| TPLNR | Functional Location | PHIN_D_TPLNR40 | CHAR | 40 | ILOM_STRNO | IFL | |||
| TPLMA | Superior Functional location | PHIN_D_TPLMA40 | CHAR | 40 | ILOM_STRNO | ||||
| H_TL_KEY | Table Line Key of Superior Object | PHIN_D_HGUID | NUMC | 8 | PHIN_DOM_GUID | ||||
| TMPL_FL | 'Copy Reference' for Functional Location | PHIN_D_TMPLFL40 | CHAR | 40 | ILOM_STRNO | ||||
| NEW_H_TL_KEY | Table Line Key of Superior Object | PHIN_D_HGUID | NUMC | 8 | PHIN_DOM_GUID | ||||
| NH_MATNR | Superior Mat. Number | PHIN_D_NH_MATNR | CHAR | 18 | Assigned to domain | MATN1 | MATNR | ||
| NH_SERNR | Superior Serial Number | PHIN_D_NH_SERNR | CHAR | 18 | GERNR | GERNR | |||
| PARTNER_MATNR | Material number used by the business partner | PHIN_D_PARTNER_MATNR | CHAR | 40 | CHAR40 | ||||
| RECENT_MATNR | Material Number Used During Last Takeover | PHIN_D_RECENT_MATNR | CHAR | 40 | CHAR40 | ||||
| UII | Unique Item Identifier | PHIN_D_UII | CHAR | 72 | UII_CHAR72 | UII | H_UII | ||
| MD_TSN_TSTAMP | Time Since New: Measurement Date (UTC Timestamp) | PHIN_D_MD_TSN_TZNTSTMPS | DEC | 15 | TZNTSTMPS | ||||
| MD_TSN | Time Since New | PHIN_D_MD_TSN | CHAR | 22 | FLTP_INOUT | ||||
| MD_CSN_TSTAMP | Cycles Since New: Measurement Date (UTC Timestamp) | PHIN_D_MD_CSN_TZNTSTMPS | DEC | 15 | TZNTSTMPS | ||||
| MD_CSN | Cycles Since New | PHIN_D_MD_CSN | CHAR | 22 | FLTP_INOUT | ||||
| MD_DISN_TSTAMP | Days Installed Since New: Measurement Date (UTC Timestamp) | PHIN_D_MD_DISN_TZNTSTMPS | DEC | 15 | TZNTSTMPS | ||||
| MD_DISN | Days Installed Since New | PHIN_D_MD_DISN | CHAR | 22 | FLTP_INOUT | ||||
| MD_TSO_TSTAMP | Time Since Overhaul: Measurement Date (UTC Timestamp) | PHIN_D_MD_TSO_TZNTSTMPS | DEC | 15 | TZNTSTMPS | ||||
| MD_TSO | Time Since Overhaul | PHIN_D_MD_TSO | CHAR | 22 | FLTP_INOUT | ||||
| MD_CSO_TSTAMP | Cycles Since Overhaul: Measurement Date (UTC Timestamp) | PHIN_D_MD_CSO_TZNTSTMPS | DEC | 15 | TZNTSTMPS | ||||
| MD_CSO | Cycles Since Overhaul | PHIN_D_MD_CSO | CHAR | 22 | FLTP_INOUT | ||||
| MD_DISO_TSTAMP | Days Installed Since Overhaul: MeasuremDate (UTC Timestamp) | PHIN_D_MD_DISO_TZNTSTMPS | DEC | 15 | TZNTSTMPS | ||||
| MD_DISO | Days Installed Since Overhaul | PHIN_D_MD_DISO | CHAR | 22 | FLTP_INOUT | ||||
| MD_TSR_TSTAMP | Time Since Repair: Measurement Date (UTC Timestamp) | PHIN_D_MD_TSR_TZNTSTMPS | DEC | 15 | TZNTSTMPS | ||||
| MD_TSR | Time Since Repair | PHIN_D_MD_TSR | CHAR | 22 | FLTP_INOUT | ||||
| MD_CSR_TSTAMP | Cycles Since Repair: Measurement Date (UTC Timestamp) | PHIN_D_MD_CSR_TZNTSTMPS | DEC | 15 | TZNTSTMPS | ||||
| MD_CSR | Cycles Since Repair | PHIN_D_MD_CSR | CHAR | 22 | FLTP_INOUT | ||||
| MD_DISR_TSTAMP | Days Installed Since Repair: MeasuremDate (UTC Timestamp) | PHIN_D_MD_DISR_TZNTSTMPS | DEC | 15 | TZNTSTMPS | ||||
| MD_DISR | Days Installed Since Repair | PHIN_D_MD_DISR | CHAR | 22 | FLTP_INOUT | ||||
| IND_DEL | Deletion Indicator | PHIN_D_DEL | CHAR | 1 | PHIN_DOM_DEL | ||||
| SOURCE | Takeover / Handover: Source Indicator | PHIN_D_SOURCE | CHAR | 1 | PHIN_DOM_SOURCE | ||||
| EQCAT | Technical Object Category | PHIN_D_EQTYP | CHAR | 1 | PHIN_DOM_EQTYP | ||||
| FLOCDELIND | Deletion Indicator | PHIN_D_DEL | CHAR | 1 | PHIN_DOM_DEL | ||||
| OBJ_LEVEL | Level in Object Structure | PHIN_D_LEVEL | INT1 | 3 | |||||
| TPLKZ | Functional location structure indicator | TPLKZ | CHAR | 5 | Assigned to domain | TPLKZ | ISR | ||
| STAT_CONS | Takeover State Consistency | PHIN_D_STATE_CONS | CHAR | 1 | CHAR1 | ||||
| STAT_EXIST | Takeover State Existence | PHIN_D_STATE_EXIST | CHAR | 1 | CHAR1 | ||||
| STAT_CREATED | Takeover State Object Created | PHIN_D_STATE_CREATE | CHAR | 1 | CHAR1 | ||||
| STAT_UPDATED | Takeover State Updated | PHIN_D_STATE_UPDATE | CHAR | 1 | CHAR1 | ||||
| STAT_FLOC | Takeover / Handover State Functional Location Assignment | PHIN_D_STATE_FLOC | CHAR | 1 | CHAR1 |
| Key field | Non-key field |
How do I retrieve data from SAP structure PHIN_S_PHINT using ABAP code?
As PHIN_S_PHINT 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_S_PHINT as there is no data to select.How to access SAP table PHIN_S_PHINT
Within an ECC or HANA version of SAP you can also view further information about PHIN_S_PHINT 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