Search Results ship_status




Overview
Explore in AI Chat

Overview

GML_GASNO_DETAILS is a table in the GML schema (Process Manufacturing Logistics) within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the detail line data of the source order from which a shipment was generated. In the Oracle Process Manufacturing (OPM) logistics flow, a shipment or bill of lading is created against one or more order lines; GML_GASNO_DETAILS records the line-level attributes of those originating orders so that shipment confirmation, delivery, and billing processes can reference the original commercial terms. The table is populated during the shipment generation process and is tightly coupled to the Bill of Lading entity represented by OP_BILL_LAD.

The documented physical schema for 12.2.2 contains 202 columns, all owned by GML. From a Data Vault modeling perspective, the metadata classifies this object heuristically as standalone, meaning it does not exhibit the classic hub-and-satellite pattern but rather behaves as a transactional detail or staging construct. Analysis of the foreign key structure reveals a single documented reference — BOL_ID pointing to OP_BILL_LAD — which anchors each detail row to its parent shipment document.

Key Information Stored

The table carries a mix of surrogate keys, status flags, dates, quantities, pricing elements, and denormalized warehouse and customer address data. The most significant columns include:

No explicit surrogate primary key is documented in the provided metadata; in practice Oracle EBS tables of this nature use a composite key (typically ORDER_ID, LINE_ID, and BOL_ID) or a generated identifier. Business-key candidates therefore center on the order-line and BOL combination. The extensive _INT / _EXT1..EXT5 column pairs (for ship method, currency, hold reason, bill-to codes, countries, states, provinces, pricing reasons, and units of measure) reflect OPM's DFF-style internal/external code-value convention.

Common Use Cases and Queries

GML_GASNO_DETAILS supports shipment verification, order-line reconciliation, freight and pricing analysis, and delivery performance reporting. Typical query patterns include retrieving all detail lines for a given bill of lading:

SELECT d.LINE_ID, d.ITEM_NO, d.ORDR_QTY1, d.SHIP_QTY1, d.SHIP_STATUS FROM GML.GML_GASNO_DETAILS d WHERE d.BOL_ID = :p_bol_id;

Reporting on outstanding shipments against promised dates is another frequent requirement, joining ORDER_ID and LINE_ID back to the originating order tables. Because the table stores denormalized bill-to and warehouse addresses, it can serve as a standalone source for shipment documentation and label generation without additional lookups.

Related Objects

  • OP_BILL_LAD — parent bill-of-lading table; joined via GML_GASNO_DETAILS.BOL_ID = OP_BILL_LAD.BOL_ID.
  • GML_GASNO_HEADERS (logical counterpart) — the shipment-level header, keyed by RUN_ID and BOL_ID.
  • Order management line tables (ONT/GML order lines) — referenced through ORDER_ID and LINE_ID.
  • GML shipping and delivery tables — consume LINE_STATUS and SHIP_STATUS for confirmation processing.
  • Billing interfaces — draw on pricing columns (BASE_PRICE, NET_PRICE, EXTENDED_PRICE) for downstream invoicing.
  • Concurrent program log tables — related through REQUEST_ID, PROGRAM_ID, and RUN_ID.