Search Results msc_resource_instance_reqs_u1

Overview

MSC.MSC_RESOURCE_INSTANCE_REQS is a planning table within the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) schema. It stores resource instance requirement records generated during the planning process, capturing the demand placed on individual resource instances, equipment, and departments as constrained plans are exploded and scheduled. It is a core work area table used by the MSC (Manufacturing and Supply Chain Planning) component to hold the resolved resource load attributable to discrete jobs, repetitive schedules, and flow schedules, and works in conjunction with resource requirement records to support constraint-based planning, capacity analysis, and scheduling algorithms.

From a Data Vault modeling perspective, this object is best classified as a standalone satellite (or, at minimum, a standalone descriptive store). The metadata identifies no dependency links to other hubs or links — the only foreign-key-like relationship documented is a lookup on DEPARTMENT_ID to BOM_DEPARTMENTS. This means the table is self-contained from a Data Vault standpoint and records descriptive planning facts rather than participating in a multi-table dimensional link structure.

Key Information Stored

The table contains 59 columns, of which the following are the most operationally significant:

• RES_INST_TRANSACTION_ID, PLAN_ID, SR_INSTANCE_ID — These three columns together form the documented unique index MSC_RESOURCE_INSTANCE_REQS_U1, and are the primary business-key candidates. PLAN_ID identifies the plan to which the row belongs, SR_INSTANCE_ID identifies the source instance (usually the source ERP instance), and RES_INST_TRANSACTION_ID identifies the transaction within the resource-instance requirement stream.
• SUPPLY_ID — Identifies the supply order that this resource instance requirement satisfies.
• RESOURCE_ID, RESOURCE_SEQ_NUM, OPERATION_SEQ_NUM — Identify the resource and its sequence on the routing/operation for which the requirement is generated.
• ORGANIZATION_ID, DEPARTMENT_ID — The owning organization and department (DEPARTMENT_ID referenced to BOM_DEPARTMENTS).
• RES_INSTANCE_ID, SERIAL_NUMBER, EQUIPMENT_ITEM_ID — Identify the specific resource instance (an individual machine, serial-numbered tool, or equipment item) being loaded.
• START_DATE, END_DATE — The planned start and end times of the resource requirement.
• RESOURCE_INSTANCE_HOURS, DAILY_RES_INSTANCE_HOURS, CAPACITY_CONSUMED_RATIO — The number of resource hours consumed by the instance and the fraction of capacity used.
• WIP_ENTITY_ID, BATCH_NUMBER, PARENT_ID, PARENT_SEQ_NUM, SETUP_SEQUENCE_NUM — Traceability back to the discrete job, batch, parent operation, and setup number.
• APPLIED, STATUS, UPDATED — Processing flags used by the planner to track application state of the row on the plan.
• ATTRIBUTE1–ATTRIBUTE15, ATTRIBUTE_CATEGORY — Standard Oracle EBS descriptive flexfield columns.

The table has no surrogate sequence-based primary key exposed in the documented metadata; the unique index is the closest equivalent to the business key.

Common Use Cases and Queries

Typical uses of MSC_RESOURCE_INSTANCE_REQS include capacity analysis for a given plan, identification of overloaded resource instances, drill-down from supply orders to the specific resource instance requirements, and reporting on unapplied or in-process planning rows. A common query pattern is to filter by plan and source instance and join to a resource or department dimension:

• Query all requirements for one plan: SELECT * FROM MSC.MSC_RESOURCE_INSTANCE_REQS WHERE PLAN_ID = :p AND SR_INSTANCE_ID = :s;
• Identify unapplied rows by using the N3 index columns: SELECT * FROM MSC.MSC_RESOURCE_INSTANCE_REQS WHERE PLAN_ID = :p AND SR_INSTANCE_ID = :s AND ORGANIZATION_ID = :org AND APPLIED = 'N';
• Trace a resource instance requirement back to its supply order: filter on SUPPLY_ID and join by RESOURCE_SEQ_NUM, OPERATION_SEQ_NUM for sequencing detail.
• Capacity-by-instance reporting: aggregate RESOURCE_INSTANCE_HOURS and DAILY_RES_INSTANCE_HOURS by RESOURCE_ID and DEPARTMENT_ID for a given date range using START_DATE and END_DATE.
• Reconciliation against the transactional resource requirement table by RES_INST_TRANSACTION_ID and PLAN_ID.

Related Objects

• BOM_DEPARTMENTS — Referenced by the DEPARTMENT_ID column, providing department attributes for resource requirements.
• MSC.MSC_RESOURCE_REQUIREMENTS — Parent resource requirement table at the operation level; joined by PLAN_ID, SR_INSTANCE_ID, SUPPLY_ID, and RESOURCE_SEQ_NUM.
• MSC.MSC_SYSTEM_ITEMS — Provides item attributes for EQUIPMENT_ITEM_ID and ASSEMBLY_ITEM_ID.
• MSC.MSC_PLANS — Plan definition for PLAN_ID.
• MSC.MSC_SR_INSTANCES — Source instance definitions for SR_INSTANCE_ID.
• WIP.WIP_ENTITIES / WIP_DISCRETE_JOBS — Source work-in-process job definition for WIP_ENTITY_ID.
• BOM.BOM_DEPARTMENTS and BOM.BOM_RESOURCES — Resource and department master data used to resolve resource loads.
• MRP/MSC planning worker APIs — Planning engine processes that populate and update this table during plan regeneration and scheduling.

Because this table is classified as a standalone object with only a department lookup FK, joins to most related entities are driven by business keys such as PLAN_ID, SR_INSTANCE_ID, SUPPLY_ID, and resource sequence columns rather than by declared foreign-key constraints.