EDI to Evergreen

From UG

(Difference between revisions)
Jump to: navigation, search
(Created page with 'Category:3PL Integration == Info == parent: [http://mantis.jaguarfreight.com/mantis/view.php?id=4227 4227] == See Also === * ASN_20_Solution#ASN_transmit * [[:Categor…')
(→Solution)
 
(11 intermediate revisions not shown)
Line 3: Line 3:
== Info ==
== Info ==
-
parent: [http://mantis.jaguarfreight.com/mantis/view.php?id=4227 4227]
+
* 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
-
== See Also ===
+
== SOWs ==
-
* [[ASN_20_Solution#ASN_transmit]]
+
=== SOW 1 EDI to Evergreen ===
-
* [[:Category:ASN 20]]
+
<hr>
-
== SOWs ==
+
'''mantis''': [http://mantis.jaguarfreight.com/mantis/view.php?id=4573 0004573] (''phase:'' Dev, ''status:'' started)
-
* [http://mantis.jaguarfreight.com/mantis/view.php?id=4573 0004573]: EDI to Evergreen
+
 
 +
==== 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 ====
 +
* '''Functionality'''
 +
* '''Communications'''
 +
:* CT2 address: dev.jaguarfreight.com
 +
::* id: evergreen_dev 
 +
::* pwd: *** <!-- FAUytV4kjuV2 -->
 +
:* Evergreen address: tpegw801.shipmentonline.com
 +
::* id: usj001477
 +
::* pwd: ***<!-- gpQDb6eI -->
 +
* '''Mapping'''
 +
:* EDI 300
 +
:* EDI 304
 +
:* EDI 315
 +
 
 +
 
 +
 
 +
<hr>
 +
 
 +
=== SOW 2: EDI Carrier Integration ===
 +
<hr>
 +
 
 +
'''mantis''': [http://mantis.jaguarfreight.com/mantis/view.php?id=4597 '''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
 +
 
 +
 
 +
 
 +
<hr>
 +
 
 +
=== SOW 3: Create new CT2 fields related to EDI to Evergreen ===
 +
<hr>
 +
 
 +
'''mantis''': [http://mantis.jaguarfreight.com/mantis/view.php?id=4688 '''4688'''] (''phase:'' Dev, ''status:'' feedback)
 +
 
 +
==== Core Requirements ====
 +
* ...
 +
* ...
 +
 
 +
==== Solution ====
 +
[[TBD]]
 +
 
 +
 
 +
 
 +
<hr>

Current revision as of 14:26, 23 December 2014


Contents

[edit] 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

[edit] SOWs

[edit] SOW 1 EDI to Evergreen

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

[edit] 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.

[edit] Solution

  • Functionality
  • 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


[edit] SOW 2: EDI Carrier Integration

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

[edit] 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".

[edit] Solution

  • EDI carriers = show a "transmit booking request" option.
  • Additional option for EDI carriers - "Save/open" AND transmit to carrier via EDI


[edit] SOW 3: Create new CT2 fields related to EDI to Evergreen

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

[edit] Core Requirements

  • ...
  • ...

[edit] Solution

TBD


Retrieved from "https://wiki.jaguarfreight.com/EDI_to_Evergreen"
Personal tools