Sap Btp Intelligent Situation Automation

SAP BTP Intelligent Situation Automation

⚠️ DEPRECATION NOTICE

Service Status: ARCHIVED / DEPRECATED as of September 24, 2025

SAP BTP Intelligent Situation Automation service was deprecated on September 24, 2025. Its 6-month end-of-service window reached March 24, 2026; remaining access may exist only where contract commitments still apply.

Immediate Action Required:

• Unsubscribe from the Intelligent Situation Automation service
• Export any required data before access is removed
• Contact component CA-SIT-ATM for questions or concerns

Overview (For Reference)

SAP Intelligent Situation Automation was a BTP service that enabled automatic handling of business situations from SAP S/4HANA and SAP S/4HANA Cloud systems. It leveraged SAP Event Mesh for real-time event communication and allowed organizations to define automated actions for resolving situations.

Documentation Source: https://github.com/SAP-docs/btp-intelligent-situation-automation

Last Verified: 2026-05-31

Table of Contents

• Overview (For Reference)
• When to Use This Skill
• Migration Information
• Quick Decision Tree
• Supported Systems
• Region & Infrastructure
• Core Components
• Role Templates
• Bundled Resources

When to Use This Skill

When to Use This Skill

⚠️ SERVICE DEPRECATED - Use only for:

• Unsubscribing from Intelligent Situation Automation service
• Exporting data before access is removed
• Understanding legacy configurations for documentation purposes
• Migration planning to alternative solutions

Do NOT use this skill for:

• New subscriptions to the service (not available)
• Setting up new automation rules (service deprecated)
• Production deployments (service will be discontinued)

Migration Information

SAP is working towards a GenAI-based capability in the Situation Handling Extended framework. Updates will be provided when available for consumption. For more information, see the SAP community announcement about the deprecation.

Quick Decision Tree

What Task?

Data Export & Unsubscription (DEPRECATED SERVICE)
├─ Export data → references/operations.md#data-export
└─ Unsubscribe → DEPRECATION NOTICE section

Legacy Documentation (For Reference Only)
├─ Understanding existing setup → references/setup-guide.md
├─ API configurations → references/onboarding.md
├─ Role assignments → references/security-roles.md
├─ Automation rules → references/operations.md
└─ Error troubleshooting → references/troubleshooting.md

Migration Planning
├─ Review Situation Handling Extended framework
├─ Contact SAP for migration options
└─ Support component: CA-SIT-ATM

Supported Systems

Region & Infrastructure

Core Components

Required Services

Communication Scenarios (SAP S/4HANA Cloud)

APIs (SAP S/4HANA On-Premise)

Role Templates

Key User Tiles

Key users with SituationAutomationKeyUser role can access:

1. Manage Situation Actions - Create custom actions 2. Manage Situation Automation - Configure automation rules 3. Situation Dashboard - View situation overview 4. Analyze Situations - Analyze resolution flows 5. Delete Data Context - Manage data retention 6. Explore Related Situations - View situation relationships

Event Mesh Configuration

Topic Space

saas/isa/cons

Outbound Event Topics

