Search Results dispensed_qty




Overview
Explore in AI Chat

Overview

GME_MATERIAL_DISPENSING_GTMP is a Global Temporary Table (indicated by the _GTMP suffix) owned by the GME schema, which supports Oracle Process Manufacturing Process Execution. The table serves as a transient staging structure used during material dispensing transactions within process manufacturing environments, particularly for batch execution and ingredient consumption workflows in Oracle EBS 12.1.1 and 12.2.2. Because global temporary tables retain data only for the duration of a session or transaction, GME_MATERIAL_DISPENSING_GTMP typically holds intermediate dispensing records before they are validated and committed to permanent tables such as GMO_MATERIAL_DISPENSES.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign key structure identifies this object as standalone, meaning it does not exhibit the satellite or link characteristics that would bind it directly into a hub-and-link topology. This classification suggests that the table functions more as a transient operational buffer than as a persistent analytical entity, and any Data Vault implementation should treat it cautiously — it is unlikely to be a stable source for historical dimension or fact loading.

Key Information Stored

The documented physical schema for release 12.2.2 comprises eight columns. The most significant include:

  • DISPENSE_ID — The primary business identifier linking each row to its parent dispensing transaction in GMO_MATERIAL_DISPENSES. This is the sole documented foreign key reference and the natural join key.
  • SUBINVENTORY_CODE — Identifies the subinventory from which material is issued, supporting inventory accuracy and audit traceability.
  • LOCATOR_ID — The specific storage locator within the subinventory, enabling precise physical bin-level tracking.
  • LOT_NUMBER — The lot or batch identifier, critical for process manufacturing genealogy and recall management.
  • DISPENSE_UOM — The unit of measure associated with the dispensing transaction.
  • DISPENSED_QTY — The primary quantity dispensed in the designated UOM.
  • SECONDARY_DISPENSED_QTY — The quantity expressed in a secondary unit of measure, supporting dual-UOM reporting requirements.
  • REVISION — The revision code of the item or formula being dispensed, relevant for version control in regulated manufacturing.

The surrogate primary key is not explicitly documented beyond DISPENSE_ID functioning as the reference point; business-key uniqueness is typically enforced via the combination of DISPENSE_ID with lot, locator, and UOM attributes.

Common Use Cases and Queries

Typical scenarios include batch execution pre-validation, dispensing reconciliation, and ingredient usage reporting. A representative query pattern joins the temporary staging data to its parent table:

  • Reconciling staged dispensing quantities against committed records in GMO_MATERIAL_DISPENSES using DISPENSE_ID as the join predicate.
  • Lot-level traceability reports that aggregate DISPENSED_QTY and SECONDARY_DISPENSED_QTY by LOT_NUMBER, SUBINVENTORY_CODE, and LOCATOR_ID.
  • Data validation extracts filtering on DISPENSE_UOM or REVISION to detect mismatched UOM or revision discrepancy conditions before final commit.

Because the table is temporary in nature, reporting should be coupled to active dispensing sessions or interfaced into permanent staging tables for downstream analytics.

Related Objects

  • GMO_MATERIAL_DISPENSES — The direct parent reference via GME_MATERIAL_DISPENSING_GTMP.DISPENSE_ID, supplying the permanent dispensing transaction record.
  • GME_MATERIAL_DISPENSING_GTMP — Related staging variants within the same GME schema that support parallel temporary processing.
  • GMO_MATERIAL_DISPENSES line and detail tables — Supporting consumption line detail.
  • Inventory subinventory and locator master tables (MTL_SUBINVENTORIES, MTL_ITEM_LOCATIONS) — Referenced conceptually through SUBINVENTORY_CODE and LOCATOR_ID.
  • Lot master (MTL_LOT_NUMBERS) — Referenced through LOT_NUMBER for genealogy.
  • Oracle Process Manufacturing batch execution APIs — Consumers of staged dispensing data during batch close.

Together these objects confirm the table's role as a transient integration point within the dispensing transaction lifecycle.