Posts

How to start from scratch for using SAP PI/PO

If you just purchased SAP PI/PO there is a lot of things to consider. This post will help you in the process of figuring out what is interesting.

The thing is you don’t know too much but it will have the greatest impact on what is set up. So it would be a good idea to have an architecture workshop where you will get all the insight into how you can create a solution that matches what you want to achieve. So it is an ideal time to get help.

I have created a mindmap video where I cover some of the most important things about the process. Watch the video below.

Architeture

A big thing is to get the architecture to match what you want in your organization. There a lot of things to consider like naming conventions and how to create interfaces. This should you would hopefully get a few sample interfaces that show how the things would look and how to monitor them. You should also consider how to make documents required for it both mapping documents if required and documentation.

It may be a good idea to have a secondary consultant to help you in the process that is on your side because you don’t know as much about what you can expect.

 

Testing

Testing is one of the important things in the process. If you “just” replace middle where you have the ability to get input and output document. If you use the Figaf IRT for SAP PI/PO testing then you will be able to perform the tests to verify that messages look identical. This way you can save some time for testing the application together with business experts.

If are doing a greenfield implementation of SAP S/4 ERP then you will have to change the interfaces on both sides. You will still have to setup testing so you can ensure that the process works correctly even when you have to apply support packs.

Migration

A good place to start is also my migration guide. It is much the same things, except that you have more free hands with what you want to do and the changes that you must make.

There are some of the things here that can be applied to the list of attributes to collect from each interface. You can find it in the slides. If you can get the information it may be a lot easier for a partner to do a good estimation of the project. You may add data like a number of fields in each interface to give better information about required mapping size maybe group it in to bucket like 1-20 , 20-100, 100+ fields that need to be mapped.

Cloud world

In this blog, we have not been covering any of the SAP platforms that may be interesting and save some time on integration. There is the SAP Cloud Platform Integration (CPI aka HCI) which is a solution that is quite simply to PI but cloud-based and more flexible. It contains a lot of prebuild content that will speed up and integration, so it may be used in some scenarios. You may also be able to run this type of interfaces on your new SAP PO system. For some integrations, it may be beneficial to use because of the flexibility and the availability of adapters.

Other advice:

I ask the question what people would like to have known before they started on the SAP PI/PO project a long time ago and I did get some interesting answers that may be quite in line with what you are looking for. There was a lot of ideas about making better guides for what should be implemented. You can read all suggestion here.

 

Good luck on your new platform. I promise it will be an adventure. 

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.