cancel
Showing results for 
Search instead for 
Did you mean: 

Active Directory cn field not updated from sap HR using ldap.

Former Member
0 Kudos

Hi,

Apologies if this is in the wrong forum area.

I am using the LDAP facility to create and modify Active Directory records from sap HR. Initially, the name field cn that was coming across into AD was in the format of the logical system and employee number, eg, RD4CLNT22000000711.

I then implemented the BADI HRLDAP_ATTRIBUTES which then changed this name field cn in the active directory listing to the format; surname, forename.

It works fine when I create a new user, however the problem comes when I update the persons name in the sap hr module. The data that comes across into Active Directory shows the change to the persons surname sn, forename and displayname fields is there but the cn field is still showing as the previous name.

In short, when a new user is created, the cn field in active directory is correct

(surname, forename) but when the employee’s name is modified, that change is not brought across to the cn field even though the surname, forename and displayname fields are updated correctlyon AD.

We are on release 4.70.

Anyway, if anyone could help I would be very grateful.

Thanks

David

Accepted Solutions (0)

Answers (3)

Answers (3)

muhammad_sohail
Participant
0 Kudos

Hi David,

I am also facing the same issue. Would you please let me know how you have solved this?

Thanks.

Sohail

Former Member
0 Kudos

Hi

The problem it is causing us is that the cn field is incorrect and does not mirror the change in sap HR, therefore the Active Directory entry for the employee is not totally accurate.

When an employee changes their name in SAP HR - usually their surname, we would then want to update the employee’s active directory account to show this change and this includes the cn field also. At the moment the firstname, lastname fields do get updated with the change so we would want the cn field to show this as well otherwise the cn field would be incorrect and not match up with the employee's AD firstname & lastname fields.

Dave

former_member273222
Participant
0 Kudos

What problem is this causing for you? Should HR be changing the cn in active directory every time an employee's name changes?

Glenn