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. 

Free Integration development Model for Enterprise Integration

I have been obsessed with finding better ways to make integrations better on. I have been looking at different ways to make the integration better on. It has not been easy and I have created multiple models to capture the most important part of it.

There is a lot of project models out there that help in all phases of a project. They do not take integration specific questions into account. For obvious reasons. It is still something that should be addressed by the people making the plans and developing any integrations.

It is an iterative process because you will need to learn what works and what should be changed. It will mostly be the places where your pattern is different than what you have created earlier. It is a good idea in the design phase the identify the pattern that is used for the integration.

In this iteration, i made it a bit more generic. To support the change in processing that allows users to consider other platforms that just SAP PI/PO. This is an important part of the development because you now have many options to deliver the same integration. Or there could be tools that are better suited to that specific integration.

You can get the 6D Enterprise Integration model free here.

IRT 1.4 Testing big messages in SAP PI/PO

You asked for it. Or our customers asked for it so now we have created it. IRT, our tool to make SAP PI/PO testing easy, has now been upgraded.

I created the following video

We had a customer that requested that we could process 400Mb messages and verify that they worked. We found that the messages about 10Mb were stuck, so we had to find a way around it. The JMS queue we are using, the build into SAP PI/PO has some limits for external clients. So we try to ZIP the payload, and if that is not enough, we save the message in the database on the agent. We can then fetch the message with a web service call later.
The comparison algorithms were using a lot of memory, so we had to refactor them to be able to compare bigger files. For comparing two 1Mb Text documents, it was using 100Mb, so that did not scale. Now the comparison algorithm has been updated to support messages of 200Mb depending on the hardware. Let’s see if the bigger also works with the memory consumption. If the compare fails it will only be on your development system, so no real problem.
We still have one improvement on the UI to show the big files, but it will come in one of the next releases. For now, you can see it in the Excel reports.

The other improvement was about creating unique numbers in each message. Here we are leveraging the option to use the number range module from the B2B Add-on because it enables good flexibility.

Learn more on how you can test your SAP PI/PO better https://figaf.com/irt

7 steps to a SAP PI to PO migration

Some time ago I created a webinar about SAP PI to PO migrations. I wanted to use the content and share it because it is quite useful for everybody working on a migration. I can see that it is some of the questions that I got on my latest webinar was also about the process. I do hope that this gives a better understanding of what is happening.

As with all things, there are 7 steps to make a good SAP Migration. So if you are in the process this is the steps that I would recommend that you take. It is assumed that you will migrate to a new system because it will make it easier to migrate a single interface at the time. If things does not work you will always have a backup plan.

The 7 steps are the following:

  1. Goals
  2. Current integrations
  3. Pattern mappings
  4. Resource consumption
  5. Migration phases
  6. Development
  7. Testing

The process should be very iterative because you learn a lot in the process that you can use to migrate other interfaces. I the current integration you are going to map out all your existing interfaces together with what types of pattern they are using. This information will then be used in the migration phase and how it is going you may get input on how the next interfaces can be migrated.

You can view this in two different ways. Either you can watch my Screen recording video of it.

Or view the slides here and download them if you want to be using them.

I have also created a longer article about some of the SAPs you need to consider more in details in the blog SAP XI/PI to PO migration.  It is not the same and the two have a lot in common.

Testing async/sync sync/async bridges in SAP PI

I this week we have added a new functionality for testing your SAP PI/PO interfaces.

IRT is a custom build application that works with SAP PI/PO to make sure you can record messages from your production system and run them on your development system. All with a few clicks in the application.

Watch the video to see more about the application

We got a client request to support async-sync bridges without BPM, and then we added support also for sync-async bridges. The system will then figure out what type of pattern that you are using. Based on the pattern modules and recording will then happen with data.

The other feature is to make sure you can limit the number of test cases you have. For instance, you may have different order types on your orders. And they each follow a different rule set and is mapped differently. If you have recorded 100 messages in total but only 5 for one type and 95 for the other type. You may just want to test with five messages for each, so verify that your interface. Then you can use the new trim functionality to delete all the other 90 test cases, so you just have 5 for each type.

You can get a free 30 day trial at http://figaf.com/irt