How the SAP PI/PO can be monitored and how to set up rules for it a lot faster.

1. Figaf Support Optimizer Tool
Do you want to reduce the time spent on support?
© Figaf 2016

2. © Figaf 2016
• Tracking
• Tracking of which errors that occur on which interfaces
• 24/7 support
• 24/7 support receiving step by step procedures to the problems
• Automatization
• When system/network is back reprocessing failed messages
• Notifications
• Ability to send emails to any Incident systems
• Learning
• Making fewer errors with the insight of past errors
What Support Optimizer Tool Helps you with

3. © Figaf 2016
Overview

4. Support Process
PI MessageFlow
Error on Message
Identification
Lookup history
Error seen
before
Perform Same
Actions
Ask what to do
about message
Action on
message
Restart CancelIgnore
Notification message
Save actio
Perform correction
action
Notification on alert
Learn

5. How it works

6. © Figaf 2016
•Bring down support tasks
•Free resources from your valuable IT employees to e.g. run
projects
•Remove frustration from customers (internal and external)
•Save money for the company by reducing “breakdown time”
Save lots of time on support

7. Figaf.com/SOT
Get a free trial today
© Figaf 2016

8. © Figaf 2016
• Multiply different Consumers to have different queues
• Standard alerts can trigger with blocked messages (require some
newer SP)
• Monitor channel errors
• Possibilities to add extra
• Queries in database for messages queues status
• Looking at BPM errors.
Errors that can be monitored

9. Steps in a support practice

10. Error occurs
• The error happens for some reason with a PI message
• It cannot be delivered to the communication channel
• Message mapping fails
• RFC Sender cannot connect to system
SAP PRO Support

11. Identify the Error
• Gather all required information
about the message
• Message information
• Message Payload
• Error
• Category
• Information
SAP PRO Support

12. Error entry
SAP PRO Support

13. Look-Up History
• Find history of previous events
• Using Xpath in the content generated by the identification process
• Find the event that matches most
• Identical mapping
• Mapping errors
• Adapter error
• Read documentation on how to handle that type of alert.
• Perform same action
SAP PRO Support

14. Rule
• Message is identified on XPATH
• Can set message to be sent
• What to do with the message
SAP PRO Support

15. SAP PRO Support
Each error message
• Actions on the message
• Cancel the message
• Retry the message
• Notification message
• Links to retry and cancel the message
• Sent message into SAP PI so something can be reversed in ERP. It could be a
transaction that should be reversed
• Ignore similar errors for a period of time
Actions

16. Investigate
• If the error has not been seen for a default notification is sent to an email
• Ask support person on what to do with the alert
• Send notification mail with all relevant information to support so they have a chance to
investigate what is going on
• Learn about the error and how it can be identified
• Figure out why the error happened
• What can be done
• Update mapping, correct Channel or ..
• Inform relevant party about the action
• Document what should be done next time the error occurs. It can take some
time to get transport on mapping fixed.
• How should be informed about the error. Is it business or the customer
SAP PRO Support