Search Results crp_resource_hours




Overview
Explore in AI Chat

Overview

The CRP_RESOURCE_HOURS table is a core data repository within the Oracle E-Business Suite (EBS) Capacity (CRP) module, specifically for versions 12.1.1 and 12.2.2. It stores the summarized results of the Rough Cut Capacity Planning (RCCP) rollup process. This process aggregates resource requirements from planned orders and discrete jobs against defined bill of resources to provide a high-level view of capacity constraints. The table's primary role is to act as a reporting and analysis foundation, enabling planners to assess whether available resource capacity can meet the demands of the master production schedule before detailed planning is executed.

Key Information Stored

The table's structure is designed to link demand, resources, and the bill of materials. Its primary key is the TRANSACTION_ID, which uniquely identifies each summarized requirement record. Critical foreign key columns establish relationships to other manufacturing entities. The ASSEMBLY_ITEM_ID, BILL_OF_RESOURCES, and ORGANIZATION_ID columns link to the CRP_BILL_OF_RESOURCE_ITEMS table, identifying the assembly and its rough-cut resource list. The DEPARTMENT_ID and RESOURCE_ID columns reference BOM_DEPARTMENT_RESOURCES, pinpointing the specific resource and its department. The SOURCE_ITEM_ID and ORGANIZATION_ID link to MTL_SYSTEM_ITEMS_B, identifying the component or item driving the demand. Finally, OPERATION_SEQUENCE_ID and RESOURCE_SEQ_NUM connect to BOM_OPERATION_RESOURCES for detailed routing-based capacity checks. The table centrally stores the calculated total resource hours required for a given planning timeframe.

Common Use Cases and Queries

The primary use case is generating and analyzing rough-cut capacity reports to identify potential bottlenecks. Planners run the RCCP process, which populates this table, and then execute standard or custom reports. A typical analytical query might aggregate required hours by resource and period for a critical department. For example:

  • SELECT resource_id, department_id, SUM(total_resource_hours) FROM crp_resource_hours WHERE organization_id = :org_id GROUP BY resource_id, department_id ORDER BY 3 DESC;

Another common scenario involves comparing these rolled-up requirements against available capacity from the CRP_RESOURCE_AVAILABILITY table. Data in CRP_RESOURCE_HOURS is also used to drive graphical load profiles and capacity planning dashboards within the CRP forms. Troubleshooting data integrity often involves verifying the foreign key relationships, such as ensuring all SOURCE_ITEM_ID values exist in MTL_SYSTEM_ITEMS_B.

Related Objects

As indicated by its foreign keys, CRP_RESOURCE_HOURS is integrally connected to several foundational manufacturing tables. CRP_BILL_OF_RESOURCE_ITEMS is its direct parent, defining the rough-cut resource associations for an assembly. BOM_DEPARTMENT_RESOURCES and BOM_OPERATION_RESOURCES provide the detailed resource and routing data. MTL_SYSTEM_ITEMS_B is the master item catalog. The table is also closely related to the CRP_RESOURCE_AVAILABILITY table, which holds capacity information for comparison. From a programmatic standpoint, data is typically inserted into this table via the RCCP engine and associated concurrent programs rather than through direct DML, and it is queried by standard Oracle reports and forms within the CRP module.