PINPES5 SAP (Structure for t7inpes5) Structure details
Description: Structure for t7inpes5
Structure field list including key, data, relationships and ABAP select examples
PINPES5 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 "Structure for t7inpes5" 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_PINPES5 TYPE PINPES5.
The PINPES5 table consists of various fields, each holding specific information or linking keys about Structure for t7inpes5 data available in SAP. These include CSFLD (Screen Field for table S5), TBFLD (Screen Field for Multiline Content), ENDDA (End Date), BEGDA (Start Date).. 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 PINPES5 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 |
| TMPID | Policy Request Template | PIN_PE_TEMPLATE | CHAR | 5 | PIN_PE_TEMPLATE | ||||
| CSFLD | Screen Field for table S5 | PIN_PE_HCUS_FLD5 | CHAR | 30 | CHAR30 | HRPADINS5 | |||
| TBFLD | Screen Field for Multiline Content | PIN_PE_HCUS_MLC_FLD | CHAR | 30 | CHAR30 | HRPADINS_MLC | |||
| ENDDA | End Date | ENDDA | DATS | 8 | DATUM | ||||
| BEGDA | Start Date | BEGDA | DATS | 8 | DATUM | ||||
| FLDVT | Field Type for screen | PIN_PE_FIELD_VIEW_TYP | CHAR | 2 | PIN_PE_FIELD_VIEW_TYP | ||||
| WIDTH | Width of the field on Screen | PIN_PE_WIDTH | NUMC | 3 | NUMC3 | ||||
| IVREQ | Field Visible To Request Screen | PIN_PE_IS_VISIBLE_REQ | CHAR | 1 | XFELD | ||||
| IEREQ | Field Enabled For Request | PIN_PE_IS_ENABLE_REQ | CHAR | 1 | XFELD | ||||
| ROREQ | Read-only for Request Screen | PIN_PE_IS_READONLY_REQ | CHAR | 1 | XFELD | ||||
| MNDRQ | Mandatory | PIN_PE_IS_MANDATORY | CHAR | 1 | XFELD | ||||
| IVAPP | Visibility to Approver | PIN_PE_IS_VISIBLE_APP | CHAR | 1 | XFELD | ||||
| IEAPP | Field Is Enabled For Approver | PIN_PE_IS_ENABLE_APP | CHAR | 1 | XFELD | ||||
| ROAPP | Read-only field for Approver Screen | PIN_PE_IS_READONLY_APP | CHAR | 1 | XFELD | ||||
| MNDAP | Mandatory | PIN_PE_IS_MANDATORY | CHAR | 1 | XFELD | ||||
| FLDOR | Order Of The Fields On Screen | PIN_PE_FIELD_ORDER | NUMC | 2 | NUMC2 | ||||
| FEACT | P2E: Action Name for Front End | PIN_PE_FE_ACTION | CHAR | 20 | CHAR20 | ||||
| DFVAL | Default Value for Field | PIN_PE_DFVAL | CHAR | 255 | PIN_PE_DFVAL | ||||
| CLNME | Object Type Name | SEOCLSNAME | CHAR | 30 | SEOCLSNAME | CLASS | |||
| MENME | Method name | SEOMTDNAME | CHAR | 61 | CHAR61 | MTDNAME |
| Key field | Non-key field |
How do I retrieve data from SAP structure PINPES5 using ABAP code?
As PINPES5 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 PINPES5 as there is no data to select.How to access SAP table PINPES5
Within an ECC or HANA version of SAP you can also view further information about PINPES5 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