PPE_PS_DYNP SAP (Screen Structure for iPPE Connection to Project System) Structure details
Description: Screen Structure for iPPE Connection to Project System
Structure field list including key, data, relationships and ABAP select examples
PPE_PS_DYNP 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 "Screen Structure for iPPE Connection to Project System" 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_PPE_PS_DYNP TYPE PPE_PS_DYNP.
The PPE_PS_DYNP table consists of various fields, each holding specific information or linking keys about Screen Structure for iPPE Connection to Project System data available in SAP. These include OTYPE (iPPE Object Type), AENNR (Change Number in iPPE), APPLOBJ_TYPE (Application Object Type for iPPE), PROJID_KEY (Identification for External Objects).. 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 PPE_PS_DYNP 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 |
| GUID | Internal Identification for PVS Objects | PVS_GUID | RAW | 16 | SYSUUID | ||||
| OTYPE | iPPE Object Type | PVS_OTYPE | CHAR | 1 | PVS_OTYPE | ||||
| AENNR | Change Number in iPPE | PVS_AENNR | CHAR | 12 | ALPHA | PPE_AENNR | |||
| APPLOBJ_TYPE | Application Object Type for iPPE | PVS_APPLOBJ_TYPE | CHAR | 4 | PVS_APPLOBJ_TYPE | ||||
| PROJID_KEY | Identification for External Objects | PVS_EX_OBJ_ID | CHAR | 40 | |||||
| PRSTYPE | Type of Project Node | PRSTYPE | CHAR | 1 | PVS_PRSTYPE | ||||
| PROJID | Project definition (internal) | PS_INTNR | NUMC | 8 | Assigned to domain | KONPD | PS_PSPNR | ||
| PSPID | Project Definition | PS_PSPID | CHAR | 24 | ABPSN | PS_PSPID | PSP | PD_DUMMY | |
| PRO_TEXT | PS: Short description (1st text line) | PS_POST1 | CHAR | 40 | TEXT40 | ||||
| WBSID | WBS Element | PS_POSNR | NUMC | 8 | Assigned to domain | ABPSP | PS_POSNR | ||
| POSID | Work Breakdown Structure Element (WBS Element) | PS_POSID | CHAR | 24 | PROJN | PS_POSID | PRO | ||
| WBS_TEXT | PS: Short description (1st text line) | PS_POST1 | CHAR | 40 | TEXT40 | ||||
| NET_INT | Routing number of operations in the order | CO_AUFPL | NUMC | 10 | AUFPL | ||||
| ACT_INT | General counter for order | CO_APLZL | NUMC | 8 | Assigned to domain | CO_APLZL | |||
| NET_EXT | Order Number | AUFNR | CHAR | 12 | Assigned to domain | ALPHA | AUFNR | ANR | |
| ACT_EXT | Operation/Activity Number | VORNR | CHAR | 4 | NUMCV | VORNR | VGN | ||
| NET_TEXT | Description | AUFTEXT | CHAR | 40 | TEXT40 | ||||
| ACT_TEXT | Operation short text | LTXA1 | CHAR | 40 | TEXT40 | ||||
| RFPNT | Reference Point for Relationship Between iPPE and PS | CN_RPIP | CHAR | 20 | Assigned to domain | CN_RFPNT | |||
| RFPNT_TEXT | Description | CN_TXT | CHAR | 40 | TEXT40 | ||||
| MARK | Checkbox | XFELD | CHAR | 1 | XFELD | ||||
| PNODID_FLG | Derive Assignment via Nodes | PPE_PS_PNODID_FLG | CHAR | 1 | XFELD | ||||
| RFPNT_FLG | Derive Assignment via Reference Point | PPE_PS_RFPNT_FLG | CHAR | 1 | XFELD | ||||
| CREADAT | Date of Application | PVS_ANDAT | DATS | 8 | DATUM | ||||
| CREABY | User who created record | PVS_ANNAM | CHAR | 12 | USNAM | ||||
| CHNGDAT | Date of Last Change | PVS_AEDAT | DATS | 8 | DATUM | ||||
| CHNGBY | Name of Person Who Changed Object | PVS_AENAM | CHAR | 12 | USNAM | ||||
| LOGSYS | Logical system | LOGSYS | CHAR | 10 | Assigned to domain | ALPHA | LOGSYS |
| Key field | Non-key field |
How do I retrieve data from SAP structure PPE_PS_DYNP using ABAP code?
As PPE_PS_DYNP 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 PPE_PS_DYNP as there is no data to select.How to access SAP table PPE_PS_DYNP
Within an ECC or HANA version of SAP you can also view further information about PPE_PS_DYNP 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