Test Script

SAP S/4HANA Cloud - 12-07-22

Situation Handling (31N)

PUBLIC

Table of Contents

1 Purpose

2 Prerequisites
2.1 System Access
2.2 Roles
2.3 Business Conditions
2.4 Additional Manual Configuration

3 Overview Table

4 Test Procedures
4.1 My Situations
4.2 My Situations - Extended
1 Purpose

Situation Handling detects business situations by evaluating conditions (rules) for business facts. A business situation occurs, for example, when a business object changes a status relevant to a user,
when critical deadlines are coming up, or when a KPI passes a threshold.
Professional users need the extensive functionality of SAP software that reflects the increasing business complexity. At the same time, users want simplified UIs and an amazing user experience. If
we know how users behave and what their requirements are in a specific situation, we can provide the right information on the spot.
Situation and context awareness allow users to focus on data and functionality that are relevant for the them in the current situation.
This document provides a detailed procedure for testing this scope item after solution activation, reflecting the predefined scope of the solution. Each process step, report, or item is covered in its
own section, providing the system interactions (test steps) in a table view. Steps that are not in scope of the process but are needed for testing are marked accordingly. Project-specific steps must be
added.

Note Values in this test script (decimal notation, date formats, and so on) are presented in U.S. standard notation. If your test system is set up to use a different notation, enter values as appropri -
ate.

