Search Results gmd_change_disposition_pk

Overview

The GMD.GMD_CHANGE_DISPOSITION table is a transactional history table within the Oracle E-Business Suite Process Manufacturing (OPM) schema, GMD. Its documented purpose is to record the history of disposition changes applied to samples, lots, and sampling events during quality and inventory operations. Each row captures a point-in-time event in which a material sample or lot was moved from one disposition state to another, preserving both the prior and resulting dispositions along with the operator, timestamp, and reason for the change.

In the context of Oracle EBS 12.1.1 and 12.2.2, this table functions as an audit and traceability artifact for the Quality Management and lot disposition processes. Because disposition states govern whether a lot or sample can be consumed, released, or quarantined, the history captured here is significant for compliance, investigation, and reporting on material status transitions.

From a Data Vault modeling perspective, the mined relationship data classifies this object as standalone. This suggests that it could be modeled effectively as a satellite table, with the natural business key represented by the disposition change event and descriptive attributes such as disposition states and grade codes. The absence of outbound foreign key dependencies in the metadata supports treating it as a leaf-level detail table rather than a link or hub.

Key Information Stored

The table contains 17 documented columns. The surrogate primary key is CHANGE_DISP_ID, which is enforced by the unique index GMD_CHANGE_DISPOSITION_PK on tablespace APPS_TS_TX_IDX. This column is the sole documented unique business-key candidate in the ETRM metadata, though it functions strictly as a surrogate identifier rather than a natural key.

The most significant descriptive columns include:

• DISPOSITION_FROM and DISPOSITION_TO — the disposition state before and after the change, forming the core of the audit record.
• SAMPLE_ID and SAMPLING_EVENT_ID — identifiers tying the disposition change to a specific sample and sampling event; SAMPLING_EVENT_ID is documented as referencing GMD.GMD_SAMPLING_EVENTS.
• ORGANIZATION_ID — the sample organization, enabling multi-organization filtering.
• LOT_NUMBER and PARENT_LOT_NUMBER — the lot affected and its parent lot, supporting lot genealogy and traceability.
• LOT_STATUS_ID — the lot status after the change.
• GRADE_CODE — the grade after the change, relevant to quality grading workflows.
• REASON_ID — the reason code associated with the disposition change.
• HOLD_DATE — the date the hold was applied.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns recording user and timestamp information.

Common Use Cases and Queries

Typical use cases center on audit reporting, lot status history, and quality investigations. A common query retrieves the disposition history for a given lot:

• SELECT CHANGE_DISP_ID, LOT_NUMBER, DISPOSITION_FROM, DISPOSITION_TO, GRADE_CODE, REASON_ID, HOLD_DATE, CREATION_DATE FROM GMD.GMD_CHANGE_DISPOSITION WHERE LOT_NUMBER = :lot_number ORDER BY CREATION_DATE DESC;
• Reporting on disposition transitions by organization and date range to identify quarantine-to-release patterns.
• Joining to GMD_SAMPLING_EVENTS on SAMPLING_EVENT_ID to correlate disposition changes with the originating sampling event.
• Auditing reason codes (REASON_ID) to analyze the frequency and cause of holds across lots.

Related Objects

The metadata documents one explicit relationship: SAMPLING_EVENT_ID references GMD.GMD_SAMPLING_EVENTS. This is the primary join path linking disposition changes to their sampling context. Additional objects that logically relate include the sample and organization tables referenced indirectly by SAMPLE_ID and ORGANIZATION_ID, as well as lot master and lot status tables implied by LOT_NUMBER and LOT_STATUS_ID. The table is referenced by GMD_CHANGE_DISPOSITION#, indicating a supplemental or history-tracking structure. Reporting queries should join to GMD_SAMPLING_EVENTS through SAMPLING_EVENT_ID and to organization and lot entities through their respective identifiers.