SI EDI
From UG
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
Create and 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)
- Business agrees that it is not real time. But at least once a day. Lets make it configurable (next phase).
Admin
Option is to create Admin similar to Trendset Admin.
Details TBD:
- what options to keep in Properties File vs UI Admin
List of fields (review with KU):
Reports
None requested.
Logs
- who changed Admin
- TBD
Inv Tab
If possible add sent/received/failed status.
Email Notifications
TBD
Open Questions
- will we get 997 messages?
SOWs
SOW 1 Create test message
mantis: 4249
spec:
- see #Phase 0,
- do it for any MOT, any E0 associated with Arden, any Jag office, any content of invoice (at list to TOC items I suggest)
- do it through code or first manually (to verify understanding)
SOW 2 Create Architecture
mantis: 4251
spec:
SOW 3 Defining and editing all parameters
mantis:
spec:
SOW 4 Generating message in 210 format
mantis:
spec:
SOW 5 Sending message (by process)
mantis:
spec:
SOW 6 Receiving Status updates
mantis:
spec:
SOW 7 Invoice reporting
mantis:
spec:
SOW 8 Logging and
mantis:
spec:
SOW 9 Email Notifications
mantis:
spec:
SOW 10
mantis:
spec:
Contacts
- Jessie.Falls@ElizabethArden.com - Transportation Manager
- Dawn.Byrum@data2logistics.com - Global Solutions Analyst
- brandon.heaton@data2logistics.com - EDI Specialist
