EDI to CargoSmart
From UG
Contents |
Info
- ...
SOWs
SOW 1 EDI to CargoSmart
mantis: 0004743 (phase: Dev, status: feedback)
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 303 Booking Cancellation
- EDI 304 Shipment Instruction
- Receiving
- EDI 301 Booking Confirmation
- EDI 315 Status Details (Ocean)
- Sending
Solution
- .
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.
SOW 2 Cargosmart Events
mantises:
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.
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 Vessel 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:
- Empty Container Picked Up
- Full Container Received by Carrier at Origin
- Departure from First Intermodal Hub
- Arrival at First Port of Load
- Loaded on Board at First Port of Load
- Loaded at Port
- Vessel Departure
- Loaded at Port of Transshipment
- Discharged at Port of Transshipment
- Discharged from Vessel at Last Port of Discharge
- Container Picked up from Port of Discharge/Transshipment Port
- First Loaded on Rail Under Inbound
- Intermodal Departure from Last Port of Discharge
- Equipment Delayed due to Transportation
- Loaded on Rail
- Arrival at Intermodal Hub by Rail
- Gate In Full at Inland Terminal
- Gate Out Full at Inland Terminal
- Loaded on Truck
- Customs Hold
- Carrier Held
- Freight Charges Settled
- Carrier Released
- Customs Released
- Picked up at Final Destination for Delivery
- Empty Container Returned to Carrier at Destination