Search Results msc_resource_requirements




Overview
Explore in AI Chat

Overview

The MSC_RESOURCE_REQUIREMENTS table is a core transactional table within the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) module. It serves as the central repository for all detailed resource capacity consumption data generated by the planning engine. Specifically, it stores the resource requirements that are calculated based on existing supplies, such as planned orders, work orders, and purchase orders, within a given manufacturing or supply chain plan. This table is critical for performing detailed capacity planning and resource load analysis, enabling planners to identify bottlenecks and ensure that production schedules are feasible given finite resource constraints. Its integrity is maintained through a complex network of foreign key relationships to other fundamental planning tables.

Key Information Stored

The table's primary key uniquely identifies each resource requirement record through a combination of PLAN_ID, SR_INSTANCE_ID (representing the specific instance of the planning server or source system), and TRANSACTION_ID. Key columns define the context and specifics of the requirement. The PLAN_ID links the requirement to a specific planning run. SUPPLY_ID connects it to the originating supply in the MSC_SUPPLIES table. The requirement is further detailed by its association to a specific manufacturing process via ROUTING_SEQUENCE_ID, OPERATION_SEQUENCE_ID, and RESOURCE_SEQ_NUM, which together pinpoint the exact operation and resource within a routing. The RESOURCE_ID and ALTERNATE_NUM identify the specific resource and its alternate designation. The PARENT_ID column supports hierarchical relationships between requirements, allowing for complex, multi-level resource structures.

Common Use Cases and Queries

The primary use case is analyzing resource load and capacity utilization for a specific plan. Planners and analysts query this table to generate reports showing total required hours per resource, broken down by department, work center, or item. A typical query involves joining to MSC_RESOURCES for resource details and MSC_SUPPLIES for supply information. For example, to find total resource requirements for a critical resource in a plan, one might use:

  • SELECT mr.RESOURCE_CODE, SUM(mrr.UNIT_REQUIREMENT) TOTAL_HOURS
  • FROM MSC_RESOURCE_REQUIREMENTS mrr, MSC_RESOURCES mr
  • WHERE mrr.PLAN_ID = :p_plan_id
  • AND mrr.RESOURCE_ID = mr.RESOURCE_ID
  • AND mrr.SR_INSTANCE_ID = mr.SR_INSTANCE_ID
  • AND mr.RESOURCE_CODE = 'CRITICAL_MACHINE_01'
  • GROUP BY mr.RESOURCE_CODE;

Another common scenario is tracing resource requirements back to their source supplies to understand what specific orders are causing a capacity overload, which involves joining to MSC_SUPPLIES and potentially MSC_ITEMS.

Related Objects

MSC_RESOURCE_REQUIREMENTS is intricately linked to several other core ASCP tables, as defined by its foreign keys. Its most critical relationship is with MSC_SUPPLIES, which provides the source demand. It is also fundamentally tied to the manufacturing process data through MSC_ROUTINGS, MSC_OPERATION_RESOURCE_SEQS, and MSC_OPERATION_RESOURCES. The table has a self-referential relationship via the PARENT_ID column, allowing for parent-child requirement hierarchies. Data from this table is often aggregated and presented through planning-specific views or user interfaces within the ASCP workbench, which provide more user-friendly access to capacity planning information.