EDI to CargoSmart

From UG

(Difference between revisions)

Jump to: navigation, search

Current revision as of 12:46, 23 January 2017

[edit] Info

...

[edit] SOWs

[edit] SOW 1 EDI to CargoSmart (initial tasks)

mantis: 0004743 (phase: Dev, status: feedback)

[edit] Core Requirements

Implement EDI to Cargosmart to send booking request and shipment instruction to receive status updates to update CT2.

Sending
- EDI 300 Booking Request
- EDI 304 Shipment Instruction
Receiving
- EDI 301 Booking Confirmation
- EDI 315 Status Details (Ocean)

[edit] Solution

.

[edit] Post-Implementation Notes

2.39.0

Implement EDI to Cargosmart to send booking request and shipment instruction to receive status messages to update CT2.
Create ability to add contract number per office for each steamshipline in admin.

2.39.1

Implement EDI 300 and 304 messages to send “B.J. International, Inc. d/b/a Jaguar Freight Services” as hard coding master shipper information on EDI message

2.39.2

N/A

2.39.3

Provide ability to send EDI 300/304 from Master without shipments - remove validation

2.39.4

Provided some more mapping info for LX loop.

2.39.5

Provided some more required info to add validation for ports/terminals information.

2.39.6

Provided some more mapping info for default weight value.

2.39.7

Update a log for some updated vessel name info from 301.

2.40.2

Create an admin setting to enable/disable process and how frequently to handle incoming files from cargosmart.

[edit] SOW 2 EDI 303 Booking Cancellation

mantises:

0004743, (phase: Dev, status: feedback)

0004909, (phase: UAT, status: new)

[edit] Core Requirements

Send EDI 303 Booking Cancellation to Cargosmart from CT Master

[edit] Solution

Implemented in sending of EDI 300 with B104="D".

[edit] SOW 3 Some Dates/Deadlines mapping in EDI 301 Booking Confirmation

mantises:

0004908, (phase: UAT, status: new)

[edit] Core Requirements

Upload dates into the Master fields as listed below:

EXPECTED SAILING DATE : 05/28/2015
PORT OF DISCHARGE : 06/11/2015

Upload deadline for the documents/dates:

AES (for US laden cargo) customs document deadline
Shipping Instruction/BL Master deadline for 304 transmission
CUTOFF DATE/TIME : deadline for delivering the cargo at the Port
Note: phase 1 comments, phase 2 “TEvents” (in the Master?) > Dashboards for impending/Past due dates will be needed.

Support mapping of RETURN LOCATION to “Master delivery” in Master GEN Tab

[edit] Solution

Implemented with receiving EDI 301:

EXPECTED SAILING DATE

Transmitting data: The ETD at First POL as declared in DTM*139*<Date> under R4*L.
CT2 mapping: ETD of Master Port of Loading.

EXPECTED ARRIVAL AT PORT OF DISCHARGE.

Transmitting data: The ETA at Last POD as declared in DTM*139*<Date> under R4*D.
CT2 mapping: ETA of Master Port of Discharge.

Shipping Instruction/BL Master deadline for 304 transmission.

Transmitting data: the Document Due Date as declared in DTM*649*<Date> under R4*L.
CT2 mapping: text line in "[Master] Bill Of Lading Comment".
Example: "304 submission deadline: 01-23-15".

CUTOFF DATE/TIME.

Transmitting data: ETA at Place of Receipt as declared in DTM*139*<Date> under R4*R.
CT2 mapping: text line in "[Master] Bill Of Lading Comment".
Example: "Cargo to port delivery deadline: 01-20-15".

Not implemented because of no current mapping in 301 for:

AES (for US laden cargo) customs document deadline.
RETURN LOCATION.

[edit] SOW 4 EDI 304 Shipment Instruction

mantises:

0004743, (phase: Dev, status: feedback)

[edit] Core Requirements

Send EDI 304 Shipment Instruction to Cargosmart from CT Master

