Results for “ahl_part_changes”

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

Overview

AHL_PART_CHANGES is a transactional table in the AHL (Complex Maintenance Repair and Overhaul) product family of Oracle E-Business Suite, present and valid in both 12.1.1 and 12.2.2. It stores part change transaction details — the record of components removed from and installed onto a configured unit during maintenance, repair, or overhaul activity. Each row represents a discrete part change event tied to a unit configuration, a work order operation, or a non-routine work order, capturing what came off, what went on, when, and against which material transactions.

The table sits at the operational core of AHL part replacement processing, bridging configuration management (unit configuration headers), instance tracking (CSI item instances), work execution (work orders and operations), and inventory movement (work order material transactions). The documented foreign keys point to AHL_UNIT_CONFIG_HEADERS, CSI_ITEM_INSTANCES, AHL_RELATIONSHIPS_B, AHL_WORKORDER_OPERATIONS, AHL_WORKORDERS, and AHL_WORKORDER_MTL_TXNS.

Based on the mined foreign-key structure, the heuristic Data Vault classification for this object is a link. It resolves many-to-many style relationships among equipment structure, instances, work orders, and inventory transactions, and would typically be modeled as a link table with the referenced hubs (item instance, work order, unit configuration) connected around it. This is a modeling suggestion inferred from the documented FK topology rather than an Oracle-declared classification.

Key Information Stored

The table carries 41 documented columns. The most operationally significant are:

• PART_CHANGE_ID — the surrogate primary key, enforced by AHL_PART_CHANGES_PK and duplicated as the unique business-key candidate AHL_PART_CHANGES_U1.
• UNIT_CONFIG_HEADER_ID — links the change to the unit configuration being modified.
• REMOVED_INSTANCE_ID and INSTALLED_INSTANCE_ID — the CSI item instance taken off and the one put on, respectively.
• REMOVAL_CODE, REMOVAL_REASON_ID, and REMOVAL_DATE — the classification, reason, and timestamp for the removal side of the transaction.
• INSTALLATION_DATE — when the replacement was installed.
• PART_CHANGE_TYPE — distinguishes the nature of the change (for example, removal, installation, or swap).
• QUANTITY — quantity involved in the change event.
• STATUS_ID — current processing status of the transaction record.
• MC_RELATIONSHIP_ID — the AHL relationship definition governing the configured position.
• WORKORDER_OPERATION_ID, NON_ROUTINE_WORKORDER_ID, and WORKORDER_MTL_TXN_ID — the work-execution and inventory context, identifying the operation, non-routine work order, and material transaction.
• COLLECTION_ID, ISSUE_MTL_TXN_ID, and RETURN_MTL_TXN_ID — grouping and inventory movement references for issued and returned material.
• Audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, OBJECT_VERSION_NUMBER), SECURITY_GROUP_ID for multi-org security, and the standard ATTRIBUTE_CATEGORY / ATTRIBUTE1–ATTRIBUTE15 DFF flexfield set.

Common Use Cases and Queries

The primary use case is part-change history and traceability: reporting which component instances were swapped on a given unit configuration, by whom, and when. A typical query joins the table to CSI_ITEM_INSTANCES twice to resolve removed and installed serial numbers:

• Configuration change history — SELECT pc.PART_CHANGE_ID, pc.REMOVAL_DATE, pc.INSTALLATION_DATE, rem.SERIAL_NUMBER removed_sn, ins.SERIAL_NUMBER installed_sn FROM AHL_PART_CHANGES pc, CSI_ITEM_INSTANCES rem, CSI_ITEM_INSTANCES ins WHERE pc.REMOVED_INSTANCE_ID = rem.INSTANCE_ID(+) AND pc.INSTALLED_INSTANCE_ID = ins.INSTANCE_ID(+) AND pc.UNIT_CONFIG_HEADER_ID = :unit_config_header_id ORDER BY pc.REMOVAL_DATE;
• Work-order audit — joining WORKORDER_OPERATION_ID to AHL_WORKORDER_OPERATIONS and NON_ROUTINE_WORKORDER_ID / WORKORDER_MTL_TXN_ID to AHL_WORKORDERS and AHL_WORKORDER_MTL_TXNS to reconcile part changes against executed operations and material movements.
• Removal reason analytics — grouping by REMOVAL_CODE and REMOVAL_REASON_ID to identify recurring failure or disposal patterns.
• Instance lifecycle — filtering by REMOVED_INSTANCE_ID or INSTALLED_INSTANCE_ID to reconstruct where a specific serialized component has been installed over time.

Related Objects

The following objects are joined most often through the documented foreign keys:

• AHL_UNIT_CONFIG_HEADERS — via UNIT_CONFIG_HEADER_ID; defines the configured unit on which the change occurs.
• CSI_ITEM_INSTANCES — via REMOVED_INSTANCE_ID and INSTALLED_INSTANCE_ID; the removed and installed item instances.
• AHL_RELATIONSHIPS_B — via MC_RELATIONSHIP_ID; the configured relationship structure permitting the change.
• AHL_WORKORDER_OPERATIONS — via WORKORDER_OPERATION_ID; the operation during which the part change is executed.
• AHL_WORKORDERS — via NON_ROUTINE_WORKORDER_ID; the non-routine work order, if applicable.
• AHL_WORKORDER_MTL_TXNS — via WORKORDER_MTL_TXN_ID; the associated material transaction.
• FND_SECURITY_GROUPS — via SECURITY_GROUP_ID; multi-org security scoping.