EDI to NYK

From UG

Contents 1 Info 2 SOWs 2.1 SOW 1 EDI Carrier Integration to NYK / EDI to NYK 2.1.1 Core Requirements 2.1.2 Solution 2.2 SOW 2: Configuration and settings 2.2.1 Core Requirements 2.2.2 Solution 2.3 SOW 3: Booking Request in EDI 300 for NYK 2.3.1 Core Requirements 2.3.2 Solution 2.4 SOW 4: Shipping Instructions in EDI 304 for NYK 2.4.1 Core Requirements 2.4.2 Solution 2.5 SOW 5: Booking Confirmation in EDI 301 from NYK 2.5.1 Core Requirements 2.5.2 Solution 2.6 SOW 6: Functional Acknowledgment in EDI 997 from NYK 2.6.1 Core Requirements 2.6.2 Solution 2.7 SOW 7: Application Acknowledgment in EDI 824 from NYK 2.7.1 Core Requirements 2.7.2 Solution 2.8 SOW 8: Freight Receipt and Invoice (Ocean) in EDI 310 from NYK 2.8.1 Core Requirements 2.8.2 Solution 2.9 SOW 9: Arrival Notice (Ocean) in EDI 312 from NYK 2.9.1 Core Requirements 2.9.2 Solution 2.10 SOW 10: Status Details (Ocean) in EDI 315 from NYK 2.10.1 Core Requirements 2.10.2 Solution

Info

• This article covers Electronic Data Interchange (EDI) between CT2 as Client and NYK as EDI Carrier/3PL Company.

• It was agreed to use our FTP (Partner FTP Server) for exchanging EDI messages between Jaguar and NYK in ANSI X12 Standards:

• Outgoing EDI messages (From Partner to NYK):
  • EDI 300 - Booking Request, Booking Cancellation
  • EDI 304 - Shipping Instructions

• Incoming EDI messages (From NYK to Partner):
  • EDI 301 - Booking Confirmation
  • EDI 997 - Functional Acknowledgment
  • EDI 824 - Application Acknowledgment
  • EDI 310 - Freight Receipt and Invoice (Ocean)
  • EDI 312 - Arrival Notice (Ocean)
  • EDI 315 - Status Details (Ocean)

SOWs

SOW 1 EDI Carrier Integration to NYK / 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).

• "Submit Booking Request" will send EDI 300 with B104="N" for new request message or with B104="U" for updated request.
• "Submit Booking Cancellation" will send EDI 300 with B104="D".

• Also for such Master, provide an ability to send "Shipment Instructions" (EDI 304).
• Provide the receiving of incoming messages and handling the data including Status Updates from EDI 315 in appropriated Master records of CT2.
• Implement the processing of exceptions and notify appropriated users.
• Reflect all related actions of sending/receiving/handling in CT2 System Log.
• Keep all messaged in archive folder on FTP server.

Solution

• Functionality

• Carrier Booking Request/Cancellation or Shipping Instructions is made from a Master.
• Import booking confirmation, status updates and other incoming EDIs from the carrier into Master and populate CT fields per current CT/M relationships.

• Communications

• CT2 address: dev.jaguarfreight.com (id: nyk_dev, pwd: *** )
• FTP folder for incoming messages = "inbound"
• FTP folder for outgoing messages = "outbound"

• Mapping

• EDI 300 - Booking Request, Booking Cancellation
• EDI 304 - Shipping Instructions
• EDI 301 - Booking Confirmation
• EDI 997 - Functional Acknowledgment
• EDI 824 - Application Acknowledgment
• EDI 310 - Freight Receipt and Invoice (Ocean)
• EDI 312 - Arrival Notice (Ocean)
• EDI 315 - Status Details (Ocean)

• NOTE: NYK system can accept “P”(Production Data) only as Usage Indicator in ISA15.

• Exceptions

• Accepted / Rejected messages
• Unknown type of EDI message
• Booking Confirmation for unknown Master
• Status updates for unknown Booking Number

• Log and Archive features

• Log
• Archive

---

SOW 2: Configuration and settings

---

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

Core Requirements

• Parameters in property file.
• Admin part in UI

Solution

• Property file contains:

• Paths to Outbound/Inbound FTP folders for Dev and Prod environmets
• Access parameters (User ID, Password etc)
• EDI parameters (i.e. usage indicator for outgoing/incoming)

• NYK case - always send ISA15="P"

• Admin part in UI

• ability to enable/disable the process
• process parameters (period of requesting the folders etc)
• list of emails for notifications (if needed)
• possible refactoring to have unified settings for multiple 3PL

---

SOW 3: Booking Request in EDI 300 for NYK

---

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

Core Requirements

• ...
• ...

Solution

TBD

---

SOW 4: Shipping Instructions in EDI 304 for NYK

---

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

Core Requirements

• ...
• ...

Solution

TBD

---

SOW 5: Booking Confirmation in EDI 301 from NYK

---

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

Core Requirements

• ...
• ...

Solution

TBD

---

SOW 6: Functional Acknowledgment in EDI 997 from NYK

---

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

Core Requirements

• ...
• ...

Solution

TBD

---

SOW 7: Application Acknowledgment in EDI 824 from NYK

---

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

Core Requirements

• ...
• ...

Solution

TBD

---

SOW 8: Freight Receipt and Invoice (Ocean) in EDI 310 from NYK

---

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

Core Requirements

• ...
• ...

Solution

TBD

---

SOW 9: Arrival Notice (Ocean) in EDI 312 from NYK

---

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

Core Requirements

• ...
• ...

Solution

TBD

---

SOW 10: Status Details (Ocean) in EDI 315 from NYK

---

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

Core Requirements

• ...
• ...

Solution

TBD

---