| Info |
|---|
...
Automatic FSM user creation after role assignment in transaction SU01 is available for SAP ECC system only.
|
...
will take place when roles are assigned via transaction PFCG - this is supported by both ECC and S/4 systems and no reports need to be executed. The newest ECC versions may also require running the report. |
SAP users can be automatically added to the FSM Cloud Connector user maintenance table and transferred to SAP FSM, based on authorization roles.
SAP roles can be assigned to users in transaction SU01, tab ‘Roles’ (
| Status | ||
|---|---|---|
|
Roles relevant for FSM user creation should be maintained in the hereby described transaction - /PACG/ECM_USROL.
New users will be created with properties set for the role, including:
Company
Substactor, Plannable, Not Active
User crowd type
Permission ID
FSM user active
...
| Info |
|---|
The |
...
...
property ‘login enabled’ is always enabled for new users, however if the new user is inactive on account level, they won’t be able to log in, regardless of this flag. |
Example flow
1. In transaction /PACG/ECM_USROL role ‘SAP_BPR_EMPLOYEE-S’ is set for company 5 as relevant for FSM user creation.
...
2. The same role is assigned to an SAP user in transaction SU01.
3. After saving the user, a new entry in
...
FSM user maintenance tables is created.
4.
...
...
The new user is automatically transferred to SAP FSM.
Removal of a role
If a role is unassigned from a user in SU01/PFCG, the user will be set as ‘inactive’ in the
...
user maintenance table
...
, both on company and account levels (property ‘inactive’ and ‘FSM user active’).
| Status | ||
|---|---|---|
|
To illustrate this better: unassignment of role SAP_BC_EMPLOYEE woudn’t deactivate the user on any level. Unassignment of both SAP_BC_EMPLOYEE and SAP_BPR_EMPLOYEE-S would deactivate it on company level but not account (it’s still relevant for company 5). In this case all three roles have to be unassigned for deactivation on account level.
