Results for “ahl_resource_mappings_v”

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

Overview

The APPS.AHL_RESOURCE_MAPPINGS_V view is a reporting and integration artifact within the Oracle E-Business Suite product family AHL — Complex Maintenance Repair and Overhaul (CMRO). Its primary role is to reconcile two distinct resource registries: the maintenance-centric resource definitions used by the AHL work execution engine (the ASO resource) and the discrete manufacturing resource definitions maintained in Oracle Bills of Material (BOM). By exposing a denormalized, human-readable join of these registries, the view enables implementers and integrators to confirm that an AHL resource has been correctly mapped to the corresponding BOM resource within a specific manufacturing organization. The view is owned by the APPS schema, is marked VALID in the ETRM 12.2.2 documentation set, and is applicable across the 12.1.1 and 12.2.2 code lines. Because resource mapping determines which shop-floor resources are available for a given work order operation, the view is frequently interrogated during CMRO implementation validation, data migration reconciliation, and interface troubleshooting. The user search term bom_org_id corresponds directly to a key column of this view, reflecting the common need to filter resource mappings by manufacturing organization.

Underlying Base Objects

The view is defined over the base table AHL_RESOURCE_MAPPINGS, which stores the authoritative mapping records, joined to three reference objects. The documented referenced base objects are AHL_RESOURCE_MAPPINGS (SYNONYM), BOM_DEPARTMENTS (SYNONYM), BOM_RESOURCES (SYNONYM), HR_ORGANIZATION_UNITS (VIEW), MFG_LOOKUPS (VIEW), plus the HR_GENERAL and HR_SECURITY packages that supply organization and security context. The core join is:

• R.BOM_RESOURCE_ID = BOM.RESOURCE_ID
• R.BOM_ORG_ID = BOM.ORGANIZATION_ID
• R.BOM_ORG_ID = HOU.ORGANIZATION_ID
• MFG.LOOKUP_TYPE (+) = 'BOM_RESOURCE_TYPE' AND MFG.LOOKUP_CODE (+) = BOM.RESOURCE_TYPE (outer join)

The ORG_ID column on AHL_RESOURCE_MAPPINGS is thus the pivot that binds the manufacturing resource to its owning organization unit. Because HR_ORGANIZATION_UNITS is itself an HR-security-governed object, effective access to the view is constrained by the HR_SECURITY package, and results are filtered according to the operating unit and organization hierarchy to which the session is exposed.

Key Columns

The view projects both the mapping identity and descriptive attributes of the underlying BOM resource. Significant columns include:

• RESOURCE_MAPPING_ID — primary key of the mapping record.
• ASO_RESOURCE_ID — the AHL/ASO-side resource identifier.
• BOM_RESOURCE_ID and BOM_ORG_ID — the manufacturing resource and the inventory organization in which it is defined.
• BOM_RESOURCE_CODE, BOM_ORG_NAME, DESCRIPTION, DISABLE_DATE — the resource code, organization name, description, and effective disable date.
• BOM_RESOURCE_TYPE and BOM_RESOURCE_TYPE_ID — the lookup meaning (e.g., Machine, Person, Department) derived from MFG_LOOKUPS.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard DFF columns available for customer extensions.
• Standard WHO columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER) for audit and optimistic locking.

Common Use Cases and Queries

Typical usage includes verifying that every AHL resource has a BOM counterpart in the intended organization, auditing disabled or expired mappings, and driving migration extracts. A representative query filtering by organization (the user's bom_org_id search) is:

SELECT RESOURCE_MAPPING_ID, ASO_RESOURCE_ID, BOM_RESOURCE_ID, BOM_RESOURCE_CODE, BOM_ORG_NAME, BOM_RESOURCE_TYPE, DISABLE_DATE FROM APPS.AHL_RESOURCE_MAPPINGS_V WHERE BOM_ORG_ID = :p_org_id ORDER BY BOM_RESOURCE_CODE;

Because the view applies HR security and outer-joins the lookup table, reports should treat BOM_RESOURCE_TYPE as potentially null and pass the organization identifier explicitly rather than relying on session defaults.