Ansicht
Dokumentation

RSSOUSCO - Consistency Check of User Tables

rdisp/max_wprun_time - Maximum work process run time   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Purpose

Check of User Consistency

Some users receive error messages when sending or receiving documents.

Error message:

Various:

• Sender or receiver names are not displayed correctly.

• Users cannot send or receive documents.

• Documents are sent to the wrong users.

• Users cannot start any SAPoffice transactions.

Cause:

Inconsistency between SAP users, SAPoffice users, and address data.

Solution:

The report checks the consistency between SAP users and SAPoffice users. New users are created or old users are deleted. In addition to this, the assigned addresses from the address administration are checked and corrected, if required.

This report produces the consistency between the following tables:

SOUD -> SAPoffice: User definition
SOUC -> SAPoffice: Inverse user (SAP user)
USR02 -> SAP user administration logon data
USR21 -> SAP user administration assignment user name address key
ADCP -> BAS assignment person/address (Business Address Services)
ADRVP -> Where-used list for people (Business Address Services)

Where an INSERT/UPDATE/DELETE only takes place in the SAPoffice tables
(in the others only INSERT).

1. Check there is an office for all USR02 records -
if not, create one.

2. Check there is an USR02 (SAP USER) for all SOUD (Office)
if not, delete SOUD records – Deleted flag to 'X'.

3. Check if every SOUD has an SOUC record – if not, create SOUC.

4. Check if every SOUC has an SOUD record – if not, delete SOUC.

5. Check addresses

5.1 USRADR = SPACE
Regenerate SO_KEY -> went SOUD update
-> did not output!
5.2 USRADR <> SPACE
- Check there is an address in SAP user administration for the user
.
- Does the entry in SAP user administration match
the central address administration and the SOUD
entry? If not, the entry from the BAS is put in the
SOUD record.

Adjust the where-used lists

Important: If the TEST parameter is started with 'X'
then the changes are not executed on the
database. For technical reasons
the address data is not checked.

If the TEST parameter is executed with ' ', then
all displayed changes
are executed on the database.
This may take some time.

Output

Example

CL_GUI_FRONTEND_SERVICES - Frontend Services   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 3080 Date: 20240520 Time: 104407     sap01-206 ( 28 ms )