PLSV SAP (Structure for collective availability check - planned orders) Structure details
Description: Structure for collective availability check - planned orders
Structure field list including key, data, relationships and ABAP select examples
PLSV 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 "Structure for collective availability check - planned orders" 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_PLSV TYPE PLSV.
The PLSV table consists of various fields, each holding specific information or linking keys about Structure for collective availability check - planned orders data available in SAP. These include MATNR (Planning material), PLWRK (Planning Plant), PWWRK (Production plant in planned order), PAART (Order type).. 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 or numeric)
SAP PLSV 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 | |
MATNR | Planning material | PLMAT | CHAR | 18 | Assigned to domain | MATN1 | MATNR | MAT | |
PLWRK | Planning Plant | PLWRK | CHAR | 4 | Assigned to domain | WERKS | WRK | ||
PWWRK | Production plant in planned order | PWWRK | CHAR | 4 | Assigned to domain | WERKS | |||
PAART | Order type | PAART | CHAR | 4 | PAART | ||||
GSMNG | Total planned order quantity | GSMNG | QUAN | 13(3) | MENG13 | ||||
PSTTR | Order start date in planned order | PSTTR | DATS | 8 | DATUM | ||||
PEDTR | Order finish date in the planned order | PEDTR | DATS | 8 | DATUM | ||||
PERTR | Planned opening date in planned order | PERTR | DATS | 8 | DATUM | ||||
WEBAZ | Goods receipt processing time in days | PLWEZ | DEC | 3 | DEC3 | ||||
DISPO | MRP controller | PLDSP | CHAR | 3 | Assigned to domain | DISPO | |||
UMSKZ | Conversion indicator for planned order | PLUMS | CHAR | 1 | XFELD | ||||
AUFFX | Firming indicator for planned order data | PLAFX | CHAR | 1 | XFELD | ||||
STLFX | Fixing indicator for BOM explosion | PLSFX | CHAR | 1 | XFELD | ||||
KNTTP | Account Assignment Category | KNTTP | CHAR | 1 | Assigned to domain | KNTTP | KNT | ||
KDAUF | Sales Order Number | KDAUF | CHAR | 10 | Assigned to domain | ALPHA | VBELN | AUN | |
KDPOS | Item Number in Sales Order | KDPOS | NUMC | 6 | NUM06 | KPO | |||
KDEIN | Delivery Schedule for Sales Order | KDEIN | NUMC | 4 | NUM04 | ||||
RSNUM | Number of Reservation/Dependent Requirement | RSNUM | NUMC | 10 | Assigned to domain | RSNUM | RES | ||
PSPEL | WBS Element | PS_POSNR | NUMC | 8 | Assigned to domain | ABPSP | PS_POSNR | ||
SOBKZ | Special Stock Indicator | SOBKZ | CHAR | 1 | Assigned to domain | SOBKZ | |||
LGORT | Storage Location | LGORT_D | CHAR | 4 | Assigned to domain | LGORT | LAG | ||
SERNR | BOM explosion number | SERNR | CHAR | 8 | Assigned to domain | SERNR | |||
AENNR | Change Number | AENNR | CHAR | 12 | Assigned to domain | AENNR | AENNR | AEN | |
VERID | Production Version | VERID | CHAR | 4 | Assigned to domain | VERID | VER | ||
SAUFNR | Run schedule header number | SA_AUFNR | CHAR | 12 | Assigned to domain | ALPHA | SA_AUFNR | ||
PLGRP | Production Supervisor | FEVOR | CHAR | 3 | Assigned to domain | FEVOR | CFV | ||
MEINS | Base Unit of Measure | MEINS | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
REVLV | Revision Level | REVLV | CHAR | 2 | NUMCV | REVLV | RVS | ||
SEQNR | Seq. number order | CY_SEQNR | NUMC | 14 | CY_SEQNR | ||||
MONKZ | Indicator: for assembly order procedures | MONKZ | CHAR | 1 | XFELD | ||||
MDPBV | Planned order: confirmation of availability | MDPBV | CHAR | 1 | MDPBV | ||||
VFMNG | Planned order: committed quantity | VFMNG | QUAN | 13(3) | MENG13 | ||||
MDACH | Action control: planned order processing | MDACH | CHAR | 2 | Assigned to domain | MDACH | |||
MDACC | Action: planned order processing | MDACC | CHAR | 4 | Assigned to domain | MDACC | |||
MDACD | Date of action: planned order | MDACD | DATS | 8 | DATUM | ||||
MDACT | Time of action: Planned order processing | MDACT | TIMS | 6 | UZEIT | ||||
GSBTR | Total commitment date of plnd ord. after ATP check f.comps. | GSBTR_PLAF | DATS | 8 | DATUM | ||||
KZAVC | Indicator for type of availability check | KZAVC | CHAR | 1 | KZAVC | ||||
TERST | Start date for production | TERST | DATS | 8 | DATUM | ||||
TERED | Finish date for production | TERED | DATS | 8 | DATUM | ||||
TRMKZ | Scheduling indicator | TRMKZ | CHAR | 1 | XFELD | ||||
PSTTI | Start Time of Planned Order | PSTTI | TIMS | 6 | UZEIT | ||||
PEDTI | End Time of Planned Order | PEDTI | TIMS | 6 | UZEIT | ||||
MATXT | Material description | CO_MATXT | CHAR | 40 | TEXT40 | ||||
MDV01 | Production line | MDV01 | CHAR | 8 | Assigned to domain | MDVXX | |||
MDV02 | Planning identification 2 | MDV02 | CHAR | 8 | Assigned to domain | MDVXX | |||
BSFAK | Confirmation factor confirmed qty. for order quantity | CO_BSFAK | QUAN | 3 | RSDQUAN | ||||
PROZENT | Unit for the Rate (Percent) | QPROZENT | UNIT | 2 | QPROZENT | ||||
BSDIF | Difference betw. rqmts. date and order date in fact.cal.days | BSDIF | CHAR | 3 | CHAR3 | ||||
RETCODE | Result of availability check | RC_VERF | CHAR | 2 | CHAR2 | ||||
KAPFX | Indicator: capacity for planned order dispatched | KAPFX | CHAR | 1 | XFELD | ||||
REMFL | Repetitive Manufacturing indicator | REMFL | CHAR | 1 | REMFL |
Key field | Non-key field |
How do I retrieve data from SAP structure PLSV using ABAP code?
As PLSV 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 PLSV as there is no data to select.How to access SAP table PLSV
Within an ECC or HANA version of SAP you can also view further information about PLSV 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