EDI to Evergreen

From UG

(Difference between revisions)
Jump to: navigation, search
(Info)
(Info)
Line 5: Line 5:
* This article covers Electronic Data Interchange ('''EDI''') between '''CT2''' ''as Client'' and '''Evergreen''' ''as 3PL Company''.
* 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:
* It was agreed to use messages in ANSI X12 Standards:
-
:* EDI 300 for Bookings/Reservation (Ocean Booking Request from CT2 to Evergreen)
+
:* EDI 300 - Reservation (Booking Request) (Ocean), from CT2 to Evergreen
-
:* EDI 304 for Shipping Instructions (from CT2 to Evergreen)
+
:* EDI 304 - Shipping Instructions, from CT2 to Evergreen
-
:* EDI 315 for Status Updates (Ocean Status Details from Evergreen to CT2)
+
:* EDI 315 - Status Details (Ocean), from Evergreen to CT2
== SOWs ==
== SOWs ==

Revision as of 11:31, 23 December 2014


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

  • ...

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



Personal tools