Embarking on a migration journey is no small feat, especially when navigating the intricate terrains of platforms like SAP PI/PO. At the core of our philosophy is a simple premise: Migration should not be about redesigning everything but only the parts that really make a difference.

We already have a good step on normal A2A migrations with multiple receivers and message mapping using Function Libraries and parameters. Or custom mapping of Channels to your specific setup. See the migration tool for A2A here; we have solved a few more of the problems since March. And then, you can see the automated testing here, which also has received a update.

When you are migrating, you should consider if you want to use Integration Content Adviser (MAGs) to handle your mappings or if you want to go raw. To use SAP PI/PO message mappings as the basis of your solution. I think the message mappings make a lot of easier and then for few scenarios that you change more frequently or make new updates to, you can create new MAG to support those case.

SAP Integration Suite has a good B2B solution once you get to start using it. I think a good guide on getting started with TPM for the Integration suite can be found here.

B2B Migrations: The Road Ahead

As we zero in on B2B migrations, specifically the EDIFACT/X12 scenarios, there are a few items that we will be working on for the next months to make sure we create a simple migration for these scenarios.

1. Refined Operation Mappings Migration: Our vision is clear – migrate with an emphasis on enhancement. As we transition from selected ICOs, we adhere to the MIG structure, ensuring that EDI documents find their best fit without unnecessary complications. The mappings will be included in iFlows with Process Direct and can easily be called from the TPM. There is some difference in the structures, but it can be fixed.

2. Test Case Creation: A hallmark of our migration edition, this tool ensures that documents are tested to ensure you have migrated everything and the partner setup is created. They will take your IDOC and EDI messages from SAP PI/PO and migrate them to run in the integration Suite. We can already migrate the case, but there are places where we can improve the setup. You can compare EDI messages and ignore the segments/fields that need to be ignored.

3. Partners & Agreements: For now, this segment is in the hands of users, laying the foundation for impeccable connectivity. Here, you can easily configure where messages should be sent based on the partners’ identities. The current version does solve the need.

We will start with versioning of the TPM objects to track what is being changed. There could be a lot of exciting steps going forward with this, like validation, comparisons and transport.

For now it is possible to manually perform these tasks but in our next release(s) we will be adding more of the functionality to enable better coverage of this. It will require a few interactions to ensure we got everything covered.

SAPs Migration Tool

SAP has made some improvements to the tool that allows you to import Message Mappings with Function Libraries as separate objects. This will also enable you to be able to use the standard functionality for migration. And I imagine there will also be profiles to support these migration cases in the future, it is some fairly simple iflows that need to be created to support this.

And you could use Figaf to test your migration result with this setup.

Want more

Want a closer look at what’s brewing? Stay connected by signing up for our, which will be the basis for this Figaf migration edition  or by following me on LinkedIn

I will be sharing some more on this journey.

 Is there anything that you are missing in this? Please share.