EDI to NYK
From UG
(Difference between revisions)
(→Info) |
(→Info) |
||
Line 18: | Line 18: | ||
:** EDI 312 - Arrival Notice (Ocean) | :** EDI 312 - Arrival Notice (Ocean) | ||
:** EDI 315 - Status Details (Ocean) | :** EDI 315 - Status Details (Ocean) | ||
- | |||
- | |||
== SOWs == | == SOWs == |
Revision as of 11:51, 23 January 2017
Contents |
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
- Outgoing EDI messages (From Partner to NYK):
- 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)
- Incoming EDI messages (From NYK to Partner):
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)" incoming messages and handling the data including Status Updates from EDI 315 in appropriated Master records of CT2.
- Keep all messaged in archive folder on FTP server.
- Implement the processing of exceptions.
- Reflect all related actions of sending/receiving/handling in CT2 System Log.
Solution
- Functionality
- 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.
- Communications
- CT2 address: dev.jaguarfreight.com
- id: nyk_dev
- pwd: ***
- Incoming folder
- id: [TBD]
- pwd: ***
- Outgoing folder
- id: [TBD]
- pwd: ***
- Mapping
- EDI 300
- EDI 304
- EDI 315
SOW 2: EDI Carrier Integration
mantis: 4597 (phase: Dev, status: new)
Core Requirements
- EDI carriers = show a "transmit booking request" option.
- Additional option for EDI carriers - "Save/open" AND transmit to carrier 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