## 13.2.8.3.3  User Management
## User Types
It is often necessary to specify different security policies for different types of users. For example, your policy may specify that users who perform their tasks interactively have to change their passwords on a regular basis, but not those users who perform their tasks using background processing.
The user types that are required for SAP Collections Management include:
- Individual users:
- For each individual user in your system, you need dialog users for the following purposes:
- To use the system via SAP GUI for Windows
- If you use SAP Collections Management in a multiple system scenario and the RFC destinations used use a Trusted/Trusting system relationship, calls to the other system are performed using the current user from the calling system. Therefore, for each user a valid user must also exist in the target system.
- Technical users:
- Background users can be used for processing in the background.
- If you use SAP Collections Management in a multiple system scenario and the RFC destinations concerned are configured such that they do not use a Trusted/Trusting system relationship, you need the following technical users for the RFC destinations:
- Communication users are used for synchronous and asynchronous BAPI calls (IDocs).
- Dialog users are used for dialog calls that take place remotely in the other system.
## Standard Users
If you use SAP Collections Management in a multiple system scenario and there is no Trusted/Trusting system relationship between the systems involved, you have to configure corresponding users for the ALE/RFC communication between the systems involved.
Note that in SAP Collections Management , asynchronous BAPI calls (IDocs), synchronous BAPI calls, and dialog calls take place between the systems involved. There are calls from the Collections Management system to the system for Accounts Receivable Accounting and vice versa.
The following table shows the standard users required if you use SAP Collections Management in a multiple system scenario and there is no Trusted/Trusting system relationship between the systems involved.
| System                                | User ID            | Type                | Password                                                                         | Description                                                                                                                                                              |
|---------------------------------------|--------------------|---------------------|----------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Collections Manage- ment system       | Example: ALE-DIAG1 | Dialog users        | The user ID and pass- word are stored in the RFC destination for the connection. | This user is used for dialog calls from the Accounts Receivable Accounting system in the Collections Man- agement system.                                                |
| Collections Manage- ment system       | Example: ALE-COMM1 | Communication users | The user ID and pass- word are stored in the RFC destination for the connection. | This user is used for synchronous BAPI calls or asynchronous BAPI calls (IDocs) from the Accounts Receiva- ble Accounting system in the Collections Man- agement system. |
| Accounts Receivable Accounting system | Example: ALE-DIAG2 | Dialog users        | The user ID and pass- word are stored in the RFC destination for the connection. | This user is used for dialog calls from the Collections Man- agement system in the Accounts Receivable Accounting system.                                                |
| Accounts Receivable Accounting system | Example: ALE-COMM2 | Communication users | The user ID and pass- word are stored in the RFC destination for the connection. | This user is used for synchronous BAPI calls or asynchronous BAPI calls (IDocs) from the Collections Man- agement system in the Accounts Receivable Accounting system.   |
Create the users required and enter them in the corresponding RFC destinations. You can assign user IDs as required. The user IDs above are merely examples.