Results for “gmd_change_disposition”

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

Overview

GMD_CHANGE_DISPOSITION is a Process Manufacturing Product Development (GMD) table that serves as the change disposition history table for the Change Disposition form. In Oracle EBS 12.1.1 and 12.2.2, the table captures an audit trail of disposition changes applied to sample lots and inventory lots during quality and product development workflows. Each row records a transition from one disposition state to another, preserving the lot identity, the sampling event context, grade assignment, and the reason for the change. The table therefore functions as a transactional history repository rather than a master data store.

The ETRM metadata classifies this object heuristically as standalone within a Data Vault model. This classification is a modeling suggestion: the table is not decomposed into separate hub, link, and satellite constructs by the source system, yet its grain — one row per disposition change event — maps naturally to a satellite pattern anchored on a lot or sample hub. Practitioners building a Data Vault layer may elect to treat CHANGE_DISP_ID as the row-level key and derive hubs for lot, sampling event, and reason.

Key Information Stored

The primary surrogate key is CHANGE_DISP_ID, enforced by the unique index GMD_CHANGE_DISPOSITION_PK. This column uniquely identifies each disposition change record and is the sole documented business-key candidate. The most significant remaining columns fall into four functional groups:

• Organizational context: ORGANIZATION_ID identifies the inventory organization in which the disposition change occurred, enabling multi-org reporting and security.
• Lot and sample identity: SAMPLE_ID, SAMPLING_EVENT_ID, PARENT_LOT_NUMBER, and LOT_NUMBER together describe the material affected. SAMPLING_EVENT_ID is a foreign key to GMD_SAMPLING_EVENTS.
• Disposition transition: DISPOSITION_FROM and DISPOSITION_TO capture the before and after disposition values, forming the core semantic payload of the history row. LOT_STATUS_ID, GRADE_CODE, and REASON_ID qualify the resulting state and justification.
• Audit and timing: HOLD_DATE, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN provide the standard EBS who/when audit footprint.

Common Use Cases and Queries

Quality analysts and supply chain users query this table to reconstruct the disposition history of a lot, to report on lots placed on hold, and to analyze grade downgrades or rejections. A typical pattern retrieves the full change trail for a lot within an organization:

• SELECT CHANGE_DISP_ID, LOT_NUMBER, DISPOSITION_FROM, DISPOSITION_TO, GRADE_CODE, HOLD_DATE FROM GMD_CHANGE_DISPOSITION WHERE LOT_NUMBER = :lot AND ORGANIZATION_ID = :org ORDER BY CREATION_DATE;
• Hold analysis: filter on HOLD_DATE to identify lots currently or previously held, joining REASON_ID to the reason code reference for root-cause reporting.
• Disposition trend reporting: aggregate counts of DISPOSITION_FROM to DISPOSITION_TO transitions by organization and period to measure quality performance.
• Integration extracts: the table is frequently staged into a warehouse as the historical fact for lot disposition, using CHANGE_DISP_ID as the change data capture key.

Related Objects

The documented foreign key relationship points from GMD_CHANGE_DISPOSITION.SAMPLING_EVENT_ID to GMD_SAMPLING_EVENTS, making that table the primary parent for sampling-driven disposition events. Additional relationships are implied by the column set and typical GMD integration surface:

• GMD_SAMPLING_EVENTS — joined on SAMPLING_EVENT_ID; supplies the sampling context for each disposition change.
• GMD_SAMPLES / sample tables — associated via SAMPLE_ID where sample master data resides.
• Grade and reason reference tables — referenced by GRADE_CODE and REASON_ID for lookup decoding.
• Lot status reference — referenced by LOT_STATUS_ID to translate the resulting status.
• MTL_LOT_NUMBERS and inventory lot objects — correlated through ORGANIZATION_ID and LOT_NUMBER for inventory-side reconciliation.

Joins should be driven from CHANGE_DISP_ID for row identity and from SAMPLING_EVENT_ID for parent context, honoring the standalone classification while preserving the documented referential path.