Downgrade Protection in ChaRM

[Former Member]

Hi,

Anybody knows how and where to configure the downgrade protection to appear in the tasklist?

We have already configured the cross system object lock and downgrade protection and both of this are working for the two options below.

• Manually - You can trigger downgrade checks from the Downgrade Protection assignment block. (CRM UI)
• Automatically - Downgrade checks are triggered automatically when releasing transport requests, importing a transport, or when reassigning a change document. (CRM_UI)

However, we are unable to find the program of downgrade protection to be inserted in the tasklist. Based on the link below, we should also be trigger the downgrade check through the tasklist.

Also, I want to understand know how the downgrade protection will work in the task list.Is the "downgrade protection check" a separate action in the task list? or will the "downgrade protection check" appear automatically when I import a transport via task list?

Thanks!

Source:

http://help.sap.com/saphelp_sm71_sp05/helpdata/en/6a/2347390517468db54e767b122110a1/content.htm

[former_member187281]

For a future reader as I believe Jon resolved this issue long time ago.

1. It is an assignment block that is to be added to the maintenance cycle, project cycle, normal change, urgent change, and defect.

In principle, when you try to save for the first time an object in a transport that does exists in another transport that has not reached Production, you receive the first warning or you may receive an error message, depending how you configured DGP in  /TMWFLOW/CONFIG_LOCK.

• The Error Status will not allow you to proceed until you move that other transport to production and its entry is removed from transaction /TMWFLOW/LOCKMON.
• The Warning will allow you to continue, but then additional warnings will happen when you try to move the latest transport before the earlier one reaches Production, warnings that happen as the change document changes statuses.  You will need to open the assignment block mentioned above in the specific change document or in the maintenance level webui to launch DGP Check, so that being aware of what you are about to do, you can still ignore the warning and proceed.
• We tested 2 scenarios and this is what we found:
• If the changes belong to the same project, when you move the latest transport to production, that transport will remain in the production import buffer, so then when the whole project goes live, all transports of that project are applied in the correct order, which resolves the issue. It is similar to what happens when you move an Urgent Change.  Good approach SAP!!!
• If the changes belong to different projects, it is more complicated as you do not only need to ignore the DGP warning at the change document level, but also at the maintenance cycle level when the project is to GoLive.  DGP tries to avoid that you make a mess, but if you totally ignore the warnings, you are on your own, having to manually re-apply the transports in order for the objects in conflict to be chronologically correct in Production, unless the projects GoLive in the correct chronological order for the objects in conflict.
• We have not tested closing the maintenance cycle to see if what was mentioned right above, gets an additional push in order to get to a status closer to chronological correction, but being 2 different projects, that may go live at different times, it sounds unlike that SAP takes an action with regards to that at the closing of the cycle, but this is just speculation.

Jon, 2.5 years after, but it is your fault to get there into DGP so long ago. 

Happy 2016 to every one.

Juan-Carlos Garcia-Garavito