Dependency Information for Transport Requests in Change Request Management

[Former Member]

If two CTS projects are not assigned to SOLMAN projects, it is possible to define a dependency successor/predecessor relation between two transport requests for the import order. For example I can state that I have to import TR 1 only after the TR 2.

When the CTS projects are assigned to SOLMAN projects, even though you have defined the dependency relation, this is not respected and from the Change Documents you can perform the import in the order you want.

How can I activate this check also in Change Request Management?

Thanks

Antonello

[Former Member · Accepted solution]

Hi Antonello,

I am facing the same issue can you please let me know if you have found the solution

Anand

SST

[Former Member]

Some things you could take a look on:

1) start report /TMWFLOW/CONFIG_SERVICES --> here you can define system, client and project specific locks.

2) Transaction /TMWFLOW/CMSCONF --> also some options for locks and definition of critical objects

3) Transaction /TMWFLOW/LOCKMON --> monitor screen for locked objects and requests.

This is actually not the same functionality as have it in CTS projects directly especially as the locks are removed once a request is removed. The most important thing is still missing here (or at least I haven't found a way to activate): sequence control when importing requests out of parallel projects into production (to prevent downgrading).

Best Regards,

Andy

[Former Member]

Dear Antonello,

have you found a solution (as I'm currently facing the same problem)?

Cheers,

Andy

[Former Member]

Dear.

For this you have to configure the Change Request Management then only you can do that ,

below i am sharing the document kindly go through it

http://www.service.sap.com/indtguides-->solaman4.0--->configuration

shailesh tiwari