Search Results wip_repetitive_items




Overview
Explore in AI Chat

Overview

The WIP_REPETITIVE_ITEMS table is a core transactional table within the Oracle E-Business Suite Work in Process (WIP) module, specifically for repetitive manufacturing. It serves as the master definition table that establishes the fundamental association between a repetitive production line and the assembly being manufactured on it. This table is critical for defining and controlling repetitive schedules, as it stores the primary item, routing, and accounting details that are applied to all production units built on a given line. Its role is to provide the static, reusable configuration for a repetitive manufacturing flow, upon which dynamic production schedules (stored in WIP_REPETITIVE_SCHEDULES) are generated and executed.

Key Information Stored

The table's primary key is a composite of WIP_ENTITY_ID and LINE_ID, uniquely identifying a specific line-assembly setup. Key columns include PRIMARY_ITEM_ID and ORGANIZATION_ID, which define the manufactured assembly. The CLASS_CODE links to WIP_ACCOUNTING_CLASSES for cost collection. The table also stores bill of material and routing designators (ALTERNATE_BOM_DESIGNATOR, ALTERNATE_ROUTING_DESIGNATOR) for specifying manufacturing processes. Inventory control is managed through COMPLETION_SUBINVENTORY and COMPLETION_LOCATOR_ID, dictating where finished units are received. Other columns track status, last updated dates, and the specific WIP_ENTITY_ID representing the repetitive schedule entity.

Common Use Cases and Queries

A primary use case is validating and reporting on the configuration of all active repetitive manufacturing lines. This is essential for production support and audit purposes. Developers often query this table to retrieve the default completion subinventory and locator for a line, or to join with item and routing tables for a complete production definition. A common reporting query pattern is:

  • SELECT wri.line_id, wri.primary_item_id, msib.segment1 item, wri.completion_subinventory, wac.class_code FROM wip_repetitive_items wri, mtl_system_items_b msib, wip_accounting_classes wac WHERE wri.primary_item_id = msib.inventory_item_id AND wri.organization_id = msib.organization_id AND wri.class_code = wac.class_code AND wri.organization_id = wac.organization_id AND wri.organization_id = :p_org_id;

This table is also central to transaction processing, as material transactions (MTL_MATERIAL_TRANSACTIONS) reference it via the REPETITIVE_LINE_ID to enforce business rules and inherit completion locations.

Related Objects

WIP_REPETITIVE_ITEMS has extensive foreign key relationships, acting as a central hub for repetitive manufacturing data. Key documented relationships include:

  • WIP_ENTITIES: Joined via WIP_ENTITY_ID. This is the parent entity record.
  • WIP_LINES: Joined via LINE_ID. Defines the production line details.
  • MTL_SYSTEM_ITEMS_B: Joined via PRIMARY_ITEM_ID and ORGANIZATION_ID. Provides the item master details for the assembly.
  • WIP_ACCOUNTING_CLASSES: Joined via CLASS_CODE and ORGANIZATION_ID. Provides cost collection accounts.
  • BOM_STRUCTURES_B: Joined via PRIMARY_ITEM_ID, ORGANIZATION_ID, and ALTERNATE_BOM_DESIGNATOR. Defines the component list.
  • BOM_OPERATIONAL_ROUTINGS: Joined via PRIMARY_ITEM_ID, ORGANIZATION_ID, and ALTERNATE_ROUTING_DESIGNATOR. Defines the manufacturing steps.
  • MTL_SECONDARY_INVENTORIES: Joined via COMPLETION_SUBINVENTORY and ORGANIZATION_ID. Validates the completion subinventory.
  • WIP_REPETITIVE_SCHEDULES: Joined via WIP_ENTITY_ID and LINE_ID. This is the critical child table holding daily production quantities and dates.
  • MTL_MATERIAL_TRANSACTIONS: Referenced by TRANSACTION_SOURCE_ID and REPETITIVE_LINE_ID for component issues and assembly completions.