Infor SyteLine EDI Expertise Immediately Available

EDI Headaches? DCS Can Help!

DCS EDI consultants have in-depth experience working with Infor10 ERP Business™ formerly SyteLine. We can help you add fields, documents, or customers working with your existing EDI system such as:

  • Gentran:Server™ for Microsoft Windows Server™
  • Global eXchange Services’ (formerly Inovis) TrustedLink™ or BizManager™
  • Extol’s EDI Integrator™
  • Seeberger’s Business IntegrationServer™
  • Microsoft’s BizTalk™
  • and other EDI systems.

DCS EDI consultants also have experience working with your key customers’ requirements. Our experience significantly lowers the cost of improving EDI processes.

Overview

EDI too often is an afterthought during the SyteLine implementation or comes up suddenly as an “on demand” project requested by a key customer that needs to be completed yesterday. In both scenarios you are forced to piece together a workable solution. This is something that you must do well and ensure that best business practices are followed, since EDI is highly visible and future development is built on this foundation.

Integration with SyteLine is a significant task. SyteLine’s structure can be complex and difficult to tackle. For example user exits or scripts are frequently used when mapping to/from the SyteLine intermediate, flat files.

The SyteLine flat file interface definitions are straight forward, but not trivial. The Purchase Order definition contains the most records (9 definitions, 13 records (some are the same). The Invoice and Shipment Notice each have two records. Flat file definitions can typically be defined in less than a week’s time.

However, the standard flat files are limited to specific fields. Several of the records have “Undefined” fields, which can be customized to be populated with needed data. An example is a Shipment Notice (ASN, 856, or DESADV) with a multiple HL structure for RFID and pallet-specific packing. Another example is a “cross-docked” Purchase Order with SDQ loops from mass merchants. DCS sets the main detail record (record 300) to repeat in order to match the quantity and ship to information from the SDQ field.

Here are the necessary deliverables you must provide:

Planning

  • Identify key resources and opportunities in your SyteLine environment.
  • Develop the project plan with all of its appropriate components (including training).
  • Set-up your development and test EDI systems.

EDI Development

  • Create a comprehensive map for each key Transaction Set, e.g. INbound Purchase Order (850).
  • Customize the comprehensive map for each Trading Partner.
  • Set-up and test communications between the translator and SyteLine.
  • Set-up data transmission testing: setting AS2 or FTP over your VPN to your Trading Partner’s test mailbox. This is done while working closely with  the firewall manager.
  • Archive off the old EDI system and data.

SyteLine Development

  • Set-up the SyteLine tables required to receive/send files (Port setup, Partner Cross-References, Partner Profiles, etc.).
  • Identify the documents used and the flat file layouts of those documents to/from SyteLine.
  • Work with your ERP programmer to help define any custom SyteLine requirements and set up any customized flat file capability.

Implementation

  • Install and test the finished maps and setup.
  • Train users (Customer Service, Accounts Receivable, and more).
  • Train I.T.(daily operations and mapping).
  • Have help available for support if needed.

Let DCS EDI specialists help build your EDI foundation or add more process automation. Since SyteLine mapping is not trivial, we recommend DCS GROW™ development service. Your EDI mapping will be thorough, quick, and economical due to our many years of SyteLine EDI experience in your industry. Having DCS develop the first few Trading Partners and communication parameters lowers the cost of implementation and hastens payback.

Here are the reasons a consultant can help:

  • Most of the U.S. companies conducting X12, EDIFACT, or GS1 EDI requirements’ are well known to us.
  • We have experience with cross-industry EDI transaction sets, not only Inbound PO’s.(850), Outbound ASN’s (856), Outbound Invoices (810), but also 3PL (94x series) transactions and Transportation (21x series) transactions.
  • DCS uses the add-ons for SyteLine created by the EDI systems providers that can save cost.
  • Communications set-up is a specialty of DCS. Connections using EDI INTAS2 (HTTPS in batch mode) reduce cost by elimination of pricey VANs.
  • Documentation and Training are a must when implementing any EDI program.

Another savings opportunity that is often overlooked is setting AS2 or FTPS to your Trading Partner. This is done while working closely with your firewall manager and can eliminate pricey VAN fees.

Conclusion

Successful change requires that all business processes are NOT interrupted. Chances are deadlines are impending and progress is slow. To maintain the peak efficiency consider outside assistance from veterans.  Using a seasoned expert who knows EDI and SyteLine will save you time and headaches. With experienced professionals, you can avoid common pitfalls when implementing EDI.

Finally, DCS EDI consultants have helped many companies implement and/or maintain EDI in their SyteLine system. Using a seasoned expert who knows EDI and SyteLine’s will save you time and headaches. With experienced professionals, you can avoid common pitfalls when implementing EDI with your SyteLine application. Your first step is easy, contact DCS for your free assessment.