CONTAX Logo

Moving to S/4HANA? Your EDI Is Moving Too

November 18, 2026  |  by Jodi Abrams

If your company is moving to S/4HANA, your EDI is moving with it. Every trading partner connection, every map, and every IDoc flow has to work on the new system before you go live.

That can be a lot of work - especially if you change some processes at the same time. It tends to land on the same few people who are already stretched thin running the rest of the project or supporting EDI today.

We Do All the Work

If you are moving to S/4HANA and you choose Arcus for your EDI, our team does the whole move from start to finish:

  • Maps - We build the maps for each of your trading partners against your new S/4HANA setup.
  • SAP connectivity - We set up the connection to the new system and make sure IDocs flow in both directions.
  • Testing - We test every transaction and work with your business and project team through their test cycles, so the EDI is tested alongside everything else. We also coordinate testing with your trading partners so you are not chasing them for test files.
  • Cutover - We help with the switch and monitor the first transactions after go-live.

All we need from your team is input on what is changing in your S/4HANA design, and sign-off when testing looks right.

The Work Is Coming Anyway, So We Fit Your Timeline

With an S/4HANA project, the system changes, the connections get rebuilt, partner profiles get redone, and many partners want fresh test files before they will accept production from a new system. None of that is optional.

So we do not run a separate project next to yours. We plug into your test cycles and your go-live date. If the project dates move, we move with them.

And there is no charge for any of it. Maps, setup, and testing are all part of the Arcus implementation. You pay nothing until you are live, and after that you pay per transaction.

Your Processes Are Probably Changing, So Your Maps Are Too

Very few S/4HANA projects are a straight copy of what you had. You may be cleaning up pricing, changing how you pack and ship, retiring custom code, or adding plants. Every one of those changes impacts what your EDI sends and receives.

Here is a small example. The ship-to on your ASN used to come from a custom field. The new design retires that field, so the map has to read from somewhere else. That change has to be made on every map that sends an ASN, and then tested end-to-end.

Here is a second one. Pricing is being cleaned up in the new design, so freight and discount charges that used to come from one condition type now come from another. The invoice map has to be reviewed for every partner that receives an 810, and each one has to be tested again.

A Good Time to Re-Evaluate Your EDI Provider

If your EDI setup was built for your old system, someone has to touch every map to get it onto S/4HANA. You are already paying for that work, whether it shows up as a project fee, internal hours, or both. It is a fair time to ask whether you are getting what you need.

Questions worth asking any provider, including us:

  • Is the S/4HANA conversion included? - Or is it a separate project with its own price? Get it in writing.
  • Who owns it when an IDoc fails inside SAP? - A provider that stops at the edge of the EDI platform leaves your SAP team with the hard part.
  • Who talks to your trading partners? - Partner testing during a cutover is a lot of emails and calendar juggling.
  • What do the tenth and fiftieth partners cost? - Cheap to start and expensive to grow is common.
  • Who owns the map documentation? - Is it yours or available to you, or does it live in someone's head?

Switching is not always the right answer. If your current provider is solid and the conversion is fairly priced, staying put can be the best choice. Just make that decision on purpose, not by default because the project is busy.

Your S/4HANA Move Is a Decision Point

Your S/4HANA project is going to touch your EDI one way or another. Every map gets reviewed, every connection gets rebuilt, and every partner gets tested again. That makes this a natural time to decide who you want running your EDI going forward, instead of letting the project decide for you by default.

Done right, nobody notices EDI on go-live day.

If you are planning a move to S/4HANA and want to talk through what your EDI will need, please reach out at info@contax.com.

About the Author

Jodi Abrams

Jodi is an expert in SAP and eCommerce integration, and is Vice President of Applications for CONTAX.

Talk to Our Team

Questions about SAP, EDI or Acumatica? We're glad to help.