Search Results gmd_technical_data_hdr_pk




Overview
Explore in AI Chat

Overview

GMD_TECHNICAL_DATA_HDR is a Process Manufacturing Product Development (GMD) table that stores the header records for technical parameter data associated with formulas, batches, items, and lots. In Oracle EBS 12.1.1 and 12.2.2, it serves as the parent container that groups technical specifications, quality parameters, and test results captured against a manufacturing entity. Each row identifies the organization, item, and optionally a specific lot, formula, or batch, providing the contextual anchor against which detailed technical data lines are stored and evaluated.

From a data modeling perspective, the heuristic Data Vault classification assigned to this object is standalone. This classification reflects that the documented physical schema does not expose foreign-key relationships originating from this table. As a modeling suggestion, this implies the table can be treated as an independent hub-like entity keyed by its surrogate identifier, with downstream dependencies represented through application logic rather than enforced referential constraints.

Key Information Stored

The table contains 17 documented columns. The most significant include:

  • TECH_DATA_ID — the surrogate primary key, defined by the unique index GMD_TECHNICAL_DATA_HDR_PK. This is the sole documented business-key candidate and uniquely identifies each header record.
  • ORGN_CODE — the organization code providing the operating context for the technical data.
  • ORGANIZATION_ID — the internal organization identifier, used to scope records to a specific inventory or process organization.
  • ITEM_ID and INVENTORY_ITEM_ID — references to the item to which the technical parameters apply.
  • LOT_ID, LOT_NUMBER, and LOT_ORGANIZATION_ID — identify the specific lot and its owning organization, enabling lot-level technical parameter tracking.
  • FORMULA_ID — links the technical data header to a formula definition.
  • BATCH_ID — links the header to a specific batch.
  • TEXT_CODE — a coded reference used to categorize or describe the technical data.
  • DELETE_MARK — the standard soft-delete indicator; a value of 1 denotes logically deleted rows that should be excluded from active queries.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — standard Oracle EBS audit columns tracking who created and last modified each record.

Common Use Cases and Queries

Typical usage centers on retrieving technical parameters for a given item, lot, or batch for quality reporting, compliance documentation, and process validation. A common query pattern filters by item and organization while excluding deleted rows:

  • SELECT h.tech_data_id, h.item_id, h.lot_number, h.formula_id, h.batch_id FROM gmd_technical_data_hdr h WHERE h.inventory_item_id = :item_id AND h.organization_id = :org_id AND NVL(h.delete_mark,0) = 0;
  • Lot-specific retrieval joins on LOT_ID and LOT_ORGANIZATION_ID to pull the exact technical parameter set recorded for a manufactured lot.
  • Formula and batch driven reporting uses FORMULA_ID and BATCH_ID to correlate technical specifications with production runs.
  • Audit and change-history reporting leverages CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and LAST_UPDATED_BY.

Related Objects

Because the object is classified as standalone, its relationships are primarily application-driven rather than enforced by foreign keys. The most significant related objects include: