Posts

Highlights from the Figaf Blog 2018

So, here, at the beginning of 2019, I think it will be appropriate to take a look back on what happened on the blog on Figaf.com during 2018.

Last year, we published 35 posts on the blog. Some blogs post were about new releases on some of Figafs´s tools, some were about new insights or how I did see the future and some were about how you can use SAP PI/PO to optimize your workflow. To be honest, I had great fun making all the videos, slideshows and blog posts.  Still, after working with SAP in more than 15 years, I find it very interesting to develop new functions on the different tools, Figaf offers, so that users, in the end, will have a better experience working with  SAP PI/PO.

So, in this blog post, I will take a trip down memory lane and show you the three blog post from 2018, that I appreciate most. Not necessarily, because it was exactly these blogs which had most readers or got most shares or likes on the social media, but because they are still worth reading today in the very early stage of 2019.

Why our testing is different than most test systems for SAP PI

This first post, “Why our testing is different than most test systems for SAP PI“, was published March 24, 2018. This blog is still very interesting, because of two reasons. Firstly, testing is, and will always be, a very important part of working with SAP PI. Secondly, the blog follows up on a podcast with Mark Oshifeso, who is a customer of Figaf IRT.

It is always very interesting for me when customers take time to explain, which challenges they see when they are working with SAP PI. And maybe it will also be valuable for you to read.

SAP PI/PO support, why not learn from the errors

The second post, “SAP PI/PO support, why not learn from the errors“, was published on September 28, 2018. I think it is still worth a read because it is very important to learn from errors and bad created scenarios when you work with SAP/PO.

As you can read in the blog, there are two kinds  of errors in an SAP PI/PO context:

  1. Errors that repeat and solvable by actions like restart the message, refresh of the cache or send mail to the business user in charge.
  2. Errors that occur because a coding error that will be fixed and never occur again (hopefully.

In the blog, you will find a video, where I talked about how you can optimize your SAP PI/PO Support.

Optimize your SAP PI/CPI development

The last blog post I would like you to take a look at is called “Optimize your SAP PI/CPI development“, and was published November 21, 2018. SAP is always in progress, and it is important to set aside time to develop so that your scenarios and solutions always are up to date. In other words, I think it will be valuable for you to take a look at the blog.

In the blog post I talk about a process built on the following steps:

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

In the blog, I also talk about a webinar, I held, about how the Figaf tool allows you to optimize and automize the different steps in the process, so you don´t have to have all the manual paper tasks to fill in. You will get much greater visibility into what is developed of your SAP PI/CPI landscape.

I hope you liked the content, I have chosen for this blog post. If so, you might also like to see Highlights from the integration podcast 2018.

If you have questions to the three blogs or other topics regarding Figaf.com, do not hesitate to contact me.

IRT SAP CPI Monitoring

In my opinion, many companies are using too much time on their support process, while working with SAP Cloud Integration (CPI/HCI). They do not have the big overview, that can help them to create and optimize the best scenarios for their workflow.  This is one of the reasons why I have created the Figaf IRT SAP CPI Monitoring. With this tool, you will be able to manage your support process in a much more efficient way. IRT SAP CPI monitoring with automation will help you to automize many of your tasks. The automation both means that the work is always done correctly and that you can use your time on something else.

I wrote about how you can monitor and search for messages earlier, and it gained some interest so it is something the SAP CPI users are interested in check out the post How to search for messages in SAP CPI, here you can see how to make it easier to monitor your iflows so they contain information that tracks them correctly.

Normally it is a slow job working with support and many things you have to take care of manually. And you have to do it in many different places. This means, that it is very difficult to remember to check all the different places, where you have to make changes, and more important: It is not easy to be sure, that all the changes are made correctly.  And that is way, IRT CPI Monitoring will be a valuable tool to many companies. You can then have just one way to monitor and support both SAP PI/PO and SAP CPI, so  you can set up rules for the processing.

Besides the normal rules we have, it would be possible to retrigger some scenarios with the tool if they are using SOAP or HTTP, but that is something that we need to develop together with a customer.

In this video, I will tell you more about IRT SAP CPI Monitoring with automation:

I offer to solutions to help you with your automation:

  • A cloud solution. If you want more information about this, please contact me. It is still in beta but has the same code line.
  • An on-premise installed version of the Figaf Integration Regression Tool can help you make better documentation to ensure you know what is changed and that you can test the correct interfaces. You can try it for free. Please take a look at figaf.com/irt

 

 

The easy way to find IDOCs in the PI monitor

When you are working to help the support of an organization you often find that you need to find the PI message from an IDOC. This can be quite a problem. But it is quite easy. This video shows how it is possible.