Automate Reuse to Maximize Migration and Onboarding Cost Savings

This blog post is the final part of a series highlighting the three keys to rapid EDI modernization for JD Edwards users.

Because standard EDI integrations provide predictable patterns, reuse is especially effective in reducing EDI migration costs. While true that some reuse actions require manual development due to individual trading partner requirements, for example, automation still plays a big role in cost savings. In fact, automation can account for the highest project cost and time savings.

Custom mapping to meet the needs of each trading partner typically requires manual intervention and takes time. But configuring acknowledgements, creating new projects from templates, configuring routing, etc. are not only well-suited for automation from a cost-savings perspective but also eliminate many forms of manual errors that can lengthen testing time and contribute to runtime exceptions as well.

Trading partner migration and subsequent onboarding of new trading partners can also largely benefit from how automated, project-level reuse works. In the demonstrated figure below of EXTOL’s Project Generator, four main processes are happening:

  • Project templates are acquired or created for each trading partner transaction profile. For each EDI transaction in a specific profile, the templates organize business processes, maps, adapters and other objects. In migration, off-the-shelf project templates can be offered as a means to help eliminate all of part of this step. For new partner onboarding, project templates created for the migration process can be reused.
  • Supply sample EDI data or a trading partner profile table that contains partner names, EDI identifiers and optional EDI attributes. Generation and automated configuration will be guided through these inputs. In some migration projects, the classic EDI source system can have the trading partner profile data automatically extracted.
  • Use Project Generator to generate and configure projects for each trading partner. The Project Generator uses the project timeline to create and configure EDI projects for each trading partner.
  • Customize, test, and deploy new EDI projects, according to each trading partner’s requirements.

Some of the projects you use as templates may include single transactions or complete transaction sets. You’re also able to generate projects for non-standard B2B integration, cloud integration, data integration and proprietary business processes.

In regards to the Project Generator, it is able to automate a large majority of reuse tasks which include:

  • Creating new projects and project objects based on any provided template
  • Renaming partner-specific objects
  • Setting partner-dependent parameters on Business Processes and Adapters
  • Configuring EDI Acknowledgments
  • Configuring inbound and outbound EDI Routes
  • Archiving generated projects

For more information about EDI modernization for JD Edwards, download our “Three Keys to Rapid EDI Modernization for JD Edwards” whitepaper. wp-download

Leave a Reply

Your email address will not be published. Required fields are marked *