SAP Readiness check for Cloud ALM

SAP will stop supporting SAP solution manager by 31.12.2027. All its functions will be migrated to SAP Cloud ALM.

The SAP readiness check for Cloud ALM will check the usage of current functions in your SAP solution manager and will validate if replacements in Cloud ALM are already present.

Since Cloud ALM is constantly growing in functionality you better run this check yearly. It is up to each customer to decide to move to SAP Cloud ALM for part of the functions or to wait until all functions are available.

There are other readiness checks as well:

Preparation in SAP solution manager

Apply the latest version of SAP note 3236443 – SAP Readiness Check for SAP Cloud ALM to your SAP solution manager system. Run program /SDF/RC_ALM_COLLECT_DATA in your solution manager production system.

It might be that your RFC for destination WEBADMIN is not setup correctly. That will cause a short dump.

If you are not using Trace Analysis function, you can remove code to this call in the local definition of class /SDF/CL_RC_ALM:

Running the check

Run program /SDF/RC_ALM_COLLECT_DATA in your solution manager production system. Select the option Schedule Analysis:

When the job is finished select Download Analysis Data and save the file.

Upload the result file on the Readiness page in SAP for me on this URL.

Result of the check

After the upload, wait up to 1 hour for SAP to process the results. For full explanation of the checks, read this SAP blog. Short description is below:

Top left you get an overview of the capabilities that were detected that are currently in use in Solution manager, or were used in the past:

Below is the most important overview. This shows if your used functions are available on Cloud ALM or will come in the near future, or only on the far Vision future:

Solution manager clean up

For parts of solution manager that you don’t use, you can perform the technical clean up.

EWA tips & tricks

SAP early watch (EWA) contains information on your system that might already or in the future impact performance and security.

A periodical review of the EWA is needed.

This blog contains tips & tricks for the technical working of the EWA reports.

For other frequently asked questions, read the note 1257308 – FAQ: Using EarlyWatch Alert.

SAP EWA generation

The EWA can be generated from SAP solution manager itself. Or you can use SAP Focused Run or Solution manager as data collection system, and than relay the information to SAP. The end result can then be seen on the online EWA workspace in the SAP support portal. More information on the EWA workspace can be found in this blog.

Since most new functions are added in the EWA workspace it is the best way forward. It is also less maintenance work. The only thing to do is to keep sending the data. Any new reporting function is done by SAP. SAP will also take care to have the content updated.

So all in all, if you are currently doing the EWA generation directly in SAP solution manager, consider to switch to the model where you send the data to the SAP EWA workspace via solution manager or via SAP Focused Run.

Setup in SAP Focused Run

A good manual for SAP Focused Run for EWA setup can be found on these reference sites:

Troubleshooting guide for EWA in SAP Focused Run, follow this link.

Also check OSS note 2715504 – Configure Early Watch Alert Job.

EWA in solution manager

General activation process of EWA in solution manager is described in OSS note 2729186 – General Process of EWA Generation in SAP Solution Manager 7.2. If an add hoc extra EWA needs to be generated, follow the steps in OSS note 2357073 – How to Create an Ad Hoc EarlyWatch Alert SAP – Solution Manager 7.2.

Adding email receivers is explained in OSS note 2282944 – EarlyWatch Alert: Solution Manager 7.2 how to setup/configure EWA reports or add email recipients.

Content update of SAP EWA content in SAP solution manager is required at regular intervals. The procedure is described in OSS note 2732608 – How to replace the Service Content (AGS_UPDATE).

Known issue list for EWA

The known issue for EWA is kept as list by SAP on this page. And OSS note 3138592 – Known Issues with the EarlyWatch Alert (EWA).

Troubleshooting when EWA is not sent to SAP

When you have issues that the EWA data is not sent to SAP properly, follow the checks in OSS note 1684537 – EarlyWatch Alert not sent to SAP: troubleshooting guide.

Removing unwanted secondary HANA database from the EWA

If you setup a secondary HANA database in DBCO, that database might appear in the EWA of the primary system. To get this unwanted information out of the EWA follow the steps as described by SAP in this page. Basically add the description NON_EWA_ in the secondary connection:

Setting up the BKF section in the EWA

OSS note 2282310 – Business Key Figures for EWA report contains the steps to get the BKF chapter activated.

Make sure in the managed system the user running the EWA data collection has the special role SAP_MANAGED_BPOANA_DIS. This is cause number 1 of issues.

If you make the settings, you would have to wait 3 weeks before the data is filled properly.

To gain speed, you can use the Express option. This option is explained in OSS note 2821062 – BKF Express Option/Manually running the BPMON job.

The UI of Business key figures Chapter Setting settings in the EWA is terrible. Please use the scroll bars to go to the right part. And the instruction mentions that you need to double click on a button or tab. This is correct. If you click once, nothing will happen. You really need to double click. This is completely counter-intuitive. But if you don't do it, it will not work, and you loose a lot of time.

If it still does not work, don’t hesitate to raise a message to SAP for component SV-SMG-SER-EWA.

SAP might ask you to apply the note 2477832 – SAP EWA Special Content BKF – on demand data collection (routine update & ZReport) as a workaround.

Generic background information

EWA wiki of SAP: link.

