sap-btp-intelligent-situation-automation

What this skill does

# 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](https://github.com/SAP-docs/btp-intelligent-situation-automation)

**Last Verified**: 2026-05-31

## Table of Contents
- [Overview (For Reference)](#overview-for-reference)
- [When to Use This Skill](#when-to-use-this-skill)
- [Migration Information](#migration-information)
- [Quick Decision Tree](#quick-decision-tree)
- [Supported Systems](#supported-systems)
- [Region & Infrastructure](#region--infrastructure)
- [Core Components](#core-components)
- [Role Templates](#role-templates)
- [Bundled Resources](#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

| System | Version | Notes |
|--------|---------|-------|
| SAP S/4HANA Cloud | Current | Full support |
| SAP S/4HANA | 2021 FPS0+ | On-premise, requires Cloud Connector |

## Region & Infrastructure

| Setting | Value |
|---------|-------|
| **Region** | Europe (Frankfurt) |
| **Technical ID** | cf-eu10 |
| **Provider** | AWS |
| **Environment** | SAP BTP Cloud Foundry |

## Core Components

### Required Services

| Service | Purpose |
|---------|---------|
| Intelligent Situation Automation | Main application (standard plan) |
| SAP Event Mesh | Event communication between S/4HANA and BTP |
| Cloud Connector | On-premise S/4HANA connectivity (optional) |

### Communication Scenarios (SAP S/4HANA Cloud)

| Scenario | Code | Purpose |
|----------|------|---------|
| Business Situation Integration | SAP_COM_0345 | Situation API access |
| Business Situation Master Data Integration | SAP_COM_0376 | Situation type data |
| Enterprise Event Enablement | SAP_COM_0092 | Event channel setup |
| Purchase Requisition Integration | SAP_COM_0102 | Contract ready action |
| Physical Inventory Document Integration | SAP_COM_0107 | Inventory monitoring action |

### APIs (SAP S/4HANA On-Premise)

| API | Purpose |
|-----|---------|
| Business Situation - Read | Read situation data |
| Business Situation Type - Read | Read situation type data |
| Purchase Requisition Integration API | Contract ready action |
| Physical Inventory Document Integration API | Inventory monitoring action |

## Role Templates

| Role | Type | Access |
|------|------|--------|
| SituationAutomationKeyUser | Key User | Full application access |
| SituationAutomationAdminUser | Admin | System onboarding only |
| RuleRepositorySuperUser | Rules | Business rule authoring |

### 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)
```json
{
  "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

| Template | Code | Required Scenario |
|----------|------|-------------------|
| Contract is Ready as Source of Supply | PROC_CONTRACTREADYTOUSE_V3 | SAP_COM_0102 |
| Physical Inventory Monitoring | MAN_PHYSICAL_INVENTORY_MONITOR | SAP_COM_0107 |

### 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 **Servi