Situation handling is a concept for bringing urgent issues to the user’s attention. “Situations” indicate exceptional circumstances that are critical to a business process

The situations concept helps the user to recognize, understand, and resolve business issues by gathering all relevant information and recommending solution proposals.

The solution proposals can be either predefined or learned, based on similar cases in the past.

Situation displayed on an object page
Situation displayed on an object page


Use situations if:

  • There is an exceptional business issue that is not part of the application itself and requires the user’s attention.
  • The business issue is not based on a standard business process and is explicitly exceptional.
  • There are recommended actions to resolve the issue.

Do not use situations if:

  • Something is, or should be, a standard feature of your application.
  • The issue is based on a standard business process and is not exceptional.
  • You just want to display a notification.

Responsiveness and Adaptiveness

The Situation section is ranked as the first anchor of the affected object page and always uses the full width. The content of the situation section wraps if the available width is not sufficient.

All content of the object page follows the standard responsive behavior of the respective SAP Fiori controls.

Size S
Size S
Size L
Size L


Currently, a situation can only be displayed on the object page for the affected object. The situation is displayed in the first section of the object page, and is called Situation or Situations.

As a minimum, the Situation(s) section contains an icon, a title, and a textual description. You must also provide actions to resolve and dismiss the situation.

In addition, you can display additional content to to explain the root cause and the impact of the situation, and to help the user understand the context.

Situation box
Situation box
The situation box contains the following elements:
  • Icon
    Indicator to catch the user’s eye.
  • Title (including an optional situation switch)
    Brief and concise description of the situation at hand.
  • Description (text is wrapped, depending on the available width)
    Detailed description of the situation.
  • Documentation link (optional, displayed directly after description text)
    Additional information with links to the referenced object.
  • Date
    Date on which the situation occurred or is expected to occur.
  • Actions
    Set of actions related to the situation.
Situation box (with reference link)
Situation box (with reference link)

Behavior and Interaction

The Situation section is displayed only when the object is currently affected by a situation. The section is removed as soon as the situation no longer exists.

Dismissing a Situation

Users can handle the lifecycle of the situation by dismissing it. They can pick a reason for dismissing the situation: situation resolved, situation obsolete, or situation incorrect.

A message toast confirms that the situation has been dismissed. If there are multiple situations, the next situation is displayed. If there are no more situations, the standard object page is displayed.

'Dismiss Situation' popover
'Dismiss Situation' popover

Switching Situations

Switching between situations
Switching between situations

If multiple situations affect the current object, a button appears next to the situation title for switching between situations.

Clicking the transparent button opens a popover with list items that display all the available situations. When the user selects an item, the display switches to the chosen situation.


Displaying Solutions and Additional Information

Most of the time it is not enough to just inform the user about the situation that is currently affecting the displayed object. You also need to provide users with additional information so that they can understand the root cause and impact of the situation.

Ideally, the system proposes several solutions to resolve the situation or to at least minimize its impact.

If additional situation-related content is available, split the first (situation) section into different subsections to structure the content. Show the subsections in the following order (each bullet represents a subsection):

  • Situation description
  • Solution proposals / recommendations
  • Additional situation-related content (if available)
  • Related situations (if available)

The number of subsections is not restricted but should remain manageable. To avoid too much white space, you can display situation solutions and related information in the same subsection if the content is manageable.

If the object page used to display the current situation is dedicated only to resolving the current situation, display the subsections as regular sections of the object page. This avoids having only a single section on the object page.

Situation subsections
Situation subsections

Notifying Users About Situations

You can use notifications to bring a situation to the user’s attention.

The notification text summarizes the situation and gives the user a quick overview of what the situation is about.

If the user clicks the notification, the system navigates to the affected object page, which shows the respective situation.


Want to dive deeper? Follow the links below to find out more about related controls, the SAPUI5 implementation, and the visual design.

Elements and Controls


No links