Search Results ic_trans_qty

Overview

GML_OM_SHIP_DTL_VW is a database view owned by the APPS schema within Oracle E-Business Suite, associated with the product module GMF – Process Manufacturing Financials. Oracle's own electronic technical reference manual explicitly flags this object as OBSOLETE, meaning it is retained in the schema only for backward compatibility and should not be used as the basis for new development or customizations. Its historical purpose was to select Oracle Order Management (OM) shipments together with their related information as recorded in OPM (Oracle Process Manufacturing) inventory transactions.

Functionally, the view acted as a reconciliation bridge between the discrete Order Management shipping model and the Process Manufacturing inventory transaction model. It joined delivery, order, and inventory transaction data into a single result set, allowing shipment details to be reported alongside the corresponding OPM inventory transaction quantities. Because it is a view and not a table, it stores no data of its own; all values are derived at runtime from its underlying base objects.

Underlying Base Objects

The documented base objects referenced by the view are all resolved through synonyms in the APPS schema:

• WSH_NEW_DELIVERIES — the delivery header, supplying DELIVERY_ID.
• WSH_DELIVERY_ASSIGNMENTS — links deliveries to delivery details.
• WSH_DELIVERY_DETAILS — the delivery line detail, supplying DELIVERY_DETAIL_ID, SOURCE_HEADER_ID, SOURCE_LINE_ID, FOB_CODE, and weight attributes.
• OE_ORDER_HEADERS_ALL — the sales order header, supplying ORDER_NUMBER.
• OE_ORDER_LINES_ALL — the sales order line, supplying LINE_NUMBER, SHIPPING_QUANTITY, SHIPPING_QUANTITY_UOM, and UNIT_SELLING_PRICE.
• IC_TRAN_PND — the OPM pending inventory transaction table, supplying item, quantity, organization, warehouse, and posting flags.

The join path requires that the delivery detail's SOURCE_CODE equals 'OE' and that OE_INTERFACED_FLAG equals 'Y', ensuring only Order Management sourced, interfaced shipment lines are included. The inventory side is restricted to DOC_TYPE 'OMSO' with COMPLETED_IND = 1, GL_POSTED_IND = 1, and DELETE_MARK = 0, so only completed and posted order shipment transactions are surfaced. The query aggregates transaction quantity using SUM(T.TRANS_QTY) grouped by the remaining selected columns.

Key Columns

• DELIVERY_ID and DELIVERY_DETAIL_ID — identifiers for the shipment and its detail line.
• SOURCE_HEADER_ID and SOURCE_LINE_ID — the originating order header and line identifiers.
• ORDER_NUMBER and LINE_NUMBER — human-readable order and line references.
• SHIPPING_QUANTITY and SHIPPING_QUANTITY_UOM — shipped quantity and its unit of measure.
• UNIT_SELLING_PRICE — the selling price on the order line.
• ITEM_ID — the inventory item shipped.
• IC_TRANS_QTY — the aggregated OPM inventory transaction quantity.
• ORGN_CODE, WHSE_CODE, and TRANS_UM — inventory organization, warehouse, and transaction unit of measure.
• FOB_CODE, NET_WEIGHT, WEIGHT_UOM_CODE — shipment freight and weight attributes.
• COMPLETED_IND and GL_POSTED_IND — indicators that the inventory transaction is complete and posted to the general ledger.

Common Use Cases and Queries

Historically, this view supported shipment-versus-inventory reconciliation reporting, particularly to confirm that shipped order quantities were reflected in OPM inventory transactions and posted to the general ledger. A representative query for inspection purposes is:

SELECT order_number, line_number, item_id, shipping_quantity, ic_trans_qty, orgn_code, whse_code FROM apps.gml_om_ship_dtl_vw WHERE order_number = :order_number;

Because Oracle designates the object OBSOLETE, existing references should be inventoried and migrated to supported alternatives. Any query against this view must be validated against the target release, as the definition may be removed in future upgrades without notice.