Explore your Enhancements and Extensions with SAP Readiness Check for SAP Cloud ALM

[astridtschense]

Note: The following blog describes the new Enhancements & Extensions functionality available within SAP Readiness Check for SAP Cloud ALM. For an overview of the other checks available in SAP Readiness Check for SAP Cloud ALM, refer to this blog.  

Dear All, 

Today, we are excited to announce that the SAP Readiness Check for SAP Cloud ALM now incorporates one additional check to provide details about the custom objects and customizing within the SAP Solution Manager system. 

All these details are summarized in a new check called Enhancements & Extensions, which will support your transition project in the decision to eventually decommission your SAP Solution Manager system landscape, and also to identify any custom modifications or enhancements to Application Lifecycle Management processes.  

Knowing which custom objects or customizations exist is important to evaluate the impact and additional efforts to move all required functionality to SAP Cloud ALM. Moreover, if you find that your system and ALM processes run close to the standard, you can start planning the move to SAP Cloud ALM directly using the other checks of the SAP Readiness Check analysis. 

Enhancements & Extensions – Custom Objects 

In the custom objects section of the new check, you will find the objects created in a customer namespace. These objects can represent an enhancement or extension to a standard process in SAP Solution Manager, or a completely new application running in the same system. If the check identified enhancements, you can evaluate if such modifications are still needed when you move your processes to SAP Cloud ALM, or if they are covered by the standard extensibility options offered in SAP Business Technology Platform and SAP Cloud ALM APIs. Additionally, after your transition to SAP Cloud ALM is complete, you might consider decommissioning your SAP Solution Manager system landscape. The custom objects results and the Add-Ons details will help you identify the impact on other processes running in the system.  

The custom objects section contains the following tables describing different types of custom enhancements:

• ABAP Enhancements: lists programs, transactions, and classes that exist in a customer namespace.
• Custom Tables: lists custom-created tables and the number of records.
• Custom Application Enhancement Fields (AET): lists custom-created fields in CRM WebUI applications, typically done to create enhancements in the area of Incident and Change Request Management.
• BSP Enhancements: lists enhancements to Business Server Pages application logic, typically representing enhancements or extensions in the area where BSPs are used, such as Incident and Change Request Management.

Enhancements & Extensions – Add-Ons

The Add-on section helps identify the installed add-ons and their vendor in the SAP Solution Manager system. Use this information to determine the impact of decommissioning your SAP Solution Manager system landscape.

Enhancements & Extensions – Change Request Management

The Change Request Management section provides details about the customizing related to specific Application Lifecycle Management processes, highlighting whether such enhancements exist in Change Request Management and what is no longer equal to standard. Generally, if only a few modifications are identified, it suggests that the transition of your Change and Request Manager should be smooth, and the capabilities in SAP Cloud ALM are likely sufficient. You can supplement this analysis and confirm if the capabilities you use are available in SAP Cloud ALM through the Availability of Relevant Capabilities check in your SAP Readiness Check analysis. 

If a high number of modifications are identified and your processes contain multiple enhancements or extensions that are still needed and are not provided by SAP Cloud ALM, you can explore the extensibility options in SAP Cloud ALM.

The Change Request Management section contains the following details:

• Transaction Types Modifications: compares custom transaction types with the standard delivered customizing for the original transaction type and shows where differences from standard exist. These differences can be either changed entries representing an enhancement or adaptation in the process, or new entries meaning an extension in the process.
• Custom Change Cycles: Change cycles are not recommended to be copied. This list shows if custom transaction types of type cycles exist, with the assigned change transactions.
• Focused Build Modifications: Focused Build is delivered as a turn-key solution and should not be modified. Modifications of the standard customizing are detailed in this list.
• Active BADI Implementations: this list contains the custom implementation of Business Add-ins in the area of Change Request Management that are also active.

The described details will allow you to identify where enhancements and extensions exist to more precisely understand how you run your Change Management processes in your SAP Solution Manager system, to help you measure the impact of moving this process to SAP Cloud ALM and evaluate where extensions are possible, but generally, it should not prevent you from starting your transition project.

Data Collection

The SAP Readiness Check for SAP Cloud ALM data collector, which runs in the SAP Solution Manager system, has been updated to include the data required for the new Enhancements & Extensions capability. Ensure version 68 (or higher) of SAP Note 3236443 has been implemented before scheduling the collector. Once the data collector is complete, you can use the generated data archive to create a new SAP Readiness Check analysis or update an existing analysis (using the Update Analysis function to upload the enhanced data collection archive).

As always, we look forward to receiving your feedback!

Your SAP Readiness Check Team