How to prevent creation of TRs outside of CHARM Task List

[Former Member]

Hello Experts,

Can you please advice how I can stop creation of transport requests outside of CHARM Task List. I need my users create Transport Requests only via CHARM Task List.

Looking forward for your help.

Thanks a lot in advance

123

[Former Member · Accepted solution]

There are two options, if you want to be completely secure you can do both:

1. You need to remove authorisation to create Transport requests in each system from all users (except ChaRM / Service connections). You can use SUIM to search for and then remove them:

Object: S_TRANSPRT

Activity: 01 - Create

Request Type: CUST Customizing Requests & DTRA Workbench Requests

2. In Transport Organiser Tools SE03, in Administration:Display/Change Request Attributes. Set SAP_CTS_PROJECT - Project in Change and Transport System to obligatory (X). This forces all transports created to belong to a Project (i.e with ChaRM in place - ChaRM project).

Paul

Edited by: Paul Duckitt on Nov 11, 2011 4:09 PM

[Former Member · Accepted solution]

Don't forget to create

[Former Member · Accepted solution]

Paul,

There is a way to prevent task request creation (customizing/workbench) also?

Because, sometimes it happens that a developer creates a new task to add to the original request when the charm is already in “testing” phase.

So this new task never gets attach to the original charm/ transport request.

Thanks in advance

Juan.

[former_member204161]

Hi ,

By removing S_TRANSPRT authorizations from all users , they won't be able to create transports from outside the task list but they can still do it from the Change Document itself . (because this uses the RFC users). To prevent this , you can disable the create TR/create task button using the UI authorization , enabling it only for certain users.

Even for the users having S_TRANSPRT with the right authorization , we may need to ensure that they create the TR only from the tasklist, not manually . So besides following the step 2 mentioned above , I believe we should close the CTS switch for creating transports outside of ChaRM  for that project .

Finally , an authorization object controls all the transport related actions in the tasklist , so this can be used to further restrict the users . Let me know if this helps.

Thanks,

Shaswat

[Former Member]

Thanks Shaswat,

As you recommend, I removed the object S_TRANSPRT, to all users in my DEV system the result was the expected, they can’t create new orders or tasks but they can still work as usual in ChaRM.

Note: for best results I leave one role “Z” with the object  S_ TRANSPRT with the following authorizations:

Act: 03,05,43
OBJTC: CUST,DTRA,TASK

So the users can Release transports, include objects from other transport and all the usual developer tasks.

Thanks

Juan

[Former Member]

Hi,

If you properly activated the ChaRM you must create TR either in Change transaction or tasklist.

may I knw what is outside ChaRM task list? you meant workcenter, service desk.

chk out this Note 1134993 - Checking transport requests outside ChaRM

Please update.

Thanks,

Jansi

[Former Member]

Any suggestions please?

Thank you

123