Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-SEC-DIR (Application Component) Directory⤷
SLDAPSYNC (Package) LDAP Synchronization
Basic Data
| Data Element | LDAP_RFLAG |
| Short Description | Mapping for Creating RDN |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | LDAPFLAG | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | RDN |
| Medium | 15 | RDN Mapping |
| Long | 20 | RDN Mapping |
| Heading | 25 | RDN Mapping |
Documentation
Definition
Specifies that this attribute is the determining attribute for creating new entries (RDN attribute).
Use
You must set this indicator for exactly one mapping.
When an entry in the directory is newly created, its Distinguished Name (DN) is made up of the Basis DN (which is entered in the server Customizing) plus this attribute.
Dependencies
Example
The filter attribute and RDN will usually be different.
Example: You are performing a user master synchronization. When doing this, the attribute that contains the SAP user name (usually sapUsername) must be set as the filter attribute.
If a new entry is now to be created in the directory by the SAP system in the context of this synchronization, this will usually receive a DN that does not contain the SAP user name, but rather, for example, personnel number as the determining element.
You should therefore select the personnel number as the RDN attribute.
History
| Last changed by/on | SAP | 20020827 |
| SAP Release Created in | 610 |
