KA HCM-Dingo Interfaces

DINGO Knowledge Article Scenario: HCM Dingo Interfaces Version 1.0

Status: DRAFT

05/14/2014

2/27

Table of Contents

Change History ........................................................................................................................................................ 3

1 Objective ........................................................................................................................................................ 4

2 Target Group ................................................................................................................................................. 4

3 Trigger ............................................................................................................................................................ 4

4 Analysis .......................................................................................................................................................... 4

5 HCM2Dingo interface .................................................................................................................................... 5

5.1 HCM Import File ...................................................................................................................................... 5

5.2 Dingo Attributes ...................................................................................................................................... 7

5.3 Mapping HCM import file - Dingo ........................................................................................................... 8

5.4 Countries ............................................................................................................................................... 10

5.5 HCM2Dingo_PSCP Workflow ................................................................................................................ 12

5.6 HCM2Dingo_DEP Workflow .................................................................................................................. 13

5.7 HCM2Dingo_ACC Workflow .................................................................................................................. 13

5.8 CSVImport_IDHCM Workflow ............................................................................................................... 14

5.9 Email Notifications ................................................................................................................................ 14

6 Dingo2HCM interface .................................................................................................................................. 15

6.1 Phone numbers File............................................................................................................................... 16

6.2 Windows Domain File ........................................................................................................................... 16

6.3 Email address File .................................................................................................................................. 17

7 Dingo Web Center Changes ......................................................................................................................... 17

8 ADP2USB ...................................................................................................................................................... 19

9 Dingo2ADP ................................................................................................................................................... 20

10 Dingo.dat file ............................................................................................................................................... 21

11 CSED file (sen_personen.txt) ....................................................................................................................... 24

12 Dingo WebCenter ........................................................................................................................................ 26

05/14/2014

3/27

CHANGE HISTORY

Version Date Reason for change Edited by

1.0 Dec, 2013 Initial draft Fernando Rivera

1.0 April, 2014 Changes to the functionality Fernando Rivera

05/14/2014

4/27

1 OBJECTIVE

The objective of this document is to describe the HCM Dingo Interfaces.

2 TARGET GROUP These work instructions are intended to be carried out by:

2nd

and 3rd

-Level Support

3 TRIGGER

This job is triggered by system admin himself.

4 ANALYSIS

There are two interfaces: HCM2Dingo (get information from HCM and store it into Dingo) and Dingo2HCM (get

information from Dingo and send it to HCM).

The HCM2Dingo interface will replace the ADP2Dingo workflow and all the CSVImport workflows.

3 new Dingo Attributes were added:

igoEmployeeStatus

igoGlobalJobRole

igoAdpPersonalNumber

Dingo Web Center, ADP2USB workflow, Dingo2ADP workflow were updated due to the HCM interface.

The dingo.dat (users.csv) and SEN_personen.txt file changed due to the HCM interface.

05/14/2014

5/27

5 HCM2DINGO INTERFACE

The HCM2Dingo interface takes the HCM import file (a csv file) as input (via pscp) and create/update/LOST

Dingo entries, create/update Departments and create/update/assign Accounting Codes.

All the Dingo entries handled by this interface have fk-source equals to CSVImportHCM.

This interface runs daily at 7:30 am CET.

The HCM2Dingo Interface consists of the following workflows:

CSVImport_IDHCM: create/update/LOST Dingo entries with fk-source CSVImportHCM

HCM2Dingo_ACC: create/update/assign Accounting Codes

HCM2Dingo_DEP: create/update Departments

HCM2Dingo_PSCP: get the HCM import file

HCM2Dingo_All: execute all workflows in this order:

1. HCM2Dingo_PSCP

2. HCM2Dingo_DEP

3. HCM2Dingo_ACC

4. CSVImport_IDHCM

5.1 HCM Import File

The HCM import file is called unify_boomi.csv (formerly known as sen_output.csv).

HCM updates the unify_boomi.csv file every 4 hours at 01:30, 05:30, 09:30, 13:30, 17:30, 21:30 (Execution

time: between 1min30sec und 2min30sec)

The HCM2Dingo_PSCP workflow gets the unify_boomi.csv file from HCM via pscp and stores it in the folder

H:\HCM2Dingo.

