PP0N SAP (Parameter String for Creating a Scenario Group) Structure details
Description: Parameter String for Creating a Scenario Group
Structure field list including key, data, relationships and ABAP select examples
PP0N 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 "Parameter String for Creating a Scenario Group" 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_PP0N TYPE PP0N.
The PP0N table consists of various fields, each holding specific information or linking keys about Parameter String for Creating a Scenario Group data available in SAP. These include VERSN (Version Number (Plan Scenario = Plan Version + Version No.)), BEGDA (Start Date for Planning Period), ENDDA (End Date of Planning Period), VNAME ((Cost) scenario group - Subdivision of a plan scenario).. 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 PP0N 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 |
| PLVAR | Plan Version | PLVAR | CHAR | 2 | T778P | PLVAR | POP | ||
| VERSN | Version Number (Plan Scenario = Plan Version + Version No.) | HR_VERSN | CHAR | 2 | T77KD | HR_VERSN | |||
| BEGDA | Start Date for Planning Period | HR_PC_BEG | DATS | 8 | DATUM | ||||
| ENDDA | End Date of Planning Period | HR_PC_END | DATS | 8 | DATUM | ||||
| VNAME | (Cost) scenario group - Subdivision of a plan scenario | HR_VNAME | CHAR | 12 | HR_VNAME | ||||
| ACTIV | Take organizational changes into account (activate) | HR_PC_ACT | CHAR | 1 | CHAR1_X | ||||
| DEPTH | Depth of organizational structure | HR_PC_DPT | DEC | 5 | DEC5 | ||||
| ABART | Personnel Cost Projection Period | HR_PC_ABT | CHAR | 1 | T546T | ABRAR | |||
| CURCY | Currency Key | HR_CURCY | CUKY | 5 | TCURC | WAERS | FWS | ||
| CURTP | Exchange rate type for currency conversion | HR_CURTYPE | CHAR | 4 | TCURV | KURST | |||
| CURDT | Date for currency conversion | HR_CURDATE | DATS | 8 | DATUM | ||||
| SUBTY | Salary Surveys (Subtype) | HR_PC_SUBT | CHAR | 4 | T778U | SUBTYP | |||
| SHFLG | Use object abbreviations only (no long texts) | HR_PC_SHT | CHAR | 1 | CHAR1_X | ||||
| VIEW_OBJ | Cost and object view | HR_PC_SEL | CHAR | 1 | CHAR1_X | ||||
| VIEW_POS | Cost and object view | HR_PC_SEL | CHAR | 1 | CHAR1_X | ||||
| VIEW_PER | Cost and object view | HR_PC_SEL | CHAR | 1 | CHAR1_X | ||||
| PROJ_FLG | Use projected pay | PC_M_PROJ | CHAR | 1 | CHAR1_X | ||||
| PREL_FLG | Use basic pay | PC_M_BASIC | CHAR | 1 | CHAR1_X | ||||
| PAYR_FLG | Use payroll results | PC_M_PAYR | CHAR | 1 | CHAR1_X | ||||
| PY_BEGDA | Start Date of Payroll Result Period | HR_PY_BEG | DATS | 8 | DATUM | ||||
| PY_ENDDA | End Date of Payroll Result Period | HR_PY_END | DATS | 8 | DATUM | ||||
| PCSAVE | Save scenario group | HR_PC_SAVE | CHAR | 1 | CHAR1_X | ||||
| VTEXT | Plan scenario name | HR_BEZTXT | CHAR | 25 | TEXT25 | ||||
| PWD | Password for scenario group to be stored | HR_PWD | CHAR | 12 | CHAR12 | ||||
| CALCT | Calculation mode in personnel cost planning | HR_PC_CALC | CHAR | 1 | CHAR1_X |
| Key field | Non-key field |
How do I retrieve data from SAP structure PP0N using ABAP code?
As PP0N 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 PP0N as there is no data to select.How to access SAP table PP0N
Within an ECC or HANA version of SAP you can also view further information about PP0N 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