[edit] Solution

.

[edit] SOW 5 EDI 315 Status Details (Ocean)

mantises:

0004743, (phase: QA, status: released)

0004898, (phase: QA, status: released)

0005293, (phase: QA, status: released)

[edit] Core Requirements

Receive EDI 315 Status Details (Ocean) from Cargosmart to Master and related CT (s)

[edit] Solution

.

[edit] Post-Implementation Notes

Ports mapping in R4 segment (R401):
- R. Place of Receipt (Contractual). Place at which cargo enters the care and custody of carrier. // Origin Terminal in CT2
- L. Port of Loading (Operational). Port at which cargo is loaded on vessel.
- D. Port of Discharge (Operational). Port at which cargo is unloaded from vessel.
- E. Place of Delivery (Contractual). Place at which cargo leaves its care and custody of carrier. // Destination Terminal in CT2
Ports/Terminals are also updates from R4 segments:

R4*R*UN*BEANR*Antwerpen*BE~
DTM*140*20141231*0700~
R4*L*UN*NLRTM*Rotterdam*NL~
DTM*140*20150111*2157~
R4*D*UN*USNYC*New York*US***NY~
DTM*139*20150125*0230~
R4*E*UN*USNYC*New York*US***NY~
DTM*139*20150127*0700~

It will override B403 value if they are diferrent (probably that will not happened in real life).
Please also note that portOfDischarge will override destinationalTerminal and portOfLoading will override originalTerminal if terminals are disabled in CT editor. - THIS removed in mantis 0005348.

[edit] SOW Z Cargosmart Events

mantises:

0004743, (phase: Dev, status: feedback)

0004898, (phase: Dev, status: feedback)

[edit] Core Requirements

Add new date fields in CT2, per listed CT2 Fields Map for Cargosmart Events.

CT2 Fields Map for Cargosmart Events

Create new "Ocean Transportation Events" tab for new fields, in CT and Master.

[edit] Solution

Dates of Cargosmart events will be transmitted from Cargosmart via EDI 315 Status Details (Ocean) Transaction Set to update CT2 dates:

B4 segment (Beginning Segment for Inquiry or Reply) transmits:

B403: Shipment Status Code (AE in Example below)
B404: Date of last reported status of cargo (20150107 in Example below)
Example: B4***AE*20150107*0851**OOLU*041034*L*22GP*BEANR*UN*2~ means "Loaded on Board at First Port of Load on 07-Jan-2015"

N9 segment (Reference Identification Qualifier) with N901 = BN (Booking Number) transmits:

N902: Booking Number as Reference Identification (2559940731 in Example below)
Example: N9*BN*2559940731~

For Ocean shipments, the following fields will be updated from EDI 315 including "TEvents" tab:

Event Description	Shipment Status Code	CT2 Mapping
Arrival at Last Intermodal Hub	AR	Actual Arrival date - Destination Terminal
Last Vessel Arrival	VA	Actual Arrival Date - Port of Arrival
Actual Door Delivery	D	Actual Delivery Date
First Loaded on Rail Under Outbound	AL	Actual departure date - Origin Terminal
First Vessel Departure	VD	Actual Departure date - Port of Departure
Transshipment Vessel Departure	Z5	Actual Departure Date - Transshipment Port
Actual Door Pickup	AF	Actual Pick Up Date
Empty Container Picked Up	EE	New Fields (TEvents)
Full Container Received by Carrier at Origin	OA
Departure from First Intermodal Hub	RL
Arrival at First Port of Load	I
Loaded on Board at First Port of Load	AE
Loaded at Port	W6
Vessel Departure	X2
Loaded at Port of Transshipment	Z3
Discharged at Port of Transshipment	Z4
Discharged from Vessel at Last Port of Discharge	UV
Container Picked up from Port of Discharge/Transshipment Port	Y9
First Loaded on Rail Under Inbound	Z7
Intermodal Departure from Last Port of Discharge	Z6
Equipment Delayed due to Transportation	W3
Loaded on Rail	Y3
Arrival at Intermodal Hub by Rail	Y2
Gate In Full at Inland Terminal	W2
Gate Out Full at Inland Terminal	W1
Loaded on Truck	AM
Customs Hold	PA
Carrier Held	X9
Freight Charges Settled	NO
Carrier Released	CR
Customs Released	CT
Picked up at Final Destination for Delivery	Z8
Empty Container Returned to Carrier at Destination	RD

