EDI to Schenker

From UG

Contents 1 Info 2 SOWs 2.1 SOW 1 EDI to Schenker 2.1.1 Core Requirements 2.1.2 Solution 2.2 SOW 2: ... 2.2.1 Core Requirements 2.2.2 Solution

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

TBD

---