EDI to Schenker
From UG
(Difference between revisions)
(Created page with 'Category:3PL Integration == Info == * ... == SOWs == === SOW 1 EDI to Schenker === <hr> '''mantis''': [http://mantis.jaguarfreight.com/mantis/view.php?id=4742 0004742] …') |
(→Info) |
||
| Line 3: | Line 3: | ||
== Info == | == Info == | ||
| - | * . | + | * CT2 and Schenker agreed to use EDI 300 (bookings) and EDI 214 (status updates). |
| - | + | * Schenker EDI policy is: | |
| + | :* to push outbound documents to our client’s servers | ||
| + | :* we expect clients to push files to our server. | ||
| + | * Once in production, booking emails should be sent to Schenker group mailbox: roacartage@dbschenker.com | ||
== SOWs == | == SOWs == | ||
Revision as of 14:18, 17 December 2014
Contents |
Info
- CT2 and Schenker agreed to use EDI 300 (bookings) and EDI 214 (status updates).
- Schenker EDI policy is:
- to push outbound documents to our client’s servers
- we expect clients to push files to our server.
- Once in production, booking emails should be sent to Schenker group mailbox: roacartage@dbschenker.com
SOWs
SOW 1 EDI to Schenker
mantis: 0004742 (phase: Dev, status: new)
Core Requirements
- ...
Solution
- ...
SOW 2: ...
mantis: ??? (phase: ???, status: ???)
Core Requirements
- ...
- ...
Solution
