EDI to Schenker

(Difference between revisions)

Revision as of 14:30, 17 December 2014

CT2 and Schenker agreed to use EDI 300 for bookings and EDI 214 for status updates.
Schenker EDI policy is:

mantis: 0004742 (phase: Dev, status: new)

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)

mantis: ??? (phase: ???, status: ???)

@@ Line 3: / Line 3: @@
 == Info ==
-* CT2 and Schenker agreed to use EDI 300 (bookings) and EDI 214 (status updates).
+* 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
-:* we expect clients to push files to our server.
+:* expect clients to push files to Schenker's server.
-* Once in production, booking emails should be sent to Schenker group mailbox: roacartage@dbschenker.com
 == SOWs ==
@@ Line 17: / Line 17: @@
 ==== 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)''