Search Results line_priority

Overview

The APPS.WIPFV_WIP_REPETITIVE_ITEMS view is a reporting and integration layer over the repetitive manufacturing structures maintained in Oracle Work in Process (WIP). It presents repetitive schedules, their associated production lines, primary assemblies, completion subinventories and locators, and the descriptive flexfield segments and lookup meanings that would otherwise require multiple joins to decode. In Oracle EBS 12.1.1 and 12.2.2 the view is defined with the WITH READ ONLY clause, confirming its intended use as a query-only construct for reporting, Oracle Discoverer/BI Publisher datasets, and inbound or outbound interface validation. It is owned by APPS and is reported as VALID in the ETRM repository.

The view is of particular interest to users searching for line_priority, because it exposes that column directly rather than requiring the caller to know that it originates from WIP_REPETITIVE_ITEMS. The column is surfaced under a renamed alias, and it is accompanied by derived lookup-meaning columns and a key flexfield attribute, making the view convenient for ad hoc reporting without additional decode logic.

Underlying Base Objects

The view joins nine base objects, all referenced through APPS synonyms:

• WIP_REPETITIVE_ITEMS — the driving table, supplying the repetitive schedule attributes including the supply type, primary line flag, production line rate, overcompletion tolerance, alternate BOM and routing designators, and the load distribution priority.
• WIP_ENTITIES — supplies the WIP entity name (the manufacturing order or schedule name) and links on WIP_ENTITY_ID.
• WIP_LINES — provides the production line code, joined on LINE_ID and ORGANIZATION_ID.
• WIP_ACCOUNTING_CLASSES — joined on CLASS_CODE and ORGANIZATION_ID to validate and describe the schedule's accounting class.
• MTL_SYSTEM_ITEMS — supplies the primary item definition, joined on PRIMARY_ITEM_ID and ORGANIZATION_ID; the item number is exposed as a key flexfield column.
• HR_ALL_ORGANIZATION_UNITS — provides the organization name, joined on ORGANIZATION_ID.
• MTL_PARAMETERS — provides the organization code.
• MTL_ITEM_LOCATIONS — outer-joined on COMPLETION_LOCATOR_ID and ORGANIZATION_ID to return the completion locator.
• MTL_SECONDARY_INVENTORIES — outer-joined on COMPLETION_SUBINVENTORY and ORGANIZATION_ID to return the completion subinventory.

The outer joins on MTL_ITEM_LOCATIONS and MTL_SECONDARY_INVENTORIES ensure that repetitive schedules lacking a defined completion locator or subinventory are not excluded from the result set.

Key Columns

Documented columns exposed by the view include ALTERNATE_BOM, ALTERNATE_ROUTING, the lookup-derived WIP_SUPPLY_TYPE meaning, LINE_PRIORITY, the lookup-derived LEAD_TIME_LINE_FLAG (the primary line flag decoded through SYS_YES_NO), PRODUCTION_LINE_RATE, the lookup-derived OVERCOMP_TOLERANCE_TYPE (decoded through WIP_TOLERANCE_TYPE), OVERCOMPLETION_TOLERANCE_VALUE, MFG_ORDER_NAME, LINE_NUMBER, ORGANIZATION_CODE, ORGANIZATION_NAME, the key flexfield ITEM_NUMBER, and LOCATOR. The underlying identifiers WIP_ENTITY_ID, LINE_ID, ORGANIZATION_ID, PRIMARY_ITEM_ID, CLASS_CODE, COMPLETION_SUBINVENTORY, COMPLETION_LOCATOR_ID, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and LAST_UPDATED_BY are also retained for join and audit purposes.

LINE_PRIORITY corresponds to the load distribution priority of the repetitive schedule and is significant when multiple schedules share a production line: it determines the sequence in which the line is loaded during scheduling and, consequently, which schedule is processed first when capacity is constrained. It maps to the LOAD_DISTRIBUTION_PRIORITY base column.

Common Use Cases and Queries

Typical uses include listing all repetitive schedules on a line ordered by priority, verifying completion subinventory and locator assignments, and exporting schedule attributes for capacity or rate-based planning analysis.

SELECT mfg_order_name,
       line_number,
       line_priority,
       production_line_rate,
       item_number,
       organization_code
  FROM apps.wipfv_wip_repetitive_items
 WHERE organization_code = :org
 ORDER BY line_number, line_priority;

When investigating schedules whose completion destination is incomplete, the outer-joined columns can be tested directly:

SELECT mfg_order_name,
       line_number,
       line_priority,
       locator
  FROM apps.wipfv_wip_repetitive_items
 WHERE locator IS NULL;

Because the view is read-only, it must not be used as the target of DML; updates to line priority belong to WIP_REPETITIVE_ITEMS through the standard WIP forms or APIs. All queries should be qualified by ORGANIZATION_ID or ORGANIZATION_CODE to preserve performance and data isolation.