← All features

Development and transport

SAP Discovery content management

Nobody can say for sure that SAP's standard Discovery content is up to date and the same on every tenant.

SAP Discovery content is the standard integration content SAP provides for SAP Integration Suite. Keeping it up to date and aligned across tenants has been a manual and subjective task: have all updates been applied to all tenants, and do all packages even exist on all of them? Figaf DevOps Suite lets the person responsible for Discovery content transport it through the landscape with the same process as the rest of your integrations.

How it works

• See where content exists. Figaf shows which Discovery packages exist on which tenant, for example that a standard package only exists in development, where a couple of its iFlows are already deployed.
• Transport a Discovery package. You add the SAP Discovery package to a Figaf ticket and transport it. You can also transport a newly created one. In the target tenant, the package is copied into your own design area the way SAP standard does it.
• Version check. Installing Discovery content in a target system always gives the latest version available from SAP. Figaf verifies that this matches the version installed and deployed, and a mismatch is caught at once, matching the design notification in SAP Integration Suite.
• Update with one click. After the content has been updated, you update the Figaf ticket with a single click, and the content is ready to be transported to the target system.
• Test before you import. Because the content is on a normal ticket, you can run your regression test cases from the Figaf Testing Tool before you import the transport.
• Standard result. After import, the package in the target tenant is still config-only, identical to a manual copy of Discovery content, and it is still eligible for updates from SAP. The content is then present in the target system, pending deployment.

Business value

• Less manual work. Aligning standard content across tenants no longer depends on someone copying packages by hand and checking each tenant.
• Consistent landscapes. Version checks show at once when tenants are out of step, which lowers the risk of differences between test and production.
• Documented adoption of SAP standard. Each transport validates and documents how Discovery content was implemented, which gives you a record for audit and change management.
• Same governance as your own content. Discovery content goes through the same tickets, testing and transport process, so it is not a blind spot in your release process.
• Still SAP standard. The result is identical to a manual copy, so you keep SAP’s update path for the content.

Good to know

Available since release 2606 in Figaf DevOps Suite. Related features: change and transport and regression testing.

Learn more

• Figaf DevOps Suite: transport