Can CoreALM replace SAP ChaRM for change management?

Yes. CoreALM enables you to manage SAP transport management directly from your enterprise platform without any dependency on SAP Solution Manager ChaRM. By embedding transport controls natively into ServiceNow, Jira, or Azure DevOps, you eliminate the need for fragmented, legacy change processes.

How can I manage SAP transports directly in ServiceNow with CoreALM?

Our solution embeds custom action buttons (for example, Create TR and Import TR) directly into your ServiceNow change workflow states. This allows authorized users to trigger SAP transport actions without ever leaving the ServiceNow interface.

Does the CoreALM Azure DevOps Integration support SAP transport management?

Yes. It enables SAP developers to create transport requests and attach them directly to Azure DevOps work items. This brings SAP development into the same agile flow as the rest of your enterprise.

Can I link Jira user stories to SAP transports using CoreALM?

Yes. The Jira Integration for SAP Transport Management allows developers to trigger transport creation and status updates directly from within a Jira issue, ensuring full traceability.

Does SAP Cloud ALM replace the need for CoreALM Transport Management?

Not entirely. While SAP Cloud ALM handles requirements and basic deployment orchestration, its current API set has limitations regarding deep transport management integration. It lacks advanced governance functions like sequencing, critical object checks, and automated retrofit. CoreALM covers those gaps with deeper integrations into Jira, Azure DevOps, and SAP transport layers.

How does CoreALM help enforce SAP Clean Core governance?

CoreALM enforces clean core principles by unifying the delivery of S/4HANA and SAP BTP extensions into a single governed process. By linking process design from SAP Signavio to delivery in Jira or Azure DevOps, teams ensure every customization is traceable, compliant, and aligned with business value.

SAP Testing with SAP Solution Manager 7.2 Focus Build

Testing in Focused Build uses the Requirements-based test approach. Work Packages are created from functional specifications and followed adding work items using a Work Breakdown Structure (WBS) representation of the scope for a Work Package. Unit, Single Functional Tests, Functional Integration, and Regression Tests are completed followed by Acceptance Testing to close the loop for Requirements based testing.

Requirements-based Test Approach

With SAP Solution Manager 7.2, Test Suite processes are integrated with in the end to end Focused Build processes. Shown below are the testing activities and deliverables using Focused Build.

Testing Activities and Deliverables using Focused Build

Example of Focused Build Project Structure using the Waterfall Methodology:

Focused Build Project Structure Using Waterfall Methodology

Example of a Focused Build Agile Project Structure with one release per project, two waves and two Sprints per project.

Focused Build Agile Project Structure

Focused Build for SAP Solution Manager supports customers with a seamless, tool-based, requirements-to-deploy process. For this purpose, Focused Build provides pre-configured standard SAP Solution Manager features and processes, as well as additional build functions.