Results for “primary_service_request_id”

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

Overview

AHL_PRD_DISPOSITIONS_B_H is the disposition history base table within the Oracle E-Business Suite Complex Maintenance, Repair, and Overhaul (AHL) module. It stores the transactional and historical record of dispositions applied to production items, capturing the decision made about a part, assembly, or component as it moves through a maintenance, repair, or overhaul workflow. In Oracle EBS 12.1.1 and 12.2.2, this table is owned by the AHL schema and is classified as VALID in the ETRM repository, with 45 documented columns in the 12.2.2 physical schema.

The table sits at the intersection of work order execution, part change management, and service request handling. Each row records the outcome of a disposition activity — for example, whether an item is to be repaired, scrapped, replaced, or returned to stock — together with the work order, operation, item instance, and organizational context in which that decision was made. Because the table preserves history (evident from the _H suffix and its companion translation history table), it is intended for audit, traceability, and historical reporting rather than as a live operational master.

From a Data Vault modeling perspective, the mined FK structure suggests a satellite-leaning classification. The table carries descriptive context and change-captured attributes around a central surrogate key, which is the typical shape of a satellite attached to a hub or link. The classification is heuristic and should be treated as a modeling suggestion rather than a documented fact.

Key Information Stored

The primary key is DISPOSITION_H_ID, a surrogate identifier that uniquely identifies each disposition history record. The unique index AHL_PRD_DISPOSITIONS_B_H_U1 enforces uniqueness on this same column, so the surrogate key and the documented unique business-key candidate coincide; there is no separate natural-key column exposed in the metadata.

The most significant columns fall into several groups:

• Disposition definition linkage: DISPOSITION_ID references the live AHL_PRD_DISPOSITIONS_B master, tying the history row to the disposition it snapshots.
• Work execution context: WORKORDER_ID, WO_OPERATION_ID, NON_ROUTINE_WORKORDER_ID, and PATH_POSITION_ID locate the disposition within a work order, its operations, and the maintenance path.
• Item identification: INVENTORY_ITEM_ID, ORGANIZATION_ID, ITEM_REVISION, ITEM_GROUP_ID, SERIAL_NUMBER, LOT_NUMBER, and INSTANCE_ID describe the specific item instance affected.
• Quantity and measures: QUANTITY and UOM record the amount and unit of measure involved.
• Disposition classification: IMMEDIATE_DISPOSITION_CODE, SECONDARY_DISPOSITION_CODE, STATUS_CODE, CONDITION_ID, and COLLECTION_ID describe the disposition outcome.
• Service and governance: PRIMARY_SERVICE_REQUEST_ID, SECURITY_GROUP_ID, and the standard who-columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, OBJECT_VERSION_NUMBER).
• Flexible attributes: ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15.

Common Use Cases and Queries

Typical reporting scenarios include disposition audit trails for a work order, item-level disposition history for warranty or reliability analysis, and reconciliation of dispositions against service requests and part changes. A common pattern joins the history table to its master and to the work order:

• Retrieve all dispositions for a work order: SELECT * FROM AHL.AHL_PRD_DISPOSITIONS_B_H WHERE WORKORDER_ID = :p_wo_id ORDER BY CREATION_DATE DESC;
• Trace a serialized item's disposition history: SELECT DISPOSITION_H_ID, INSTANCE_ID, IMMEDIATE_DISPOSITION_CODE, STATUS_CODE, CREATION_DATE FROM AHL.AHL_PRD_DISPOSITIONS_B_H WHERE INSTANCE_ID = :p_instance_id;
• Resolve the master disposition: SELECT h.DISPOSITION_H_ID, m.DISPOSITION_ID FROM AHL.AHL_PRD_DISPOSITIONS_B_H h, AHL.AHL_PRD_DISPOSITIONS_B m WHERE h.DISPOSITION_ID = m.DISPOSITION_ID;
• Summarize dispositions by organization and item for management reporting.

Related Objects

The most significant related objects, based on documented foreign keys, are:

• AHL_WORKORDERS via WORKORDER_ID and NON_ROUTINE_WORKORDER_ID.
• AHL_WORKORDER_OPERATIONS via WO_OPERATION_ID.
• AHL_PRD_DISPOSITIONS_B via DISPOSITION_ID.
• MTL_SYSTEM_ITEMS_B via INVENTORY_ITEM_ID and ORGANIZATION_ID.
• CSI_ITEM_INSTANCES via INSTANCE_ID.
• AHL_PART_CHANGES via PART_CHANGE_ID.
• AHL_MC_PATH_POSITIONS via PATH_POSITION_ID.
• CS_INCIDENTS_ALL_B via PRIMARY_SERVICE_REQUEST_ID.
• AHL_PRD_DISPOSITIONS_TL_H, which references this table through DISPOSITION_H_ID and carries translated disposition text.