## 13.2.8.2.3  User Management
## User Administration Tools
The table below shows the user management tools for SAP DisputeManagement .
User Management Tools
| Tool                                                                 | Detailed Description                                                                                                    | Prerequisites   |
|----------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------|-----------------|
| User and role maintenance with AS ABAP (transactions SU01 and PFCG ) | For more information, see User and Role Administration of Application Server ABAP in the ABAP Platform doc- umentation. |                 |
## 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 Dispute 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 SAPDisputeManagement 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 SAPDisputeManagement 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.
For more information about these user types, see under User Types in the Security Guide for AS ABAP .
## Standard Users
If you use SAP Dispute 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 RFC communication between the systems involved.
Note that in SAP Dispute Management , asynchronous BAPI calls, synchronous BAPI calls, and dialog calls take place between the systems involved. There are calls from the Dispute Case Processing system to the system for Accounts Receivable Accounting and vice versa.
The table below shows the users required if you use SAP Dispute Management in a multiple system scenario and there is no Trusted/Trusting system relationship between the systems involved.
Standard Users
| System                             | User ID                   | Type                | Password                                                                         | Description                                                                                                                                                  |
|------------------------------------|---------------------------|---------------------|----------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|
| System for Dispute Case Processing | Example: ALERE- MOTE1_COM | Communication users | The user ID and pass- word are stored in the RFC destination for the connection. | These users are used when synchronous or asynchronous BAPI methods are called from the Accounts Re- ceivable system in the Dispute Case Process- ing system. |
| System for Dispute Case Processing | Example: ALERE- MOTE1_DIA | Dialog users        | The user ID and pass- word are stored in the RFC destination for the connection. | This user is used for di- alog calls from the Ac- counts Receivable Ac- counting system in the Dispute Case Process- ing system.                             |
| System                                | User ID                   | Type                | Password                                                                         | Description                                                                                                                                                |
|---------------------------------------|---------------------------|---------------------|----------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Accounts Receivable Accounting system | Example: ALERE- MOTE2_COM | Communication users | The user ID and pass- word are stored in the RFC destination for the connection. | These users are used when synchronous or asynchronous BAPI methods are called from the Dispute Case Processing system in the Accounts Receiva- ble system. |
| Accounts Receivable Accounting system | Example:ALERE- MOTE2_DIA  | 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 Dispute Case Process- ing system in the Ac- counts Receivable Ac- counting system.                             |
Create the users and enter them in the corresponding RFC destinations. You can assign user IDs as required. The user IDs above are merely examples.