Hierarchy

⤷

⤷

Basic Data
Data Element | SEFS_D_LDAP_SERVER |
Short Description | Symbolic name of LDAP server |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | LDAPSERVID | |
Data Type | CHAR | Character String |
Length | 16 | |
Decimal Places | 0 | |
Output Length | 16 | |
Value Table | LDAPSERVER |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | LDAP_SERV | |
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | LDAP |
Medium | 15 | LDAP Server |
Long | 20 | LDAP Server Name |
Heading | 20 | LDAP Server Name |
Documentation
Definition
LDAP server for the assigned network domain.
Use
If your Enterprise File Search scenario includes file shares with access control lists, the security IDs representing users and user groups in the affected domain must be obtained from the responsible LDAP directory.
In order to access an LDAP directory you need to maintain the LDAP server configuration in transaction LDAP.
In large domains, the directory content might be distributed between multiple LDAP servers.
Dependencies
Make sure that the Base entry in your LDAP server configuration is the folder that contains the users and roles. You can test this in transaction LDAP using the Find function and the search depth 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 more than one LDAP server in transaction LDAP and in table SEFS_LDAP_DOMAIN.
Example
History
Last changed by/on | SAP | 20110908 |
SAP Release Created in | 710 |