Migration Guide: PI/PO B2B Mappings to Integration Suite using Figaf

A guide for migrating PI/PO B2B mappings to Integration Suite is provided. The guide includes steps to set up an environment, prepare company, partner profiles, MIGs, and MAGs, and perform migration using Figaf tool. The guide is recorded on a preview of Figaf 2508 and follows naming conventions for handling larger perspectives. The migration process is time-consuming and can be performed manually, but using Figaf tool is recommended.

Migrating Business-to-Business (B2B) mappings from PI to the Integration Suite is a complex yet essential task for ensuring seamless operations in a modern business environment. This guide provides a detailed, step-by-step approach to facilitate the migration process using the Figaf tool. The process involves setting up an environment, preparing company and partner profiles, creating MIGs and MAGs, and performing the actual migration. The guide is based on the latest version of Figaf (2508) and adheres to specific naming conventions to handle larger perspectives effectively.

Setting Up the Environment

Before initiating the migration, it is crucial to set up an environment that supports the EDI setup. This involves installing and configuring the Figaf tool in your own environment. The Figaf tool simplifies the migration process, though manual execution is possible, albeit more time-consuming.

Preparing the Company and Partner Profiles

1. Create Company: Establish your company and any subsidiaries you will be using. Follow the Figaf guide to create partner profiles, ensuring you add identifiers and systems as required.
2. Prepare Partner Profiles: Use the Figaf fast-track feature to quickly prepare all partner profiles with corresponding systems and identifiers. This step is essential for your PI B2B migrations.

Creating MIGs and MAGs

1. Define MIGs and MAGs: As part of the preparation for your PI B2B migration, define all MIGs (Message Implementation Guides) and ideally MAGs (Message Agreement Guides). While MAGs are not mandatory for the migration process, they are advisable for better alignment of agreement templates.

Preparing Integration Suite TPM Agreement Templates

Follow the naming conventions specified in the guide to prepare the mandatory B2B Agreement Templates for your full B2B scope of message formats (typeSystems).

Performing the Migration

1. Migrate PI/PO Operation Mapping: Use the Figaf tool to perform the migration of PI/PO operation mappings to the Integration Suite TPM. This step ensures that your B2B scenarios are easier to manage and monitor in the Figaf "B2B" menu.

Conclusion

Migrating PI/PO B2B mappings to the Integration Suite is a demanding task but achievable with the right tools and preparation. The Figaf tool simplifies the process, making it more efficient and less prone to errors. By following the steps outlined in this guide, financial professionals can ensure a smooth transition to an operational B2B scenario in the Integration Suite.

References
[1] https://community.sap.com/t5/technology-blog-posts-by-members/guide-for-migrating-pi-po-b2b-mappings-to-integration-suite-b2b-tpm/ba-p/14186491
[2] https://www.ainvest.com/news/ss-black-diamond-morningstar-alliance-redefining-wealth-management-platform-migration-2508/