SAP Cloud ALM – What’s New in Week 44
SAP Cloud ALM continues to evolve with enhancements that improve data transformation, monitoring capabilities, landscape management, and operational visibility across the platform.
The Week 44 release introduces several improvements to SAP Business Transformation Center, including more flexible transformation cycles, enhanced data quality checks, database usage analysis, and improved migration scope management. RISE with SAP Methodology also introduces more relevant system filtering and updated Clean Core classifications.
Operations expands monitoring capabilities with detailed AI agent session metrics, dynamic thresholds for integration monitoring, SAP Web Dispatcher monitoring, and more flexible security validation checks.
Meanwhile, Implementation improves feature collaboration and workflow integration while expanding library documentation capabilities. Administration introduces greater control over cloud service imports, a new Product Packages overview, and enhanced system registration security.
Together, these updates provide greater flexibility, transparency, and control across SAP Cloud ALM.
SAP Business Transformation Center – Cycle and Monitoring, Data Management, Scoping
New Change Load Phase for Transformation Cycles
SAP Business Transformation Center introduces a new Change Load phase in the Manage Cycles app, providing additional flexibility when migrating data during transformation cycles.
The new phase allows users to migrate tables that were not included when the cycle was originally executed. This provides an additional opportunity to include missing tables without having to incorporate them into the original cycle execution.

As an optional phase, Change Load helps address additional migration requirements identified during the transformation process, providing greater flexibility in managing data migration scope.
TL;DR:
The new Change Load phase allows users to migrate tables that were not included in the original cycle execution, providing greater flexibility during transformation cycles-
Compare Data Quality Check Results with the Data Management Orchestration Agent
SAP Business Transformation Center expands its AI-assisted data management capabilities by introducing the ability to compare results from different quality-check runs using the Data Management Orchestration Agent.
Users can now compare two quality-check runs belonging to the same data assessment to identify differences in data quality between executions. This makes it easier to evaluate whether data quality has improved or whether issues remain after corrective activities.
By comparing assessment results, users can gain better visibility into data quality changes and track progress throughout data preparation activities.
Availability: This capability is currently part of SAP’s Early Adopter Care (EAC) program and is not yet available to users outside the program.
TL;DR:
The Data Management Orchestration Agent can now compare two quality-check runs from the same data assessment, helping users identify data quality changes. Currently available through SAP Early Adopter Care (EAC) only.
Enhanced Database Usage Analysis and Growth Forecasting
SAP Business Transformation Center introduces two new metrics in the Relevancy & Retention tab of the Manage Data Assessment app, providing deeper insights into SAP ECC database usage and future storage requirements.
The new DB Usage Analysis metric provides a detailed breakdown of database size and potential data reduction opportunities. Users can analyze database usage by Application Area, Document Type, and distribution dimensions, such as fiscal year or company code.
The metric also identifies potential archiving and deletion candidates, including information about complexity and retention periods. This helps organizations evaluate which data can be reduced or removed before migrating to SAP S/4HANA.
Additionally, the new Monthly Growth Statistics metric provides visibility into database growth trends over the previous 12 months, including total, used, and free database space.
Based on historical average growth rates, users can configure projections of future database size. Color-coded status indicators highlight when capacity-related actions may be recommended.

