The purpose of this wiki page is to collect the frequently asked questions of customers starting with SAP Solution Manager 7.2.
July 12, 2018: IMPORTANT INFORMATION FOR SP07
Implement SAP Note 2667205 - Duplicate entries in AIC_RELEASE_CYCL as soon as you get your system in SP07 to avoid problems with your already created phase and continual cycles that were using change control landscapes. If you have already made a change in the cycle document, like moving the cycle phase, you would need to run the indicated report in the SAP Note.
0. What happens with my ChaRM projects if I want to upgrade my system from SAP Solution 7.1 to 7.2? Content Activation
You don´t need to close your ChaRM projects before moving to 7.2.
Open projects will be migrated to the new master data model, using Solution, Branch, logical component groups, etc., and to new change cycle types. Content of the assignment blocks Projects, Documents and Solutions will be transferred to content of Solution Documentation assignment block (as far as this is possible).
For this you need to perform the Content Activation process, all information about the Content Activation can be found in the Content Activation Guide and in this wiki page SAP Solution Manager 7.2 Content Activation.
The Content Activation has two parts:
- GP1 - Guided Procedure 1 - Preparation: which is the prepare activation part, this is done in 7.1 System.
- GP2 - Guided Procedure 2 - Activation: which is the content activation part, this is done in 7.2 System
NOTE: The GP1 can be also performed in 7.2 System, but no changes can be done to projects / solutions because they are read-only and SMSY is not available!
So it is recommended to do GP1- Preparation in 7.1 System before the technical upgrade and then after the technical upgrade with the system already in version 7.2 start the content activation from Solman_Setup.
Look for SAP Note with name "Composite SAP Note: Preparation for content activation for SAP Solution Manager 7.2" to find the SAP Note for your SAP Solution Manager 7.2 patch version like
2645166 - Composite SAP Note: Preparation for content activation for SAP Solution Manager 7.2 as of SP07
Pay attention to implement these two SAP Notes too before running the transaction PREPARE_ACTIVATION:
2610265 - Content Activation: Add GP1 technical ChaRM checks
2658285 - Content Activation GP1: Check for inconsistent iBase
Call transaction /nPREPARE_ACTIVATION in your 7.1 system.
Transaction PREPARE_ACTIVATION is used to define the scope of solutions and projects, which will be migrated to Solman 7.2, this transaction will open the first Content Activation Guided Procedure. Read chapters 1 to 3 of the Content Activation Guide.
- Step 1: Scope of Content Activation
From ChaRM point of view, all projects are checked looking for an active task list and an active open change cycle. If so, the checkbox in the column “ChaRM” is preselected.
If the ChaRM column is selected for a project and also the checkbox in the first column is marked, this will mean that the project is included in the scope and later during the Content activation part the corresponding change cycle document will be created and the change documents associated to the maintenance/implementation cycles in Solman 7.1 will be associated to the new change cycle document in Solman 7.2. The task lists do not have to be activated, they are reused.
If the change cycle and task list of the project were closed while there were still open change documents assigned to the project that you don´t want to lose, then create a new change cycle and a new task list to put the project into scope for content activation. Please note, this can only be done in Solman 7.1. In Solman 7.2 there is no way to get this project activated, because you cannot create a change cycle and a task list for this Solar Project anymore!
You therefore need to select all SAP Solution Manager 7.1 projects that use Change Request Management and that you want to continue working with in Solman 7.2.
We recommend to close all request for change and all change documents in SAP Solution Manager 7.1, which are assigned to a SAP Solution Manager 7.1 project, which you will not use in SAP Solution Manager 7.2 anymore. Such non-activated change documents and requests for change are read-only in the CRM UI in SAP Solution Manager 7.2 and can only be changed into a final status using the report SOCM_CRM_SERVICE_REPORT. See also SAP Note 2474918 - How to View Data Created in SAP Solution Manager 7.1 Change Request Management (ChaRM) in SAP Solution Manager 7.2.
Note: Ensure that you have selected projects where all assigned systems in the logical component of the project are mapped into existing technical system in LMDB. ULA GUID from ib53 ibase component will be check against SAP_GUID of the technical system client in LMDB. If the match is not correct you will receive error message 'Ibase instance &1 is not in LMDB (see also note 2447548)' AI_SMMIG_MSG_CHECK 201. In this SAP Note 2447548 - Modify Ibase component in change documents you will find a report to change the ibase component of the change documents for 7.2 and also for 7.1 system.
- Step 2: Group and Consolidate Logical Components
You will select the name of your solution and the name of the logical component group LCG. Please try to understand the meaning of these concepts in Solman 7.2. Refer to the Content Activation Guide.
Read the documentation of this step carefully and notice that the name of the solution and the name of the LCG cannot be change later.
- Step 3: Maintain Logical Component Groups
You must understand what branches are in the new SAP Solution Manager 7.2 solutions. Refer to the Content Activation Guide
Check also wiki page How to create a solution for Change Request Management fpr some tips and tricks for the creation of a good solution for Change Request Management.
- Step 4: Assign Target Branches and Close Preparation
You will see an overview of the solutions you have assigned to which SAP Solution Manager 7.2 solutions. You also have the opportunity to choose the branch within the new solutions the contents will be moved in to and activated. This step completes this guided procedure.
Finishing this step does not mean you can't edit it in the future. You can open it at any time by using transaction PREPARE_ACTIVATION if you ever change your mind about your plans. You can go back and change things as often as you like until you reach the third step of the second Content Activation Guided Procedure. Once you have completed step three of the second guided procedure, you can still view what you did in this guided procedure by calling transaction DISPLAY_ACTIVATION.
Then perform the upgrade of the SAP Solution Manager system to 7.2.
Note: ensure that SAP Note 2516678 - Product system activated with wrong type is applied before content activation is started, the note is included in SAP Note 2397667 - Composite SAP Note: Preparation for content activation for SAP Solution Manager 7.2 as of SP03, in case that you have projects with dual-stack JAVA product systems.
Called from /nSOLMAN_SETUP->Related Links -> Solution Documentation Content Activation
After successful upgrade, complete the activation by using a the second Content Activation guided procedure on the SAP Solution Manager 7.2 system. Refer to chapters 4 of the Content Activation Guide.
During this procedure, project and solution content scoped during Preparation is transferred into the new solution documentation environment and activated for use, together with related application content in ChaRM, QGM, IT PPM, BPMon and Test Suite.
Important Note: Before this content activation can be performed, the Mandatory Configuration guide procedures must be performed: System Preparation, Infrastructure Preparation, Basic Configuration.
Also you need to run the SOLMAN_SETUP for the Change Control Management configuration before the Content Activation for ChaRM/QGM and the SOLMAN_SETUP for the Managed System Setup.
Then it is recommended to create a test phase cycle and a continual cycle, and change the status for both until reaching their final status. Create the task lists.
The idea is to test that the Solman 7.2 ChaRM workflow works correctly before starting the Content activation.
If you have been using add-ons, partner solutions and self-defined BAdI implementations in 7.1, make sure that they are fully functional before starting content activation. The best way of doing this is to check and, if necessary, repair those extras in your development system.
Errors likeTECHNICAL_SYSTEM_NOT_FOUND in "Check Readiness for Charm Content" will indicate that the system, Non-ABAP or virtual system, is not assigned to a technical system in LMDB.
In SAP Solution Manager 7.2 systems without SLD data suppliers are created in LMDB under the Transport Domains tab where they are created. However, they are not automatically assigned a technical system. You must therefore assign the technical system explicitly.
Under Transport Domains tab, select the correct transport domain name for the system where you create the Non-ABAP or virtual system. Then under Non-ABAP Systems tab or Virtual Systems tab, select the system and assign the required technical system.
Also ensure that these SAP notes are implemented in the domain controller system of the managed landscape (also in the other systems):
1977240 - Extension of the AS ABAP SLD Data Supplier (RZ70)
2148577 - RZ70 always sets communication client to 000 for non-ABAP system
With this you ensure that the domain controller system is sending the information of the non-ABAP system created to the SLD of the SAP Solution Manager.
See other issues in SAP Note 2334553 - Error during content activation in Change Request Management due to inconsistent data in the LMDB.
- Step 1: Check Prerequisites
A mix of manual and automatic activities looks mainly at the basics of proper user and system setup.
"Check Readiness for ChaRM Content” performs a syntax check on CRM coding. Starting with SP04 , additional checks are performed, if all relevant product systems can be transferred into corresponding technical systems, and if the piece list activation has been performed.
Note: In the case that you performed a system copy from the SAP Solution Manager production system to prepare the Content Activation in a sandbox system you, could get errors during the Check Readiness for ChaRM content and later during the ChaRM content activation, the reason is due to the missing sytems in LMDB. This real-time system landscape data from LMDB is required to convert the projects to new cycles in 720.
- Step 2. Activate Content Activity
Activity “Adapt Number Ranges for ChaRM" creates an interval 01 for AIC_REL_ID (used as replacement for SolarProject_ID)
Activity “Activate ChaRM Content" does the ChaRM migration for each of the project selected during the preparation.
When activating a 7.1 project with Change Request Management content, first a change control landscape, is automatically created.
Following that, the activity creates a new change cycle for each project in scope.
For a SMMN (Maintenance project SAP0 variant, M* task list) document a SMIM change cycle documnet (phase cycle) is created.
For a SMDV (Implementation project SAP0 variant, I* task list) document a SMIM change cycle document (phase cycle) is created.
For a SMMM (Maintenance project SAP1 variant, M* task list) document a SMAI change cycle document (continual cycle) is created.
For activation of self-defined change cycles (in customer Z-namespace, e.g. ZMMN or ZMDV), you have to tell the system the change cycle process types before and after (e.g. ZMDV in 7.1 may turn into the standard 7.2 type SMIM, or ZMDV in 7.1 remains in the self-defined space and turn into ZMIM in 7.2) through mapping table AIC_SM72_MAPPROC.
The new change cycle process type must already exist at the time of filling the mapping table in the 7.2 SAP Solution Manager system. If old and new change cycle process types use different status profiles with different user status values, you also have to maintain status value mapping in table AIC_SM72_MAPSTAT.
Existing task lists, open requests for change and open change documents of the old cycles are then reassigned to the new cycles. Finally, the system assigns the related change transactions to a new change cycle. This process is logged in database table AIC_SM72_CM_LOG. Change transactions which have not been activated, or are assigned to projects which have not been activated, cannot be accessed in change mode in 7.2. They remain visible as read-only entities.
After upgrading to SAP Solution Manager 7.2, you cannot edit self-defined Z change cycle types (created in 7.1) or change cycles of type SMMM, SMMN, or SMDV, although you can continue to display them in the WebClient UI. The same applies to any requests for change or change documents that have not been activated, for example, because they are already complete or are not assigned to an activated project. If you discover change transactions you want to work with in 7.2, but which are read-only in 7.2 because the 7.1 projects they belonged to were not activated for 7.2, you can use report AIC_CM_72_POST_MIGRATION to recover them. The report for subsequent activation can only handle change transactions related to projects that have an open task list and an open change cycle and the project can only be activated into an existing branch of an existing solution. You can find further details in the online info text provided with report AIC_CM_72_POST_MIGRATION.
See KBA 2628825 in case of errors "Technical_system_not_found" and “Unknown system” for decommissioned systems.
In the Administration Cockpit you will see now that the M* and I* task lists from migrated SMMN and SMDV projects under Task List ->Phase Cycles tab.
Please ensure this SAP Note 2375499 - ChaRM : Migrated project should be listed under phase cycle in task list of Admin Cockpit is implemented.
- Step 3. Close Activation
After following these actions please have a look to section 1.10 How to handle your Z transaction types after the upgrade to 7.2.
1. Main changes in SAP Solution Manager – Change Request Management scenario
1.1. I cannot create a project in solar_project_admin
In SAP Solution Manager 7.2 not projects will be used anymore, ChaRM and QGM will used Solutions and Change Control landscapes. Solutions and Change Control Landscapes will have branches.
Branches will contain logical component groups that will contain logical components for each branch. Inside the logical component groups you will enter your managed systems from each managed landscapes.
This is the best official guide that I know speaking about Solutions and the use of them in Change Request Management.
1.2. What is a Solution –Branch – Logical Component Group – System Role - Change Control Landscape - Sites
The solution should contain the complete customer system landscape, processes, and solution documentation in a customer's business.
Technically, a solution is the root of a structure that contains all of those objects.
From a process perspective, a solution covers all the company’s business processes. From a system perspective, a solution covers all productive systems that are connected through interfaces.
Even for an international multi-site company one solution will generally be sufficient.
Multiple productive solutions typically cover the use case of a service provider running multiple productive solutions for different clients.
By default a newly created 7.2 solution has a production and a maintenance branch.
The best way to get what is a branch is to see the examples provided also in the same guide about how was a project- logical component in Solman 7.1 and how to get the same managed systems included in the branches and logical component groups of a solution in Solman 7.2, from section "2.6 Activating Common Landscape Scenarios" of Content Activation Guide:
The next example is a little bit trickier.
Customer has a development system, a QAS system and a PRD system. The transport tracks are in the example from GHD:100 to GHQ:100 to GHP:100 and from GHD:200 to GHQ:200 to GHP:200. This landscape pattern can have different reasons which leads to different landscape designs.
In case 1 client 100 is used for a different Business Scenario than client 200 - like 100 for SD and 200 for MM, then it is recommended to create two different logical component groups
In case 2 client 100 is where the workbench development is done and is transported to GHP:100 on a different transport track and the end-user/business user are only working in client GHP:200, then it is recommended use Global site for Workbench client and <site1> for the business which can then be labeled properly
Note: standard "Global" sites are automatically inserted into thebranches. It is the expression of the global significance of the common development source system GHD:100 for all sites. As the site concept covers both the global and site-specific aspects of SAP solution landscapes, a "Global" site is always included. You cannot delete it.
In case 3 client 100 is where workbench development and customizing is done let say for ASIA region and client 200 is only for the customizing for EMEA region, then it is recommended to create two diferent sites
The option to use two productive system roles was only recommended until SP02, with SP03 and the site concept is not recommended anymore.
Branches can be understood as 'version contexts' of a solution. The currently productive solution is documented in the production branch. If you run a development environment in which you are setting up a new product version (which will become set productive in the future), possibly including your own custom developments, you would represent this by a development branch for the systems in the development track. Typical maintenance activities such as implementation of SAP Notes would normally be handled in a separate maintenance branch, not in a development branch.
But please remember that still the real data are the data maintained in the TMS of the managed systems, the systems included in the Logical Component Groups should fit with the created TMS transport routes.
Logical component groups
A logical component group LCG comprises all systems of a solution that have the same productive system and system type e.g. ABAP or Java, so you create a separate logical component group for each ABAP-based and each non-ABAP based productive system. For example, a solution could contain the logical component groups HR, ERP, CRM, BI, PI, BOBJ, PORTAL. An important exception to the rule is that companies with, e.g. multiple ERP productive systems per site (country, plant) have to use only one ERP logical component group.
Logical component groups should be created from the solutions.
Note: all the systems of one transport track have to be in the same logical component group, see SAP Note 2461467 - ChaRM&QGM: One transport track should not contain systems crossing logical component groups.
See SAP Note 2441119 - ChaRM: Support system with different roles in different logical components
Each system inside a logical component group is having a system role like for example, Development, Test, or Production.
There is no change in the concept of system roles from SAP Solution Manager 7.1 to 7.2, but the maximum number of custom roles has been increased from 10 to 52.
Note: You can use all lower and upper-case letters except A, B, C, D, E, F, P, S, T, V, as well as numbers. This is necessary to assign systems of multiple sites to the same logical component (countries, plants). Use system roles for this purpose, do not create site logical components,
In sm30: smsy_roles you can create new roles, however what it is really important is not the description name of the role, it is the Type of Role linked to it, assign it in transaction /nmaint_roles:
Change Control Landscape
In the solution you can create a Change Control Landscape that is a subset of LCGs available in the solution.
You can use Change Control Landscapes in ChaRM scenario.
For example in the case that you has a large number of LCG, then you can create one or more Change Control Landscapes and then select only some LCG and not all. Then when creating a cycle you can select the "big" solution or directly a change control landscape.
When using Release Management, the release cycle can only use Change Control Landscape instead of Solution.
Sites are provided in SP03 in case that you have for example multiple production system:clients like when using different regions.
Please see "2.6.5. Activating a Multi-Production Scenario" of "Solution Documentation Content Activation Guide" .
Another example for using sites is if you are using the same system:client under different roles, for example as source system and also as target sytem, then you could try to separate them in two sites for the same logical component group to enter the different roles in the different sites.
1.3. How to create a solution
In /nslan you can create your solution. Please see wiki page How to create a solution for Change Request Management for the detailed steps to create a solution including a maintenance landscape and also an implementation landscape:
1.4. New change cycles transaction types
Maintenance cycles SMMN, SMMM, SMDV disappear in Solman 7.2, new change cycles transaction types are:
- SMIM: Phase cycle (was: Implementation cycle, SMDV and SMMN) - variant SAP0 - created in CRM Web UI directly.
- SMAI :Continual cycle (was: Maintenance cycle, SMMM) - variant SAP1 - created in CRM Web UI directly. It is for urgent change documents only until SP06.
Since SP06 you can create normal and standard changes also for SMAI cycles, detiails here.
- SMRE: Release cycle - variant SAP0. This kind of cycle has to be created in Release Planning Tool. End user has to create the releases in the Release Planning Tool first and then generate the CRM transaction of the cycle for each release.
When creating a change cycle you should select a solution/change control landscape and a branch.
Only the branches containing a logical component group with a system with role source are available for selection.
- new Change Cycle documents for each selected Solar project which has active task lists will be created. Those will be assigned to the Solution/Change Control Scenarios and respective Branches.
- the existing task lists will be re-assigned to the newly created Change Cycles automatically.
- all SMDV, SMMN will be mapped to a “Phase Cycle”. All SMMM will be mapped to a “Continual Cycle”. Each Change Cycle will then get the same status as before.
- after the Cycles have been updated, all open change transactions (Request for Change + Change Documents) will be re-assigned from their former Solar-Project assignment to the newly created Change-Cycles automatically.
Note: All SD* transaction types will be removed in Solman 7.2, customer should closed all documents for these types before upgrading
Note: See also SAP Note 2331779 - How to Manage Change Requests and Change Documents which are not part of Migrated Projects in SAP Solution Manager 7.2
1.5. Task list creation
Task list is created now from the maintenance cycle document directly by using a guided procedure when moving the document from Created to Scope for example in a SMIM document:
When you select a solution- branch for a change cycle document, the source systems in the logical component groups of the branch will be used to draw the Transport Track Overview, all other systems will be based on the whole logical component groups included in the Solution, in all branches.
1.6. More -> Redefine landscape action
You could redefine your system landscape and then recreate the task list structure based on the new landscape, this option was initially only available for the systems with target role.
Jan. 2018: With SAP Note 2587310 - Remove Development and Production systems during redefine landscape two additional scenarios were added:
Scenario 1: You keep the track but want to remove one of several production systems. These checks are performed:
- There is no open change document to which the configuration item of the production system to be deleted is assigned. (Only for ChaRM)
- There is no scope item of open RfC to which the configuration item of the production system to be deleted is assigned. (Only for ChaRM)
- There is no active H task list which contains the production system to be deleted. (Only for ChaRM)
- If the import buffer of the production systems to be deleted is still reachable, there is no “waiting for import” transport requests from the relevant track in the buffer.
Scenario 2: You want to remove whole track(s), that is: the development system or the exclusive production system. To remove the exclusive production system, all the checks of scenario 1 are performed. To remove the development system, the following checks are performed:
- There is no open transport request from that track.
- There is no open change document which contains the transport request from that track.
- If the development system to be deleted is assigned to the “Development <-> Retrofit” relationship, there is no unfinished retrofit transport request.
If the checks are not passed, the redefinition of the system landscape is stopped. Detailed information is logged in SLG1 log /TMWFLOW/CMSV TRACK_LANDSCAPE.
- If you remove inactive or disused systems, you get a warning but you can continue the redefinition.
If you remove systems that have been deleted from the LMDB, the checks are skipped and you can continue the redefinition.
1.7. Complete Change cycles
- SMIM: Phase cycle (was: Implementation cycle, SMDV and SMMN)
For SMIM, when setting it to ‘Completed’ from ‘Being Completed’, a popup window will be raised showing unfinished change documents, Request for Change documents and transport requests.
You can complete the phase cycle but the unfinished change documents and Request for Change documents will be moved to a NEW PHASE CYCLE document that is created automatically. I* task list remains the same one.
In case there are change transactions with ITPPM integration, the cycle switch cannot be performed. With SP05, in case there are change transactions with ITPPM integration, the ITPPM project is shown as well as the ITPPM project manager; means if there are change transactions with ITPPM integration, there is no cycle switch possible. In this case the change manager has to contact the project manager of the particular ITPPM project and request to decouple the change transaction from the ITPPM project.
Only if all change documents and request for changes are closed and all transport requests are imported to production systems and no longer available in the import buffer, only If both conditions are met, you will receive a popup when closing the cycle asking you whether you want to close it completely.
- SMAI :Continual cycle (was: Maintenance cycle, SMMM)
There is no cycle switch for it.
You can ONLY complete the continual cycle if there are not unfinished change documents and request for change documents.
There is no option to move these unfinished changes documents to a next phase cycle, so the only option is to finish them.
- SMRE: Release cycle
Here we have ‘Single Task List Strategy’ which means all the release cycles assigned to the same combination of change control landscape and branch will share the same task list.
For SMRE, the cycle switch happens when setting it to ‘Hypercare’ from ‘Deploy’.
In ST7.2 the predecessor cycle completion and successor cycle creation are done at one shot.
In case there are change transactions with ITPPM integration, the cycle switch cannot be performed. With SP 05, in case there are change transactions with ITPPM integration, the ITPPM project is shown as well as the ITPPM project manager; means if there are change transactions with ITPPM integration, there is no cycle switch possible. In this case the change manager has to contact the project manager of the particular ITPPM project and request to decouple the change transaction from the ITPPM project.
1.8. Administration Cockpit
Administration Cockpit is the entry point to the administrative activities, you can find it as a tile in SAP Solution Manager Fiori Launchpad in /nsm_workcenter .
- Task Lists
On this tab page, you can execute operational and background activities for distributing software in your system landscape, for example, handling change cycles, task lists, and import scheduling.
- Landscape Overview
You can display information about the managed systems contained in the logical component groups that are connected to Change Request Management, and/or Quality Gate Management (QGM), via the solution landscape (transaction SLAN ) or the change control landscape assignment. Each managed system in the logical component groups is listed along with the communication systems.
Landscape overview tab is empty until you create a phase/continual/release cycle for a solution/change control landscape and branch
- Critical Objects
You can define and edit critical transport objects.
- Cross-System Object Locks
On this tab page, you can manage cross-system object lock entries. You can display lock entries according to defined criteria, remove them or register lock entries for transport requests that are managed by Change Request Management or Quality Gate Management.
Note: In the case that you get this error when trying to switch on the CSOL for a system client:
Fail to switch the Cross-System Object Lock check for the system <SID> / <client>
No administration authorization in Change and Transport System (message number TK620)
Have a look to KBA 2424269 - Fail to switch the Cross-System Object Lock check for the system.
- Transport Analysis
You can analyze the transport requests in your landscape in different views.
- Search tab: the Search is using the Embedded Search functionality.
You can search for various objects based on your search criteria.
Depending on your authorizations, the system displays search results, for example, change transactions. You can navigate from the search directly to the transactions in the CRM WebClient UI.
As a prerequisite for the Search works you need to create connectors for Change Request Managements and scheduled the indexing. To achieve this, you make the required settings in SAP Solution Manager Configuration (transaction SOLMAN_SETUP) under Change Control Management -> Change Request Management -> Step 7 - > Configure Embedded Search -> Create Search Connectors activity and Schedule Initial Indexing activity.
- Scheduled Import Jobs (tab coming in SP03)
The Schedule Import Jor for Transport Request task is called from the task list.
In the Date tab you will see the option to select a period, you can select None, 15 minutes, 30 minutes, Hourly, Daily, Weekly, Monthly and Other Period.
Then in the Administration cockpit -> Scheduled Import Jobs tab you will have very flexible way to display/redefine/delete import jobs.
When scheduling the import as periodical job it is expected that there is not user interaction, so the import strategy should be import project all or status dependent import.
Selective import is not the good option here. If you need to choose the transports before each import, then it is not a good idea to schedule such a import as periodical jobs. In case you have configured selective import, and you have made requests selection in the import popup, then the same selection will be kept for all scheduled jobs in the admin cockpit. This is the standard behavior.
Report /TMWFLOW/SCHEDULE_IMPORT is obsolete in SAP Solution Manager 7.2.
May 2018: Note 2629408 - Enable Report /TMWFLOW/SCHEDULE_IMPORT for ST7.2
Note: Please check KBA 2388692 - Fiori Administration Cockpit Web Page Service Cannot Be Reached – Solution Manager in case that you have issues opening the Administration Cockpit in the launchpad.
1.9. Transaction SMSY is not existing any more
LMDB is now the single source of landscape information.
1.10. How to handle your Z transaction types after the upgrade to 7.2
After the upgrade to 7.2 and the content activation you notice that when creating a ZMCR, ZMMJ …document (Z transaction types were created in 7.1) in the CRM UI screens some fields like change cycle, landscape and branch are not editable. Also your Z transaction types are not appearing in the ZMCR Scope assignment block for selection.
With the version 7.2 new tables were introduced to support the new master data model, using Solution, Branch, etc. Like the one for Configure Status-Dependent UI Element Control table AICV_PROC_EDIT2 and the copy control table AIC_V_TRTY_MAP2.
SAP just provided the standard customizing in these table. But unfortunately there is no migration tool available which migrates the customer data.
Here there are two options depending on your needs:
1. If you can “redo” the configuration of your Z transaction types and if the Z transaction types were created using the copy report AI_CRM_CPY_PROCTYPE then use the update option “Overwrite existing data with standard settings”, the data for the Z transaction types will be updated with the 7.2 standard customizing.
Update option “Insert new data (existing data will not be updated)” will not update the data.
2. In you cannot “redo” the configuration of your Z transaction types then you will need to perform the update of the tables manually.
In transaction SPRO->SAP Solution Manager under Capabilities (Optional) -> Change Control Management -> Change Request Management Framework
2.1. Make Settings for Change Transaction Types
Select the transaction type and then:
- Check the change request management actions and the consistency checks per the Z transaction types by comparing them with the standard, you can find a list of change request management actions and consistency checks deleted and new in What's New in SAP Solution Manager 7.2. Select the Support Package Stack and then Change Control Management.
For example consistency check CHECK_IN_AND_OUT is obsolete in 7.2.
- Check the Specify Status Attributes for predecessor documents SET_PREDOC customizing by comparing with the standard transaction type.
- Check Copy Control Rules. Check the entries your Z transaction types.
For the new cycle transaction types ensure that your Z transaction types are included in the Specify Status Attributes-> Specify Required Status Values for Follow-Up Docs for for being taken into account during the consistency check SUB_ITEMS.
2.2. Configure status-independent UI element control
Select Assignment Block Details. Select UI Elements CONFIGURATION_ITEM. Select Status-Depended Control of UI Elements and check that your Z transaction types have the correct entries here like for the standard transaction types.
Select Transaction Types. Check the entries for your Z transaction types and compare them with the entries for standard transaction types.
See also SAP Note 2317411 - Request for Change: Change Cycle is not editable in status 'In Validation'
In transaction SPRO->SAP Solution Manager under Capabilities (Optional) -> Change Control Management -> Transactions -> Actions -> Change Actions and Conditions
2.3. Check the PPF actions of your Z transaction types by comparing with the standard transaction types, for example, action SMCR_ASSIGN_SOLMAN_IBASE is obsolete in 7.2.
In transaction SPRO->SAP Solution Manager under Capabilities (Optional) -> Change Control Management ->Transport Management System -> Define Import Strategy for Transport Requests
2.4. Enter your entries according to the new master data model.
In both cases you will need to check also your business roles, as you can read in point 3.1 of this wiki page, the customer business roles are not updated after an upgrade to 7.2.
Please take note of the used navigation bar profile for your Z business role and check the content of Define Generic Outbound Plug Mappings, compare it with the SOLMANPRO navigation bar profile content and add the required entries. See SAP KBA 2397830 - Create new Transport Request is disabled in Transport Management AB of change document - Solution Manager.
See also SAP Note 1805236 - SAP CRM WebUI: Error "Recent items; dynamic navigation is not supported by this object" is thrown.
If you performed adjustments to the User Interface configuration of your Z transaction types in SAP Solution Manager 7.1, then you will require manual adjustment to get the new SAP standard fields and new assigment blocks displayed in the upgraded SAP Solution Manager 7.2 system.
In blog ChaRM: A Boost to Your 7.20 Project After the Content Activation Is Done, 1. Adopt the UI configuration section you can read that there new SAP standard fields that have been introduced like: Landscape, Branch, Change Cycle Description, Change Cycle ID, Change Cycle Type, Release Number, Change Cycle Status, Development Close, Go-Live Date.
Old fields like Project and Solution field are obsolete -> replaced by Change Cycle field, …
Also, there are some new assignment blocks like Solution documentation that replaces the Solutions, Documents and Projects assignment blocks.
These three old assignment blocks can be displayed, existing entries are still available, but read-only, Content is migrated into Solution Documentation assignment block, as far as possible.
There are two ways to adopt the UI configuration:
- Delete the customer specific UI Configuration, then the SAP Standard Default UI configuration is used. This standard UI configuration can be used as copy template to copy this into your Z Transaction Types. Then adjust the UI per your specific needs again. This is recommended if you were adding small number of customer specific fields or if you only renamed some field labels or removed SAP fields.
- Alternative, you can keep the existing customer specific UI configuration, and adjust this UI configuration. This means, the new SAP standard fields from 7.2 standard need to be inserted manually. This is recommended if you added big number of customer specific fields to the UI configuration.
See all details and recommendations in the indicated blog ChaRM: A Boost to Your 7.20 Project After the Content Activation Is Done.
Note: In case of BSP errors like the following one when completing a SMIM cycle
The following error text was processed in the system:
Define component usage ´CUCycleSwitch´
Exception class: CX_BSP_WD_INCORRECT_IMPLEMENT
Program: CL_BSP_WD_REPOSITORY …
Remember that if you enhance a UI component then after each patch application you should go to /nBSP_WD_CMPWB open the UI component with the enhancement set and click on
Environment -> Runtime Repository comparison. Here check the differences and adjust your enhancement to the standard.
Also pay attention to Transport-Related Checks:
In SAP Solution Manager 7.2 SP03 every time you perform a transport-related operation, such a transport request release, import, some transport-related checks are done such as Cross-System Object Lock CSOL, Downgrade Protection DGP, Critical Objects, ABAP Test Cockpit, Code Inspector and Customer-Specific checks.
In the case that you have upgraded your SAP Solution Manager from 7.1 to 7.2 you need to adapt your Ztransaction types for the change documents such as ZMHF and ZMMJ to get the missing transport-related checks. Absent customizing can cause incorrect processing of transport-related PPF actions for these transaction types. Follow SAP Note 2325006 indications to see how to proceed.
More information about Transport-Related Checks can be found in this Application help link.
Note: Dump ASSERTION_FAILED when executing action "Pass Urgent Change to test"
Runtime Errors ASSERTION_FAILED
ABAP Program /TMWFLOW/CL_SYSTEM============CP
Sometimes after the upgrade to Solman 7.2 after the ChaRM content activation you cannot work with the change documents created in Solman 7.1, the reason could be that these change documents have archived/missing configuration items. There is a report AI_MODIFY_IBASE_IN_DOC provided in SAP Note 2447548 - Report for Replacing Ibase component in documents to change the ibase of the change documents.
Note: This report is intended to be run for change documetns, no for request for change documents.
The faster way to check this is in se38 crm_order_read, enter the document number created in 7.1 and look in ET_REFOBJ structure for the PRODUCT_ID value.
In ib53 check if this configuration item has a ULA-GUID that matches with the SAP-GUID in LMDB.
In case that you need to change the configuration item of a document report AI_MODIFY_IBASE_IN_DOC can be used.
- Document ID: enter one or more documents numbers
- Process Type: enter the process type of the document
You can find this information of the document by running report crm_order_read in se38, enter the document number in field Transaction Number and look in ET_ORDERADM_H, the value under PROC column is the process type of the document.
- Old Ibase: enter the Installed base of the ibase text component associated to the configuration item of the document.
You can find this information in the previous report, look in ET_REFOBJ for the value under column IB_IBASE.
- Old Ibase Component: enter the ibase text component associated to the configuration item entered of the document.
Look in ET_REFOBJ for the value under column IB_INSTANCE.
- New Ibase Component: enter the new ibase text component associated to the new configuration item that represents the production system currently.
Ensure that the ULA-GUID of the new configuration item (information shown in ib53 for the configuration item in the Component Detail tab) needs to match with the SAP-GUID of the Technical system in LMDB ( to see this value go to LMDB to the technical system and then click on Details button, Qualifiers tab.)
- Test Mode: Select this option if you want to run the report in test mode
This information is also provided in SAP KBA 2394599 - How to handle your Z transaction types after the upgrade to 7.2.
*NEW SP05* 1.11. Enhanced Change Request Management action COPY_ALL_ENH
You can use the enhanced Change Request Management action COPY_ALL_ENH to release and import automatically/immediatelly the transports of copy (ToC) into the test system. If the release of the transport of copies is done to a transport target group, the import will be triggered to all the systems that are included in this transport target group.
Note: For transport operations to work correctly, for existing custom transaction types based on normal change (SMMJ), copy the Change Request Management action COPY_ALL_ENH from the Customizing of the standard transaction to the Customizing of the custom transaction types.
This action could be used in SP03 and SP04 for normal changes documents.
As this action is not provided in the standard customizing of the normal change documents for SP03 and SP04 if you want to use it please check also SAP Note 2467166 ChaRM: Use COPY_ALL_ENH for custom normal change-based transaction types and SAP Note 2445103.
*NEW SP05* 1.12. Standard Changes documents
Standard change is used to perform low-risk changes that are uncritical and frequently used.
Please see this wiki page to find some hints for using this change document type How to work with ChaRM Standard Changes documents.
2. Role SAP_SYSTEM_REPOSITORY_DISP does not exist
You are creating template user in activity SOLMAN_SETUP > Change Control Management > 5.1 Create Template Users and you get this error "Role SAP_SYSTEM_REPOSITORY_DISP does not exist" in all template users like CHARM_*.
Implement SAP Note 2225713 - SOLMAN_SETUP additional corrections for 7.20 SP01
3. Business roles
3.1. Customer business roles are not updated after an upgrade to SAP Solution Manager 7.2
When you upgrade to SAP Solution Manager 7.2, SAP will only modify the standard business roles such as SOLMANPRO. This is why you were requested to create new business roles, new transaction types in the Z/Y namespace. So that if you were to modify/customize something, an upgrade would not overwrite these changes.
From SAP Note 2188112 - FAQ ST720: "If you have copied the CRM business roles delivered by SAP (for example if you copied business role SOLMANPRO to ZSOLMANPRO or similar), you should compare and check your copied role with the corresponding role delivered by SAP: your copied role may have outdated or missing links. In particular, SAP has delivered new reporting links in the business roles. You should perform such a check after you apply each support package from SAP."
If you don´t do this link check you could miss some new links such as Requirement Management, and see old links such as Reporting, which don't work in Solution Manager 7.2.
4. Solution Documentation AB
4.1. No search results
When you are trying to assign a solution element in the Solution Documentation AB of a change document the search doesn´t find anything.
If you want to use the search you need to complete the configuration of SOLMAN_SETUP => Process Management => Step 7 "Configure Embedded Search":
4.2 How to add an element when change document has status other than "Created / In Development
In the standard change document transaction types, it is only allowed to add an element in the "Solution Documentation" assignment block when the change document has status “Created” (E0001) or “In Development” (E0002).
If you need to be able to add an element with another status such as “To Be Tested” (E0004) status, then first look in transaction /nSPRO for activity "Configure Status-Independent UI Element Control". Select assignment block SOLDOC and change in "Editable/Executable" column the value for this status to "Editable/Executable".
Then ensure that you enter also the associated SOCM action SOL_DOC_CREA in transaction SPRO -> "Make Settings for Change Transaction Types" activity.
This will ensure that the SOLDOC elements attached/assigned in this new status, for example, "To Be Tested”(E0004) moves to the production branch when the change documents move to production.
Select your transaction type and create a new entry as a copy of the existing one for status E0001. Change the status to the required status, for example, "To Be Tested” (E0004).
This is a late action to ensure that you also have an entry here for the created entry:
See screenshots for the above process in KBA 2464656 - Solution Documentation" assignment block - How to add an element when change document has status other than "Created / In Development.
5. Release Planning - Release Management
For using Release planning scenario you need to perform the solman_setup activities under Change Request Management and Managed System Setup guided procedures.
Release Management means that you can operate big release development over different landscapes.
You can synchronize the developments over the different systems landscapes boundaries, the integration test phase and the Go live.
When using Release Management, the release cycle can only use Change Control Landscapes instead of a Solution. A Change Control Landscape is a subset of LCGs available in the solution.
5.1. Empty screen in Release planning - no Create button available
To create, edit, or change releases you need to go to CRM WebClient UI, /nsm_crm, choose Change Request Management => Release Planning . Then choose Create button. If the Create button is missing as you can see in the screenshot below:
Ensure that you have activated the ODATA Service for Release Planning Tool AIC_RELEASE_PLANNING_SRV in the SAP Solution Manager Configuration in the Cross-Scenario Configuration scenario -> Mandatory Configuration -> Infrastructure Preparation -> Step 7 Enable Gateway Services.
In transaction /n/IWFND/ERROR_LOG look for possible issues like "System alias '' does not exist"
If this is the case check in SAP Customizing Implementation Guide => SAP Netweaver => SAP Gateway => OData Channel => Configuration => Connection Setttings => SAP Gateway to SAP System => Manage System Aliases that an entry exists in table /IWFND/C_DFSYAL like:
SAP System Alias Description Local SAP GW RFC Destination Software Version
LOCAL Local System Alias X NONE DEFAULT
See KBA 2249736 - FAQ related to the System Alias and Gateway flags.
After any modification please clean all caches according to KBA 2319491 -How to clean up the cache after applying changes that affect SAP Fiori apps and retest.
Note: Ensure that you have created a Change Control Landscape for your solution or implement SAP Note 2343846.
6. Requirement Management
6.1. IT Requirement is not be created from a Business Requirement
After the copy of the standard transaction types SMBR and SMIR to ZMBR and ZMIR please notice that action ZMBR_CREATE_IT_REQUIREMENT (in action profile ZMBR_ACTIONS) that is creating the follow-up document IT requirement needs to be modified. Parameter PROCESS_TYPE needs to be changed from SMIR to ZMIR value.
6.2 IT Requirement Change Cycle not found
In SAP Solution Manager 7.2 SP04 when creating an IT Requirement document for a customer transaction type like ZMIR the result list of Change Cycle / Phase field does not show all the possible change cycles for selection, in sm30 for view TSOCM_PROXY_IMPL remove this entry: SMI2 CL_CHM1_IT_REQUIREMENT IR05
KBA 2446888 - IT Requirement Change Cycle not found
7. My Business Requirements app
For any issue using this Firoi app please implement latest version of SAP Note 2248668 - Corrections for My Business Requirements (Display, Edit, Create) Solution Manager 7.20 Support Package 1 or SAP Note 2345632 - Corrections for My Business Requirements (Display, Edit, Create) Solution Manager 7.20 Support Package 3 depending of your ST-UI 100 patch level.
Then make sure you clean all caches according to SAP Note 2319491 -How to clean up the cache after applying changes that affect SAP Fiori apps and retest
7.1. Error when creating Business Requirement with My Business Requirements App
Once you have entered all data for the creation of the Business Requirement and click on Save button, nothing happens and the Business Requirement is not saved.And even you can get an Alert popup with this information "Problem updating Business Requirement".
If you are using IE please click on F12 Developer Tools and check the Console error messages.
1946234 - Fiori: Recommendations about Virus ScanningSAP Note
For testing, please disable Virus Scan completely in transaction /n/IWFND/VIRUS_SCAN and test again.
Official guide is in SAP Service Marketplace in /instguides: "SAP Fiori for SAP Solution Manager 1.0 Configuration guide". Check section “Section 2.4 Virus Scanning”, which contains all the information regarding virus scanning.
For more information about Virus Scan and how to create user * scan profile, see link http://help.sap.com/saphelp_nw74/helpdata/en/4e/0ba5960499001be10000000a42189c/frameset.htm.
8. Embedded Search - SAP Netweaver Enterprise Search
How to use it and configure it in SAP Netweaver Enterprise Search: new search option in SAP Solution Manager 7.2 for ITSM and Change Control Management scenarios.
8.1 Error when scheduling the initial creation of the search index in the Connector Administration Cockpit (transaction ESH_COCKPIT)
After the creation of the search connector for the data extraction for ITSM or ChaRM scenarios you need to schedule the initial creation of the index by selecting the connector and running Actions -> Schedule indexing, the action ends with errors.
In the job log you can see this entry: "Parallel load triggered, but parallel customizing not available" CRM_ES_EXTRACTION010.
You need to define a server group in rz12 and then follow the indications in KBA 2147477 - Parallel load triggered but parallel customizing not available In spro => SAP Customizing Implementation Guide => Customer Relationship Management => UI Framework => Enterprise Search Integration => Define Settings for Parallel Extraction Please specify the Server group and the Parameters here, the recomendaded values are:
8.2 Error creating connector AI_CM_BUS2000116
If you are getting this error when createing/preparing the connector AI_CM_BUS2000116 Change Request Management: Transaction in ESH_COCKPIT :
Error Messages (3)
Database table ESH:SID001~SID001~AI_CM_BUS2000116~BTORDER could not be created
HANA call terminated with HANA engine error. Error code: 320
Error message: cannot create index on expression with datatype LOB: BOL_ROOT_ENTITY_KEY: line 1 col 68 (at pos 67)
Please implement SAP Note 2370922 - ChaRM: AI_CM_BUS2000116 Enterprise Search connector creation error
9. BSP error CX_SOCM_NOT_IMPLEMENTED working with request for change and change documents
After you upgrade your solman system from 7.1 to 7.2 you could get this BSP error in class CL_CHM1_INSTANCE method IF_EX_SOCM_CHECK_CONDITION~CHECK_CONDITION when you are confirming a request for change or completing an urgent change.
The root cause is the obsolete consistency check CHECK_IN_AND_OUT. Issue will not the shown in SP03 but for the moment the only option is to remove this consistency check for all transaction types manually in sm34:AIC_SETTINGS, choose the involved transaction type -> Assign Consistency Checks -> Remove all checks with name "CHECK_IN_AND_OUT".
After that the BSP and the associated dump will disappear.
Update: See the comment from Yuliya K:
"We were able to resolve the BSP error 'CX_SOCM_NOT_IMPLEMENTED' mentioned in the point #8 via SAP Note 2310567 (ChaRM action SET_PREDOC does not work for ITSM transaction types) on SAP Solution Manager 7.2 SP01. The prerequisite note is SAP Note 2318118 (Missing condition PREDOC_EXISTS leads to a termination). There was no need for us to delete the consistency check 'CHECK_IN_AND_OUT' in SM34: AIC_SETTINGS as we implemented the two notes. However, we are planning to delete the entries as they are pointing to the consistency check 'CHECK_IN_AND_OUT' that no longer exists."
10. Error "No IBase component has not been assigned to the document" when creating a request for change document
The reason of error is that the consistency check IB_SYST_CHK used for example in status E0001 for SMCR in SM34 -> AIC_SETTINGS -> <Select your transaction type for request for change> -> Assign Consistency Checks -> E0001 IB_SYST_CHK is obsolete.
Please remove manually the obsolete consistency check IB_SYST_CHK for the used transaction type.
11. Transaction ID, Description and Status empty in Scope of Request for Change
You have added new change documents (Urgent, Admin changes) in Scope assignment block of a Request for Change. After running action "Release for Development" and saving you notice that fields "Transaction ID", "Description" and "Status" in Scope are not filled and remain empty. However the change documents have been correctly created.
Switch CRM_ASYNC_SAVE is activated in your Solution Manager system. Business function CRM_PERFORMANCE contains the switch CRM_ASYNC_SAVE and such business function CRM_PERFORMANCE is activated in your SolMan system ( transaction SFW5 ). This switch activates asynchronous update and this is not compatible with ChaRM and Incident Management scenarios.
See KBA 2381459 - ChaRM - Transaction ID, Description and Status empty in Scope of Request for Change for details.
12. ChaRM reporting /TMWFLOW/REPORTINGN - Report is obsolete
You will need to use Administration Cockpit 'Transport Analysis' tab to analyze the transport requests.
13. Quality Gate Management
13.1. Integration with Change Request Management
As you can read in the application help Quality Gate Management does not support an integration with Change Request Management in SAP Solution Manager 7.2.
14. Solution Manager Fiori Launchpad- Change Control Management Analytics
When opening the SAP Solution Manager Fiori Launchpad ( /nsm_workcenter) you can see under Change Management a tile call "Change Control Management Analytics".
When you click on this tile a new screen is opening for this URL http://....../sap/bc/ui5_ui5/sap/dsh_builder_ui5/...
The screen comes with the a set of tiles for the Analytics. However, the tiles are refreshing/loading for ever.
Please activate DSBUILDER_HDLER service, details in KBA 2384798 - Fiori tiles for IT Service and Change Management Dashboard never load - Solution Manager and SAP Note 2388885 - Dashboard data cannot be displayed.
Check the content of the Change Management dashboards in this link.
15. Some CRM Web Client UI issues after the upgrade to SAP Solution Manager 7.2
- In CRM UI, the Recent Items show “Loading…”, but never return the list
Check SAP KBA 2087632 - SAP CRM WebUI: Recent Items is showing Loading and Recent Items wiki page.
- In CRM UI, the match code returns the results but the user is not able to select the value from the Result List in IE (not in Chrome)
Check SAP Note 2252647 - IE8 - 'More' menu on UI Workbench Configuration does not open and Search Help and Smart Input Help wiki page.
- In CRM UI, in ITMS/ChaRM search view, in F4 help for a business partner field, IE returns: "the object does not support the property or method 'createEvent()'"
Also, check SAP Note 2252647 - IE8 - 'More' menu on UI Workbench Configuration does not open and Search Help and Smart Input Help wiki page.
- In CRM UI, the Automatic Save Confirmation dialog window is not displayed when creating an Incident without save and coming back to CRM UI Check the content in Auto Save Feature wiki page.
Please visit CRM Web Client UI Framework wiki page for further information.
16. Error when retrofitting in a Release cycle
When you are trying to retrofit a transport request for a Release cycle you get error "Error Text R000000XXXXXX ID TREE language EN not found " and in the task list you find
The system is not in any task list with these search conditions /TMWFLOW/TASKLIST280.
Please implement SAP Note 2426229 - consider release cycle in retrofit
17. Important SAP Notes when using Focused Build
When Focused Build add-on (ST-OST 200 SP0) is installed on a SAP Solution Manager 7.2 system please pay attention to these SAP notes:
- 2407934 - Focused Build - Release search shows no Change Request Management releases
This note fixes the issue of missing standard cycles types in the cycle search help of a RfC and change document
- 2436871 - Focused Build: Error Creating Task List (Continual Cycle)
This note contains manual activities only and fixes the issue of not able to create a task list for a continual cycle
In the case that you are using custom cycle transaction types and custom phase models, then you need to implement the following notes:
- 2443595 - Focused Build: Task List Variant Determination for Custom Cycle Transaction Types
- 2428777 - Focused Build: Custom Cycle Transaction Types are not Supported
18. Status-Dependent Import and Selective Import of Transport Requests
When you schedule the "Import Job for Transport requests" from the task list, you get an Import Transport Request pop-up.
If you have selectived Import Strategy "Import with Selection Popup" or " Import by Status and Selection Popup" in sm34 /TMWFLOW/VC_IMPS then you will get the Import Transport Requests pop-up with all change documents/transport requests. In SP05 all change documents/transport requests are deselected by default.
The reasons of this change in SP05 are:
1) Select all and Deselect all button for selective import are introduced
2) Make the default selection as empty, so that user do not mistakenly import any request. If you want all requests to be selected, please just press the select all button
19. Landscape and branch issue in change cycle
Nov 11, 2016: IMPORTANT INFORMATION FOR SP03
After implementing ChaRM Master Note for SP03 2285968 you cannot create a Change Cycle (SMIM) because field Branch and Configuration item are mandatory but not branch is available for selection, the search returns "No entries found".
Other symptoms are:
- in SOLMAN_SETUP activity Solution Documentation Content Activation => Activate Content => Activate ChaRM Content fails with the error
Solution content can't be activated for project <project_name>: Document: <cycle document number> SY-SUBRC: 1 /TMWFLOW/MISC442 Could not enable Change Request Management content for project <project_name> AI_SMMIG_GP533
See details for this sympton in SAP KBA 2422139 - Solution content can't be activated for project : Document: SY-SUBRC: 1
- the existing Cycles are not linked to Branch and Landscape, the Branches section is display only,
- the Transport Tracks Overview contains SolMan systems landscape and it shouldn’t. It should only have the systems for the track selected
- when creating an urgent change you can move to In development and create a transport request, however then the urgent change shows error "No link to cycle"
To fix the issue ensure that you have done the manual activity indicated in SAP Note 2375508 - Customer Change cycles. Pay attention because the names are slightly similar but really different.
This is documented also in SAP KBA 2436463 - Landscape and branch issue in change cycle
20. Transport request with status “Request Already Imported” in the STMS import queue
In Solman 7.2 from ChaRM task list for release and implementation cycles we don´t trigger anymore tp IMPORT ALL commands, we always trigger tp IMPORT SUBSET commands.
tp IMPORT SUBSET removes the transport request physically from the import buffer if the import was correct however in the STMS-> Overview -> Import -> Select a system ->
Import queue (result list) the transport request is not removed from the list although it is showing status “Request Already Imported”.
When ChaRM was triggering the tp IMPORT ALL command this command was making the import of the transport request and then remove physically the imported transport request from the import buffer if the import was correct. This tp IMPORT ALL command was also removing the transport request from the STMS-> Overview -> Import -> Select a system -> Import queue (result list).
So, now in SAP Solution Manager 7.2 system it could happen that you see more transport request in STMS with status “Request Already Imported”.
However there is not risk to get a transport request with status “Request Already Imported” imported again.
If you don´t not want to see these already imported transport request in the STMS-> Overview -> Import -> Select a system -> Import queue (result list) you can manually remove them by selecting “Extras -> Delete Imported Requests” or by scheduling the job indicated in SAP Note 565574 - Deleting imported entries from TMS import queue.
SAP KBA 2491680 - Transport request with status “Request Already Imported” in the STMS import queue.
21. Issues when the configuration item/ibase of the production system used in a ChaRM document changes
There are some reasons why the configuration item/ibase component of a production system using in a ChaRM document could change, like when a duplicate entry SID00001 is created in LMDB. Another reason could the that configuration item/ibase component was not synchronized with the techcnical system in LMDN ( SAP_GUID different than ULA_GUID), then after the system upgrade to SAP Solution Manager 7.2 LMDB Notification Framework job could have created a new configuration item/ibase component for the system and system:clients.
For the first case, to avoid that a new technical system SID00001 is created for an already existing technical system SID for example when the installation number change, you have to know that SLD/LMDB is able to handle an installation number change for a system, please check this SAP Notes:
If you before change (as per 1694004) the values in service market place and ask for a new license for the >>old<< system than you need only apply the settings like described here: 1727294 - AS Java/ABAP System move functionality.
If you are executing action "Extend scope" in a request for change RFC that has change documents associated to the old configuration item you will get errors like “Scope item: Installed Base component is not correct” AI_CRM_CM_MESSAGE 186 or "product XX is locked" or "Object XXX is locked", the only option is to change the configuration item for all change documents involved.
For this use the report provided in SAP Note 2447548 - Report for Replacing Ibase component in documents, multiple selection available
See more details for this report AI_MODIFY_IBASE_IN_DOC in section 1.10. How to handle your Z transaction types after the upgrade to 7.2.
22. CRM UI Search Issue in 720 SP06
After upgrade to 720 SP06, it could happend that documents created before cannot be searched in CRM UI. This is due to some code changes released in SP06 to make improve the search performance.
Please implement SAP Notes:
- 2713359 ChaRM:performance improvement and adjustment in search document
- 2595149 ChaRM CRM UI Search without criteria excludes RfCs without cycle assignment
As you can see in these SAP Notes table TSOCM_CR_CONTEXT content is now checked for each documents.
23. Shortdump DBSQL_TABLE_UNKNOWN for table /SDF/TMW_ADM occurs in phase CHECK4NOTES_TOOL_SHD2 and RUN_RSAIMMERGE_UPG_SHD
The same dump DBSQL_TABLE_UNKNOWN for table /SDF/TMW_ADM could happen also in phase RUN_RSAIMMERGE_UPG_SHD (main program RSAIMMERGE_UPG_SHD) if additionaly to the two SAP Notes indicated before the SUM SP and patch level used is too old (compilation date < 12.2017), this is documented in KBA 2663234.