ChaRM: Global locking of transports

[Former Member]

Hi!

We are implementing ChaRM and have the following questions:

Is it possible to lock all the transports e.g. from DEV to QAS system that are not belonging to some IMG projects?

background:

CHaRM controlls only the transports within special IMG project. It means it is still possible to transport from DEV into QAS without IMG project assigment.

Thank you very much!

regards

[Former Member]

Hi.

First off you might want to set project assignment as mandatory so no new transports can be created without project assignement.

You are able to control export of those transports via project switches.

This is maintained in your satellite systems via tx: SE03 -> Display/Change Request Attribues -> SAP_CTS_PROJECT.

To avoid export of already existing transports you should revoke auth. object S_TRANSPRT.

Using ChaRM it should be still possible to release open transport requests.

You could also create one separate project for all of those transport requests and assign them to ChaRM following note 1150426.

This way - again - you have control about these requests using project status switches.

Hope this helps.

/cheers