Apply Large-grained Reuse for Common Transaction Sets

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

Despite some lingering reservations around migration costs, EDI modernization, either driven by internal platform migration or external trading partner requirements, has become a strong consideration for JD Edwards users. The secret to success is all about selecting the right strategy.

While certainly true that reuse is one of the most significant cost saving strategies in migrating to a new EDI solution, not all reuse strategies yield similar results. The numbers show that deploying a large-grained approach to reuse can save significantly more than looking at smaller units.

Figure 1

Figure 1

As exhibited in Figure 1, the degree of time and cost reduction that is attainable varies. If you are working on a customer-wide integration, it is easier to accomplish with a large-scale integration because inbound and outbound processes only have slight differences for maps, adapters, business processes and other integrations. By reusing the integration level, more time is saved and cost associated with the EDI modernization is minimized.

Further along in the EDI partner implementations, transaction set levels can also benefit from large-grained reuse. Standard sequences are carried in the Order-to-Invoice, Load tender-to-Delivery and other EDI transactions, but they can be used to migrate or onboard multiple customers.

For JDE users, this large-grained reuse does not necessarily mean there is a reduced effort for integration, but it does make the process more seamless from time saved collecting and connecting objects that are typically used together in common integration scenarios.

Another way to evaluate the success of reuse is by looking at it from a 100-partner migration project viewpoint. Figure 2 provides more detail on applying reuse at different levels, using a common 3-document transaction set (e.g. Order Receipt/Ship Notice/Invoice).

Figure 2

Figure 2

In looking at the figure above, four main points are evident:

  • Not taking advantage of any reuse costs the user about 75 percent more time and effort than manual reuse at any object level.
  • Object-level or manual reuse will allow the user to save a significant amount of time, especially when compare with no reuse.
  • Manual integration/project-level reuse saves a decent amount of additional time through related integration object organization.
  • Automated project-level reuse actually saves the most amount of time – almost 60 percent – as it eliminates most manual customization and attendant customization errors.

Even though object-level reuse has been seen as the foundation of rapid onboarding and migration, as you can see from the 100-partner migration project, only one percent more time is saved when base maps are ready at the start of the project when compared to building the templates from scratch.

In contrast, about 77 percent of savings comes from using map templates in reuse. The effort needed to create them in the first place accounts for a small fraction of overall project time, which approaches zero percent as the number of partners needed to migrate grows.

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 *