EDI to Schenker

From UG

Current revision as of 16:22, 13 January 2015

[edit] 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)

[edit] SOWs

[edit] SOW 1 EDI to Schenker

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

[edit] 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~

[edit] Solution

[edit] Booking

• Currently, Schenker would want the booking emails sent to group mailbox: roacartage@dbschenker.com

• "Schenker" is adding to ASN Misc in Admin section as 3PL
• Request to Schenker 3PL for booking is transmitting ASN info as an email with attachment in XLS format

• In attached spreadsheet, we send the following info to Schenker:

• 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

[edit] Status Updates

• Incoming Status Updates messages should be sent by Schenker in EDI 214 standard and received to Cybertrax FTP folder

• NOTE: servers and folders are different for testing and Production environments (according to requirements)

• CT2 checks the folder and handles received messages to update appropriate shipments

• Estimated Dates should be indicated with prefix "EST: "

• 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

• ISA, GS, ST
• B10 - Beginning Segment for Transportation Carrier Shipment Status Message

• B1001 - Reference Identification (Carrier Assigned Pro Number)
• B1002 - Shipment Identification Number (CT Shipment Number)
• B1003 - Standard Carrier Alpha Code (SCNK = Schenker)

• LX - Assigned Number (To reference a line number in a transaction set)

• Number assigned for differentiation within a transaction set

• AT7 - Shipment Status Details

• AT701 - Shipment Status Code

• A1 = Booked (provided by Schenker, not implemented)
• C1 = Estimated to Depart Terminal Location (Estimated Time of Departure)
• AF = Carrier Departed Pick-up Location with Shipment (Departure)
• B6 = Estimated to Arrive at Carrier Terminal (Estimated Time of Arrival)
• X4 = Arrived at Terminal Location (Arrival)

• AT702 - Shipment Status or Appointment Reason Code (NS = Normal Status)
• AT705 - Date
• AT706 - Time
• AT707 - Time Code (ES = Eastern Standard Time)

• L11 - Business Instructions and Reference Number

• L1101 - Reference Identification
• L1102 - Reference Identification Qualifier (QN = Stop Sequence Number)
• L1103 - Description

• SE, GE, IEA

• Log / Archive

• All handled updates - Events and Dates - should be reflected in the CT2 System Log
• Messages recognized as valid should be archived in separate folder on FTP
• Messages recognized as not valid (wrong data shipment number or unknown status) should be stored to specific folder on FTP

[edit] SOW 2: ...

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

[edit] Core Requirements

• ...
• ...

[edit] Solution

TBD