on 11-29-2013 2:53 PM
Hello together
I have a question regardings transports and risk.
Is it a risk when a user can access the STMS Transport Management System as well as the STMS_Import TMS Import queue? Or does the user actually need other rights for really performing a transport?
Thank you for your help and input.
Mike
Hi Mike,
Yes it is risk, the user shouldn't have STMS_import. The basis team will have this authorization.
Regards.
Visu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
_________________________
PS: Is it an interview question? If so please do not post here
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Mike
What type of access do you mean here - display, modify, release, etc
The transaction codes are further controlled by objects such as S_TRANSPRT and S_CTS_ADMI. You could allow users the access to see the queue but not actually import the change.
I have worked in situation where I had transport create and release from dev. I then had STMS access to import my change to QA. However, I wasn't allowed to import to Pre-Prod or Prod. STMS can also add approval steps to segregate the access.
These options depend on change and release processes for your site.
Most transport import is reserved as a Basis activity. A benefit here is to have a team responsible for verifying sequencing and transport dependencies to avoid configuration corruption, etc.
As a note, SE* transactions are not the only place to create a transport
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.