Results for “mrp_wip_resources”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

MRP_WIP_RESOURCES is a table in the MRP (Master Scheduling/MRP) schema that stores the resource requirements and consumption details associated with discrete and repetitive jobs within Oracle EBS manufacturing. Each row represents a specific resource — such as labor, machine, or equipment — that is used at a particular operation on a work-in-process entity. The table acts as the planning-side mirror of shop-floor resource assignments, allowing the MRP and capacity planning engines to evaluate resource loads, hours required, and hours expended against scheduled and released jobs.

The ETRM metadata's heuristic Data Vault classification identifies this object as a link. This is consistent with its structure: it does not represent an independent business entity but rather an association among a work order (WIP entity), a department, a resource, and an operation, all scoped by organization and compile designator. In a Data Vault model, this table would naturally be modeled as a link table connecting the referenced hubs, carrying descriptive and measure attributes as link-level or satellite data.

Key Information Stored

The primary key, MRP_WIP_RESOURCES_PK, is a composite surrogate formed from ORGANIZATION_ID, COMPILE_DESIGNATOR, WIP_ENTITY_ID, DEPARTMENT_ID, RESOURCE_ID, OPERATION_SEQ_NUM, and RESOURCE_SEQ_NUM. A second unique index, MRP_WIP_RESOURCES_U1, contains the same set of columns and serves as the documented business-key candidate. The most significant descriptive and measure columns include:

• ORGANIZATION_ID — the inventory organization that owns the job and resource assignment.
• COMPILE_DESIGNATOR — identifies the MRP plan or compilation set under which the record was generated.
• WIP_ENTITY_ID — the work order (job) to which the resource belongs.
• DEPARTMENT_ID — the department performing the operation.
• RESOURCE_ID — the specific resource (labor, machine, or equipment) assigned.
• OPERATION_SEQ_NUM and RESOURCE_SEQ_NUM — sequencing within the routing operation and resource list.
• INVENTORY_ITEM_ID — the item being manufactured by the job.
• FIRST_UNIT_START_DATE and RESOURCE_END_DATE — scheduling boundaries for the resource usage.
• OPERATION_HOURS_REQUIRED and HOURS_EXPENDED — planned versus actual usage.
• BASIS_TYPE and RESOURCE_UNITS — the charging basis and quantity of resource applied.
• WIP_JOB_TYPE — indicates the job category (for example, discrete versus repetitive).
• Standard audit columns (LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY, REQUEST_ID, PROGRAM_ID) track who and which concurrent program produced the row.

Common Use Cases and Queries

Capacity planners and production supervisors query this table to determine resource loading across departments and periods. A typical query joins MRP_WIP_RESOURCES to a WIP entity source to report remaining hours by department:

• Resource load reporting — aggregate OPERATION_HOURS_REQUIRED and HOURS_EXPENDED by RESOURCE_ID and DEPARTMENT_ID to compare planned versus actual labor or machine usage.
• Job detail drill-down — retrieve all resource rows for a given WIP_ENTITY_ID and COMPILE_DESIGNATOR to inspect routing-level assignments.
• Capacity vs. demand analysis — join to resource availability data to identify overloaded departments for a planning horizon.
• Variance analysis — compare HOURS_EXPENDED to OPERATION_HOURS_REQUIRED to flag jobs exceeding planned resource consumption.

A representative pattern: SELECT resource_id, department_id, SUM(operation_hours_required), SUM(hours_expended) FROM mrp.mrp_wip_resources WHERE organization_id = :org AND compile_designator = :plan GROUP BY resource_id, department_id;

Related Objects

Foreign key relationships anchor this table to the central WIP entity and to the resource definition master:

• MRP_ITEM_WIP_ENTITIES — joined on INVENTORY_ITEM_ID, ORGANIZATION_ID, COMPILE_DESIGNATOR, and WIP_ENTITY_ID; parent of the job record.
• BOM_DEPARTMENT_RESOURCES — joined on DEPARTMENT_ID and RESOURCE_ID; supplies the resource master definition used by the assignment.
• WIP_DISCRETE_JOBS / WIP_REPETITIVE_SCHEDULES — transactional job tables that share the WIP_ENTITY_ID key for cross-referencing actuals.
• BOM_OPERATION_RESOURCES — the routing-level definition from which resource requirements are derived.
• MRP_WIP_COMPONENTS — companion planning table holding material rather than resource requirements for the same job.