This is the layout of the HCM import file:

Position Field Name Mandatory/

Optional

Conditions for checking

1 GID (Person Id) Mandatory 8 characters

2 Country Mandatory

3 Legal Entity Optional

4 Dingo Location Code Mandatory

05/14/2014

6/27

5 Employment Information Recent Hire Date Optional format DD/MM/AAAA or empty

6 Employment Information Termination Date Optional format DD/MM/AAAA or empty

7 Salutation Optional

8 Gender Optional Male,Female or empty

9 Local Department Name Optional

10 Cost Center Mandatory

11 Legal Entity ARE Code Optional

12 Legal Entity Legal Entity ID Optional

13 Local Job Title Optional

14 Global Job Role (Job Title) Optional

15 Employee Class Mandatory Must be any of the following

values:

Assignee

Inboud Delegates

Outbound Delegates

Expatriate

Agency/Temp

Intern

Apprentice

Contractor

Students

Trainee

Hinterbliebene

ERA Mitarbeiter (GER)

ERGTV Mitarbeiter (GER)

Employee

16 Employee Status Mandatory Must be any of the following

values:

Active

Unpaid Leave

Paid Leave

Retired

Suspended

Terminated

Furlough

17 Manager User Sys ID Optional empty, NO_MANAGER, or 8

characters

18 Custom Manager Job Relationships User ID Optional empty or 8 characters

19 Legal Manager Job Relationships User ID Optional empty or 8 characters

20 Nickname Optional

21 Preferred Last Name Optional

22 First Name Mandatory

23 Last Name Mandatory

24 Department Code Optional

25 Employment Information Previous Employee

ID

Optional

26 Local ID Optional

05/14/2014

7/27

5.2 DINGO ATTRIBUTES

These are the Dingo attributes used in the HCM2Dingo workflow:

Position LDAP Attribute Flags

1 accounting-code

2 c DONT-DEL-ATTR

3 DDN

4 department DONT-DEL-ATTR

5 e-mail-admin-domain DONT-MOD-ATTR

6 entry-date DONT-DEL-ATTR

7 expiry-date

8 fk-link-status

9 fk-source

10 fk-value

11 gender DONT-DEL-ATTR

12 gidOwner

13 givenName

14 givenNameNational

15 job-title-text

16 location-link

17 location-short DONT-DEL-ATTR

18 o DONT-DEL-ATTR

19 objectClass DONT-MOD-ATTR

20 organization-link

21 ou DONT-DEL-ATTR

22 personal-id

23 personal-title

24 send-to-scd

25 settlement-accounting

26 single-sign-on DONT-MOD-ATTR

27 sn

28 status

29 surnameNational

30 tc-key

31 user-type

32 dxrEndDate

33 dxrStartDate DONT-DEL-ATTR

34 dxrState

35 employeeType

36 superiorPersonalId

38 superiorLink

39 igoFunctionalManager

40 igoEmployeeStatus

41 igoGlobalJobRole

42 SAPPersonalnr

43 igoAdpPersonalNumber

44 representation

05/14/2014

8/27

5.3 MAPPING HCM IMPORT FILE - DINGO

The import of the data is done by the activity 020_CSVImport_IDHCM_MetaCP of the HCM2Dingo workflow.

This is the mapping between the HCM import file and Dingo:

Input Output Remarks

"CSVImportHCM" ldap(fk-source)

file(tc-key) ldap(fk-value)

"HCM-" file(tc-key) ldap(personal-id)

"OK" ldap(fk-link-status)

Calculated ldap(sn) surname international: HCM field

"Preferred Last Name" if non

empty, otherwise HCM field "Last

Name"

file(sn) Calculated ldap(surnameNational) surname international: HCM field

"Preferred Last Name" if non

empty, otherwise HCM field "Last

Name"

Calculated ldap(givenName) givenname international: HCM

field "Nickname" if non empty,

otherwise HCM field "First Name"

file(givenName) Calculated ldap(givenNameNational) givenname international: HCM

field "Nickname" if non empty,

otherwise HCM field "First Name"

Calculated ldap(c) mapping of HCM country names

(file(c)) to 2-letter ISO code.

file(o) ldap(o) Company

"Unify" ldap(ou)

