Results for “quantity_completed”

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

Overview

The WIP_FLOW_LINEARITY_V view is a Flow Manufacturing Workstation base view owned by the APPS schema in Oracle E-Business Suite (12.1.1 and 12.2.2). Its purpose is to expose the relationship between planned quantity and completed quantity for a production line across a sequence of calendar dates, enabling linearity analysis in a Flow/Lean manufacturing environment. Linearity measures how evenly production output is distributed against the plan over a given horizon; a perfectly linear line produces the same quantity each working day. The view aggregates schedule data from WIP_FLOW_SCHEDULES and projects it onto a calendar derived from the organization's workday calendar, producing one row per calendar date in the requested range. It is a reporting and inquiry object rather than a transactional table, and it relies on session context supplied through the WIP_SFCB_UTILITIES package (organization, line, and from/to dates), which means it is typically queried from within the Flow Workstation UI or from custom reports seeded with the same context.

Underlying Base Objects

The view is defined over the following documented base objects, referenced through APPS synonyms:

• WIP_FLOW_SCHEDULES — the primary fact source supplying PLANNED_QUANTITY, QUANTITY_COMPLETED, SCHEDULED_COMPLETION_DATE, and LINE_ID.
• BOM_CALENDAR_DATES — the organization workday calendar table that generates one row per valid calendar date, filtered by the organization's CALENDAR_CODE and CALENDAR_EXCEPTION_SET_ID.
• MTL_PARAMETERS — supplies the organization's default CALENDAR_CODE and CALENDAR_EXCEPTION_SET_ID used to join to BOM_CALENDAR_DATES.
• WIP_SFCB_UTILITIES — a PL/pgSQL package (schema APPS) providing runtime context functions such as GET_ORGANIZATION, GET_LINE, GET_LINEARITY_FROM_DATE, GET_LINEARITY_TO_DATE, and SDATE_TO_CDATE (a date-to-display conversion helper).

The outermost query is built from BOM_CALENDAR_DATES (aliased BCD2) left-outer-joined ((+) Oracle outer join) to an inline aggregate query, so every calendar date in the requested range appears at least once — even dates with no scheduled or completed quantity — and those gaps are reported as zero via NVL.

Key Columns

• CALENDAR_DATE — each workday date in the linearity window, derived from the organization's manufacturing calendar.
• PLANNED_QUANTITY — sum of planned quantities from flow schedules whose SCHEDULED_COMPLETION_DATE falls on that calendar date (for the current line and organization); defaults to 0 when no schedule exists.
• QUANTITY_COMPLETED — sum of completed quantities from the same schedules on that date; defaults to 0.

The comparison of these two columns across dates is the essence of linearity reporting. The view text also applies the organization filter, line filter (WFS.LINE_ID = GET_LINE), and the from/to date bounds (GET_LINEARITY_FROM_DATE/GET_LINEARITY_TO_DATE) inside the inline subquery, making the view non-reusable without a valid session context.

Common Use Cases and Queries

Typical uses include linearity dashboards, Flow Workstation planning inquiries, and custom variance reporting. A representative query, assuming the context package values have been set (which normally requires an active OAF session):

SELECT calendar_date,
       planned_quantity,
       quantity_completed,
       (quantity_completed - planned_quantity) AS variance
  FROM apps.wip_flow_linearity_v
 ORDER BY calendar_date;

Because the view depends on WIP_SFCB_UTILITIES session state, direct SQL from a generic client may return no rows or fail to filter correctly unless the same organization, line, and date range are established. Analysts should therefore either run it through the Flow Workstation UI or replicate the underlying join against WIP_FLOW_SCHEDULES, BOM_CALENDAR_DATES, and MTL_PARAMETERS with explicit bind variables when building standalone reports.