EDI to NYK

From UG

---

Revision as of 10:57, 23 January 2017

Contents 1 Info 2 SOWs 2.1 SOW 1 EDI to NYK 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 NYK 2.3.1 Core Requirements 2.3.2 Solution

Info

• This article covers Electronic Data Interchange (EDI) between CT2 as Client and NYK 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 NYK

---

parent mantis: 0005035 (phase: Dev, status: new)

Core Requirements

• In Master, when Steamshipline is "NYK" show "Submit Booking Request" button (clicking this should send EDI 300 message to NYK).
• 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: nyk_dev
• pwd: ***

• NYK address: not provided

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

---

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

Core Requirements

• ...
• ...

Solution

TBD

---