EDI to NYK
From UG
(Difference between revisions)
(→Info) |
(→SOW 1 EDI to NYK) |
||
| Line 28: | Line 28: | ||
==== Core Requirements ==== | ==== Core Requirements ==== | ||
* In Master, when Steamshipline is "NYK" show "Submit Booking Request" button (clicking this should send EDI 300 message to NYK). | * 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). | * Also for such Master, provide an ability to send "Shipment Instructions" (EDI 304). | ||
| - | * Provide receiving | + | * 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. | |
| - | * Implement the processing of exceptions. | + | |
* Reflect all related actions of sending/receiving/handling in CT2 System Log. | * Reflect all related actions of sending/receiving/handling in CT2 System Log. | ||
| + | * Keep all messaged in archive folder on FTP server. | ||
==== Solution ==== | ==== Solution ==== | ||
* '''Functionality''' | * '''Functionality''' | ||
| - | :* Carrier Booking Request is made from | + | :* Carrier Booking Request/Cancellation or Shipping Instructions is made from a Master. |
| - | :* Import booking confirmation from the carrier into Master and populate CT fields per current CT/M relationships. | + | :* Import booking confirmation, status updates and other incoming EDIs from the carrier into Master and populate CT fields per current CT/M relationships. |
* '''Communications''' | * '''Communications''' | ||
| - | :* CT2 address: dev.jaguarfreight.com | + | :* CT2 address: dev.jaguarfreight.com (id: nyk_dev, pwd: *** <!-- ??? -->) |
| - | + | :* FTP folder for incoming messages = "inbound" | |
| - | + | :* FTP folder for outgoing messages = "outbound" | |
| - | :* | + | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
* '''Mapping''' | * '''Mapping''' | ||
| - | :* EDI 300 | + | :* EDI 300 - Booking Request, Booking Cancellation |
| - | :* EDI 304 | + | :* EDI 304 - Shipping Instructions |
| - | :* EDI 315 | + | :* 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 <span style="color:red">“'''P'''”(''Production Data'')</span> only as Usage Indicator in ISA15. | ||
Revision as of 12:21, 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).
- "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.
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
