EDI to Evergreen
From UG
Contents |
Info
- This article covers Electronic Data Interchange (EDI) between CT2 as Client and Evergreen as 3PL Company.
- It was agreed to use messages in ANSI X12 Standards:
- EDI 300 - Reservation (Booking Request) (Ocean), from CT2 to Evergreen
- EDI 304 - Shipping Instructions, from CT2 to Evergreen
- EDI 315 - Status Details (Ocean), from Evergreen to CT2
SOWs
SOW 1 EDI to Evergreen
mantis: 0004573 (phase: Dev, status: started)
Core Requirements
- In Master, when Steamshipline is "Evergreen" show "Submit Booking Request" button (clicking this should send EDI 300 message to Evergreen).
- Also for such Master, provide an ability to send "Shipment Instructions" (EDI 304).
- Provide receiving "Status Details (Ocean)" messages (EDI 315) and handling Status Updates in appropriated Master records of CT2.
- Reflect the process of sending in CT2 System Log.
Solution
- Communications
- CT2 address: dev.jaguarfreight.com
- id: evergreen_dev
- pwd: ***
- Evergreen address: tpegw801.shipmentonline.com
- id: usj001477
- pwd: ***
- Mapping
- EDI 300
- EDI 304
- EDI 315
SOW 2: EDI Carrier Integration
mantis: 4597 (phase: Dev, status: new)
Core Requirements
- Carrier Booking Request is made from the Master.
- Import booking confirmation from the carrier into Master and populate CT fields per current CT/M relationships.
- User creates "MBL" document > option to "transmit via EDI".
Solution
- EDI carriers = show a "transmit booking request" option.
- Additional option for EDI carriers - "Save/open" AND transmit to carrier via EDI
SOW 3: Create new CT2 fields related to EDI to Evergreen
mantis: 4688 (phase: Dev, status: feedback)
Core Requirements
- ...
- ...
Solution
