3366251 - Urgent Change loses its link to Request for Change when working with Release Cycles

• You are working with SMRE Release Cycles.
• You have a RfC with several types of Change Documents including Urgent Changes.
• You set Release cycle to Hypercare.
• RfC and all Change Documents but Urgent Changes are now linked to the successor Release.
• Urgent Change loses its link to RfC and remains linked to the original Release.

SAP Solution Manager 7.2 as of SP06

According to SAP Note 2503525 - ChaRM: When setting a release cycle to Hypercare phase urgent change should stay in current cycle: open urgent changes must be processed in the "Hypercare" or "Operate" phase of the current cycle. They should not be handed over to the successor cycle. 

This is standard and expected behavior. When setting the original Release cycle to FINI status, the Urgent Changes are also transferred to the successor Release and it should be possible to reassign them to original RfC using the Related Document field of the Urgent Change.

SAP Note 2503525 - ChaRM: When setting a release cycle to Hypercare phase urgent change should stay in current cycle

SAP Note 2830558 - Link Change Document directly to Request for Change or IT Requirement

UC, RfC, Solution Manager, ChaRM, break, link, lost , KBA , SV-SMG-CM , Change Request Management , Problem