Last release of the year. It is probably not the biggest firework of new improvements and many features. But a necessary release that makes it possible to simplify your usage of SAP Integration.
If you have Edge Integration Cell activate we will recommend that you upgrade to this release as we found some challenge in the CPI Message Overview to ensure data is continues collected.
Notice if you are upgrading on BTP please also update the Security roles that have been changed. You can download the latest deployment or just the xs-security.json. You can update with “cf update-service figaf-xsuaa -c xs-security.json” or by go into the instances and update it with the JSON file above.
Pipeline Concept 1.0.8
We have improved our migration to support the latest pipeline concept. Now you can generate all the receivers and interfaces in just one XSLT, saving a lot of processing. When configuring the migration, you can select what you want to be using.
I strongly recommend you check out the Pipeline Concept for your migrations since it will simplify many scenarios, that would otherwise require extra effort.
New help document
We have reformatted the help page to a multipage layout. It makes it a little easier to manage and explore and find relevant content. We will probably in the new year remove the version number from it because we see customers have more updated systems. And it anyway should be a good idea to upgrade if there is some problems.
You can see the new content here.
File content conversion in migration
We have opted to support the standard content converter module from SAP. We think this will give you more options to migrate easier. There are some differences between the PI and the Groovy script but that is something that you can fix manually or ask to fix by the team.
It works for File Content Converter and the MessageTransformationBean that now gets this migration.
SAP Identity Service
So we learned that the SAML based authentication directly into a sub account, were will be depreciated. So in 2411 we added support for using SAP Passport. But it does require you have enabled the ability to logon with SAP user.
In this release you can create a user in SAP IAS and use it for login. This will make it easier to connect to systems and control access better. You need to have a user with email and password that can login with all the access of the Integration Suite system. The usage is quite easy but it does require some from you to know how to set it up and use it.
BTP User access
We have made a number of fixes around users provide by BTP and if they came from IAS then there could be some problems that we have resolved.
Edge Integration Cell support
We have added a few items to improve the monitoring of the CPI Message Overview. We did have some functionality in 2411 but it could lead to some corruption of the statistic this have been improved in this release. The overview also has the option to show displayed names for the companies that have difficulty interpreting technical names.
If you have Edge integration Cell please update to this.
Keep iFlow descriptions in the transport
When you save your iFlow you have a description of the iFlow. When we have been moving them to QA or production we have added comments to the Figaf Ticket and the external ticket. This would enable you to easy go from the CPI iFlow to Figaf and explore why it was changed.
Some users would add comments into the iFlows about what they have done of changes. You can now also get this description in the transport path.
On the landscape you now have the option to select which strategy to use for the transport. You can use the current, a mixture or only the text.
Notice that the space is limited, and you will only get the last information.
B2B migrations conversion between PI and ICA formats
For migration of B2B scenarios we have been exploring migration of exiting Operation and Message Mappings into a separate iFlow.
One of the challenges is there is a slight change of the XML structure for this. We have created a generic Groovy script that will allow you to transition between the structures. To simplify the journey
If you are working on X12 migration with tool reach out to Figaf support to get access and help test it.
Ideally, it should just be included in the migrated conversions and added automatically when you use the EDI profile.
Dual stack recording
If you have been running Figaf in BTP it has not been possible to access and record messages from your dual stack system. Here we used the RFC. We thought we could just use RFC via cloud connector. But that requires you to use the Java packages which we are not.
We therefore will use your Integration Suite system as a proxy to connect to the on-prem system RFC.
You need to create a RFC destination to the SAP PI ABAP system in the BTP, that can access the monitoring RFCs. Then select which Integration Suite can be used for it.