← Blog

Optimize your SAP PI/CPI development

The steps of an SAP PI/PO and CPI development process, from scoping to support, and how automating them improves change management. Webinar replay.

November 21, 2018 · 1 min read

Your SAP Integration development is not all about delivering interfaces fast. It is also about making sure that you do the proper Change Management for the interfaces. In all organizations, integration is playing a key role in the future of the organization. If you have SAP PI/PO or Cloud Platform Integration (CPI), then you probably have quite a number of projects to look at. It is difficult to get time to architecture, development, and QA because there are too many projects going on. My presentation is built on a process like the following steps. And it is the same if you are using agile or waterfall. Sure there may be a difference in the step size, duration, and naming. But they will always be there. They are the following:

  • Scoping
  • Development
  • Testing
  • Document
  • Transport
  • Validation
  • Go live
  • Support

Figaf DevOps Suite allows you to optimize and automate the different steps in the process, so you don’t have to have all the manual paper tasks to fill in. You will get a much greater visibility into what is developed of your SAP PI/CPI landscape. And then you are going to get just one landscape for handling all your developments since Figaf DevOps Suite supports both PI/CPI in one common landscape.

In the webinar, I also get to show off the new data anonymization process that allows you to anonymize data, so you can do a good test with your HR data anyway.

You can watch the replay here. We did have some technical issues and the video did not turn out correct. So I had to create a new version of the video. I guess it is better because of the rehearsal.

Watch on YouTube Webinar: How to speedup your SAP PI/CPI development

You can start a free trial of Figaf DevOps Suite.

This post covers these products

Capabilities covered

  • Change and transportMoving a change between systems is manual, undocumented, and often done by someone outside the integration team.
  • Regression testingYou cannot tell what a change broke until someone downstream complains.

More from the blog

All posts →

See this working in your landscape

No credit card required.

Integration cost calculator →

Start your free trial

No credit card required

Try Figaf DevOps Suite free for 30 days. It takes less than an hour to get started, and we send everything you need by email.

Join our newsletter

Get the latest about Figaf, SAP and anything relevant to SAP integration, every week in Figaf Weekly.