EDI Considerations When Moving to SAP RISE

When planning a move to RISE with SAP, most of the focus is on system readiness; transports, security, connectivity, and testing. EDI is usually part of that scope, but it helps to look at a few small details that can make the migration smoother and reduce post-go-live cleanup.

These aren’t major redesign items, just configuration points and technical checks that tend to get overlooked during the transition.

1. Review your partner profiles and message types

Start with transaction WE20 and review each partner’s outbound and inbound settings. It’s a good opportunity to confirm that message types, ports, and processing routines are still correct for your new environment.

If you have older partners or message types that aren’t in use, this is a good time to deactivate them or remove unnecessary entries. A clean partner setup makes testing easier and reduces noise during go-live.

2. Check your IDoc versions

SAP RISE migrations can introduce small version changes. For example, an interface might start generating IDocs that have different segments than what you had before. Even though the difference may be minor, it can affect how the data is processed by your EDI translator and potentially impact mapping.

You have two choices here:

1. Use the most recent segment version of the IDoc and adjust any mappings accordingly. This is a good choice if you need to use the functionality available in the newer version.
2. Downgrade your IDoc version to the one you were using before the upgrade. This reduces the changes you need to make in your EDI mapping.

If you do not need any of the functionality available in the newer version, there is no reason not to downgrade. It greatly reduces the work required on the EDI side of the upgrade and will keep existing functionality intact.

You can control the version in WE20:

• Open the partner’s Outbound Parameters
• Select the message type and go into the details
• In the Outbound Options section, fill in the field “Seg. Release in IDoc type” with the value that corresponds to your old SAP release

3. Validate port configurations

In WE21, review your port definitions. Depending on how you connect externally, you may have:

• tRFC or HTTP ports that point to middleware or managed services
• File ports if you have on-prem EDI software

With HTTP for example, you’ll need to add a proxy host and service when migrating to RISE.

4. Recheck authorizations and certificates

If your system connects to external networks through SFTP, AS2, or APIs, make sure any required keys or certificates are available in the new environment. These are easy to overlook during system moves, and re-importing them early avoids delays in testing.

Review what is loaded in STRUST for any certificates required to connect to your EDI solution and ensure it has the latest.

The SAP authorizations for the user that connects to the system should not have changed, but your testing will uncover any issues should they exist.

5. Determine your testing strategy

A good approach is to test each map in the new system. This doesn’t have to include integration testing with the trading partner, as you can compare translated EDI and IDoc data from the old system with your new RISE system. With strong attention to detail, you can match up values and ensure that the data is consistent between environments.

A smooth transition

EDI migration to RISE doesn’t need to be complicated. With a quick review of profiles, versions, ports, and connections, most interfaces move over without major redesign. Addressing the small details early just helps ensure everything runs as reliably in the cloud as it did before—ideally, with a bit less clutter.