Generic background information on EWA can be found in these OSS notes and blogs:

Technical clean up for Solution Manager

This blog will focus on technical clean up for SAP solution manager.

Questions that will be answered are:

  • How can I reduce size of fast growing tables in SAP solution manager?
  • Which functions of SAP solution manager are in use or were in use?

SAP Readiness check for Cloud ALM

SAP Cloud ALM will replace SAP solution manager. You can run the SAP Readiness check for Cloud ALM to determine which functions of solution manager you use or were in use in the past.

Technical clean up general

SAP solution manager is a netweaver system which also used BI functions. For the general tables read the Technical clean up blog and for the BI parts, the BI clean up blog.

Solution manager specific clean up

A good starting point for clean up is OSS note 2549260 – Certain tables in Solution Manager system grow fast. This covers the most common use cases.

Special use cases are list below.

BI clean up

For BI specific clean up of solution manager, read OSS note2053261 – Solution Manager: HANA Database Cubes are not reorganized.

Custom code management clean up

Check OSS note 2790429 – Custom Code Management: Deletion Report for SP05 and higher. Then run program RAGS_CC_DATA_DELETION.

LMDB clean up

Table LMDB_P_CHANGELOG can grow very large. Note 1695927 – Cleaning up the change history in the LMDB explains to run program RLMDB_CLEAR_CHANGELOG for clean up.

CUP data

If table CUP_USAGE_DATA grows fast, follow the instructions from OSS note 2150720 – CUP enabled by default with automated cleanup process for outdated statistics.

E2E diagnostics data

If table SMD_HASH_TABLE is growing fast, check OSS note 1480588 – ST: E2E Diagnostics – BI Housekeeping – Information to clean up the data.

Technical monitoring data

If you are using Solution manager to do technical monitoring, the instructions for data reduction are listed in this OSS note: 2345041 – How to Reduce and Maintain Table Growth in Technical Monitoring for Solution Manger 7.1 & 7.2.

If you set up the monitoring in the past, but are not using it, best to switch it off. If you are actively using it, consider moving it to SAP Focused Run, which is far superior. More on Focused Run in this blog series.

Large SWJ_CONT table

If table SWJ_CONT is growing, you can run program RSPPF_SWJCLEAN for clean up. See note 1890845 – Removal of unnecessary entries from SWJ_CONT.

Solution manager demo system

This blog will explain about the free available SAP solution manager 7.2 demo system. If you are looking for a Cloud ALM demo system, read this blog.

Questions that will be answered are:

  • How can I access the free available SAP solution manager 7.2 system?

SAP solution manager 7.2 demo system

To promote the use of SAP solution manager 7.2 SAP has made a system available for everybody to test drive.

Follow this link to go to the main page. Then scroll down to the access link:

This will bring you to the launchpad by using one of the roles (with user ID and password on the site):

After logon you reach the launchpad, for that specific role (example here is Business Process Expert):

This will enable you to test drive the new functionality for Solution documentation:

This is just one of the examples. You can also test drive Focused Build and Focused Insights functionality. Both are free to use as of 1.1.2020 (see blog).

The system that SAP offers does have regular updates and resets of data. Read the SAP blog for the actual dates.

Licenses for SAP solution manager

SAP solution manager licenses have been renewed last few years by SAP.

Questions that will be answered in this blog are:

  • Do I need a user license for solution manager users?
  • If I run solution manager on HANA, do I need to pay HANA database licenses?
  • How can I get Focused Build and Focused Insights?
  • What about Focused Run licenses?

User licenses for SAP solution manager

Since 1.1.2018 the requirement of having named users was dropped by SAP.

HANA database licenses

If you want to run HANA database below SAP solution manager as database, you need to procure the infrastructure. The HANA database rights are included in SAP solution manager. This is the only exception SAP has. For all other use case you need to pay for HANA as database as well.

Using SAP solution manager for non-SAP components

You can use SAP solution manager to manage non-SAP components as well. Especially the ITSM service desk component can be used for this. When you use this function for non-SAP components, you will need SAP enterprise support rights for SAP solution manager in stead of the SAP standard support.

Focused Insights and Focused Build

SAP offers Focused Insights and Focused Build as extra options on top of SAP solution manager. Both are installed as add-on. Focused Insights brings extra dashboard building capabilities. With Focused Build you can get an extra grip on your solution build process.

As of 01.01.2020 both solutions are part of standard maintenance contract. See also OSS note 2361567 – ST-OST Usage Rights and Support.

If you want to try out these solutions, you can use the available free SAP demo system. Read more about this in the following blog.

SAP Focused run now also covers the functionality of Focused Insights, but in a far superior and more performing way. Read more in this blog.

Focused Run

Focused Run is separate solution with separate license to optimize the running of large SAP landscapes. Focused run does NOT run on SAP solution manager. It runs on a separate environment and only runs on SAP HANA. You cannot combine a Focused Run and SAP solution manager on one single installation. More information on Focused Run can be found on the SAP site. And on the specialised SAP Focused Run Guru site.

For licenses of Focused Run, read this dedicated blog.

Despite the fact that Focused Run is a paid solution, it offers by far the most sophisticated and added value product.

More background information

More information can be found on the SAP solution manager usage rights website.