ADPIC_S_POSCHEDULEX SAP (Sch. LineX with identifier for the parsing to BAPI_PO_CHANGE) Structure details
Description: Sch. LineX with identifier for the parsing to BAPI_PO_CHANGE
Related tables to ADPIC_S_POSCHEDULEX
Access table ADPIC_S_POSCHEDULEX
Structure field list including key, data, relationships and ABAP select examples
ADPIC_S_POSCHEDULEX 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 "Sch. LineX with identifier for the parsing to BAPI_PO_CHANGE" 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_ADPIC_S_POSCHEDULEX TYPE ADPIC_S_POSCHEDULEX.
The ADPIC_S_POSCHEDULEX table consists of various fields, each holding specific information or linking keys about Sch. LineX with identifier for the parsing to BAPI_PO_CHANGE data available in SAP. These include PO_ITEM (Item Number of Purchasing Document), SCHED_LINE (Delivery Schedule Line Number), PO_ITEMX (Updated information in related user data field), SCHED_LINEX (Updated information in related user data field).. 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 ADPIC_S_POSCHEDULEX 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 |
LINE_ID | Unique identification of document line | MB_LINE_ID | NUMC | 6 | MB_LINE_ID | ||||
PO_ITEM | Item Number of Purchasing Document | EBELP | NUMC | 5 | Assigned to domain | EBELP | BSP | ||
SCHED_LINE | Delivery Schedule Line Number | ETENR | NUMC | 4 | Assigned to domain | ETENR | |||
PO_ITEMX | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
SCHED_LINEX | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
DEL_DATCAT_EXT | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
DELIVERY_DATE | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
QUANTITY | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
DELIV_TIME | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
STAT_DATE | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
PREQ_NO | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
PREQ_ITEM | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
PO_DATE | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
ROUTESCHED | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
MS_DATE | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
MS_TIME | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
LOAD_DATE | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
LOAD_TIME | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
TP_DATE | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
TP_TIME | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
GI_DATE | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
GI_TIME | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
DELETE_IND | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
REQ_CLOSED | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
GR_END_DATE | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
GR_END_TIME | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
COM_QTY | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
COM_DATE | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
GEO_ROUTE | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
HANDOVERDATE | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
HANDOVERTIME | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE |
Key field | Non-key field |
How do I retrieve data from SAP structure ADPIC_S_POSCHEDULEX using ABAP code?
As ADPIC_S_POSCHEDULEX 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 ADPIC_S_POSCHEDULEX as there is no data to select.How to access SAP table ADPIC_S_POSCHEDULEX
Within an ECC or HANA version of SAP you can also view further information about ADPIC_S_POSCHEDULEX 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