Search Results csf_r_request_tasks

Overview

CSR_WTP_DISPLAY_V is an APPS-owned database view within the CSR (Scheduler) product module of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It presents "Where-Used" window-to-promise planning data, exposing the association between scheduling requests, resource results, plan options, and the promotional windows (win-to-promis definitions) against which resources are committed. The view consolidates scheduling cost and timing information into a single flattened result set, making it suitable for reporting, Oracle Discoverer workbooks, and custom concurrent program queries rather than for transactional DML. Because it is a view rather than a table, it carries no independent storage and derives all values dynamically from its participating objects at query time.

Underlying Base Objects

The view is defined over four primary objects joined on their key relationships:

• CSF_R_REQUEST_TASKS (synonym over the base scheduling request tasks table) — supplies the SCHED_REQUEST_ID and the REQUEST_TASK_ID join key.
• CSF_R_RESOURCE_RESULTS — supplies resource-level results, including RESOURCE_ID, RESOURCE_TYPE, and RESOURCE_RESULT_ID, joined via REQUEST_TASK_ID.
• CSF_R_PLAN_OPTIONS — supplies cost, timing, and the PLAN_OPTION_ID and WIN_TO_PROMIS_ID linkage, joined via RESOURCE_RESULT_ID.
• CSR_WIN_PROMIS_VL — the translated win-promis value list, providing window NAME, START_TIME, and END_TIME, joined via WIN_PROMIS_ID.

Documented metadata additionally lists referenced dependencies including CSR_RULE_WINDOWS_V, the CSF_RESOURCE_PUB package (used by the GET_RESOURCE_NAME function), and XML aggregation types such as WINDOW1532_COLL, AGGXMLIMP, XMLSEQUENCE, and SYS_IXMLAGG. The GET_RESOURCE_NAME call resolves the human-readable resource name from the numeric RESOURCE_ID and RESOURCE_TYPE at runtime.

Key Columns

• WINDOW_TYPE — the name of the win-promis window (from WP.NAME).
• START_TIME / END_TIME — computed by combining the truncated scheduled start date with the window's start and end times, yielding effective window boundaries.
• WTP_DATE — the raw SCHEDULED_START_DATE from the plan options record.
• COST — the plan option cost associated with the resource result.
• PLAN_OPTION_ID — identifier of the plan option row.
• RESOURCE_NAME — resolved descriptive resource name returned by CSF_RESOURCE_PUB.GET_RESOURCE_NAME.
• RESOURCE_ID / RESOURCE_TYPE — the resource key and its classification.
• SCHED_REQUEST_ID — the parent scheduling request identifier.
• WIN_PROMIS_ID — the win-promis definition identifier linking to the window value list.

Common Use Cases and Queries

Typical usage involves reporting on scheduled resource commitments per window, reconciling costs, and auditing win-promis assignments. A common query filters on a specific scheduling request:

• SELECT window_type, start_time, end_time, resource_name, cost FROM apps.csr_wtp_display_v WHERE sched_request_id = :request_id;
• SELECT wtp_date, resource_name, SUM(cost) FROM apps.csr_wtp_display_v GROUP BY wtp_date, resource_name;
• SELECT window_type, win_promis_id, resource_id FROM apps.csr_wtp_display_v WHERE start_time BETWEEN :from_date AND :to_date ORDER BY start_time;

Since the view calls CSF_RESOURCE_PUB.GET_RESOURCE_NAME per row, large unfiltered extracts can be performance-sensitive; restricting by SCHED_REQUEST_ID, WTP_DATE, or window date range is advisable. The view is read-only and should be treated as a reporting artifact, not a data maintenance interface.