BAPI_WRF_POSCHEDULE_STY SAP (Obsolete: Please do not use) Structure details
Description: Obsolete: Please do not use
Related tables to BAPI_WRF_POSCHEDULE_STY
Access table BAPI_WRF_POSCHEDULE_STY
Structure field list including key, data, relationships and ABAP select examples
BAPI_WRF_POSCHEDULE_STY 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 "Obsolete: Please do not use" 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_BAPI_WRF_POSCHEDULE_STY TYPE BAPI_WRF_POSCHEDULE_STY.
The BAPI_WRF_POSCHEDULE_STY table consists of various fields, each holding specific information or linking keys about Obsolete: Please do not use data available in SAP. These include SCHED_LINE (Delivery Schedule Line Number), DEL_DATCAT_EXT (Category of Delivery Date), DELIVERY_DATE (Delivery Date), QUANTITY (Scheduled Quantity).. 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 BAPI_WRF_POSCHEDULE_STY 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 |
| 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 | |||
| DEL_DATCAT_EXT | Category of Delivery Date | LPEIN | CHAR | 1 | Assigned to domain | PRGBZ | |||
| DELIVERY_DATE | Delivery Date | EEIND | CHAR | 10 | CHAR10 | ||||
| QUANTITY | Scheduled Quantity | ETMEN | QUAN | 13(3) | MENGE | ||||
| DELIV_TIME | Delivery Date Time-Spot | LZEIT | TIMS | 6 | UZEIT | ||||
| STAT_DATE | Statistics-Relevant Delivery Date | SLFDT | DATS | 8 | DATUM | ||||
| PREQ_NO | Purchase Requisition Number | BANFN | CHAR | 10 | ALPHA | BANFN | BAN | MBAN_C | |
| PREQ_ITEM | Item Number of Purchase Requisition | BNFPO | NUMC | 5 | Assigned to domain | BNFPO | BAP | ||
| PO_DATE | Order date of schedule line | ETBDT | DATS | 8 | DATUM | ||||
| ROUTESCHED | Route Schedule | AULWE | CHAR | 10 | Assigned to domain | AULWE | |||
| MS_DATE | Material Staging/Availability Date | MBDAT | DATS | 8 | DATUM | ||||
| MS_TIME | Material Staging Time (Local, Relating to a Plant) | MBUHR | TIMS | 6 | TIME_PLANT | ||||
| LOAD_DATE | Loading Date | LDDAT | DATS | 8 | DATUM | ||||
| LOAD_TIME | Loading Time (Local Time Relating to a Shipping Point) | LDUHR | TIMS | 6 | TIME_SHIPP | ||||
| TP_DATE | Transportation Planning Date | TDDAT_D | DATS | 8 | DATUM | ||||
| TP_TIME | Transp. Planning Time (Local, Relating to a Shipping Point) | TDUHR | TIMS | 6 | TIME_SHIPP | ||||
| GI_DATE | Goods Issue Date | WADAT | DATS | 8 | DATUM | ||||
| GI_TIME | Time of Goods Issue (Local, Relating to a Plant) | WAUHR | TIMS | 6 | TIME_PLANT | ||||
| DELETE_IND | Deletion Indicator in Purchasing Document | ELOEK | CHAR | 1 | ELOEK | ||||
| OTB_KEY_ID | Unique Number of Budget | WRF_BUDG_KEY_ID | NUMC | 16 | WRF_BUDG_KEY_ID | ||||
| OTB_VALUE | Currency amount for BAPIS (with 9 decimal places) | BAPICUREXT | DEC | 28(9) | BAPICUREXT | ||||
| OTB_CURRENCY | Currency Key | CURRENCY | CUKY | 5 | Assigned to domain | WAERS | |||
| OTB_CURRENCY_ISO | ISO code currency | WAERS_ISO | CHAR | 3 | ISOCD | ||||
| OTB_RES_VALUE | Currency amount for BAPIS (with 9 decimal places) | BAPICUREXT | DEC | 28(9) | BAPICUREXT | ||||
| OTB_SPEC_VALUE | Currency amount for BAPIS (with 9 decimal places) | BAPICUREXT | DEC | 28(9) | BAPICUREXT | ||||
| OTB_BUDG_TYPE | Budget Type | WRF_BUDG_TYPE | CHAR | 2 | WRF_BUDG_TYPE | WRF_POTB_BUDGET_TYPE_F4 | |||
| OTB_STATUS | OTB Check Status | WRF_POTB_STATUS | CHAR | 1 | WRF_POTB_STATUS | ||||
| OTB_REASON | Reason Indicator for OTB Check Status | WRF_POTB_STATUS_REASON | CHAR | 3 | WRF_POTB_STATUS_REASON | ||||
| DATELINE_ID | Date Line ID (GUID) | WRF_PSCD_DL_ID | CHAR | 22 | SYSUUID_22 | ||||
| HANDOVER_DATE | Transfer Date | WRF_PSCD_HANDOVER_DATE | DATS | 8 | DATS | ||||
| HANDOVER_COUNTRY | Transfer Country ID | WRF_PSCD_HANDOVER_COUNTRY | CHAR | 3 | Assigned to domain | LAND1 | |||
| HANDOVER_COUNTRY_ISO | ISO country code for VAT registration number | STCEG_L_ISO | CHAR | 2 | INTCA | ||||
| HANDOVER_CITY | Transfer Region ID | WRF_PSCD_HANDOVER_CITY | CHAR | 3 | Assigned to domain | REGIO | |||
| CNCL_ANCMNT_DONE | Cancellation Threat Made | WRF_PCTR_CNCL_ANCMT_DONE | CHAR | 1 | CHAR1_X |
| Key field | Non-key field |
How do I retrieve data from SAP structure BAPI_WRF_POSCHEDULE_STY using ABAP code?
As BAPI_WRF_POSCHEDULE_STY 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 BAPI_WRF_POSCHEDULE_STY as there is no data to select.How to access SAP table BAPI_WRF_POSCHEDULE_STY
Within an ECC or HANA version of SAP you can also view further information about BAPI_WRF_POSCHEDULE_STY 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