Make EDI Regression Testing a Priority for QAD EE Upgrades

Posted on: September 12, 2017 | By: Tim Lovely | QAD Business Process, QAD Distribution, QAD Financials, QAD Practice News, QAD Manufacturing

At Logan Consulting, we view the Validation and Testing phase of our methodology to be a critical component of a successful upgrade. In the QAD space, upgrades from QAD Standard Edition to QAD Enterprise Edition often include bringing forward existing EDI customer trading partners and their associated EDI transaction sets.

Our clients often have a successful track record of using EDI in SE and the project team can be tempted to put the regression testing of these transactions lower on the priority list if there are no planned changes to the EDI maps or transactions. Conversion of EDI Ecommerce maps and Trading Partner data can seem straight forward as part of the upgrade to EE.

However, upgrades to QAD EE often include changes to master data, including customer and ship-to numbering, which will cause required translations to occur in Trading Partner data. Opportunities for error exist throughout the conversion and upgrade path, including the following:

  • Master Data Changes such as Customer and/or Ship-to Numbering

  • Conversion of Trading Partner Mapping

  • EDI Ecommerce Map Translations

  • Third Party Communication Software Changes

A thorough regression testing cycle of all key Trading Partner transactions in a copy of a Production ready QAD EE environment is always recommended to ensure a smooth cutover to the latest version of QAD EE.