Search Results bol_comment

Overview

GML_GASNO_SHIPMENTS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the GML (Process Manufacturing Logistics) product family. Its documented description is simply "Shipment view," and it serves as a consolidated, denormalized access point for bill-of-lading (BOL) shipment information that must be communicated to external trading partners. The view is declared VALID and is present in both 12.1.1 and 12.2.2 environments, where the underlying GML and order-management schemas remain structurally consistent.

The view's purpose is export-oriented: it projects shipping transactions into a flat record set suitable for EDI or flat-file generation. The literal 'EC' in the COMMUNICATION_METHOD column and the '00' DOCUMENT_PURPOSE_CODE indicate that the view is designed to feed an E-commerce/EDI communication layer rather than to serve as a normalized transactional source. It joins header, detail, order, freight, port, and shipment master data to present one row per trading-partner detail record. Fields are aliased into a trading-partner (TP_) naming convention, reinforcing its role as a transport structure for partner-facing messages.

Underlying Base Objects

The view is defined over a mixture of ECE trading-partner tables, GML views, and OP/IC synonyms. Documented referenced objects include:

• ECE_TP_HEADERS and ECE_TP_DETAILS — trading-partner header and detail records supplying TP_HEADER_ID, TP_DETAIL_ID, TP_CODE, TEST_FLAG, and the ATTRIBUTE1–15 flexfields.
• OP_BILL_LAD — the bill-of-lading master providing BOL_ID, BOL_NO, embarkation/debarkation ports, waybill, and shipper codes.
• OP_ORDR_DTL and OP_ORDR_HDR — order lines and headers contributing freight-billing method, FOB code, and ship method.
• OP_CUST_MST, OP_FOBC_MST, OP_FRGT_MTH, OP_PORT_MST, OP_SHIP_MST, OP_SHIP_MTH — descriptive master tables resolving codes into names and descriptions.
• IC_WHSE_MST and SY_ADDR_MST — warehouse and address master data.
• GML_GASNO_SUM_V — a summary view supplying NET_WT, TARE_WT, and PALLET_WT aggregates.
• GML_EC_CONTACT_V — contact information for the EDI message.
• FND_PROFILE — the profile-options package, typically used to resolve multi-org or site-level settings at runtime.

Each join enriches the shipment row with partner-, order-, freight-, and weight-level context without requiring the caller to navigate the underlying normalized tables.

Key Columns

The view exposes several logical groups of columns. Trading-partner identity and routing are captured by TP_HEADER_ID, TP_DETAIL_ID, TP_CODE, TP_LOCATION_CODE_EXT, TP_DESCRIPTION, and TP_REFERENCE1/2. Header and detail flexfields are surfaced as TP_HEADER_ATTRIBUTE1–15 and TP_DETAIL_ATTRIBUTE1–5, with their respective ATTRIBUTE_CATEGORY columns.

• TP_DETAIL_ATTRIBUTE1 (mapped from ETD.ATTRIBUTE1) — one of the descriptive flexfield segments on the trading-partner detail record. This column is the most commonly searched attribute in this view and is typically used to carry partner-specific reference data such as certificate numbers or customer-assigned identifiers.
• BOL_ID, BOL_NO, WAYBILL_NO, ORGN_CODE, BOL_COMMENT — bill-of-lading and shipment identifiers.
• FRTBILL_MTHD_INT/FRTBILL_DESC, FOB_CODE_INT/FOB_NAME, SHIP_MTHD_INT/METH_DESC1 — code-to-description pairs for freight billing, FOB terms, and shipping method.
• EMBARKATION_PORT_INT/DESC, DEBARKATION_PORT_INT/DESC — port codes resolved to descriptions.
• SHIPPER_CODE_INT/SHIPPER_NAME — shipper identification.
• NET_WT, TARE_WT, PALLET_WT — aggregated weights from GML_GASNO_SUM_V.
• TRANSACTION_DATE (SYSDATE) — the effective date stamped on the message.

Common Use Cases and Queries

Because the view is partner-export oriented, its principal uses are EDI extraction, shipment reconciliation, and audit of trading-partner attribute data. A frequent requirement is locating shipments by the detail flexfield value that users entered on the trading-partner detail record.

• Retrieve all shipment rows for a specific partner attribute value:

  SELECT bol_no, tp_code, tp_document_code, tp_detail_attribute1, net_wt
  FROM   apps.gml_gasno_shipments_v
  WHERE  tp_detail_attribute1 = :attribute_value;

• Extract a full EDI-ready rowset for a given bill of lading:

  SELECT * FROM apps.gml_gasno_shipments_v WHERE bol_id = :bol_id;

• Cross-check order-level freight and FOB terms attached to a shipment:

  SELECT bol_no, frtbill_desc, fob_name, meth_desc1
  FROM   apps.gml_gasno_shipments_v
  WHERE  orgn_code = :organization_code;

When querying, note that TP_DETAIL_ATTRIBUTE1 depends on the ATTRIBUTE_CATEGORY context assigned to the trading-partner detail; filtering without the matching category can return unrelated segments. All access should be granted through the APPS synonym, and joins to additional base tables are unnecessary because the view already resolves descriptive values.