Results for “owner_res”

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

Overview

APPS.CRP_24HR_AVAILABLE_HOURS is a reporting view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments that exposes the daily, calendar-driven capacity of manufacturing resources that have been flagged as available on a 24-hour basis. Its name reflects its principal function: it aggregates the capacity_units of 24-hour resources and multiplies that quantity by 24 to produce the effective available hours for each resource and each calendar date within the organization's manufacturing calendar.

The view is most commonly invoked within the capacity requirements planning (CRP) and production scheduling domain, where the planning engine and downstream reports must determine how many working hours a resource offers on a given day. Rather than computing this from raw department and resource records each time, the view consolidates the relevant joins. The user search term "owner_res" directly references the OWNER_RES alias used in the view’s defining SQL, which represents the owning department-resource relationship when a resource is shared between departments.

Underlying Base Objects

The ETRM metadata documents the view as defined over the following base objects, each referenced through a synonym in the APPS schema:

• BOM_CALENDAR_DATES – provides the working calendar dates and sequence numbers used to enumerate availability days.
• BOM_DEPARTMENTS – supplies department identifiers, codes, and descriptions.
• BOM_DEPARTMENT_RESOURCES – the central table linking departments and resources, including the AVAILABLE_24_HOURS_FLAG and SHARE_FROM_DEPT_ID used to resolve shared ownership.
• BOM_RESOURCES – provides the resource code, description, and organization context for each resource.
• MTL_PARAMETERS – supplies the organization’s calendar code and calendar exception set, aligning availability days to the correct organizational calendar.

Because the view is built over these tables, changes to resource sharing flags, department assignments, or calendar definitions are immediately reflected in the view’s output.

Key Columns

• DEPARTMENT_ID, DEPARTMENT_CODE, DESCRIPTION – identifying attributes of the department that holds or shares the resource.
• RESOURCE_ID, RESOURCE_CODE, DESCRIPTION – identifying attributes of the resource itself.
• ORGANIZATION_ID, ORGANIZATION_CODE – the operating unit/organization in which the resource and department are defined.
• CALENDAR_DATE – the specific working date for which availability is calculated.
• SUM(OWNER_RES.CAPACITY_UNITS * 24) – the aggregated available hours, computed as the owning department-resource capacity units multiplied by 24 and summed across matching owner resource rows.

The grouping is applied across department, resource, organization, and calendar date attributes, producing one row per resource per date combination.

Common Use Cases and Queries

Planners and technical developers use this view to validate capacity assumptions, feed scheduling reports, and troubleshoot discrepancies between planned and available resource hours. A typical query retrieves the available hours for a specific organization over a date range:

• Capacity verification: compare available hours against scheduled load for a given resource on a specific CALENDAR_DATE.
• Cross-organization reporting: aggregate available hours by ORGANIZATION_CODE to support multi-org capacity analysis.
• Shared-resource analysis: identify resources whose hours arise from a shared owner department by examining the department and resource combination.

A sample SQL statement follows:

SELECT organization_code, resource_code, calendar_date, SUM(capacity_hours)
FROM apps.crp_24hr_available_hours
WHERE organization_code = 'M1'
AND calendar_date BETWEEN :start_date AND :end_date
GROUP BY organization_code, resource_code, calendar_date
ORDER BY resource_code, calendar_date;

Such queries make the view particularly useful where a resource is available around the clock and its capacity must be expressed in true working hours rather than nominal capacity units.