SI EDI

From UG

Revision as of 05:49, 2 August 2013 (edit) Alex (Talk | contribs) (→Admin) ← Older edit		Revision as of 05:56, 2 August 2013 (edit) (undo) Alex (Talk | contribs) (→Technical Requirements from data2solutions) Newer edit →
Line 72:		Line 72:
	w. Accessorial costs		w. Accessorial costs
	</pre>		</pre>
		+
		+	* Misc:
		+
		+	ISA Qualifier: *ZZ*
		+	ISA Receiver ID: ELARUS
		+	GS Receiver ID: ELARUS
	== Systems Analysis and Solution ==		== Systems Analysis and Solution ==

---

Revision as of 05:56, 2 August 2013

Contents 1 Info 2 Business Need 3 Phases 3.1 Phase 0 3.2 Later phases 4 See Also 5 Technical Requirements from data2solutions 6 Systems Analysis and Solution 6.1 Scalability 6.2 Data exchange 6.3 Admin 6.4 Reports 6.5 Logs 6.6 Inv Tab

Info

parent: 0004242

Business Need

Immediate business need is to respond to Arden's request to start sending most invoices through EDI.

This would cover:

• all MOTs and
• all Jaguar offices

Exceptions:

• EDI for all invoices except the ones for Maintenance, Web Portal and Administration fees.

Arden has a new partner company to support this: data2logistics.

Arden discontinued similar EDI with previous EDI partner Trendset permanently about 1 month ago.

Phases

Phase 0

Send one test EDI file to data2logistics.

Later phases

Arden agreed to staged approach. We can first convert invoices just for one MOT and or Jag office. And later turn on others.

See Also

• Protocol 210 - pdf attached to parent mantis
  • This Draft Standard for Trial Use contains the format and establishes the data contents of the Motor Carrier Freight Details and Invoice Transaction Set (210) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide detail information for charges for services rendered by a motor carrier. It is used both as a motor carrier invoice to request payment or as details pertaining to motor freight shipment(s) charges.

• EDI with Trendset and
• UG:Trendset USER GUIDE
  • spec and user guide for similar project (EDI with Arden for Sales Invoices through Trendset)

Technical Requirements from data2solutions

data2solutions that will accept all EDI messages for Arden communicated these requirements:

• post files on their ftp site (credentials TBD)
• use Protocol 210 - see #See Also sec
• Items Required list - see below

a. Ultimate Consignee must be captured for International Shipments
b. Invoice Number
c. Bill of Lading number
d. LOAD NUMBER (required for inbound only)
e. Shipper Acct # (only required for small package carriers)
f. Shipper info including address (city, state, zip and county code)
g. Consignee Info including address (city, state, zip and county code)
h. Port of Entry (only required air / ocean int. shipments)
i. Port of Departure (only required air / ocean int. shipments)
j. Delivery Date
k. Ship Date
l. Invoice Date
m. Total # of pieces
n. Total Weight
o. Billed Weight
p. Mileage
q. Movement Type (Mode and any expedited options)
r. Container Size (20, 40, 40HC, LCL) (only required air / ocean int. shipments)
s. Terms / Incoterms
t. Carrier Name
u. Pro#
v. Freight Cost
w. Accessorial costs

• Misc:

ISA Qualifier: *ZZ*
ISA Receiver ID: ELARUS
GS Receiver ID: ELARUS

Systems Analysis and Solution

Scalability

Since many Jaguar client companies would start/stop sending invoices through various EDI providers it would be nice to create generic solution to accommodate that.

Data exchange

• send invoices automatically (no need for operator to push or review)

• see #Technical Requirements from data2solutions

Admin

Option is to create Admin similar to Trendset Admin.

Details TBD.

Reports

None requested.

Logs

TBD

Inv Tab

If possible add sent/received/failed status.