Transport Document

Header Image
Project:
Transport Document : Public Class
Created: 10/19/2023 2:43:47 PM
Modified: 12/20/2024 10:58:26 AM
Author: DCSA
Version: 2024.4
Project:
Advanced:
The document that governs the terms of carriage between shipper and carrier for maritime transportation. 2 distinct types of transport documents exist: <br/><ol>
<li>Bill of Lading</li><li>Sea Waybill</li></ol><p/>
  • Attributes
  • Associations To
  • Associations From
  • Advanced
  • Other Links
Attribute Scope Type
Transport Document Reference Private String(20)
Notes: The unique identifier for an object of this class, in the scope of a single enterprise / organisational unit. In this case a unique reference allocated by the shipping line to the transport document and the main number used for tracking status of the shipment <br/>
Transport Document Sub Reference Private String(100)
Notes: Additional reference that can be optionally used alongside the `Transport Document Reference` in order to distinguish between versions of the same `Transport Document`.<br/>
Transport Document Status Code Private Document Status Code
 
Issue Date Private DateTime
Notes: Date when the transport document was issued<br/>
Shipped On Board Date Private Date
Notes: Date when the last container that is linked to the transport document is physically loaded onboard the vessel indicated on the transport document.<br/><br/>When provided on a Transport Document, the Transport Document is a Shipped On Board B/L.<br/><br/>Exactly one of <b>Shipped On Board</b> and <b>Receive For Shipment Date</b> must be provided on an issued B/L.<br/>
Received for Shipment Date Private Date
Notes: Date when the last container linked to the transport document is physically in the terminal (customers cleared against the intended vessel)<br/>
Displayed Shipped On Board Received For Shipment Public String(250)
Notes: The text to be displayed on the `Transport Document` as evidence that the goods have been received for shipment or shipped on board.<br/>
Number of Rider Pages Private Integer
Notes: The number of additional pages required to contain the goods description on a transport document. Only applicable for physical transport documents<br/>
Carrier Clause Public String(20000)
 
Terms and Conditions Public String(5000)
Notes: Carrier terms and conditions of transport.<br/>
Element Source Role Target Role
Shipping Instructions
Class  
Name:  
 
Name: Transport Document Reference
 
Details:
 
Party
Class  
Name:  
 
Name: issuing party
 
Details:
A link to the Party issuing the Transport Document. The Issuing Party can be an Agent, Carrier or anything represented by a Party<br/>
Location
Class  
Name:  
 
Name: place of transport document issue
 
Details:
 
Transports
Class  
Name:  
 
Name:  
 
Details:
 
Party
Class  
Name:  
 
Name: carriers agent at destination
 
Details:
 
Carrier
Class  
Name:  
 
Name: issuer
The carrier that has issued the transport document.
Details:
 
Element Source Role Target Role
Document Status Code
Class  
Name:  
 
Name:  
 
Details:
 
EBL Envelope
Class  
Name:  
 
Name:  
 
Details:
 
Charge
Class  
Name:  
 
Name:  
 
Details:
 
Property Value
isFinalSpecialization: 0
Object Type Connection Direction Notes
Ship Onboard Date BusinessObject Dependency To  
Transport Document API Interface Dependency From  
ShippingInstructions Class Dependency From  
Document Status Code Class Strong From  
«ArchiMate_Contract» Transport document (TD) Contract Dependency To  
Transport Document Class Dependency From  
Transport Document Class Dependency From  
«ArchiMate_BusinessObject» Transport document number BusinessObject Dependency To  
Ship Onboard Date BusinessObject Dependency To  
Shipped On Board Confirmation Contract Dependency To  
Payment Term Type Code Enumeration Dependency To  
Transport Document Class Dependency From  
Transport Document API Interface Dependency From  
Issuance API Interface Dependency From  
Transport Document Class Dependency From  
«ArchiMate_BusinessObject» (Number of) Rider pages BusinessObject Dependency To  
«ArchiMate_BusinessObject» Transport document type BusinessObject Dependency To  
LDM TD Where is Shipper attached to the Transport Document? Issue Dependency From  
LDM TD Mutiple Transport Document classes exist, but they a slightly different Issue Dependency From  
Transport Document Status Enumeration Dependency To  
Transport Document Class Dependency From  
«ArchiMate_BusinessObject» Shipping Instructions Reference BusinessObject Dependency To  
Transport Document API Interface Dependency To  
ShippingInstructions Class Dependency From