Search Results planned_quantity2

Overview

GML_SO_RESERVATIONS_V is a reporting view owned by the APPS schema within the Oracle E-Business Suite Process Manufacturing Logistics (GML) module. Its documented purpose is to present batch reservation data — a consolidation of reserved, planned, and committed quantities associated with process manufacturing batches tied to sales order delivery details. Unlike transactional tables that store one row per operation or allocation, this view aggregates reservation quantities by batch and reservation identifiers, delivering a summarized perspective suited to reporting, inquiry screens, and integration extracts.

The view is particularly relevant when the goal is to determine how much material a given batch has reserved, planned, or committed against sales order demand, and when that batch's activity is scheduled — which is where columns such as PLAN_CMPLT_DATE become central. Because it is a view (not a table), it carries no independent storage; every query re-derives its results from the underlying base object, ensuring the reported figures remain synchronized with the transactional data held in the Process Manufacturing Logistics tables.

Underlying Base Objects

The documented base object behind GML_SO_RESERVATIONS_V is GML_BATCH_TMP, accessed through a synonym in the APPS schema. The view text performs a GROUP BY over this source, collapsing multiple reservation rows into one summarized line per combination of BATCH_RES_ID, BATCH_ID, BATCH_NO, BATCH_LINE_ID, WHSE_CODE, DELIVERY_DETAIL_ID, BATCH_TYPE, BATCH_STATUS, START_DATE, and PLAN_CMPLT_DATE. A HAVING clause filters the result set so that only batches with a positive line reserved quantity or a positive planned quantity are returned. The aggregation uses SUM across the reserved, planned, and committed quantity columns, with NVL applied to planned and reserved quantities to treat nulls as zero. The presence of the "_TMP" suffix on the base object suggests it functions as a staging or transient structure populated during reservation processing, from which the view derives a stable, query-friendly projection.

Key Columns

• BATCH_RES_ID / BATCH_ID / BATCH_LINE_ID — Identifiers for the batch reservation, the batch, and the batch line, forming the primary grouping keys.
• BATCH_NO — The human-readable batch number.
• WHSE_CODE — Warehouse associated with the reservation.
• DELIVERY_DETAIL_ID — Links the batch reservation to the sales order delivery detail.
• BATCH_TYPE / BATCH_STATUS — Classification and current status of the batch.
• START_DATE — Start date of the batch activity.
• PLAN_CMPLT_DATE — Planned completion date of the batch; the column most frequently used to assess scheduling and availability relative to delivery demand.
• RESERVED_QUANTITY / RESERVED_QUANTITY2 — Aggregated reserved quantities, expressed in the primary and secondary units of measure.
• PLANNED_QUANTITY / PLANNED_QUANTITY2 — Aggregated planned quantities per unit of measure.
• COMMIT_QUANTITY / COMMIT_QUANTITY2 — Aggregated committed quantities per unit of measure.

Common Use Cases and Queries

A typical use is to retrieve all reservations for a delivery detail or warehouse where planning is complete or imminent, filtered on PLAN_CMPLT_DATE. For example:

SELECT batch_no, whse_code, delivery_detail_id, batch_status, start_date, plan_cmplt_date, reserved_quantity, planned_quantity, commit_quantity FROM apps.gml_so_reservations_v WHERE plan_cmplt_date BETWEEN :p_from AND :p_to ORDER BY plan_cmplt_date;

Other scenarios include reconciling reserved versus committed quantities per batch, identifying batches whose planned completion date falls after the required delivery date (indicating a potential shortfall), and feeding downstream reporting or integration extracts that need a summarized batch reservation picture. Because the view already aggregates and filters, it is well suited as a source for dashboards and inquiry forms rather than for row-level transactional updates.