Results for “crp_planned_resources”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

CRP_PLANNED_RESOURCES is a table in the CRP (Capacity Requirements Planning) schema that stores the list of resources planned during a CRP run. Capacity Requirements Planning evaluates whether manufacturing resources have sufficient capacity to execute the material requirements plan produced by MRP, and this table captures the resource-level output of that evaluation. Each row represents a planned resource tied to an organization, a work order line, a department resource, and a utilization assessment. The table is owned by the CRP schema and is marked VALID in the ETRM registry for both 12.1.1 and 12.2.2, with 35 documented columns.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign key structure is link. This suggestion reflects the table's role as an intersection connecting multiple business entities: a department resource (BOM_DEPARTMENT_RESOURCES), a work in process line (WIP_LINES), and an organization. The presence of both descriptive measures (utilization, efficiency) and standard audit columns also gives it satellite-like characteristics, but the dominant modeling pattern is that of a link bridging resource and work order line contexts.

Key Information Stored

The most significant columns in CRP_PLANNED_RESOURCES fall into three groups: identifying keys, foreign references, and capacity measures.

• ORGANIZATION_ID — identifies the manufacturing organization whose capacity plan is being evaluated.
• COMPILE_DESIGNATOR — the planning compile or plan identifier grouping rows produced by a single CRP run.
• LINE_ID — foreign key to WIP_LINES, tying the planned resource to a specific work order line.
• DEPARTMENT_ID — foreign key to BOM_DEPARTMENT_RESOURCES, identifying the department that owns the resource.
• RESOURCE_ID — foreign key to BOM_DEPARTMENT_RESOURCES, identifying the specific resource within the department.
• OWNING_DEPARTMENT_ID — identifies the department that owns the resource, distinct from the performing department context.
• UTILIZATION, MIN_UTILIZATION, MAX_UTILIZATION — the plan's computed utilization and its allowed bounds.
• EFFICIENCY — the resource efficiency factor applied during the capacity calculation.
• OVERUTILIZED_PERCENT / UNDERUTILIZED_PERCENT — thresholds used to flag overloaded or underloaded resources.
• RESOURCE_SHORTAGE_TYPE / RESOURCE_EXCESS_TYPE — coded values that classify whether the resource is short or in excess.
• LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard Who-column audit trail.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard EBS descriptive flexfield (DFF) columns.

The documented metadata does not identify a surrogate primary key column explicitly. The business-key candidates are the combination of COMPILE_DESIGNATOR, ORGANIZATION_ID, LINE_ID, DEPARTMENT_ID, and RESOURCE_ID, which together uniquely distinguish a planned resource within a CRP run. The foreign key relationships define the join semantics more reliably than any single-column key.

Common Use Cases and Queries

CRP_PLANNED_RESOURCES supports capacity analysis and exception reporting. A typical query joins to BOM_DEPARTMENT_RESOURCES and WIP_LINES to display shortages and excesses per resource for a given plan:

SELECT cp.organization_id, cp.resource_id, cp.department_id,
       cp.utilization, cp.overutilized_percent, cp.resource_shortage_type
FROM   crp.crp_planned_resources cp
WHERE  cp.compile_designator = :plan_id
AND    cp.organization_id   = :org_id;

Reporting use cases include identifying overutilized resources (UTILIZATION exceeding MAX_UTILIZATION), listing all planned resources attached to a work order line via LINE_ID, and reconciling planned capacity against the department resource master. Departmental capacity dashboards typically aggregate UTILIZATION and EFFICIENCY by DEPARTMENT_ID or OWNING_DEPARTMENT_ID.

Related Objects

• BOM_DEPARTMENT_RESOURCES — joined via DEPARTMENT_ID and RESOURCE_ID; the master definition of the resource being planned.
• WIP_LINES — joined via LINE_ID; the work order line consuming the resource.
• WIP_DISCRETE_JOBS / WIP_ENTITIES — upstream work order context reached through WIP_LINES.
• BOM_DEPARTMENTS — resolves the owning and performing department identifiers.
• CRP_PLANNED_RESOURCES DFF views and the CRP planning engine — consume these rows during or after a capacity plan run.

Together these objects let developers trace a planned resource from its work order line back to the department resource definition and forward into capacity exception reports.