Results for “crp_resource_hours”

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

Overview

CRP_RESOURCE_HOURS is a table owned by the CRP (Capacity) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Per the ETRM documentation, its description is "Results of the rollup for rough cut capacity." In practice, the table stores the computed resource-hour load generated when capacity planning programs roll up demand against resources at the department level, covering a planning horizon expressed through setback days. It is a transient, program-populated results table rather than a master or transactional entry table; rows are typically written by the rough cut capacity planning (RCCP) concurrent programs and consumed by capacity inquiry forms and reports.

From a Data Vault modeling perspective, the heuristic classification of CRP_RESOURCE_HOURS is a link. This suggestion is derived from the FK structure, which resolves relationships among items, bills of resources, departments, resources, and operations rather than holding a hub of independently identifiable business entities. The table effectively associates an assembly, a resource, a department, and an operation sequence within a planning run.

Key Information Stored

The table contains 43 columns. The most consequential are the identifiers and the calculated load figures that drive capacity reporting.

• TRANSACTION_ID — the surrogate primary key defined by CRP_RESOURCE_HOURS_PK and also the sole unique index, CRP_RESOURCE_HOURS_U1. It is a system-generated identifier, not a user-visible business key.
• ORGANIZATION_ID — the inventory organization for which capacity was rolled up; it participates in several foreign key relationships.
• ASSEMBLY_ITEM_ID, SOURCE_ITEM_ID — the manufactured assembly and the demand source item, referencing CRP_BILL_OF_RESOURCE_ITEMS and MTL_SYSTEM_ITEMS_B respectively.
• BILL_OF_RESOURCES — the bill of resources that supplied the routing/resource relationship for the rollup.
• RESOURCE_ID, DEPARTMENT_ID — the resource and department whose available hours are loaded; these reference BOM_DEPARTMENT_RESOURCES.
• OPERATION_SEQUENCE_ID, OPERATION_SEQ_NUM, RESOURCE_SEQ_NUM — identify the specific routing operation and resource occurrence within the bill of resources.
• RESOURCE_DEPARTMENT_HOURS — the computed load, in hours, placed on the resource in the department.
• LINE_ID, SETBACK_DAYS, ASSEMBLY_USAGE, ORIGINATION_TYPE, RESOURCE_UNITS, BASIS — the planning context: setback offset used during the rollup, the quantity basis, and the origin of the demand.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — the concurrent request and program that produced the row, providing traceability.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — standard EBS audit columns present on nearly every table.

Fifteen ATTRIBUTE and DDF_CONTEXT columns exist as descriptive flexfield placeholders, but they are not central to capacity computations.

Common Use Cases and Queries

The principal use case is reporting resource load by department and resource across a planning horizon. A typical query joins the resource and department names and aggregates hours:

• Aggregate RESOURCE_DEPARTMENT_HOURS by ORGANIZATION_ID, DEPARTMENT_ID, and RESOURCE_ID to produce a load profile for a planning run.
• Filter by REQUEST_ID or PROGRAM_ID to isolate the output of a specific RCCP concurrent request and reconcile to its log.
• Join to MTL_SYSTEM_ITEMS_B and CRP_BILL_OF_RESOURCE_ITEMS to trace a capacity figure back to the assembly that generated it.
• Compare RESOURCE_DEPARTMENT_HOURS against available capacity to identify overloaded resources.

Because rows are regenerated each run, queries should generally scope to the most recent REQUEST_ID to avoid double-counting historical rollups.

Related Objects

• CRP_BILL_OF_RESOURCE_ITEMS — joined on ASSEMBLY_ITEM_ID; supplies the bill of resource definition behind the load.
• BOM_DEPARTMENT_RESOURCES — joined on DEPARTMENT_ID and RESOURCE_ID; provides department resource master data.
• MTL_SYSTEM_ITEMS_B — joined on SOURCE_ITEM_ID and ORGANIZATION_ID; resolves the demand source item.
• BOM_OPERATION_RESOURCES — joined on OPERATION_SEQUENCE_ID and RESOURCE_SEQ_NUM; defines the routing operation resource.
• BOM_DEPARTMENTS and BOM_RESOURCES — supporting master tables referenced through BOM_DEPARTMENT_RESOURCES for descriptive reporting.
• RCCP concurrent programs and the capacity planning inquiry forms that populate and consume this table.