There are two options to completely restrict
users creating Transport Requests without using ChaRM:
- SAP_CTS_PROJECT : Set the project assignment as mandatory
for a Transport Request in the managed system. This can be set either from
Solution Manager system or into Managed system directly. This attribute forces
all Transport Requests that is created must belong to a Project (i.e with ChaRM
in place - ChaRM project).
Managed System:
a. In
Transport Organiser Tool using transaction SE03.
b. Under Administration:
Display/Change Request Attributes
or you can access it directly using
report in transaction SE38 --> RSWBO006
c. Now, set
attribute SAP_CTS_PROJECT with "Attribute Required for
Requests" as "X Mandatory".
Check the following SAP Help link to get
more information about this attribute:
Attribute SAP_CTS_PROJECT
Solution
Manager System:
a. Call transaction
/n/TMWFLOW/CMSCONF
b. Check the entries in the
"Proj. Assignment" column.
c. Double click on the entry for
which mandatory Project Assignment needs to apply.
d. Change it to
Mandatory. - Authorization Object: S_TRANSPRT: If users still can create
Transport Requests manually from managed system without using ChaRM, then remove
authorization to create Transport requests in each system from all users (except
ChaRM / Service connections). In this way, users won't be able to create
Transport Requests from outside the Task list but can still work as normal in
ChaRM and create Transport Requests from the Change Document itself as this uses
RFC users.
So, remove activity 01 (create) from:
Object:
S_TRANSPRT
Activity: 01 - Create
Request Type:
CUST Customizing Requests & DTRA Workbench Requests
Check
the following SAP help link to know more information about Authorization Object:
S_TRANSPRT:
Authorization Objects in the CTS
Also check:
Authorization Objects A Simple Guide - document or Authorization Objects A
Simple Guide
To find the users having authorization
object: S_TRANSPRT, please use the following steps:
a. Transaction
SUIM.
b. Under User --> Users by Complex Selection
Criteria, execute "By Authorizations".
c. Enter Authorization Object:
S_TRANSPRT.
d. Execute.
Note: For best results, leave
one role “Z” with the object S_ TRANSPRT with the following authorizations so
that the users can Release transports, include objects from other transport and
all the usual developer tasks:
Act: 03,05,43
OBJTC: CUST,DTRA,TASK
See Also
- Notes:
2027347 -
Saving Project in the Transport Request
1150426 - Registering transport requests in ChaRM
1134993 - Checking transport
requests outside ChaRM
1861679 - Fix for project status switches for non-ABAP
systems
1288365 -
Project status switches for non-ABAP systems - SAP Help:
Setting the Project Status Switch
Thanks
Vikram