Search Results wip_operations




Overview
Explore in AI Chat

Overview

The WIP_OPERATIONS table is a core transactional table within the Oracle E-Business Suite (EBS) Work in Process (WIP) module, specifically for versions 12.1.1 and 12.2.2. It serves as the master repository for all manufacturing operation sequences defined for discrete jobs and repetitive schedules. This table is fundamental to the execution and tracking of production workflows, as it stores the routing details that define the sequence of steps required to build an assembly. Each record represents a specific operation within the manufacturing process for a given work order, linking the production job to its underlying engineering and resource data from the Bills of Material (BOM) module.

Key Information Stored

The table's primary key uniquely identifies an operation using a combination of WIP_ENTITY_ID (the discrete job or repetitive schedule), OPERATION_SEQ_NUM, and REPETITIVE_SCHEDULE_ID. Key columns include WIP_ENTITY_ID, which links to WIP_DISCRETE_JOBS or WIP_REPETITIVE_SCHEDULES, and OPERATION_SEQUENCE_ID, which references the standard routing definition in BOM_OPERATION_SEQUENCES. DEPARTMENT_ID links the operation to a production department from BOM_DEPARTMENTS. The table also maintains the operational network through PREVIOUS_OPERATION_SEQ_NUM and NEXT_OPERATION_SEQ_NUM columns, which establish the sequence flow. Additional columns typically store status, scheduled dates, and counts for quantity in queue, running, and completed at the operation level.

Common Use Cases and Queries

Primary use cases involve production reporting, shop floor control, and transaction validation. Common queries include retrieving the operation sequence for a specific job to display on a work order traveler, calculating work-in-process at each operation for capacity planning, and validating move transactions against defined operation sequences. A typical query pattern joins WIP_OPERATIONS with WIP_DISCRETE_JOBS and BOM_OPERATION_SEQUENCES to get a full routing view.

  • Sample Query: Job Operation Routing
    SELECT wo.operation_seq_num, bos.operation_code, wo.department_id
    FROM wip_operations wo,
    bom_operation_sequences bos,
    wip_discrete_jobs wdj
    WHERE wo.wip_entity_id = wdj.wip_entity_id
    AND wo.operation_sequence_id = bos.operation_sequence_id
    AND wdj.job_name = '<JOB_NAME>'
    ORDER BY wo.operation_seq_num;

Related Objects

The WIP_OPERATIONS table has extensive relationships, acting as a central hub for WIP transactions and planning. As documented in the ETRM, key foreign key relationships include:

  • BOM_DEPARTMENTS: Via DEPARTMENT_ID.
  • BOM_OPERATION_SEQUENCES: Via OPERATION_SEQUENCE_ID.
  • WIP_DISCRETE_JOBS and WIP_REPETITIVE_SCHEDULES: Via WIP_ENTITY_ID and REPETITIVE_SCHEDULE_ID.
  • Self-Referential Relationships: To define the operation sequence network (PREVIOUS_OPERATION_SEQ_NUM, NEXT_OPERATION_SEQ_NUM).
  • Transaction Interfaces: WIP_MOVE_TXN_INTERFACE references it for from/to operation validation.
  • Component Tables: WIP_OPERATION_RESOURCES, WIP_SUB_OPERATION_RESOURCES, and WIP_REQUIREMENT_OPERATIONS all use its primary key to attach detailed resource and material data.
  • External Integration: Referenced by JAI_PO_OSP_LINES for outside processing.