Results for “bol_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

GML_GASNO_SHIPMENT_TEXT_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, registered against the Process Manufacturing Logistics (GML) product family. As its name and description indicate, the view exposes shipment-related text — the free-form paragraph and remark content attached to a Bill of Lading — in a denormalised, reporting-friendly form. Rather than requiring report authors and integrators to join the underlying logistics base tables themselves, the view presents a single flattened result set keyed by Bill of Lading identifier, language, paragraph code, sub-paragraph code, and line number. This makes it a convenient access point for printed shipping documentation, compliance narratives, customer-facing Bill of Lading output, and any integration that must render or transmit shipment text alongside its parent logistics document. The view is documented as VALID in the ETRM metadata for 12.2.2, and the same definition is applicable to 12.1.1 environments. The metadata carries the standard Oracle Proprietary, Confidential Information designation.

Underlying Base Objects

The view is defined over two documented synonyms: OP_BILL_LAD and OP_TEXT_TBL. OP_BILL_LAD is the Bill of Lading detail table and supplies the BOL_ID identifier together with the TEXT_CODE that links each Bill of Lading to its stored text. OP_TEXT_TBL is the shared text repository used across Process Manufacturing Logistics, holding the actual paragraph content together with its language, paragraph code, sub-paragraph code, and line sequencing. The join is performed on TEXT_CODE (BL.TEXT_CODE = TT.TEXT_CODE), so each row in the view represents one line of text belonging to one Bill of Lading. The view text additionally filters on DELETE_MARK = 0, meaning soft-deleted Bills of Lading are excluded from the result set — a filtering behaviour that report developers should note, since the view will not surface text for logically deleted shipping documents.

Key Columns

• BOL_ID — the Bill of Lading identifier, inherited from OP_BILL_LAD; the primary correlation key back to the logistics document.
• LANG_CODE_INT — the language code of the stored text, sourced from OP_TEXT_TBL.LANG_CODE; supports multi-language shipment documentation.
• PARA_CODE_INT — the paragraph code (OP_TEXT_TBL.PARAGRAPH_CODE), the element referenced by the search term "para_code_int". It classifies which standard text paragraph a line belongs to, such as shipping instructions, hazardous notes, or delivery terms.
• SUB_PARACODE — a finer classification within the paragraph code, allowing multiple subordinate text blocks per paragraph.
• LINE_NO — the sequence number of the text line, used to reassemble paragraphs in the correct order.
• TEXT — the actual text content of the line.

Common Use Cases and Queries

Typical uses include Bill of Lading printing, shipment documentation extracts, and downstream integrations that need the narrative text associated with a shipment. Because text is stored line-by-line, queries generally aggregate or order by the sequencing columns.

• Retrieve all text lines for one Bill of Lading in correct order:

  SELECT bol_id, para_code_int, sub_paracode, line_no, text
  FROM   apps.gml_gasno_shipment_text_v
  WHERE  bol_id = :p_bol_id
  ORDER BY para_code_int, sub_paracode, line_no;

• Filter to a specific paragraph type across shipments:

  SELECT bol_id, line_no, text
  FROM   apps.gml_gasno_shipment_text_v
  WHERE  para_code_int = :p_para_code
  ORDER BY bol_id, line_no;

• Reassemble paragraph content into a single string for reporting:

Report developers should remember that all lines of a paragraph share BOL_ID, PARA_CODE_INT, SUB_PARACODE, and LANG_CODE_INT, with LINE_NO providing the ordering key — making these columns the natural GROUP BY and ORDER BY candidates for any aggregated text output.