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.

Adapting to major authorization changes in SAP Solution Manager 7.2

SAP Solution Manager is a central component for administrative tasks in implementing, operating and upgrading systems in your system landscape. The roles and authorization objects are to help us define what should the user be allowed to execute and see to accomplish their daily tasks.

SAP delivers template roles for your use, they can be used without modification, before modifying authorizations or using SAP template roles, we need to define the roles from a technical as well as functional concept for SAP Solution Manager.

Major Representative Changes came with SAP Solution Manager 7.2. We have a new LaunchPad with groups that replaced the old work centers, in order to access the LaunchPad new role is required for all users (SAP_SM_FIORI_LP_EMBEDDED), in addition specific old roles are required to execute different areas such as (*SMWORK*).

In Solution Manager 7.2 the old SOLAR GUI Documentation is replaced with new Solution Documentation application and the roles for SOLAR01, SOLAR02 are obsolete, all scenarios such as Test Suite, Business Process Operations, Change Request Management, etc. are affected (SAP SOL_PROJ_ADMIN_*, SAP_SOLAR_* and SAP_SM_SOLUTION_* are replaced by SAP_SM_SL_*).

The Solution Documentation Assistant in SAP Solution Manager 7.2 is removed and we have new BPMN Editor integrated for Solution Documentation with the role: SAP_SM_SL_EDIT_BPMN. The roles for Process Management are obsolete (SAP_SOL_BC_COMP, SAP_SOL_TC_COMP and SAP_SOL_RE_COMP)

The roadmap authoring environment is obsolete and the role: SAP:RMDEF_RMAUTH_* are obsolete but we can have the role for display only (SAP_RMMAIN_*).

Maintenance Optimizer is replaced by Maintenance Planner and the roles like SAP_MAINT_OPT_* etc. are obsolete and Maintenance planner is now available on SAP support Launchpad.

We dare say that SAP Solution Manager 7.2 is the biggest upgrade to Solution Manager yet and changes how you interact with it. If you like like to learn more about SAP Solution Manager and how it helps your organization, feel free to reach out to us.