Integration Center chose start entity for Learning jobs - best practice?

[AC_LMS_RO]

hi!

I am wondering if there is a best practice from SAP in regards to the starting entity for the user import via integration center for learning. All i could find is a blog - that covers the topic very vaguely.

I am asking this because the navigation from the user entity is most of the time messy when you have EC and you cannot always read the data from the fields that are effectively dated - and the solution offered by the integration is to change the starting entity (so from the EP to EC entities).

Moreover when we discuss starting from the user entity who does not support ID & Definitions as separate fields in EP - when in LMS you do have the possibility for most of the job related fields to import data with ID and Description separately in the connector.

Is this something that is worth a discussion for you as well?
What are your pros and cons when we talk integrating the user data with Learning from empJob (EC) OR from user (EP)?

thank you!
Adina

[nathanharding]

If you have a look at how I mapped these objects from for instance the User (EmpInfo) > Emp Employ (JobInfoNav) > Job Info (Depart) > Department (Code) then you avoid the multiple object associations and only pick up the relevant code.

[nathanharding]

I really haven't found the issues that you are talking about when using Integration Centre to create the following LMS Connectors:

1. Organisational Hierarchy
2. Job Code 
3. SF User

With the SF USER connector being easy to bring in the ID and the Description (See below Integration Specification) for Location (and or other entities as required by my clients).  I 

Field Number	Field Label	SF Entity	SF Field	Default Value	Association	Data Type	Format	Value Lookup Table
Body Fields
1	STATUS	User	Status (status)		status	Edm.String		STATUS Lookup Table
2	USERID	User	User ID (userId)		userId	Edm.String
3	LASTNAME	User	Last Name (lastName)		lastName	Edm.String
4	FIRSTNAME	User	First Name (firstName)		firstName	Edm.String
5	MI					Edm.String
6	EMAIL	User	Email (email)		email	Edm.String
7	GENDER	Personal Information (PerPersonal)	gender		costCenterManagerOfFOCostCenterNav/*/costcenterManagerNav/usersSysIdOfEmployeeDataReplicationElementNav/*/personNav/personalInfoNav/*/gender	Edm.String
8	HIREDATE	User	Hire Date (hireDate)		hireDate	Edm.DateTime	MM/dd/yyyy
9	TITLE	User	Job Title (jobTitle)		jobTitle	Edm.String
10	JOBCODE	User	Job Code (jobCode)		jobCode	Edm.String
11	LOCATION_ID	Location (FOLocation)	Location ID (externalCode)		empInfo/jobInfoNav/*/locationNav/externalCode	Edm.String
12	LOCATION_DESC	Location (FOLocation)	Location Name (name)		empInfo/jobInfoNav/*/locationNav/name	Edm.String
13	DEPARTMENT	Job Information (EmpJob)	Department (department)		empInfo/jobInfoNav/*/department	Edm.String
14	DIVISION	Job Information (EmpJob)	Division (businessUnit)		empInfo/jobInfoNav/*/businessUnit	Edm.String
15	MANAGER	User	User ID (userId)		manager/userId	Edm.String
16	TIMEZONE	User	Time Zone (timeZone)		timeZone	Edm.String
17	DEFAULT_LOCALE	User	Default Locale (defaultLocale)		defaultLocale	Edm.String
18	DOMAIN_ID			ACME_ALL		Edm.String
19	PERSON_ID_EXTERNAL	User	User ID (userId)		userId	Edm.String
20	PERSON_GUID	Biographical Information (PersonKey)	Person UUID (perPersonUuid)		personKeyNav/perPersonUuid	Edm.String

I would refer to the IDP document IDP - SuccessFactors Suite Impact of Implementing Employee Central for LMS Customers_V1.41.pdf (sap....

And check out the SAP SuccessFactors Learning – Get Your Implementation Right! (Repeat) (you may have to search for where it has moved too) as "Week 3: Leverage Integration Center for Connectors" is awesome for this with videos and tutorials.

I hope that this helps :).

Kind Regards,

Nathan H.

[AC_LMS_RO]

hey Nathan,

thank you for your reply.

May i ask which entity you started with?

Because in EP you don't have a specific field for ID and a specific field for Description - maybe they are merged in one and you split?

i am asking this because we tend to navigate to the EC entities to get the ID separately from the Desc, and that works perfectly.

as for the SF Connector, we had issues with writing data to JP_desc and JL_desc - since SAP mentioned that is not to be used. Guess you can use the Position connector... but another integration for another thing, when the simple connector does wayyyy better on the other side.

[AC_LMS_RO]

as well, what issues i encountered with navigating from User to EC is that you might have a one-to-many relationship and Integration Center doesn't always works graciously with that. and then they suggest to move to other entities to start with.