Skip to Content

SAP Solution Manager 7.2 Insight…

If you are a customer currently using Change Request Management (ChaRM) in SAP Solution Manager 7.1 and planning to upgrade to 7.2 SP03/04, then here is an activity required for Upgrade Guide document. This activity contributed to the successful upgrade at my client’s site!

 

Symptoms

  1. The performance of ChaRM Content Activation in step 2 Activate Content of Solution Documentation Content Activation is poor during migration of Change Request Management reporting tables (ex. /TMWFLOW/REP71KR).
  2. The performance of ChaRM Content Activation in step 2 Activate Content of Solution Documentation Content Activation is poor during migration of Change Request Management change documents for a Change Cycles that have more than 1,000 Change Documents assigned.

 

Solution

  1. Implement SAP Note 2417302 (ChaRM: Asynchronous reporting tables migration) using Note Assistance (transaction SNOTE) and perform the manual post-implementation activities as described in the notes on SAP Solution Manager 7.2. If this note is implemented, the ChaRM reporting data is not migrated as part of the content activation. An asynchronous job (CM_MIGRATE_REPORTING_TABLES) is automatically submitted to migrate the ChaRM reporting tables after Content Activation is performed. We had 30,000,000 entries in table /TMWFLOW/REP71KR and the job took 90 minutes to finish. The average estimate is 1 hour for 10,000,000 entries as it depends on the power of the servers.
  2. Implement SAP Note 2419683 (ChaRM Content Activation Improvement) using Note Assistance (transaction SNOTE) and perform the manual post-implementation activities as described in the notes on SAP Solution Manager 7.2. We had one Change Cycle with ~1,500 Change Documents assigned and another Change Cycle with ~5,500 Change Documents assigned.

Without these Notes, it would have taken us roughly 8-10 hours to complete Content Activation but instead it was 2 hours.

 

Additional Information

In activity Check Readiness of ChaRM Content (step 1 Check Prerequisites of Solution Documentation Content Activation), the system checks whether Change Request Management content can be activated. A background job confirms the format of BDoc data structures used in the CRM backend is compatible with the CRM release after upgrade to 7.2.

If an error message occurs (see below) in activity Check Readiness of ChaRM Content, refer to SAP Note 1643013 which explains how to solve the error. Once you have corrected the error, restart the activity.

If an error message occurs (see below) in IMG Activity: Maintain Field Catalog as per steps from SAP Note 1643013, then process the BDocs if possible, or remove them (only type PRODUCT_SRV is relevant). Use transaction SMW01 to correct the situation in ALL clients. To search for BDocs use transaction SMW03. Once you have corrected the error, restart the generation.

Also, please ensure the latest version of the SAP Note 2410497 (Fix Content Activation ChaRM for technical non-ABAP Systems) is implemented, otherwise activity Check Readiness of ChaRM Content will give you a false error message, which will prevent you to move forward to step 2 Content Activation.

 

Until next SAP SolMan 7.2 Insight…

Yuliya

 

P.S. A Big Thank You to the SAP Solution Manager Development Team in Walldorf, Germany for continuously releasing SAP Notes based on the feedback received from customers around the world.

To report this post you need to login first.

3 Comments

You must be Logged on to comment or reply to a post.

  1. K. Lai

    Content activation (Solution/Branch processing + Activate ChaRM content) in our clone of 7.2 SP04 production system took 70 minutes and after that the asynchronous job CM_MIGRATE_REPORTING_TABLES took 110 minutes. We had 86,000,000 entries in table /TMWFLOW/REP71KR. So initially I was expecting the asynchronous job to take at least 6 hours based on your given average estimate and was suprised it went four times quicker.

     

    (0) 
    1. Klaus Dickgiesser

      Depending on the DB server hardware the performance can be better. What was noticed in general, using SAP HANA as database system speeds up the runtime of the asynchronous job CM_MIGRATE_REPORTING_TABLES  dramatically. Here the estimation is that about 40 million datasets are migrated per hour.

      (0) 

Leave a Reply