Search Results gmo_dispense_area_b




Overview
Explore in AI Chat

Overview

GMO_DISPENSE_AREA_B is the base table that defines dispense areas within the Oracle E-Business Suite Manufacturing Execution System for Process Manufacturing (GMO) module. A dispense area represents a physically or logically distinct staging location — such as a weigh-and-dispense booth, a staging lane, or a controlled dispensing room — from which operators draw and dispense ingredient materials against production batches. The table resides in the GMO schema and holds 11 documented columns in ETRM 12.2.2. It is the transactional anchor for dispensing activities, referenced by planning, execution, storage, and material movement records throughout the GMO data model.

From a Data Vault modeling perspective, the mined foreign-key structure classifies this object heuristically as standalone, but given that it carries a surrogate primary key (DISPENSE_AREA_ID) and descriptive attributes such as DISPENSE_AREA_NAME, DEFAULT_AREA_IND, and NUMBER_OF_TASKS_PER_DAY, it is most naturally modeled as a hub with an associated satellite holding the descriptive and defaulting attributes. Consumers should treat the classification as a suggestion rather than a rigid schema decision.

Key Information Stored

The table is keyed on the surrogate primary key DISPENSE_AREA_ID, enforced by the unique index GMO_DISPENSE_AREA_B_PK. This surrogate is the value propagated to all referencing tables. The most significant columns are:

  • DISPENSE_AREA_ID — surrogate primary key; unique identifier of the dispense area.
  • ORGANIZATION_ID — the inventory organization to which the dispense area belongs; the primary scoping/partitioning attribute for multi-org queries.
  • DISPENSE_AREA_NAME — the user-facing name of the dispense area, used in operator screens and reports.
  • DEFAULT_AREA_IND — flag denoting whether the area is the default dispense area for the organization.
  • SUBINVENTORY_CODE — the subinventory from which material is drawn for dispensing in this area.
  • NUMBER_OF_TASKS_PER_DAY — a capacity/throughput attribute controlling how many dispensing tasks the area is expected to process per day.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns capturing who created and last modified the row and when.

The documented unique index covers only DISPENSE_AREA_ID, so the true business key — likely the combination of ORGANIZATION_ID and DISPENSE_AREA_NAME — is not enforced by a separate unique constraint in the metadata.

Common Use Cases and Queries

Typical scenarios include listing all active dispense areas in an organization, identifying the default area, and driving operator task assignment and dispense volume reporting. A representative query follows:

  • SELECT dispense_area_id, dispense_area_name, subinventory_code FROM gmo_dispense_area_b WHERE organization_id = :org_id AND default_area_ind = 'Y';
  • Join to GMO_MATERIAL_DISPENSES and GMO_MATERIAL_UNDISPENSES on DISPENSE_AREA_ID to reconcile dispensed versus undis­pensed quantities by area.
  • Join to GMO_DISPENSING_PLANNING to evaluate planned task load against NUMBER_OF_TASKS_PER_DAY for capacity utilization reporting.
  • Join to GMO_DISPENSE_AREA_TL on DISPENSE_AREA_ID to retrieve translated dispense area names for multilingual reporting.

Related Objects

The following objects reference GMO_DISPENSE_AREA_B through the DISPENSE_AREA_ID foreign key, and are the primary join partners for transactional and reporting work:

  • GMO_DISPENSING_PLANNING — planned dispensing activity per dispense area.
  • GMO_MATERIAL_DISPENSES — completed material dispense transactions.
  • GMO_MATERIAL_UNDISPENSES — reversed or un-dispensed material records.
  • GMO_DISPENSE_AREA_TL — translated (language-specific) dispense area names.
  • GMO_DISPENSE_STORAGE_SUBINVS — subinventory mapping associated with each dispense area.
  • GMO_DISPENSE_BOOTH_B — dispense booth definition linked to the parent area.