sap/s4/beh/businesssituation/v1/BusinessSituation/*
sap/s4/beh/businesssituationtype/v1/BusinessSituationType/*

Topic Rules (Service Instance)

{
  "topicRules": {
    "publishFilter": [],
    "subscribeFilter": ["saas/isa/cons/*"]
  }
}

Destination Configuration

Key Constraints

1. Single System Per Subaccount: One subaccount connects to one S/4HANA system only 2. Base URL Only: Destination URL must contain only the base system URL (no paths) 3. Same System Destinations: All destinations in a subaccount must point to the same system

Changing Connected System

To connect to a different S/4HANA system:

• Option A: Create a separate subaccount
• Option B: Unsubscribe and resubscribe with new destination

Onboarding Workflow

Prerequisites

1. Administrator role assigned 2. Event Mesh enabled in subaccount 3. Destination configured to S/4HANA system 4. Communication arrangements created (Cloud) or APIs exposed (On-premise)

Steps

1. Expose Situation Handling APIs (in S/4HANA) 2. Configure Destinations (in BTP Cockpit) 3. Set Up Event Mesh Communication (Event channel + topic bindings) 4. Onboard System (using Onboard System app)

Onboard System App Process

1. Launch Onboard System application 2. Click Add 3. Select destination from list 4. Click Check Connection to verify 5. Enter system name and description 6. Click Create 7. Wait for status: Pending → Successful

Troubleshooting: If onboarding fails, hover over info icon for details. Use Retry after fixing issues.

Automatic Situation Resolution

Supported Situation Templates

Custom Actions

Use the Manage Situation Actions application to create custom actions beyond standard SAP actions.

Data Export

Export all stored data using the endpoint:

[https://<subdomain>.<region>.intelligent-situation-automation.cloud.sap/exportdata](https://<subdomain>.<region>.intelligent-situation-automation.cloud.sap/exportdata)

Audit Logging

Intelligent Situation Automation uses the Audit Log service to track:

• Changes to automation configurations
• System onboarding events

View logs via the Audit Log Viewer in Cloud Foundry.

Unsubscription Instructions

Prerequisites

• Administrator role for the subaccount
• Data export completed (if needed)

Steps to Unsubscribe

1. Open your global account in the SAP BTP cockpit 2. Navigate to your subaccount 3. In the navigation area, choose Services > Instances and Subscriptions 4. Find Intelligent Situation Automation in the subscription list 5. Select the three dots at the end of the subscription row 6. From the menu, select Delete 7. Confirm deletion - all application data will be removed

Support

For any questions or concerns about the deprecation:

• Component: CA-SIT-ATM
• Create an incident via SAP for Me

Common Issues (Legacy)

Reference Files

Detailed Guides Available

1. references/setup-guide.md - Prerequisites, subscription, Event Mesh, network requirements 2. references/onboarding.md - API exposure, destinations, event communication, system onboarding 3. references/security-roles.md - Role templates, collections, user assignment 4. references/operations.md - Automatic resolution, data export, logging 5. references/troubleshooting.md - Error handling, support component 6. references/external-links.md - All SAP documentation links with document IDs

Best Practices

Setup

• ✅ Enable Event Mesh before subscribing to ISA
• ✅ Create Event Mesh instance in same subaccount as ISA subscription
• ✅ Use Europe (Frankfurt) region with cf-eu10

Destinations

• ✅ Use only base URL (no additional paths)
• ✅ One S/4HANA system per subaccount
• ❌ Don't mix destinations to different S/4HANA systems

Communication

• ✅ Set topic space to saas/isa/cons
• ✅ Bind both BusinessSituation and BusinessSituationType topics
• ✅ Use SAP_COM_0092 for cloud event channels

User Management

• ✅ Assign SituationAutomationAdminUser for onboarding tasks
• ✅ Assign SituationAutomationKeyUser for daily operations
• ✅ Add RuleRepositorySuperUser for rule authoring

External Resources

SAP Documentation

• SAP Help Portal: https://help.sap.com/docs/intelligent-situation-automation
• SAP Event Mesh: https://help.sap.com/docs/SAP_EM
• SAP BTP: https://help.sap.com/docs/BTP

Source Repository

• GitHub Docs: https://github.com/SAP-docs/sap-btp-intelligent-situation-automation

Support

• Component: CA-SIT-ATM
• SAP for Me: Incident creation

Updates and Maintenance

⚠️ SERVICE DEPRECATED: No further updates expected as the service is deprecated.

Documentation Source:

• Original: https://github.com/SAP-docs/btp-intelligent-situation-automation
• Deprecation Announcement: https://community.sap.com/t5/technology-blog-posts-by-sap/deprecation-of-intelligent-situation-automation-service/ba-p/14214342

Final Verification: 2025-11-27

Maintenance Status: ARCHIVE ONLY - Skill maintained for historical reference and unsubscription guidance.

Bundled Resources

Reference Documentation

• references/setup-guide.md - Complete setup and configuration guide
• references/onboarding.md - System onboarding and configuration
• references/security-roles.md - Role templates and permissions
• references/operations.md - Operations and monitoring guide
• references/external-links.md - External documentation and SAP notes
• references/troubleshooting.md - Common issues and resolution

---

Skill Version: 1.1.0 Status: ARCHIVED / DEPRECATED Last Updated: 2026-05-31 License: GPL-3.0 Maintainer: SAP Skills Team | https://github.com/secondsky/sap-skills

---

Version History:

• v1.1.0 (2025-11-27): Added deprecation notice and unsubscription instructions
• v1.0.0 (2025-11-22): Initial release for active service

SAP BTP Intelligent Situation Automation Skill

⚠️ SERVICE ARCHIVED / DEPRECATED

Status: Deprecated as of September 24, 2025 End-of-Service Window: Reached March 24, 2026; active contract commitments may extend access

This skill is now archived and maintained only for:

• Data export guidance
• Unsubscription instructions
• Historical reference

Overview (For Reference)

This skill previously provided guidance for implementing situation-based automation between SAP S/4HANA systems and SAP Business Technology Platform.

Auto-Trigger Keywords

This skill activates when discussing:

Service Names

• Intelligent Situation Automation
• ISA
• Situation Automation
• Business Situation Handling

SAP Systems

• SAP S/4HANA Cloud situations
• SAP S/4HANA situations
• S/4HANA business situations
• Situation types
• Situation handling APIs

Communication Scenarios

• SAP_COM_0345
• SAP_COM_0376
• SAP_COM_0092
• SAP_COM_0102
• SAP_COM_0107
• Business Situation Integration
• Business Situation Master Data Integration

BTP Services

• Event Mesh for situations
• Situation event communication
• Business Event Handling
• Event channel for S/4HANA

Applications

• Manage Situation Actions
• Manage Situation Automation
• Situation Dashboard
• Analyze Situations
• Onboard System app
• Delete Data Context
• Explore Related Situations

Roles

• SituationAutomationKeyUser
• SituationAutomationAdminUser
• RuleRepositorySuperUser
• Situation automation roles

Configuration

• Situation destinations
• Situation onboarding
• Situation automation rules
• Automatic situation resolution

Troubleshooting

• CA-SIT-ATM
• Situation automation errors
• No Action Applied
• No Automation Configuration Found

Region/Infrastructure

• cf-eu10 situation automation
• Frankfurt region ISA

Quick Start

⚠️ For Unsubscribing from Deprecated Service

1. Export any required data using the data export endpoint 2. Follow unsubscription instructions in SKILL.md 3. Contact CA-SIT-ATM for support

Legacy Setup Flow (For Reference Only)

1. Enable Event Mesh in subaccount
2. Subscribe to Intelligent Situation Automation (standard plan) - NO LONGER AVAILABLE
3. Configure destinations to S/4HANA system
4. Expose Situation Handling APIs in S/4HANA
5. Set up Event Mesh communication
6. Onboard S/4HANA system
7. Assign user roles
8. Configure automation rules

Coverage

Setup & Subscription

• Prerequisites and region requirements
• Service subscription (standard plan)
• Event Mesh configuration
• Browser and network requirements

System Onboarding

• API exposure for SAP S/4HANA Cloud (SAP_COM_0345, SAP_COM_0376)
• API exposure for SAP S/4HANA on-premise
• Destination configuration
• Event Mesh service instance and keys
• Event channel setup
• Topic bindings
• Onboard System application

User Management

• Role templates (Key User, Admin User)
• Role collections
• User assignment via IdP
• Required role collections for each user type

Operations

• Automatic situation resolution
• Standard vs. custom actions
• Data export
• Audit logging

Troubleshooting

• Common error scenarios
• Resolution steps
• Support component (CA-SIT-ATM)

File Structure

sap-btp-intelligent-situation-automation/
├── SKILL.md                    # Main skill file
├── README.md                   # This file
└── references/
    ├── setup-guide.md          # Prerequisites, subscription, Event Mesh
    ├── onboarding.md           # APIs, destinations, system onboarding
    ├── security-roles.md       # Roles, collections, assignment
    ├── operations.md           # Resolution, export, logging
    ├── troubleshooting.md      # Errors, solutions, support
    └── external-links.md       # All SAP documentation links & IDs

Documentation Sources

• GitHub: https://github.com/SAP-docs/btp-intelligent-situation-automation
• Deprecation Announcement: https://community.sap.com/t5/technology-blog-posts-by-sap/deprecation-of-intelligent-situation-automation-service/ba-p/14214342
• SAP Help: https://help.sap.com/docs/intelligent-situation-automation (archived)
• Event Mesh: https://help.sap.com/docs/SAP_EM

Version

• Skill Version: 1.1.0
• Status: ARCHIVED / DEPRECATED
• Last Updated: 2026-05-31
• Deprecation Date: 2025-09-24
• End-of-Service Window: 2026-03-24; active contract commitments may extend access

License

GPL-3.0 License - See repository LICENSE file.

Contributing

See the main repository CONTRIBUTING guidelines at https://github.com/secondsky/sap-skills.

External Documentation Links - SAP BTP Intelligent Situation Automation

Source: https://github.com/SAP-docs/sap-btp-intelligent-situation-automation/tree/main/docs Purpose: Centralized reference for all SAP documentation links cited in source docs Last Verified: 2025-11-22

---

Overview

This file preserves all external documentation links referenced in the SAP BTP Intelligent Situation Automation documentation. These links enable:

• Direct access to detailed SAP guides
• Easy skill updates when documentation changes
• Comprehensive coverage of all source material

---

SAP Help Portal Document IDs

The source documentation uses SAP Help Portal document IDs (loio* format). These enable direct linking.

Note: IDs marked with † are partial (7-char suffix from filename). Full 32-character IDs can be obtained from SAP Help Portal page source.

Direct Link Formats

Preferred (Direct Access): Use the viewer format for direct document access:

[https://help.sap.com/viewer/{loio_id}/en-US](https://help.sap.com/viewer/{loio_id}/en-US)

Example:

[https://help.sap.com/viewer/loio4832a67a390d42ca9f876a1ded9ea84d/en-US](https://help.sap.com/viewer/loio4832a67a390d42ca9f876a1ded9ea84d/en-US)

Alternative (Search-based): For discovery when exact document ID is uncertain, use search:

[https://help.sap.com/docs/intelligent-situation-automation?locale=en-US&q=loio{ID}](https://help.sap.com/docs/intelligent-situation-automation?locale=en-US&q=loio{ID})

Note: The viewer format provides direct access; the search format may return multiple results.

---

SAP Business Technology Platform (BTP)

Core BTP Documentation

• SAP BTP Overview: https://help.sap.com/docs/BTP
• BTP Cloud Foundry Environment: https://help.sap.com/docs/BTP/65de2977205c403bbc107264b8eccf4b/9c7092c7b7ae4d49bc8ae35fdd0e0b18.html

Subscription & Account Management

Connectivity

Security & Authorization

Monitoring & Logging

Feature Scope Description

---

SAP Event Mesh

---

SAP S/4HANA Cloud

Communication Scenarios

---

SAP S/4HANA (On-Premise)

---

SAP Business Accelerator Hub (API Hub)

---

Intelligent Situation Automation Specific

---

Usage Notes

Updating Links

When SAP documentation changes: 1. Check if document IDs (loio*) are still valid 2. Update specific URLs as needed 3. Test links before committing 4. Update "Last Verified" date

Link Patterns

SAP Help Portal links follow these patterns:

• Product docs: [https://help.sap.com/docs/{PRODUCT}](https://help.sap.com/docs/{PRODUCT}`)
• Viewer format: [https://help.sap.com/viewer/{loio_id}/{locale}](https://help.sap.com/viewer/{loio_id}/{locale}`) (preferred for direct access)
• New format: [https://help.sap.com/docs/{product}/{doc_id}.html](https://help.sap.com/docs/{product}/{doc_id}.html`)

See "Direct Link Formats" section above for usage examples.

---

Document Version: 1.0.0 Last Updated: 2025-11-22

Onboarding Guide - SAP BTP Intelligent Situation Automation

Source: https://github.com/SAP-docs/sap-btp-intelligent-situation-automation/tree/main/docs Last Verified: 2025-11-22

---

Overview

Onboarding connects your SAP S/4HANA or SAP S/4HANA Cloud system to Intelligent Situation Automation on SAP BTP. This enables real-time situation events to flow from S/4HANA to BTP for automated processing.

Prerequisites

• Administrator role assignment
• Intelligent Situation Automation subscription active
• Event Mesh service instance created with service key

---

Onboarding Activities

Four activities must be completed:

1. Expose Situation Handling APIs - Enable API access in S/4HANA 2. Configure Destinations on SAP BTP - Point BTP to your S/4HANA system 3. Set Up Communication With SAP BTP - Configure Event Mesh integration 4. Onboard S/4HANA System - Complete onboarding via application

---

1. Expose Situation Handling APIs

SAP S/4HANA Cloud

Create communication arrangements for these scenarios:

Steps: 1. Log into SAP S/4HANA Cloud 2. Navigate to Communication Management 3. Create communication arrangement for SAP_COM_0345 4. Create communication arrangement for SAP_COM_0376 5. Note the authentication credentials

Reference: See SAP S/4HANA Cloud Communication Management

SAP S/4HANA (On-Premise)

Expose and activate these APIs:

Steps: 1. Log into SAP S/4HANA GUI 2. Enter transaction /IWFND/MAINT_SERVICE 3. Choose Add Service to publish the Business Situation - Read OData service 4. Select the appropriate system alias and activate the service 5. Repeat for Business Situation Type - Read OData service

Additional Requirement: Install and configure SAP Cloud Connector to enable BTP access to on-premise system.

Reference: See Activate and Maintain Services and Activate OData Services for APIs

---

2. Configure Destinations on SAP BTP

Create Destination

1. Open SAP BTP Cockpit 2. Navigate to your subaccount 3. Go to Connectivity → Destinations 4. Click New Destination 5. Configure destination pointing to S/4HANA system

Destination URL Requirements

Critical: The URL must contain only the base URL of the SAP S/4HANA system.

Subaccount Constraints

Important Limitation: A single subaccount must connect to one SAP S/4HANA or SAP S/4HANA Cloud system only.

• All destinations in a subaccount must reference the same S/4HANA system
• You cannot mix destinations to different S/4HANA systems

Connecting to a Different System

If you need to connect to a different S/4HANA system:

---

3. Set Up Communication With SAP BTP

Communication uses the Business Event Handling framework with SAP Event Mesh.

Create Event Mesh Service Instance

Ensure the Event Mesh instance exists in the same subaccount as ISA subscription.

Topic Rules Configuration:

{
  "topicRules": {
    "publishFilter": [],
    "subscribeFilter": ["saas/isa/cons/*"]
  }
}

Create Event Mesh Service Key

1. Open Event Mesh service instance 2. Navigate to Service Keys 3. Click Create Service Key 4. Save credentials for event channel setup

Create Event Channel

SAP S/4HANA Cloud

Use communication scenario SAP_COM_0092 (Enterprise Event Enablement):

1. Create communication arrangement for SAP_COM_0092 2. Use Event Mesh service key credentials 3. Set Topic Space: saas/isa/cons

SAP S/4HANA (On-Premise)

Follow the on-premise event channel creation procedure using Event Mesh service key.

Maintain Outbound Event Topic Bindings

Bind these topics as outbound topics:

SAP S/4HANA Cloud

Use the Maintain Outbound Event Topic Bindings application.

SAP S/4HANA (On-Premise)

Use the on-premise topic binding maintenance procedure.

---

4. Onboard S/4HANA System

Prerequisites

• SituationAutomationAdminUser role assigned
• Destination configured and accessible
• Event channel configured with topic bindings

Using the Onboard System Application

Step 1: Launch Application

• Access the Onboard System application from your BTP subscription

Step 2: Add New System

• Click Add to start adding a new system

Step 3: Select Destination

• Choose the destination from the list that points to your S/4HANA system

Step 4: Test Connection

• Click Check Connection to verify connectivity
• Ensure the test passes before proceeding

Step 5: Enter System Details

• Name: Enter a descriptive system name
• Description: Add system description

Step 6: Create System

• Click Create to initiate onboarding

Step 7: Monitor Progress

• Watch the progress indicator
• Status transitions: Pending → Successful or Failed

Onboarding Status

Troubleshooting Failed Onboarding

If onboarding fails:

1. Hover over info icon to see error details 2. Fix the issue based on error message 3. Click Retry to attempt onboarding again

Common Issues:

• Destination URL incorrect (not base URL only)
• Event channel not configured
• Topic bindings missing
• Authentication credentials invalid

Persistent Failures: After multiple retry attempts, create an incident under component CA-SIT-ATM.

Editing Onboarded System

To modify system details:

1. Click the edit icon next to the onboarded system 2. Update name or description 3. Note: Destination must still point to the same system 4. Click Save

---

Verification Checklist

After onboarding, verify:

• [ ] APIs exposed in S/4HANA (SAP_COM_0345, SAP_COM_0376)
• [ ] Destination configured with base URL only
• [ ] Event Mesh service instance in same subaccount
• [ ] Event channel created with correct topic space
• [ ] Topic bindings for BusinessSituation and BusinessSituationType
• [ ] System shows "Successful" status in Onboard System app

---

Event Flow Diagram

S/4HANA                    Event Mesh                BTP (ISA)
   │                           │                        │
   │ Business Situation Event  │                        │
   ├──────────────────────────►│                        │
   │                           │ saas/isa/cons/*        │
   │                           ├───────────────────────►│
   │                           │                        │
   │                           │                        │ Process Situation
   │                           │                        │ Execute Actions
   │                           │                        │

---

External Resources

For a complete list of SAP documentation links and document IDs, see references/external-links.md.

Key resources:

• Cloud Connector: https://help.sap.com/docs/connectivity/sap-btp-connectivity-cf
• Event Mesh: https://help.sap.com/docs/SAP_EM

---

Document Version: 1.0.0 Last Updated: 2025-11-22

Operations Guide - SAP BTP Intelligent Situation Automation

Source: https://github.com/SAP-docs/sap-btp-intelligent-situation-automation/tree/main/docs Last Verified: 2025-11-22

---

Overview

This guide covers operational aspects of Intelligent Situation Automation including automatic situation resolution, data export, and audit logging.

---

Automatic Situation Resolution

How It Works

Situations can be resolved automatically using: 1. Standard SAP Actions - Pre-built actions for specific situation templates 2. Custom Actions - User-defined actions created in Manage Situation Actions

Manage Situation Actions Application

Use this application to:

• View available standard actions
• Create custom actions
• Configure action parameters
• Test action execution

---

Standard SAP Actions

Supported Situation Templates

Required Communication Scenarios

SAP S/4HANA Cloud

SAP S/4HANA (On-Premise)

Configuring Standard Actions

1. Open Manage Situation Automation app 2. Select the situation type 3. Enable automation for the situation 4. Configure the standard action 5. Set conditions (optional) 6. Activate the automation

---

Custom Actions

Creating Custom Actions

1. Open Manage Situation Actions app 2. Click Create 3. Define action properties:

• Name and description
• Action type
• Target endpoint
• Parameters

4. Save and activate

Action Configuration Options

---

Manage Situation Automation Application

Purpose

Configure which situations are automated and how they are resolved.

Key Functions

Creating Automation Rules

1. Select a situation type 2. Define rule conditions based on situation data 3. Assign action to execute when conditions match 4. Set priority if multiple rules exist 5. Activate the rule

---

Situation Dashboard

Purpose

Monitor situation status and automation performance.

Available Views

---

Analyze Situations Application

Purpose

Deep analysis of individual situations and resolution flows.

Resolution Flow

The Resolution Flow shows the complete processing history:

• When situation was received
• Which rules were evaluated
• What action was applied
• Resolution outcome

Status Indicators

---

Data Export

Purpose

Export all data stored by Intelligent Situation Automation.

Export Endpoint

[https://<subdomain>.<region>.intelligent-situation-automation.cloud.sap/exportdata](https://<subdomain>.<region>.intelligent-situation-automation.cloud.sap/exportdata)

URL Components

Example

[https://mycompany-dev.eu10.intelligent-situation-automation.cloud.sap/exportdata](https://mycompany-dev.eu10.intelligent-situation-automation.cloud.sap/exportdata)

Export Content

The export includes:

• Situation records
• Automation configurations
• Resolution history
• System onboarding data

---

Audit Logging

Audit Log Service

Intelligent Situation Automation uses the SAP BTP Audit Log service to track changes.

Logged Events

Viewing Audit Logs

Access logs through the Audit Log Viewer in Cloud Foundry environment:

1. Navigate to BTP Cockpit 2. Go to your subaccount 3. Open Audit Log Viewer service 4. Filter by application or time range 5. Review logged events

Reference: SAP Help documentation for Audit Log Viewer for Cloud Foundry Environment

---

Delete Data Context Application

Purpose

Manage data retention and cleanup of situation data.

Available Functions

Data Retention Considerations

• Review data retention policies before deletion
• Deleted data cannot be recovered
• Audit logs may retain references

---

Explore Related Situations Application

Purpose

Discover relationships between situations.

Relationship Types

Use Cases

• Identify patterns across situations
• Find root causes
• Optimize automation rules

---

Operational Best Practices

Monitoring

• ✅ Regularly review Situation Dashboard
• ✅ Check for failed automations
• ✅ Monitor resolution rates
• ✅ Track automation performance trends

Rules Management

• ✅ Start with simple rules
• ✅ Test rules before production activation
• ✅ Document rule logic
• ✅ Review and optimize regularly

Data Management

• ✅ Export data periodically for backup
• ✅ Implement data retention policies
• ✅ Review audit logs for compliance

Troubleshooting

• ✅ Use Analyze Situations for detailed investigation
• ✅ Check Resolution Flow for specific situations
• ✅ Verify rule conditions match actual data

---

External Links

• Audit Log Viewer: https://help.sap.com/docs/BTP/65de2977205c403bbc107264b8eccf4b/
• Data Protection: https://help.sap.com/docs/btp/sap-business-technology-platform/data-protection-and-privacy
• Business Rules: https://help.sap.com/docs/business-rules

---

Document Version: 1.0.0 Last Updated: 2025-11-22

Security and Roles Guide - SAP BTP Intelligent Situation Automation

Source: https://github.com/SAP-docs/sap-btp-intelligent-situation-automation/tree/main/docs Last Verified: 2025-11-22

---

Overview

Intelligent Situation Automation uses role-based access control through SAP BTP role templates and role collections. Users must be assigned appropriate role collections to access application features.

---

Role Templates

Intelligent Situation Automation provides two role templates:

Note: Since these templates have no attributes, corresponding roles are created automatically. Templates with attributes require manual role creation with specified attribute values.

---

SituationAutomationKeyUser

Purpose

Key user access for managing situation automation on a daily basis.

Access Level

Full application access including all operational tiles.

Available Tiles

Typical Users

• Business process owners
• Operations managers
• Situation analysts
• Automation administrators

---

SituationAutomationAdminUser

Purpose

Admin access for system onboarding and technical configuration.

Access Level

Limited to system onboarding tasks only.

Available Functions

Typical Users

• System administrators
• Technical architects
• Initial setup personnel

---

RuleRepositorySuperUser

Purpose

Business rules management for authoring automation rules.

Origin

This role comes from SAP Business Rules service, not Intelligent Situation Automation.

Requirement

Key users who need to author rules must have both:

• SituationAutomationKeyUser
• RuleRepositorySuperUser

---

Role Collections

What Are Role Collections?

Role collections bundle one or more roles from one or more applications. They provide a convenient way to assign multiple permissions at once.

Creating Role Collections

1. Navigate to SAP BTP Cockpit 2. Go to your subaccount 3. Navigate to Security → Role Collections 4. Click Create 5. Enter name and description 6. Add roles from role templates

Recommended Role Collections

*Example names; customize based on your organization's naming conventions.

Reference: See Building Roles and Role Collections for Applications

---

Assigning Role Collections to Users

Prerequisites

Users must exist in one of:

• SAP ID service
• Identity Authentication service (IAS)
• Another configured identity provider (IdP)

Assignment Methods

Individual User Assignment

1. Navigate to SAP BTP Cockpit 2. Go to your subaccount 3. Navigate to Security → Users 4. Select the user 5. Click Assign Role Collection 6. Select appropriate role collection 7. Confirm assignment

User Group Assignment (IAS/Custom IdP)

1. Navigate to SAP BTP Cockpit 2. Go to your subaccount 3. Navigate to Security → Role Collections 4. Select the role collection 5. Go to User Groups tab 6. Add user group from IdP 7. All users in group receive the role collection

---

Required Role Collections by User Type

For Key Users (Daily Operations)

For Admin Users (Setup Only)

---

Trust and Federation

Identity Provider Configuration

For detailed guidance on configuring trust with identity providers, see SAP BTP documentation for Trust and Federation with Identity Providers.

Common Configurations

---

Authorization Flow

User Login
    │
    ▼
Identity Provider
    │
    ▼
BTP Authentication
    │
    ▼
Role Collection Check
    │
    ├─── SituationAutomationKeyUser ───► Access operational tiles
    │
    └─── SituationAutomationAdminUser ──► Access onboarding only

---

Best Practices

Role Assignment

• ✅ Create dedicated role collections for your organization
• ✅ Use descriptive names for role collections
• ✅ Document which users/groups have which roles
• ✅ Assign minimum necessary roles (least privilege)
• ✅ Use group-based assignment when possible (with IAS)

Security

• ✅ Review role assignments regularly
• ✅ Remove roles when users change responsibilities
• ✅ Separate admin and key user roles
• ✅ Track changes via audit logs

Common Mistakes

• ❌ Assigning SituationAutomationAdminUser to all users
• ❌ Forgetting RuleRepositorySuperUser for rule authors
• ❌ Not removing roles when users leave
• ❌ Over-permissioning for convenience

---

Troubleshooting Access Issues

"Server Error" on Application Access

Symptom: Error message when accessing Manage Situation Automation app

Cause: User not assigned required role collection

Solution: Assign SituationAutomationKeyUser role collection to the user

Cannot Access Onboard System

Symptom: Onboard System app not visible or accessible

Cause: Missing admin role

Solution: Assign SituationAutomationAdminUser role collection

Cannot Create/Edit Rules

Symptom: Rule authoring functions unavailable

Cause: Missing rule repository role

Solution: Assign RuleRepositorySuperUser role collection in addition to SituationAutomationKeyUser

---

External Links

For a comprehensive list of SAP documentation links with document IDs, see references/external-links.md.

Key resources for role and security management:

• Building Roles and Role Collections: https://help.sap.com/docs/BTP/65de2977205c403bbc107264b8eccf4b/eaa6a26291914b348e875a00b6beb729.html
• Trust Configuration: https://help.sap.com/docs/BTP/65de2977205c403bbc107264b8eccf4b/cb1bc8f1bd5c482e891063960d7acd78.html
• Authorization Management: https://help.sap.com/viewer/65de2977205c403bbc107264b8eccf4b/Cloud/en-US/6373bb7a96114d619bfdfdc6f505d1b9.html

---

Document Version: 1.0.0 Last Updated: 2025-11-22

Setup Guide - SAP BTP Intelligent Situation Automation

Source: https://github.com/SAP-docs/sap-btp-intelligent-situation-automation/tree/main/docs Last Verified: 2025-11-22

---

Technical Prerequisites

Supported SAP Systems

Administrator Requirements

You must have administrator role assignments for:

• SAP BTP global account
• SAP BTP subaccount (for subscription)
• SAP S/4HANA system (for API configuration)

---

Additional Services

Event Mesh Requirement

Critical: You must enable Event Mesh for your SAP BTP subaccount before subscribing to Intelligent Situation Automation.

Event Mesh enables:

• Real-time event communication between S/4HANA and BTP
• Business situation event publishing
• Situation type synchronization

Documentation: https://help.sap.com/docs/SAP_EM

Event Mesh Service Instance

Create the Event Mesh instance in the same subaccount where you subscribe to Intelligent Situation Automation.

---

Network Requirements

Region Selection

Documentation: See SAP Help for available regions and hosts.

Internet Connectivity

Ensure network access to:

• SAP BTP Cloud Foundry endpoints
• SAP Event Mesh endpoints
• Your S/4HANA system (via Cloud Connector for on-premise)

---

Browser Support

Intelligent Situation Automation supports the standard browsers supported by SAP BTP.

Reference: Feature Scope Description for SAP BTP, Cloud Foundry, ABAP, and Kyma Environments (PDF)

Consult the FSD document for specific browser versions and settings.

---

Subscription Process

Prerequisites Checklist

Before subscribing, ensure:

• [ ] Global account configured
• [ ] Administrator role assigned for global account
• [ ] Subaccount created in cf-eu10 region
• [ ] Event Mesh enabled in subaccount

Step 1: Create Subaccount

Create a new subaccount with these settings:

Step 2: Configure Entitlements

1. Navigate to your global account in BTP Cockpit 2. Go to Entitlements → Subaccount Assignments 3. Select your subaccount 4. Add entitlement for Intelligent Situation Automation 5. Select the standard plan

Step 3: Subscribe to Service

1. Navigate to your subaccount 2. Go to Services → Service Marketplace 3. Find Intelligent Situation Automation 4. Click Create 5. Select standard plan 6. Complete the subscription

Subscription Plans

---

Event Mesh Configuration

Create Service Instance

1. Navigate to your subaccount 2. Go to Services → Instances and Subscriptions 3. Click Create 4. Select Event Mesh 5. Configure topic rules:

{
  "topicRules": {
    "publishFilter": [],
    "subscribeFilter": ["saas/isa/cons/*"]
  }
}

Create Service Key

After creating the service instance:

1. Open the Event Mesh service instance 2. Go to Service Keys 3. Click Create Service Key 4. Save the credentials for S/4HANA configuration

The service key credentials are needed to:

• Create the event channel in S/4HANA
• Configure SAP_COM_0092 communication scenario

---

Post-Subscription Steps

After successful subscription:

1. Assign Roles: Grant SituationAutomationAdminUser to administrators 2. Configure Destinations: Create destination to your S/4HANA system 3. Expose APIs: Configure communication arrangements in S/4HANA 4. Set Up Event Communication: Create event channel and topic bindings 5. Onboard System: Use Onboard System app to complete setup

See references/onboarding.md for detailed onboarding steps.

---

Verification Checklist

After setup, verify:

• [ ] Subscription status shows "Subscribed"
• [ ] Event Mesh instance created in same subaccount
• [ ] Event Mesh service key generated
• [ ] Subaccount region is cf-eu10
• [ ] Administrator roles assigned

---

Troubleshooting Setup Issues

Subscription Fails

Possible Causes:

• Missing entitlements
• Wrong region selected
• Quota exceeded

Resolution: 1. Verify entitlements are assigned to subaccount 2. Ensure subaccount is in cf-eu10 region 3. Check quota limits

Event Mesh Instance Creation Fails

Possible Causes:

• Event Mesh not entitled
• Topic rules syntax error

Resolution: 1. Add Event Mesh entitlement 2. Verify JSON syntax in topic rules

---

External Links

• SAP BTP Documentation: https://help.sap.com/docs/BTP
• Event Mesh Documentation: https://help.sap.com/docs/SAP_EM
• Subscription Guide: https://help.sap.com/docs/BTP/65de2977205c403bbc107264b8eccf4b/7a3e39622be14413b2a4df7c02ca1170.html

---

Document Version: 1.0.0 Last Updated: 2025-11-22

Troubleshooting Guide - SAP BTP Intelligent Situation Automation

Source: https://github.com/SAP-docs/sap-btp-intelligent-situation-automation/tree/main/docs Last Verified: 2025-11-22

---

Overview

This guide covers common errors, their causes, and solutions for Intelligent Situation Automation. For issues not covered here, create an incident with SAP Support.

---

Support Component

Component: CA-SIT-ATM

Use this component when:

• Creating support incidents
• Escalating unresolved issues
• Reporting bugs or defects

---

Known Errors and Solutions

Error 1: Server Error on Application Access

Symptom:

"A server error has occurred. Please try again later"

This error appears when accessing the Manage Situation Automation app after onboarding.

Root Cause: User lacks required authorization.

Solution: 1. Navigate to SAP BTP Cockpit 2. Go to Security → Users 3. Select the affected user 4. Assign the required role collection:

• SituationAutomationKeyUser for key users
• SituationAutomationAdminUser for administrators

5. User should log out and log in again 6. Retry accessing the application

Reference: See references/security-roles.md for role assignment details.

---

Error 2: No Action Applied

Symptom: Resolution Flow in Analyze Situations app shows "No Action Applied"

Location: Analyze Situations app → Select situation → Resolution Flow

Root Cause: Rule conditions do not match the actual situation data.

Investigation Steps: 1. Open Analyze Situations app 2. Find the affected situation 3. Review the Resolution Flow 4. Check which rules were evaluated 5. Compare rule conditions with actual situation data

Solution: 1. Open Manage Situation Automation app 2. Find the automation rule for this situation type 3. Review and revise the rule conditions 4. Update conditions to match expected data patterns 5. Deactivate the rule 6. Reactivate the rule 7. Trigger automation again with current data

Important Note: After revising a rule, previously processed situations with "No Action Applied" status will remain in manual processing queue. Only new situations will be evaluated against the updated rule.

---

Error 3: No Automation Configuration Found

Symptom: Resolution Flow shows "No Automation Configuration Found"

Location: Analyze Situations app → Select situation → Resolution Flow

Root Cause: No automation configuration exists in SAP BTP for the triggered situation type.

Investigation Steps: 1. Open Manage Situation Automation app 2. Check if the situation type appears in the list 3. Verify if automation is configured and activated

Solution: 1. Open Manage Situation Automation app 2. Find the situation type (or add if missing) 3. Configure automation:

• Enable automation for the type
• Create rules with conditions
• Assign actions to execute

4. Activate the automation configuration 5. New situations of this type will now be automated

---

Onboarding Issues

Connection Test Fails

Symptom: "Check Connection" fails in Onboard System app

Possible Causes:

Solutions: 1. Review destination configuration in BTP Cockpit 2. Ensure URL contains only base URL 3. Verify authentication credentials 4. For on-premise: Check Cloud Connector status 5. Verify communication arrangements in S/4HANA

Onboarding Status: Failed

Symptom: Onboarding status shows "Failed" after creation

Diagnosis: 1. Hover over the info icon next to the failed system 2. Read the error details displayed

Common Causes and Solutions:

Retry Process: 1. Fix the identified issue 2. Click Retry on the failed system 3. Monitor for success

Persistent Failures: After multiple retry attempts, create incident with component CA-SIT-ATM.

---

Event Mesh Issues

Events Not Received

Symptom: Situations not appearing in ISA despite being created in S/4HANA

Check List:

Topic Binding Errors

Symptom: Error when binding topics in S/4HANA

Solution: 1. Verify Event Mesh service key is valid 2. Confirm topic space is saas/isa/cons 3. Check correct topic patterns:

• sap/s4/beh/businesssituation/v1/BusinessSituation/*
• sap/s4/beh/businesssituationtype/v1/BusinessSituationType/*

---

Role and Access Issues

Missing Tiles/Apps

Symptom: Some tiles not visible in launchpad

Cause: Missing role collection assignment

Solution: Assign appropriate role collection:

Cannot Edit Rules

Symptom: Rule editing functions disabled

Cause: Missing RuleRepositorySuperUser role

Solution: Add RuleRepositorySuperUser role collection to user

---

Automation Execution Issues

Action Execution Failed

Symptom: Resolution Flow shows failed action

Investigation: 1. Open Analyze Situations app 2. Review Resolution Flow details 3. Check error message from action

Common Causes:

Wrong Action Executed

Symptom: Different action executed than expected

Investigation: 1. Review all rules for the situation type 2. Check rule priorities 3. Verify condition logic

Solution: 1. Adjust rule conditions for specificity 2. Update rule priorities 3. Test with sample situation

---

Diagnostic Tools

Analyze Situations App

Use for detailed situation analysis:

• Resolution Flow visualization
• Rule evaluation history
• Action execution details

Audit Log Viewer

Use for tracking changes:

• Configuration modifications
• System onboarding events
• User actions

Situation Dashboard

Use for monitoring:

• Overall automation status
• Resolution rates
• Trend analysis

---

Troubleshooting Checklist

Before Contacting Support

• [ ] Verified user has required role collections
• [ ] Checked Resolution Flow in Analyze Situations
• [ ] Reviewed destination configuration
• [ ] Confirmed Event Mesh connectivity
• [ ] Checked audit logs for errors
• [ ] Attempted retry/reconfiguration
• [ ] Documented steps to reproduce

Information to Include in Incident

1. Error message (exact text) 2. Application where error occurred 3. User experiencing the issue 4. Timestamp of occurrence 5. Steps to reproduce 6. Screenshots if applicable 7. Subaccount ID and region 8. S/4HANA system details

---

FAQ

Q: How long before situations appear after onboarding?

A: Situations should appear within minutes after successful onboarding and proper event channel configuration. If not: 1. Verify Event Mesh configuration 2. Check topic bindings 3. Create a test situation in S/4HANA to verify flow

Q: Can I connect multiple S/4HANA systems to one subaccount?

A: No. Each subaccount can connect to only one S/4HANA system. Use separate subaccounts for different systems.

Q: How do I change the connected S/4HANA system?

A: Either: 1. Create a new subaccount for the new system, or 2. Unsubscribe from ISA and resubscribe with new destination

Q: Why are old situations not processed by new rules?

A: Rules only apply to new situations. Situations processed before rule changes retain their original status.

---

External Links

• SAP for Me: https://me.sap.com/ (incident creation)
• SAP Community: https://community.sap.com/
• SAP Help: https://help.sap.com/docs/intelligent-situation-automation

---

Document Version: 1.0.0 Last Updated: 2025-11-22