Results for “scheduled_completion_date”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The WIP_FLOW_MIX_LINEARITY_V view is a Work in Process (WIP) reporting object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes a "Flow Workstation base view" that aggregates flow manufacturing schedule data to measure mix linearity — a key indicator of how closely actual completion quantities align with planned quantities per production line and per scheduled completion date. The view converts the raw schedule date via WIP_SFCB_UTILITIES.SDATE_TO_CDATE and truncates it, producing a day-level SCHEDULED_COMPLETION_DATE that is the natural search key users reference when investigating flow line performance. Mix linearity reporting supports lean manufacturing disciplines by quantifying whether a line is producing the intended mix of models in the intended sequence, rather than concentrating output into a few large batches.

Underlying Base Objects

The view is defined over two documented base objects. The primary source is the synonym WIP_FLOW_SCHEDULES, which stores flow schedule records including organization, line, primary item, planned quantity, quantity completed, and scheduled completion date. The second is the package WIP_SFCB_UTILITIES, whose SDATE_TO_CDATE function is invoked inside the subquery to normalize the scheduled completion date into a comparable calendar value before truncation. The view's definition uses a nested inline subquery named SUBVIEW that groups WIP_FLOW_SCHEDULES by organization, line, converted completion date, and primary item, summing planned and completed quantities. The outer query then re-aggregates by organization, line, and converted date to produce line-level totals and the derived linearity percentages. Because the view is a pure aggregation over schedules, it carries no direct dependency on discrete job or repetitive schedule tables.

Key Columns

• ORGANIZATION_ID — Inventory organization owning the flow line; the primary partitioning dimension for reporting.
• LINE_ID — The flow production line identifier.
• SCHEDULED_COMPLETION_DATE — Aliased from the derived CDATE column; the truncated daily scheduled completion date, and the column most commonly used in WHERE and GROUP BY clauses.
• TOTAL_PLANNED_QTY — Sum of PLANNED_QUANTITY across all items on the line for the day.
• TOTAL_QTY_COMPLETED — Sum of QUANTITY_COMPLETED across all items on the line for the day.
• SUM_ITEM_DIFFERENCE — Sum of the absolute difference between planned and completed quantity per item, measuring mix deviation.
• MIX_PERCENT — The linearity score. When total planned is zero, a value of 100 is returned if the absolute difference sum is also zero, otherwise 0. Otherwise the formula ((1 - SUM_ITEM_DIFFERENCE / TOTAL_PLANNED_QTY) * 100) is applied, with the result floored at zero via GREATEST.

Common Use Cases and Queries

A typical use is to trend mix linearity by line over a date range. Because SCHEDULED_COMPLETION_DATE is the search term, queries commonly restrict on it directly:

SELECT organization_id, line_id, scheduled_completion_date,
  total_planned_qty, total_qty_completed, mix_percent
FROM apps.wip_flow_mix_linearity_v
WHERE scheduled_completion_date BETWEEN :start_date AND :end_date
ORDER BY organization_id, line_id, scheduled_completion_date;

Analysts also flag days where linearity falls below a threshold, for example WHERE mix_percent < 95, to identify lines requiring schedule leveling. Aggregations using AVG(mix_percent) grouped by line_id provide a rolling line scorecard, while comparisons of total_planned_qty against total_qty_completed reveal throughput adherence alongside mix adherence. Because the view is read-only and performs no DML, it is safe for ad hoc SQL, BI Publisher reports, and custom concurrent programs.