Results for “item_uom”

50+ results




Overview
Explore in AI Chat

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

Overview

APPS.WIP_BIS_LATE_PROD_COMP_V is a Business Intelligence System (BIS) reporting view in the Work in Process (WIP) module of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. Its documented purpose is to identify discrete jobs and repetitive schedules that were completed after their scheduled completion date — that is, production orders that finished late. The view is a read-only aggregation layer intended for reporting, dashboards, and downstream integration, not for transactional processing.

Because the user search referenced mtl_item_flexfields, note that this view is one of the standard WIP objects that joins directly to MTL_ITEM_FLEXFIELDS. That join is what allows the view to present item-level descriptive attributes (item number, UOM, description) alongside WIP execution data without requiring the caller to re-derive item information from the inventory item key flexfield.

The view issues no DML and carries no base-table maintenance responsibility; it simply projects a query result set.

Underlying Base Objects

Per the ETRM metadata, WIP_BIS_LATE_PROD_COMP_V is defined as a UNION of two branches and references the following objects:

  • MTL_ITEM_FLEXFIELDS (VIEW) — supplies item number, primary UOM code, and description.
  • WIP_ENTITIES (SYNONYM) — the WIP entity header (job or schedule name).
  • WIP_DISCRETE_JOBS (SYNONYM) — discrete job scheduling and completion dates, used in the first UNION branch.
  • WIP_REPETITIVE_SCHEDULES (SYNONYM) — repetitive schedule dates, used in the second branch.
  • WIP_REPETITIVE_ITEMS (SYNONYM) — links repetitive schedules to their primary item.
  • WIP_LINES (SYNONYM) — production line code; joined with an outer (+) in the discrete branch.

The first branch joins WIP_ENTITIES, WIP_DISCRETE_JOBS, WIP_LINES, and MTL_ITEM_FLEXFIELDS on organization and primary item. The second branch joins the repetitive schedule objects plus WIP_REPETITIVE_ITEMS and MTL_ITEM_FLEXFIELDS. Both branches restrict to STATUS_TYPE IN (3, 4, 5, 12) and apply the lateness predicate NVL(date_completed, SYSDATE) > scheduled_completion_date, which treats open jobs whose scheduled date has passed as late.

Key Columns

Common Use Cases and Queries

Typical uses include on-time delivery reporting, WIP aging, and feeding OBIEE or custom BIS extracts.

SELECT organization_id, wip_entity_name, item_number,
       sched_comp_date, actual_comp_date,
       (actual_comp_date - sched_comp_date) days_late
FROM   apps.wip_bis_late_prod_comp_v
WHERE  organization_id = :org_id
ORDER  BY days_late DESC;

A variant filters by a date window on the scheduled date, and a third joins the view to MTL_ITEM_FLEXFIELDS or MTL_SYSTEM_ITEMS_B if additional item attributes are needed. Results are best read in a reporting schema or via a custom responsibility, as the view is owned by APPS.