SAP Knowledge Base Article - Preview

2696057 - Duplicate DGP conflicts when moving a change document to status "To be tested" if a DGP conflict is detected


You use Change Request Management (ChaRM) to manage your transport distribution, and you enabled Downgrade Protection (DGP) check for your transports.

You are working with an urgent change document or a normal change document where SOCM COPY_ALL_ENH is configured and this change document contains a transport request that has a DGP conflict at release. You can see this conflict in the Transport-Related Checks assignment block, Downgrade Protection tab.

When executing action "Pass urgent/normal change to test" developer will get a first Downgrade Protection- Detailed Check Results popup of type Downgrade Warning caused by Released at Change Level.

Developer can ignore this conflict at release in the Downgrade Protection- Detailed Check Results popup when executing the action. However the action will fail and the document will remain in "In development" status.

Then IT operator, Change Manager or Administrator needs to ignore the new conflict that appears in the Transport-Related Checks assignment block.

Developer needs to execute action "Pass urgent/normal change to test" again to get the change document in status "To be tested".



SAP Solution Manager 7.2


SAP Solution Manager 7.2


Downgrade Protection, DGP, Cross-System Object Lock, CSOL, urgent, ZMHF, normal, ZMMJ, COPY_ALL_ENH, Pass normal change to test, Pass urgent change to test, popup framework , KBA , SV-SMG-CM , Change Request Management , How To

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.