Search Results gmo_dispensing_planning_pk

Overview

GMO_DISPENSING_PLANNING is a transactional table owned by the GMO schema in Oracle E-Business Suite, within the Manufacturing Execution System for Process Manufacturing product family. The table serves as the dispense planning repository for process manufacturing operations, capturing the scheduling, prioritization, and execution state of material dispensing tasks that flow from production reservations to physical dispense transactions on the shop floor. In EBS 12.1.1 and 12.2.2 the object is documented as VALID and comprises 14 columns. Its primary role is to bridge planned production demand (via inventory reservations) and actual dispensing activity (via material dispense records), providing planners and supervisors with a controlled, prioritized work queue for weighing and dispensing operations.

Under a heuristic Data Vault classification mined from the foreign key structure, the table is modeled as standalone. This classification reflects that GMO_DISPENSING_PLANNING does not function purely as an association between two parent hubs; it carries its own descriptive attributes (priority, planned date, status) alongside its relationships. In Data Vault terms it behaves more like a satellite-style record anchored to a planned task identity, with outbound links to reservations, dispense areas, and material dispenses. This is a modeling suggestion, not a physical constraint of the EBS schema.

Key Information Stored

The table is keyed by a single-column surrogate primary key, GMO_DISPENSING_PLANNING_PK, defined on PLANNED_TASK_ID. This is the only documented unique index and therefore the sole business-key candidate. The most significant columns are:

• PLANNED_TASK_ID — surrogate primary key uniquely identifying each planned dispensing task.
• RESERVATION_ID — foreign key to MTL_RESERVATIONS, tying the task to the inventory reservation that supplies the material.
• DISPENSE_AREA_ID — foreign key to GMO_DISPENSE_AREA_B, identifying the physical or logical dispensing area where the task is executed.
• DISPENSE_ID — foreign key to GMO_MATERIAL_DISPENSES, linking the plan to the resulting dispense transaction once executed.
• PRIORITY — sequencing rank used to order the dispensing work queue.
• PLANNED_DISPENSING_DATE — scheduled date for the planned dispensing activity, used for scheduling and backlog reporting.
• STATUS — current state of the planned task (for example, pending, in progress, completed), driving workflow and query filters.
• DISPENSED_DATE — actual execution timestamp recorded when the dispense occurs.
• OPER_ID — routing operation identifier associating the task with a specific step in the production routing.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns for change tracking and concurrency control.

Common Use Cases and Queries

Typical usage centres on shop-floor dispense scheduling and reconciliation. A common query retrieves the outstanding workload for a dispense area, ordered by priority and planned date:

• SELECT p.planned_task_id, p.priority, p.planned_dispensing_date, p.status FROM gmo.gmo_dispensing_planning p WHERE p.dispense_area_id = :area AND p.status <> 'COMPLETE' ORDER BY p.priority, p.planned_dispensing_date;
• Linking planned versus actual execution to identify tasks where DISPENSE_ID is populated but DISPENSED_DATE is null, or where planned and dispensed dates diverge significantly, supports cycle-time reporting.
• Joining RESERVATION_ID to MTL_RESERVATIONS allows planners to validate that sufficient material remains reserved before release to the dispense queue.
• Aggregating by OPER_ID supports operation-level workload balancing across routing steps.

Related Objects

Dependency relationships are defined by the documented foreign keys and primary key:

• MTL_RESERVATIONS — joined on RESERVATION_ID; supplies reserved material context.
• GMO_DISPENSE_AREA_B — joined on DISPENSE_AREA_ID; defines the dispensing area master.
• GMO_MATERIAL_DISPENSES — joined on DISPENSE_ID; holds the executed dispense transaction.

Additional related process manufacturing objects commonly leveraged alongside this table include GMO routing and operation definitions referenced through OPER_ID, and production reservation views used in planning reports. In EBS 12.2.2 the column set remains consistent with the 12.1.1 footprint, so queries and reports are portable across both releases.