PLST SAP (Status table for planned order processing) Structure details
Description: Status table for planned order processing
Structure field list including key, data, relationships and ABAP select examples
PLST 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 "Status table for planned order processing" 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_PLST TYPE PLST.
The PLST table consists of various fields, each holding specific information or linking keys about Status table for planned order processing data available in SAP. These include AKTAL (Current explosion available), AKTFT (Indicator 'Detailed scheduling available'), AKTRT (Indicator: 'scheduling rates of production' available), AKTGT (Indicator: 'rough-cut scheduling available').. 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 (character-type)
SAP PLST 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 |
| PLNUM | Planned order number | PLNUM | CHAR | 10 | Assigned to domain | ALPHA | PLNUM | PAF | |
| AKTAL | Current explosion available | AKTAL | CHAR | 1 | XFLAG | ||||
| AKTFT | Indicator 'Detailed scheduling available' | AKTFT | CHAR | 1 | XFELD | ||||
| AKTRT | Indicator: 'scheduling rates of production' available | AKTRT | CHAR | 1 | XFELD | ||||
| AKTGT | Indicator: 'rough-cut scheduling available' | AKTGT | CHAR | 1 | XFELD | ||||
| GSAEN | Net change planning indicator | GSAEN | CHAR | 1 | XFELD | ||||
| STAUF | BOM explosion for posting in planned order | STAUF | CHAR | 1 | XFELD | ||||
| PTERM | Lead time scheduling when posting planned orders | PTERM | CHAR | 1 | XFELD | ||||
| NEWSC | Scheduling was carried out in planned order processing | NEWSC | CHAR | 1 | XFELD | ||||
| LOCOX | Checkbox | XFELD | CHAR | 1 | XFELD | ||||
| COMPZ | Checkbox | XFELD | CHAR | 1 | XFELD | ||||
| BOMCH | Indicator: Change in components | BOMCH | CHAR | 1 | CHAR1 | ||||
| SCHCH | Indicator: Change relevant to scheduling | SCHCH | CHAR | 1 | CHAR1 |
| Key field | Non-key field |
How do I retrieve data from SAP structure PLST using ABAP code?
As PLST 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 PLST as there is no data to select.How to access SAP table PLST
Within an ECC or HANA version of SAP you can also view further information about PLST 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