News for Figaf IRT – January 2019 Improving SAP CPI and PI development and monitoring

Enhanced SAP CPI Monitor, Web integration and PI create test form error

So, lately I have been working with development of Figafs Integration Regression Tool, and I think the new stuff is pretty cool. Hopefully, it will be something that is useful for you to improve the ability to develop and run SAP CPI/PI content even faster and give you less support. If you have ideas for improvements I’ll like to hear.

Improved SAP CPI monitoring

We have improved the logging of errors. So it will download the attachments for the failed flows. Then it will be a lot easier for you to monitor and process the alerts. We have also improved the OData filter, so you can specify filters for messages that do not fail. So if you are using sender and receiver information you can setup a filter like Sender = ‘Salesforce’ and Receiver = ‘LOG’ that way you can get the payloads even if there are no errors on the CPI flow.

Support tool with webhooks

The IRT Support desktop is not the only one in your organization. This way you can setup integration with Jira, Paparduty or Solution manager. We configure to receive Jira notifications in about 1 hour with the information we got from the rules using zapier.com but you can use SAP PI/CPI for it.

 

Used Mappings report

Understand what is used on your SAP PI system of mappings, we have now added an option to show also Java Mappings, XSLT and also Message Mappings. Just use the Excel export of your configuration scenario.

In December 2018 I published a blog about this topic: SAP PI/PO Used message mapping.

Create a test case from a failed message

If your message fails because of a message mapping, you can set up a new test case to cover that case. This way it becomes a lot faster to validate that you have fixed the mapping once you have fixed the problem.

 

Want to ease your work?

I do believe that these improvements will make your work a lot easier. If you want to learn more please watch this video:

 

The last details

I also cover my newest insight about IRT in this slideshow:

 

You can try the features now on your own SAP PI/CPI system.

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.

SAP PI/PO Used message mapping

Update (April 9., 2019) I have added some cool new features. Take a look at the blog, I published April 9., 2019: What is the test coverage of your SAP PI message mappings.

One thing that I have been helping with is to help to understand, which mapping is used at the customer location. For instance in a migration project or upgrade project where they need to get away from using the Seeburger Message mapping to the B2B Add-on from SAP.

With the Figaf IRT tool, we already have a link from Message Mapping to ICO, so it would make a lot of sense to use that information to create a report. Then we only needed to understand what was used on your system and join the data.

What does a report look like? Check out the link below.

Operation mapping usage Sample Report

This is released in the beginning of January 2019, and is now a part of the Figaf IRT tool. It will be free to use the feature for now.

If you want to know more, please sign up for the free webinar, I will hold Tuesday 15, January 2019 at 16.00 CEST / 10.00 EST: Create a succesful SAP PI/PO migration in 2019.

Or just get the IRT tool now

https://figaf.com/IRT

We dont need this java on PI

I was working with a client doing Bank (BCM) integration on the SAP PI platform. Everything was going well. Then I got into a talk around if we could get rid of this Java thing.

Then I had a small issue… Since my focus was to make everything in the integration layer as simple as possible and be able to upgrade it. So it would be possible to go to the single stack.

The claim was fair enough that the bank department did not have enough skills on the Java to support a lot of java code. There was enough ABAP developers around, because they had worked with ABAP for 5+ years. They had the skills for coding and supporting ABAP, in that perspective it was much easier for him and the team to support it.

The same does I see when I do consulting with smaller clients, where they only have a basis or an ABAP developer to handle the PI as a side project. How many things can you handle and support before it is too much.

They seem to have gotten the idea that SAP was moving away form Java. So all business logic from SAP will be in ABAP. They thought of this because of the Oracle acquisition of Sun. My comments was that in my view SAP was still investing heavily in Java both for the PI/PO and for the cloud applications.

I recorded this video around the issue.

I think we got to an agreement on what should be different. The big issue was about maintain lookup values for the business. Most of the values should be maintain on the ERP system, which is not a complete goodbye to the Java stack.

And ABAP mappings was never in the scope.

I still think it is a valid point, what are you required to now inhouse before you can maintain a SAP PI system. Do you need to be PI certificed or can you just have some skills in debugging and monitor the PI system?

The post We dont need this java on PI appeared first on SAP PI course.