on 03-31-2015 2:13 PM
Dear experts,
I would like to know if the Downgrade Protection functionality of ChaRM is capable of detecting the following conflict or not.
I have an Urgent Change Document (UC1) on which I create a transport request (TR1). In this TR1; I create one function module (FM1) and I create a program (P1) in which I use this FM1.
I release&import my UC1 to the Test system.
I then have an Urgent Change Document UC2. In that one I create a TR2. In TR2 I create a program P2 but in this program I decide to use FM1.
I believe at this moment no CSOL or DGP warning goes of; because only program P2 is entered as an object in my TR2?
When I release & Import TR2 in the Test system; everything is OK because FM1 exists there. But if I import TR2 in production, dumps will occur because FM1 does not exist in production (it is still in TR1 which is still in the Test system).
Is there anything Solution Manager can do to detect this sort of conflict?
I have the impression that this tool: is capable of detecting this as described under the title "Objects go to Production with previous versions in Acceptance" like the image shows.
Thank you for any input on this!
Kr
Joyca
Hi Joyca
It should be detected by CSOL and DGP:
Check out the following information and specifically the bullet points under overview:
Best regards
Tom
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Joyca ,
I have limited knowledge on ABAP. But my views are as below.
The FM which is created must first be made sure to be available in DEV/QA/PRD in the first place.Try to have this included in a separate transport first TR1 . And then when in P1 you include the FM with another followup transport TR2 and just leave it in QA system and then when P2 includes FM with TR3 and moved until production ,the CSOL conflict will definitely be detected between TR2 and TR3. The TR1 should be imported first in PRD to avoid the dumps then TR2 is moved second.
CSOL can detect the conflicts as per configurations done, but maintaining the dependency we will need to take care .
I hope my views are right .Experts please comment .
Regards
Sweetha Shankaravelu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am receiving the following question more and more from customers.
Is there anyone who can give me some info on this please?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Joyca,
DGP function tracks objects in TRs and in turn it also reports the conflicts in various scenerios:
1. Cross System Object Lock (CSOL)
2. Release Check (Based on CSOL)
3. Predecessor Check (Based on CSOL)
4. Imminent Check (Based on CSOL)
5. Reassign Check (Based on CSOL)
Please refer this link for details on DGP:
How to work with Change Request Management Downgrade Protection DGP - Solution Manager - SCN Wiki
Regards,
Gopal
Thank you for your reply Gopal.
I know when CSOL and DGP checks are executed.
However I wanted to know the level of detail that is possible in the conflict detection itself.
As far as I understood from various documents, CSOL and DGP will only detect a conflict if a SAME object is edited in two transport requests. I was wondering if it was also able to detect dependencies between transports, like in the example that I have written out in which a program uses a function module that is saved in another transport. As the program and the FM are different objects, I suspect that neither CSOL nor DGP is able to detect this conflict and dumps would then still occur in prd due to this (undetected) dependency...
Kr,
Joyca
User | Count |
---|---|
84 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.