Professional Documents
Culture Documents
Administration Guide For Intelligent Situation
Administration Guide For Intelligent Situation
2023-05-03
1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2 Technical Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1 Additional Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.2 Internet Connection and Network Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.3 Browsers and Browser Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4 Onboarding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
4.1 Expose Situation Handling APIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
4.2 Configure Destinations on SAP BTP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4.3 Set Up Communication With SAP BTP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4.4 Onboard SAP S/4HANA or SAP S/4HANA Cloud System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
8 Error Handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
This administration guide describes the steps you need to perform as an administrator to set up and run
Intelligent Situation Automation. It covers application-specific information only. For general information, see
SAP Business Technology Platform (BTP).
• System administrators
Before you start using Intelligent Situation Automation, check the requirements and recommendations in this
section.
Note
In addition to SAP S/4HANA Cloud, we now support SAP S/4HANA from 2021 FPS0 onwards.
You need to enable Event Mesh for your SAP BTP subaccount. For more information, see SAP Event Mesh.
For Intelligent Situation Automation, choose Europe (Frankfurt) with the technical key cf-eu10 as the region,
which is provided by AWS (Amazon Web Services) and runs on the SAP BTP, Cloud Foundry environment.
This application supports the standard browsers supported by SAP BTP. For more information, see the related
chapter in the Feature Scope Description for SAP BTP, Cloud Foundry, ABAP, and Kyma Environments.
To access the user interface, subscribe to the Intelligent Situation Automation service with the standard plan.
For more information about the subscription process, see the SAP BTP documentation Subscribe to
Multitenant Applications Using the Cockpit.
Prerequisites
• You have set up your global account. For more information, refer to Managing Global Accounts Using the
Cockpit.
• You are assigned the Administrator role for the global account.
Create a Subaccount
Create a subaccount in the region Europe (Frankfurt) with the technical key cf-eu10. For more information,
refer to Create a Subaccount.
Entitlements
In the case of entitlements for Intelligent Situation Automation, you need to configure them for these
subaccounts. You will find Intelligent Situation Automation as one of these entitlements. For more information,
refer to Managing Entitlements and Quotas Using the Cockpit.
In addition to SAP S/4HANA Cloud, we now support SAP S/4HANA from 2021 FPS0 onwards.
Prerequisite
Onboarding Activities
You need to complete these onboarding activities and subscribe to Intelligent Situation Automation:
• You need to expose Situation Handling APIs. For more information, refer to Expose Situation Handling APIs
[page 6].
• You need to configure destinations on SAP BTP. For more information, refer to Configure Destinations on
SAP BTP [page 7].
• You need to set up communication between an SAP S/4HANA or an SAP S/4HANA Cloud system and SAP
BTP using the SAP Event Mesh service. For more information, refer to Set Up Communication With SAP
BTP [page 7].
• You need to onboard your SAP S/4HANA or SAP S/4HANA Cloud system using the Onboard System
application. For details, refer to Onboard SAP S/4HANA or SAP S/4HANA Cloud System [page 9].
You can access SAP S/4HANA or SAP S/4HANA Cloud situations from an external system by exposing the
corresponding SAP Situation Handling APIs.
A key user needs to create and activate a communication arrangement for a communication scenario.
For Intelligent Situation Automation to access SAP S/4HANA Cloud situations, these communication scenarios
must be configured in the SAP S/4HANA Cloud system:
For more information about creating communication arrangements, refer to Communication Management.
SAP S/4HANA
For SAP S/4HANA systems, the following APIs must be exposed and activated:
For more information, refer to Activate and Maintain Services and Activate OData Services for APIs.
Use the cloud connector to allow access from SAP BTP to your SAP S/4HANA system. For more information,
refer to Cloud Connector.
You need to use the Destinations editor in the SAP BTP cockpit to configure destinations. For more information
about configuring destinations, refer to Create HTTP Destinations.
Create a destination pointing to your SAP S/4HANA or SAP S/4HANA Cloud system with the URL of the
system.
Note
• A single subaccount must be connected to an SAP S/4HANA or an SAP S/4HANA Cloud system.
All configured destinations must be from the same system. If you want to connect to another SAP S/
4HANA or SAP S/4HANA Cloud system, you need to use another subaccount. Or you can unsubscribe
from the service and subscribe again. This time use the destination pointing to the new SAP S/4HANA
or SAP S/4HANA Cloud system.
• The URL of a destination must contain only the base URL of the SAP S/4HANA or SAP S/4HANA
Cloud system.
New situations created are published as events by the Business Event Handling framework. Intelligent Situation
Automation consumes these events by using the SAP Event Mesh service. To enable the exchange of events
across different platforms, you need to create an Event Mesh instance.
Ensure that you have topicRules configured so that it can send a message to the topic saas/isa/cons/*.
Intelligent Situation Automation automatically processes situation events published with this topic.
For more information about creating an Event Mesh service instance, see Create an Event Mesh Service
Instance.
After creating a service instance, you need to create a service key for your Event Mesh service instance. The
service key helps to connect a SAP S/4HANA or SAP S/4HANA Cloud system to your service instance.
To create a service key, open your service instance, and choose Service Keys Create Service Key .
You need to use the service key for your Event Mesh service instance to set up an event channel. While creating
the channel, ensure saas/isa/cons is the Topic Space.
SAP S/4HANA
Refer to Creating Channels Using a Service Key.
In the SAP S/4HANA or SAP S/4HANA Cloud system, bind these topics as the outbound topics for the created
channel:
• sap/s4/beh/businesssituation/v1/BusinessSituation/*
• sap/s4/beh/businesssituationtype/v1/BusinessSituationType/*
SAP S/4HANA
Refer to Maintain Outbound Event Topics.
Access the Onboard System application to onboard an SAP S/4HANA or an SAP S/4HANA Cloud system. You
can also check and edit existing system configurations.
Prerequisite
The SituationAutomationAdminUser role has to be assigned to you. For more information, refer to Assigning
Role Collections to Users [page 11].
Add a System
Posting Instructions
If the onboarding fails, check the reasons by hovering over the information icon on this status. Once the
issues are fixed, choose Retry. If you are unable to onboard your system after several attempts, report an
incident on component CA-SIT-ATM.
Note
2. Choose Save.
This section describes how to configure user management for your application. As a prerequisite, you have
created business users and user groups in your identity provider (IdP). SAP ID service is configured as the
default IdP, but you can also add your instance of SAP Cloud Identity Services - Identity Authentication or a
different IdP.
If you use the Identity Authentication service, you can find more information in the SAP BTP documentation
under Manually Establish Trust and Federation Between UAA and Identity Authentication.
If you use a different IdP, you can find more information under Establish Trust and Federation with UAA Using
Any SAML Identity Provider.
If the role template doesn't have any attributes, then the corresponding roles are identical to the role templates
and are created automatically. If the role template has one or more attributes, you must create roles based on
the role templates and provide the attribute values.
As a prerequisite for assigning roles to IdP users or user groups, you also need to configure role collections.
A role collection consists of one or more roles from one or more applications and can be used to bundle
authorizations within and across applications.
For more information about how to create roles and how to bundle them in role collections using the SAP BTP
cockpit, see Building Roles and Role Collections for Applications.
In the SAP BTP cockpit, you must assign role collections to IdP users or user groups. As a prerequisite, users
and user groups must have been created in the Identity Authentication service or another IdP.
Note
If you use the SAP ID service, you assign role collections to individual users. If you use the Identity
Authentication service or another IdP, you assign them either to individual users or to user groups.
For more information about how to assign role collections to users or user groups using the SAP BTP cockpit,
see Assigning Role Collections to Users or User Groups.
Intelligent Situation Automation uses the standard authentication and authorization procedures provided in
the SAP BTP, Cloud Foundry. For more information, see Authorization and Trust Management in the Cloud
Foundry Environment.
Situations can be resolved automatically either by using standard actions delivered by SAP or custom actions.
(PROC_CONTRACTREADYTOUSE_V3) (SAP_COM_0102)
(MAN_PHYSICAL_INVENTORY_MONITOR) (SAP_COM_0107)
SAP S/4HANA
(PROC_CONTRACTREADYTOUSE_V3)
(MAN_PHYSICAL_INVENTORY_MONITOR)
You can also resolve a situation with a custom action when you create an automation rule. A custom action can
be implemented as a synchronous REST API and a POST request is made with the following payload, which
contains information about the situation data context.
Sample Code
{
"input": {
"dataContext": "<situation data context json>"
}
}
Note
When creating an automation configuration, you can see the payload in the parameter section of the
custom action.
You can export data stored by Intelligent Situation Automation whenever required. To export data, add /
exportdata at the end of the base URL.
If you need support or encounter technical issues while working with Intelligent Situation Automation, you can
contact SAP by reporting an incident for component CA-SIT-ATM. However, before you report an incident take
a look at the following section to too see whether a solution to your error has already been described.
The user has onboarded but is unable to access the app. This leads to an error.
Solution: The user needs the roles listed in Assigning Role Collections to Users [page 11].
The user has configured the rule and triggered automation. Automation was not performed. In the app, the
Resolution Flow on the Situation Instance Details page shows No Action Applied.
Cause: Rule condition might not match the actual data and may have to be enhanced or corrected.
Solution: Correct the rule, and then activate and trigger the situation again with the newest data. Older
situations will not be re-picked. Instead, they’ll be sent back to manual processing.
A situation is triggered and in the app, on the Situation Instance Details page, the Resolution Flow shows No
Automation Configuration Found.
Cause: A situation for situation type X is triggered in the SAP S/4HANA Cloud system. However, no automation
configuration exists in SAP BTP for that corresponding situation type X.
Solution: The user has to create an automation configuration for the corresponding situation type by using the
app in SAP BTP.
Intelligent Situation Automation uses the Audit Log service to save changes to situation automation
configurations and onboarded system. For more information, refer to Audit Log Viewer for the Cloud Foundry
Environment.
Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:
• Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:
• The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
• SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
• Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering an SAP-hosted Web site. By using
such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.
Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.
Bias-Free Language
SAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities,
genders, and abilities.
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 companies.