file(l) ldap(location-short)

Calculated ldap(gender) Same as in CSVImportXXX

file(personal-title) Calculated ldap(personal-title) If empty then "pers"

file(department) Calculated ldap(department) If Local Department Name is

empty use Department Code

file(accounting-code) ldap(accounting-code)

file(Legal Entity ARE Code) ldap(settlement-accounting) the ARE has to be extracted from

file(settlement-accounting) field.

For example: for "SEN_425k_DE",

the ARE is "425K". Extract the

middle value between the "_". In

Upper-case.

Calculated ldap(entry-date) Same as in CSVImportXXX

Calculated ldap(expiry-date) "Same as in CSVImportXXX.

05/14/2014

9/27

if (recent hire date) >=

(Termination date) and (recent

hire data)

05/14/2014

10/27

Employment Information

Previous Employee ID value.

Calculated ldap(igoAdpPersonalNumber) Set the Dingo Attribute

igoAdpPersonalNumber with

the Local ID value. If Local ID

is empty then use the GID.

Calculated ldap(representation) "local manager in Dingo = HCM

field ""Legal Manager"" if non

empty, otherwise HCM field

""Manager User Sys ID""

For Employee Class =

""Contractor"" and

""Agency/Temp"" , the Manager

User Sys ID must go into the field

Responsible NOT into the field

Local Manager."

5.4 COUNTRIES

The countries handled by this interface are the following:

Name des Landes ISO 3166-2 ISO 3166-3

United Arab Emirates AE ARE

Argentina AR ARG

Australia AU AUS

Austria AT AUT

Belgium BE BEL

Bulgaria BG BGR

Brazil BR BRA

Canada CA CAN

Switzerland CH CHE

Chile CL CHL

China CN CHN

Colombia CO COL

Czech Republic CZ CZE

Germany DE DEU

Denmark DK DNK

Algeria DZ DZA

Spain ES ESP

Finland FI FIN

France FR FRA

United Kingdom GB GBR

Greece GR GRC

Hong Kong HK HKG

Hungary HU HUN

05/14/2014

11/27

India IN IND

Ireland IE IRL

Italy IT ITA

Japan JP JPN

Korea, South KR KOR

Luxembourg LU LUX

Morocco MA MAR

Mexico MX MEX

Netherlands NL NLD

Peru PE PER

Philippines PH PHL

Poland PL POL

Romania RO ROU

Russian Federation RU RUS

Singapore SG SGP

Slovakia SK SVK

Sweden SE SWE

Thailand TH THA

Turkey TR TUR

United States US USA

Venezuela, Bolivarian Republic of VE VEN

Viet Nam VN VNM

South Africa ZA ZAF

The countries which are going to be processed by the workflow are uncommented in the function

igoSetValidCountries of the CSVImport_User_Hooks tcl program.

proc igoSetValidCountries { countries_var } {

upvar $countries_var countries

set countries [llist]

lappend countries "AE;United Arab Emirates"

lappend countries "AR;Argentina"

lappend countries "AT;Austria"

lappend countries "AU;Australia"

lappend countries "BE;Belgium"

lappend countries "BG;Bulgaria"

lappend countries "BR;Brazil"

lappend countries "CA;Canada"

lappend countries "CH;Switzerland"

lappend countries "CL;Chile"

lappend countries "CN;China"

lappend countries "CO;Colombia"

lappend countries "CZ;Czech Republic"

lappend countries "DE;Germany"

#lappend countries "DK;Denmark"

#lappend countries "DZ;Algeria"

lappend countries "ES;Spain"

lappend countries "FI;Finland"

05/14/2014

12/27

lappend countries "FR;France"

lappend countries "GB;United Kingdom"

lappend countries "GR;Greece"

lappend countries "HK;Hong Kong"

lappend countries "HU;Hungary"

#lappend countries "IE;Ireland"

lappend countries "IN;India"

lappend countries "IT;Italy"

#lappend countries "JP;Japan"

#lappend countries "KR;Korea, South"

lappend countries "LU;Luxembourg"

#lappend countries "MA;Morocco"

lappend countries "MX;Mexico"

lappend countries "NL;Netherlands"

lappend countries "PE;Peru"

#lappend countries "PH;Philippines"

lappend countries "PL;Poland"

lappend countries "RO;Romania"

lappend countries "RU;Russian Federation"

lappend countries "SE;Sweden"

lappend countries "SG;Singapore"

lappend countries "SK;Slovakia"

#lappend countries "TH;Thailand"

#lappend countries "TR;Turkey"

lappend countries "US;United States"

lappend countries "VE;Venezuela, Bolivarian Republic of"

lappend countries "VN;Viet Nam"

#lappend countries "ZA;South Africa"

return 0

}

