Results for “ahl_resource_mappings_u1”

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

Overview

AHL_RESOURCE_MAPPINGS is a table in the AHL schema belonging to the Complex Maintenance Repair and Overhaul (CMRO) product family within Oracle E-Business Suite 12.1.1 and 12.2.2. Its purpose is to persist the mapping between an ASO (Autonomous System Organization / Oracle Service) resource definition and the equivalent BOM (Bill of Materials) resource definition. In CMRO installations, maintenance work orders, routings, and repair execution records frequently need to consume shop-floor resources that originate in the Bills of Materials module, while the service-side resource registry is maintained in the AHL/Service tables. AHL_RESOURCE_MAPPINGS bridges these two registries so that a single logical resource can be recognized in both contexts.

Based on the mined foreign-key structure, the object is best modeled as a link table in a Data Vault heuristic: it carries no descriptive payload of its own beyond standard audit and descriptive flexfield columns, and it resolves a many-to-many association between two independent hubs, AHL_RESOURCES and BOM_RESOURCES. This classification is a modeling suggestion only; the physical implementation follows the standard EBS transactional table conventions with an OBJECT_VERSION_NUMBER for optimistic locking and WHO audit columns.

Key Information Stored

The table contains 28 documented columns. The most significant are:

• RESOURCE_MAPPING_ID — surrogate primary key, enforced by AHL_RESOURCE_MAPPINGS_PK and also indexed by the unique index AHL_RESOURCE_MAPPINGS_U1. This is the single business-key candidate documented for the table.
• ASO_RESOURCE_ID — foreign key to AHL_RESOURCES, identifying the service-side (ASO) resource.
• BOM_RESOURCE_ID — foreign key to BOM_RESOURCES, identifying the manufacturing-side resource.
• BOM_ORG_ID — the BOM organization context under which the BOM resource applies, since BOM_RESOURCES is organization-scoped.
• DEPARTMENT_ID — foreign key to BOM_DEPARTMENTS, tying the mapping to a department for routing and capacity purposes.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting multi-org / data-security partitioning.
• OBJECT_VERSION_NUMBER — optimistic locking token used by the OAF/BC4J layer.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns managed by the EBS framework.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — descriptive flexfield segments available for customer-specific extension.

The surrogate key is distinct from the business-key candidate; RESOURCE_MAPPING_ID is the only documented unique identifier, and the true business uniqueness (ASO_RESOURCE_ID plus BOM_RESOURCE_ID plus BOM_ORG_ID) is not enforced by a documented unique index.

Common Use Cases and Queries

Typical scenarios include resolving which BOM resource corresponds to a given service resource when CMRO work orders are released to the shop floor, and validating that a resource selected on a maintenance routing exists in both registries. Reporting on department capacity often requires traversing this table to reconcile ASO and BOM resource usage.

• Lookup by ASO resource: SELECT bom_resource_id, bom_org_id, department_id FROM ahl.ahl_resource_mappings WHERE aso_resource_id = :p_aso_resource_id;
• Reverse lookup by BOM resource: SELECT aso_resource_id FROM ahl.ahl_resource_mappings WHERE bom_resource_id = :p_bom_resource_id AND bom_org_id = :p_org_id;
• Join to AHL_RESOURCES and BOM_RESOURCES to produce a cross-reference report of resource names, codes, and departments.
• Data-quality checks for orphan mappings or duplicate ASO/BOM pairs, since no unique constraint is documented on the business key.

Related Objects

• AHL_RESOURCES — referenced via ASO_RESOURCE_ID; the parent of the service-side resource identity.
• BOM_RESOURCES — referenced via BOM_RESOURCE_ID; the parent of the manufacturing-side resource identity.
• BOM_DEPARTMENTS — referenced via DEPARTMENT_ID; provides department context for routing and capacity.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID; enforces data security partitioning.
• AHL_RESOURCE_MAPPINGS_PK and AHL_RESOURCE_MAPPINGS_U1 — the primary key constraint and unique index defined on RESOURCE_MAPPING_ID.
• BOM_ORG_ID conceptually links to the organization definition (ORG_ORGANIZATION_DEFINITIONS), which scopes the BOM resource.