Search Results line_fixed_throughput

Overview

WIP_REPETITIVE_ITEMS_V is an APPS-owned, VALID view in the Work in Process (WIP) product family of Oracle E-Business Suite 12.1.1 and 12.2.2. It is documented in ETRM as providing "foreign-key data for WIP_REPETITIVE_ITEMS," meaning it does not merely project the repetitive item rows verbatim but resolves the descriptive and referential attributes that would otherwise require explicit joins. The view decorates each repetitive schedule line with its line code, line description, scheduling attributes from WIP_LINES, the translated supply-type meaning from MFG_LOOKUPS, and the locator type of the completion subinventory from MTL_SECONDARY_INVENTORIES. This makes it a convenient, denormalized read-only surface for reports, concurrent program queries, OAF/Forms LOVs, and integration extracts that need repetitive schedule context without reproducing the join logic.

Underlying Base Objects

Per the documented view text, WIP_REPETITIVE_ITEMS_V is defined over four referenced objects: WIP_REPETITIVE_ITEMS (SYNONYM), WIP_LINES (SYNONYM), MFG_LOOKUPS (VIEW), and MTL_SECONDARY_INVENTORIES (SYNONYM). WIP_REPETITIVE_ITEMS is the driving table, supplying the repetitive schedule identity (WIP_ENTITY_ID), the associated LINE_ID, the primary item, BOM and routing designators, class code, supply type, completion subinventory and locator, distribution priority, line rate, tolerance data, and the standard WHO columns plus 15 descriptive flexfield attributes. WIP_LINES is joined on both LINE_ID and ORGANIZATION_ID (a two-column, multi-tenant-safe join) to supply LINE_CODE, LINE_DESCRIPTION, LINE_SCHEDULE_TYPE, LINE_MINIMUM_RATE, LINE_MAXIMUM_RATE, and LINE_FIXED_THROUGHPUT. MTL_SECONDARY_INVENTORIES is joined with an outer join (+) on SECONDARY_INVENTORY_NAME equal to COMPLETION_SUBINVENTORY and ORGANIZATION_ID equal to ORGANIZATION_ID, preserving rows whose completion subinventory is not defined at the organization level. MFG_LOOKUPS is joined on LOOKUP_TYPE = 'WIP_SUPPLY' and LOOKUP_CODE = WIP_SUPPLY_TYPE to return the meaning in WIP_SUPPLY_TEXT.

Key Columns

• ROW_ID — the ROWID of the WIP_REPETITIVE_ITEMS row, usable as a unique handle for the underlying base record.
• WIP_ENTITY_ID / LINE_ID — the repetitive schedule and production line identifiers; the primary join keys back to WIP entities and lines.
• LINE_CODE, LINE_DESCRIPTION, LINE_SCHEDULE_TYPE, LINE_MINIMUM_RATE, LINE_MAXIMUM_RATE, LINE_FIXED_THROUGHPUT — production line attributes sourced from WIP_LINES.
• WIP_SUPPLY_TEXT — the translated meaning of WIP_SUPPLY_TYPE resolved through MFG_LOOKUPS.
• PRIMARY_ITEM_ID, ALTERNATE_BOM_DESIGNATOR, ALTERNATE_ROUTING_DESIGNATOR, CLASS_CODE — the item and engineering context for the schedule.
• PRIMARY_LINE_FLAG — flags whether the line is the primary line for the repetitive schedule. This is the column most frequently referenced in searches, as it controls line assignment and defaulting logic in repetitive manufacturing.
• PRODUCTION_LINE_RATE, LOAD_DISTRIBUTION_PRIORITY — rate and prioritization data used in scheduling and line loading.
• ORGANIZATION_ID, COMPLETION_SUBINVENTORY, COMPLETION_LOCATOR_ID, LOCATOR_TYPE — organization and completion material handling context; LOCATOR_TYPE defaults to 1 via NVL when the subinventory join finds no match.
• OVERCOMPLETION_TOLERANCE_TYPE, OVERCOMPLETION_TOLERANCE_VALUE — tolerance configuration for over-completion.
• ATTRIBUTE_CATEGORY through ATTRIBUTE15 — the descriptive flexfield segment columns.
• WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and the request/program columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE) — audit and concurrent program provenance.

Common Use Cases and Queries

The view serves repetitive manufacturing reporting, production line dashboards, and interface programs that must resolve line and supply-type descriptions. A typical query returning repetitive schedules for an organization, including the primary line indicator, is:

• SELECT wip_entity_id, line_code, line_description, primary_item_id, primary_line_flag, wip_supply_text, production_line_rate FROM apps.wip_repetitive_items_v WHERE organization_id = :org_id ORDER BY wip_entity_id;
• Filtering on the primary line: SELECT wip_entity_id, line_id, line_code FROM apps.wip_repetitive_items_v WHERE organization_id = :org_id AND primary_line_flag = 'Y';
• Resolving supply type descriptions for an extract: SELECT wip_entity_id, wip_supply_type, wip_supply_text, completion_subinventory, locator_type FROM apps.wip_repetitive_items_v WHERE organization_id = :org_id AND wip_supply_type IN ('PUSH','PULL');

Because the view is read-only and its joins include an outer join to MTL_SECONDARY_INVENTORIES and an inner join to MFG_LOOKUPS, organizations with non-standard or missing WIP_SUPPLY lookup codes should verify that all WIP_SUPPLY_TYPE values have matching lookups, since unmatched rows are excluded by the inner join. For high-volume reporting, consider joining WIP_REPETITIVE_ITEMS directly to WIP_LINES when only line attributes are required.