WRF_POHF_EXT_SCHEDULE_STY SAP (Schedule Line Data: Seasonal Procurement Add-On) Structure details
Description: Schedule Line Data: Seasonal Procurement Add-On
Related tables to WRF_POHF_EXT_SCHEDULE_STY
Access table WRF_POHF_EXT_SCHEDULE_STY
Structure field list including key, data, relationships and ABAP select examples
WRF_POHF_EXT_SCHEDULE_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 "Schedule Line Data: Seasonal Procurement Add-On" 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_WRF_POHF_EXT_SCHEDULE_STY TYPE WRF_POHF_EXT_SCHEDULE_STY.
The WRF_POHF_EXT_SCHEDULE_STY table consists of various fields, each holding specific information or linking keys about Schedule Line Data: Seasonal Procurement Add-On data available in SAP. These include KEY_ID (Unique Number of Budget), OTB_VALUE (Required Budget), OTB_CURR (OTB Currency), OTB_RES_VALUE (Reserved Budget for OTB-Relevant Purchasing Document).. 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 WRF_POHF_EXT_SCHEDULE_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 |
KEY_ID | Unique Number of Budget | WRF_BUDG_KEY_ID | NUMC | 16 | WRF_BUDG_KEY_ID | ||||
OTB_VALUE | Required Budget | WRF_POTB_VALUE | CURR | 17(2) | WRF_POTB_VALUE | ||||
OTB_CURR | OTB Currency | WRF_POTB_CURRENCY | CUKY | 5 | Assigned to domain | WAERS | |||
OTB_RES_VALUE | Reserved Budget for OTB-Relevant Purchasing Document | WRF_POTB_RES_VALUE | CURR | 17(2) | WRF_POTB_RES_VALUE | ||||
OTB_SPEC_VALUE | Special Release Budget | WRF_POTB_SPECIAL_VALUE | CURR | 17(2) | WRF_POTB_SPECIAL_VALUE | ||||
SPR_RSN_PROFILE | Reason Profile for OTB Special Release | WRF_POTB_SPR_RSN_PROFILE | CHAR | 4 | WRF_POTB_SPR_RSN_PROFILE | ||||
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 | ||||
CHECK_TYPE | Type of OTB Check | WRF_BUDG_OTB_CHECK | CHAR | 1 | WRF_BUDG_OTB_CHECK | ||||
DL_ID | Date Line ID (GUID) | WRF_PSCD_DL_ID | CHAR | 22 | SYSUUID_22 | ||||
HANDOVER_DATE | Transfer Date | WRF_PSCD_HANDOVER_DATE | DATS | 8 | DATS | ||||
NO_SCEM | Purchase Order Not Transferred to SCEM | WRF_PSCD_NO_SCEM | CHAR | 1 | CHAR1_X | ||||
DNG_DATE | Creation Date of Reminder Message Record | WRF_PCTR_DNG_DATE | DATS | 8 | DATUM | ||||
DNG_TIME | Creation Time of Reminder Message Record | WRF_PCTR_DNG_TIME | TIMS | 6 | UZEIT | ||||
CNCL_ANCMNT_DONE | Cancellation Threat Made | WRF_PCTR_CNCL_ANCMT_DONE | CHAR | 1 | CHAR1_X | ||||
DATESHIFT_NUMBER | Number of Current Date Shifts | WRF_PCTR_DATESHIFT_NUMBER | DEC | 3 | DEC3 | ||||
MAHNZ | Number of Reminders/Expediters | MAHNZ | DEC | 3 | PACK2 |
Key field | Non-key field |
How do I retrieve data from SAP structure WRF_POHF_EXT_SCHEDULE_STY using ABAP code?
As WRF_POHF_EXT_SCHEDULE_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 WRF_POHF_EXT_SCHEDULE_STY as there is no data to select.How to access SAP table WRF_POHF_EXT_SCHEDULE_STY
Within an ECC or HANA version of SAP you can also view further information about WRF_POHF_EXT_SCHEDULE_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