Use Log Display for Central User Administration (transaction SCUL) primarily to check the status of the IDoc distribution when you change company addresses or users.
If you change a company address in the central system of a central user administration (CUA), the address is replicated and a CCLONE IDoc is sent to every child system of the CUA. If you change a user in the CUA central system, the user data is also distributed to the child systems assigned to it.
You can then see in the result list of the log display whether a user or a company address has been successfully replicated to the child systems.
The IDoc type appears as the first subentry below the user and child system node. The status of the distribution of this IDoc type is also displayed.
O: Creation or change started
A: Deletion started
G: Created or changed (green)
D: System assignment for the user deleted (green)
W: Created/changed with warnings (yellow)
E: Created/changed with errors (red)
The number of the IDoc with which the relevant data was sent, appears in the third position, followed by the short text for the status message, the date and time of the last change, and the user name of the last user to change it.
Use the System View/User View button to display the result list by user or by system. Use the Alphabetical Sequence/Sequence by Distribution Status button to sort the list.
To redistribute users or company addresses from the result list, choose Distribute. If you redistribute users, a dialog box appears, in which you determine which IDocs to send.
Process the entries in the result list depending on the distribution status displayed:
Distribution Status | What Happened? | What to do? |
---|---|---|
Distribution with Errors (red) | The IDoc could not be updated. The error messages are listed. | Correct the errors and redistribute the user or the company address. |
Distribution Unconfirmed (gray) |
The IDoc was not processed by the child system.
|
Use Status Monitor for ALE Messages (transaction BD87) to check the distribution status of the IDoc in the central system and in the child system. Was the IDoc sent from the central system? Use Status Monitor for ALE Messages (transaction BD87) to check the central system for message types CCLONE (for problems with the distribution of company addresses) or USERCLONE (for problems with the distribution of users IDocs that were hung up). From this transaction you can manually resend the IDoc. Did the IDoc arrive in the child system? Use IDoc Tracing (transaction BDM2) to check the central system for message types CCLONE and USERCLOSE. The partner number of the reciever is the logical system name of the target child system. Did the child system process the IDocs? Use Status Monitor for ALE Messages (transaction BD87) to check the child system for message types CCLONE and USERCLOSE. |
There is an error in the distribution itself. |
Check whether central user administration is correctly installed and whether the RFC connections, including the system user, its password, and authorizations (see Defining Authorizations for System Users) from the central system to the child system and from the child system to the central system are correctly set up. Did the status message of the IDoc not make it back to the central system? Use Transactional RFC (transaction SM58) to check the status of the transactional RFCs. Also check the RFC connections in Configuration of RFC Connections (transaction SM59). Sometimes after a system copy the RFC connections still point to the previous central system and not the current one. |
|
Distribution with Warnings (yellow) | The IDoc was updated, but there are warnings. |
Check the messages and remove the cause of the warnings. Redistribute the user or the company address. |
Distributed Error-Free (green) | The IDoc was updated. | None |