Together, these metrics support more informed decisions about data reduction, retention, and database capacity planning, helping organizations prepare their data landscape for SAP S/4HANA transformations.
TL;DR:
New DB Usage Analysis and Monthly Growth Statistics metrics provide insights into SAP ECC database usage, data reduction opportunities, and future storage requirements, supporting more effective transformation planning.
Targeted Data Quality Checks with the New Spotcheck Scope
SAP Business Transformation Center introduces a new Spotcheck scope type for data quality checks, allowing users to validate selected subsets of data instead of evaluating the entire KPI scope.
With Spotcheck, users can focus on specific business areas, such as a company code or fiscal year, to verify data quality improvements or investigate potential issues.
This targeted approach enables faster validation of corrective actions and helps identify data quality problems without requiring a complete KPI evaluation.
To support partial assessments, SAP also introduces a new Unknown data quality status, distinguishing results that have not been fully evaluated from those covered by complete KPI assessments.
Additionally, error counts, trend analysis, and quality indicators have been enhanced to correctly represent Spotcheck results while maintaining the context of previous full-scope evaluations.
These improvements provide greater flexibility in data quality management and support more focused validation activities throughout the transformation process.
TL;DR:
The new Spotcheck scope type enables targeted data quality checks for selected KPI data, supported by an Unknown status and improved reporting that distinguishes partial assessments from full evaluations.
Adjust Migration Scope for Auto-Confirmed Tables
SAP Business Transformation Center introduces additional flexibility in managing migration scope through the Select Scanned Tables app.
Users can now modify the scope of scanned tables with an Auto-confirmed status, allowing them to exclude tables containing data that is no longer required for the migration.
Previously, automatically confirmed tables offered less flexibility for scope adjustments. With this enhancement, users have greater control over which tables remain included in the transformation scope.
This helps organizations refine their migration scope as requirements evolve and avoid transferring unnecessary data to the target system.
TL;DR:
The Select Scanned Tables app now allows scope changes for Auto-confirmed tables, giving users greater control over which data is included in the migration.
RISE with SAP Methodology – Several Apps*, System View
Improved System Filtering in RISE with SAP Methodology
SAP Cloud ALM introduces updated filtering across the RISE with SAP Methodology dashboard, providing a more focused view of relevant systems.
Systems associated with inactive or obsolete Customer ERP IDs are now automatically excluded from all dashboard views. This ensures that the displayed information reflects systems linked to active Customer ERP IDs, reducing unnecessary entries and improving the clarity of system-related analysis.
As a result, users may notice changes in the systems available in selection dialogs compared to previous releases.
This enhancement improves data relevance and dashboard usability, helping users focus on the active systems in their landscape.
TL;DR:
RISE with SAP Methodology now automatically excludes systems linked to inactive or obsolete Customer ERP IDs, providing cleaner dashboard views and more relevant system selections.
Updated Clean Core Classification for SLT Interfaces
SAP Cloud ALM introduces an updated classification for SAP Landscape Transformation Replication Server (SLT) interfaces in the System View.
The SLT interface type has been reclassified from Level D to Level C in the Clean Core Compliance of Interfaces KPI card.
This adjustment reflects the widespread adoption of SLT across customer landscapes and aligns the classification with current usage patterns, following customer feedback and product expert review.
For organizations using SLT replication interfaces, the updated classification may result in improved Clean Core Compliance KPI results, providing a more representative assessment of their integration landscape.

The change affects how SLT interfaces are evaluated within the Clean Core compliance model and does not require changes to the interfaces themselves.
For further details on the classification model, refer to SAP Note 3690029.
TL;DR:
SLT interfaces are now classified as Level C instead of Level D in Clean Core Compliance of Interfaces, potentially improving compliance KPI results for systems using SLT replication.
Implementation – Features, Libraries,
Enhanced Feature Collaboration and Workflow API Integration
SAP Cloud ALM introduces new capabilities in the Features app, improving collaboration and extending workflow integration throughout the feature lifecycle.
Users can now add comments directly to features, providing a way to document discussions, share updates, and communicate relevant information within the feature itself. This helps project teams keep important context connected to development and deployment activities.

Additionally, the Workflow API integration has been extended to support four feature status transitions:
Start Implementation
Handover to Test
Approve for Production
Confirm Deployment
These additional transitions expand the possibilities for integrating feature lifecycle activities with external workflow processes, supporting more consistent coordination between implementation, testing, and deployment.
Together, these enhancements improve feature collaboration and workflow integration, helping teams manage feature-related activities more effectively.
TL;DR:
The Features app now supports comments and extends the Workflow API to four additional feature status transitions, improving collaboration and integration across the feature lifecycle.
Expanded and Reorganized Library Element Types
SAP Cloud ALM introduces improvements to Library element classification, providing a more structured way to document development objects, applications, and interfaces.
For Development elements, element types are now organized into four groups: General, Restful ABAP Programming, Cloud Application Programming, and Legacy. Several new element types have also been introduced, while existing values have been renamed to better reflect their purpose.
For example, BTP App/Extension is now called Extension, and Classes/Interface has been renamed to ABAP Class.
The Function Module and Custom Fiori Application element types have been deprecated. Existing elements using these types remain searchable, but new elements can no longer be created with these values.
For Application elements, a new AI Agent type is available, allowing AI agents to be documented as part of the application landscape.
Interface elements also receive a revised classification structure, with types organized into six groups: Data Replication, Integration, Legacy, Others, Process Integration, and Technology. Additional interface types have been introduced, and the existing File type has been renamed to General File.

These changes make it easier to classify and organize technical landscape elements while providing more consistent terminology across the Libraries application.
TL;DR:
Libraries introduces new and reorganized element types for Development, Application, and Interface elements, including a new AI Agent type and updated classifications for modern development and integration technologies.
Additional Interface Documentation Fields
SAP Cloud ALM enhances the Libraries app with four new fields for Interface elements, enabling more detailed documentation of integration characteristics.
The following fields are now available in the Interface element detail view:
Usage Frequency: Describes how frequently an interface is used and the volume of interface calls.
Usage Schedule: Specifies when data transfers occur or what triggers them.
Data Flow Direction: Defines the direction of information exchange relative to the documented system.
Execution Mode: Describes how communication between systems is technically handled.

