Shipping Instructions

DCSA Repository / Information Model / Logical Data Model / 1. Shipment Journey - Logical Data Model / Booking and eBL - Logical Data Model / Shipping Instructions

Project:

Booking and eBL - Logical Data Model

Shipping Instructions : Public Class

Created:	10/19/2023 2:43:53 PM
Modified:	9/30/2024 9:23:53 AM
Author:	DCSA
Version:	2024.3

Project:
Author:	DCSA
Version:	2024.3
Phase:	1.0
Status:	Published
Complexity:	Easy
Difficulty:
Priority:
Multiplicity:
Advanced:
UUID:	{51F260A0-C384-48db-AA80-634AFA4912FF}
Appears In:	LDM Overall (entity - subject area) LDM, LDM Overall (entity - subject area) LDM, Depricated - Domain LDM, BK - Booking and eBL Overview - Logical Data Model, BK - Transport Document - Logical Data Model, BK - Parties - Logical Data Model, BK - References - Logical Data Model, BK - Customs References - Logical Data Model, Temporary Diagram Class, API Design eBL 3.0, eBL Possession - Business Rule Model, WIP - Booking and eBL Overview, WIP - References

Note that multiple bookings can map to the same Shipping Instructions. This is only possible when the following attributes are common for all: <ul>
<li>Transport Plan</li><li>Shipment Locations</li><li>Receipt Type at Origin</li><li>Delivery Type at Destination</li><li>Cargo Movement Type at Origin</li><li>Cargo Movement Type at Destination</li><li>Service Contract Reference</li><li>Terms and Conditions</li><li>Invoice Payable AtPlace of B/L issue (if provided)</li></ul>

Attributes
Associations To
Associations From
Advanced
Other Links

Attribute

Scope

Type

Shipping Instructions Reference

Private

String(100)

Shipping Instructions Status Code

Private

String(50)

Updated Shipping Instructions Status Code

Private

String(50)

Transport Document Type Code

Private

String(3)

Notes:

Specifies the type of the associated Transport Document (Bill of Lading or Sea Waybill)

Is Shipped On Board Type

Private

Boolean

Notes:

Specifies whether the Transport document type is a received for shipment or shipped onboard

Number Of Copies With Charges

Private

Integer

Notes:

The requested number of copies of the Transport Document with charges to be issued by the carrier. Only applicable for physical documents

Number Of Copies Without Charges

Private

Integer

Notes:

The requested number of copies of the Transport Document without charges to be issued by the carrier. Only applicable for physical documents

Number Of Originals With Charges

Private

Integer

Notes:

Number of originals of the bill of lading that have been requested by the customer with charges. Only applicable for physical documents

Number Of Originals Without Charges

Private

Integer

Notes:

Number of originals of the bill of lading that have been requested by the customer without charges. Only applicable for physical documents

Freight Payment Term Code

Private

String(3)

Notes:

An indicator of whether freight and ancillary fees for the main transport are prepaid (PRE) or collect (COL). When prepaid the charges are the responsibility of the shipper or the Invoice payer on behalf of the shipper (if provided). When collect, the charges are the responsibility of the consignee or the Invoice payer on behalf of the consignee (if provided).

Method Of Payment

Private

String(1)

Is Electronic

Private

Boolean

Notes:

An indicator of whether the transport document is electronically transferred

Send To Platform

Private

String(4)

Is To Order

Private

Boolean

Notes:

Indicates whether the B/L is issued ‘to order’ or not. If TRUE, the B/L is considered negotiable and an Endorsee party can be defined in the Document parties. If no Endorsee is defined, the B/L is blank endorsed. If FALSE, the B/L is considered non-negotiable (also referred to as ‘straight’). Is to Order must be FALSE if Transport Document Type Code = SWB (Sea Waybill).

Is Carriers Agent At Destination Required

Private

Boolean

Notes:

Indicates whether the Carrier's agent at destination name, address and contact details should be included in the `Transport Document`.

Displayed Name For Place Of Receipt

Private

