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 (e.g., 'Create TR', '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. SAP Cloud ALM has limitations regarding deep transport integration. It lacks advanced governance functions like sequencing, critical object checks, and automated retrofit. CoreALM covers those gaps with integrations into Jira, Azure DevOps, and SAP.

How does CoreALM help enforce SAP Clean Core governance?

CoreALM enforces clean core principles by unifying S/4HANA and SAP BTP delivery into a single governed process. It links SAP Signavio to Jira or Azure DevOps so that every customization is traceable and aligned with business value.

SAP Solution Manager Focused Build and Atlassian Jira integration

With Focused Build for SAP Solution Manager, SAP delivers an out-of-the-box, fully integrated, tool-supported processes and methodology to manage requirements and software development in large, agile innovation projects such as SAP S/4HANA implementations for better and faster project execution.

SAP Focused Build and Jira are integrated in the build phase thru a generic OData web service API. This API enables you to connect an external software development tool Atlassian Jira to SAP Focused Build. To keep the API generic, the communication is based on OData web services.

SAP Solution Manager and Jira API pathways

The integration allows development teams to use Jira during the build phase. All other phases of requirement to deploy process remain in SAP Solution Manager, the team leads defines the Requirements in discovery workshops and creates Work Packages and Work Items

Starting point for the integration with Jira is once the architects finished the scoping of the Work Packages. With the status change handover to development the external tool API in Focused Build is triggered and creates Work Packages and Work Items corresponding issues (Epic and User Story) on Jira side.

Once status of the Work Package is set handover to development therefore the development team can start working on their tasks. The Work Packages are synced to Jira as Epic, the Work Item are synced to User Story and have correlation to the Epic. The User Story status will be synced to Focused Build and the Scrum team creates the Tasks for detailed planning.