8.9 KiB
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:
- Navigate to SAP BTP Cockpit
- Go to Security → Users
- Select the affected user
- Assign the required role collection:
- SituationAutomationKeyUser for key users
- SituationAutomationAdminUser for administrators
- User should log out and log in again
- 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:
- Open Analyze Situations app
- Find the affected situation
- Review the Resolution Flow
- Check which rules were evaluated
- Compare rule conditions with actual situation data
Solution:
- Open Manage Situation Automation app
- Find the automation rule for this situation type
- Review and revise the rule conditions
- Update conditions to match expected data patterns
- Deactivate the rule
- Reactivate the rule
- 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:
- Open Manage Situation Automation app
- Check if the situation type appears in the list
- Verify if automation is configured and activated
Solution:
- Open Manage Situation Automation app
- Find the situation type (or add if missing)
- Configure automation:
- Enable automation for the type
- Create rules with conditions
- Assign actions to execute
- Activate the automation configuration
- New situations of this type will now be automated
Onboarding Issues
Connection Test Fails
Symptom: "Check Connection" fails in Onboard System app
Possible Causes:
| Cause | Check |
|---|---|
| Destination URL incorrect | Verify base URL only (no paths) |
| Authentication failure | Check credentials in destination |
| Network connectivity | Verify Cloud Connector (on-premise) |
| APIs not exposed | Confirm SAP_COM_0345/0376 configured |
Solutions:
- Review destination configuration in BTP Cockpit
- Ensure URL contains only base URL
- Verify authentication credentials
- For on-premise: Check Cloud Connector status
- Verify communication arrangements in S/4HANA
Onboarding Status: Failed
Symptom: Onboarding status shows "Failed" after creation
Diagnosis:
- Hover over the info icon next to the failed system
- Read the error details displayed
Common Causes and Solutions:
| Error Detail | Solution |
|---|---|
| Destination not found | Create/correct destination in BTP Cockpit |
| Connection refused | Check network/Cloud Connector |
| Authentication failed | Update credentials in destination |
| API not available | Expose APIs in S/4HANA |
Retry Process:
- Fix the identified issue
- Click Retry on the failed system
- 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:
| Check | Action |
|---|---|
| Event Mesh instance | Verify instance in same subaccount |
| Event channel | Confirm channel created in S/4HANA |
| Topic bindings | Verify BusinessSituation topics bound |
| Topic rules | Check subscribeFilter includes saas/isa/cons/* |
Topic Binding Errors
Symptom: Error when binding topics in S/4HANA
Solution:
- Verify Event Mesh service key is valid
- Confirm topic space is
saas/isa/cons - 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:
| Missing Access | Required Role |
|---|---|
| Operational tiles | SituationAutomationKeyUser |
| Onboard System | SituationAutomationAdminUser |
| Rule authoring | RuleRepositorySuperUser |
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:
- Open Analyze Situations app
- Review Resolution Flow details
- Check error message from action
Common Causes:
| Cause | Solution |
|---|---|
| Target endpoint unreachable | Verify destination and connectivity |
| Authentication failed | Check credentials in action configuration |
| Invalid parameters | Review action parameter mapping |
| Timeout | Increase timeout or optimize action |
Wrong Action Executed
Symptom: Different action executed than expected
Investigation:
- Review all rules for the situation type
- Check rule priorities
- Verify condition logic
Solution:
- Adjust rule conditions for specificity
- Update rule priorities
- 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
- Error message (exact text)
- Application where error occurred
- User experiencing the issue
- Timestamp of occurrence
- Steps to reproduce
- Screenshots if applicable
- Subaccount ID and region
- 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:
- Verify Event Mesh configuration
- Check topic bindings
- 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:
- Create a new subaccount for the new system, or
- 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