PPCAD SAP (Personnel Cost Planning: Admin.Data for Scenario Group) Structure details
Description: Personnel Cost Planning: Admin.Data for Scenario Group
Structure field list including key, data, relationships and ABAP select examples
PPCAD 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 "Personnel Cost Planning: Admin.Data for 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_PPCAD TYPE PPCAD.
The PPCAD table consists of various fields, each holding specific information or linking keys about Personnel Cost Planning: Admin.Data for Scenario Group data available in SAP. These include PLVAR (Plan Version), VERSN (Version Number (Plan Scenario = Plan Version + Version No.)), BEGDA (Start Date), ENDDA (End 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 PPCAD 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 | |||
PLVAR | Plan Version | PLVAR | CHAR | 2 | Assigned to domain | PLVAR | POP | ||
VERSN | Version Number (Plan Scenario = Plan Version + Version No.) | HR_VERSN | CHAR | 2 | Assigned to domain | HR_VERSN | |||
BEGDA | Start Date | BEGDATUM | DATS | 8 | DATUM | BEG | |||
ENDDA | End Date | ENDDATUM | DATS | 8 | DATUM | END | |||
VNAME | (Cost) scenario group - Subdivision of a plan scenario | HR_VNAME | CHAR | 12 | HR_VNAME | ||||
UNAME | User Name | USRNAME | CHAR | 12 | CHAR12 | ||||
DATUM | Changed on | AEDTM | DATS | 8 | DATUM | ||||
UZEIT | Time of last change | HR_UZEIT | TIMS | 6 | UZEIT | ||||
STEXT | Comments on scenario group | HR_COTXT | CHAR | 40 | TEXT40 | ||||
FRFLG | Plan scenario released | HR_FRFLG | CHAR | 1 | KREUZ | ||||
ABART | Personnel Cost Projection Period | HR_PC_ABT | CHAR | 1 | Assigned to domain | ABRAR | |||
LTEXT | Long text for employee subgroups for personnel calc. rule | ABLTX | CHAR | 25 | TEXT25 | ||||
CURCY | Currency Key | HR_CURCY | CUKY | 5 | Assigned to domain | WAERS | FWS | ||
PWD | Password for scenario group to be stored | HR_PWD | CHAR | 12 | CHAR12 | ||||
COSTS_TYPE | Object Type | OTYPE | CHAR | 2 | Assigned to domain | OTYPE | POT | ||
TXT | Personnel cost planning: Reserve field | HR_PC_RESV | CHAR | 100 | TEXT100 |
Key field | Non-key field |
How do I retrieve data from SAP structure PPCAD using ABAP code?
As PPCAD 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 PPCAD as there is no data to select.How to access SAP table PPCAD
Within an ECC or HANA version of SAP you can also view further information about PPCAD 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