Search Results crp_planned_resources




Overview
Explore in AI Chat

Overview

The CRP_PLANNED_RESOURCES table is a core data repository within the Oracle E-Business Suite (EBS) Capacity Requirements Planning (CRP) module. It functions as the transactional ledger for capacity planning runs, storing a detailed list of all manufacturing resources that have been planned or scheduled during a specific CRP simulation or execution. This table is critical for analyzing the capacity load placed on resources (machines, labor, departments) against their available capacity, enabling planners to identify bottlenecks and optimize production schedules. Its existence is fundamental to the CRP module's purpose of performing detailed, resource-level capacity analysis based on material and production plans.

Key Information Stored

While the provided metadata does not list specific columns, the table's description and foreign key relationships define its essential data structure. It primarily stores identifiers that link planned resource usage to master data and transactional entities. Key fields logically include a unique identifier for the CRP plan or run, the planned resource quantity or hours, and dates for the planned activity. Crucially, the documented foreign keys confirm it stores the DEPARTMENT_ID and RESOURCE_ID, linking directly to BOM_DEPARTMENT_RESOURCES to define the specific resource within a department. It also stores a LINE_ID, linking to WIP_LINES, which ties the planned resource consumption to a specific production line or assembly line context.

Common Use Cases and Queries

This table is central to post-CRP run analysis and custom capacity reporting. A primary use case is generating a detailed resource load report by joining to resource and department master data. Planners often query this table to compare planned resource hours against available capacity from related tables. Common SQL patterns involve filtering by a specific CRP plan name or date range and aggregating planned hours by resource or department. For instance, a query to identify overloaded resources might join CRP_PLANNED_RESOURCES to BOM_DEPARTMENT_RESOURCES and a capacity calendar table, summing planned units and comparing them to available shifts. Data from this table is also used to populate or feed the graphical capacity planning dashboards and workbenches within the EBS interface.

Related Objects

The table maintains defined foreign key relationships with two key manufacturing tables, as per the provided metadata:

  • BOM_DEPARTMENT_RESOURCES: This relationship, via DEPARTMENT_ID and RESOURCE_ID, ensures that every planned resource entry corresponds to a valid, defined resource within a department master. This join is essential for retrieving resource descriptions, cost rates, and availability profiles.
  • WIP_LINES: The relationship via LINE_ID connects the planned resource usage to a specific manufacturing line. This allows capacity analysis to be segmented by production line, which is vital for discrete manufacturing environments.

As a transactional table for the CRP module, it is also intrinsically linked to the parent CRP plan header table (commonly named like CRP_PLANS or similar, though not listed in the metadata) which defines the overall planning run parameters and scope.