In this release we open up most of the B2B functions through the Figaf public API. The functions you use every day in the Figaf Tool to build and maintain SAP Integration Suite TPM content can now be called by scripts, pipelines and AI agents. We have also added wildcard support to the migration, and made a number of smaller improvements.
- Most of the B2B functions are now available in the public API
- Wildcard support in the migration
- More of our calls to SAP now go through SAP’s public APIs, where that is possible, to follow SAP’s API policies
- A public API to search for tracked objects in Integration Suite, which makes it much easier to build apps
- Many usability improvements
Wildcard support in migration
Most users need wildcard migration, so we have added it to the migration. It does add some complexity around how the communication channels are created when more of them are selected.
B2B through the public API
The public API now covers agreement templates, MIGs, MAGs, partners, subsidiaries, the PI to Integration Suite migration and test case creation.
Why it matters. B2B onboarding involves many small steps that are done the same way every time. When those steps run through an API, they can be automated, repeated and checked, and nobody has to click through them one by one. Each endpoint follows the same rules as the UI, so the result is the same either way.
B2B content
- Agreement templates. Create agreement templates with their B2B scenarios, add scenarios to an existing template, and read the scenarios of any template.
- MIGs and MAGs. Read them, create them and create new versions of them.
- Custom IDoc messages. Look them up, or create them directly from an XSD.
- Partners and subsidiaries. Create and update trading partner profiles and company or subsidiary profiles. These are the same functions as in the Figaf Tool UI.
- Search tracked objects. Search the tracked objects of an agent, so an automation can find what is already there before it creates anything.
PI to Integration Suite B2B migration
The Check and Migrate steps of the B2B migration are now available in the public API. You can see which operation mappings are already migrated, and look up candidate agreement templates, partners and CPI systems. You can run a Check, which writes nothing to CPI and returns typed logs, and then migrate. The migration result shows whether deployment and activation succeeded, and if they failed, it gives SAP’s message.
Parallel migrations are now locked per iFlow and per agreement, not per CPI system. Starting a second B2B migration on the same tenant no longer fails with an internal error, in the UI too.
Mass creation of B2B test cases from payload archives
Upload a zip of archived payloads through the API to create B2B test cases in bulk. The API returns the same validation result as the UI, so you can see which message groups match the chosen scenario, which match another scenario, and which match none. You can then upload all of them, or only the matching ones.
More B2B improvements
Test case migration takes the ICO order settings along. When you migrate PI test cases to a B2B scenario, the order settings of the ICO are now copied too. If the ICOs of one operation mapping need different settings, the Figaf Tool creates a separate shared configuration for each ICO, so no test case breaks another. The B2B migration also copies the tags of the operation mapping to the B2B scenario.
Faster subsidiary setup. In Create Subsidiary, you can now paste an SAP Integration Suite service key, and the client ID and secret are filled in for you. The User Account column now sits right next to Client Secret.
Smaller B2B improvements and fixes
- An agreement created with a custom integration flow can now be activated. Before, SAP rejected it with “Mapping is required”.
- Configuration rules for collection item identification that contain a ; followed by a line break are now parsed correctly.
Coming later
Some features are built but did not make it into this release. They may come in a later patch.
- Pipeline setups on Edge landscapes. This will let you migrate to Edge Integration Cell and create all the relevant artifacts there, synchronize content, and transport between systems (this needs Partner Directories).
- Other AI providers than OpenAI, such as SAP AI Core.
Get it now
Try Figaf for free, or book a meeting if you want to see how the B2B API can automate your migration.
