Migration from SAP PI/PO to Integration Suite is something most SAP PI/PO Customers are considering. How do you make an effective migration process? Tools can speed up the migration process.
I often get the question: “So Daniel, what works and what does not work with your migration Tool.” In this post I’ll try to highlight some of the things that can cause problems and you need to check.
Besides migrating your integrations, the tool also speeds up the rest of the migration by providing a testing service and giving you an overview of your migration. It is recommended to start with the free Figaf Migration Edition, which gives you 10 free migrations and a 2-month trial of Figaf DevOps Suite. Then you can try the migration tool and experience how it speeds up your process.
As of February 2024
What works
- Flow
- Flow is generated based on Receiver and Interface split. Each interface with mapping flow will get its own local process to work with. Conditions are handled.
- JMS retry can be added automatically to handle processes
- Messages are only sent to JMS if it fails in the sending part. This can be adjusted in the error handling script.
- You can update and add the custom error handling
- EDI related messages using the TPM/MIG framework
- Message Mappings
- Message Mappings are migrated and linked to WSDLs, XSD or IDOCs
- Mapping with internal UDFs is migrated
- Function Libraries are converted to groovy scripts or use SAPs Function Library objects
- RFC functions are migrated as empty Groovy scripts, easy to fill in the code
- Constant parameters are mapped into the iFlow depending on where defined
- Support for multi mappings and split of the payloads after processing
- It is possible to map using the B2B Mapping Kit with some additions
- Other mappings
- XSLTs are mapped, though PI Java functions are not validated
- Java mappings are migrated with a Groovy script that calls your Java mapping (since release 2410)
- Channels migration
- It is possible to create your own mapping between SAP PI/PO channels and Cloud Integration.
- You can add your own mappings or use some of the templates.
- Modules can be mapped to Script collections
- XML to CSV/CSV to XML migration is automated
- Migration target Cloud Integration
- Neo
- CF
- Integration Suite
What is manual or not supported for now
- Flows do not support Operations and Receiver Rules object
- Retry does not support datastore or shared JMS, but it is simple to implement.
- Message mappings with local functions using imported archives. There seems to be some compile issues
- Function Libraries
- Convert container to use MappingContext instead of Container from PI which is two different functions.
- Dynamic Attributes handling in mappings
- Advanced functions with full queue are not supported
- Imported archives using SAP PI specific libraries
- ABAP Mappings/XSL are not supported
- Channels should be supported by Cloud Integration and accept the same payload. If it differs the interface should be changed and testing cannot be used. You can map IDOC/Proxy sender to ProcessDirect and then have a separate flow to handle the processing and distribution.
- We need to use the adapters from SAP or partners; we don’t provide our own adapters.
Note: There are for sure more scenarios that we do not support today and we don’t have any knowledge about.
If you have any questions, contact us and we will get back to you. I would always recommend that you try the 10 migrations you can get from the tool to see if the tool speeds up your migration. And you can always have a mixed approach with Figaf, SAP and manual redevelopment.
