EDI to NYK
From UG
(Difference between revisions)
(→Core Requirements) |
|||
(7 intermediate revisions not shown) | |||
Line 21: | Line 21: | ||
== SOWs == | == SOWs == | ||
- | === SOW 1 EDI to NYK === | + | === SOW 1 EDI Carrier Integration to NYK / EDI to NYK === |
<hr> | <hr> | ||
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. | ||
+ | |||
+ | * '''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 | ||
<hr> | <hr> | ||
- | === SOW 2: | + | === SOW 2: Configuration and settings === |
<hr> | <hr> | ||
- | '''mantis''': [http://mantis.jaguarfreight.com/mantis/view.php?id= | + | '''mantis''': [http://mantis.jaguarfreight.com/mantis/view.php?id=5682 '''5682'''] (''phase:'' Dev, ''status:'' started) |
==== Core Requirements ==== | ==== Core Requirements ==== | ||
- | * | + | * Parameters in property file. |
- | * | + | * Admin part in UI |
==== Solution ==== | ==== 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 | ||
<hr> | <hr> | ||
- | === SOW 3: | + | === SOW 3: Booking Request in EDI 300 for NYK === |
<hr> | <hr> | ||
- | '''mantis''': [http://mantis.jaguarfreight.com/mantis/view.php?id= | + | '''mantis''': [http://mantis.jaguarfreight.com/mantis/view.php?id=5683 '''5683'''] (''phase:'' Dev, ''status:'' new) |
==== Core Requirements ==== | ==== Core Requirements ==== | ||
Line 87: | Line 108: | ||
[[TBD]] | [[TBD]] | ||
+ | |||
+ | <hr> | ||
+ | |||
+ | === SOW 4: Shipping Instructions in EDI 304 for NYK === | ||
+ | <hr> | ||
+ | |||
+ | '''mantis''': [http://mantis.jaguarfreight.com/mantis/view.php?id=5684 '''5684'''] (''phase:'' Dev, ''status:'' new) | ||
+ | |||
+ | ==== Core Requirements ==== | ||
+ | * ... | ||
+ | * ... | ||
+ | |||
+ | ==== Solution ==== | ||
+ | [[TBD]] | ||
+ | |||
+ | |||
+ | <hr> | ||
+ | |||
+ | === SOW 5: Booking Confirmation in EDI 301 from NYK === | ||
+ | <hr> | ||
+ | |||
+ | '''mantis''': [http://mantis.jaguarfreight.com/mantis/view.php?id=5685 '''5685'''] (''phase:'' Dev, ''status:'' new) | ||
+ | |||
+ | ==== Core Requirements ==== | ||
+ | * ... | ||
+ | * ... | ||
+ | |||
+ | ==== Solution ==== | ||
+ | [[TBD]] | ||
+ | |||
+ | |||
+ | <hr> | ||
+ | |||
+ | === SOW 6: Functional Acknowledgment in EDI 997 from NYK === | ||
+ | <hr> | ||
+ | |||
+ | '''mantis''': [http://mantis.jaguarfreight.com/mantis/view.php?id=5686 '''5686'''] (''phase:'' Dev, ''status:'' new) | ||
+ | |||
+ | ==== Core Requirements ==== | ||
+ | * ... | ||
+ | * ... | ||
+ | |||
+ | ==== Solution ==== | ||
+ | [[TBD]] | ||
+ | |||
+ | |||
+ | <hr> | ||
+ | |||
+ | === SOW 7: Application Acknowledgment in EDI 824 from NYK === | ||
+ | <hr> | ||
+ | |||
+ | '''mantis''': [http://mantis.jaguarfreight.com/mantis/view.php?id=5687 '''5687'''] (''phase:'' Dev, ''status:'' new) | ||
+ | |||
+ | ==== Core Requirements ==== | ||
+ | * ... | ||
+ | * ... | ||
+ | |||
+ | ==== Solution ==== | ||
+ | [[TBD]] | ||
+ | |||
+ | |||
+ | <hr> | ||
+ | |||
+ | === SOW 8: Freight Receipt and Invoice (Ocean) in EDI 310 from NYK === | ||
+ | <hr> | ||
+ | |||
+ | '''mantis''': [http://mantis.jaguarfreight.com/mantis/view.php?id=5688 '''5688'''] (''phase:'' Dev, ''status:'' new) | ||
+ | |||
+ | ==== Core Requirements ==== | ||
+ | * ... | ||
+ | * ... | ||
+ | |||
+ | ==== Solution ==== | ||
+ | [[TBD]] | ||
+ | |||
+ | |||
+ | <hr> | ||
+ | |||
+ | === SOW 9: Arrival Notice (Ocean) in EDI 312 from NYK === | ||
+ | <hr> | ||
+ | |||
+ | '''mantis''': [http://mantis.jaguarfreight.com/mantis/view.php?id=5689 '''5689'''] (''phase:'' Dev, ''status:'' new) | ||
+ | |||
+ | ==== Core Requirements ==== | ||
+ | * ... | ||
+ | * ... | ||
+ | |||
+ | ==== Solution ==== | ||
+ | [[TBD]] | ||
+ | |||
+ | |||
+ | <hr> | ||
+ | |||
+ | === SOW 10: Status Details (Ocean) in EDI 315 from NYK === | ||
+ | <hr> | ||
+ | |||
+ | '''mantis''': [http://mantis.jaguarfreight.com/mantis/view.php?id=5690 '''5690'''] (''phase:'' Dev, ''status:'' new) | ||
+ | |||
+ | ==== Core Requirements ==== | ||
+ | * ... | ||
+ | * ... | ||
+ | |||
+ | ==== Solution ==== | ||
+ | [[TBD]] | ||
<hr> | <hr> |
Current revision as of 12:43, 23 January 2017
[edit] 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):
[edit] SOWs
[edit] SOW 1 EDI Carrier Integration to NYK / EDI to NYK
parent mantis: 0005035 (phase: Dev, status: new)
[edit] 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.
[edit] 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
[edit] SOW 2: Configuration and settings
mantis: 5682 (phase: Dev, status: started)
[edit] Core Requirements
- Parameters in property file.
- Admin part in UI
[edit] 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
[edit] SOW 3: Booking Request in EDI 300 for NYK
mantis: 5683 (phase: Dev, status: new)
[edit] Core Requirements
- ...
- ...
[edit] Solution
[edit] SOW 4: Shipping Instructions in EDI 304 for NYK
mantis: 5684 (phase: Dev, status: new)
[edit] Core Requirements
- ...
- ...
[edit] Solution
[edit] SOW 5: Booking Confirmation in EDI 301 from NYK
mantis: 5685 (phase: Dev, status: new)
[edit] Core Requirements
- ...
- ...
[edit] Solution
[edit] SOW 6: Functional Acknowledgment in EDI 997 from NYK
mantis: 5686 (phase: Dev, status: new)
[edit] Core Requirements
- ...
- ...
[edit] Solution
[edit] SOW 7: Application Acknowledgment in EDI 824 from NYK
mantis: 5687 (phase: Dev, status: new)
[edit] Core Requirements
- ...
- ...
[edit] Solution
[edit] SOW 8: Freight Receipt and Invoice (Ocean) in EDI 310 from NYK
mantis: 5688 (phase: Dev, status: new)
[edit] Core Requirements
- ...
- ...
[edit] Solution
[edit] SOW 9: Arrival Notice (Ocean) in EDI 312 from NYK
mantis: 5689 (phase: Dev, status: new)
[edit] Core Requirements
- ...
- ...
[edit] Solution
[edit] SOW 10: Status Details (Ocean) in EDI 315 from NYK
mantis: 5690 (phase: Dev, status: new)
[edit] Core Requirements
- ...
- ...
[edit] Solution