Search Results wip_sub_operation_resources




Overview
Explore in AI Chat

Overview

The WIP_SUB_OPERATION_RESOURCES table is a core transactional table within the Oracle E-Business Suite Work in Process (WIP) module. It functions as the detailed repository for resource assignments at the sub-operation level for discrete and repetitive manufacturing jobs and schedules. This table is essential for capturing the specific resources, such as labor, machines, or tools, required to perform an operation, along with their associated usage, scheduling, and cost data. It directly supports shop floor execution, capacity planning, and manufacturing cost collection by maintaining the link between a production operation, its assigned resources from the Bills of Material (BOM), and the actual work performed.

Key Information Stored

The table's primary key uniquely identifies a resource assignment for a specific operation within a specific manufacturing entity. The key columns are WIP_ENTITY_ID (identifying the job or schedule), OPERATION_SEQ_NUM (the operation sequence), RESOURCE_SEQ_NUM (a unique sequence for multiple resources on the same operation), and REPETITIVE_SCHEDULE_ID (identifying the schedule for repetitive manufacturing; NULL for discrete jobs). Other critical columns include RESOURCE_ID, which links to the BOM_RESOURCES table to define the resource, and ACTIVITY_ID, which links to CST_ACTIVITIES for cost collection purposes. The table also stores planning and usage data such as UOM_CODE (unit of measure), USAGE_RATE_OR_AMOUNT, BASIS_TYPE, and SCHEDULED_QUANTITY, which define how the resource is consumed.

Common Use Cases and Queries

A primary use case is generating detailed shop floor documentation or resource loading reports. For example, a query to list all resources for a specific job would join WIP_SUB_OPERATION_RESOURCES with WIP_DISCRETE_JOBS and BOM_RESOURCES. Another critical scenario is cost analysis, where data from this table is joined with CST_ACTIVITIES and cost tables to analyze resource costs applied to a job. Troubleshooting resource assignment errors often involves querying this table to verify that resources from the routing have been correctly instantiated for a job. A common SQL pattern is:

  • SELECT wsr.RESOURCE_SEQ_NUM, br.RESOURCE_CODE, wsr.USAGE_RATE_OR_AMOUNT, wsr.UOM_CODE
  • FROM WIP_SUB_OPERATION_RESOURCES wsr, BOM_RESOURCES br
  • WHERE wsr.RESOURCE_ID = br.RESOURCE_ID
  • AND wsr.WIP_ENTITY_ID = :p_wip_entity_id
  • AND wsr.OPERATION_SEQ_NUM = :p_op_seq;

Related Objects

The table maintains defined foreign key relationships with several fundamental manufacturing and costing tables, as documented in the ETRM metadata. It references the BOM_RESOURCES table via the RESOURCE_ID column to obtain the master definition of the resource. It references the WIP_OPERATIONS table via the composite key of WIP_ENTITY_ID, OPERATION_SEQ_NUM, and REPETITIVE_SCHEDULE_ID, ensuring the resource is tied to a valid operation. For cost management, it references the CST_ACTIVITIES table via the ACTIVITY_ID column. The table is a child of WIP_OPERATIONS and is itself a parent to various transactional and costing tables that record actual resource usage and charges, such as WIP_TRANSACTION_ACCOUNTS and WIP_COST_TXN_INTERFACE.