PINPESA SAP (P2E: Structure for Policy data Save) Structure details
Description: P2E: Structure for Policy data Save
Structure field list including key, data, relationships and ABAP select examples
PINPESA 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 Policy data Save" 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_PINPESA TYPE PINPESA.
The PINPESA table consists of various fields, each holding specific information or linking keys about P2E: Structure for Policy data Save data available in SAP. These include MANDT (Client), POGUI (Policy Guid), VERSN (Policy Version), 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 PINPESA 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 | |||
POGUI | Policy Guid | PIN_PE_POLICY_GUID | CHAR | 22 | SYSUUID_22 | ||||
VERSN | Policy Version | PIN_PE_VERSION | NUMC | 4 | NUMC04 | ||||
BEGDA | Start Date | BEGDA | DATS | 8 | DATUM | ||||
ENDDA | End Date | ENDDA | DATS | 8 | DATUM | ||||
POLID | P2E: Policy ID | PIN_PE_POLID | CHAR | 8 | Assigned to domain | PIN_PE_POLID | |||
DESCR | Description | PIN_PE_DESCRIP | CHAR | 60 | PIN_PE_DESCRIP | ||||
AREKY | Area Key | PIN_PE_AREA_KEY | CHAR | 5 | Assigned to domain | PIN_PE_AREA_KEY | |||
ARDES | Description | PIN_PE_DESCRIP | CHAR | 60 | PIN_PE_DESCRIP | ||||
POCST | P2E: Policy Cost | PIN_PE_COST | CURR | 18(2) | PIN_PE_COST | ||||
WAERS | Currency Key | WAERS | CUKY | 5 | Assigned to domain | WAERS | FWS | ||
GRPID | Policy Group | PIN_PE_POL_GRPID | CHAR | 3 | Assigned to domain | PIN_PE_POL_GRPID | |||
GRDES | Description | PIN_PE_DESCRIP | CHAR | 60 | PIN_PE_DESCRIP | ||||
INITI | P2E: Policy Initiator | PIN_PE_INITIATOR | CHAR | 1 | PIN_PE_INITIATOR | ||||
INDES | Description | PIN_PE_DESCRIP | CHAR | 60 | PIN_PE_DESCRIP | ||||
FREQU | P2E: Request Frequency | PIN_PE_FREQUENCY | CHAR | 2 | PIN_PE_FREQUENCY | ||||
FRDES | Description | PIN_PE_DESCRIP | CHAR | 60 | PIN_PE_DESCRIP | ||||
POTYP | Policy Type | PIN_PE_POL_TYPE | CHAR | 3 | Assigned to domain | PIN_PE_POL_TYPE | |||
TYDES | Description | PIN_PE_DESCRIP | CHAR | 60 | PIN_PE_DESCRIP | ||||
POSTS | P2E: Policy Status | PIN_PE_POL_STATUS | CHAR | 2 | PIN_PE_POL_STATUS | ||||
STDES | Description | PIN_PE_DESCRIP | CHAR | 60 | PIN_PE_DESCRIP | ||||
PACTI | Policy activity | PIN_PE_POLICY_ACTIVITY | CHAR | 2 | PIN_PE_POLICY_ACTIVITY | ||||
TMPID | Policy Request Template | PIN_PE_TEMPLATE | CHAR | 5 | PIN_PE_TEMPLATE | ||||
TMDES | Description | PIN_PE_DESCRIP | CHAR | 60 | PIN_PE_DESCRIP | ||||
ORDOC | P2E: Attachment ID | PIN_PE_ATTACHMENT_ID | CHAR | 25 | Assigned to domain | ALPHA | DOKNR | ||
MODOC | P2E: Attachment ID | PIN_PE_ATTACHMENT_ID | CHAR | 25 | Assigned to domain | ALPHA | DOKNR | ||
NOELG | Number of Eligible employee for policy | PIN_PE_NOELG | NUMC | 16 | PIN_PE_NOELG | ||||
RUNON | Date | DATUM | DATS | 8 | DATUM | ||||
ISLST | Is latest Record Indicator | PIN_PE_ISLST | CHAR | 1 | PIN_PE_ISLST | ||||
CREBY | User Name in User Master Record | XUBNAME | CHAR | 12 | Assigned to domain | XUBNAME | XUS | ||
CREON | P2E: Date and Time | PIN_PE_CTIME | DEC | 15 | TSTPS | PIN_PE_CTIME | |||
CHABY | User Name in User Master Record | XUBNAME | CHAR | 12 | Assigned to domain | XUBNAME | XUS | ||
CHAON | P2E: Date and Time | PIN_PE_CTIME | DEC | 15 | TSTPS | PIN_PE_CTIME | |||
SPRAS | Language Key | SPRAS | LANG | 1 | Assigned to domain | ISOLA | SPRAS | SPR | H_T002 |
STPDT | 0 | ||||||||
RESE1 | Reserved Field of Length 10 | PIN_PE_RESERVED | CHAR | 10 | PIN_PE_RESERVED | ||||
VALDA | 0 | ||||||||
DECSI | 0 | ||||||||
APPDA | 0 | ||||||||
CLODA | 0 | ||||||||
CLOVA | 0 |
Key field | Non-key field |
How do I retrieve data from SAP structure PINPESA using ABAP code?
As PINPESA 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 PINPESA as there is no data to select.How to access SAP table PINPESA
Within an ECC or HANA version of SAP you can also view further information about PINPESA 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