5.5 HCM2Dingo_PSCP Workflow

The HCM2Dingo_PSCP workflow gets the unify_boomi.csv file from HCM via pscp and stores it in the folder

H:\HCM2Dingo.

The connection parameters to get the HCM import file are stored in the Specific Attributes of the

HCM2Dingo_PSCP workflow:

Server: prodftp2.successfactors.eu

Userid: sen

Password: (see it in the workflow)

Folder: /OUTPUT

The workflow also creates a backup of the last unify_boomi.csv file, this backup file is named

unify_boomi_old.csv and is stored in folder H:\HCM2Dingo.

05/14/2014

13/27

The workflow compares the two files, the new unify_boomi.csv file and the unify_boomi_old.csv file, to check if

there are new changes. If there are changes the file diff_unify_boomi.txt is created with no data (empty) else

the diff_unify_boomi.txt file is created with the information FC: no differences encountered.

5.6 HCM2Dingo_DEP Workflow

The HCM2Dingo_DEP workflow creates/updates Department objects in Dingo.

It takes the HCM import file as input and for each record tries to add or update the department of the

employee in Dingo. If the department already exists in Dingo then it tries to update it, otherwise, it tries to add

it.

There are some validations for each record.

The following fields are required for each record in the HCM import file:

1. Department (Department Name or Department Code)

2. ARE

3. Company

4. Country

The following checks are done for each record in the HCM import file:

1. Country enabled for HCM

2. Company exists in Dingo

3. Department is not empty

4. ARE exists in Dingo

If some validation does not approve then the record is ignored.

5.7 HCM2Dingo_ACC Workflow

The HCM2Dingo_ACC workflow creates/updates/assigns Accounting Code objects in Dingo.

It takes the HCM import file as input and for each record tries to add or update the accounting code of the

employee in Dingo. If the accounting code already exists in Dingo then it tries to update it, otherwise, it tries to

add it.

It also tries to assign the accounting code to the department of the employee if the accounting code is not

already assigned. If the department is empty then the assignment of the accounting code is cancelled.

There are some validations for each record.

The following fields are required for each record in the HCM import file:

1. Accounting code

2. Department (Department Name or Department Code)

3. ARE

4. Company

5. Country

05/14/2014

14/27

The following checks are done for each record in the HCM import file:

1. Country enabled for HCM

2. Company exists in Dingo

3. Accounting code is not empty

4. ARE exists in Dingo


5.8 CSVImport_IDHCM Workflow

The CSVImport_IDHCM workflow creates/updates/LOST Dingo entries with fk-source=CSVImportHCM.

It takes the HCM import file as input and for each record tries to add or update the Dingo entry of the

employee. If exist a Dingo entry (fk-source=CSVImportHCM) and does not exist a corresponding record in the

HCM import file then the workflow tries to set to LOST the entry.

The filter to get the current Dingo entries is:

set gl_qsys_config(search_base) "ou=Dingo,o=SCD"

set gl_qsys_config(filter) "(&(fk-source=CSVImportHCM)(fk-value=*)(objectclass=dingo))"

set gl_qsys_config(subset) "-subtree"

The filter to join the HCM record with a Dingo entry is:

(&(fk-source=$rh_ldap(fk-source))(fk-value=$rh_ldap(fk-value))(objectclass=dingo)(!(duplicate-link=*))) or (&(tc-key=$rh_ldap(tc-key))(|(status=TBD)(&(fk-source=*)(fk-link-status=LOST)))(objectclass=dingo)(!(duplicate-link=*))) or (&(personal-id=$rh_ldap(personal-id))(|(status=TBD)(&(fk-source=*)(fk-link-status=LOST))(!(fk-source=*)))(objectclass=dingo)(!(duplicate-link=*)))

