Hi everyone! If you have been using the On Premise version of SAP Profitability and Performance Management or is knowledgeable about the solution, then you might be familiar already to My Events application or screen wherein users can look at the error event messages that occurred during execution of activities, define temporary or permanent correction overlays for the data and trigger a partial rerun. In the Cloud version of Profitability and Performance Management, a simplified version of Business Events Management Screen has been recently implemented and in this blogpost, I will provide more information on what to expect about the simplified screen.

If you know My Events in the On Premise version of SAP Profitability and Performance Management, then this blog is something you might be interested with or is exactly for you. Let me start with my blogpost by giving you an overview of the simplified version of Business Events Management Screen. Same as in the On Premise version, the screen allows users to access the business events or errors that occurred during execution of activities. However one of the main difference of the simplified screen in Cloud vs My Events in On Premise is that in the Cloud version, there is no overlay rules for data or the IF-THEN maintenance section where users can apply overlay rules. Instead, a “real” data correction option was introduced in Business Events Management Screen in Cloud. This means that users can navigate to the appropriate Input/Output Activity Screens (Show/Analyze/Visualize) and from there, they can immediately correct the events/errors in the source data. Another difference is that in order to create business events in Cloud, event handling must be set to “Correction”, in On Premise it should be set to “Management” in order to create business events. Below screenshots show how Business Events Management screen looks like in Cloud.

In the next section, I will be discussing the steps on how business events can be created in Cloud and how users can access the simplified Business Events Management Screen.

Preconfiguration in Modeling Screen:

1.User needs to configure the functions and set event handling of the processing function to “Correction”. For functions with assigned error and abort checks as well as for functions with unassigned items, it is expected that business events will be created. User will have to create editable query functions and connect the input tables of the executable function in order to make corrections in the source tables once user is in Business Events Management Screen.

2. Create a process template which will later on be used in creation of Process Instance in Process Management Screen. The process template should include an executable activity that uses the function that will trigger the business events as well as the Input/Output activities where the source tables/data are connected.

3. Define the Business Event Field. Once everything is set in Modeling, go to Process Management Screen by choosing Go to Process Button.

Execution of Activity in Process Management Screen:

In Process Management Screen, (1) create a process instance using the process template that was configured in Modeling Screen. After creation, (2) select the executable activity and (3) trigger the run. Since there are errors or unassigned items, business events indicator will then be visible beside the execution activity. (4) User should click on the business events indicator in order to open Business Events Management Screen in a new tab.

Handling Business Events in Business Events Management Screen:

In Business Events Management Screen, the important buttons and sections are shown in the screenshot below.

Tools in the Header contains:

• Run – this button executes/runs the process with the full dataset. Meaning, data will be deleted in the Ytable then populate it again with the run result
• Restart – processes the corrected data and the corrected data is added to the Ytable. Meaning, if there were 2 errors that were corrected, choosing restart will just process those two records and will insert the data to the Ytable
• Refresh – this button will refresh the screen
• Messages – will open application monitor in a new tab

To correct the erroneous records, user will need to click on Go to button. All the available Input/Output activities in the Process will then be displayed and user can choose Show, Analyze or Visualize to display and correct the data. This has been implemented so users will no longer have to go back to Processing or Modeling Screen just to access or change the Query functions or source tables. Once user opens any of the screens, the screen will be filtered already and will display only the erroneous dataset.

From Show Screen, user can directly change or correct the erroneous data provided that the Query used in the Input/Output activity is set to Editable.

Once all erroneous data have been updated, user can close Show screen and go back to Business Events Management Screen then choose Run or Restart button. The rows that displays functions with business events will be cleared out after run/restart.

And once user triggers refresh button, the displayed processes will be cleared out as well. That’s how simple or easy it is to handle business events in Profitability and Performance Management Cloud. The erroneous records are filtered already so the users can easily handle or correct the business events.

The next section is to provide some simple scenarios that can be used for Business Events Management.

Scenario 1 – Allocation with Unassigned items. In this scenario, a direct allocation is used where records with the same characteristics will be allocated from Sender to Receiver. Below is the Sender and Receiver Table that will be used in this scenario and in the Sender Table, there is Customer “CX” which does not have any match from the Receiver table and is expected to be unassigned once the allocation function is executed. If event handling is set to Correction, it is expected to create business events once execution activity is triggered in Process Management Screen.

Scenario 2 – Function with Error check. In this scenario, an allocation function with error check is used. In the error check, Customer field is assigned and it will give an error in case Customer field contains “CX”. Since customer field contains “CX”, it is expected to create an error after execution of the function. An abort check can also be used in this scenario.

That’s it for my short blogpost about the simplified Business Evens Management Screen in Profitability and Performance Management Cloud. I hope the simple scenarios as well as the configuration steps somehow helped you to understand how BEM works in Cloud. If there will be any updates or enhancements, do expect that this blogpost will be updated as well. 🙂