EDI to CargoSmart

From UG

Current revision as of 12:46, 23 January 2017

Contents

[edit] Info

[edit] SOWs

[edit] SOW 1 EDI to CargoSmart (initial tasks)

[edit] Core Requirements

[edit] Solution

[edit] Post-Implementation Notes

[edit] SOW 2 EDI 303 Booking Cancellation

[edit] Core Requirements

[edit] Solution

[edit] SOW 3 Some Dates/Deadlines mapping in EDI 301 Booking Confirmation

[edit] Core Requirements

[edit] Solution

[edit] SOW 4 EDI 304 Shipment Instruction

[edit] Core Requirements

[edit] Solution

[edit] SOW 5 EDI 315 Status Details (Ocean)

[edit] Core Requirements

[edit] Solution

[edit] Post-Implementation Notes

[edit] SOW Z Cargosmart Events

[edit] Core Requirements

[edit] Solution

Views

Personal tools

Navigation

Toolbox

Search

@@ Line 7: / Line 7: @@
 == SOWs ==
-=== SOW 1 EDI to CargoSmart ===
+=== SOW 1 EDI to CargoSmart (initial tasks) ===
 <hr>
@@ Line 16: / Line 16: @@
 :* Sending
 :** EDI 300 Booking Request
-:** EDI 303 Booking Cancellation
 :** EDI 304 Shipment Instruction
 :* Receiving
@@ Line 52: / Line 51: @@
 <hr>