These additional attributes provide a more complete description of interface behavior, helping teams better understand integration dependencies and data exchange patterns.
The enhanced documentation can also support integration landscape analysis, transformation planning, and technical assessments by making relevant interface characteristics easier to identify.
TL;DR:
Interface elements in Libraries now include Usage Frequency, Usage Schedule, Data Flow Direction, and Execution Mode, enabling more detailed documentation and analysis of system integrations.
Operations – AI Agent Monitoring, Configuration & Security Analysis – Validation, Health Monitoring, Integration & Exception Monitoring
Enhanced Session Monitoring with Detailed Session Metrics
SAP Cloud ALM expands its AI Agent Monitoring capabilities by introducing additional session metrics, providing greater visibility into AI agent execution and performance.
Users can now access Session Metrics directly in the Session Details view to analyze traces associated with individual sessions.
The available metrics include:
Session Calls: Provides information about calls executed within a session.
LLM Calls: Displays calls made to large language models during session execution.
Agent Details: Provides information about the agent associated with individual trace spans.
Total Time Spent: Shows the execution time of individual calls.
These metrics help users better understand how AI agents process requests, identify time-consuming operations, and investigate potential performance issues.
By providing more detailed execution information, this enhancement improves transparency and troubleshooting capabilities for monitored AI agents.
TL;DR:
AI Agent Monitoring now provides detailed Session Metrics, including session calls, LLM calls, agent details, and execution times, improving visibility into AI agent performance.
Exclude Systems and Services from Validation Checks
SAP Cloud ALM introduces a new Exceptions tab in Configuration & Security Analysis – Validation, providing greater flexibility when configuring validation checks.
Users can now exclude specific services, systems, or items from validation calculations by defining exceptions when creating or editing a check.
This allows organizations to account for situations where certain systems or configuration items should not be included in a particular validation assessment.
Checks containing exceptions are also identifiable within the Configuration & Security Analysis – Validation app, improving transparency into how validation results are calculated.
This enhancement supports more targeted validation configurations and helps ensure that check results reflect the intended monitoring scope.
TL;DR:
The new Exceptions tab in Configuration & Security Analysis – Validation lets users exclude specific services, systems, or items from validation calculations. Check results then reflect the intended monitoring scope.
SAP Web Dispatcher Monitoring Now Available in SAP Cloud ALM
SAP Cloud ALM expands its Health Monitoring capabilities with support for SAP Web Dispatcher, enabling centralized monitoring of Web Dispatcher instances alongside other SAP systems.
Users can now connect SAP Web Dispatcher to SAP Cloud ALM through SAP Host Agent and monitor its operational status and key health indicators directly in the Health Monitoring dashboard.
The integration allows organizations to include Web Dispatcher instances in their existing monitoring landscape, providing better visibility into the health of components responsible for routing and distributing incoming requests.

To enable monitoring, the following setup is required:
SAP Host Agent version 722 PL72 or later must be installed.
The Web Dispatcher instance must be registered using the SAP Cloud ALM service key.
Registration is performed in the SAP Host Agent WebUI under Configuration → SAP Cloud ALM.
Once connected, Web Dispatcher health information becomes available in SAP Cloud ALM, supporting centralized operational monitoring and troubleshooting.
This enhancement extends monitoring coverage to an additional SAP infrastructure component, helping operations teams maintain a more complete view of their system landscape.
TL;DR:
SAP Web Dispatcher can now be monitored in SAP Cloud ALM Health Monitoring through SAP Host Agent, enabling centralized visibility into Web Dispatcher health and operational status.
Dynamic Thresholds for Message Processing Anomaly Detection
SAP Cloud ALM introduces Dynamic Thresholds for anomaly events in Integration & Exception Monitoring, enabling automatic threshold calculation based on historical message processing data.
Instead of relying exclusively on manually configured threshold values, users can now allow SAP Cloud ALM to calculate and periodically adjust thresholds based on historical message counts.

