First Course on using Figaf IRT to test SAP PI/PO

I have now created the first recording of a course on using Figaf IRT to test your SAP PI/PO system. The goal is to make it easy to understand all the

There will be room for improvement. Probably a lot. But it will be a starting point, and there will be a new revision of it once we get some more features ready to make the SAP PI/PO testing even easier. You can find the videos here.

The videos are free. My goal is to get you to set up the test cases and I believe it is easier with a bit of training. Video will take around 1 hour to watch. I have included slides at the end of the presentation

If you want to install the free version of Figaf IRT for SAP PI you can find it here.

Installation and configuration of IRT

Collecting test data for SAP PI

Running tests on SAP PI with Figaf IRT

SAP Cloud Platform Integration Day 2017 (aka third annual HCI Day )

I attended the SAP Cloud Platform Integration(HCI) day this week.

I created a video around the topic where I’m going deeper into the content that I can describe here.

 

There is a problem with the name of the product. There is no official abbreviation of it so during the presentation it was mentioned as HCI, SCP Integration and CPI. CPI is the most logical but is used by another product. The lack will mean it becomes more difficult to find people with the correct skillsets because there is so many different solutions. So until somebody find an official abbreviation I’ll be using HCI.

There was a section with the news highlights of HCI where Udo Paltzer was presenting some new.

·        Self service key store

·        JMS Queues internally to decouple async message. It is on the enterprise version.

·        99.99% uptime on a monthly basis. Somebody was mentioning that contract giving SAP access to hours of service window if it was planned.

·        Web UI was the way forward, Eclipse would be depreciated.

·        A customer regression testing solution. Since it is something I’m quite interested in with my tool for doing the same on SAP PI/PO. Check out http://figaf.com/irt to learn about the generic solution to test SAP PI/PO.

Customer regression testing is a service SAP provides where a customer can submit an iFlow together with in and out test messages. SAP would then make a test mock of the service and run the tests on it.

SAP will then run those mock iFlows in their own system before the code is released for customers and if there are any errors they would ensure that they do not break any functionality. This is a service you need to buy at SAP and will only cover your most critical or complex scenarios. And if your iFlow changes you will need to submit new tests. It will be a service you will see on the price list.

SAP was also presenting some of their services that used the HCI. There was a Ariba Connector hub something which enabled you to onboard vendors or suppliers fairly easy. Here the user was guided thru a wizard about the integration. There was some confusion where it fitted in but they were just creating iflow based on the configuration. There was also a Farma net demo where they also created iFlows in the background using some internal APIs for HCI. The API will be public this fall.

I was at a workshop last summer in Waldorf where we were looking for better ways to improve the integration experience. One of the ideas was this one click or wizard approach to create integrations.

There was also a Successfactor and eDocuments presentations. From them it was clear to see that these services gave companies an approach to SAP HCI and then they would get to know the product. And hopefully start moving more integrations to it. The hot example is the Spanish SII document that will start 1 july 2017. Last weeks there was 80 productive instances running now there was 280. So it was a big driver for getting HCI to customers.

There was 9 partner presentations of different levels of depth and relevance to HCI.

Some of the takeways I got from Morten Wittrock from KMD was that it would be beneficial to learn about the Camel framework and groovy scripts because it enabled you to leverage the full platform.

ProXcellence was talking about if customers was really ready for the cloud. It was something to buy HCI but not all organizations was able to leverage it together with the changed capabilities of the cloud infrastructure. HCI was quite simple but you sometimes needed to get some more experienced developers onboard because there were limitations to what business uses knew about certificates and the integration.

Do check out video attached to this post.

 

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.