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.

How to use the SAP PI Message Mapping documenting tool

For a couple of years I have been developing on a tool for making it much easier to document mappings. The tool is available as open source, so you can try to use it for yourself.

There is also a running version available on that allows you to test out how it works and get instant results back. This is the preferred way to use the tool because you don’t need to install PHP and the project. It is though useful if you want more control of what you are putting into your documents, or don’t want to send your mappings to my server. I do delete the mappings every 15 minutes, so I don’t keep them longer.

I don’t think that I have created a video that shows what the tool can. So that is why that I’m creating this video now. It is really simple to use.

The only thing you need to care about it to export the mapping this is done my pressing CTRL + SHIFT + =, and then you can download the mapping.

There are 3 features with the tool that is useful.

  1. To make documentation simply upload the XMI file.
  2. To copy the comments that you have filled out in a document, you can upload the old excel document and then it will be possible to see the comments.
  3. Find the difference between two different mappings or versions. The tool will show what is different between the documents.

The difference tool is really useful when you don’t know what a person did last time or what a patch contained.

Check out the video, which will guide you thru the process of steps of the documentation.

Start using it now 

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.

Hitler as Project manager for SAP implementations

Very funny video about Hitler as project manger for a SAP implementation. Lots of truths.