Results for “op_bill_lad”

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

Overview

OP_BILL_LAD is a table in the GML (Process Manufacturing Logistics) product module of Oracle E-Business Suite, present and valid in both release 12.1.1 and 12.2.2. It stores header-level information for a shipment, functioning as the Bill of Lading (BOL) master record within the Process Manufacturing logistics model. A Bill of Lading aggregates shipment-level attributes such as carrier, ports, addresses, weights, and demurrage charges, and serves as the linkage point for shipment lines, order details, and, in the India localization context, excise and GST-related transaction records.

The table is owned by the GML schema and contains 63 documented columns. Two unique indexes are defined: OP_BILL_LAD_PK on BOL_ID (the surrogate primary key) and OP_BILL_LAD_U1 on the combination of ORGN_CODE and BOL_NO, which establishes the business key.

The heuristic Data Vault classification mined from the foreign-key structure is satellite-leaning. This reflects a table that hangs off a core shipment entity (OP_SHIP_MST) and carries descriptive and transactional attributes rather than acting purely as a hub or link. Practically, BOL_ID behaves as a durable hub key, while the remaining descriptive and code columns (ports, addresses, currencies, text references) behave as satellite attributes.

Key Information Stored

The most significant columns fall into identity, operational, geographic, financial, and control categories:

• BOL_ID — surrogate primary key (OP_BILL_LAD_PK); referenced by numerous child tables.
• ORGN_CODE — organization code; combined with BOL_NO it forms the unique business key (OP_BILL_LAD_U1).
• BOL_NO — the human-readable Bill of Lading number.
• MSTBOL_ID — master BOL reference, supporting BOL hierarchy or consolidation.
• SHIPPER_CODE — foreign key to OP_SHIP_MST, identifying the shipper.
• BOLADDR_ID — foreign key to SY_ADDR_MST, the BOL address.
• EMBARKATION_PORT / DEBARKATION_PORT — foreign keys to OP_PORT_MST, defining origin and destination ports.
• WAYBILL_NO, TRAILER_NO — carrier and transport identifiers.
• BOLSHIP_WT, BOL_UM — shipment weight and its unit of measure (BOL_UM references SY_UOMS_MST).
• BOL_TYPE, REGISTERED_IND — classification and registration flags.
• DEMURRAGE_AMT, DEMURRAGE_CURRENCY — demurrage amount and currency (DEMURRAGE_CURRENCY references GL_CURR_MST).
• PICKUP_TIME, DROPOFF_TIME — scheduling timestamps.
• TEXT_CODE — foreign key to OP_TEXT_HDR, linking free-form notes.
• PRINT_COUNT, DATE_PRINTED, EDI_TRANS_COUNT — document output and EDI tracking.
• DELETE_MARK, IN_USE, ATTRIBUTE_CATEGORY, ATTRIBUTE1–30 — standard Oracle EBS control and extensibility columns.

Common Use Cases and Queries

OP_BILL_LAD is queried for shipment reporting, carrier and port analytics, demurrage reconciliation, and localization compliance reporting.

• Retrieve BOL headers for an organization using the business key: SELECT BOL_ID, BOL_NO, SHIPPER_CODE, BOLSHIP_WT, BOL_UM FROM OP_BILL_LAD WHERE ORGN_CODE = :org AND DELETE_MARK = 0.
• Join to port masters to report embarkation/debarkation: SELECT b.BOL_NO, p1.PORT_NAME embark_port, p2.PORT_NAME debark_port FROM OP_BILL_LAD b, OP_PORT_MST p1, OP_PORT_MST p2 WHERE b.EMBARKATION_PORT = p1.PORT_ID AND b.DEBARKATION_PORT = p2.PORT_ID.
• Aggregate demurrage by currency: SELECT DEMURRAGE_CURRENCY, SUM(DEMURRAGE_AMT) FROM OP_BILL_LAD WHERE DELETE_MARK = 0 GROUP BY DEMURRAGE_CURRENCY.
• Reconcile order details to BOLs via OP_ORDR_DTL.BOL_ID to trace shipments back to sales orders.

Related Objects

OP_BILL_LAD sits at the centre of a well-defined referential network. Key related tables and views include:

• OP_ORDR_DTL — references BOL_ID; links order details to the shipment header.
• OP_SHIP_MST — referenced via SHIPPER_CODE; provides shipper master data.
• OP_PORT_MST — referenced via EMBARKATION_PORT and DEBARKATION_PORT.
• SY_ADDR_MST — referenced via BOLADDR_ID for address information.
• SY_UOMS_MST — referenced via BOL_UM for weight units.
• GL_CURR_MST — referenced via DEMURRAGE_CURRENCY.
• OP_TEXT_HDR — referenced via TEXT_CODE for descriptive notes.
• SY_ORGN_MST / SY_ORGN_MST_B — referenced via ORGN_CODE for organization validation.
• GML_GASNO_SHIPMENTS / GML_GASNO_DETAILS / GML_GASNO_SHIPMENT_TEXT — gas shipment tables carrying BOL_ID references.
• JAI_CMN_RG_* tables (JAI_CMN_RG_PLA_TRXS, JAI_CMN_RG_23AC_I_TRXS, JAI_CMN_RG_23AC_II_TRXS, JAI_CMN_RG_23D_TRXS, JAI_CMN_RG_I_TRXS) — India localization excise and GST registers that depend on BOL_ID.
• GMD_COA_HEADERS — certificate of analysis header referencing the BOL.

Together these relationships confirm that OP_BILL_LAD is a pivotal shipment header supporting both standard logistics and localized compliance processes across Oracle EBS 12.1.1 and 12.2.2.