Results for “ahl_pp_resrc_req_asg_v”

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

Overview

AHL_PP_RESRC_REQ_ASG_V is an APPS-owned database view in the Oracle E-Business Suite 12.1.1 / 12.2.2 environment. It belongs to the AHL product family, which supports Complex Maintenance Repair and Overhaul (CMRO). The view exposes resource requirement assignments that link work order operations to the resources and departments that execute them, and it is designed to drive production planning, capacity review, and resource-loading reports within the AHL module.

Because it consolidates data from manufacturing bills-of-material resource definitions, AHL resource mappings, and AHL work order operations, the view presents a de-normalized, report-ready picture of which resources are expected to be applied against a given operation. It is read-only in nature; the underlying AHL processing is performed by PL/SQL packages such as AHL_COMPLETIONS_PVT, AHL_PRD_PRINT_PVT, and AHL_UTILITY_PVT, while this view serves purely as a query surface. The view is defined with a UNION, meaning it returns two logical categories of resource assignments: the primary resource assignment and the alternate resource assignment, distinguished by the ALT_PRIM_TYPE and PRIORITY columns.

Underlying Base Objects

The view is defined over a mix of synonyms, views, and lookup objects. The principal base objects are BOM_RESOURCES (the resource master, providing resource code, description, unit of measure, and resource type) and BOM_DEPARTMENT_RESOURCES, which constrains resources to departments. These are joined to AHL_RESOURCE_MAPPINGS, the bridge between a BOM resource and an AHL resource definition, and to AHL_RT_OPER_RESOURCES, which associates the AHL resource to an operation. The AHL-side operation context is supplied by AHL_WORKORDER_OPERATIONS_V, and the parent work order context is supplied by AHL_WORKORDERS_V.

Alternate-resource branches additionally draw on AHL_ALTERNATE_RESOURCES to obtain priority sequencing. Descriptive lookups come from FND_LOOKUP_VALUES_VL (for AHL_PP_RESOURCE_TYPE, resolved for lookup code PRIMARY) and MFG_LOOKUPS (for BOM_RESOURCE_TYPE). Units of measure are resolved from MTL_UNITS_OF_MEASURE via an outer join on the resource UOM code. Supporting packages referenced by the object neighborhood include FND_GLOBAL, FND_PROFILE, HR_GENERAL, HR_SECURITY, and MO_GLOBAL, providing security and organization context at runtime rather than contributing rows to the view itself.

Key Columns

• RESOURCE_CODE and RESOURCE_ID — identifier and surrogate key of the BOM resource.
• DESCRIPTION — resource description from BOM_RESOURCES.
• ALT_PRIM_TYPE — the alternate/primary indicator, derived from the FND lookup meaning.
• PRIORITY — literal 1 for the primary branch; the AHL_ALTERNATE_RESOURCES priority for alternate rows.
• DEPARTMENT_ID, WORKORDER_ID, OPERATION_ID, OPERATION_SEQUENCE_NUM — the work order and operation context.
• RESOURCE_TYPE_CODE and RESOURCE_TYPE_NAME — resource type from MFG_LOOKUPS (BOM_RESOURCE_TYPE).
• UOM_CODE — the resource unit of measure code from BOM_RESOURCES.UNIT_OF_MEASURE.
• UOM_NAME — the full unit of measure name resolved from MTL_UNITS_OF_MEASURE.

The user search term "uom_name" corresponds directly to this final column, which many users query to display readable units rather than raw codes.

Common Use Cases and Queries

Typical scenarios include resource-load review by work order operation, unit-of-measure reporting, and reconciliation of primary versus alternate resource assignments. The following sample retrieves resources for a specific work order with readable UOM text:

SELECT workorder_id, operation_id, operation_sequence_num, resource_code, description, resource_type_name, alt_prim_type, priority, uom_code, uom_name FROM apps.ahl_pp_resrc_req_asg_v WHERE workorder_id = :p_workorder_id ORDER BY operation_sequence_num, priority;

To audit unit-of-measure usage across resources:

SELECT DISTINCT resource_code, description, uom_code, uom_name FROM apps.ahl_pp_resrc_req_asg_v ORDER BY resource_code;

To separate primary assignments from alternates for a given department:

SELECT department_id, operation_id, resource_code, alt_prim_type, priority FROM apps.ahl_pp_resrc_req_asg_v WHERE department_id = :p_department_id AND alt_prim_type = 'Primary';

Because the view applies HR security and MO_GLOBAL-based organization context, query results are naturally filtered by the operating unit and organization responsibilities of the session, making it suitable for organization-scoped reporting and integration extracts without additional predicates.