Posts

Watch the full flow of Figaf to handle SAP CPI Change Management

We have an integrated approach for handling Change Management for SAP CPI (Cloud Platform Integration aka HCI). In this video (25 minutes) I show how the full application is connected. It is a way to have a central place to manage all your SAP Integration development.

In the video I show how you can get a good change management process for SAP CPI with

  • Full traceability for all modifications made for the development, and linking with business request
  • Ability to view differences between objects and understand how they have been changed because of a business request
  • Test the process have been developed correctly
  • Configuration of Iflows across the landscape, so there are no manual steps for the transport
  • Transport of individual iflows in the landscape
  • Document all changes in the process

There is also part of the monitoring that makes monitoring of the CPI easier and enables you to setup alerting if a message is in a specific state.

If you like it and want to see how we are able to support the change management process in SAP PI/PO.

If you want to try it out then try our cloud offering for Figaf IRTCloud

Figaf now improves your SAP PI/PO CTS transports

SAP PI/PO Change management and documentation have not developed much. And the full cycle of development is the same. It is really a manual process that requires people are spending a lot of time on documentation.

Is your Integration Important. Do you want to minimize the downtime and failures? Then the documentation and QA important.

If you are doing spending too much time on documentation, and if you are not you don’t have enough documentation of the changes made.

We have automated the full process from start to end designed to optimize SAP PI/PO. So you can get the transport documented with all integration objects have been changed.

This means that all your SAP PI/PO transports will be

  • Documented all your development objects
  • Changed link to a business reason, so you know how have approved the change and why.
  • Tested and validated in the QA system with same set of test cases, so you know that everything works as expected.
  • Configured in once place so developers do not need access to configure production system
  • Linking with the incident system so you can get information about what is wrong with your system faster

Check out the video

Because of the above reason, you will be able to:

  • Deliver integrations faster because of an automated delivery process with less time consumption
  • Happier employees because they do not need to perform documentation manually
  • Your QA process will be a lot faster because you don’t have everything delivered automatically
  • Higher quality with fewer errors because you are able to test all integrations fast
  • Fewer differences in the productive system because people are not doing modifications in other systems

Try IRT

We also support the same change management process for SAP CPI

SAP PI/PO Governance made easy

One of the biggest challenges with SAP PI/PO has been the lack of governance models for users. Documentation part has really been lacking making it and it has required a lot of manual work to get it done.

The process for handling governance for SAP PI/PO is just the same as with SAP XI for 15 years ago. The tooling has not changed much. There have just been a few changes that could say to improve the area. Ever since I started with XI/PI i have been working on different ways to improve the process of documentation but we have not made the dream solution yet.

Last year we added the option to use the ticket and thereby log changes to any object in SAP PI and PO, so all versions between them would be remembered. This was the first step in making documentation easier with Figaf IRT.

Now we are ready with the next big thing liking the full development together. So all documentation of your development is linked to CTS transports. That way you will know why something was changed and can see what is being transported much more transparent.

We have also added a central configuration of your channels. So there is just one place where you need to configure the information. IRT will then apply the configuration once the transport has been imported.

You can then make exports of your Integration scenarios documentation, and then show a changelog of this. And also show what was performed as a result of a ticket that you can add to your Jira, Solman to prove what you have done.

Here you can find the recording of the webniar that I did on 1 May 2019, where we showed this information to the public.

We are soon adding this to the release, so signup to check out the current version, and be the first to know once we have released the new iteration. If you have ideas on how to improve the tool and be a part of the beta program reach out to support@figaf.com.