Lesson 1 of 6
Operations after Solution Manager
10 min
Listen to this lesson
Course sap-alm-205 introduced SAP Cloud ALM monitoring for delivery teams; sap-alm-302 planned the move off Solution Manager. This course is for the people who will run production with it: Basis, integration and release teams, and the test leads who rely on their data. It starts with a date that matters more for run teams than for anyone else.
Why run teams have the earliest deadline
SAP's Solution Manager page states that mainstream maintenance for SAP Solution Manager 7.2 runs until the end of 2027. Customers who take extended maintenance for SAP Business Suite 7 receive extended maintenance for Solution Manager 7.2 until the end of 2030 at no extra cost, but only for requirements management, project management, process management, the test suite, change control, IT service management and landscape management. Monitoring is not on that list. Technical monitoring, interface monitoring, job monitoring and business process monitoring in Solution Manager therefore have a 2027 clock even for customers with extended maintenance. SAP recommends moving to SAP Cloud ALM before the end of 2027.
From Solution Manager to SAP Cloud ALM
| Solution Manager 7.2 capability | SAP Cloud ALM for Operations | Note |
|---|---|---|
| Technical monitoring (system monitoring) | Health Monitoring | Focused Run System Monitoring for full-featured needs |
| Interface and connection monitoring, PI monitoring, message flow monitoring | Integration & Exception Monitoring | Covers cloud services and ABAP and Java on-premise |
| Job monitoring | Job & Automation Monitoring | Adds cloud schedulers and automation services |
| Business process monitoring | Business Process Monitoring | KPIs per process; custom KPIs possible |
| End-user experience monitoring | Synthetic User Monitoring, Real User Monitoring | Scripted checks and real user request data |
| Configuration validation | Configuration & Security Analysis | Compare configuration across systems |
| Guided procedures, alert reactions | Operations Automation, Intelligent Event Processing | Operation flows can run automatically on events |
| Monitoring and alerting infrastructure, alert inbox | Intelligent Event Processing, alert inbox and Notification Management | Events, alerts, emails, tickets |
Capability mapping for operations. Check SAP's transition guidance per scenario for your landscape.
Contoso's monitored landscape
Data collection always starts in Landscape Management, where each system or cloud service is registered and connected to the tenant. ABAP systems push data through the ST-PI and, for business process monitoring, ST-A/PI add-ons, with SAP Notes listed per use case on SAP's expert portal; cloud services such as Cloud Integration are connected with endpoints and credentials from their BTP subaccount. Only then can each monitoring app switch on collection for that system.
- Register CMP, CMR, the Cloud Integration tenant and the BTP subaccount in Landscape Management.
- Bring ST-PI and ST-A/PI on CMP and CMR to the levels each use case requires and apply the listed notes (lessons 2 to 4).
- Define business services, for example "Order to cash, US", that group the systems and interfaces a process depends on.
- Switch on data collection per app and per category, with filters, starting with production.
- Define events and their reactions: who is alerted, by which channel, for what.
| Person | Primary apps | Typical question |
|---|---|---|
| Sam, Basis lead | Health Monitoring, Job & Automation Monitoring, Landscape Management | Are the systems and the nightly batch healthy? |
| Theo, integration lead | Integration & Exception Monitoring | Did Great Lakes and Lakeside messages flow and post? |
| Luis, release manager | Business Service Management, maintenance windows | Is the release window open or closed, and what did it affect? |
| Maria (O2C key user) and Dan (finance process owner) | Business Process Monitoring | Are orders, deliveries and invoices flowing? |
| Priya and Ravi, testing | All of the above, read-only, plus synthetic checks | What fails in production that our tests missed? |
Who uses which operations app at Contoso.
What would you do?
Contoso's ECC run team says it can keep using Solution Manager interface and job monitoring for the read-only ECC copy until 2030, because Contoso pays for extended maintenance on other Business Suite 7 products. What is the accurate position?
- Solution Manager 7.2 mainstream maintenance ends at the end of 2027; extended maintenance does not cover monitoring.
- SAP Cloud ALM for Operations has an app for each monitoring scenario, plus events, alerts and operation flows.
- Everything starts in Landscape Management; ABAP systems need ST-PI (and ST-A/PI for process monitoring).
- Set up and test monitoring in pre-production, not only in production.
Check your understanding · not graded
Lesson check
1. Why do monitoring functions have a 2027 clock even with extended maintenance?
2. Where does every SAP Cloud ALM operations setup begin?
3. Which Cloud ALM app replaces Solution Manager interface monitoring?
4. Why set up monitoring in CMR as well as production?