Skip to Content

Monitoring of SAP PI interfaces is also a business responsibility

As a developer I’m often in touch with the business about something that is failing in SAP PI. It is not always me that has done anything wrong. Sometime a mapping error is because I have done something wrong or did not take in to consideration an important element.

Sometime the error is because for instance the purchase order is missing a required field by the partner or standard. This is a business error, and the only people how can fix this part is the business consultants. It can sometimes be a bit difficult to explain what went wrong and it is not a SAP PI error.

I created this video to talk a bit more about the problems and what it means for the business when they see these errors. So please share this video with your business consultants who say it always is the PI that gives problems.

The monitoring is something that both developers and business in some way should be involved in.

One way I’m working on information the business about what SAP PI is on my site. SAP PI for everybody, where you can find some free training videos about what PI is and what to consider.

7 Comments
You must be Logged on to comment or reply to a post.
  • Hi Daniel,

    very interesting blog.

    At my current client we are finding the same kind of monitoring is needed in CE for the Business Processes, in fact from end to end in BPM, that's MDM Import Ports, Syndicator, PI Channels, and CE Processes, all need to be monitored to ensure the whole solution runs sweetly.

    All the best,

    Andy.

  • Hi Daniel,

    When an error occurs (mapping or routing) the technical people will be the first ones to see it. Then they need to talk to the business to resolve that. On that point I agree.

    When you say: "Monitoring of SAP PI is also a business responsibility"  I do not agree on that. The business responsibility is to monitor their process and PI/PO is just some tooling.

    We also can not expect that business users are diving into a PI/PO system to see how their messages are processed. It even gets worse when the process uses different applications.

    My point is, due to the lack of some easy-to-use Process Monitoring Tooling we can not expect the business to do monitoring of systems. From my perspective I see that PI/PO still has only a technical monitoring and there is also a gap.

    Best regards,

    Guido Koopmann

    • Hi Guido,

      Yes the business does not have the skills or tools to monitor complex systems with a lot of loose systems connected. Some third party tools can make it easier to monitor the messages and see the messaeg status based on the business requirements.

  • Hi Daniel,

    Good blog,

    Bussiness errors are really common but unfortunately no permanent solution to handle this , i always recommend my bussiness team to write a proper validation mechanism before data reaching to PI.

    Even SAP ECC team has to write a effectivate validation logic, this is one best way to minimize bussiness errors.

    Regards,

    Raj

    • It is a great idea about having the validation on the ECC side. It is the right place to have the business logic validation of documents. Then they can see what is wrong when they save the documents.

  • We are using Advantco's PI Monitor. With this tool you are able to monitor PI technical messages together with business monitoring in a centralized dashboard, covering sender system, PI and ECC systems. You can even view business process, i.e. document flow of a sales order, directly from the PI monitor client.   Just for you guys information.