How to prevent creation of TRs outside of CHARM

[former_member210667]

Hi,

We had closed the project switch from the project,but user are still able to create the transport from the development system.

what is the role for "show project status  switch "?

Regards,

Neni

[Aravindkumarj]

Neni,

Please share screenshots of your settings from satellite development systems.

a. SE03 -> Display change attributes

b. Project status switches

Thanks,

Aravind Kumar

[former_member210667]

sorry,i dont have access.What should be the configurations ?

[VJain]

There are two options to completely restrict
users creating Transport Requests without using ChaRM:

1. 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.
   
   
   
   
2. 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

[VJain]

Also check this note:

1528657 - Workaround when SolMan system is temporarily unavailable

[former_member210667]

So your saying ""show project status  switch " doesn't matter if you open or close to create the transports right?

[Miguel_Ariño]

It matters once you have the user authorizations correctly configured.

Best regards,

Miguel Ariño 

[luigi_co]

Hi Neni,

The CTS project switches are used to prevent TPs being created manually UNDER the CTS project. It does not prevent TP creation outside of ChaRM.

To prevent TPs being created outside of ChaRM you can follow the instructions shared above, which is to use transaction SE03. This would not really prevent TP creation outside of ChaRM, but would require TPs to have a CTS project assigned. This way, all TPs will have CTS projects assigned which would in a way "prevent" TPs not to be created outside of ChaRM.

Regards,

Luigi

[former_member210667]

If i put project switches off- between QA to PROD for urgent change or normal changes,can we still move the transports?

[TomCenens]

The switches are for TMS purpose only so if you switch everything off, you can import using CHARM only ~ through the task list, or through action on the change document or through import job that uses CHARM as long as it's CHARM triggering the import it will work

TMS won't work so in transaction STMS, an administrator wouldn't be able to import that request using the import button (truck) nor using a TMS job that is scheduled in SM37

[VJain]

Hi Neni,

Please check and follow my following KBA:

2203520 - Restrict users to create Transport Request using CHARM only

Thanks

Vikram

[former_member210667]

Vikram

My question is---> Even Project is locked,still the user is able to create  the transports from charm transport,please let me know how  it will be possible?

[Aravindkumarj]

Hello Neni,

Project status switches from the project only restricts users from creating transports and assign the CTS_PROJECT ID generated during the Solution Manager project creation.  It doesn't prevent users from creating transports outside ChaRM.

For your issue you have to

a. Logon to satellite development system

b. Call transaction SE03 -> Display/Change Request Attributes

c. Goto edit mode and double click on 'SAP_CTS_PROJECT'

d. If you have multiple source clients ie Customizing client, Client for ABAP changes and Security ,      then choose the value 'Mandatory' in the drop down 'Default for all clients'. If you want to restrict for      lets say one specific client, then enter the client number in the Client column below and make sure      the check box 'Required' is checked against it.

e. Save the changes.

Best Regards,

Aravind Kumar Jagannathan

[former_member210667]

Hi,

Thanks for the reply.

Even Project is locked,still the user is able to create  the transports from charm transport,please let me know how  it will be possible?

Regards,

Neni