Set Up Field Distribution Parameters

Use

If you are using Central User Administration (CUA), you can use the distribution parameters in transaction SCUM to determine where individual parts of a user master record are maintained.

In the central system
Locally in the child system
In the child system with automatic redistribution to the central system and the other CUA child systems

Every input field of the user maintenance transaction SU01 has a field attribute that you set once in the central system with transaction SCUM during Customizing. As far as possible, you should then not change the field maintenance indicator at all.

Caution

If you later change the distribution from Local or Proposal to Global or Redistribution, data inconsistencies can occur.

You must be particularly careful when removing inconsistencies, since data is lost when you switch system-dependent parameters from local to global maintenance and then distribute the users again. The distribution creates the central system status in all child systems. If you have previously maintained system-dependent data, such as the user assignment of roles, this data is unknown to the central system. This means that when you distribute the central system entries, you overwrite the role assignments of the child system. This system-specific data is therefore permanently lost.

To re-create data consistency after changing the field distribution parameters, proceed as follows:

To maintain cross-system parameter (such as printers) globally rather than locally, set the parameter appropriately and then redistribute the users from the central system to the child systems. This means that the central system status is adopted in all child systems.

Caution

To maintain system-dependent parameters (such as role or profile assignments) globally rather than locally, you must not redistribute the users. Instead, you must remove the CUA and set it up again, so that you can copy the users and their system-specific data from the child systems into the central system again. After completely removing the CUA and setting it up again, the field distribution parameters are set to Global by default. Check these settings before you transfer the users again with transaction SCUM.

The only exception to this is the Locks tab. You can change the indicators on this tab at any time without any risk.

Procedure

Log on to the central system (in this example, ADM, client 070).

In the Implementation Guide (IMG, transaction SALE), choose Start of the navigation path

Modeling and Implementing Business Processes Next navigation step

Predefined ALE Business Processes Next navigation step

Cross-Application Business Processes Next navigation step

Central User Administration Next navigation step

Set Distribution Parameters for Fields (transaction SCUM) End of the navigation path

The system displays the User Distribution Field Selection screen, with tab of the fields whose distribution parameters you can set. To display additional fields, choose page down.

You can select the following indicators on the tab:

Global	You can only maintain the data in the central system. The data is then automatically distributed to the child systems. These fields do not accept input in the child systems, but can only be displayed. All other fields that are not set to Global accept input both in the central and in the child systems and are differentiated only by a different distribution after you have saved.
Local	You can only maintain the data in the child system. Changes are not distributed to other systems.
Proposal	You maintain a default value in the central system that is automatically distributed to the child systems when a user is created. After the distribution, the data is only maintained locally, and is not distributed again, if you change it in the central or child system.
RetVal	You can maintain data both centrally and locally. After every local change to the data, the change is redistributed to the central system and distributed from there to the other child systems.
Everywhere	Note The option Everywhere is relevant only for Lock and for Logon Data → Initial Password. You can maintain data both, centrally and locally with the following consequences: Local changes in a child system are not distributed. The behaviour is exactly the same as for indicator Local. Changes made in the central system can be distributed to selected systems. Note Compared to option Global, the changes are not distributed automatically in this case. The Everywhere indicator only makes sure, that a distribution function is available in `SU01` in the central system. To distribute the changes you have to go to transaction `SU01` in the central system to actively perform the distribution step. It is not possible to distribute the changes using respective BAPIs! (See below).
HR/BP	This data cannot be maintained at all by Central User Administration. Maintenance autonomy for this data resides either with HR or the business partner. For further information about maintaining address data for users with business partner assignment, see SAP Note 2558350 .

To maintain the other parameters, too, switch to the other tab. The tab corresponds to those of user maintenance.
Save your entries.

Logon Data Tab

On this tab, you can assign the indicators Global, Local, Proposal, and Redist to all entries. However, you can only assign the indicator Everywhere to the initial password. With this setting, the administrator of the central system can set the initial password for a user system-specifically, and the administrator of a child system can set the initial password locally.

Setting Initial Passwords

However, there is no BAPI_USER* function module, that is able to realize all features of transaction SU01 regarding the setting of initial passwords. For example, it is not possible to distribute an initial password to several or all child systems using a BAPI_USER* function module. BAPI_USER_CHANGE can change the initial password always only for users in the current client and under the following conditions:

If the SCUM indicator is set to Global, the function call can change the initial password only for users in the central system. Password changes for users in child systems are not possible.
If the SCUM indicator is set to Everywhere, the function call can change the initial password for users in both, central system client and child system clients.

The SCUM indicator Proposal has the same impact on BAPI_USER_CHANGE as indicator Everywhere.

Locks Tab

You can control the distribution of lock data on this tab, and therefore determine which locks can be set and/or reset in which systems. When you reset locks, you must pay close attention to the lock indicators in the user master record that can be combined in any way you choose, and the functions available in this system, so that you can set the indicators on the Locks tab appropriately.

The following functions are available in the respective systems:


Lock globally	This function is only available in the central system. The request to lock or unlock is sent to all child systems and performed there.
Unlock globally	This function is only available in the central system. The request to lock or unlock is sent to all child systems and performed there.
Unlock incorrect logon globally	This function is only available in the central system. The request to lock or unlock is sent to all child systems and performed there.
Lock locally
Unlock locally	This function attempts to remove all three possible lock indicators: Locked due to incorrect logons, global lock, and local lock.
Unlock incorrect logon locally

Selection on the Lock Tab

Field	Global	Local	Everywhere
Unlock globally Controls the removal of a global lock	Removal of a global lock using the Unlock globally function is allowed.	not possible	not possible
Lock globally Controls the setting of a global lock	Setting of a global lock using the Lock globally function is allowed.	not possible	not possible
Unlock locally Controls the removal of a local lock	not possible	Removal of a local lock using the Unlock locally function is allowed.	Removal of a local lock using the unlock locally function is allowed and Removal of a local lock using the unlock globally function is allowed.
Lock locally Controls the setting of a local lock	not possible	Setting of a local lock the using the Lock locally function is allowed.	not possible
Unlock incorr. logon Controls the removal of a lock due to incorrect logon attempts	Removal of a lock due to incorrect logon using the Unlock globally function is allowed. Local locks can be removed by clicking button Unlock globally (F9) in the central system. It is not possible to remove a local lock only in one single child system.	Removal of a lock due to incorrect logon using the Unlock locally function is allowed. Local locks can be removed by clicking button Unlock locally (F9) in the child system.	Removal of a lock due to incorrect logon using the Unlock locally function is allowed and Removal of a lock due to incorrect logon using the Unlock globally function is allowed. Local locks can be removed either in the central system or in the child system.

Recommendations for Other Fields

Field	Setting
Printer	Proposal
Parameter	Proposal
Group (Gen.)	Proposal
Fields for data that the users maintain themselves	Redistribution