EDI to Schenker
From UG
Contents |
Info
- CT2 and Schenker agreed to use EDI 300 for bookings and EDI 214 for status updates.
- Schenker EDI policy is:
- to push outbound documents to our client’s servers
- expect clients to push files to Schenker's server.
SOWs
SOW 1 EDI to Schenker
mantis: 0004742 (phase: Dev, status: new)
Core Requirements
- FTP credentials
- test:
- address: dev.jaguarfreight.com
- login: schenker_dev
- password: *********
- production:
- address: ct.jaguarfreight.com
- login: schenker
- password: *********
- List of Milestone Events for Air and Ocean
- ISA and GS IDs for test and production
Solution
- Currently, Schenker would want the booking emails sent to group mailbox: roacartage@dbschenker.com
- Common IDs
- EDI 300 mapping (bookings)
- EDI 214 mapping (status updates)
SOW 2: ...
mantis: ??? (phase: ???, status: ???)
Core Requirements
- ...
- ...
Solution