PINPER2 SAP (P2E: Structure for request UI config data) Structure details
Description: P2E: Structure for request UI config data
Structure field list including key, data, relationships and ABAP select examples
PINPER2 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 "P2E: Structure for request UI config data" 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_PINPER2 TYPE PINPER2.
The PINPER2 table consists of various fields, each holding specific information or linking keys about P2E: Structure for request UI config data data available in SAP. These include CSFLD (Screen Field), ENDDA (End Date), BEGDA (Start Date), MNDTR (Mandatory).. 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 PINPER2 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 | PIN_PE_HCUS_FLD | CHAR | 30 | CHAR30 | HRPADINS | |||
| ENDDA | End Date | ENDDA | DATS | 8 | DATUM | ||||
| BEGDA | Start Date | BEGDA | DATS | 8 | DATUM | ||||
| MNDTR | Mandatory | PIN_PE_IS_MANDATORY | CHAR | 1 | XFELD | ||||
| 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 | ||||
| UIPOS | Position of Field | PIN_PE_POSITION | CHAR | 2 | PIN_PE_POSITION | ||||
| IVPOL | Visibility on Policy Screen | PIN_PE_IS_VISIBLE_POLICY | CHAR | 1 | XFELD | ||||
| IEPOL | Field Enabled For Policy Screen | PIN_PE_IS_ENABLE_POLICY | CHAR | 1 | XFELD | ||||
| ROPOL | Read-only field for Policy Screen | PIN_PE_IS_READONLY_POLICY | CHAR | 1 | XFELD | ||||
| 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 | ||||
| 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 | |||
| CFLBL | Field Label | PIN_PE_FLD_LABEL | CHAR | 40 | PIN_PE_FLD_LABEL | ||||
| TLTIP | Information Text | PIN_PE_TOOL_TIP | CHAR | 200 | PIN_PE_TOOL_TIP | ||||
| DCLNE | Object Type Name | SEOCLSNAME | CHAR | 30 | SEOCLSNAME | CLASS | |||
| DMENE | Method name | SEOMTDNAME | CHAR | 61 | CHAR61 | MTDNAME |
| Key field | Non-key field |
How do I retrieve data from SAP structure PINPER2 using ABAP code?
As PINPER2 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 PINPER2 as there is no data to select.How to access SAP table PINPER2
Within an ECC or HANA version of SAP you can also view further information about PINPER2 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