Solution Manager ChaRM Issues when Upgrading Satellite System

[Former Member]

When upgrading a satellite system that is connected to Solution Manager's Change Request Management, is there anything that we need to be aware of?

Will Change Documents still be able to go to completion (Production status) if we modify the landscape from the time the Change Document is In Development to the time it is moved to Production?

1. Normal Correction (In Development) Development (ECC 5.0) -> Quality (ECC 5.0) -> Production (ECC 5.0)

2. Landscape is changed to Development (ECC 6.0) -> Quality (ECC 6.0) -> Production (ECC 5.0)

3. Normal Correction moved to To Be Tested -> Consolidated -> Production

Will the Normal Correction be in error because the landscape changed for the iBASE?

Are there any other lessons learned that anyone has experienced with Change Request Management or Implementation during and after an upgrade?

Thank You,

Carlen

Edited by: Carlen Yuen on Jan 13, 2009 1:50 AM

Edited by: Carlen Yuen on Jan 13, 2009 1:51 AM

[Former Member · Accepted solution]

Hi,

There will not be any impact while moving to Production.

The changes are not reflected in the Ibase as only Installation number, client and SID is maintained.

Change the Logical component in SMSY, and include the new logical component in the Project.

Regards,

Subhashini.

[Former Member · Accepted solution]

Thanks Subhashini!

We had issues updating the Task List in the past. After we update the landscape and refresh the project and update the Task List, do you foresee any other problems?

Are there any additional items we should look out for? For example, we understand it is a requirement to release all transports prior to beginning the upgrade. However, since the release of the transport locks the change into the cycle for the next production move, this will present a problem if the change is not yet ready to be moved into Production. Do you have any further insight to any additional issues such as this?

Thanks again!

Carlen