Results for “ahl_prd_dispositions_b”

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

Overview

In Oracle E-Business Suite Release 12.1.1 and 12.2.2, AHL.AHL_PRD_DISPOSITIONS_B is a base table within the Complex Maintenance Repair and Overhaul (AHL) product family. It persists information about a work order's disposition — that is, the decision and associated item detail describing what is to be done with a part or assembly removed, replaced, or identified during a maintenance visit. As the "_B" suffix indicates, this is the base (non-translated) table of a multilanguage pair, with descriptive text carried in the companion AHL_PRD_DISPOSITIONS_TL table.

The table is the operational anchor for the MRO disposition process: it links a disposition record to its work order, work order operation, part change, configuration path position, inventory item and instance, and originating service request. Its structure sits at the centre of the AHL disposition model, with translated and history tables as well as material transaction, planning, and pegging tables all resolving back to it.

From a heuristic Data Vault modelling perspective, the metadata classifies this object as satellite-leaning. It holds descriptive, degenerate, and attribute columns describing a business entity, with the primary-key surrogate and multiple foreign keys. In Data Vault terms it behaves most like a satellite attached to a hub or link keyed on the disposition, but with enough embedded FK references to be treated as the operational anchor of its surrounding relationships. This is a modelling suggestion rather than a documented implementation detail.

Key Information Stored

The documented physical schema contains 44 columns. The most significant are:

• DISPOSITION_ID — surrogate primary key, constrained by AHL_PRD_DISPOSITIONS_B_PK and also the unique index AHL_PRD_DISPOSITIONS_B_U1.
• WORKORDER_ID — foreign key to AHL_WORKORDERS, identifying the work order the disposition belongs to.
• WO_OPERATION_ID — foreign key to AHL_WORKORDER_OPERATIONS, tying the disposition to a specific routing operation.
• PART_CHANGE_ID — foreign key to AHL_PART_CHANGES, linking the disposition to a part change event.
• PATH_POSITION_ID — foreign key to AHL_MC_PATH_POSITIONS, placing the disposition within the maintained configuration.
• INVENTORY_ITEM_ID and ORGANIZATION_ID — joint foreign key to MTL_SYSTEM_ITEMS_B, identifying the item and inventory organization.
• ITEM_GROUP_ID — foreign key to AHL_ITEM_GROUPS_B.
• INSTANCE_ID — foreign key to CSI_ITEM_INSTANCES, identifying the tracked item instance.
• PRIMARY_SERVICE_REQUEST_ID — foreign key to CS_INCIDENTS_ALL_B, tying the disposition to its service request.
• NON_ROUTINE_WORKORDER_ID — second foreign key to AHL_WORKORDERS, for non-routine work generated by the disposition.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enabling multi-org security filtering.
• IMMEDIATE_DISPOSITION_CODE, SECONDARY_DISPOSITION_CODE, STATUS_CODE — the disposition decision, follow-on decision, and lifecycle status of the record.
• SERIAL_NUMBER, LOT_NUMBER, QUANTITY, UOM, ITEM_REVISION — quantity and identity attributes of the affected material.

The DISPOSITION_ID column is the only documented business-key candidate (unique index U1) besides the surrogate primary key. OBJECT_VERSION_NUMBER, the five WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN), COLUMN CONDITION_ID, COLLECTION_ID, and ATTRIBUTE_CATEGORY plus ATTRIBUTE1–15 are also present for concurrency control, extensibility, and audit purposes.

Common Use Cases and Queries

Dispositions are typically queried during maintenance execution and close-out. A common pattern joins the disposition to the work order, item, and instance to produce a work-order disposition report:

• List all dispositions for a work order with item detail:

SELECT d.disposition_id, d.workorder_id, d.status_code,
       d.immediate_disposition_code, msi.segment1 item,
       d.serial_number, d.quantity, d.uom
FROM   ahl.ahl_prd_dispositions_b d,
       mtl_system_items_b msi
WHERE  d.inventory_item_id = msi.inventory_item_id
AND    d.organization_id  = msi.organization_id
AND    d.workorder_id     = :p_workorder_id;

• Reporting dispositions by service request or item instance, resolving the instance via CSI_ITEM_INSTANCES.
• Driving material transaction postings — AHL_PRD_DISP_MTL_TXNS references AHL_PRD_DISPOSITIONS_B.DISPOSITION_ID to record the inventory transactions generated by a disposition.
• Feeding planning and pegging engines: MRP/MSC tables (MSC_DEMANDS, MSC_SUPPLIES, MSC_PART_DEMANDS, MSC_RESERVATIONS, MSC_PART_PEGGING, MRP_FULL_PEGGING, and the ATP pegging tables) all carry a DISPOSITION_ID reference into this table.
• Security filtering: apply SECURITY_GROUP_ID against FND_SECURITY_GROUPS to respect multi-org access in custom reports.

Related Objects

• AHL_WORKORDERS — referenced twice (WORKORDER_ID and NON_ROUTINE_WORKORDER_ID); the primary parent entity.
• AHL_WORKORDER_OPERATIONS — via WO_OPERATION_ID, routing-level context.
• AHL_PART_CHANGES — via PART_CHANGE_ID.
• AHL_MC_PATH_POSITIONS — via PATH_POSITION_ID, configuration position in the maintained asset.
• MTL_SYSTEM_ITEMS_B — via INVENTORY_ITEM_ID and ORGANIZATION_ID.
• CSI_ITEM_INSTANCES — via INSTANCE_ID, the tracked instance.
• CS_INCIDENTS_ALL_B — via PRIMARY_SERVICE_REQUEST_ID.
• AHL_PRD_DISPOSITIONS_TL and AHL_PRD_DISPOSITIONS_TL_H — translated text and history tables keyed on DISPOSITION_ID.
• AHL_PRD_DISP_MTL_TXNS — material transactions generated from the disposition.
• AHL_PRD_DISPOSITIONS_B_H — history table, plus the MRP/MSC planning and pegging tables (MSC_DEMANDS, MSC_SUPPLIES, MSC_PART_PEGGING, and the ATP pegging family) that reference DISPOSITION_ID for supply-and-demand planning.

Together these relationships make AHL_PRD_DISPOSITIONS_B the central operational record for MRO dispositions, bridging work execution, asset configuration, inventory, service requests, and downstream planning.