The workflow does validations for each record of the HCM import file according to the above layout of the file.


5.9 Email Notifications

The CSVImport_IDHCM workflow has the following email notifications:

Name Subject Sent Attachment Recipient

NotifyChangesExc

eed

Delivery from DINGO:

HCM import did more

than 10% changes

When the workflow

made more than 10% of

changes.

thomas.distler@un

ify.com

[email protected]

NotifyFileNoChang

es


HCM import file has no

When the HCM import

file has no changes.

thomas.distler@un

ify.com

tsmx-unify-

05/14/2014

15/27

6 DINGO2HCM INTERFACE

changes [email protected]

NotifyLost Delivery from DINGO:

HCM Dingo entries set to

LOST

When there are entries

which were set to LOST

by the workflow.

HCM_lost.csv

[email protected]

[email protected]

NotifyNoImported Delivery from DINGO:

HCM Records not

imported because of

incorrect data

When there are users

which were not

imported into Dingo by

the workflow because

they had invalid values.

HCM_not_imported_data.csv

[email protected]

[email protected]

NotifyNoLost Delivery from DINGO:

HCM Dingo entries not set

to LOST

When there are entries

which could not be

LOST because they

were more than the

maximum allowed.

HCM_no_lost.csv

[email protected]

[email protected]

NotifySpecialLost Delivery from DINGO:

HCM Special Dingo entries

set to LOST

When there are special

entries which were set

to LOST.

These are the special

entries:

ZZZZZOK2 -> Schwaicker Dieter

Z00076ZL -> Fredricks Jack

Z0003AHF -> Adams Matthew

Z000B3AO -> Pimentel Jones Bertoli

Z0001EBL ->

Dienstleder-Koenig

Silvia

HCM_special_lost.csv

[email protected]

[email protected]

NotifyUserTypeCh

g


HCM Records with user-

type change

When there are users

which could not be

imported because the

user-type is different

(ISEEXE).

HCM_not_imported_type.csv

[email protected]

[email protected]

05/14/2014

16/27

The Dingo2HCM interface is a workflow that takes all active Dingo entries and creates 3 csv files that send to

HCM via pscp:

1. Phone numbers file: sen_phone_import.csv

2. Windows Domain file: sen_dom_im_import.csv

3. Email address file: sen_mail_import.csv

The connection parameters to send the export files to HCM are stored in the Specific Attributes of the

Dingo2HCM workflow:

Server: prodftp2.successfactors.eu

Userid: sen

Password: (see it in the workflow)

Folder: /INPUT

This interface runs daily at 6:00 am, 11:00 am, 06:00 pm, 09:30 pm CET.

6.1 PHONE NUMBERS FILE

The phone numbers are sent to HCM in the file sen_phone_import.csv via pscp.

Layout of the sen_phone_import.csv file:

Position Field Name Dingo Attribute

1 Person Id External tc-key

2 Phone Type See table below

3 Phone Number See table below

5 Operation ""

4 Primary See table below

Dingo Attribute

telephoneNumber Business Primary=Yes

facsimileTelephoneNumber Fax Primary=No

telephone-mobile Cell Primary=No

The file has two heading lines (sen_phone_import_header.csv):

personInfo.person-id-external,phone-type,phone-number,operation,isPrimary,

Person Id External,Phone Type,Phone Number,Operation,Primary,

The fields are separated by commas and the last comma of each record is removed with the sed.exe program

located under H:\CSVImport\ID003\Prepare\tools\bin.

6.2 WINDOWS DOMAIN FILE

The windows domain is sent to HCM in the file sen_dom_im_import.csv via pscp.

Layout of the sen_dom_im_import.csv file:

05/14/2014

17/27


1 Person Id External tc-key

2 Operation ""

3 IM ID internetMailService, "dummy" if empty

4 Windows Domain current-nt-user-account, "dummy" if empty

If entry does not have email address (rfc822Mailbox) then it is omitted in the file.

The file has two heading lines (sen_dom_im_import_header.csv):

personInfo.person-id-external,operation,im-id,domain,

Person ID External,Operation,Instant Messaging ID,Windows Domain,



6.3 EMAIL ADDRESS FILE

The email address is sent to HCM in the file sen_mail_import.csv via pscp.

