Figaf DevOps Suite for SAP
One tool to handle all of your SAP Integration processes
- Document every transport and developed object
- Link changes to the relevant business request
- Test and validate changes consistently in QA
- Manage configuration centrally without production access
- Connect incidents to the relevant integration changes
- Understand what changed, when and why
Release Faster and Better SAP Integrations with Figaf Dev Ops Suite
Suite size options below are based on the scope of your integration landscape.
We only enhance SAP standard. We never replace it.
Every customer running Figaf still has 100% SAP standard TPM underneath. You can use Figaf, scale it back, or remove it completely, at any point, without losing that standard functionality. You’re not locking yourself in. If a better solution comes along, whether that’s SAP’s own roadmap or something you build yourselves, walking away from Figaf stays simple
Small Landscape
Medium Landscape
Large Landscape
Enterprise Landscape
Price shown is per month, billed annually. Monthly billing available at 20% surcharge.
* Count based on integrations (iFlows, MAGs and B2B TPM Agreements)
Note on Integration Suite testing: Testing of iFlows in SAP Integration Suite is included in the Figaf DevOps Suite until April 15, 2027. From that date, Integration Suite testing is provided by a third party and requires a separate license. We will help you move your existing test cases to the new tool.
That kind of responsiveness made a real difference.
Discover Figaf DevOps Suite Features
Git integration
All development processes start with having a good place for handling your SAP CPI and API management development. You can use your favorite IDE to develop and run your Groovy scripts, it can save you a lot of development effort.
It will also give all developers an opportunity to develop using the same toolset without having to reinvent the wheel.
See how the Git functionality works.
Change tracking
The Figaf DevOps Tool is able to monitor all objects important for SAP Integration. It will enable you to find all the differences between versions. You will be able to see when and why something was changed. This allows you to monitor all changes.
Tickets
There should be a reason for all changes of your code. It is normally that business that makes a Service Request, creates a Jira or ServiceNow ticket.
The Figaf DevOps Tool allows you to log which objects are affected by a change and link it to the business requests. That way all changes should happen because of a requirement. On all objects in all versions, you will be able to find the business reason for the change.
Transport
Transport is about understanding what is being moved in your landscape. It is also to perform the correct approval, configuration and testing process. Figaf DevOps Tool will allow you to monitor what integrations are transported. Ensure that managers or architects know what is being transported before they approve a change. And of cause enable you to test how the change impact your integration.
Configuration
Each time you import new content into your landscape you need to make sure that it is configured correctly to point to the correct system. This is normally something users need to perform after imports in the landscape. Figaf DevOps Tool is a central repository where you can have all the required information you need. This will simplify the process and make it easier for users to perform the transports.
Documentation
Documentation is one of the processes that takes the most time. Figaf DevOps Tool can create the two types of documentation needed automatically.
- Is a list of the changes that occurs as a part of a ticket or business requirement, including test runs.
- Is a scenario documentation that shows all relevant information and artifacts used for the interface.
Testing
Testing is an important part of every project, to make sure that it does not introduce unexpected processes. Figaf DevOps Tool helps you automate the testing process. You can take data from your productive system, where you have all the variances of data.
It is simple to create test cases based on the content. You can also run only the interfaces that are affected by a change. That way you don’t have to run all your test cases.
Note on Integration Suite testing: Testing of iFlows in SAP Integration Suite is included in the Figaf DevOps Suite until April 15, 2027. From that date, Integration Suite testing is provided by a third party and requires a separate license. We will help you move your existing test cases to the new tool.
See Figaf Testing Tool for more information, it is an included part of the tool.
Monitoring and alerting
The only way you are able to react in time is if you have the tool to handle and sort alerts. Figaf comes with a set of tools that allow you to set up rules really simple for all abnormalities of your SAP integration. You will be able to find and resolve the critical issues much faster.
See Figaf Alerting Tool for more information
Get more information or start your trial now
Try Figaf yourself, or talk it through with our team first, whatever fits how you work.
Whitepaper: How to Deliver SAP Integration Fast and in High Quality
- Challenges of the SAP Integration Process and how to improve it
- How to deliver and maintain Integrations conveniently
- How to build trust for the Integration within the Organization
- Costs of manual SAP Integration and how it compares to Automation