Search Results line_fixed_throughput

Overview

APPS.WIP_REPETITIVE_ITEMS_V is a reporting and integration view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that consolidates repetitive manufacturing schedule definitions with their associated production line attributes. The view joins the repetitive item assignment records held in WIP_REPETITIVE_ITEMS to the line-level definition stored in WIP_LINES, resolves the WIP supply type to a user-facing meaning through MFG_LOOKUPS, and optionally resolves completion subinventory attributes from MTL_SECONDARY_INVENTORIES. The result is a single denormalized record per repetitive schedule that exposes both the item-side planning data (rates, tolerances, alternate designators) and the line-side scheduling data (schedule type, minimum rate, maximum rate, fixed throughput).

Because it carries the WIP_ENTITY_ID and the full set of WHO audit columns, the view is commonly used as a data source for repetitive schedule inquiries, custom reports, and outbound interfaces that must reconstruct a schedule exactly as the planning and work-in-process modules understand it.

Underlying Base Objects

The view is defined over four documented base objects:

• WIP_REPETITIVE_ITEMS (synonym) — the driving table, aliased WRI, holding the repetitive schedule and item assignment. Its primary key WIP_ENTITY_ID and LINE_ID anchor the view.
• WIP_LINES (synonym) — aliased WL, the production line definition, joined on LINE_ID and ORGANIZATION_ID. This supplies the line code, description, schedule type, and rate/throughput attributes.
• MFG_LOOKUPS (view) — aliased ML, joined on LOOKUP_TYPE = 'WIP_SUPPLY' and LOOKUP_CODE = WRI.WIP_SUPPLY_TYPE, providing the MEANING text used as WIP_SUPPLY_TEXT.
• MTL_SECONDARY_INVENTORIES (synonym) — aliased MSV, joined with outer-join syntax (+) on SECONDARY_INVENTORY_NAME and ORGANIZATION_ID, supplying LOCATOR_TYPE and allowing schedules with no completion subinventory to remain in the result set.

The join to WIP_LINES is an inner join, so a repetitive item is only returned when a valid production line exists in the same organization.

Key Columns

• WIP_ENTITY_ID, LINE_ID, ORGANIZATION_ID — primary identifiers linking the schedule to its line and inventory organization.
• LINE_CODE, LINE_DESCRIPTION, LINE_SCHEDULE_TYPE, LINE_MINIMUM_RATE, LINE_MAXIMUM_RATE — production line attributes sourced from WIP_LINES.
• LINE_FIXED_THROUGHPUT — the fixed throughput flag from WIP_LINES.FIXED_THROUGHPUT, indicating whether the line runs at a fixed rate rather than within a minimum/maximum rate band. This is the column most often referenced by users searching the term "line_fixed_throughput".
• PRODUCTION_LINE_RATE — the rate at which the repetitive schedule is planned to produce.
• PRIMARY_ITEM_ID, ALTERNATE_BOM_DESIGNATOR, ALTERNATE_ROUTING_DESIGNATOR, CLASS_CODE — item and structure definition for the scheduled assembly.
• WIP_SUPPLY_TYPE, WIP_SUPPLY_TEXT — the supply type code and its decoded meaning.
• COMPLETION_SUBINVENTORY, COMPLETION_LOCATOR_ID, LOCATOR_TYPE — completion location data, with LOCATOR_TYPE defaulted to 1 via NVL when no secondary inventory match exists.
• LOAD_DISTRIBUTION_PRIORITY, PRIMARY_LINE_FLAG — scheduling controls for constrained and primary line assignment.
• OVERCOMPLETION_TOLERANCE_TYPE, OVERCOMPLETION_TOLERANCE_VALUE — tolerance settings controlling permitted over-completion.
• ATTRIBUTE1–ATTRIBUTE15, ATTRIBUTE_CATEGORY — the DFF-enabled descriptive flexfield columns.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — audit and concurrent program provenance columns.

Common Use Cases and Queries

The view supports repetitive schedule inquiries, capacity and rate analysis, and interface extraction. A typical query lists schedules for an organization and flags fixed-throughput lines:

SELECT wip_entity_id, line_code, primary_item_id, line_schedule_type,
     line_minimum_rate, line_maximum_rate, line_fixed_throughput,
     production_line_rate, wip_supply_text
 FROM apps.wip_repetitive_items_v
 WHERE organization_id = :org_id
 ORDER BY line_code, primary_item_id;

To isolate fixed-rate lines, add WHERE line_fixed_throughput = 'Y'. A second scenario extracts schedule detail with completion locations for interface processing, selecting COMPLETION_SUBINVENTORY and LOCATOR_TYPE. Because the LOCATOR_TYPE expression uses NVL(...,1), consumers should not assume a null locator type indicates an error. The view should be queried rather than joined directly to WIP_LINES in custom code, since it already encapsulates the line, lookup, and subinventory joins consistently.