ChaRM: system with client 001 is not a productive instance (error in ChaRM project)

[Former Member]

Hello,

we have some running projects in our Solution Manager 7.1 (SPS 10) ChaRM and for example the project W12345 use the logical component "Z_CRM". Because of an CRM upgrade we changed the product version of the logical component "Z_CRM" after the upgrade of the whole landscape was finished.

Now we get error messages in our projects that the CRM system with client 001 is not a productive instance. Further there's not possible to transport through the CRM landscape via ChaRM.

Is it possible that the change of the product version for the logical components removed the CRM system in our running projects?

How can we reassign the CRM system to our running projects?

Thank you for your help!

[rishav54]

Hi,

Please check if below can help you.

http://scn.sap.com/people/dolores.correa/blog

Changes in the logical components of a project where Charm is already activated 

Please never add or remove Logical Components for active project cycle, this is always dangerous.                                              

If you would like to add/remove Logical Component to project landscape or to manually adjust systems (change systems and roles) included in exiting Logical Component for active project cycle after the task list generation, I would recommend always follow the following steps:                                     

• Close the current project cycle
• Add/remove Logical Component
• Generate a new project cycle

Any change in the TMS configuration, in the transport routes for example, will be handling in the same way.

NOTE:   When you refreshed the managed system with development role them you need to follow the same steps, closing the current MC and opening a new one or work with a new maintenance project directly. This must be done to avoid problems with the CTS ID project attached to the IMG project.

When you refresh your development managed system, the number range for CTS projects in your DEV system is refreshed to, but that old information is still used in your solman system, closing the cycle and re-creating a new one will generate a new CTS project.

Check in table /TMWFLOW/PROJMAP that CTS_ID projects are always unique.

The task list is generated with help of some tables:

/TMWFLOW/TTRCKHC transport track header                                                   

/TMWFLOW/TTRCKEC transport track entries                                                  

/TMWFLOW/CMSCONF all systems in the task list                                             

A transport track contains all systems belonging to exact one development system.                                                                       

'Belonging' means: they are linked by TMS transport routes.                               

'Development system' means: the systems have the role type 'D' in the Solution Manager (SMI) project.                                                           

'All systems' means: they are linked by TMS transport routes and they are included in the SMI project.                                                          

These three tables are built up when you define a SMI project and mark it as relevant for the Change Request management.

If you change the SMI project or the TMS transport routes after the generation of the task list, you will have to complete the task list and generate a new one.

Why? when systems in the logical component of the SMI project or TMS transport routes has been changed after the generation of  the task list, tables /TMWFLOW/TTRCKHC and /TMWFLOW/TTRCKEC will be updated partly, the tables will be updated in that way that new entries will be created. The new entry in the header table /TMWFLOW/TTRCKHC will get the 'active' flag    , and the old entry will remain, but get the 'Completed' flag. The task list will go on working with the old entries. But if you complete the task list and generate a new one, this will use the new entries.

Regards

Rishav