Situation Handling (31N

Purpose PUBLIC 2
2 Prerequisites

This section summarizes all the prerequisites for conducting the test in terms of systems, users, master data, organizational data, other test data and business conditions.

2.1 System Access

System Details

System Accessible via SAP Fiori launchpad. Your system administrator provides you with the URL to access the various apps assigned to your role.

2.2 Roles
Create business roles using the following business role templates delivered by SAP and assign them to your individual test users.
Alternatively, if available, you can use the following spaces delivered by SAP. You create a space with pages containing predefined essential apps and assign it to the business role. You then assign
this business role to your individual users.
For more information, refer to How to Create a Business Role for the Administrator in the product assistance for SAP S/4HANA Cloud.

Name (Role Template) ID (Role Template) Name (Launchpad Space) ID (Launchpad Space) Log On

Employee SAP_BR_EMPLOYEE Employee SAP_BR_EMPLOYEE

The SAP_BR_EMPLOYEE business role contains the Situation Handling business catalog (SAP_CA_BC_SITN_MYSITUATION_PC).

2.3 Business Conditions

Before this scope item can be tested, the following business conditions must be met.

Scope Item Business Condition

1NJ - Responsibility Must be run before this test script. The required teams and responsibility definitions have to be created that are required for the recipient determination. The current user also needs to be assigned
Management to the team that is assigned to the situation type for this test script. (see also next step, Additional Manual Configuration [page ] 4).

Situation Handling (31N

Purpose PUBLIC 3
2.4 Additional Manual Configuration
Before you can test this scope item, you must have completed the additional configuration steps that are described in the Set-Up Instructions for this scope item. These configuration steps are specific
for your implementation and include mandatory settings that are not delivered by SAP and must be created by you. For more information, refer to the Set-Up Instructions for this scope item on SAP
Best Practices Explorer (https://rapid.sap.com/bp/#/browse/scopeitems/<enter the scope item ID>).

Situation Handling (31N

Purpose PUBLIC 4
3 Overview Table

In this test script, we describe the following process steps in the table below for this scope item:

Note If your system administrator has enabled spaces and pages on the SAP Fiori launchpad, the homepage will only contain the essential apps for performing the typical tasks of a business
role.
You can find all other apps not included on the homepage using the search bar.
If you want to personalize the homepage and include the hidden apps, navigate to your user profile and choose App Finder.

Process Step Business Role App/Transaction Expected Results

My Situations [page ] 6 Employee My Situations (F4154)

My Situations - Extended [page ] 7 Employee My Situations - Extended (F4537)

Situation Handling (31N

Purpose PUBLIC 5
4 Test Procedures

This section describes test procedures for each process step that belongs to this scope item.

4.1 My Situations

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Testing Date:

Tester Name: Duration:

Business Role(s): Responsibility: <State the Service Provider, Customer or Joint Service Provider and Customer>

Purpose

The My Situations (F4154) app is the generic app with which you can view and access all open standard object-based situations that have occurred in the SAP S/4HANA Cloud system. In this
app, you can:
● Close a situation manually.
● Navigate from the situation list entry to the situation object page.

Note You can navigate to the situation object page only if you have the business authorization (business role) required to access the underlying business objects.

For more information, refer to the app description under My Situations.

Prerequisites

● Your user must be defined as responsible for the situation in the Recipients section of the situation type. If you use the Responsibility by Teams option, for example, you need to be a team mem-
ber of the team that is linked there.
● There must be at least one open situation instance. Instances are created in the system only when the required configurations for the situation type are set up as described in the Set-Up Instruc-
tions for this scope item under Create Standard Object-Based Situation Type.

Situation Handling (31N

Purpose PUBLIC 6
Procedure

Test Step Test Step Name Instruction Expected Result Pass / Fail / Com-
# ment

1 Log On Log on to SAP Fiori launchpad as an Em-

ployee

2 Access the App Open the My Situations (F4154) app. You see all the open situations in your area of responsibility.

3 Close the Situation Select a situation from the list, then choose Three statuses are available for closing the situation manually:
Close Situations. 1. Resolved
2. Obsolete
3. Invalid

4 Confirm the Selection Select one of the three options, then choose The status of the situation instance changes and the instance no longer shows up on the list.
Confirm.

5 Navigate to the Corresponding App Select an open situation instance from the Go to the app that corresponds to the affected business object. If you don't have the authorization to go
for the Situation list. to the business object, an error message is displayed.

4.2 My Situations - Extended

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Testing Date:

Tester Name: Duration:

Business Role(s): Responsibility: <State the Service Provider, Customer or Joint Service Provider and Customer>

Purpose

The My Situations - Extended (F4537) app is the generic app with which you can view and access all open extended object-based and message-based situations that have occurred in the SAP S/
4HANA Cloud system. In this app, you can:

Situation Handling (31N

Purpose PUBLIC 7
● Close a situation manually or with the help of proposed callback or navigation actions.
● Navigate from the situation list view to the situation page.
For more information, refer to the app description under My Situations - Extended.

Prerequisites

● Your user must be defined as responsible for the situation in the Recipients section of the situation type. If you use the Responsibility by Teams option, for example, you need to be a team mem-
ber of the team that is linked there.
● There must be at least one open situation instance. Instances are created in the system only when the required configurations for the situation type are set up as described in the Set-Up Instruc-
tions for this scope item under Create Custom Object-Based Situation Type.

Procedure

Test Test Step Name Instruction Expected Result Pass / Fail /

Step # Comment

1 Log On Log on to SAP Fiori launchpad as an Employee

2 Access the App Open the My Situations - Extended (F4537) app. You see all open situations in your area of responsibility.

3 Go to the Situation Page Select the situation instance from the list that was created with the set-up instructions for creating You go to the situation page with the booking details for each
a custom object-based situation type. Then click on the arrow on the right-hand side of the table of the overbookings.
entry.

Note Alternatively, you can go directly to the situation page by clicking on the situation noti-
fication that you've received on SAP Fiori launchpad.

4 Under Solution Proposals, Se- On the Solution Proposals tab, three actions that close the situation are displayed: If you choose any of these options, the proposed action is per-
lect an Action (Alternatively, go ● Cancel Bookings formed and the situation is closed automatically.
to step 5).
● Upgrade Passengers
● Rebook Passengers

5 Under Related Apps, Go to An-
other App
The Related Apps section lets you go to other apps that may help you remove the root cause of a In the My Situations - Extended app, the booking information
situation. is updated accordingly.
In our test case, the Manage Flight Bookings option lets you go to the Situation Handling Demo
app. There, on the Bookings tab, you can remove some of the overbooked economy class book-
ings by choosing the appropriate action:
● Upgrade to business class.

Situation Handling (31N

Purpose PUBLIC 8
 Test Test Step Name Instruction Expected Result Pass / Fail /
Step # Comment

● Change to the next flight for the same connection.

● Cancel the bookings.

Note If you remove all overbooked economy class bookings, the situation is closed automat-
ically. In this case, step 6 is not required.

6 Close the Situation Choose Close Situation. For the remaining overbookings, choose Resolved and con-
Three statuses are available for closing a situation manually: firm your selection.

1. Resolved The status of the situation changes and the situation is no

longer displayed in the overview list of open situations of the
2. Obsolete
My Situations - Extended app.
3. Invalid

Situation Handling (31N

Purpose PUBLIC 9
 Typographic Conventions

Type Style Description

Example Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names,
menu paths, and menu options.
Textual cross-references to other documents.

Example Emphasized words or expressions. www.sap.com/contactsap

EXAMPLE Technical names of system objects. These include report names, program names, transaction codes, table names, and
key concepts of a programming language when they are surrounded by body text, for example, SELECT and IN-
CLUDE.

Example Output on the screen. This includes file and directory names and their paths, messages, names of variables and parame-
ters, source text, and names of installation, upgrade and database tools.

Example Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documenta-
tion.

<Example> Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to
make entries in the system.

EXAMPLE Keys on the keyboard, for example, F 2 or E N T E R .

© 2022 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or
for any purpose without the express permission of SAP SE or an SAP affili-
ate company. The information contained herein may be changed without
prior notice.
Some software products marketed by SAP SE and its distributors contain
proprietary software components of other software vendors. National product
specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for in-
formational purposes only, without representation or warranty of any kind,
and SAP or its affiliated companies shall not be liable for errors or omissions
with respect to the materials. The only warranties for SAP or SAP affiliate
company products and services are those that are set forth in the express war-
ranty statements accompanying such products and services, if any. Nothing
herein should be construed as constituting an additional warranty.
SAP and other SAP products and services mentioned herein as well as their
respective logos are trademarks or registered trademarks of SAP SE (or an
SAP affiliate company) in Germany and other countries. All other product
and service names mentioned are the trademarks of their respective compa-
nies.

See www.sap.com/copyright for additional trademark informa-

Situation Handling (31N tion and notices.
Purpose PUBLIC 10