SPOP01 SAP (Schedule Record of a Planned Order) Structure details
Description: Schedule Record of a Planned Order
Structure field list including key, data, relationships and ABAP select examples
SPOP01 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 "Schedule Record of a Planned Order" 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_SPOP01 TYPE SPOP01.
The SPOP01 table consists of various fields, each holding specific information or linking keys about Schedule Record of a Planned Order data available in SAP. These include OPIT (Schedule record item), PLNUM (Planned order number), OBJID (Object ID of the resource), SEQNR (Seq. number order).. 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 SPOP01 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 |
| OPID | ID for a schedule record | SP_OPID | NUMC | 15 | SP_OPID | ||||
| OPIT | Schedule record item | SP_OPITEM | NUMC | 5 | SP_OPITEM | ||||
| PLNUM | Planned order number | PLNUM | CHAR | 10 | Assigned to domain | ALPHA | PLNUM | PAF | |
| OBJID | Object ID of the resource | CR_OBJID | NUMC | 8 | Assigned to domain | CR_OBJID | |||
| SEQNR | Seq. number order | CY_SEQNR | NUMC | 14 | CY_SEQNR | ||||
| SCHEDULED | Indicator: Schedule Record/Operation Scheduled | SPSCHEDULED | CHAR | 1 | XFELD | ||||
| FIXED | Indicator: Schedule Record/Operation Deallocated | SPFIXED | CHAR | 1 | XFELD | ||||
| STATU | Status of Schedule Record/Operation | SPSTATU | CHAR | 1 | SPSTATU | ||||
| FIRSTBEGDATE | Start Date of First Takt | SPFIBEGDAT | DATS | 8 | SP_DATE | ||||
| FIRSTBEGTIME | Start Time of First Takt | SPFIBEGTIM | TIMS | 6 | SP_TIME | ||||
| FIRSTENDDATE | End Date of First Takt | SPFIENDDAT | DATS | 8 | SP_DATE | ||||
| FIRSTENDTIME | End Time of First Takt | SPFIENDTIM | TIMS | 6 | SP_TIME | ||||
| LASTBEGDATE | Start Date of Last Takt | SPLABEGDAT | DATS | 8 | SP_DATE | ||||
| LASTBEGTIME | Start Time of Last Takt | SPLABEGTIM | TIMS | 6 | SP_TIME | ||||
| LASTENDDATE | End Date of Last Takt | SPLAENDDAT | DATS | 8 | SP_DATE | ||||
| LASTENDTIME | End Time of Last Takt | SPLAENDTIM | TIMS | 6 | SP_TIME |
| Key field | Non-key field |
How do I retrieve data from SAP structure SPOP01 using ABAP code?
As SPOP01 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 SPOP01 as there is no data to select.How to access SAP table SPOP01
Within an ECC or HANA version of SAP you can also view further information about SPOP01 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