EDI to Evergreen
From UG
(Difference between revisions)
(→Solution) |
|||
| (10 intermediate revisions not shown) | |||
| Line 3: | Line 3: | ||
== Info == | == 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 == | == SOWs == | ||
| Line 13: | Line 17: | ||
==== Core Requirements ==== | ==== 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 ==== | ==== 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 | ||
| Line 26: | Line 44: | ||
'''mantis''': [http://mantis.jaguarfreight.com/mantis/view.php?id=4597 '''4597'''] (''phase:'' Dev, ''status:'' new) | '''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 ==== | ==== Core Requirements ==== | ||
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
