EDI to Schenker
From UG
(Difference between revisions)
(→Info) |
(→Solution) |
||
| Line 47: | Line 47: | ||
* Currently, Schenker would want the booking emails sent to group mailbox: roacartage@dbschenker.com | * Currently, Schenker would want the booking emails sent to group mailbox: roacartage@dbschenker.com | ||
* Common IDs | * Common IDs | ||
| - | * | + | * We send in XLS: |
| - | + | : Shipment information | |
| - | + | :* CT# | |
| - | + | :* PO Issued by Company | |
| - | + | :* Mode/Submode | |
| - | + | :* Created By | |
| - | + | :* Approval Date | |
| - | + | :* Cargo Available | |
| - | + | :* Cargo Due date | |
| - | + | :* Shipper | |
| - | + | :* Pick Up Location | |
| - | + | :* Ship To Location | |
| - | + | : Commodity information | |
| - | + | :* Invoice, P.O., SKU, Qty, Item Descr, Ttl # of plts, Ttl pkgs on plts, Units, Pick Up Instructions, Commodity Description | |
| - | + | : See example of spreadsheet attached in mantis | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
* EDI 214 mapping ''(status updates)'' example | * EDI 214 mapping ''(status updates)'' example | ||
ISA*00* *00* *ZZ*SCHENKERAMT *02*JAFR *141119*0213*U*00401*000002764*0*T*> | ISA*00* *00* *ZZ*SCHENKERAMT *02*JAFR *141119*0213*U*00401*000002764*0*T*> | ||
Revision as of 12:13, 24 December 2014
Contents |
Info
- This article covers Electronic Data Interchange (EDI) between CT2 as Client and Schenker as 3PL Company.
- It was agreed to use the following messaging:
- for bookings: XLS spreadsheet (sent from approved ASN to Schenker)
- for status updates: EDI 214 message in ANSI X12 Standard (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
- We send in XLS:
- Shipment information
- CT#
- PO Issued by Company
- Mode/Submode
- Created By
- Approval Date
- Cargo Available
- Cargo Due date
- Shipper
- Pick Up Location
- Ship To Location
- Commodity information
- Invoice, P.O., SKU, Qty, Item Descr, Ttl # of plts, Ttl pkgs on plts, Units, Pick Up Instructions, Commodity Description
- See example of spreadsheet attached in mantis
- EDI 214 mapping (status updates) example
ISA*00* *00* *ZZ*SCHENKERAMT *02*JAFR *141119*0213*U*00401*000002764*0*T*> GS*QM*SCHENKERAMT*JAFR*20141119*0213*2764*X*004010 ST*214*000002764 B10*ROA92018894*SHIPMENT_NUMBER*SCNK LX*1 AT7*X4*NS***20141115*175200*ES L11*1*QN*USARD1 SE*6*000002764 GE*1*2764 IEA*1*000002764
SOW 2: ...
mantis: ??? (phase: ???, status: ???)
Core Requirements
- ...
- ...
Solution
