Search Results resource_utilization




Overview
Explore in AI Chat

Overview

APPS.MRPBV_PLAN_DEPT_RESOURCES is a Business Intelligence System (BIS) view in the Oracle E-Business Suite APPS schema, registered under FND Design Data as MRP.MRPBV_PLAN_DEPT_RESOURCES. Its documented purpose is to present the departments and resources associated with a plan, exposing the planned resource load alongside the departmental and organizational context in which that load is incurred. In practice the view answers the question "which resources, in which departments, are consumed by a given plan, and at what utilization and efficiency?" — which is precisely the semantics users are seeking when they search for resource_utilization.

Because the object is a view rather than a table, it is a read-only reporting artifact. It is not referenced by any other database object, so it does not participate in the EBS transaction-processing chain; its role is confined to query, reporting, and integration. It is a conventional candidate for ad-hoc SQL, custom concurrent programs, Oracle Discoverer / BI Publisher datasets, and outbound extracts into capacity and scheduling dashboards.

Underlying Base Objects

The view is defined over five APPS synonyms, each resolving to a base EBS table:

  • CRP_PLANNED_RESOURCES — the primary fact source, holding planned resource capacity/load records.
  • BOM_DEPARTMENTS — departmental definitions, supplying department code and department identifiers.
  • BOM_RESOURCES — resource definitions, supplying resource code and related resource attributes.
  • HR_ALL_ORGANIZATION_UNITS — organization master, supplying organization name and inventory organization identifiers.
  • MTL_PARAMETERS — inventory organization parameters, supplying the organization code.

The join strategy is therefore a straightforward dimensional enrichment: planned-resource rows are resolved to their department, resource, and owning organization, then decorated with human-readable codes and names from HR and MTL. All base objects are accessed through APPS synonyms, so the view is subject to standard EBS security via the underlying tables rather than exposing any bespoke security logic of its own.

Key Columns

Common Use Cases and Queries

Typical scenarios include capacity-versus-load reviews by department, identification of bottleneck resources within a plan, and feed of utilization/efficiency figures into external planning or costing models.

Resource utilization across a plan:

SELECT plan_name, organization_code, department_code, resource_code,
       resource_utilization, resource_efficiency
FROM   apps.mrpv_plan_dept_resources
WHERE  plan_name = :plan
ORDER  BY organization_code, department_code, resource_code;

Aggregate load by department:

SELECT organization_code, department_code,
       SUM(resource_utilization) total_utilization
FROM   apps.mrpv_plan_dept_resources
WHERE  plan_name = :plan
GROUP  BY organization_code, department_code
ORDER  BY total_utilization DESC;

Join the view back to BOM_RESOURCES or CRP_PLANNED_RESOURCES using RESOURCE_ID, DEPARTMENT_ID, and ORGANIZATION_ID when additional base-table attributes are required. Because the view carries no row-level security of its own, access should be granted and constrained through responsibility and MO: Security Profile configuration.