During each evaluation cycle, the current message count is compared against the calculated thresholds. When the message count exceeds or falls outside the expected range, SAP Cloud ALM identifies a potential anomaly and automatically triggers the configured event actions.
The new Threshold Preview section provides visibility into historical message counts and calculated thresholds, allowing users to review how threshold values change over time.
To activate this capability, users can select Dynamic as the Threshold Type in the Parameters section when configuring an anomaly event.
This enhancement helps monitoring configurations adapt to changing message processing patterns, reducing the need for manual threshold adjustments and supporting more effective anomaly detection.
TL;DR:
Integration & Exception Monitoring now supports Dynamic Thresholds for anomaly events, automatically calculating thresholds from historical message counts and triggering configured actions when potential anomalies are detected.
Administration – Landscape Management, Tenant Information
Selective Customer Number Import for Cloud Services
SAP Cloud ALM introduces greater control over cloud service imports in Landscape Management, allowing organizations to select which customer numbers should be included in their SAP Cloud ALM tenant.
For companies managing multiple subsidiaries under a Customer Center of Expertise (CCC), this enhancement helps prevent unnecessary cloud services from being imported.
During the initial S-user configuration, users can now select the customer numbers whose cloud services should be imported. The default SAP Cloud ALM customer number is always included, while additional selections can be managed through Configuration → Imported Customer Numbers.

The new overview provides color-coded status indicators to distinguish between:
Green: Active customer numbers included in the import.
Blue: Customer numbers belonging to the CCC but excluded from the import.
Red: Obsolete customer numbers that are no longer accessible or part of the CCC.
When a customer number is deactivated, its associated cloud services are marked as Obsolete after the next import job and can subsequently be deleted.
SAP Cloud ALM also validates customer number access during daily import jobs. For existing tenants, previously imported customer numbers remain active by default.
This enhancement improves landscape organization and data relevance, particularly for organizations managing multiple SAP customer numbers.
TL;DR:
Landscape Management now supports selective cloud service imports by customer number, helping organizations control which services appear in SAP Cloud ALM and reducing unnecessary landscape entries.
New Product Packages Overview for Cloud Services
SAP Cloud ALM introduces a new Product Packages page in Landscape Management, providing a structured overview of SAP offerings that contain multiple applications and tenants.
The new page organizes imported product packages into a three-level hierarchy, aligned with the structure available in SAP for Me:
Product Package: Represents the purchased package and displays the number of included solutions.
Solution: Shows the individual products within a package, including service type, business type, and customer information. Users can also maintain solution display names and descriptions.
Tenant: Displays the cloud services associated with each solution, including their status, service type, and source, with direct navigation to the corresponding details in Services & Systems.

Product packages and their associated solutions and tenants are imported automatically, eliminating the need for manual configuration.
Additionally, each level includes status event indicators that highlight the most severe active event, such as a disruption, degradation, or maintenance activity. Users can open these indicators to view the related event details.
Frequently accessed product packages and solutions can also be added to the Home page as favorites.
This enhancement improves visibility into complex SAP cloud landscapes by connecting commercial product structures with their associated technical services and operational status.
TL;DR:
The new Product Packages page provides a hierarchical overview of SAP product packages, solutions, and tenants, including automatic imports, operational status indicators, and quick access through favorites.
Enhanced Security Controls for Unknown System Registration
SAP Cloud ALM introduces additional security controls in Landscape Management to manage the registration of previously unknown systems.
By default, only systems already known to Landscape Management can register with an SAP Cloud ALM tenant. This helps prevent unintended registrations when a valid SAP Cloud ALM service key is used by a system that does not belong to the tenant’s managed landscape.
For scenarios where a new system needs to be connected, such as an on-premise ABAP system, administrators can temporarily enable the Allow Registration for unknown systems setting under Registration Settings.

Once enabled, the setting remains active for seven days and is automatically disabled afterward, limiting the period during which unknown systems can register.
Activating this option requires the Landscape Security Administrator role, ensuring that registration permissions are managed by authorized users.
This enhancement provides a balance between secure system onboarding and administrative flexibility, helping organizations control which systems can connect to their SAP Cloud ALM tenant.
TL;DR:
Landscape Management now restricts registration to known systems by default, with a seven-day temporary registration option for unknown systems available to users with the Landscape Security Administrator role.
Tenant Information App Replaced by Self-Monitoring
SAP Cloud ALM has removed the Tenant Information app, consolidating its monitoring capabilities within the Self-Monitoring app.
Users who previously relied on Tenant Information to monitor tenant-related metrics can now access the same information through Self-Monitoring.
This change simplifies the application landscape by providing a centralized location for monitoring SAP Cloud ALM tenant metrics, reducing the need to switch between separate applications.
For more information, refer to the SAP Self-Monitoring documentation.
TL;DR:
The Tenant Information app has been removed, and its monitoring metrics are now available in the Self-Monitoring app.




























































