Search Results dispensed_date

Overview

GMO.GMO_DISPENSING_PLANNING is a transactional table in the Oracle E-Business Suite Process Manufacturing (OPM) dispensing module, owned by the GMO schema. It serves as the dispense planning table that links planned manufacturing or dispensing tasks to physical dispensations of materials. Each row represents a planned dispense activity, capturing scheduling intent (priority, planned date), execution state (status), and, once executed, the resulting dispensing transaction and its timestamp. The table is stored in the APPS_TS_TX_DATA tablespace, with its unique and non-unique indexes residing in APPS_TS_TX_IDX.

In Data Vault modeling terms, the metadata classifies this object heuristically as standalone. As a modeling suggestion, it may be treated as a satellite anchored on a planned task hub, with its foreign keys to reservations, dispense areas, and material dispenses acting as link candidates. This reflects that the table itself does not depend on any upstream table for its existence but does reference several core OPM entities.

Key Information Stored

The primary key is PLANNED_TASK_ID, documented as the unique business-key candidate (GMO_DISPENSING_PLANNING_PK) and described as the "planned id." It is the surrogate identifier for each planning record. The most significant columns are:

• PLANNED_TASK_ID — Primary key; uniquely identifies the planned task.
• RESERVATION_ID — Foreign key to MTL_RESERVATIONS; ties the plan to a material reservation.
• DISPENSE_AREA_ID — Foreign key to GMO_DISPENSE_AREA_B; identifies the physical dispensing area.
• PRIORITY — VARCHAR2(15); value of High, Medium, or Low.
• PLANNED_DISPENSING_DATE — DATE; the intended dispense date.
• STATUS — VARCHAR2(15); PLANNED, DISPENSD, or REVRDISP.
• DISPENSE_ID — Foreign key to GMO_MATERIAL_DISPENSES; populated once dispensed.
• DISPENSED_DATE — DATE; the actual dispense timestamp, populated when dispensed.
• OPER_ID — Person ID of the operator.
• Standard who columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

The non-unique index GMO_DISPENSING_PLANNING_N1 covers DISPENSE_ID and DISPENSED_DATE, making it the primary access path for the frequently searched dispensed_date predicate.

Common Use Cases and Queries

The most common reporting need is reconciling planned versus actual dispensing. Because DISPENSED_DATE is indexed via GMO_DISPENSING_PLANNING_N1, date-range filtering is efficient:

• Query dispensations for a date range:
  SELECT PLANNED_TASK_ID, DISPENSE_ID, DISPENSED_DATE, STATUS FROM GMO.GMO_DISPENSING_PLANNING WHERE DISPENSED_DATE BETWEEN :from_date AND :to_date;
• Identify completed versus pending plans by filtering STATUS = 'DISPENSD' or 'PLANNED'.
• Audit planned-versus-actual variance by comparing PLANNED_DISPENSING_DATE with DISPENSED_DATE.
• Operator productivity reporting grouped by OPER_ID.

Related Objects

• MTL_RESERVATIONS — joined on RESERVATION_ID; supplies reservation detail.
• GMO_DISPENSE_AREA_B — joined on DISPENSE_AREA_ID; base table for dispense areas.
• GMO_MATERIAL_DISPENSES — joined on DISPENSE_ID; holds the executed dispense transaction.
• GMO_DISPENSING_PLANNING# — the underlying base table referenced by this object.

Together these relationships support end-to-end traceability from planning through physical material dispensing within the OPM dispensing process.