1、1SAP ALM SUMMIT 2025BOOS T YOUR ALM V ALUE!Transitioning change request management to SAP Cloud ALM:best practices for standard use cases2Agenda1How does a standard SAP Solution Manager Change Request Management setup look like?2What is the equivalent in SAP Cloud ALM?3Demo4Wrap-Up&Outlook3How does
2、a standard SAP Solution Manager Change Request Management setup look like?4Restrictions on managed system SAP_CTS_PROJECT can be set as required attribute for specific clients in transaction SE03 This will restrict creation of transports without a SAP CTS Project assigned5 In status Active“all trans
3、port-related activities are allowedContinual Cycle Cycle contains the relevant landscape data6Urgent&Normal Change Workflow Developer creates transport for CTS and implements changes With status switch to”Successfully Tested”the transport requests will be released By handing over to“To Be Tested”a T
4、ransport of Copies(ToC)will be imported to QA7What is the equivalent in SAP Cloud ALM?8Restrictions on managed system Set attribute CALM_CDM_FEATURE_ID as required for specific clients to restrict the release of transport requests on the managed system Only transport requests created from a feature
5、can be released Use Authorization Object S_TRANSPRT Select Request Type TASK Add Activities Add or Create“(01)and Release“(43)9Assign following role collections Deployment Manager Project MemberAssign following role collections Change Manager Project MemberAssign role collection Project Viewer and a
6、 custom role collection containing the following role templates imp_tkm_TaskManager to work with task types and test management imp_cdm_Tester to confirm the successful testAssign following role collections Developer Project Viewer Change Management role concept-SAP Cloud ALM Check out the SAP Help