Bill of Lading Form in Sap

BILL OF LADING (SAP INTEGRATED TRANSPORT LOGISTICS)

Document Control

• Effective Date: [Date]
• Version: 1.0
• Jurisdiction: [Governing Jurisdiction/State]
• SAP Object Reference: [Internal SAP Document/Shipment Number]

1. LEGAL DISCLAIMER & COMPLIANCE NOTICE

This Bill of Lading (BOL) serves as a receipt of goods, a contract of carriage, and a document of title. This instrument is intended for integration with SAP ERP (SD/LE/TM modules). Parties acknowledge that data transmitted via Electronic Data Interchange (EDI) or SAP IDocs associated with this BOL shall constitute legally binding records. All logistics operations governed herein must comply with the Uniform Commercial Code (UCC) and international conventions (e.g., Hague-Visby Rules) where applicable.

2. PARTIES & SHIPMENT DATA

• Shipper (Consignor): [Company Name], [Address], [SAP Vendor/Customer ID]
• Consignee: [Full Legal Name], [Address], [SAP Customer/Plant ID]
• Carrier: [Carrier Name], [SCAC Code], [SAP Carrier ID]
• Shipment Date: [Date]
• Total Weight/Units: [Amount] / [Unit of Measure]
• SAP Shipment Reference: [Shipment Number]

3. OPERATIVE CLAUSES

1. Receipt of Goods: Carrier acknowledges receipt of the goods described in the attached SAP-generated Packing List (Material Document # [Number]) in apparent good order, except as noted.
2. Contract of Carriage: Carrier agrees to transport the specified goods from the point of origin to the designated destination in accordance with the terms of the Master Service Agreement (MSA) on file.
3. Liability Limits: Carrier’s liability for loss or damage shall be limited to $[Amount] per unit or as defined by the governing tariff, whichever is lower. Claims must be submitted in writing within [Number] days of delivery.
4. SAP Data Integrity: The electronic data submitted via SAP IDoc [IDoc Number] supersedes any physical notations on this BOL in the event of discrepancy, unless a physical exception is signed by an authorized representative at the point of transfer.
5. Title and Risk: Title and risk of loss shall pass to the Consignee upon [Transfer of Possession/Delivery at Destination].
6. Governing Law: This agreement shall be governed by the laws of [Jurisdiction], without regard to conflict of law principles.

4. EXECUTION & SIGNATURES

Shipper Representative: Signature: __________________________ Printed Name: __________________________ Title: ______________________________ Date: ________________________________

Carrier Representative: Signature: __________________________ Printed Name: __________________________ Title: ______________________________ Date: ________________________________

5. EXECUTION & SAP INTEGRATION GUIDE

• Step 1: SAP Data Validation: Before printing, ensure the "Shipment" (VT01N/VT02N) status in SAP is set to 'Planned' or 'Active'. Confirm all HUs (Handling Units) are assigned.
• Step 2: Output Generation: Trigger the BOL output type (e.g., ZBOL) in the SAP shipment document to pull the exact quantities, weights, and batch numbers directly from the SAP database to ensure data accuracy.
• Step 3: Execution: Both parties must sign the physical copy upon loading. A digital scan of the signed document must be attached to the SAP Shipment Object via the Generic Object Services (GOS) attachment button (Paperclip icon).
• Step 4: Posting Goods Issue (PGI): Once the document is signed and the vehicle departs, execute the PGI in SAP (VT02N) to trigger the financial accounting document and update inventory valuation.
• Step 5: Record Retention: Store the original signed BOL in accordance with the corporate document retention policy (typically 7 years) to satisfy potential audit requirements by Tax or Customs authorities.
• Step 6: Enforcement: In the event of a dispute, provide the SAP Audit Trail (Change Documents for the Shipment) alongside this BOL as primary evidentiary support.