A visibility process is a template provided by SAP to enable the rapid deployment of a SAP EM enabled process. (Read A step-by-step guide on how SAP Event Management works to see how SAP EM works and for links to other blogs describing what SAP EM is) They are not meant to be used as is but rather to be used as templates towards your desired solution. (It is almost similar to the old pre-configured client (PCC) that SAP provided with some standard config that enabled standard processes)
The intent of SAP EM is for you to drive the business process out of your SAP back-end, your 3rd party application system, or your partners back-end system. I.e. it’s your system of record. You then pass the relevant information to SAP EM where you track, trace, report on the level that you require.
Visibility processes provide this tracking and tracing functionality by providing substantial portions of the SAP EM process to you. The parts that it provides to you is described in the figure below and discussed in detail below.
Each visibility process provides the following preconfigured content:
On the Application System
On the application side (E.g. SAP ERP) all of the following is delivered as a template for you to work off of:
- Solutions and Scenarios
- Business Process Type
- The Application Object Type configuration together with all the relevant extractors and relevance functions are delivered. These include the business object key extractor function, the SAP EM relevance check function, the tracking ID extractor function, the control / info parameter extractor functions and the expected event extractor function.
- The Event Type configuration is delivered if applicable. This includes the event data extractor and the event relevance function.
- The implementation of the BAdIs to call the SAP EM Application Interface is delivered together with the Application Interface and is delivered with the Visibility process.
Note: What’s not delivered is the definition of the SAP EM system. Also, note that each of the relevance checks and extractor functions are provided as a general guideline or template showing you how to do that respective task. Take these templates and create your own custom Z functions to take forward in to production.
On the SAP Event Management system
On the SAP EM system, the following configuration is delivered with each visibility process: (Note: Each visibility process may differ slightly in what content it provides. SAP has tried to give examples of each piece of SAP EM functionality and they have used various visibility processes as example implementations.)
Solutions and Scenarios
Event Handler Types and Event Handler Sets
Rule sets with corresponding rules with activities
Status Attribute Profiles
Expected Event Profiles and overdue event rules with activities
Unexpected events and event codes
Parameters with parameter mapping
Authorization and Filter Profiles
Example integration with the alert framework, document flow and workflow
Note: What is not delivered is generally the following:
The definition of the SAP Application System/s (AS) together with its corresponding logical system and RFC destination
The assignment of a parameter mapping profile with an application system
The assignment of users to a role as per the authorization profile
Web User Interface on the SAP EM system
On SAP EM the configuration is provided for both Web UI solutions for status retrieval. It includes the following:
Web interface transaction or scenarios
Web user profiles together with display, selection and event message profiles
Note: What is not delivered is generally the following:
The assignment of a user to a role and a role to a web transaction thus providing the user access to that web scenario in the WCL or Web Dynpro.
On the SAP NetWeaver BI system
The generic extractors for SAP NetWeaver BI are used to pull data from the SAP EM system. In addition there is standard BI content available to make use of the SAP EM data in BI.
Om the SAP NetWeaver PI system
Certain scenarios make use of PI to post messages. The OER solution makes exclusive use of the PTA visibility scenario and all interaction with the OER is expected to go through PI. The PI content is available for download and is available for certain scenarios, specifically the PTA scenario.
Two sets of documents are provided with each visibility scenario:
This document details the process flow that is covered by the visibility process. It also lists the events that are reported together with their corresponding follow on activities. The roles that are provided for in terms of status retrieval are mentioned. E.g. the scenario covers the Sales Rep and Supplier role. If BI is covered then the document will cover what values are covered by the extraction. E.g. the procurement visibility process covers BI reporting content covering Supplier Lead Time from PO to Acknowledgment, From Acknowledgement to ASN, from ASN to GR, from GR to IR and from IR to Payment.
One of the most important topics covered by the scenario description document is the Business Process Procedure which covers, in detail, how to go about testing the scenario as configured by SAP in the visibility process. It is very detailed and typically the scenarios are tailored for specific process variants (e.g. LTL deliveries in shipments).
Note: It is important to understand the criteria under which the standard scenario operates because it is also the basis for the understanding as to how many alterations are required to the standard scenario to get it molded to your situation in your implementation.
Scenario configuration guide
The second document describes what steps need to be taken to enable this scenario in your system. Not all configuration can be delivered by SAP as some information is system specific and it’s mainly these steps together with authorizations that need to be performed prior to having the process enabled on your system.
Available Visibility Processes
For details of the individual processes you can download the 2 related documents for each visibility process from SDN.