You can map specific SAP data fields to directory attributes (or directory attributes to SAP data fields) using a function module. You specify the function module to be used with transaction LDAPMAP.
In transaction LDAPMAP, the system first displays the Mapping Overview screen; you perform the mapping on the Mapping Details screen.
On this screen, you enter the data that the function module requires for the mapping:
The field (or fields, if an attribute is mapped to more than one field), the name of which is created from the table and the field names
The attribute (or attributes, if a field is mapped to more than one attribute)
The parameter (Separator)
We deliver the following function modules (linking type) with the following possible parameters.
Function Module |
Parameter Value |
Additional Notes |
Example |
---|---|---|---|
MAP_DEFAULT |
none |
Standard linking type that maps one field to one attribute |
SAP data field BAPIBNAME is mapped one-to-one to the directory attribute cn. |
MAP_CONCAT_CHAR |
Separator (such as -, /,; or SPACE*) Only the parameter specified in the first line is taken into account. |
Maps two directory attributes to one field. |
The directory attributes givenName and sn are merged into the field FULLNAME during import to the SAP system. |
MAP_SPLIT_CHAR |
Separator (such as -, /,; or SPACE*) Only the parameter specified in the first line is taken into account. |
Maps two SAP data fields to one directory attribute. |
The directory attribute telephoneNumber is split into TEL1_NUMBR and TEL1_EXT when imported to the SAP system. |
MAP_UNION |
none |
Creates a union of values from more than one data source. |
Each system stores the role assignment in its own attribute. To show all assigned roles in your SAP systems, the MAP_UNION function module reads the values of all of these attributes and outputs the complete list. |
* To use a space as a separator, you must enter SPACE.
After you have created the mapping, it is displayed on the Mapping Overview screen.
You set the mapping indicators, which specify the purpose of the mapping, on this screen. This is required above all in special cases, such as if an SAP data field is used in two mappings and is therefore mapped to two different attributes of the LDAP-compatible directory service. The contents of the SAP data field BAPIBNAME in the USERNAME structure can be written to various attributes during export. When importing the cn and sapUsername attributes, on the other hand, you must define which of these attributes is to fill the SAP data field BAPIBNAME in the USERNAME structure.
Number |
SAP Structure |
SAP Data Field |
Attribute |
Import Mapping Indicator |
Export Mapping Indicator |
---|---|---|---|---|---|
1 |
USERNAME |
BAPIBNAME |
cn |
x |
x |
2 |
USERNAME |
BAPIBNAME |
sapUsername |
- |
x |
3 |
ADDRESS |
FULLNAME |
givenName |
x |
- |
3 |
sn |
||||
4 |
ADDRESS |
FIRSTNAME |
givenName |
x |
x |
4 |
ADDRESS |
LASTNAME |
sn |
x |
x |
You then set the synchronization indicators, which determine which entries of an object are synchronized.