Schema Name: BillOfLadingCreate
Schema Purpose:
Document ID: 01-427-10-25-2006
© PIDX, Inc. 2012
Use of this copyrighted material is subject to the PIDX End User License Agreement available at
www.pidx.org/license. Each user agrees to such End User License Agreement by making any use
of the copyrighted material.
This document was prepared and is maintained in accordance with the PIDX Procedures for Standards
Development, a copy of which is available at www.pidx.org/procedures, and the PIDX Antitrust Guidelines,
a copy of which is available at www.pidx.org/antitrust.
Schema Version Number: 1.41
Version Date: 2012-01-09
Change Management Log:
Version Person Date Description
Feb2006 Original 2006-02-14 From FEB2006 release
1.41 PIDX BMWG 2012-01-09 Transfer to PIDX, Inc.
Information pertaining to the person/company purchasing the product.
Specifies information pertaining to the carrier (a.k.a. hauler) of the product.
When populated, this content model contains the product owner (when different from supplier).
In exchange accounting scenarios, when the PDXB records are being SENT through a VAN, the 2 digit company code is the
company that is the receiver of the data; when PDXB records are being RECEIVED, the 2 digit company code is the
company that sent the data.
Specifies the gravity of the product.
Specifies the type of gravity.
A numeric signed field which represents the gross (metered) quantity of product loaded. Since this is a signed field, negative values are allowed. Negative values could mean: a cancelled transaction, receipt of product into a terminal, etc.
This represents a combination of the following 2 fields in the PDXB v3 record set: 'GrossQuantity' and 'GrossCreditSign'.
A numeric signed field which represents the net (metered) quantity of product loaded. Since this is a signed field, negative values are allowed. Negative values could mean: a cancelled transaction, receipt of product into a terminal, etc.
This represents a combination of the following 2 fields in the PDXB v3 record set: 'Net Quantity or Temperature / Gravity' (field 38) and 'NetCreditSign'.
Freeform data that may be used for any information that the terminal operator would like to send.
Information about the location to which products are shipped.
Seller of the product to the customer.
Specifies information pertaining to the facility where product is stored and loaded.
A 2 digit PIDX Company Code.
Specifies the type of BoL transaction associated with typical BoL trading partners. Normal types include Invoice, Billing, etc.
Refers to PDXB v3 data field: MeasurementType
Information about a vehicle involved in the load.
For real-time (PDXR) type authorizations, this is the number assigned/returned from the load authorizing application.
An alpha-numeric field which identifies the consignee as it appears on the BOL.
This field may include the following two data fields: 'Bill To ID' and (optionally) 'Ship To ID'.
A system generated load verification number
The date when the driver stops the load/transaction. Typically, this is when the driver is finished loading at the truck rack load lane and “cards out.”
The time when the driver stops the load/transaction. Typically, this is when the driver is finished loading at the truck rack load lane and “cards out.”
The date when the driver entered the terminal.
The time when the driver entered the terminal.
The date when the driver finished (either when carded out and did the BOL print, or when carded out to exit the terminal).
The time when the driver finished (either when carded out and did the BOL print, or when carded out to exit the terminal).
Identifies which lane or loading area the driver loaded the product.
The date when the driver started the load/transaction. Typically, this is when the driver “cards in” at the truck rack load lane to begin loading.
The time when the driver started the load/transaction. Typically, this is when the driver “cards in” at the truck rack load lane to begin loading.
An alpha-numeric field, which contains the significant digits of the bill of lading number. Right justification and padding with leading zeros is not required.
Specifies the total number of finished products.
The sum of the GrossQuantity element values directly beneath (one level below) the FinishedProduct elements – regardless of the UOM. This is used as a checksum for the document.
The sum of the NetQuantity element values directly beneath (one level below) the FinishedProduct elements – regardless of the UOM. This is used as a checksum for the document.
2 numerics followed by a dash, followed by 7 digits.
2 numerics followed by a dash, followed by 7 digits.
A number or code used by the terminal automation system to uniquely identify the carrier of the product.
SCAC stands for Standard Carrier Alpha Code.
Specifies whether a truck is loaded at multiple lanes at the terminal truck rack.
Specifies information about a company.
An alpha-numeric field, from the PIDX company code list, that is used to identify the company.
2 numerics followed by a dash, followed by 7 digits.
Data that belongs to the Terminal Automation System.
An identifier used for the vehicle/transport involved. This should reference a VehicleNumber from CarrierInformation.VehicleInformation in the BillOfLadingHeader.
Identifier the compartment within the vehicle/transport involved.
Indicates that there has been some modification to the product.
Indicates whether the product is additized and if so, with what. Additives are proprietary if it is the proprietary additive of the final seller of the product.
The numeric value of the cetane or octane. For example, 87.0 would be a typical octane value for gasoline; 42.0 would be a typical cetane value for #2 diesel.
A single alpha-numeric character indicating if the product contains a dye. Acceptable values are: Y=Yes, N=No.
Indicates whether the product is fungible or segregated.
Regulatory Oxy percentage. This is a percentage value (e.g. 2.7 means 2.7%).
Volume percent of oxygenate. This is a percentage value (e.g. 10.0 means 10%).
Indicates whether the product type is reformulated gasoline.
Reid Vapor Pressure. This is a percentage value (e.g. 8.5 means 8.5%).
A numeric indication of the sulphur content of the product. This is a percentage value (e.g. 1.0 means 1%). (If the sulphur content is .06% or higher, the product is considered to be a high sulphur product. If the sulphur content is .05% or lower, the product is considered to be a low sulphur product.)
A code which identifies the product loaded. Codes used are the Oil Industry Common Product Codes. The codes are maintained and available from the PIDX Downstream E-Business Subcommittee. If there was no blending, the Component and Finished Product Codes should be the same code.
Refers to PDXB v3: DestinationCountyCode
Specifies the name of a receiver of a product. In some cases this may be the marketer. In other cases, this may be the end location.
Specifies the state to which goods are shipped.
The four-character EPA-assigned ID for the entity (I believe this will be assigned to the operating company at the terminal)
The five-character EPA-assigned ID for the facility. Filled with leading zeroes if applicable.
An alpha-numeric field identifying the Internal Revenue Service’s Terminal Control Number. (Use “NON-IRS” if not applicable such as for an asphalt terminal or refinery)
A numeric field used to identify the physical location of the terminal from which the product was withdrawn.
An identifier used for the vehicle/transport involved.
9-digit Federal Employer Identification Number (2 numerics followed by a dash, followed by 7 numerics)
SPLC stands for Standard Point Location Code.