EDI to Schenker

From UG

Revision as of 14:24, 18 December 2014 by Andrei (Talk | contribs)
Jump to: navigation, search


Contents

Info

  • This article covers Electronic Data Interchange (EDI) between CT2 as Client and Schenker as 3PL Company.
  • It was agreed to use messages in ANSI X12 Standards:
  • EDI 300 for bookings (from CT2 to Schenker)
  • EDI 214 for status updates (from Schenker to CT2)

SOWs

SOW 1 EDI to Schenker


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

Core Requirements

  • Communications
  • Schenker EDI policy is:
  • to push outbound documents to our client’s servers
  • expect clients to push files to Schenker's server.
  • 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 (value in element AT701 of EDI 214).
  • Booked - A1
  • Estimated Time of Departure - C1
  • Estimated Time of Arrival - B6
  • Arrival - X4
  • Departure - AF
  • Pick up and delivery dates(estimated and actual) - to be confirmed
  • ISA and GS IDs for test and production
  • test:
  • ISA*00* *00* *02*JAFR *ZZ*SCHENKERAMT *140514*1631*U*00401*000000001*0*T*>~
  • GS*IM*JAFR*SCHENKERAMT*20140514*163038*118039*X*004010~
  • production:
  • ISA*00* *00* *02*JAFR *ZZ*SCHENKERAM *140514*1631*U*00401*000000001*0*P*>~
  • GS*IM*JAFR*SCHENKERAM*20140514*163038*118039*X*004010~

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

TBD



Personal tools