Search Results first_res

Overview

APPS.CRP_REQUIRED_HOURS is a reporting and integration view in Oracle E-Business Suite (12.1.1 and 12.2.2) that presents capacity requirements at the resource level, expressed in hours, across a schedule's date range. It consolidates data from the CRP (Capacity Requirements Planning) resource hours table with bill of resources, department, resource, calendar, and schedule metadata to produce a flattened, human-readable result set. In ETRM terms, the view is owned by APPS and is described as a "VIEW" whose source text is provided. Its principal role is to expose computed required hours per resource per calendar date per organization, allowing planners, reports, and downstream integrations to consume capacity load without reimplementing the underlying calculation logic.

The view derives from CRP logic rather than storing data itself. The calculation at its core uses a DECODE on the BASIS column of CRP_RESOURCE_HOURS: when BASIS equals 1, required hours are computed as NVL(SCHEDULE_QUANTITY, REPETITIVE_DAILY_RATE) multiplied by NVL(RESOURCE_DEPARTMENT_HOURS, 0) multiplied by NVL(ASSEMBLY_USAGE, 1); otherwise, RESOURCE_DEPARTMENT_HOURS is divided by the span of calendar sequence numbers (LAST_DUE.SEQ_NUM - FIRST_DUE.SEQ_NUM + 1). Results are then aggregated with SUM and grouped by resource, department, schedule designator, organization, and calendar date.

Underlying Base Objects

The view is defined over a join of multiple tables, all referenced as SYNONYMs in the ETRM metadata. The documented base objects are:

• CRP_RESOURCE_HOURS — the central fact source holding resource hours, basis, setback days, assembly usage, schedule quantity, repetitive daily rate, department hours, and organization/resource/department keys.
• BOM_RESOURCES — supplies RESOURCE_CODE and DESCRIPTION for the resource.
• BOM_DEPARTMENTS — supplies DEPARTMENT_CODE and DESCRIPTION, joined on organization and department.
• MTL_PARAMETERS — provides ORGANIZATION_CODE and, importantly, the CALENDAR_CODE and CALENDAR_EXCEPTION_SET_ID used to align all calendar joins.
• MRP_SCHEDULE_DATES — provides the schedule workdate and optional RATE_END_DATE that bound the due-date range.
• MRP_SCHEDULE_DESIGNATORS — provides SCHEDULE_DESIGNATOR, the schedule identifier carried through to output.
• BOM_CALENDAR_DATES — referenced four times as aliases FIRST_DUE, LAST_DUE, FIRST_RES, and LAST_RES, plus once as RESOURCE_DATE. These aliases generate the calendar sequence ranges used in the join predicates and in the divisor of the non-BASIS-1 calculation.

The joins are anchored on the organization's calendar: RESOURCE_DATE.CALENDAR_DATE must fall between FIRST_RES and LAST_RES, exceptions sets and calendar codes must match MTL_PARAMETERS, and setback days shift first/last due sequence numbers to derive the resource window.

Key Columns

• RESOURCE_ID, RESOURCE_CODE, DESCRIPTION — identity and description of the resource.
• DEPARTMENT_ID, DEPARTMENT_CODE, DEPARTMENT DESCRIPTION — owning department context.
• BILL_OF_RESOURCES — the bill of resources identifier associated with the required hours record.
• SCHEDULE_DESIGNATOR — the MRP schedule under which requirements are calculated.
• ORGANIZATION_ID, ORGANIZATION_CODE — the inventory organization scope.
• CALENDAR_DATE — each date on which required hours are reported for the resource.
• Aggregated required hours — the SUM(DECODE(...)) expression, representing the computed capacity load in hours. Because the view text exposes this as an unaliased aggregate, consumers should confirm the runtime column alias, commonly a required-hours or load column, before referencing it.

The LAST_DUE alias is significant to the searched term "last_due": it supplies the sequence number used both to compute the calendar span divisor and to bound the schedule end via NVL(DATES.RATE_END_DATE, DATES.SCHEDULE_WORKDATE).

Common Use Cases and Queries

Typical uses include capacity load reports, resource utilization dashboards, and integration extracts feeding planning or MES systems. A representative query filters by organization and schedule:

• SELECT resource_code, department_code, schedule_designator, calendar_date, <required_hours_column> FROM apps.crp_required_hours WHERE organization_id = :org_id AND schedule_designator = :sched ORDER BY resource_code, calendar_date;
• Aggregate by resource to compare total load against available capacity:
• SELECT resource_code, SUM(<required_hours_column>) total_hours FROM apps.crp_required_hours WHERE organization_id = :org_id GROUP BY resource_code;
• Join to BOM_RESOURCES or BOM_DEPARTMENTS for additional attributes not exposed, and filter calendar_date ranges to isolate horizon periods.

Because the view performs the CRP hour expansion itself, it should be treated as a read-only reporting layer; direct DML is not supported.