Search Results crp_resource_plan




Overview
Explore in AI Chat

Overview

The CRP_RESOURCE_PLAN table is a core data object within the Oracle E-Business Suite Capacity (CRP) module. It serves as the primary repository for storing capacity resource plan data. This table is fundamental to the application's ability to model, analyze, and manage resource capacity against production demands. The resource plan data stored here is typically generated by the system's planning engines to provide a detailed view of resource utilization, enabling planners to identify bottlenecks and optimize production schedules. Its role is integral to the closed-loop manufacturing planning process, linking high-level planning recommendations to detailed capacity analysis.

Key Information Stored

While the provided ETRM metadata is concise, the table's structure and relationships indicate the nature of its data. The primary key, TRANSACTION_ID, uniquely identifies each resource plan record. A critical foreign key column is SOURCE_TRANSACTION_ID, which links the capacity plan back to its originating source transaction, typically a specific recommendation from the Master Production Schedule (MPS) or Material Requirements Planning (MRP) engine. Although specific column details are not listed, a table of this nature in the CRP module would commonly store information such as resource code, department, start and end dates for the planning bucket, available capacity, total required load, and the calculated utilization percentage. This data collectively forms a time-phased resource capacity plan.

Common Use Cases and Queries

The primary use case for the CRP_RESOURCE_PLAN table is reporting and analysis of capacity constraints. Planners execute queries to compare available resource hours against planned and scheduled load. A common SQL pattern involves joining to the MRP_RECOMMENDATIONS table to understand the demand driving the resource requirements. For instance, a report identifying over-utilized resources might follow this pattern:

  • SELECT crp.resource_code, crp.plan_date, crp.available_hours, crp.required_hours FROM crp_resource_plan crp WHERE (crp.required_hours / crp.available_hours) > 1;

Another critical use case is tracing capacity requirements back to specific manufacturing or planned orders, achieved by joining via SOURCE_TRANSACTION_ID to MRP_RECOMMENDATIONS and related order tables. Data from this table is also essential for graphical capacity planning views within the Oracle EBS user interface.

Related Objects

The documented relationship data specifies a direct foreign key dependency for this table. The CRP_RESOURCE_PLAN table has a defined relationship where its SOURCE_TRANSACTION_ID column references the MRP_RECOMMENDATIONS table. This is a crucial link in the planning architecture, tethering capacity plans to the specific material planning recommendations that generated the demand. The primary key constraint CRP_RESOURCE_PLAN_PK on the TRANSACTION_ID column ensures the integrity of this table as a target for other potential relationships within the CRP schema, such as detailed resource assignments or utilization histograms, which are not explicitly detailed in the provided excerpt but are common in this module.