PHIN_S_GDT SAP (Handover/Takeover Data Exchange Structure with GDTs) Structure details
Description: Handover/Takeover Data Exchange Structure with GDTs
Structure field list including key, data, relationships and ABAP select examples
PHIN_S_GDT 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 "Handover/Takeover Data Exchange Structure with GDTs" 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_GDT TYPE PHIN_S_GDT.
The PHIN_S_GDT table consists of various fields, each holding specific information or linking keys about Handover/Takeover Data Exchange Structure with GDTs data available in SAP. These include INDIVIDUALMATERIALID (Equipment Number), LANGUAGE (Language Key), INSTALLATIONPOINTDESCRIPTION (Description of functional location), INDIVIDUALMATERIALDESCRIPTION (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_GDT 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 |
INSTALLATIONPOINTID | Functional Location | PHIN_D_TPLNR40 | CHAR | 40 | ILOM_STRNO | IFL | |||
INDIVIDUALMATERIALID | Equipment Number | EQUNR | CHAR | 18 | Assigned to domain | ALPHA | EQUNR | EQN | EQUI |
LANGUAGE | Language Key | SPRAS | LANG | 1 | Assigned to domain | ISOLA | SPRAS | SPR | H_T002 |
INSTALLATIONPOINTDESCRIPTION | Description of functional location | PLTXT | CHAR | 40 | TEXT40 | ||||
INDIVIDUALMATERIALDESCRIPTION | Description of technical object | KTX01 | CHAR | 40 | TEXT40 | ||||
PRODUCTDESCRIPTION | Material Description (Short Text) | MAKTX | CHAR | 40 | TEXT40 | ||||
INSTALLATIONPOINTCATEGORYCODE | Functional location structure indicator | TPLKZ | CHAR | 5 | Assigned to domain | TPLKZ | ISR | ||
INDIVIDUALMATERIALCATEGORYCODE | Equipment category | EQTYP | CHAR | 1 | Assigned to domain | EQTYP | EQT | ||
LOCATIONID | Additional Information (Example: ATA) | PHIN_D_LOC | CHAR | 30 | PHIN_DOM_LOC | ||||
IEQUI | Installation of equipment allowed at the functional location | IEQUI | CHAR | 1 | X | ||||
SUPERIORINSTALLATIONPOINTID | Superior functional location | TPLMA | CHAR | 30 | Assigned to domain | TPLNR | TPLNR | IFLM | |
SUPERIORINDIVIDUALMATERIALID | Superordinate Equipment | HEQUI | CHAR | 18 | Assigned to domain | ALPHA | EQUNR | ||
INSTALLATIONDATE | Installation Date (UTC Timestamp) | PHIN_D_ID_TSTAMP | DEC | 15 | TZNTSTMPS | ||||
INSTALLATIONPOSITIONID | Position in superior technical object | ILOM_POSNR | CHAR | 4 | CHAR4 | ||||
MANUFACTURERPRODUCTID | Manufacturer Part Number | MFRPN | CHAR | 40 | CHAR40 | ||||
MANUFACTURERSERIALID | Manufacturer serial number | SERGE | CHAR | 30 | CHAR30 | ||||
SUBMT | Construction type material of the object | SUBMT | CHAR | 18 | Assigned to domain | MATN1 | MATNR | MAT | |
PRODUCTID | Material Number | MATNR | CHAR | 18 | Assigned to domain | MATN1 | MATNR | MAT | S_MAT1 |
SERIALID | Serial Number | GERNR | CHAR | 18 | GERNR | GERNR | SER | ||
KMATN | Configurable Material | KMATN | CHAR | 18 | Assigned to domain | MATN1 | MATNR | MAT1 | |
CONSTRUCTIONYEAR | Year of construction | BAUJJ | CHAR | 4 | GJAHR | CJAHR | |||
CONSTRUCTIONMONTH | Month of construction | BAUMM | CHAR | 2 | BAUMM | ||||
QUANTITY | Quantity | PHIN_D_QTY | QUAN | 13(3) | MENGV13 | ||||
MEASUREUNITCODE | Unit of Measure | PHIN_D_QUNIT | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
TIMESINCENEW_VALUE | Time Since New | PHIN_D_MD_TSN | CHAR | 22 | FLTP_INOUT | ||||
TIMESINCENEW_DATE | Time Since New: Measurement Date (UTC Timestamp) | PHIN_D_MD_TSN_TZNTSTMPS | DEC | 15 | TZNTSTMPS | ||||
CYCLESSINCENEW_VALUE | Cycles Since New | PHIN_D_MD_CSN | CHAR | 22 | FLTP_INOUT | ||||
CYCLESSINCENEW_DATE | Cycles Since New: Measurement Date (UTC Timestamp) | PHIN_D_MD_CSN_TZNTSTMPS | DEC | 15 | TZNTSTMPS | ||||
DAYSSINCENEW_VALUE | Days Installed Since New | PHIN_D_MD_DISN | CHAR | 22 | FLTP_INOUT | ||||
DAYSSINCENEW_DATE | Days Installed Since New: Measurement Date (UTC Timestamp) | PHIN_D_MD_DISN_TZNTSTMPS | DEC | 15 | TZNTSTMPS | ||||
TIMESINCEOVERHAUL_VALUE | Time Since Overhaul | PHIN_D_MD_TSO | CHAR | 22 | FLTP_INOUT | ||||
TIMESINCEOVERHAUL_DATE | Time Since Overhaul: Measurement Date (UTC Timestamp) | PHIN_D_MD_TSO_TZNTSTMPS | DEC | 15 | TZNTSTMPS | ||||
CYCLESSINCEOVERHAUL_VALUE | Time Since Overhaul | PHIN_D_MD_TSO | CHAR | 22 | FLTP_INOUT | ||||
CYCLESSINCEOVERHAUL_DATE | Time Since Overhaul: Measurement Date (UTC Timestamp) | PHIN_D_MD_TSO_TZNTSTMPS | DEC | 15 | TZNTSTMPS | ||||
DAYSSINCEOVERHAUL_VALUE | Days Installed Since Overhaul | PHIN_D_MD_DISO | CHAR | 22 | FLTP_INOUT | ||||
DAYSSINCEOVERHAUL_DATE | Days Installed Since Overhaul: MeasuremDate (UTC Timestamp) | PHIN_D_MD_DISO_TZNTSTMPS | DEC | 15 | TZNTSTMPS | ||||
TIMESINCEREPAIR_VALUE | Time Since Repair | PHIN_D_MD_TSR | CHAR | 22 | FLTP_INOUT | ||||
TIMESINCEREPAIR_DATE | Time Since Repair: Measurement Date (UTC Timestamp) | PHIN_D_MD_TSR_TZNTSTMPS | DEC | 15 | TZNTSTMPS | ||||
CYCLESSINCEREPAIR_VALUE | Cycles Since Repair | PHIN_D_MD_CSR | CHAR | 22 | FLTP_INOUT | ||||
CYCLESSINCEREPAIR_DATE | Cycles Since Repair: Measurement Date (UTC Timestamp) | PHIN_D_MD_CSR_TZNTSTMPS | DEC | 15 | TZNTSTMPS | ||||
DAYSSINCEREPAIR_VALUE | Days Installed Since Repair | PHIN_D_MD_DISR | CHAR | 22 | FLTP_INOUT | ||||
DAYSSINCEREPAIR_DATE | Days Installed Since Repair: MeasuremDate (UTC Timestamp) | PHIN_D_MD_DISR_TZNTSTMPS | DEC | 15 | TZNTSTMPS |
Key field | Non-key field |
How do I retrieve data from SAP structure PHIN_S_GDT using ABAP code?
As PHIN_S_GDT 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_GDT as there is no data to select.How to access SAP table PHIN_S_GDT
Within an ECC or HANA version of SAP you can also view further information about PHIN_S_GDT 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