Search Results gmo_dispense_area_tl




Overview
Explore in AI Chat

Overview

GMO_DISPENSE_AREA_TL is the translation table for dispense areas within the Oracle E-Business Suite Manufacturing Execution System for Process Manufacturing (GMO/OPM) module. A dispense area defines a physical or logical staging location from which ingredients are weighed, dispensed, and issued to a batch or work order during the execution of a process manufacturing recipe. Because Oracle EBS supports multiple installed languages, the base table GMO_DISPENSE_AREA_B stores language-independent attributes, while GMO_DISPENSE_AREA_TL stores the language-specific descriptive text that accompanies each dispense area record.

The table resides in the GMO schema and is classified as VALID in the ETRM 12.2.2 repository, with documented parity to 12.1.1. Under the heuristic Data Vault classification mined from its foreign key structure, the table is characterized as standalone. Modeling-wise, it may be treated as a satellite-like descriptor table, keyed to the dispense area hub (GMO_DISPENSE_AREA_B) and carrying translated attributes rather than participating in transactional links. Practically, it functions as the multilingual text extension of the dispense area master data.

Key Information Stored

The physical schema documents nine columns. The most significant are:

  • DISPENSE_AREA_ID — Surrogate identifier of the dispense area. Along with LANGUAGE, it forms the primary key GMO_DISPENSE_AREA_TL_PK and is also the foreign key referencing GMO_DISPENSE_AREA_B.
  • LANGUAGE — The installed Oracle language code (for example, US or DE) identifying the translation row. It is the second component of both the primary key and the unique business-key candidate index.
  • DISPENSE_AREA_DESC — The translated description or name of the dispense area, presented to users in their session language.
  • SOURCE_LANG — The language in which the source description was originally entered, used by the translation framework to track derivation.
  • CREATED_BY, CREATION_DATE — Standard audit columns recording who inserted the row and when.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE — Audit columns recording the most recent change and its author.
  • LAST_UPDATE_LOGIN — The login/session identifier associated with the last update.

The unique index GMO_DISPENSE_AREA_TL_PK (DISPENSE_AREA_ID, LANGUAGE) is the documented business-key candidate; DISPENSE_AREA_ID alone is the surrogate-to-source link, not a standalone unique key.

Common Use Cases and Queries

Typical uses include multilingual dispense-area lookups on batch execution and dispensing screens, translation maintenance for OPM master data, and reporting on dispense area labels. A standard join retrieves the translated description alongside the base row:

  • SELECT b.dispense_area_id, t.dispense_area_desc, t.language FROM gmo_dispense_area_b b, gmo_dispense_area_tl t WHERE b.dispense_area_id = t.dispense_area_id AND t.language = USERENV('LANG');
  • Detecting missing translations: outer-join the base table to the TL table and filter where DISPENSE_AREA_DESC IS NULL for a given LANGUAGE.
  • Auditing change history using CREATION_DATE, LAST_UPDATE_DATE, and LAST_UPDATED_BY for translation governance.

Related Objects

  • GMO_DISPENSE_AREA_B — Base (language-independent) dispense area table; joined on DISPENSE_AREA_ID and referenced by the documented foreign key.
  • GMO_DISPENSE_AREA_TL_PK — Unique index enforcing the (DISPENSE_AREA_ID, LANGUAGE) business key.
  • OPM dispensing and batch execution entities — Transactional tables that consume DISPENSE_AREA_ID to place material issues and weights.
  • FND_LANGUAGES — Reference for valid LANGUAGE and SOURCE_LANG values.
  • FND_USER / audit views — Interpretation of CREATED_BY and LAST_UPDATED_BY.

Because GMO_DISPENSE_AREA_TL is a pure text satellite, direct DML is discouraged; translations should be maintained through supported OPM setup and translation utilities to preserve referential integrity with GMO_DISPENSE_AREA_B.