The report RSBCS_USER_DELETE_JOB is used to deletes BCS users that have already been flagged as deleted.
Background
There is exactly one BCS user for each SAP user. These users are used to send messages, for example; the BCS user is set as the sender of the message. If the SAP user is deleted, the BCS user is flagged as deleted, but is retained. This is done so that information about the sender of the message remains available.
However, an SAP user can be created and then deleted without the corresponding BCS user having ever created, sent, changed, or forwarded a message. This BCS user is not used, but remains in the database, flagged as deleted.
Features
You use the report RSBCS_USER_DELETE_JOB to delete BCS users that are flagged as deleted. The entries from the SOUD and SOUC tables are deleted. The personal address is also deleted from address management.
Depending on the selection screen settings, the report checks whether the BCS user is still in use. It checks whether the user is used as an owner, creator, or changer of an SAPoffice document, or as a sender, recipient, or forwarder of a message.
Selection
On the selection screen, you can restrict the selection of the BCS user by name, ID, or creation date.
You use the ‘Delete Despite Use’ flag if you want to delete BCS users that are flagged as deleted, but are still used. If this flag is set and the detailed output is inactive, the usage check is skipped. This should significantly reduce the runtime of the report.
The report also contains the following three parameters:
- Package size
- Number of table records that are read from SOUD and processed at the same time.
- Maximum Number of Hits
- Maximum number of BCS users to be deleted. You can set this to restrict runtime.
- Detailed Output
- Overview of the BCS users that are deleted or are to be deleted after the report has run.
- Test Mode
- If this field is selected, no database changes will be made.
