Search Results bol_no
Overview
The OP_BILL_LAD table is a core data object within the Oracle E-Business Suite (EBS) Process Manufacturing Logistics (GML) module. It serves as the primary header table for storing Bill of Lading (BOL) information, which is the fundamental legal and operational document detailing the contract of carriage for a shipment. As a header table, OP_BILL_LAD contains the master record for a shipment, capturing critical administrative, logistical, and financial details that govern the movement of goods. Its role is central to shipment management, providing the foundational data that links to detailed shipment lines, orders, and related logistics transactions throughout the system.
Key Information Stored
The table's primary key is the BOL_ID, a unique system-generated identifier for each Bill of Lading record. According to the provided metadata, other significant columns include ORGN_CODE, which identifies the operating unit, and BOL_NO, the user-assigned Bill of Lading number. The table's foreign key relationships reveal additional key data points it stores: shipment ports (EMBARKATION_PORT, DEBARKATION_PORT), the shipper (SHIPPER_CODE), currency details for charges (DEMURRAGE_CURRENCY), a unit of measure for the BOL (BOL_UM), address information (BOLADDR_ID), and associated text notes (TEXT_CODE). These columns collectively define the shipment's origin, destination, parties involved, and commercial terms.
Common Use Cases and Queries
This table is essential for generating shipment documentation, tracking shipment status, and supporting freight accounting. Common operational reports include shipment registers, pending shipment lists, and carrier performance analysis. A typical query might join OP_BILL_LAD to the OP_ORDR_DTL table to list all order lines associated with a specific shipment, using the BOL_ID as the link. For example:
- SELECT bol.bol_no, bol.shipper_code, ordr.order_no FROM gml.op_bill_lad bol JOIN gml.op_ordr_dtl ordr ON bol.bol_id = ordr.bol_id WHERE bol.orgn_code = :p_org;
Another common pattern is querying shipment headers within a date range for a specific port, which involves joining to OP_PORT_MST for port descriptions.
Related Objects
OP_BILL_LAD has extensive relationships with other master and transactional tables in EBS, as documented by its foreign keys. Key related objects include:
- OP_ORDR_DTL: This table holds the detailed shipment lines and references OP_BILL_LAD via the BOL_ID column, forming the core shipment structure.
- SY_ORGN_MST / SY_ORGN_MST_B: Provide the operating unit (ORGN_CODE) master data.
- OP_SHIP_MST: Contains master data for the shipper (SHIPPER_CODE).
- OP_PORT_MST: Provides master data for the embarkation and debarkation ports.
- GL_CURR_MST, SY_UOMS_MST, SY_ADDR_MST, OP_TEXT_HDR: These are supporting master tables for currency, units of measure, addresses, and descriptive text, respectively.
-
Table: OP_BILL_LAD
12.2.2
owner:GML, object_type:TABLE, fnd_design_data:GML.OP_BILL_LAD, object_name:OP_BILL_LAD, status:VALID, product: GML - Process Manufacturing Logistics , description: Header information for a shipment. , implementation_dba_data: GML.OP_BILL_LAD ,
-
Table: OP_BILL_LAD
12.1.1
owner:GML, object_type:TABLE, fnd_design_data:GML.OP_BILL_LAD, object_name:OP_BILL_LAD, status:VALID, product: GML - Process Manufacturing Logistics , description: Header information for a shipment. , implementation_dba_data: GML.OP_BILL_LAD ,
-
View: GML_GASNO_SHIPMENTS_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:GML.GML_GASNO_SHIPMENTS_V, object_name:GML_GASNO_SHIPMENTS_V, status:VALID, product: GML - Process Manufacturing Logistics , description: Shipment view , implementation_dba_data: APPS.GML_GASNO_SHIPMENTS_V ,
-
View: GML_GASNO_SHIPMENTS_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:GML.GML_GASNO_SHIPMENTS_V, object_name:GML_GASNO_SHIPMENTS_V, status:VALID, product: GML - Process Manufacturing Logistics , description: Shipment view , implementation_dba_data: APPS.GML_GASNO_SHIPMENTS_V ,