Best Practice Skills for SAP PO/PI Integration


When talking about best practices in the area of SAP integration, we must take into account the skillset which is necessary for a successful career in SAP PI/PO development.

This post is a part of my best practice series where I’m covering what is going on with SAP PI/PO best practice. Check out the introduction to the series here 

I see there is different levels of skills in the organisation. It is important to know which of the skills that is most important for a organisation. This post is about to figure out which level of skill you have in your organisation. I see there is five different levels of skills in all organisations. You can read about them below.

Best Practice SAP


All organizations must have an internal level-based structure, which allows its members to see the constituents of their business clearly. Those working for the organization have to know what SAP PO is, what it can do, and what types of questions can the developers answer. A good businessperson has to know more than just the specifics of the business; they also have to know what they can expect from the PO system.



Next, there needs to be someone who monitors the existing processes. This person needs to be able to troubleshoot and to fix things – in case some of the messages aren’t processed, or if a different error pops up. These errors need to be corrected in a short period of time, as the contents of the PO system are business-critical, and an interface that is not running properly will negatively impact the company; it can even lead to loss of business.

Bug fixer

On the next level, the organization will need someone who is able to make small adjustments, e.g. mapping a different field, changing a communication channel so it points to a different directory, adding a new user, and other basic administration and PI tasks. This person has to make sure everything is in working order, while also fixing the areas that do not work as expected.


The next level is reserved for the SAP PI/PO developer, whose tasks include developing new scenarios, and correcting complex mappings. This level generally includes both Junior and Senior Developers. This position requires a more specialized set of skills, e.g. the completion of a full PI course, and a lot of assignments that add up to a substantial degree of experience.


The highest level belongs to the architect. This is the level where the main objective of the business is described, and where the various types of required scenarios are discussed. This the highest and most complex level.


You have to figure out where your place is in the hierarchy of your organization, according to your education and experience (of course, it depends on the number of co-workers and their respective skill sets as well). The higher you reach, the more autonomy you have – but it comes at a cost: hiring good developers can be expensive and challenging, but once you are in a position of power, this will also be your job. You will have to find PI/PO developers with approximately 3-5 years of experience.

Externally, freelance consultants can also work for the organization. Their work has a broader spectrum; basically, they can be contacted for any extra tasks. Even as an architect, you might need a fresh perspective from time to time.

SAP certifications are not needed per se. However, as an SAP customer, you will receive a more comprehensive perspective on SAP along with the certification. You will be sure that the people you hired know how to handle the landscape, and how to come up with improvements and adjustments to the system. The certification exists to reassure you, but it is otherwise useless.


Obviously, SAP tools are evolving. New tools appear on the market. As a developer, you have to keep up with these. Don’t get too comfortable on any of these levels – a pro is always ready to learn something new, and is eager to see what is happening in the world of SAP.


After all, it is in your best interest to use the the newest, most time-efficient tools.


Which is your preferred level? Do you like being the lone wolf at the top, the administrator who gets to do a bit of everything, the Junior/Senior developer or the freelance consultant? Let me know in the comments section!

Check out my other posts from the SAP Best Practices series, and do not hesitate to share your opinions.


Part 1:

Part 2:

Part 3:

Part 4:



Comments are closed.