String(35)[5]

Notes:

Note that this is an array of String.

Displayed Name For Port Of Load

Private

String(35)[5]

Notes:

Link to a Displayed Name to be used in order to specify how the Port of Load should be displayed on the transport document to match the name and/or address provided on the letter of credit

Displayed Name For Port Of Discharge

Private

String(35)[5]

Notes:

Link to a Displayed Name to be used in order to specify how the Port of Discharge should be displayed on the transport document to match the name and/or address provided on the letter of credit

Displayed Name For Place Of Delivery

Private

String(35)[5]

Notes:

Link to a Displayed Name to be used in order to specify how the Place of Delivery should be displayed on the transport document to match the name and/or address provided on the letter of credit

Element	Source Role	Target Role
Party Contact Details Class	Name:	Name:
Details:
Routing Of Consignment Countries Class	Name:	Name:
Details:
House Bill Of Lading Class	Name:	Name:
Details: A list of `House Bill of Ladings` specified by the Shipper.<br/>
Location Class	Name:	Name: place of shipping instructions issue
Details: Must be provided by the shipper if the information is not part of the service contract or previously provided in the booking request.<br/>
Party Class	Name:	Name: issue to party
Details:
Shipping Instructions Class	Name: update	Name:
Details:
Notify Party Class	Name:	Name: N1, N2, NI as defined by type ICS2
Details:

Element	Source Role	Target Role
Consignment Item Class	Name:	Name:
Details:
Charges Payment Term Class	Name: destination charges	Name:
Details:
Reference Class	Name:	Name:
Details:
Party Class	Name: endorsee	Name:
Details:
Document Party Class	Name: other party	Name:
Details: The associated shipping instructions for the Document Party. There cannot be an association with both Shipping Instructions and Shipment.<br/>
Party Class	Name: seller	Name:
Details:
Party Class	Name: buyer	Name:
Details:
Transport Document Class	Name:	Name:
Details:
Requested Carrier Certificate Class	Name:	Name:
Details:
Requested Carrier Clause Class	Name:	Name:
Details:
Shipping Instructions Class	Name: update	Name:
Details:
Charges Payment Term Class	Name: origin charges	Name:
Details:
Customs Reference Class	Name:	Name:
Details:

Property	Value
isFinalSpecialization:	0

Object	Type	Connection	Direction	Notes
Shipping Instructions Update Code	Enumeration	Dependency	To
Shipping Instructions API	Interface	Dependency	From
BR EBL Determination of negotiable with named endorsement B/L	Requirement	Dependency	To
BK LDM IS this data type correct	Issue	Dependency	From
BR EBL Determination of straight B/L	Requirement	Dependency	To
Displayed Location	DataType	Dependency	To
eBL Solution Providers Code	Enumeration	Dependency	To
BR EBL Determination of negotiable blank endorsed B/L	Requirement	Dependency	To
Charges Payment Term	Class	Strong	From
Shipping Instructions API	Interface	Dependency	From
Transport Document Type Code	Enumeration	Dependency	To
Displayed Location	DataType	Dependency	To
Shipping Instructions Status Code	Enumeration	Dependency	To
Displayed Location	DataType	Dependency	To
BR EBL Determination Shipping instructions available as eBL	Requirement	Dependency	To
Displayed Location	DataType	Dependency	To
BR EBL Determination of negotiable blank endorsed B/L	Requirement	Dependency	To
BR EBL Determination of negotiable with named endorsement B/L	Requirement	Dependency	To
Shipping Instructions API	Interface	Dependency	From
BR EBL Determination of straight B/L	Requirement	Dependency	To
ICS2 Method Of Payment Code	Enumeration	Dependency	To
Requested Carrier Certificate	Class	Strong	From
Transport Document Status Code (DEPRECATED)	Enumeration	Dependency	To
Payment Term Type Code	Enumeration	Dependency	To
Shipping Instructions API	Interface	Dependency	From
Requested Carrier Clause	Class	Strong	From
Charges Payment Term	Class	Strong	From