-=== SOW 2 Cargosmart Events ===
+=== SOW 2 EDI 303 Booking Cancellation ===
+<hr>
+'''mantises''':
+: [http://mantis.jaguarfreight.com/mantis/view.php?id=4743 '''0004743'''],  (''phase:'' Dev, ''status:'' feedback)
+: [http://mantis.jaguarfreight.com/mantis/view.php?id=4909 '''0004909'''],  (''phase:'' UAT, ''status:'' new)
+==== Core Requirements ====
+* Send EDI 303 Booking Cancellation to Cargosmart from CT Master
+==== Solution ====
+* Implemented in sending of EDI 300 with B104="D".
+<hr>
+=== SOW 3 Some Dates/Deadlines mapping in EDI 301 Booking Confirmation ===
+<hr>
+'''mantises''':
+: [http://mantis.jaguarfreight.com/mantis/view.php?id=4908 '''0004908'''],  (''phase:'' UAT, ''status:'' new)
+==== Core Requirements ====
+* Upload dates into the Master fields as listed below:
+:* EXPECTED SAILING DATE : 05/28/2015
+:* PORT OF DISCHARGE : 06/11/2015
+* Upload deadline for the documents/dates:
+:* AES (for US laden cargo) customs document deadline
+:* Shipping Instruction/BL Master deadline for 304 transmission
+:* CUTOFF DATE/TIME : deadline for delivering the cargo at the Port
+:* Note: phase 1 comments, phase 2 “TEvents” (in the Master?) > Dashboards for impending/Past due dates will be needed.
+* Support mapping of RETURN LOCATION to “Master delivery” in Master GEN Tab
+==== Solution ====
+* '''Implemented''' with receiving EDI 301:
+:* EXPECTED SAILING DATE
+::* Transmitting data: The ETD at First POL as declared in DTM*139*<Date> under R4*L.
+::* CT2 mapping: ETD of Master Port of Loading.
+:* EXPECTED ARRIVAL AT PORT OF DISCHARGE.
+::* Transmitting data: The ETA at Last POD as declared in DTM*139*<Date> under R4*D.
+::* CT2 mapping: ETA of Master Port of Discharge.
+:* Shipping Instruction/BL Master deadline for 304 transmission.
+::* Transmitting data: the Document Due Date as declared in DTM*649*<Date> under R4*L.
+::* CT2 mapping: text line in "[Master] Bill Of Lading Comment".
+::* Example: "304 submission deadline: 01-23-15".
+:* CUTOFF DATE/TIME.
+::* Transmitting data: ETA at Place of Receipt as declared in DTM*139*<Date> under R4*R.
+::* CT2 mapping: text line in "[Master] Bill Of Lading Comment".
+::* Example: "Cargo to port delivery deadline: 01-20-15".
+* '''Not implemented''' because of no current mapping in 301 for:
+:* AES (for US laden cargo) customs document deadline.
+:* RETURN LOCATION.
+<hr>
+=== SOW 4 EDI 304 Shipment Instruction ===
+<hr>
+'''mantises''':
+: [http://mantis.jaguarfreight.com/mantis/view.php?id=4743 '''0004743'''],  (''phase:'' Dev, ''status:'' feedback)
+==== Core Requirements ====
+* Send EDI 304 Shipment Instruction to Cargosmart from CT Master
+==== Solution ====
+* .
+<hr>
+=== SOW 5 EDI 315 Status Details (Ocean) ===
+<hr>
+'''mantises''':
+: [http://mantis.jaguarfreight.com/mantis/view.php?id=4743 '''0004743'''],  (''phase:'' QA, ''status:'' released)
+: [http://mantis.jaguarfreight.com/mantis/view.php?id=4898 '''0004898'''],  (''phase:'' QA, ''status:'' released)
+: [http://mantis.jaguarfreight.com/mantis/view.php?id=5293 '''0005293'''],  (''phase:'' QA, ''status:'' released)
+==== Core Requirements ====
+* Receive EDI 315 Status Details (Ocean) from Cargosmart to Master and related CT (s)
+==== Solution ====
+* .
+==== Post-Implementation Notes ====
+* Ports mapping in R4 segment (R401):
+** R. Place of Receipt (Contractual). Place at which cargo enters the care and custody of carrier. // Origin Terminal in CT2
+** L. Port of Loading (Operational). Port at which cargo is loaded on vessel.
+** D. Port of Discharge (Operational). Port at which cargo is unloaded from vessel.
+** E. Place of Delivery (Contractual). Place at which cargo leaves its care and custody of carrier. // Destination Terminal in CT2
+* Ports/Terminals are also updates from R4 segments:
+ R4*R*UN*BEANR*Antwerpen*BE~
+ DTM*140*20141231*0700~
+ R4*L*UN*NLRTM*Rotterdam*NL~
+ DTM*140*20150111*2157~
+ R4*D*UN*USNYC*New York*US***NY~
+ DTM*139*20150125*0230~
+ R4*E*UN*USNYC*New York*US***NY~
+ DTM*139*20150127*0700~
+* It will override B403 value if they are diferrent (''probably that will not happened in real life'').
+* Please also note that ''portOfDischarge'' will override ''destinationalTerminal'' and ''portOfLoading'' will override ''originalTerminal'' if terminals are disabled in CT editor. - <span style="color:red">THIS removed in mantis [http://mantis.jaguarfreight.com/mantis/view.php?id=5348 '''0005348''']</span>.
+<hr>
+=== SOW Z Cargosmart Events ===
 <hr>
@@ Line 69: / Line 179: @@
 ::* '''B403''': Shipment Status Code ('''''AE''''' in ''Example'' below)
 ::* '''B404''': Date of last reported status of cargo ('''''20150107''''' in ''Example'' below)
-::* ''Example: B4***'''AE'''*'''20150107'''*0851**OOLU*041034*L*22GP*BEANR*UN*2~'' means ''"Loaded on Vessel on 07-Jan-2015"''
+::* ''Example: B4***'''AE'''*'''20150107'''*0851**OOLU*041034*L*22GP*BEANR*UN*2~'' means ''"Loaded on Board at First Port of Load on 07-Jan-2015"''
 :* '''N9''' segment (''Reference Identification Qualifier'') with N901 = '''BN''' (Booking Number) transmits:
 ::* '''N902''': Booking Number as Reference Identification ('''''2559940731''''' in ''Example'' below)
 ::* ''Example: N9*BN*'''2559940731'''~''
-* For Ocean shipments, "TEvents" tab added to CT Editor. It contains the following fields:
+* For Ocean shipments, the following fields will be updated from EDI 315 including "TEvents" tab:
 {| border="1" valign="top" style="border-collapse:collapse;margin: 1em auto 1em auto;" cellpadding="2" width="75%"
 |-
@@ Line 111: / Line 221: @@
 | Empty Container Picked Up
 | style="text-align: center;" | EE
-| New Field - ?
+| rowspan="26" style="text-align: center;" | New Fields (TEvents)
 |-
 | Full Container Received by Carrier at Origin
 | style="text-align: center;" | OA
-| New Field - ?
 |-
 | Departure from First Intermodal Hub
 | style="text-align: center;" | RL
-| New Field - ?
 |-
 | Arrival at First Port of Load
 | style="text-align: center;" | I
-| New Field - ?
 |-
 | Loaded on Board at First Port of Load
 | style="text-align: center;" | AE
-| New Field - ?
 |-
 | Loaded at Port
 | style="text-align: center;" | W6
-| New Field - ?
 |-
 | Vessel Departure
 | style="text-align: center;" | X2
-| New Field - ?
 |-
 | Loaded at Port of Transshipment
 | style="text-align: center;" | Z3
-| New Field - ?
 |-
 | Discharged at Port of Transshipment
 | style="text-align: center;" | Z4
-| New Field - ?
 |-
 | Discharged from Vessel at Last Port of Discharge
 | style="text-align: center;" | UV
-| New Field - ?
 |-
 | Container Picked up from Port of Discharge/Transshipment Port
 | style="text-align: center;" | Y9
-| New Field - ?
 |-
 | First Loaded on Rail Under Inbound
 | style="text-align: center;" | Z7
-| New Field - ?
 |-
 | Intermodal Departure from Last Port of Discharge
 | style="text-align: center;" | Z6
-| New Field - ?
 |-
 | Equipment Delayed due to Transportation
 | style="text-align: center;" | W3
-| New Field - ?
 |-
 | Loaded on Rail
 | style="text-align: center;" | Y3
-| New Field - ?
 |-
 | Arrival at Intermodal Hub by Rail
 | style="text-align: center;" | Y2
-| New Field - ?
 |-
 | Gate In Full at Inland Terminal
 | style="text-align: center;" | W2
-| New Field - ?
 |-
 | Gate Out Full at Inland Terminal
 | style="text-align: center;" | W1
-| New Field - ?
 |-
 | Loaded on Truck
 | style="text-align: center;" | AM
-| New Field - ?
 |-
 | Customs Hold
 | style="text-align: center;" | PA
-| New Field - ?
 |-
 | Carrier Held
 | style="text-align: center;" | X9
-| New Field - ?
 |-
 | Freight Charges Settled
 | style="text-align: center;" | NO
-| New Field - ?
 |-
 | Carrier Released
 | style="text-align: center;" | CR
-| New Field - ?
 |-
 | Customs Released
 | style="text-align: center;" | CT
-| New Field - ?
 |-
 | Picked up at Final Destination for Delivery
 | style="text-align: center;" | Z8
-| New Field - ?
 |-
 | Empty Container Returned to Carrier at Destination
 | style="text-align: center;" | RD
-| New Field - ?
 |-
 |}