Search Results crp_24hr_available_hours




Overview
Explore in AI Chat

Overview

CRP_24HR_AVAILABLE_HOURS is an Oracle E-Business Suite APPS schema view published under the CRP (Capacity) product family. It exposes the daily available capacity of resources that have been flagged as operating on a 24-hour basis. Unlike standard capacity calculations that derive working time from shift patterns and calendar exceptions, this view bypasses shift logic and computes availability as a flat multiple of the calendar day, using the resource's capacity units multiplied by 24.

The object is read-only and carries a VALID status in both 12.1.1 and 12.2.2. It serves reporting and integration purposes rather than transactional processing: capacity planners, manufacturing engineers, and custom dashboards use it to reconcile the theoretical capacity of continuously available resources against the calendars assigned at the organization level. Because the view resolves department sharing relationships, it also reflects capacity delegated from an owning department to a sharing department via the SHARE_FROM_DEPT_ID attribute.

Underlying Base Objects

The view is defined over five documented base objects, all referenced through APPS synonyms:

  • BOM_DEPARTMENT_RESOURCES — the central table; joined twice, once as DEPT_RES (the reporting department/resource assignment) and once as OWNER_RES (the owning department supplying capacity).
  • BOM_DEPARTMENTS — supplies department code and description.
  • BOM_RESOURCES — supplies resource code, description, and organization.
  • BOM_CALENDAR_DATES — supplies individual calendar dates; rows with a null SEQ_NUM are excluded.
  • MTL_PARAMETERS — supplies the organization code and the organization's assigned calendar and exception set, which filter the calendar dates.

The join condition applies NVL(DEPT_RES.SHARE_FROM_DEPT_ID, DEPTS.DEPARTMENT_ID) against OWNER_RES.DEPARTMENT_ID, ensuring that shared resources draw capacity from the originating department when one exists. Organization IDs on departments, resources, and MTL_PARAMETERS must all match, which keeps the result set organization-scoped.

Key Columns

Common Use Cases and Queries

Typical scenarios include verifying that 24-hour resources show full-day availability regardless of shift definitions, auditing shared-department capacity, and feeding custom capacity dashboards. A representative query lists availability for a specific organization and date range:

  • SELECT organization_code, dept_code, res_code, available_date, available_hours FROM apps.crp_24hr_available_hours WHERE organization_code = :org AND available_date BETWEEN :start_date AND :end_date ORDER BY dept_code, res_code, available_date;
  • SELECT dept_code, res_code, SUM(available_hours) total_hours FROM apps.crp_24hr_available_hours WHERE available_date BETWEEN :start_date AND :end_date GROUP BY dept_code, res_code;
  • SELECT * FROM apps.crp_24hr_available_hours WHERE res_code = :resource_code;

Because the view aggregates by department, resource, and date, results can be joined to BOM_DEPARTMENT_RESOURCES for further detail or to CRP capacity tables for comparison against planned load. As with all APPS views, querying through a reporting responsibility with appropriate MOAC security is recommended.