Tracking the use of an object in several transport requests

[artemzhegalin]

Hello, SAP gurus.

CSOL and DGP can track dependencies when an object is changed in two or more transport requests. But there is a simple situation when CSOL and DGP will not help us:

1. Developer 1 creates new function module and saves it to TR1;
2. Developer 2 uses that module (but does not change anythig in it) and saves his work in TR2.

Now if TR2 will be imported first - we will have a dump in our target system.

Does SAP SM have some standard functionality for solving such situations?

BR,

Artem

[Former Member]

Hi,

The example here is not for CSOL or DGP.

The Object in TR1 is just used in TR2 so it does fall under either CSOL ( as the object is not being worked upon in TR2) and neither in DGP( even if you move the TR1 later it will not be overwriting any object).

This is the case of sequencing the TR.

If you are moving the TRs togther then solman takes care of it( Import All functionality).

But if not then you have manually take of the sequencing.

Regards

Abhishek

[dillipkumar_r]

Hello Artem,

I agree with Abhishek.

This is with the developer, the release sequence should be properly maintained while releasing the transport this is very important for ChaRM, CSOL, DGP to help life easier.

The case you gave us is a problem with the sequencing and any tools for the matter really can't help here.

Hope this helps you.

Regards,

Dillip

[rishav54]

Hi Artem

Yes ideally DGP checks should warn you about the sequence it should follow.

Thanks

Rishav

[artemzhegalin]

Hello, Rishav.

The idea of DGP is to track objects that are changed. But when we just use FM (that is stored in TR1) for other development (TR2) - there will be no conflicts between requests.

BR,

Artem

[rishav54]

Hi Artem

There is predecessor check functionality of DGP and it should work in this scenario.

However it will always depend on the way you release your transport it will be imported to production in the same sequence. But if the sequence you had released is not correct than DGP should warn you.

Thanks

Rishav

[Former Member]

Hi,

Predecessor check wont work here as there are no conflicts identified.

Hello, Rishav.

The idea of DGP is to track objects that are changed. But when we just use FM (that is stored in TR1) for other development (TR2) - there will be no conflicts between requests.

BR,

Artem

• Predecessor check (based on cCTS)
  The system can detect conflicting predecessors, that is, preceding transport requests containing conflicts, at the time of importing transport requests or transport of copies to the production or quality assurance system.

Regards
Abhishek

[rishav54]

Hi,

Oh surprised same object is being used and if not conflicts identified then yes DGP can not work here.

the sequence of release from the system is the key.

thanks

Rishav