PINPEV10 SAP (P2E: Structure for Validation view) Structure details
Description: P2E: Structure for Validation view
Structure field list including key, data, relationships and ABAP select examples
PINPEV10 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 Validation view" 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_PINPEV10 TYPE PINPEV10.
The PINPEV10 table consists of various fields, each holding specific information or linking keys about P2E: Structure for Validation view data available in SAP. These include STPID (Policy Step ID), STDES (Description), 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: Can Be Enhanced (Deep)
SAP PINPEV10 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 |
| POGUI | Policy Guid | PIN_PE_POLICY_GUID | CHAR | 22 | SYSUUID_22 | ||||
| STPID | Policy Step ID | PIN_PE_STEPID | CHAR | 8 | PIN_PE_STEPID | ||||
| STDES | Description | PIN_PE_DESCRIP | CHAR | 60 | PIN_PE_DESCRIP | ||||
| ENDDA | End Date | ENDDA | DATS | 8 | DATUM | ||||
| BEGDA | Start Date | BEGDA | DATS | 8 | DATUM | ||||
| ATRID | Validation Attribute | PIN_PE_ATTRIB_ID | CHAR | 6 | Assigned to domain | PIN_PE_ATTRIB_ID | |||
| ATDES | Description | PIN_PE_DESCRIP | CHAR | 60 | PIN_PE_DESCRIP | ||||
| UNIT | P2E: Unit | PIN_PE_UNIT | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
| ANDOR | P2E: AND/OR Condition | PIN_PE_ANDOR | CHAR | 1 | PIN_PE_ANDOR | ||||
| XINDI | Mandate Check | PIN_PE_TFINDICATOR | CHAR | 1 | PIN_PE_TFINDICATOR | ||||
| PNODE | Validation Attribute | PIN_PE_ATTRIB_ID | CHAR | 6 | Assigned to domain | PIN_PE_ATTRIB_ID | |||
| ATSEQ | Sequence Number | PIN_PE_SEQNUM | NUMC | 3 | PIN_PE_SEQNUM | ||||
| VDATA | 0 | ||||||||
| DELNA | Data Element Name | PIN_PE_DATAELEMENT_NAME | CHAR | 30 | CHAR30 | ||||
| LINAT | Validation Attribute | PIN_PE_ATTRIB_ID | CHAR | 6 | Assigned to domain | PIN_PE_ATTRIB_ID | |||
| TSIGN | P2E: Include Exclude Indicator | PIN_PE_IE_INDIC | CHAR | 1 | PIN_PE_IE_INDIC | ||||
| TOPTY | P2E : Operation Type | PIN_PE_OPT_TYPE | CHAR | 2 | PIN_PE_OPT_TYPE |
| Key field | Non-key field |
How do I retrieve data from SAP structure PINPEV10 using ABAP code?
As PINPEV10 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 PINPEV10 as there is no data to select.How to access SAP table PINPEV10
Within an ECC or HANA version of SAP you can also view further information about PINPEV10 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