Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
Showing results for 
Search instead for 
Did you mean: 
0 Kudos

SAP Solution Manager 7.2 Insight...

If you are a customer currently using Change Request Management (ChaRM) in SAP Solution Manager 7.1 and are planning to upgrade to 7.2 SP03, then here is a manual activity required for Upgrade Guide document.

After implementing SAP Note 2285968 version 17, you are not able to use an existing Change Cycle that was in scope for Content Activation or to create a new Change Cycle (SMIM). Below are the two scenarios explained in detail.

Scenario #1: Existing Change Cycle
1. Logon to WebClient UI.
2. Choose Change Request Management in the Navigation Menu.
3. Choose Change Cycle under Search.
4. Search for existing change cycle that was selected for Content Activation.
5. Select the change cycle to open it.

If you see the same UI configuration with blank Change Cycle/Phase, type/ID, Landscape/Branch fields then please refer to a Solution section in this post.

Scenario #2: New Change Cycle
1. Run SM_WORKCENTER transaction.
2. Select Administration Cockpit tile under Change Management group.
3. Select Create Cycle under Task List tab.
4. Select Phase Cycle (SMIN).
*You can also initiate creation of a new Change Cycle via WebClient UI*

5. Select Open Input Help in the Branch field.
6. Select Search.

If you get the same result "No entries found" then please refer to a Solution section in this post.

Once you implement the automatic corrections in the SAP Note 2375508, make sure that all manual activities listed in that SAP Note are implemented.

Raquel Pereira da Cunha explains in the comments section on Dolores' SAP Solution Manager 7.2 - Change Request Management: Usual questions and known errors page what the manual activity does in the systems to resolve the symptoms:
"The manual action in the note corrects the entries of table TSOCM_PROXY_IMPL, which defines the class used for document type Release cycle (CMRE). The programs behind look for these entries and based on that checks which subobject to select to show the configuration view. If the entries are wrong, no "object subtype" is selected and the <DEFAULT> configuration view is displayed, with fields for change documens, not for cycles. Once you correct the table, the UI for Cycle will be displayed correctly (object subtype SMAI or SMIM, not <DEFAULT>), with fields Landscape and Branch."

Additional Information
SAP Note 2375508 (Customer Change Cycle) is referenced in the SAP Note 2285968 (Master Note for Change Request Management and Quality Gate Management 7.20, SP3) and listed in the section 1A (Mandatory with Manual Activities).

Implementation of Master Note is a mandatory step in the POST-Upgrade phase (SOLMAN_SETUP --> 1 Perform Basic Setup --> 1.2 Implement Master Note).

Until next SAP SolMan 7.2 Insight...

Labels in this area