EDI to Evergreen

From UG

Contents 1 Info 2 SOWs 2.1 SOW 1 EDI to Evergreen 2.1.1 Core Requirements 2.1.2 Solution 2.2 SOW 2: EDI Carrier Integration 2.2.1 Core Requirements 2.2.2 Solution 2.3 SOW 3: Create new CT2 fields related to EDI to Evergreen 2.3.1 Core Requirements 2.3.2 Solution

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 for Bookings/Reservation (Ocean Booking Request from CT2 to Evergreen)
• EDI 304 for Shipping Instructions (from CT2 to Evergreen)
• EDI 315 for Status Updates (Ocean Status Details from Evergreen to CT2)

SOWs

SOW 1 EDI to Evergreen

---

mantis: 0004573 (phase: Dev, status: started)

Core Requirements

• ...

Solution

• ...

---

SOW 2: EDI Carrier Integration

---

mantis: 4597 (phase: Dev, status: new)

Core Requirements

• ...
• ...

Solution

TBD

---

SOW 3: Create new CT2 fields related to EDI to Evergreen

---

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

Core Requirements

• ...
• ...

Solution

TBD

---