We have another release of the Figaf tool enabling you to streamline how you work with SAP Integration Suite. Including the migration from SAP PI/PO to Cloud Integration, Partner Directory Alternative ID, and testing.
There are a large range of usability improvements and bug fixes across the application. Most of this will only be applicable.
Note License change for documentation
We have previous not been licensing our documentation as a separate item. That is changing with this release. If you don’t have the documentation license you may not be able to create some of the documentation you want.
We do this because we see the documentation the tool has a huge value, for the people that value it.
In the trial period you will still be able to generate the documentation. And our SAP PI landscape report can still be generated. After this you will just see the first part of the list.
If you purchased Documentation as a part of our agreement email support and we will assign it.
SAP PI to Cloud Integration migration
There are a lot of details when performing a migration that can make or break what to use an automated migration. In this release we have added more of these edge cases.
Split Function Library to Groovy and SAP FL Object
For the first migrations we worked on we added an option to convert the FL object in to a Groovy script because it was the only option for some scenarios. Now you have the FL object which does give some advantages in some scenarios like using the container object or All values of a queue. Something that is not supported in Groovy.
Therefore, we have seen customers exploring combining the two for ideal migrations. So now you can combine them.
For the Function Lib you select you want to mix it.
Then you can choose how it should be migrated and you can mix multiply different UDF with the function.
When migrate remember to use Overwrite shared artifact of the Message Mapping so it will be updated with new mapping.
B2B Migration profile extended with conversion between PI and MIG profile
Our goal is to make it as easy as possible to migrate, so you can reuse the message mappings you already have but leverage the TPM in Integration Suite to handle it. We had a customer project where we did see that this worked suite well for the cases where you did not want to rebuild the mappings.
Reusing the message mapping does come with some limits but being able to explore what is possible is the first part. If it is possible it will speedup your migration a lot.
We have now added an automatic groovy script that supports conversion of EDIFACT, X12 and Tradacom. The biggest challenge is the different schemas and upholding the standards.
There may be a few exceptions because the schemas are different, probably because the difference is used versions.
And of cause you should be testing this just like if you performed migration to ICA. Here Figaf can help with the testing.
This is waiting for update of the Figaf connector in Business Accelerator Hub.
Support of message parameters
It is now possible to add the list of parameters of a message mapping. We have therefore converted our old approach about setting it as properties to this setup and discarded the script we created. You can thereby use the simulate functions for this.
There is of course limits to what is possible like you cannot modify the list of parameters in the mapping.
Pipeline Queues support
If you are using Pipeline 1.0.9 there is now new set of queues that is used. You can therefore select which queue you want to use for the inbound flow.
Test message recording with BI and Module archive
One customer had a case that could not trigger an IDOC, but only via the test tool. It would therefore require a mixture of BI stage and Adapter module.
Event Mesh improvements in Integration Suite
After last months release of Event Mesh we found that there was a few areas that we could improve in. We have added those improvements in the release making it easier to work with Event Mesh.
The browser has now been improved. We did find some issues if you where looking a huge queues or payloads then you may not be able to get all messages in a regular time. The browser does not consume or change the order of the messages.
Moreover, you can then see the content and payload.
We have also improved the stability of the testing, making it easier to create test cases in it.
There is a fairly low thru put of the Event Mesh to you may not see all the first 200 messages. Also we would consider that even this consuming of the message will count towards your used messages.
Alternative Partners
For customers using the partner directory the Alternative Partners. This allows you to use different keys to perform lookup for a PID.
You can now use Figaf to keep track of all the Alternative Partners. We will release a patch where you will be able to create and edit them in Figaf.
We do miss the transport part of this but it is a bit more complicated how such a transport is going to work. We are looking for user input on that part.
Create credentials
If you are working on a transport and Figaf find that you are missing a credential. You now have an option to create this as a part of the transport process. You get a warning on the configuration side. If you click it you can then add the credential.
Once you have added the credential it will be added to the Integration Suite.
Then you can create the Credential or Oauth2 on the target tenant.
API Hub version working again
We have for a long time had the ability to see what is being changed in Business Accelerator Hub (api.sap.com). But it has been broken. Now it is working again so you can see the impact of the changes SAP have added to the APIs you are using.
Where to start?
If you have already started your trial then upgrade either through our download page or our docker image page.
If you haven’t started yet, then encourage you to start a trial and explore the tool.