Search Results wtp_date

Overview

APPS.CSR_WTP_DISPLAY_V is a reporting view in the Oracle E-Business Suite (EBS) Advanced Supply Chain Planning and Enterprise Territory / Resource Management domain, used within the Oracle Field Service and resource scheduling modules. The view consolidates scheduling, resource, and cost information produced by the planning engine to present the "Window to Promise" (WTP) data set. In practice, it exposes planned task assignments along with the resource, scheduling, and rule-window context needed to interpret them.

The view draws together request tasks, resource results, plan options, and rule windows, resolving the window-to-promise identifier into a human-readable window name. The central reporting date column is aliased WTP_DATE, which reflects CSF_R_PLAN_OPTIONS.SCHEDULED_START_DATE. Users who search for "wtp_date" are typically looking for this column, which represents the scheduled start of the promised work window.

Underlying Base Objects

The documented base objects referenced by this view include:

• CSF_R_REQUEST_TASKS (synonym) — the scheduling request task records.
• CSF_R_RESOURCE_RESULTS (synonym) — per-resource results generated from a task.
• CSF_R_PLAN_OPTIONS (synonym) — the plan option records supplying scheduling dates, cost, and window references.
• CSR_RULE_WINDOWS_V (view) — the rule window definitions providing window names and start/end time components.
• CSF_RESOURCE_PUB (package) — the public resource API invoked via GET_RESOURCE_NAME to resolve resource identifiers to display names.

The joins are straightforward and well-defined. CSF_R_REQUEST_TASKS links to CSF_R_RESOURCE_RESULTS on REQUEST_TASK_ID, resource results link to plan options on RESOURCE_RESULT_ID, and rule windows link to plan options on WIN_TO_PROMIS_ID = WINDOW_ID. This inner-join chain means records are only returned when a task, resource result, plan option, and matching window all exist.

Key Columns

• WINDOW_TYPE — the rule window name (RW.WINDOW_NAME), describing the window applied to the promise.
• START_TIME — derived by adding the window's start hour/minute to the truncated scheduled date.
• END_TIME — derived similarly from the window's end hour/minute.
• WTP_DATE — the scheduled start date from the plan option, representing the promise date.
• COST — the cost associated with the plan option.
• PLAN_OPTION_ID — identifier of the underlying plan option row.
• RESOURCE_NAME — display name resolved through CSF_RESOURCE_PUB.GET_RESOURCE_NAME.
• RESOURCE_ID / RESOURCE_TYPE — raw resource identifiers.
• SCHED_REQUEST_ID — link back to the originating scheduling request.
• WIN_PROMIS_ID — the rule window identifier used to build the promise.

Common Use Cases and Queries

Typical use cases include auditing scheduled promises by resource, reconciling promise dates against rule-window boundaries, and reporting planned costs by window and resource. Because the view resolves the resource name and window name, it is well suited to end-user reporting without additional lookups.

• List promises after a given date:

  SELECT resource_name, window_type, wtp_date, cost
  FROM   apps.csr_wtp_display_v
  WHERE  wtp_date >= TO_DATE('01-JAN-2024','DD-MON-YYYY')
  ORDER  BY wtp_date;

• Show the effective promise window by resource:

  SELECT resource_name, window_type, start_time, end_time, wtp_date
  FROM   apps.csr_wtp_display_v;

• Aggregate planned cost by window type:

  SELECT window_type, COUNT(*) num_promises, SUM(cost) total_cost
  FROM   apps.csr_wtp_display_v
  GROUP  BY window_type;

Note that the ETRM metadata lists additional parsed dependencies (WINDOW1532_COLL, XMLSEQUENCE, AGGXMLIMP, SYS_IXMLAGG, XMLSEQUENCEFROMXMLTYPE) reflecting the view's internal construction. Consumers should treat the four core tables and CSF_RESOURCE_PUB as the primary dependencies for performance tuning.