SmartChange comes with some template roles which can be used such as roles for developers, approvers, administrators:
Role name | Function | Explanation |
/RTC/TM_ADMINISTRATOR | TM Administrator | TM: Admin permissions |
/RTC/TM_ALL | TM ALL authorizations | TM: All in TM + Standard authorizations |
/RTC/TM_APPR1 | Content approver | TM-Role for approver1 |
/RTC/TM_APPR1_C_ONLY
(C, FC) | ||
/RTC/TM_APPR2 | Technical approver | TM-Role for approver2 (T, FT) |
/RTC/TM_DEV | Developer | TM-Role for developer (U, FU) |
/RTC/TM_P_MANAGER | Project manager | TM-Role for Project Manager |
/RTC/TM_RFC_HIGH
TM: Transport- and Job user TM-client
/RTC/TM_RFC_LOCAL
(AP, AU) |
/RTC/TM |
_ |
Job user
/RTC/TM_RFC_MEDIUM
TM: Transport user TM-client
SUP_APPR1 | Super content approver | TM-Role for super approver1 (CS, SC) |
/RTC/TM_SUP_APPR2 | Super technical approver | TM-Role for super approver2 |
/RTC/TM_UMODE
(ST, TS) | ||
/RTC/TM_USER_BASICS | Basic user | TM: Minimal authorization for TM user |
You can start assigning these roles to your users and copy and modify them is needed.
The internal authorization object ‘ZRTC_TM’ is delivered with Transport Management. This authorization object has four authorization fields which enable to assign authorizations individually to each action by project, destination, and transport level. Depending on the role distribution, authorizations, and roles can be created and assigned to these objects. Additionally, a minimum of SAP authorizations, which are all contained in the provided role ‘/RTC/TM_USER_BASICS’, is to be assigned to each user. There is a value list for the authorization field ‘/RTC/TM_AC’ of each action in Transport Management. In addition to the individual authorizations for object ‘ZRTC_TM’ each Transport Management user additionally requires at least the authorizations of the delivered role ‘/RTC/TM_USER_BASICS’.
Example: To be authorized to grant content approvals for external requests, a user requires the activities ‘FC’ and ‘FR’ within the same authorization. It is not sufficient to have both activities in one role if these are assigned to two different authorizations.
...
Here are all activities in detail:
Activity | Description |
AB | Administration: Business Add-Ins |
AC | Administration: package definition |
AD | Administration: Logical destinations |
AE | Administration: Loader |
AF | Administration: Switcher |
AG | Administration: System(Transport) groups |
AL | Administration: Transport levels |
AM | Administration: Maintain manual/documentation |
AO | Administration: Online Monitor |
AP | Administration: Projects |
AQ | Administration: System queues |
AR | Administation: Reset TransportManager |
AS | Administration: Security and Quality |
AT | Administration: Common settings |
AU | Administration: User groups |
AV | Administration: Dependencies |
AW | Administration: Maintenance of allowed critical objects |
C | Own requests: Signature (content) |
CP | Create new packages |
CS | Supersigner own requests (content) |
D | Own requests: Delete |
DP | Delete Personal Queue |
FC | Foreign requests: Signature (content) |
FD | Foreign requests: Delete |
FH | Foreign requests: Status change to Workflow History |
FI | Foreign requests: Import |
FP | Foreign requests: Confirm Sync for Requests |
FR | Administration: Requests of foreign systems |
FS | Foreign requests: Status change |
FT | Foreign requests: Signature (technical) |
FU | Foreign requests: Insertion into TransportManager |
FV | Foreign requests: Analysis of Requests |
FX | Foreign requests: Ext. Status change from 'Curr.' to 'Queue' |
GQ | Generation: System queues |
H | Own requests: Status change to Workflow History |
I | Own requests: Import |
IR | Foreign requests: Repeat Import |
IT | Import Tracking |
MA | Mass approval |
OP | Maintenance of /RTC/TM_OPT table |
P | Own requests: Confirm Sync for Requests |
P1 | Create Import Proposal |
P2 | Delete Import Proposal |
P3 | Approve Import Proposal |
PA | Package approval |
PD | Delete packages |
PM | Package maintenance |
RI | Own requests: Repeat Import |
RT | Export of a request without adding into TM (BAdI) |
S | Own requests: Status change |
SC | Supersigner foreign requests (content) |
SJ | Scheduling of special requests |
SL | Signature for emergency transports |
ST | Supersigner foreign requests (technical) |
T | Own requests: Signature (technical) |
TA | Value assignment to TM Attributes |
TS | Supersigner own requests (technical) |
TT | TM-Tools: Administrator |
U | Own requests: Insertion into TransportManager |
UE | User Exit maintenance |
UM | Maintenance of the Unconditional Mode |
V | Own requests: Analysis of Requests |
X | Own requests: Ext. Status change from 'Curr.' to 'Queue' |