Ansicht
Dokumentation

RSEFS_LDAP_USER_UPDATE - Enterprise File Search: Update User Cache

PERFORM Short Reference   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Purpose

You can use this report to load and update the user cache for Enterprise File Search.

Integration

If your Enterprise File Search scenario includes file shares with access control lists, the security IDs representing users and user groups must be obtained from the responsible LDAP directory. To improve the search response time, the security IDs are buffered in a persistent cache per user and domain. The name of the cache table is SEFS_LDAP_USER. You can use transaction SE16 to display this table.

Not only users can be members of user groups. A group can in turn be a member of other groups. Therefore, recursive group resolution is required. To accelerate the update of the user cache, the group resolution is buffered in a separate cache table, SEFS_LDAP_GROUP.

Prerequisites

• Access to the LDAP server must be configured using transaction LDAP.

• Table SEFS_LDAP_DOMAIN must be maintained. You can use transaction SM30 to do this.

Features

This report updates the user cache table SEFS_LDAP_USER from the configured LDAP server.

Group resolutions are not done for each user but are taken from the user group cache table SEFS_LDAP_GROUP. If a required user group is not available in the cache yet or if the cache entry is older than 24 hours, the user group cache entry is created or updated on-the-fly.

Selection

You can select single users to be updated in the cache.

Standard Variants

If you leave the select option empty, the user cache is updated for all users of this system.

Output

You will receive statistics containing the number of updated users.

Activities

To achieve maximum search performance in Enterprise File Search, you can run this report every night in batch mode after running report RSEFS_LDAP_USERGROUP_UPDATE.

If you do not run this report every night, the required cache entries are updated on demand if they are older than 24 hours.

If the response time of your LDAP server is fast, it may be sufficient to run only report RSEFS_LDAP_USERGROUP_UPDATE every night.

You could even run neither of these reports. In this case, you must accept that the user group IDs contained in the user cache are based on a group resolution that is up to 48 hours old (24 + 24).

Example

Notes

• If you enter a select option that does not specify at least one valid user for this system, the report ends instantly with no results.

• If you enter a valid user for this system and the report still returns no results, you should check table SEFS_LDAP_DOMAIN. It could be that the specified user is valid in this system, but not in the configured LDAP server.

• If the error message "Operation failed" appears, you should use transaction LDAP to check the following:

• Select an active connector and the server assigned in table SEFS_LDAP_DOMAIN.

• Choose Log On, select the Use System User option, and choose Execute. The message "Operation successful" should appear.

• Choose Find.

• On the following screen, change the search depth to Basis Entry Only and choose Execute. If the error message "Operation failed" appears again, you should check your LDAP connection. One reason might be that the Distinguished Name of the assigned System User is not valid in the LDAP directory.

• If the users for this system cannot be found in the LDAP directory, you should use transaction LDAP to test the Base entry in your LDAP server configuration: For performance reasons, this report restricts the search depth to One Level Below Basis Entry. If you need more than one Base Entry to cover all SAP users in your LDAP directory, you can configure multiple LDAP servers in transaction LDAP and in table SEFS_LDAP_DOMAIN.

General Material Data   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Length: 4888 Date: 20240601 Time: 161732     sap01-206 ( 85 ms )