For all companies, it is important to be compliant with frameworks like SOX or you’re following your audit best practices. It should also cover SAP PI/PO or SAP CPI because they cover an important aspect of your SAP Landscape.
It requires that a developer cannot move code to production without approval from one or more people. They need to check the code and ensure that the developer is not adding any harmful content into the code.
It could be to add your own bank information or in other ways to harm the company or for personal profit.
It is a task that SAP Integration architects have been involved with finding and approving transports. Most of the time they don’t even have the ability to see what is changed and it is the process of labor to figure out what is changed. Without a tool like Figaf, it is close to impossible.
Many SAP CPI clients still rely on File export/imports to handle transports. It is not something that works well with an audit trail.
We have added a few things in the new release of Figaf to make the process better for users.
- Users can now not approve their own transports. It will allow a two eye principle for all transports and give much better visibility on who is changing what
- Email notifications so users and approvers will get notified if they need to approve some transports and once your transport is approved.
- View so you can see which transports you need to approve and work on
- The report will show which approvers have approved which transport
- We have added logging of which user is logging in and which users are changing users and more. That will give you better visibility on who is working on the system.
You can see a demonstration here
Watch on YouTube SOX compliant SAP CPI Transports
The platform supports SAP PI/PO, SAP CPI, and SAP API management where you have all the same options to add approvers and be able to view what is different.
It is easy to get started: start a free trial.
There is also a 30 minute getting started guide.
