Search Results net_wt




Overview
Explore in AI Chat

Overview

GML_GASNO_SUM_V is a reporting view owned by the APPS schema within the Oracle E-Business Suite environment, catalogued under the GML - Process Manufacturing Logistics product family. It is documented with the description "Total Weights view" and is stamped with a status of VALID. In EBS 12.1.1 and 12.2.2 deployments, the view serves as a lightweight aggregation layer that consolidates weight and volume figures for shipments at the bill of lading level. Rather than requiring report authors, Discoverer workbooks, or integration extracts to repeatedly sum detail records, GML_GASNO_SUM_V presents a pre-aggregated result set keyed by bill of lading.

The name reflects its parent application context: GML corresponds to Process Manufacturing Logistics, the module that manages shipping, bills of lading, and the physical movement of goods in process manufacturing operations. This view is therefore primarily consumed by logistics reporting artifacts, including Oracle Reports, XML Publisher templates, and custom dashboards that need totals for net weight, tare weight, pallet weight, and shipping volume without traversing order detail rows individually.

Underlying Base Objects

The documented metadata identifies a single referenced base object: OP_ORDR_DTL, accessed through a synonym. OP_ORDR_DTL is the order detail table within the Process Manufacturing Logistics schema, storing line-level shipment information including weights and volumes. The view text confirms a direct dependency on this table, aliasing it as OD and grouping aggregation results by the BOL_ID column. Because OP_ORDR_DTL is exposed to APPS via a synonym, the view can be compiled and referenced from the APPS schema without hardcoding the owning schema name, which preserves portability across cloned and multi-organization instances. No joins to additional tables appear in the documented view definition, so GML_GASNO_SUM_V is a single-source aggregation rather than a composite of multiple transactional tables.

Key Columns

  • BOL_ID — The bill of lading identifier. This is the grouping key and uniquely identifies each aggregated row returned by the view.
  • NET_WT — The summation of the NET_WT column from OP_ORDR_DTL. This represents the total net weight across all detail lines belonging to the bill of lading, and is the column most frequently targeted by users searching on "net_wt".
  • TARE_WT — The summed tare weight, capturing the aggregate weight of packaging or containers associated with the shipment.
  • PALLET_WT — The summed pallet weight, reflecting the total weight contributed by pallets in the shipment.
  • SHIP_VOLUME — The summed shipping volume, providing the total volumetric measure for the bill of lading.

Collectively these four measures give a complete physical profile of a shipment: net product weight, container weight, pallet weight, and volume.

Common Use Cases and Queries

Typical usage centres on retrieving shipped totals for a specific bill of lading or for a set of bills. A representative query is:

SELECT BOL_ID, NET_WT, TARE_WT, PALLET_WT, SHIP_VOLUME FROM APPS.GML_GASNO_SUM_V WHERE BOL_ID = :p_bol_id;

Reports that print bill of lading documentation use this view to display consolidated weights in header sections while detail lines remain sourced separately. Integration extracts that feed external transportation management or warehouse systems frequently select the entire view and filter by BOL_ID ranges pushed from the source system. Analysts comparing net weight against tare and pallet weights to derive gross shipment weight also use the view, summing NET_WT, TARE_WT, and PALLET_WT in a single query. Because the view is pre-aggregated, it reduces query complexity and improves performance relative to ad hoc grouping of OP_ORDR_DTL, though users should note that any filtering occurs on the aggregated result set.