Layout of the sen_mail_import.csv file:


1 person-id-external tc-key

2 Email Type "Business"

3 Email Address rfc822Mailbox

4 Operation ""

5 Is Primary "Yes"

If entry does not have email address (rfc822Mailbox) then it is ommited in the file.

The file has two heading lines (sen_mail_import_header.csv):

personInfo.person-id-external,email-type,email-address,operation,isPrimary,

person-id-external,Email Type,Email Address,Operation,Is Primary,



7 DINGO WEB CENTER CHANGES

In Dingo Web Center the following changes were done due to the HCM interface:

1. New handle for CSVImportHCM entries.

2. Field Functional Manager is read-only for Dingo Entries with fk-source CSVImportHCM

3. Label Local Manager changed to Legal Manager

4. Label Fachlicher Manager changed to Funktionale Fhrungskraft

5. Label Lokaler Manager changed to Vorgesetzter

6. New page for creating EXE entries (displayed when click on Create external entry link):

05/14/2014

18/27

05/14/2014

19/27

8 ADP2USB

The ADP2USB workflow was modified to get the HCM entries (fk-source=CSVImportHCM) as follows:

1. Specific Attribute/user_filter of job ADP2Dingo_vollmachten_MetaCP: changed fk_value attribute by

igoAdpPersonalNumber attribute

2. Specific Attribute/user_filter of job ADP2Dingo_vollmachten_MetaCP: changed fk-source=SAP HR by

fk-source=CSVImportHCM

user_filter = (&(igoAdpPersonalNumber=$pernr)(fk-source=CSVImportHCM)(fk-link-

status=OK)(|(status=OK)(status=NEW)))

05/14/2014

20/27

9 DINGO2ADP

The Dingo2ADP workflow was modified as follow:

1. The Search Filter of the Export Properties (Dingo_In_Dingo2ADP_DE channel) changed the fk-

source=SAP HR to fk-source=CSVImportHCM

2. Dingo is now sending to ADP the igoAdpPersonalNumber instead of the SAPPersonalnr.

3. Change Filter to get only ISE and HID employees.

05/14/2014

21/27

10 DINGO.DAT FILE

The dingo.dat file (users.csv) generated by the CSVExport4Dingo.dat workflow changed is layout as follows:

1. The field 105 was fk-value attribute, now it is the igoAdpPersonalNumber attribute.

2. The fk-value attribute was added as the field 106.

3. The igoEmployeeStatus attribute was added as the field 107.

4. The igoGlobalJobRole attribute was added as the field 108.

New layout of the dingo.dat file:

Position Field Name

1 cn

2 single-sign-on

3 user-type

4 e-mail-admin-domain

5 status

6 modifyTimestamp

7 createTimeStamp

8 duplicate-link

9 sn

10 givenName

11 title

12 personal-title

13 display-name

14 c

15 o

16 department

17 location-short

05/14/2014

22/27

18 street

19 houseIdentifier

20 room-number

21 physicalDeliveryOfficeName

22 telephoneNumber

23 facsimileTelephoneNumber

24 telephone-mobile

25 rfc822Mailbox

26 accounting-code

27 rank

28 employee-identification

29 personal-id

30 current-nt-user-account

31 gender

32 nt-service-status

33 ou

34 initials

35 roles

36 secretary

37 representation

38 send-to-scd

39 defaultusername

40 surnameNational


42 localityName

43 postalCode

44 fk-source

45 multiple-link

46 department-old

47 accounting-code-old

48 post-office-text

49 gid

50 scd-key

51 tc-key

52 it-service-center

53 Net-Domain

54 videoConferenceNumber2

55 phoneNumberSecure

56 alternatePhone

57 personalFax

58 faxNumberSecure

59 netMeeting

60 mainFunction

61 releaseExtern

62 orgId

63 webMailAddress

64 lteEmailAddress

05/14/2014

23/27

65 lteMappingStatus

66 lteStatus

67 lteActive

68 technicalMailAddress

69 firewall

70 internetMailService

71 SAPPersonalnr

72 SAPOrgnote

73 personnelsubrange

74 personneldomain

75 SCDDeliveryID


77 gnsName


79 superiorLink

80 Areu

