Search Results crp_required_hours




Overview
Explore in AI Chat

Overview

CRP_REQUIRED_HOURS is a concurrent-program and reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Capacity (CRP) product family and presents required resource hours aggregated by calendar day. In the CRP planning cycle, load is generated at the operation, resource, and department level, then flattened into CRP_RESOURCE_HOURS. This view re-expresses that load against the manufacturing calendar so that planner workbenches, capacity reports, and custom dashboards can display daily capacity demand without applying calendar arithmetic themselves. Because the workload is materialized per calendar date, the view is also the natural integration point for external scheduling, MES, or APS systems that need a daily bucket of required hours keyed by resource, department, organization, and date.

Underlying Base Objects

The view is defined over seven documented base objects, resolved through public synonyms in the APPS schema:

  • CRP_RESOURCE_HOURS — the driving table of required resource load, holding basis, resource department hours, assembly usage, and setback days.
  • BOM_RESOURCES — resource definition supplying the resource code and description.
  • BOM_DEPARTMENTS — department definition supplying the department code and description.
  • MRP_SCHEDULE_DATES — supplies the schedule workdate and rate end date used to anchor each load bucket.
  • MRP_SCHEDULE_DESIGNATORS — supplies the schedule designator.
  • MTL_PARAMETERS — supplies the organization code and the calendar code and exception set that bind the query to the correct shop calendar.
  • BOM_CALENDAR_DATES — referenced four times as FIRST_DUE, LAST_DUE, FIRST_RES, and RESOURCE_DATE to translate due dates into calendar dates using backward setback offsets.

The join between CRP_RESOURCE_HOURS and the four BOM_CALENDAR_DATES aliases applies RES_HOURS.SETBACK_DAYS so that planned load lands on the correct capacity day, honoring the exception set from MTL_PARAMETERS.

Key Columns

  • RESOURCE_ID, RESOURCE_CODE, DESCRIPTION — the resource carrying the load.
  • DEPARTMENT_ID, DEPARTMENT_CODE, DESCRIPTION — the owning department.
  • ORGANIZATION_ID, ORGANIZATION_CODE — the manufacturing organization.
  • BILL_OF_RESOURCES — the routing or bill of resources referenced by the load.
  • SCHEDULE_DESIGNATOR — identifies the MPS/MRP schedule the load derives from.
  • CALENDAR_DATE — the required date, sourced from RESOURCE_DATE.CALENDAR_DATE.
  • SUM(...) aggregate — required hours for the day. When BASIS equals 1 the value is schedule quantity (or repetitive daily rate) multiplied by resource department hours and assembly usage; otherwise it is resource department hours divided across the due-date span.

Common Use Cases and Queries

Typical uses include daily capacity versus available-hours comparison, departmental load leveling, and feeding required hours to external planning tools for a given schedule designator. Most user searches for req_date resolve to CALENDAR_DATE, the required date column.

  • Resource load by day: SELECT resource_code, calendar_date, SUM(required_hours) FROM crp_required_hours WHERE organization_id = :org AND calendar_date BETWEEN :start AND :end GROUP BY resource_code, calendar_date;
  • Department load for a schedule: SELECT department_code, calendar_date, SUM(required_hours) FROM crp_required_hours WHERE schedule_designator = :desig GROUP BY department_code, calendar_date;
  • Peak-day identification: order the daily aggregate descending to locate overloaded dates.

Because CALENDAR_DATE is generated from BOM_CALENDAR_DATES, results are restricted to valid working dates in the organization calendar, and rows falling on exceptions are handled according to the exception set configured in MTL_PARAMETERS.