- SAP Managed Tags:
With SAP S/4HANA Cloud 2202 you can now create your own situation use cases. In this blog post series, I’d like to introduce the new configuration apps based on demo cases. In the third part of this blog series, you learned how to create a situation scenario. Now let’s create the first template for a use case and derive a productive situation type to trigger situation instances.
To illustrate how you can create situation use cases from scratch, the extended framework comes with demo cases you can trigger with the Situation Handling Demo app. The app is based on a simplified booking portal that uses SFlight demo data. The configuration comprises two objects (Flight and Booking), one scenario (Flight Profitability), and three demo templates (Ecological Footprint, Sales Rate, and Booking Rate). See also: Situation Handling – Extended Framework.
A situation template serves as a blueprint for a situation type that is used productively and creates situation instances. With the template you define the basic configuration. Let’s start with the simple demo case Ecological Footprint. It monitors the eco index of flights. The threshold defined in the condition section is the basis for creating situations.
The standard settings for the instance behavior are unchanged. Each trigger creates a single situation instance and, after closing a situation, it remains in the system. The situations are displayed in the Instance List of the corresponding situation type in the Manage Situation Types - Extended app.
There is no one-click action for solving such an issue. That’s why a navigation option to a related app is used. The action is configured as a general action because it relates to the anchor object. It is automatically available for any anchor-trigger combination and displayed in the trigger details section as a navigation action.
The eco index only needs to be checked from time to time because it’s erratic. Also, numerous flights might be affected, which could lead to information overflow for the end user if each and every change is signaled directly. Therefore, the batch-based trigger Periodical Flight Check is used.
You use the trigger details to define the conditions that determine if and when users will be notified about situations.
To create situations, only one condition is necessary. The filters limit the monitoring to flights with an eco index above 80 % and departing within the next fourteen days.
Since no further conditions have been configured, all situations need to be closed manually.
Two different texts are defined for the situation display. One is shown in the My Situations – Extended app and the other in the notification on SAP Fiori launchpad. The situation text describes a single instance while the notification aggregates situations referring to the same airline, for instance: Critical Eco Index for LH. There are 5 LH flights with a critical eco index.
For notifications a standard behavior is selected. It informs all users responsible when a situation has been created. If someone is already working on a situation, they also get a notification after updates occur.
The general Display Airline action is automatically displayed in the Trigger Details section.
The batch jobs are scheduled every Monday morning at eight o’clock.
Recipient determination works in the way you’re familiar with from the standard framework of Situation Handling.
To trigger situation instances let’s create and enable a situation type called Critical Eco Index. The configuration of the template can be used right away for a productive situation type. We want to change the recipients and inform only the manager about critical eco indexes. Therefore, we’ll set the filter in the Member Functions to Manager.
The settings in the Manage Teams and Responsibilities app needs to reflect the roles in the Team Members section.
The users responsible get a notification that aggregates the situation per airline.
Selecting the notification takes you to the My Situations – Extended app. The situation page displays the detailed information as configured in the situation scenario, including the navigation option to a related app as configured in the situation type.
The next blog post illustrates how to configure an escalation case in which situation instances can be closed and reopened according to changing data.
Let me point you to further information:
New apps for the extended framework for Situation Handling
Demo Cases
To illustrate how you can create situation use cases from scratch, the extended framework comes with demo cases you can trigger with the Situation Handling Demo app. The app is based on a simplified booking portal that uses SFlight demo data. The configuration comprises two objects (Flight and Booking), one scenario (Flight Profitability), and three demo templates (Ecological Footprint, Sales Rate, and Booking Rate). See also: Situation Handling – Extended Framework.
Create a Situation Template
A situation template serves as a blueprint for a situation type that is used productively and creates situation instances. With the template you define the basic configuration. Let’s start with the simple demo case Ecological Footprint. It monitors the eco index of flights. The threshold defined in the condition section is the basis for creating situations.
Situation Instances
The standard settings for the instance behavior are unchanged. Each trigger creates a single situation instance and, after closing a situation, it remains in the system. The situations are displayed in the Instance List of the corresponding situation type in the Manage Situation Types - Extended app.
General Actions
There is no one-click action for solving such an issue. That’s why a navigation option to a related app is used. The action is configured as a general action because it relates to the anchor object. It is automatically available for any anchor-trigger combination and displayed in the trigger details section as a navigation action.
Situation Triggers
The eco index only needs to be checked from time to time because it’s erratic. Also, numerous flights might be affected, which could lead to information overflow for the end user if each and every change is signaled directly. Therefore, the batch-based trigger Periodical Flight Check is used.
Trigger Details
You use the trigger details to define the conditions that determine if and when users will be notified about situations.
Conditions
To create situations, only one condition is necessary. The filters limit the monitoring to flights with an eco index above 80 % and departing within the next fourteen days.
Since no further conditions have been configured, all situations need to be closed manually.
Situation Display
Two different texts are defined for the situation display. One is shown in the My Situations – Extended app and the other in the notification on SAP Fiori launchpad. The situation text describes a single instance while the notification aggregates situations referring to the same airline, for instance: Critical Eco Index for LH. There are 5 LH flights with a critical eco index.
Notification Behavior
For notifications a standard behavior is selected. It informs all users responsible when a situation has been created. If someone is already working on a situation, they also get a notification after updates occur.
Navigation Actions
The general Display Airline action is automatically displayed in the Trigger Details section.
Batch Job Scheduling
The batch jobs are scheduled every Monday morning at eight o’clock.
Recipients
Recipient determination works in the way you’re familiar with from the standard framework of Situation Handling.
Create a Situation Type
To trigger situation instances let’s create and enable a situation type called Critical Eco Index. The configuration of the template can be used right away for a productive situation type. We want to change the recipients and inform only the manager about critical eco indexes. Therefore, we’ll set the filter in the Member Functions to Manager.
The settings in the Manage Teams and Responsibilities app needs to reflect the roles in the Team Members section.
Informing End Users
The users responsible get a notification that aggregates the situation per airline.
Selecting the notification takes you to the My Situations – Extended app. The situation page displays the detailed information as configured in the situation scenario, including the navigation option to a related app as configured in the situation type.
The next blog post illustrates how to configure an escalation case in which situation instances can be closed and reopened according to changing data.
- Custom Situation Cases: Configure Your Own Use Cases (1/6)
- Custom Situation Cases: Model Your Own Situation Objects (2/6)
- Custom Situation Cases: Create Your Own Situation Scenarios (3/6)
- Custom Situation Cases: Configure a Simple Use Case (4/6)
- Custom Situation Cases: Configure an Escalation Case (5/6)
- Custom Situation Cases: Configuration of a Complex Use Case (6/6)
Let me point you to further information:
- SAP Help Portal: Situation Handling – Extended Framework for SAP S/4HANA Cloud
- SAP Community: Intelligent Situation Handling