81 job-title-text

82 expiry-date

83 description

84 e-mail-service-status

85 e-mail-service

86 e-mail-mailbox-name

87 nt-service

88 postOfficeBox

89 st

90 labeledURI

91 active-directory-guid

92 send-to-topdial

93 dingoKeyword

94 ceAuthenticationKey

95 superiorGID

96 representationGID

97 secretaryGID

98 superiorsSecretaryGID

99 superiorsRepresentationGID

100 superiorDingoKey

101 representationDingoKey

102 secretaryDingoKey

103 superiorsSecretaryDingoKey

104 superiorsRepresentationDingoKey

105 igoAdpPersonalNumber

106 fk-link-status

107 fk-version

108 igoAircardNumber

109 igoSecondMobilePhoneNumber

110 igoThirdMobilePhoneNumber

111 igoFourthMobilePhoneNumber

05/14/2014

24/27

112 igoFunctionalManager

113 igoFuncManagerGid

114 igoSkills

115 igoResponsibilities

116 fk-value


118 igoGlobalJobRole

11 CSED FILE (SEN_PERSONEN.TXT)

The SEN_personen.txt file generated by the CSVExport4OSD workflow changed is layout as follows:

1. The igoFuncManagerGid attribute was added as field 105.

2. The igoEmployeeStatus attribute was added as field 106.

This is the new layout of the SEN_personen.txt file:

Position Field Name

1 cn

2 single-sign-on

3 user-type

4 e-mail-admin-domain

5 status

6 modifyTimestamp

7 createTimeStamp

8 duplicate-link

9 sn

10 givenName

11 title

12 personal-title

13 display-name

14 c

15 o

16 department

17 location-short

18 street

19 houseIdentifier

20 room-number

21 physicalDeliveryOfficeName

22 telephoneNumber

23 facsimileTelephoneNumber

24 telephone-mobile

25 rfc822Mailbox

26 accounting-code

27 rank

28 employee-identification

29 personal-id

05/14/2014

25/27

30 current-nt-user-account

31 gender

32 nt-service-status

33 ou

34 initials

35 roles

36 secretary

37 representation

38 send-to-scd

39 defaultusername

40 surnameNational


42 localityName

43 postalCode

44 fk-source

45 multiple-link

46 department-old

47 accounting-code-old

48 post-office-text

49 gid

50 scd-key

51 tc-key

52 it-service-center

53 Net-Domain

54 videoConferenceNumber2

55 phoneNumberSecure

56 alternatePhone

57 personalFax

58 faxNumberSecure

59 netMeeting

60 mainFunction

61 releaseExtern

62 orgId

63 webMailAddress

64 lteEmailAddress

65 lteMappingStatus

66 lteStatus

67 lteActive

68 technicalMailAddress

69 firewall

70 internetMailService

71 SAPPersonalnr

72 SAPOrgnote

73 personnelsubrange

74 personneldomain

75 SCDDeliveryID


05/14/2014

26/27

77 gnsName


79 superiorLink

80 Areu

81 job-title-text

82 expiry-date

83 description

84 e-mail-service-status

85 e-mail-service

86 e-mail-mailbox-name

87 nt-service

88 postOfficeBox

89 st

90 labeledURI

91 active-directory-guid

92 send-to-topdial

93 dingoKeyword

94 ceAuthenticationKey

95 superiorGID

96 representationGID

97 secretaryGID

98 superiorsSecretaryGID

99 superiorsRepresentationGID

100 superiorDingoKey

101 representationDingoKey

102 secretaryDingoKey

103 superiorsSecretaryDingoKey

104 superiorsRepresentationDingoKey

105 igoFuncManagerGid


12 Dingo WebCenter

The Dingo WebCenter was changed to handle the entries with fk-source=CSVImportHCM in the same way that

it does with the ADP entries.

Dingo WebCenter also was changed to set as read-only the field Functional Manager

Change the following strings to make them Equal to HCM:

05/14/2014

27/27

DE

Fachlicher Vorgesetzter set to Funktionale Fhrungskraft

Lokaler Manager set to diszpl Vorgesetzter

ENG

Functional Manager as is Functional Manager

Local Manager set to Legal Manager

KA HCM-Dingo Interfaces

Documents