Enterprise Resource Planning Blogs by SAP
Get insights and updates about cloud ERP and RISE with SAP, SAP S/4HANA and SAP S/4HANA Cloud, and more enterprise management capabilities with SAP blog posts.
cancel
Showing results for 
Search instead for 
Did you mean: 
Situation Handling is SAP S/4HANA functionality provided to bring certain settings (situations) to the attention of a relevant group of business users. This allows for proactive notification to the needed users for a situation that has occurred. Situations may be seen as problems or chances.

Business users are given the notification of a situation, together with the notification status (Open, Resolved, Obsolete, Invalid), contextual information relating to the object pertaining to the situation and lastly, any actions deemed necessary to address the situation. Situation Handling conveys the crucial and appropriate information to the attention of the business users.


Figure 1: Process Flow of the Situation Scenario


With SAP S/4HANA Cloud 2202 you can create your own situation use cases with the extended framework for Situation Handling.  The extended framework offers three new configuration apps: The extended framework also contains an enhanced end-user app, My Situation- Extended, and the Situation Handing Demo app. You use the demo app to manage the flights of a fictional booking portal and to trigger situations based on pre-delivered configuration samples.

Manage Situation Object:

In this application, we can model business objects that enable Situation Handling. A situation object connects existing application artefacts such as CDS views, events, and actions that form the foundation to set up situation use cases. Model business objects that enable Situation Handling, including the events that trigger a situation.

Manage Situation Scenario:

In this app, you can model your own situation scenarios for extended object-based situations. That is, situations that occur for a specific business object, such as a contract. A situation scenario is the technical description of a business scenario and provides the foundation for defining multiple use cases in the form of situation templates, which serve as blueprints for situation types. The business object affected by a situation is defined as the anchor object. In the app, you define the anchor object and add all objects that could trigger situations for the anchor object. For the trigger objects, you define the trigger events and the actions that help the users resolve the situations. And you define which information is displayed in the My Situation - Extended app to the users responsible for solving situations based on this scenario.

Manage Situation Extended:

In this application, you can create situation templates as blueprints for business cases. It can also create situation types for productive use. You could manage instances here and collect the message-based situation which is supposed to be triggered.

Situation Handling Demo:

This app contains test data you can use to explore the extended framework of Situation Handling. This is a simplified version of a booking portal focusing on actions for flights and bookings. After defining and enabling a situation type, you can use the app's actions to trigger situations.

My Situations – Extended:

With this app, you can display all situations in your area of responsibility, based on the extended framework of Situation Handling. From the overview table, you can go to the situation page where context information and related actions help you solve the situation.

In this blog, you will learn how to use the extended framework for Situation Handling based on demo cases. Business Scenario for the Demo Case of a Fictional Flight Booking Scenario. As in any business, trust, reliability, and a smooth process is to be looked upon. The sales and profit of the flights are considered. Other issues like Cancellation, Overbooking, rebooking, missing, or flight delays must be captured thoroughly. To get a better grip on the processes the right user groups should get informed if such issues are likely to happen. These heads-ups allow us to react to the situations in time and decrease negative effects to a minimum.

The Situation Handling app supports these cases. You can manipulate the flight data, for instance by assigning a smaller plane to overbook the economy class.


Figure 2: Flight details showcased by Situation Handling Application


The end user gets a notification on the SAP Fiori launchpad.


Figure 3: Notification Preview


The situation is also displayed in the list view of the My situation-extended app. The details about the situations are shown on the situation page in the My situation-extended app. Situation Configuration with Templates, Scenarios, and Objects. The extended framework for Situation Handling introduces the new concepts situation scenario and situation object in addition to the existing situation template. This three-layer approach lets you configure your own situations in a generic yet controlled way. As you know from the standard framework of Situation Handling, situation templates are used as blueprints for use cases. The pain points identified in the fictional booking portal translate well into templates which are configured in the Manage Situation -Extended app. For the overbooking case, the values of seat occupancy and flight date are of interest. Situations can be detected by a regular check of the flight data or by events such as new bookings, cancelled bookings, or upgrades. Taking the details of the templates into account, we can see a similar pattern. All templates refer to a flight. The flight data can be observed with a batch job. Alternatively, situations can be triggered by a flight event or a booking event. This means you can combine these use cases within a scenario. The situation scenario provides the basis for situation templates of a similar pattern. It defines the anchor object that is affected by a situation, which, in our case, is the flight. The scenario also contains all the triggers that relate to the flight, for instance, the batch job to check flight data and events that change flight data or booking data. This rather generic collection of situation triggers for an anchor object lets you create a wide range of templates. Any trigger can be used to model conditions based on any supported data from the CDS views. Scenarios are configured in the Manage Situation Scenario app.

The demo scenario is based on two objects: the flight and the booking. These objects are not specific to our demo scenario, they could also be used for further scenarios, for instance, to configure situations for bookings, or in combination with further objects for modelling flight maintenance and service cases. The scenario supports reusability by mapping the objects while the details of the objects are configured in the Manage Situation Object app. A situation object is a model of a business object that reuses application artefacts. The main components for the detection of situations are CDS views, which represent the object and events that trigger situations. In addition to modelling the detection of situations with the extended framework, you also configure how the end user is informed – either through SAP Fiori launchpad notifications and/or the Manage Situation Extended application. Sending notifications to the right group of users works as it does for the standard framework for Situation Handling. You define the texts in the situation templates. With the extended framework, you can now configure different texts for each condition too. The Manage Situation Extended app provides many more features for the end user, including search and filter functions and a situation page with detailed information and solution proposals.


Figure 4: The situation of Flight along with Proposed Solution


In addition to modelling triggers for an object, you can also add actions that help users solve a situation. In the scenario, you select the actions that support the business case as defined in the situation object. You can configure the scenario-specific layout of the My Situation- Extended app. For the scenario-specific list view, you can choose to add one column with detailed data related to the anchor object (flight) and another for the trigger object (flight or booking). You can also configure filter options for the selected data. For the situation page, you can configure a detail section for the anchor object and the trigger object. In the situation template, the texts for the situation instance and notifications are defined as in the standard framework. Here by, you filter which actions are relevant for a specific use case.


Figure 5: The Details of the Flight Situations Scenario


In conclusion we learn the complete scenario of what a situation is in any realm of business. The causes of that situation, the trigger points, the action items required to be done after the situation takes place. And along with that we learn our options to resolve or propose a solution to handle the situation.
4 Comments