EDI to Schenker

From UG

Revision as of 14:32, 17 December 2014 (edit) Andrei (Talk | contribs) (→Info) ← Older edit		Revision as of 14:47, 17 December 2014 (edit) (undo) Andrei (Talk | contribs) Newer edit →
Line 17:		Line 17:
	==== Core Requirements ====		==== Core Requirements ====
-	* FTP credentials	+	* FTP connectivity
-	:* test:	+	:* Schenker EDI policy is:
-	::* address: dev.jaguarfreight.com	+	::* to push outbound documents to our client’s servers
-	::* login: schenker_dev	+	::* expect clients to push files to Schenker's server.
-	::* password: *********	+	:* FTP credentials
-	:* production:	+	::* test:
-	::* address: ct.jaguarfreight.com	+	:::* address: dev.jaguarfreight.com
-	::* login: schenker	+	:::* login: schenker_dev
-	::* password: *********	+	:::* password: *********
-	* List of Milestone Events for Air and Ocean	+	::* production:
		+	:::* address: ct.jaguarfreight.com
		+	:::* login: schenker
		+	:::* password: *********
		+	* List of Milestone Events for Air and Ocean (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		* ISA and GS IDs for test and production
		+	:* test:
		+	:* ''ISA*00*          *00*          *02*JAFR          *ZZ*SAMPLE        *140514*1631*U*00401*000000001*0*T*>~''
		+	:* ''GS*IM*JAFR*SAMPLE*20140514*163038*118039*X*004010~''
		+	:*production:
		+	:* ''ISA*00*          *00*          *02*JAFR          *ZZ*SAMPLE        *140514*1631*U*00401*000000001*0*P*>~''
		+	:* ''GS*IM*JAFR*SAMPLE*20140514*163038*118039*X*004010~''
	==== Solution ====		==== Solution ====

---

Revision as of 14:47, 17 December 2014

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

• This article covers Electronic Data Interchange (EDI) between CT2 and Schenker.
• It was 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
• expect clients to push files to Schenker's server.

SOWs

SOW 1 EDI to Schenker

---

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

Core Requirements

• FTP connectivity

• 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 (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*SAMPLE *140514*1631*U*00401*000000001*0*T*>~
• GS*IM*JAFR*SAMPLE*20140514*163038*118039*X*004010~
• production:
• ISA*00* *00* *02*JAFR *ZZ*SAMPLE *140514*1631*U*00401*000000001*0*P*>~
• GS*IM*JAFR*SAMPLE*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

---