CONFIDENTIAL
Document Version: 1H 2021 – 2021-07-14
© 2021 SAP SE or an SAP affiliate company. All rights reserved.
Importing User Data from Platform with User
Connector - SF
THE BEST RUN
Content
1
Engage Certified Partner to Import Data to SAP SuccessFactors Learning . . . . . . . . . . . . . . . . . . . 5
2
Purpose of User Connector - SF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3
Initial Configuration for User Connector - SF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.1
Configuring the Connector FTP Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.2
Enabling Connector Logging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.3
Enabling Email Notifications in SAP SuccessFactors Learning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.4
Enabling the Connector Archive. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.5
Requiring Both Feed Files for the User Connector - SF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.6
Allowing Hire Dates in the Future in SAP SuccessFactors Learning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.7
Setting the Default Security Role for User Connector - SF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.8
Sending Users with Missing Domains, Organizations, or Finance Accounts to Temporary Holding
Domains. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.9
Configuring User Connector - SF to Assign Job Related Curricula. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.10
Adding a New Locale for User Connector - SF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
3.11
Changing Default Descriptions for Phone Numbers in User Connector - SF. . . . . . . . . . . . . . . . . . . . . . . 18
4
Field Mapping for User Connector - SF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.1
User Connector - SF People (CORE) Feed Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.2
User Connector - SF Live Profile (EXTENDED) Feed Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
4.3
Downloading Learning Connector Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
4.4
Mapping platform Data to Learning Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
4.5
Importing Custom Fields from platform to Learning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
4.6
Copying Values Between Input Columns in User Connector - SF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
4.7
Connector Data Mapping Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
4.8
Learning Regions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Why Regions Matter to Facilities and Your Physical Learning Environment. . . . . . . . . . . . . . . . . . . . . 48
Why Regions Matter to Instructors and your Physical Learning Environment. . . . . . . . . . . . . . . . . . . 48
4.9
SAP SuccessFactors Learning Native Deeplink User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49
5
Export and Import Jobs Creation for User Connector - SF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
5.1
Types of Employee Export Jobs for User Connector - SF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
5.2
Scheduling Weekly Employee Export Job Type for User Connector - SF. . . . . . . . . . . . . . . . . . . . . . . . . 51
5.3
Scheduling Daily Delta Employees Export Job Type for User Connector - SF. . . . . . . . . . . . . . . . . . . . . . 53
5.4
Scheduling Weekly Live Profile Export Job Type for User Connector - SF. . . . . . . . . . . . . . . . . . . . . . . . 55
5.5
Scheduling Daily Live Profile Export Job Type for User Connector - SF. . . . . . . . . . . . . . . . . . . . . . . . . . 57
5.6
Scheduling Learning Connector Jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
2
CONFIDENTIAL
Importing User Data from Platform with User Connector - SF
Content
6
Person IDs Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
6.1
Enabling Person GUID Export. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
6.2
Setting Up the SAP SuccessFactors Learning Person IDs Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
7
Troubleshooting Connectors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
7.1
Connector Prefixes in SAP SuccessFactors Learning Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
7.2
Connector Log Clean-Up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
7.3
Export Cautions for User Connector - SF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66
7.4
Termination Date Processing for User Connector - SF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67
Verifying that User Connector - SF Allows Rehires. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68
7.5
Manager Processing for User Connector - SF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
7.6
Alternate Manager Processing Logic for User Connector - SF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
7.7
Manager, Matrix Manager, HRBP, and Alternate Manager Mapping in User Connector - SF. . . . . . . . . . . . 70
7.8
Default Process Rules for Activating and Inactivating learners with User Connector - SF. . . . . . . . . . . . . 72
Results of Inactivating Users in SAP SuccessFactors Learning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Changing Default Active Behavior in User Connector - SF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74
Enforcing Consistency for Learner Inactivation by Learning Connectors. . . . . . . . . . . . . . . . . . . . . . 76
Remapping Shopping Accounts to Status for User Connector - SF. . . . . . . . . . . . . . . . . . . . . . . . . . 77
7.9
How User Connector - SF Processes Custom Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
7.10
Time Zone Processing for User Connector - SF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
7.11
Reference Values Processing in User Connector - SF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
7.12
Full Time Mapping for User Connector - SF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
7.13
Update on Null for User Connector - SF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
7.14
Verifying Hire Date Transformation for User Connector - SF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81
Importing User Data from Platform with User Connector - SF
Content
CONFIDENTIAL
3
Change History
Learn about changes to the documentation for synchronizing learning user data with platform.
<1H 2021 - Present>
Type of Change
Description
None
We did not update this document.
More Info
<1H 2020>
What's New
Description
New User Interface for SAP SuccessFac­
tors Learning Administration
In the 1H 2020 release, the user interface New User Interface for SAP SuccessFac­
for SAP SuccessFactors Learning Admin­ tors Learning Administration
istration was updated to enhance the
user experience and streamline naviga­
tion and terminology.
4
CONFIDENTIAL
More Information
Importing User Data from Platform with User Connector - SF
Change History
1
Engage Certified Partner to Import Data to
SAP SuccessFactors Learning
Learning connectors can import thousands of entities in the system, so we highly recommend that you engage with
our Professional Services organization or a certified Learning implementation partner before you attempt to use
connectors or any data import, especially in a production environment.
You can attempt to implement connectors on your own, but in doing so, you assume full responsibility for your
actions. While we provide safeguards when able, it’s possible to load thousands of erroneous data in the system
and end up incurring significant costs to correct them. Operational interruptions can be caused by having incorrect
completion data; causing severe impact in regulated trades and industries. As with any other opt-in feature, we
highly recommend that you do thorough testing before turning on connectors.
Importing User Data from Platform with User Connector - SF
Engage Certified Partner to Import Data to SAP SuccessFactors Learning
CONFIDENTIAL
5
2
Purpose of User Connector - SF
User Connector - SF syncs users and their attributes from platform to Learning so that you can assign courses, find
users, and report on users in Learning.
When you implement SAP SuccessFactors, SAP SuccessFactors platform is the system of record for user data. You
sync the platform user attributes to Learning so that you can assign courses based on their attributes. If you do not
schedule the connector, then the data in Learning becomes old and your learners do not get assignments based on
their current attributes.
For example, you can create an assignment profile to assign courses by employees' city. It assigns one course, for
example, to learners in Tokyo and another course to learners in Berlin. If an employee moves to another city,
administrators update the employees' city in platform. User Connector - SF syncs learner's new city to Learning so
that the learner's assignment is correct for his or her new city.
 Note
Syncing user identity is among the most important parts of User Connector - SF. Although Learning has a
student ID, which contains the users' data for learning, the identity of the user across the suite is the user's
person ID, represented as an external ID and a GUID.
6
CONFIDENTIAL
Importing User Data from Platform with User Connector - SF
Purpose of User Connector - SF
3
Initial Configuration for User Connector SF
Before you can sync data from platform to Learning, you must configure some basic behavior for the connector.
When you configure User Connector - SF, you first manage some initial configuration to set up the rules of the
connector, then you configure how fields in platform map to Learning, then you define the data feed schedule from
platform, and then test and troubleshoot the connector.
Initial configuration for User Connector - SF includes defining how the connector runs, how you want to log the
connector runs for troubleshooting, and some business logic configuration. It is the work you do before you create
the mapping between where data is stored in platform and where data is stored in Learning because the mapping
depends on the initial configuration.
3.1
Configuring the Connector FTP Site
Configure the SAP SuccessFactors Learning FTP site so that when the connector job runs, it knows where to get
the data files to import and where to write detailed logs.
Prerequisites
You run User Connector - SF, which contains user data. To encrypt this data, you need PGP encryption.
The keyring must be provided to the party that is generating the PGP encrypted file so that the encryption and
decryption match. The keyring value is a base64 encoding of the binary keyring file. Use the Linux base64
command or other tool for decoding the property value to obtain the public keyring file that needs to be provided to
both ends of the transaction.
Procedure
1. Go to SAP SuccessFactors Learning Administration and then go to
System Administration
Configuration
System Configuration .
2. Edit CONNECTORS.
3. Set connector.input.file.location to FTP.
4. Set the location of the FTP site and directory where the connectors fetch their data files.
Importing User Data from Platform with User Connector - SF
Initial Configuration for User Connector - SF
CONFIDENTIAL
7
Property
connector.ftp.protocol
Description
The protocol used by the FTP server. Valid values are
ftpand sftp.
connector.ftp.server
The name of the FTP server. For example,
ftp.acme.internal.
connector.ftp.port
The port that the FTP server listens to. For example, 22.
connector.ftp.userID
The user ID on the FTP server that owns this process. When
specifying the user, make sure that the user has access to
the directories where the system reads data files and writes
log files.
connector.ftp.password
The password for the user. The password is clear text until
you save the CONNECTOR file. On save, the system encrypts
the value.
connector.ftp.input.remoteDirectory
This is the folder where SAP SuccessFactors looks for data
files. If for example, you plan to drop data files in /root/
connectors/input, add the folder path as follows.
 Sample Code
<...>.remoteDirectory=/root/
connectors/input
5. Set connector.input.file.name.tenant.suffix.enable to false.
When false, the connector doesn't expect a suffix. If you set it to true, the connector expects a data file that
ends in your tenant ID.
6. Add encryption settings.
Property
Description
connector.pgp.enabled
If you encrypt the data file, set to true so that the system
can decrypt the files. If this setting is set to true, it impacts
all connectors. If the connector doesn't find a .pgp file, it will
still process other file types such as .csv, .txt., and .zip. En­
crypted files are common when they contain sensitive infor­
mation, like user identification numbers.
connector.pgp.public.keyring
The connector.pgp.public.keyring property
connector.pgp.secret.keyring
connector.pgp.passphrase
connector.pgp.file.extension
value is the public keyring used by the system to decrypt the
encrypted files.
The secret keyring, passphrase, and extension are standard
PGP encryption properties. The extension is usually .pgp.
7. Set connector.input.file.fetch.retry.enable to cause the connector to wait until the next run to
retry or to retry again before the next run.
○ Set to false if you want to wait until the next connector run if there’s a file read error. Set to true to try to
fetch two more times on file read error. In practice, many organizations set to false because they run a
connector every day and they believe that the information can wait until the next connector run in the
8
CONFIDENTIAL
Importing User Data from Platform with User Connector - SF
Initial Configuration for User Connector - SF
unlikely event of a file read error. Additionally, file read errors are often caused by issues like missing files or
a bad FTP password: issues that won't be solved by trying the fetch again.
○ Set to true if you believe that the connector information has more time sensitivity than the next connector
run. For performance reasons, we control the amount of time that the connector waits before attempting
another fetch.
3.2
Enabling Connector Logging
Enable connector logging during initial implementation so that your team can be alerted to trouble with connectors
and easily see a log of the connector.
Prerequisites
Enable Learning email notifications. You usually enable Learning email notifications as part of your overall
implementation because they apply to more than just connector logs. Think broadly about Learning email
notifications when you enable them.
Set up an email distribution list of the people who are to be notified of connector trouble.
Procedure
1. Go to SAP SuccessFactors Learning Administration and then go to
System Administration
Configuration
System Configuration .
2. Edit CONNECTORS.
3. Set connector.ftp.output.report.enable to true to enable the reports to go to your FTP site.
4. Set connector.ftp.output.report.remoteDirectory to /logs so that logs are written to a folder called
logs in the FTP site.
5. Decide how SAP SuccessFactors sends status of the connector.
Property
Value
connector.report.email.enable
Set to true to receive an email copy of the report.
connector.report.email.toAddresse
s
The email distribution list address that receives the emailed report log
if the emailed report is enabled. Don’t use a person's email address.
connector.report.email.CCAddresse
s
If you also want to copy an address, add the address here.
connector.report.email.mailSubjec
t
The value of this property is the subject line of the report email. We rec­
ommend a value like $interfaceId$ - Connector Results.
At run time, the system substitutes the name of connector for
$interfaceId$.
Importing User Data from Platform with User Connector - SF
Initial Configuration for User Connector - SF
CONFIDENTIAL
9
Property
Value
connector.report.email.enableDeta
ilReportAttachments
If set to true, then a detailed log is sent as an attachment to the
email. Otherwise, the email contains the time of the run and success or
failure.
A good strategy to reduce the size of the email messages: set this prop­
erty to false and then tell the recipients to look at the detailed report
in the
System Administration
Connectors
section of the Admin­
istrator interface. To use this strategy, recipients must have access to
the SAP SuccessFactors Learning Administration environment.
6. Decide how SAP SuccessFactors handles the detailed report.
Property
Description
connector.report.detail.displayMe
ssageTypes
This property specifies the level of log entries that must be part of the
detailed report. Possible values are: Exception, Warning, FATAL, and
info. To include more than one, add as a comma-separated list. For ex­
ample:
<property>=Exception,Warning,FATAL
connector.report.detail.numberOfE
xceptionsDisplayed
Change the default value of 5000 only if you need to. For example: if
you’re troubleshooting during implementation.
7. Save and close CONNECTORS.
3.3
Enabling Email Notifications in SAP SuccessFactors
Learning
Enable email notifications in SAP SuccessFactors Learning so that Learning can send email messages about
training and system information.
Prerequisites
We rely on a separate (Simple Mail Transfer Protocol) SMTP server to send email. The configuration of the SMTP
server is done at the backend. You can also use the server we provide. If you plan to use your own, your
configuration is more complex. You must, however, have an SMTP server identified before you enable the email
notifications.
10
CONFIDENTIAL
Importing User Data from Platform with User Connector - SF
Initial Configuration for User Connector - SF
Context
You typically enable notifications during implementation and when you start a new instance.
 Note
When you select a custom certificate for Default Certificate Template for Items and Default Certificate Template
for Programs, email notifications are sent to users irrespective of the Enable email configuration in
Application Settings
Global
Mail . If you don't select a custom certificate, then email notifications are sent based on
the Enable email configuration in
Global Application Settings
Mail .
Procedure
1. Go to SAP SuccessFactors Learning Administration and then go to
Global Application Settings
System Administration
Configuration
Mail .
2. Select Enabled in Enable email.
 Note
The SMTP server settings are handled at the backend.
3. Type the email addresses that administrators see as the sender in Admin Email Notification and that learners
see as the sender in User Email Notification.
For example, you can type noreply@<your company domain>.
4. In Email Frequency, type 5.
Email Frequency is the number of minutes that you want the application server to wait before it contacts the
SMTP server to send notification messages.
5. In Send email notification from select Select from list and then type a comma-delimited list of email addresses.
Select from list allows administrators to choose an address from one or more addresses that you provide and
control. When administrators create ad-hoc notifications, Learning adds the email address of the administrator
who is attempting to send the notification to the top of this list automatically, but they can select any one of the
emails addresses you provide.
○ Free-form allows administrators to type any email address with valid syntax. It doesn’t do a legal check of
the text that an administrator types.
○ Admin forces administrators to use their own email addresses.
6. Choose Apply Changes.
Next Steps
Configure email invitations and email archiving.
Importing User Data from Platform with User Connector - SF
Initial Configuration for User Connector - SF
CONFIDENTIAL
11
3.4
Enabling the Connector Archive
Enable the SAP SuccessFactors Learning connector archive so that you have a record of connector files for
troubleshooting connector issues.
Context
Enable the connector archive and keep archived files for three months for troubleshooting. If you don't select
Enable input file archive, you increase your troubleshooting efforts.
Procedure
1. Go to SAP SuccessFactors Learning Administration and then go to
System Administration
Connectors
Connector Settings .
2. Select Enable input file archive.
 Note
Enable input file archive doesn't work for User Connector - Federal, so
Connectors
User Connector - Federal
System Administration
never has a Show archived input files button.
On each connector run, SAP SuccessFactors compresses and encrypts all input files for that run into a .zip file.
To access the input files, go to
Show archived input files.
System Administration
Connectors , select the connector, and then click
3. In Purge archived input files older than, type 3.
4. Click Apply Changes.
3.5
Requiring Both Feed Files for the User Connector - SF
Read how you can require both the base and the extended feeds to be present on the FTP folder in order for the
User Connector - SF to run.
Context
If you use both the base and the extended User Connector - SF files, you may want to require that they are both
present on the FTP folder before the LMS connector attempts to process them. Otherwise, you end up with
12
CONFIDENTIAL
Importing User Data from Platform with User Connector - SF
Initial Configuration for User Connector - SF
incomplete user data in the LMS. For example, if the base file (user_data) exists but the extended file
(user_extended_data) does not, and if your connector runs, you get incomplete user data in the LMS.
We have added a property to the CONNECTORS configuration file that you can set to require the extended file in the
User Connector - SF. If the connector sees that you require the extended file, it looks for it before it runs and shows
you an error if it is missing. If it is missing, the connector run stops.
Procedure
1. Go to
System Administration
Configuration
System Configuration
CONNECTORS .
2. Find sfuser.connector.processingRule.requiredFiles.
○ If you set it to null, then the connector runs even if all files are not present.
○ If you set it to a comma separated list of file names, then the system checks that those files exist before it
runs. For example: user_data.csv,user_extended_data.csv.
Related Information
Types of Employee Export Jobs for User Connector - SF [page 50]
Scheduling Weekly Employee Export Job Type for User Connector - SF [page 51]
Scheduling Daily Delta Employees Export Job Type for User Connector - SF [page 53]
Scheduling Weekly Live Profile Export Job Type for User Connector - SF [page 55]
3.6
Allowing Hire Dates in the Future in SAP SuccessFactors
Learning
Allow hire dates in the future in Learning because future hire dates are allowed in SAP SuccessFactors platform and
any restriction on hire dates should be handled in the system of entity: platform.
Context
Users in platform often have future hire dates: they’re set up in the system so that they’re ready for the employees'
first day. Enable future hire dates so that you can do things like assign onboarding courses before users' first day.
 Note
Although we understand that some customers in some situations can’t have future hire dates, you should build
that restriction in the system of entity and not in Learning. If you build the restriction in platform, then you
prevent the future hire date at the source.
Importing User Data from Platform with User Connector - SF
Initial Configuration for User Connector - SF
CONFIDENTIAL
13
Procedure
1. Go to SAP SuccessFactors Learning Administration and then go to
System Administration
Configuration
System Configuration .
2. Edit LMS_ADMIN.
3. Find allowFutureHireDates and set it to true.
3.7
Setting the Default Security Role for User Connector - SF
When you configure your security roles and workflows, we recommend that you use one security role for the user
persona. Set that security role as the default security role.
Procedure
1. Go to SAP SuccessFactors Learning Administration and then go to
System Administration
Security
Role
Management .
2. Click Add/Remove Criteria and select Role Type.
3. Click Select.
4. In Role Type, type STUDENT and then click Search.
5. In the search results, copy the role ID of your default learner role.
 Caution
The system default learner role is LEARNING_USER. This is the role that you copy when you create your
company's default learner role, but it is not your role. Do not set LEARNING_USER as your default role in
the connector file.
6. Go to
System Administration
Configuration
System Configuration
and then edit CONNECTORS.
7. Find sfuser.connector.defaultValue.studentRoleID.
8. For its value, paste the role ID.
For example, if your company has the default learner security role DEFAULT_LEARNER:
 Sample Code
sfuser.connector.defaultValue.studentRoleID=DEFAULT_LEARNER
9. Click Apply Changes.
14
CONFIDENTIAL
Importing User Data from Platform with User Connector - SF
Initial Configuration for User Connector - SF
3.8
Sending Users with Missing Domains, Organizations, or
Finance Accounts to Temporary Holding Domains
When you run User Connector - SF, if users are assigned to a domain, an organization, or a finance account in
platform that does not yet exist in Learning, you want the user to go to a temporary holding domain so that you can
resolve the error.
Prerequisites
Create temporary holding domains for the new domains, organizations, or finance accounts:
● TEMP_USER_DOMAIN_HOLD
● TEMP_ORG_HOLD
● TEMP_FIN_ACCT_HOLD
You often create holding domains when you set up your security system.
Procedure
1. Go to SAP SuccessFactors Learning Administration, go to
System Administration
Configuration
System
Configuration , and then edit CONNECTORS.
2. Search for sfuser.connector.defaultValue and set domainID, orgDomainID, and finAcctDomainID
to their holding domains.
 Sample Code
sfuser.connector.defaultValue.domainID=TEMP_USER_DOMAIN_HOLD
sfuser.connector.defaultValue.orgDomainID=TEMP_ORG_HOLD
sfuser.connector.defaultValue.finAcctDomainID=TEMP_FIN_ACCT_HOLD
 Caution
Do not set sfuser.connector.defaultValue.domainID to PUBLIC. If you set it to PUBLIC all users
without a domain in platform are visible to all learning administrators.
3. Click Apply Changes.
Results
When User Connector - SF runs:
● If a user's domain is null, the user is placed into the TEMP_USER_DOMAIN_HOLD domain.
Importing User Data from Platform with User Connector - SF
Initial Configuration for User Connector - SF
CONFIDENTIAL
15
● If a user's organization ID is not recognized by Learning, it goes into the TEMP_ORG_HOLD domain.
● If a user's financial account ID is not recognized by Learning, it goes into the TEMP_FIN_ACCT_HOLD domain.
Next Steps
On a regular interval, learning system administrators should run a user report that searches for all users,
organizations, and financial accounts in the holding domains and resolve the issues with the users, organizations,
or financial accounts.
3.9
Configuring User Connector - SF to Assign Job Related
Curricula
If you want to assign curricula to users based on their job codes, you set User Connector - SF to default users to
auto-assign curricula based on job codes.
Prerequisites
If you assign curricula based on job codes, then for the connector to assign them you must have job codes
configured for curricula:
● For the job codes that should assign curricula, you define the curricula in
Learning Activities
Curricula .
● Set the job codes to automatically add and remove curricula when the job code changes. Go to
References
People Management
Job Codes
Summary
and select:
○ Automatically assign the curricula when the user is assigned this job code
○ Automatically remove the curricula when the user's job code changes
Context
 Note
This is uncommon. Most customers assign courses with assignment profiles.
Procedure
1. Go to SAP SuccessFactors Learning Administration, go to
System Administration
Configuration
System
Configuration , and then edit CONNECTORS.
16
CONFIDENTIAL
Importing User Data from Platform with User Connector - SF
Initial Configuration for User Connector - SF
2. Find sfuser.connector.defaultValue.jpAutoAssignQuals and set it to Y.
3. Find sfuser.connector.defaultValue.jpAutoRemoveQuals and set it to Y.
3.10 Adding a New Locale for User Connector - SF
Add a new local for User Connector - SF so that it can import users to the right locale from platform.
Prerequisites
Add a new locale in References Manage Labels Locales
patterns and so on. Make a note of the name of the locale.
and set it up completely with default number
Context
Locales in the platform user tables (the system of record for integrated environments) use standard encoding for
the locales (en for English and en_US for English, United States). SAP SuccessFactors Learning uses the full name
of the language, like English or German. Therefore, you map the platform table values to the SAP SuccessFactors
Learning values.
 Caution
Keep the default settings for User Connector - SF because they are the same that the user update event bus
uses. If a user is updated through User Connector - SF and through the event bus, their mapping should be the
same.
Procedure
1. Go to SAP SuccessFactors Learning Administration, go to
System Administration
Configuration
System
Configuration , and then edit CONNECTORS.
2. Find and copy the line: sfuser.field.transform.data.LOCALE.English=en,en_US, which is the default
locale and locale mapping.
For example, the French and Brazilian Portuguese Learning Locale ID values map as follows:
 Sample Code
sfuser.field.transform.data.LOCALE.French=fr
sfuser.field.transform.data.LOCALE.LOCALE.Brazilian\ Portuguese=br_PT
Importing User Data from Platform with User Connector - SF
Initial Configuration for User Connector - SF
CONFIDENTIAL
17
 Note
If the locale from SAP SuccessFactors Learning has a space in it, you must escape the space with a back
slash: \. For example: Brazilian\ Portuguese.
3. Paste it just below the original line position.
4. Change English to the name of the locale in
References
Geography
Locales .
5. Change en,en_US to the values that you expect from platform when this user is in that locale.
6. Click Apply Changes.
3.11
Changing Default Descriptions for Phone Numbers in User
Connector - SF
Some customers change the default descriptions for phone numbers that User Connector - SF imports to SAP
SuccessFactors Learning if they don't use business phone or business fax or do not like the descriptions.
Context
Although it is rare for customers to change the default descriptions, it is supported if you do not use standard data
objects in platform or you want to change the description. Most customers can use the default descriptions of
business phone and business fax because that is how they are defined in platform and using the default
descriptions simplifies and standardizes the configuration.
sfuser.field.transform.data.PHON_NUM1_DESC.@DEFAULT@=Business Phone
sfuser.field.transform.data.PHON_NUM2_DESC.@DEFAULT@=Business Fax
Procedure
1. Go to SAP SuccessFactors Learning Administration, go to
System Administration
Configuration
System
Configuration , and then edit CONNECTORS.
2. Find sfuser.field.transform.data.PHON_NUM1_DESC.@DEFAULT@.
This is the description for BIZ_PHONE. Customers rarely map it differently.
 Sample Code
sfuser.field.mapping.data.PHON_NUM1=BIZ_PHONE
3. Set it to the description that you want to use.
For example, you can change the description to mobile phone.
18
CONFIDENTIAL
Importing User Data from Platform with User Connector - SF
Initial Configuration for User Connector - SF
 Sample Code
sfuser.field.transform.data.PHON_NUM1_DESC.@DEFAULT@=Mobile Phone
4. Find sfuser.field.transform.data.PHON_NUM2_DESC.@DEFAULT@.
This is the description for FAX. Customers rarely map it differently.
 Sample Code
sfuser.field.mapping.data.PHON_NUM2=FAX
5. Set it to the description that you want to use.
For example, you can change the description to office fax number.
 Sample Code
sfuser.field.transform.data.PHON_NUM2_DESC.@DEFAULT@=Office Fax Number
6. Click Apply Changes.
Importing User Data from Platform with User Connector - SF
Initial Configuration for User Connector - SF
CONFIDENTIAL
19
4
Field Mapping for User Connector - SF
Before you can sync data from platform to Learning, you must configure how fields in platform map to Learning.
When you configure User Connector - SF, you first manage some initial configuration to set up the rules of the
connector, then you configure how fields in platform map to Learning, then you define the data feed schedule from
platform, and then test and troubleshoot the connector.
SAP SuccessFactors Learning assigns courses to users (learners) based on their attributes. Learning gets user
attributes from platform because it is the system of record, but you can control how they map to Learning for the
purpose of assignment.
 Caution
Keep the default settings for User Connector - SF because they are the same that the user update event bus
uses. If a user is updated through User Connector - SF and through the event bus, their mapping should be the
same.
4.1
User Connector - SF People (CORE) Feed Mapping
When you map core fields, you declare that you want the value from a core field in platform to populate a particular
core field in Learning.
Notes about Mapping Fields
The Mapping Property column contains values that you find in Learning administration:
System Admin
Configuration System Configuration CONNECTORS . The Usually Maps To column contains the column in the
core feed that the property usually maps to. For example, in the first row, the mapping in CONNECTORS is almost
always:
 Sample Code
sfuser.field.mapping.data.NOTACTIVE=STATUS
 Caution
Mapping must be one-to-one. For example, if you set ORG_ID to DIVISION, you cannot use DIVISION in
another mapping. This is a common configuration problem and Learning does not catch it when you save
CONNECTORS. Instead, you see errors in your first connector run. If you want to use the value from one
platform data object to more than one Learning field, please use
sfuser.connector.copy.field.mappings to copy the value.
20
CONFIDENTIAL
Importing User Data from Platform with User Connector - SF
Field Mapping for User Connector - SF
 Note
Most customers ignore the following columns from the core feed:
● CUSTOM_MANAGER (this is passed to Learning as a pipe delimited file that Learning cannot parse).
● SECOND_MANAGER
● PROXY
● USERNAME (USERNAME is the login name for native SAP SuccessFactors platform access. It is not used in
Learning, so most customers ignore it.)
● REVIEW_FREQ (REVIEW_FREQ is not useful for assigning learning and is better managed centrally in
platform)
Mapping Fields
Common Core Mapping
Maps to the platform
This Mapping Property and field in
Column from the SF
Learning...
People Export...
sfuser.field.mapping.data
.NOTACTIVE
STATUS
And you Should Know This About How it is Used...
Required to be present in the input file and almost always map­
ped to STATUS.
Indicates the status of the employee. Defaults to active if null or
invalid.
Users' active status also affects their shopping account type.
sfuser.field.mapping.data
.STUD_ID
USERID
Required to be present in the input file.
This is the system ID in the SF tables. It needs to match the
LMS user ID.
sfuser.field.mapping.data
.FNAME
FIRSTNAME
The given name of the user.
User name information.
sfuser.field.mapping.data
.LNAME
LASTNAME
The family name of the user.
User name information.
sfuser.field.mapping.data
.MI
MI
sfuser.field.mapping.data
.GENDER
GENDER
The middle initial of the user.
Most customers do not import gender into Learning because
they do not use it for learning assignments. When reporting in
Report Center, users' gender is available (for example, if you
wanted to be sure that men and women were assigned courses
equally).
Importing User Data from Platform with User Connector - SF
Field Mapping for User Connector - SF
CONFIDENTIAL
21
Maps to the platform
This Mapping Property and field in
Column from the SF
Learning...
People Export...
sfuser.field.mapping.data
.PERSON_ID_EXTERNAL
PERSON_ID_EXTER Always map this field. This is a unique identifier of a person. It
NAL
will eventually be used as the display identifier of a user record
And you Should Know This About How it is Used...
in Learning.
sfuser.field.mapping.data
.PERSON_GUID
PERSON_GUID
sfuser.field.mapping.data
.JP_ID
JOBCODE
Always map this field. This is the immutable unique identifier of
a person.
This is the job code of the user. The name of the mapping con­
figuration can be confusing: it is not job position; it is job code.
Job codes are useful for assigning learning and managing com­
petencies that you import to Learning. If the provided job code
ID does not exist in Learning, the connector creates it automati­
cally.
Recommended. Used to determine competency mapping in
Human Experience Management (HXM). In the LMS, this will be
the job code.
sfuser.field.mapping.data
.JP_DESC
N/A
Do not map JP_DESC. By leaving it unmapped, you avoid
complexity. You need the job code ID for assignment profiles
but don't need the description. When you do not map
JP_DESC, the value defaults to JP_ID (the description of the
job code is the ID of the job code). This works because of the
default copy mapping in
sfuser.connector.copy.field.mappings.
Additionally, we use the description only if the ID in same row
does not yet exist in Learning. When the connector automati­
cally creates the new job code ID, it uses this description. If the
ID already exists in Learning, the connector ignores the descrip­
tion.
sfuser.field.mapping.data
.JOB_TITLE
TITLE
Job Title is not directly associated with Job Position ID in Learn­
ing. Most customers skip title because it is not available to as­
signment profiles: you cannot assign courses automatically
based on job title.
Instead of using job title, customers use job code ID.
22
CONFIDENTIAL
Importing User Data from Platform with User Connector - SF
Field Mapping for User Connector - SF
Maps to the platform
This Mapping Property and field in
Column from the SF
Learning...
People Export...
And you Should Know This About How it is Used...
sfuser.field.mapping.data
.ROLE_ID
N/A
Do not map sfuser.field.mapping.data.ROLE_ID.
Instead, set
sfuser.connector.defaultValue.studentRoleI
D to your default user security role. You do this because almost
all Learning configurations use a single learner role. The
sfuser.field.mapping.data.ROLE_ID mapping is
provided for cases where you have a more complex implemen­
tation.
When you add a user, an invalid or no role then the connector
defaults to the value in the configuration file. If a role is invalid
or not supplied, the existing role is retained.
sfuser.field.mapping.data
.JL_ID
LOCATION
This is the location of the user. It can be useful for learning as­
signment in assignment profiles, but most customers find the
address fields more useful than location because they are more
specific. If provided Job Location ID does not exist in Learning,
the connector creates it automatically.
sfuser.field.mapping.data
.JL_DESC
N/A
Do not map JL_DESC. By leaving it unmapped, you avoid
complexity. You might need the job location for assignment
profiles but don't need the description. When you do not map
JL_DESC, the value defaults to JL_ID (the description of the
job location is the ID of the job location). This works because of
the default copy mapping in
sfuser.connector.copy.field.mappings.
Additionally, we use the description only if the ID in same row
does not yet exist in Learning. When the connector automati­
cally creates the new job location, it uses this description. If the
ID already exists in Learning, the connector ignores the descrip­
tion.
sfuser.field.mapping.data
.DMN_ID
N/A
Map sfuser.field.mapping.data.DMN_ID to the
data object where you store domain ID in SAP SuccessFactors
platform. If the domain ID you pass does not exist in Learning,
it is created automatically and under the standard configura­
tion should go to the holding domain. The connector does not
create or update parent relationships and it does not update ex­
isting domain records.
Importing User Data from Platform with User Connector - SF
Field Mapping for User Connector - SF
CONFIDENTIAL
23
Maps to the platform
This Mapping Property and field in
Column from the SF
Learning...
People Export...
And you Should Know This About How it is Used...
sfuser.field.mapping.data
.DMN_DESC
N/A
Most customers do not map the domain description. It is used
only if you add a domain ID for the user, and the domain does
not yet exist in Learning. In that case, the ID is added automati­
cally and gets the description from the column that you map to
sfuser.field.mapping.data.DMN_DESC. If the ID al­
ready exists in Learning, we ignore the value that you pass in
the column mapped to
sfuser.field.mapping.data.DMN_DESC. We do not
nullify it or change it.
sfuser.field.mapping.data
.ORG_ID
N/A
Users' organization ID is critical to learning assignments. You
almost always want to use assignment profiles to automatically
assign courses to users based on their organization ID. For ex­
ample, all users in the finance organization or all users in the
human resources organization should be assigned the same set
of courses.
Although Employee Central contains an organization ID, plat­
form stores only division and department names. For this rea­
son, you typically need to store the organization ID in a custom
data object in platform and then map
sfuser.field.mapping.data.ORG_ID to the custom
data object.
If you pass a value that does not yet exist in Learning, it is cre­
ated automatically for you. Under standard configuration, it is
sent to the holding domain so that you can find it and set its at­
tributes correctly. The connector does not create or update pa­
rent relationships, and it does not update existing organization
records.
sfuser.field.mapping.data
.EMP_TYP_ID
EMPLOYEE-CLASS
Use employee type with assignment profiles to automatically
assign courses to users based on their employee type. Em­
ployee type is a description, matched to your business, of how
you categorize employees. For example: student intern, con­
tractor, part time, full time, and so on. You often want to assign
courses by these categories.
Employee type is not usually a part of the core file and only in
the extended file. If you pass a value that does not yet exist in
Learning, it is created automatically for you.
24
CONFIDENTIAL
Importing User Data from Platform with User Connector - SF
Field Mapping for User Connector - SF
Maps to the platform
This Mapping Property and field in
Column from the SF
Learning...
People Export...
And you Should Know This About How it is Used...
sfuser.field.mapping.data
.EMP_TYP_DESC
N/A
This is rarely mapped because you cannot assign based on a
description and, for most companies, the ID is clear enough.
Additionally, we use the description only if the ID in same row
does not yet exist in Learning. When the connector automati­
cally creates the new employee type, it uses this description. If
the ID already exists in Learning, the connector ignores the de­
scription.
sfuser.field.mapping.data
.EMP_STAT_ID
EMPLSTATUS
Use employee status with assignment profiles to automatically
assign courses to users based on their employee status. It is a
description, matched to your business, of the current relation­
ship of the employee to the business. For example: full time,
family leave, disability leave, and so on. You often want to assign
courses by these categories.
Employee status isn’t usually a part of the core file and only in
the extended file. If you pass a value that doesn’t yet exist in
Learning, it’s created automatically for you.
sfuser.field.mapping.data
.EMP_STAT_DESC
N/A
This is rarely mapped because you cannot assign based on a
description and, for most companies, the ID is clear enough.
If the employee status ID already exists in Learning, we ignore
the value that you pass in the column mapped to
sfuser.field.mapping.data.EMP_STAT_ID.
Additionally, we use the description only if the ID in same row
does not yet exist in Learning. When the connector automati­
cally creates the new employee status, it uses this description.
If the ID already exists in Learning, the connector ignores the
description.
sfuser.field.mapping.data
.@ADDR1
ADDR1
Customers rarely change this mapping. It is the first line of the
street address of the user. You can assign learning by the ad­
dress.
sfuser.field.mapping.data
.@ADDR2
ADDR2
Customers rarely change this mapping. It is the second line of
the street address of the user. You can assign learning by the
address.
Learning does not support a second address line, so ADDR2
appends to ADDR1. For example, if in platform, ADDR1 is 123
Maple Street and ADDR2 is Apartment 456, then in Learning,
the address is 123 Maple Street Apartment 456.
Importing User Data from Platform with User Connector - SF
Field Mapping for User Connector - SF
CONFIDENTIAL
25
Maps to the platform
This Mapping Property and field in
Column from the SF
Learning...
People Export...
And you Should Know This About How it is Used...
sfuser.field.mapping.data
.CITY
CITY
Customers rarely change this mapping. It is the city of the user.
You can assign learning by the city: for example, all users in San
Fransisco might need to take a course that is required by the
city of San Fransisco.
sfuser.field.mapping.data
.STATE
STATE
Customers rarely change this mapping. It is the state or prov­
ince of the user. You can assign learning by the state or prov­
ince: for example, all users in California might need to take a
course that is required by the state of California.
sfuser.field.mapping.data
.POSTAL
ZIP
Customers rarely change this mapping. It is the postal code of
the user. You can assign learning by the postal code: for exam­
ple, you might assign courses to all postal codes surrounding a
city.
sfuser.field.mapping.data
.CNTRY
COUNTRY
Customers rarely change this mapping. It is the country of the
user. You can assign learning by the country: for example, you
might assign courses to all users in Germany.
You declare all countries in your Learning system by going to
References
Geography
Countries
. If you pass a value
that you have not yet declared, the connector rejects the user.
sfuser.field.mapping.data
.REGION_ID
N/A
Define regions in
Users
Regions
. Your list of regions is
the list of places where you have learning facilities. Most cus­
tomers do not use region to assign courses, but regions are
useful for search. Users often want to find courses in their re­
gion: at facilities that have their same region ID.
Of the mappings for User Connector - SF, region is most com­
monly a custom object.
If you pass a region ID does not exist in Learning, it is created
automatically.
The connector rejects the record if the Region ID is not valid.
sfuser.field.mapping.data
.EMAIL_ADDR
EMAIL
Users rarely change this mapping. It is the users' email address.
The users' email addresses are for notification email messages.
Learning email address validation settings are not applied dur­
ing Connector run.
26
CONFIDENTIAL
Importing User Data from Platform with User Connector - SF
Field Mapping for User Connector - SF
Maps to the platform
This Mapping Property and field in
Column from the SF
Learning...
People Export...
And you Should Know This About How it is Used...
sfuser.field.mapping.data
.HIRE_DTE
HIREDATE
This is the date that the user is hired in your company. As a pre­
requisite, allow hire dates in the future.
The hire date transforms as defined in
sfuser.field.transform.date.format.HIRE_DT
E
sfuser.field.mapping.data
.TERM_DTE
EXIT_DATE
This is the date that the user separated from your company. In
Learning, you can use it for data protection and privacy and to
search for users, but in Learning, the active status of the user is
more important. Termination date has rules to prevent you
from, for example, adding a termination date to an active em­
ployee.
This format must be: MON-DD-YYYY HH24:MI:SS
sfuser.field.mapping.data
.SUPER
MANAGER
This is users' manager in Learning. For the user at the top of the
learning manager hierarchy (usually your CEO), must have a
value of NO_MANAGER (in all caps) listed in the MANAGER data
object, so that the Learning knows how to treat this individual in
the routing chain. This value must be exactly NO_MANAGER.
Any other value fails.
sfuser.field.mapping.data
.RESUME_LOCN
N/A
Do not map this. Resume location is part of a legacy Plateau
feature. It is not useful for finding learning, assigning learning,
or reporting on learning.
sfuser.field.mapping.data
.COMMENTS
N/A
Most customers do not import comments about users. Instead,
they leave the comments in platform so that they can be cen­
trally managed. They are not useful for finding learning, assign­
ing learning, or reporting on learning.
sfuser.field.mapping.data
.ACCT_ID
N/A
sfuser.field.mapping.data
.PHON_NUM1
BIZ_PHONE
If you pass an account code that does not exist in Learning, the
connector creates it in the user’s domain.
You rarely change this. You also rarely change the default de­
scription in
sfuser.field.transform.data.PHON_NUM1_DESC
.@DEFAULT@
sfuser.field.mapping.data
.PHON_NUM2
FAX
You rarely change this. You also rarely change the default de­
scription in
sfuser.field.transform.data.PHON_NUM2_DESC
.@DEFAULT@
Importing User Data from Platform with User Connector - SF
Field Mapping for User Connector - SF
CONFIDENTIAL
27
Maps to the platform
This Mapping Property and field in
Column from the SF
Learning...
People Export...
And you Should Know This About How it is Used...
sfuser.field.mapping.data
.PHON_NUM3
N/A
Very few customers add a third phone number because plat­
form does not support a third phone number by default. If you
decide you need a third phone number, you must map a de­
scription in
sfuser.field.mapping.data.PHON_NUM3_DESC.
sfuser.field.mapping.data
.PHON_NUM3_DESC
N/A
sfuser.field.mapping.data
.COL_NUM1_VAL
CUSTOM01
You must map this to a data header if you map
sfuser.field.mapping.data.PHON_NUM3.
The connector adds custom field references as needed. Our
platform has 15 custom fields in the standard feed for all parts
of SAP SuccessFactors all enabled applications. In many cases,
the custom fields are not useful for assigning courses, finding
users, or reporting on courses, so think about whether you
need the values before you import them in the standard feed.
sfuser.field.mapping.data
.COL_NUM2_VAL
CUSTOM02
The connector adds custom field references as needed. Our
platform has 15 custom fields in the standard feed for all parts
of SAP SuccessFactors all enabled applications. In many cases,
the custom fields are not useful for assigning courses, finding
users, or reporting on courses, so think about whether you
need the values before you import them in the standard feed.
sfuser.field.mapping.data
.COL_NUM3_VAL
CUSTOM03
The connector adds custom field references as needed. Our
platform has 15 custom fields in the standard feed for all parts
of SAP SuccessFactors all enabled applications. In many cases,
the custom fields are not useful for assigning courses, finding
users, or reporting on courses, so think about whether you
need the values before you import them in the standard feed.
sfuser.field.mapping.data
.COL_NUM4_VAL
CUSTOM04
The connector adds custom field references as needed. Our
platform has 15 custom fields in the standard feed for all parts
of SAP SuccessFactors all enabled applications. In many cases,
the custom fields are not useful for assigning courses, finding
users, or reporting on courses, so think about whether you
need the values before you import them in the standard feed.
sfuser.field.mapping.data
.COL_NUM5_VAL
CUSTOM05
The connector adds custom field references as needed. Our
platform has 15 custom fields in the standard feed for all parts
of SAP SuccessFactors all enabled applications. In many cases,
the custom fields are not useful for assigning courses, finding
users, or reporting on courses, so think about whether you
need the values before you import them in the standard feed.
28
CONFIDENTIAL
Importing User Data from Platform with User Connector - SF
Field Mapping for User Connector - SF
Maps to the platform
This Mapping Property and field in
Column from the SF
Learning...
People Export...
And you Should Know This About How it is Used...
sfuser.field.mapping.data
.COL_NUM6_VAL
CUSTOM06
The connector adds custom field references as needed. Our
platform has 15 custom fields in the standard feed for all parts
of SAP SuccessFactors all enabled applications. In many cases,
the custom fields are not useful for assigning courses, finding
users, or reporting on courses, so think about whether you
need the values before you import them in the standard feed.
sfuser.field.mapping.data
.COL_NUM7_VAL
CUSTOM07
The connector adds custom field references as needed. Our
platform has 15 custom fields in the standard feed for all parts
of SAP SuccessFactors all enabled applications. In many cases,
the custom fields are not useful for assigning courses, finding
users, or reporting on courses, so think about whether you
need the values before you import them in the standard feed.
sfuser.field.mapping.data
.COL_NUM8_VAL
CUSTOM08
The connector adds custom field references as needed. Our
platform has 15 custom fields in the standard feed for all parts
of SAP SuccessFactors all enabled applications. In many cases,
the custom fields are not useful for assigning courses, finding
users, or reporting on courses, so think about whether you
need the values before you import them in the standard feed.
sfuser.field.mapping.data
.COL_NUM9_VAL
CUSTOM09
The connector adds custom field references as needed. Our
platform has 15 custom fields in the standard feed for all parts
of SAP SuccessFactors all enabled applications. In many cases,
the custom fields are not useful for assigning courses, finding
users, or reporting on courses, so think about whether you
need the values before you import them in the standard feed.
sfuser.field.mapping.data
.COL_NUM10_VAL
CUSTOM10
The connector adds custom field references as needed. Our
platform has 15 custom fields in the standard feed for all parts
of SAP SuccessFactors all enabled applications. In many cases,
the custom fields are not useful for assigning courses, finding
users, or reporting on courses, so think about whether you
need the values before you import them in the standard feed.
sfuser.field.mapping.data
.COL_NUM11_VAL
CUSTOM11
The connector adds custom field references as needed. Our
platform has 15 custom fields in the standard feed for all parts
of SAP SuccessFactors all enabled applications. In many cases,
the custom fields are not useful for assigning courses, finding
users, or reporting on courses, so think about whether you
need the values before you import them in the standard feed.
Importing User Data from Platform with User Connector - SF
Field Mapping for User Connector - SF
CONFIDENTIAL
29
Maps to the platform
This Mapping Property and field in
Column from the SF
Learning...
People Export...
And you Should Know This About How it is Used...
sfuser.field.mapping.data
.COL_NUM12_VAL
CUSTOM12
The connector adds custom field references as needed. Our
platform has 15 custom fields in the standard feed for all parts
of SAP SuccessFactors all enabled applications. In many cases,
the custom fields are not useful for assigning courses, finding
users, or reporting on courses, so think about whether you
need the values before you import them in the standard feed.
sfuser.field.mapping.data
.COL_NUM13_VAL
CUSTOM13
The connector adds custom field references as needed. Our
platform has 15 custom fields in the standard feed for all parts
of SAP SuccessFactors all enabled applications. In many cases,
the custom fields are not useful for assigning courses, finding
users, or reporting on courses, so think about whether you
need the values before you import them in the standard feed.
sfuser.field.mapping.data
.COL_NUM14_VAL
CUSTOM14
The connector adds custom field references as needed. Our
platform has 15 custom fields in the standard feed for all parts
of SAP SuccessFactors all enabled applications. In many cases,
the custom fields are not useful for assigning courses, finding
users, or reporting on courses, so think about whether you
need the values before you import them in the standard feed.
sfuser.field.mapping.data
.COL_NUM15_VAL
CUSTOM15
The connector adds custom field references as needed. Our
platform has 15 custom fields in the standard feed for all parts
of SAP SuccessFactors all enabled applications. In many cases,
the custom fields are not useful for assigning courses, finding
users, or reporting on courses, so think about whether you
need the values before you import them in the standard feed.
sfuser.field.mapping.data
.TIMEZONE
TIMEZONE
Do not change the default mapping.
sfuser.field.mapping.data
.LOCALE
LOCALE
Do not change the default mapping.
This is the default locale preference for the user. The locale
preference sets the date/number format preferences.
sfuser.field.mapping.data
.CAN_USE_ORG_ACT
N/A
This allows user’s to access the account codes available to their
linked organization ID for chargebacks. Map only if you use
commerce features.
30
CONFIDENTIAL
Importing User Data from Platform with User Connector - SF
Field Mapping for User Connector - SF
Maps to the platform
This Mapping Property and field in
Column from the SF
Learning...
People Export...
And you Should Know This About How it is Used...
sfuser.field.mapping.data
.CURRENCY_CODE
N/A
Do not change the mapping.
This is the currency preference for the user. The connector
does not update currency for existing records because users
can manage their own preferences.
If null defaults to the value of
sfuser.connector.defaultValue.preferenceCu
rrency. If the value is not in the list of declared currencies,
then the record is rejected.
sfuser.field.mapping.data
.ACCT_DESC
N/A
Used if you map
sfuser.field.mapping.data.ACCT_ID. This is not
often mapped because most customers have already set up
their accounts and descriptions and update only the ID.
If account code ID already exists, provided account code de­
scription is ignored. It does not overwrite or nullify the existing
value.
sfuser.field.mapping.data
.JP_EFF_DTE
N/A
This is not often mapped because although you might want to
know the job, its effective date is not important. If job position
change date is later than the system date when the connector
runs, record will be rejected (job code change effective date
cannot be in the future).
The format of the datetime is: MON-DD-YYYY HH24:MI:SS
sfuser.field.mapping.data
.MAPPED_ADMIN_ID
N/A
Provides mapping between user ID and admin ID.
Must be a valid administrator ID and must match the user ID. If
this value does not map to an administrator ID then the record
is rejected.
sfuser.field.mapping.data
.MAPPED_INST_ID
N/A
Provides mapping between user ID and instructor ID.
Must be a valid instructor ID and must match the user id. If this
value does not map to an instructor ID then the record is re­
jected.
Importing User Data from Platform with User Connector - SF
Field Mapping for User Connector - SF
CONFIDENTIAL
31
Maps to the platform
This Mapping Property and field in
Column from the SF
Learning...
People Export...
And you Should Know This About How it is Used...
sfuser.field.mapping.data
.ALT_SUPER1
N/A
In the configuration for User Connector - SF, ignore all mapping
fields that begin with
sfuser.field.mapping.data.ALT_SUPER or
sfuser.field.mapping.data.REMOVE_ALT_SUPER.
They are for infrequent cases: when customers build a custom
way of storing matrix managers and other users who are alter­
nate managers. They come with their own complex logic. Al­
most all customers can use standard configuration for the busi­
ness result they want: Human Resource Business Partners
(HRBP) and matrix managers helping managers manage their
learning. Standard configuration is:
 Sample Code
sfuser.field.mapping.data.TEMP_ALT_SU
PER=MATRIX_MANAGER
sfuser.field.mapping.data.HRBP=HR
sfuser.field.mapping.data
.ALT_SUPER2
N/A
In the configuration for User Connector - SF, ignore all mapping
fields that begin with
sfuser.field.mapping.data.ALT_SUPER or
sfuser.field.mapping.data.REMOVE_ALT_SUPER.
They are for infrequent cases: when customers build a custom
way of storing matrix managers and other users who are alter­
nate managers. They come with their own complex logic. Al­
most all customers can use standard configuration for the busi­
ness result they want: Human Resource Business Partners
(HRBP) and matrix managers helping managers manage their
learning. Standard configuration is:
 Sample Code
sfuser.field.mapping.data.TEMP_ALT_SU
PER=MATRIX_MANAGER
sfuser.field.mapping.data.HRBP=HR
32
CONFIDENTIAL
Importing User Data from Platform with User Connector - SF
Field Mapping for User Connector - SF
Maps to the platform
This Mapping Property and field in
Column from the SF
Learning...
People Export...
And you Should Know This About How it is Used...
sfuser.field.mapping.data
.ALT_SUPER3
N/A
In the configuration for User Connector - SF, ignore all mapping
fields that begin with
sfuser.field.mapping.data.ALT_SUPER or
sfuser.field.mapping.data.REMOVE_ALT_SUPER.
They are for infrequent cases: when customers build a custom
way of storing matrix managers and other users who are alter­
nate managers. They come with their own complex logic. Al­
most all customers can use standard configuration for the busi­
ness result they want: Human Resource Business Partners
(HRBP) and matrix managers helping managers manage their
learning. Standard configuration is:
 Sample Code
sfuser.field.mapping.data.TEMP_ALT_SU
PER=MATRIX_MANAGER
sfuser.field.mapping.data.HRBP=HR
sfuser.field.mapping.data
N/A
.REMOVE_ALT_SUPER1
In the configuration for User Connector - SF, ignore all mapping
fields that begin with
sfuser.field.mapping.data.ALT_SUPER or
sfuser.field.mapping.data.REMOVE_ALT_SUPER.
They are for infrequent cases: when customers build a custom
way of storing matrix managers and other users who are alter­
nate managers. They come with their own complex logic. Al­
most all customers can use standard configuration for the busi­
ness result they want: Human Resource Business Partners
(HRBP) and matrix managers helping managers manage their
learning. Standard configuration is:
 Sample Code
sfuser.field.mapping.data.TEMP_ALT_SU
PER=MATRIX_MANAGER
sfuser.field.mapping.data.HRBP=HR
Importing User Data from Platform with User Connector - SF
Field Mapping for User Connector - SF
CONFIDENTIAL
33
Maps to the platform
This Mapping Property and field in
Column from the SF
Learning...
People Export...
And you Should Know This About How it is Used...
sfuser.field.mapping.data
N/A
In the configuration for User Connector - SF, ignore all mapping
fields that begin with
.REMOVE_ALT_SUPER2
sfuser.field.mapping.data.ALT_SUPER or
sfuser.field.mapping.data.REMOVE_ALT_SUPER.
They are for infrequent cases: when customers build a custom
way of storing matrix managers and other users who are alter­
nate managers. They come with their own complex logic. Al­
most all customers can use standard configuration for the busi­
ness result they want: Human Resource Business Partners
(HRBP) and matrix managers helping managers manage their
learning. Standard configuration is:
 Sample Code
sfuser.field.mapping.data.TEMP_ALT_SU
PER=MATRIX_MANAGER
sfuser.field.mapping.data.HRBP=HR
sfuser.field.mapping.data
N/A
In the configuration for User Connector - SF, ignore all mapping
fields that begin with
.REMOVE_ALT_SUPER3
sfuser.field.mapping.data.ALT_SUPER or
sfuser.field.mapping.data.REMOVE_ALT_SUPER.
They are for infrequent cases: when customers build a custom
way of storing matrix managers and other users who are alter­
nate managers. They come with their own complex logic. Al­
most all customers can use standard configuration for the busi­
ness result they want: Human Resource Business Partners
(HRBP) and matrix managers helping managers manage their
learning. Standard configuration is:
 Sample Code
sfuser.field.mapping.data.TEMP_ALT_SU
PER=MATRIX_MANAGER
sfuser.field.mapping.data.HRBP=HR
sfuser.field.mapping.data
.SHOPPING_ACCT_TYPE
N/A
Do not map this field. If you configured the connector correctly,
the shopping account type is updated automatically based on
users' status. You configure the automatic update with
sfuser.field.transform.data.SHOPPING_ACCT_
TYPE.*.
34
CONFIDENTIAL
Importing User Data from Platform with User Connector - SF
Field Mapping for User Connector - SF
Maps to the platform
This Mapping Property and field in
Column from the SF
Learning...
People Export...
And you Should Know This About How it is Used...
sfuser.field.mapping.data
.ENABLE_SHOPPING_ACCT
N/A
If you are using the commerce features of Learning, then when
you import users, you might want to toggle their shopping ac­
count access. You can store the shopping account toggle in a
custom platform data object.
Many customers can simply not pass a value for
ENABLE_SHOPPING_ACCT because it defaults to enabled
(Y) if you do not pass a value. If you want to enable all users'
shopping accounts, therefore, you can do nothing and they are
enabled by default.
sfuser.field.mapping.data
.PTG_USER
N/A
sfuser.field.mapping.data
.POS_NUM_ID
N/A
This is the job position ID.
sfuser.field.mapping.data
.INCLUDE_IN_GOVT_REPORTIN
G
N/A
This is a flag on the user that makes the user show up in Train­
Do not map this field. This is part of a Plateau product that is no
longer supported.
ing Planner. Very few customers use training planner, so most
do not need to map this.
Map the training planner fields to custom data objects that
store the information in platform.
sfuser.field.mapping.data
.LGL_ENTITY_2483_ID
N/A
This is the Legal Entity ID used for training planner. If the data
file contains a legal entity ID that does not exist in Learning, the
connector creates it automatically.
Very few customers use training planner, so most do not need
to map this.
Map the training planner fields to custom data objects that
store the information in platform.
sfuser.field.mapping.data
.LGL_ENTITY_2483_DESC
N/A
The connector ignores the description except when the legal
entity ID is new (LGL_ENTITY_2483_ID) for the user. This is
the description of the legal entity.
Map the training planner fields to custom data objects that
store the information in platform.
sfuser.field.mapping.data
.LGL_COUNTRY_ID
N/A
The connector ignores the country ID except when the legal en­
tity ID is new (LGL_ENTITY_2483_ID) for the user. This is
the country that the legal entity belongs to.
Map the training planner fields to custom data objects that
store the information in platform.
Importing User Data from Platform with User Connector - SF
Field Mapping for User Connector - SF
CONFIDENTIAL
35
Maps to the platform
This Mapping Property and field in
Column from the SF
Learning...
People Export...
And you Should Know This About How it is Used...
sfuser.field.mapping.data
.EMP_CLASS_2483_ID
N/A
This is the Employee Class ID used for training planner. If pro­
vided Employee Class ID does not exist in Learning, the connec­
tor creates it automatically.
Very few customers use training planner, so most do not need
to map this.
sfuser.field.mapping.data
N/A
The connector ignores the country ID except when the em­
ployee class ID is new (EMP_CLASS_2483_ID) for the user.
.EMP_CLASS_2483_DESC
This is the country that the legal entity belongs to.
sfuser.field.mapping.data
N/A
.HOURLY_RATE
This is the hourly rate used for training planner.
Very few customers use training planner, so most do not need
to map this.
sfuser.field.mapping.data
N/A
This is the hourly rate currency used for training planner. This
must be a valid currency ID that you previously added to the
.HOURLY_RATE_CURRENY
currency list in Learning.
Very few customers use training planner, so most do not need
to map this.
sfuser.field.mapping.data
.REGULAR_TEMP_ID
N/A
This is the Regular Temp ID used for training planner. If pro­
vided Regular Temp ID does not exist in Learning, it will be cre­
ated automatically.
The Regular / Temp ID is a Learning attribute that is custombuilt for the training planner. Few customers use training plan­
ner, so most customers can ignore it and instead use Employee
Type. Employee types are more common and they map to
standard a standard platform field (EMPLOYEE-CLASS). Ig­
nore Regular / Temp ID if you do not use training planner.
sfuser.field.mapping.data
.FULLTIME
N/A
Do not map this field.
In SAP SuccessFactors Learning, the user attribute Is Full Time
is a legacy attribute. It was added to support Plateau
Compensation, a product that we no longer support. Instead of
using Is Full Time to indicate that someone is a full time user,
please use Employee Type instead. Employee Type is a more ac­
curate and more powerful way to categorize your employees
because you can, for example, add employee types of Full Time
Contractor and Full Time Employee: both work a full week but
one is an internal employee and the other is a contractor. When
you assign learning, therefore, you can more accurately target
the assignment with (for example) full time users who are inter­
nal, full time users who are contractors, or both.
36
CONFIDENTIAL
Importing User Data from Platform with User Connector - SF
Field Mapping for User Connector - SF
Maps to the platform
This Mapping Property and field in
Column from the SF
Learning...
People Export...
sfuser.field.mapping.data
.NATIVE_DEEPLINK_USER
NATIVE_DEEPLINK Do not change this mapping.
_USER
And you Should Know This About How it is Used...
This indicates whether the user can access native deep links. It
applies to how the user logs into the Learning to authenticate
and how users are processed for data protection and privacy.
For regular users (not external users), it should be N.
sfuser.field.mapping.data
.ADJUSTED_HOURLY_RATE
N/A
This is the adjusted hourly rate used for training planner.
Very few customers use training planner, so most do not need
to map this.
sfuser.field.mapping.data
.ADJUSTED_HOURLY_RATE_CUR
RENCY
N/A
This is the adjusted hourly rate currency used for training plan­
ner. This must be a valid currency ID that you previously added
to the currency list in Learning.
Very few customers use training planner, so most do not need
to map this.
sfuser.field.mapping.data
.AGE
N/A
Do not map this field.
sfuser.field.mapping.data
.DISABILITY_CLASSIFICATIO
N_ID
N/A
This is used for training planner. It is the user’s disability classi­
fication.
Very few customers use training planner, so most do not need
to map this.
sfuser.field.mapping.data
.TEMP_ALT_SUPER
MATRIX_MANAGER
We provide
sfuser.field.mapping.data.TEMP_ALT_SUPER as
a standard configuration to allow your matrix managers to help
supervise users' learning. You almost always map it to
MATRIX_MANAGER. Internally to SAP SuccessFactors Learn­
ing, the user you pass here is added as an alternate manager,
but the temporary alternate manager mapping handles the
logic and hides the complexity of direct mapping.
Because the user is added internally as an alternate manager,
the rules of alternate manager relationships are enforced: the
matrix manager must exist in Learning, the matrix manager ID
cannot be the same as the managed user's ID, and so on. If any
of the rules are violated, you see an error in the log and the
changes are rejected.
Importing User Data from Platform with User Connector - SF
Field Mapping for User Connector - SF
CONFIDENTIAL
37
Maps to the platform
This Mapping Property and field in
Column from the SF
Learning...
People Export...
And you Should Know This About How it is Used...
sfuser.field.mapping.data
.HRBP
HR
We provide sfuser.field.mapping.data.HRBP as a
standard configuration to allow your Human Resource Business
Partners (HRBP) managers to help supervise users' learning.
You almost always map it to HR. Internally to SAP SuccessFac­
tors Learning, the user you pass here is added as an alternate
manager, but the HRBP mapping handles the logic and hides
the complexity of direct mapping.
Because the user is added internally as an alternate manager,
the rules of alternate manager relationships are enforced: the
HRBP manager must exist in Learning, the HRBP manager ID
cannot be the same as the managed user's ID, and so on. If any
of the rules are violated, you see an error in the log and the
changes are rejected.
If you pass NO_HR the HRBP column for a user, then the con­
nector removes (nullifies) any HRBP users from the user in the
USERID column.
If the user in the HR field is inactive in SAP SuccessFactors
Learning, the connector does not associate the user in HR as
an HRBP with the user in USERID.
If the user in USERID is already associated with the user in HR,
the connector makes no changes to the association.
sfuser.field.mapping.data
.BIRTH_DATE
BIRTH_DATE
This is used for training planner to calculate the person's age
for government reporting.
Very few customers use training planner, so most do not need
to map this.
Related Information
Learning Regions [page 47]
SAP SuccessFactors Learning Native Deeplink User [page 49]
Mapping platform Data to Learning Fields [page 43]
Importing Custom Fields from platform to Learning [page 43]
Copying Values Between Input Columns in User Connector - SF [page 45]
Termination Date Processing for User Connector - SF [page 67]
Manager Processing for User Connector - SF [page 68]
Alternate Manager Processing Logic for User Connector - SF [page 69]
Manager, Matrix Manager, HRBP, and Alternate Manager Mapping in User Connector - SF [page 70]
Default Process Rules for Activating and Inactivating learners with User Connector - SF [page 72]
38
CONFIDENTIAL
Importing User Data from Platform with User Connector - SF
Field Mapping for User Connector - SF
Results of Inactivating Users in SAP SuccessFactors Learning [page 73]
How User Connector - SF Processes Custom Data [page 79]
Time Zone Processing for User Connector - SF [page 79]
Reference Values Processing in User Connector - SF [page 80]
Full Time Mapping for User Connector - SF [page 80]
4.2
User Connector - SF Live Profile (EXTENDED) Feed
Mapping
When you map extended fields, you declare that you want the value from the live profile export in platform to
populate a particular extended (usually custom column) field in Learning.
 Note
The most common use of the SF Live Profile (extended) mapping is to import custom data in platform to
custom data in Learning.
Default Field Mapping for the SF Live Profile Feed
This Mapping Property and field in
Maps to the platform Column from the
And you Should Know This About How
Learning...
SF Live Profile Export...
it is Used...
sfuser.extendeduser.field.m
apping.data.STUD_ID
^USERID
This is the unique leaner ID (LMS user ID)
of the user. It is required. Do not change
the mapping.
sfuser.extendeduser.field.m
apping.data.PERSON_GUID
PERSON_GUID
sfuser.extendeduser.field.m
apping.data.PERSON_ID_EXTER
NAL
PERSON_ID_EXTERNAL
Always map this field. This is the immuta­
ble unique identifier of a person.
Always map this field. This is a unique
identifier of a person. It will eventually be
used as the display identifier of a user re­
cord in Learning.
sfuser.extendeduser.field.m
apping.data.REGULAR_TEMP_ID
REGULAR-TEMP
The Regular / Temp ID is a Learning at­
tribute that is custom-built for the train­
ing planner. Few customers use training
planner, so most customers can ignore it
and instead use Employee Type. Em­
ployee types are more common and they
map to standard a standard platform
field (EMPLOYEE-CLASS). Ignore
Regular / Temp ID if you do not use train­
ing planner.
Importing User Data from Platform with User Connector - SF
Field Mapping for User Connector - SF
CONFIDENTIAL
39
This Mapping Property and field in
Maps to the platform Column from the
And you Should Know This About How
Learning...
SF Live Profile Export...
it is Used...
sfuser.extendeduser.field.m
apping.data.FULLTIME
IS-FULLTIME-EMPLOYEE
In SAP SuccessFactors Learning, the
user attribute Is Full Time is a legacy at­
tribute. It was added to support Plateau
Compensation, a product that we no lon­
ger support. Instead of using Is Full Time
to indicate that someone is a full time
user, please use Employee Type instead.
Employee Type is a more accurate and
more powerful way to categorize your
employees because you can, for exam­
ple, add employee types of Full Time
Contractor and Full Time Employee: both
work a full week but one is an internal
employee and the other is a contractor.
When you assign learning, therefore, you
can more accurately target the assign­
ment with (for example) full time users
who are internal, full time users who are
contractors, or both.
sfuser.extendeduser.field.m
apping.data.EMP_TYP_ID
EMPLOYEE-CLASS
Use employee type with assignment pro­
files to automatically assign courses to
users based on their employee type. Em­
ployee type is a description, matched to
your business, of how you categorize em­
ployees. For example: student intern,
contractor, part time, full time, and so on.
You often want to assign courses by
these categories.
Employee type is not usually a part of the
core file and only in the extended file. If
you pass a value that does not yet exist in
Learning, it is created automatically for
you.
40
CONFIDENTIAL
Importing User Data from Platform with User Connector - SF
Field Mapping for User Connector - SF
This Mapping Property and field in
Maps to the platform Column from the
And you Should Know This About How
Learning...
SF Live Profile Export...
it is Used...
sfuser.extendeduser.field.m
apping.data.EMP_STAT_ID
EMPLSTATUS
Use employee status with assignment
profiles to automatically assign courses
to users based on their employee status.
It is a description, matched to your busi­
ness, of the current relationship of the
employee to the business. For example:
full time, family leave, disability leave, and
so on. You often want to assign courses
by these categories.
Employee status isn’t usually a part of
the core file and only in the extended file.
If you pass a value that doesn’t yet exist
in Learning, it’s created automatically for
you.
sfuser.extendeduser.field.m
apping.data.BIRTH_DATE
BIRTH_DATE
This is used for training planner to calcu­
late the person's age for government re­
porting.
Very few customers use training planner,
so most do not need to map this.
Related Information
Learning Regions [page 47]
SAP SuccessFactors Learning Native Deeplink User [page 49]
Mapping platform Data to Learning Fields [page 43]
Importing Custom Fields from platform to Learning [page 43]
Copying Values Between Input Columns in User Connector - SF [page 45]
Termination Date Processing for User Connector - SF [page 67]
Manager Processing for User Connector - SF [page 68]
Alternate Manager Processing Logic for User Connector - SF [page 69]
Manager, Matrix Manager, HRBP, and Alternate Manager Mapping in User Connector - SF [page 70]
Default Process Rules for Activating and Inactivating learners with User Connector - SF [page 72]
Results of Inactivating Users in SAP SuccessFactors Learning [page 73]
How User Connector - SF Processes Custom Data [page 79]
Time Zone Processing for User Connector - SF [page 79]
Reference Values Processing in User Connector - SF [page 80]
Full Time Mapping for User Connector - SF [page 80]
Importing User Data from Platform with User Connector - SF
Field Mapping for User Connector - SF
CONFIDENTIAL
41
4.3
Downloading Learning Connector Templates
Download Learning connector templates to see sample import files so that you can see the correct format of
Learning connector import files.
Context
When you configure connectors, you usually want to know what Learning expects for the format of the file.
Connector files are delimited files where the first row is the header row, so by looking at an example of the headers,
you can see data that you can import with the connector file. If you match your delimited file to the template, and if
you followed the configuration of the data, you can expect a smooth data import.
Procedure
1. Go to SAP SuccessFactors Learning Administration and then go to
System Administration
Connectors
Download Connector Template .
2. In Action, decide if you want to download all headers or only the headers you have already mapped.
○ Select Download Template (all columns) if you want to see all possible columns that the connector accepts.
○ Select Download Template (only mapped columns) if you want to see what the connector accepts based on
your configuration. You map columns in
System Administration
Configuration
System Configuration
CONNECTORS .
3. In Connector, select the connector template that you want to download.
 Note
Competency - SF and User Connector - SF export from platform. For these connectors, also check the
headers in the export from platform.
4. In Supported files, select the file that you want to export for the connector.
 Note
Some connectors, like the learning item connector, use more than one import file.
5. In File extension, select the file extension for the export.
The headers remain the same regardless of the file format you choose, but we understand that some
companies restrict the types of files that their employees can download, so we offer you choices.
6. Choose Submit.
42
CONFIDENTIAL
Importing User Data from Platform with User Connector - SF
Field Mapping for User Connector - SF
4.4
Mapping platform Data to Learning Fields
Map platform data to Learning fields so that data from platform arrives to the correct fields in Learning for each
connector run. With the right data in the right fields, you can use the fields for learning assignment.
Procedure
1. Go to SAP SuccessFactors Learning Administration, go to
System Administration
Configuration
System
Configuration , and then edit CONNECTORS.
2. Find the configuration lines that begin sfuser.field.mapping.data..
3. For each line, add the platform column name from the export file that maps to the field in Learning.
For example, to map the export file column header STATUS to NOTACTIVE:
 Sample Code
sfuser.field.mapping.data.NOTACTIVE=STATUS
4. When you are finished, click Apply Changes
Related Information
Importing Custom Fields from platform to Learning [page 43]
Copying Values Between Input Columns in User Connector - SF [page 45]
Downloading Learning Connector Templates [page 42]
User Connector - SF People (CORE) Feed Mapping [page 20]
User Connector - SF Live Profile (EXTENDED) Feed Mapping [page 39]
4.5
Importing Custom Fields from platform to Learning
To add a user custom field in Learning, create it in platform, which is the system of record for user data, and then
import it to a Learning custom field with User Connector - SF.
Prerequisites
Create the custom data object in platform and verify that it exports through SF People or SF Live Profile. Pay
attention to which export includes the custom data. The SF People export contains a limited amount of custom
Importing User Data from Platform with User Connector - SF
Field Mapping for User Connector - SF
CONFIDENTIAL
43
fields. When you reach the limit, the custom data appears in the SF Live Profile export. You need to know which file
contains your custom data so that you can map correctly.
Context
Of the different custom data types, user custom data impacts Learning the most because you can use it to assign
courses based on the attributes of learners. For example, you might want to assign courses to users based on their
sales region, and the sales region might mean something different than training region to your organization. The
standard field region might represent the learners' geographic region so that they can find their closest training
facility, but a custom data object of sales region might be the region where they sell your product. A user might be
geographically located in Miami but sell to Argentina. By default, you can represent the user's geographic region
(Miami) with Region so that he or she can attend courses in your Miami facility. But Learning does not have a
default field to help you represent the sales region (Argentina) so that you can assign courses to help him or her
improve sales in that region (as opposed to a Miami based user who sells to Brazil, for example).
 Note
The properties file continues to use previous terminology for custom fields. For example, while the term
Custom Columns changed to Custom Fields, the references to these in the configuration properties files remain
as sfuser.field.customcolumn.<column number>.
Procedure
1. Go to
System Administration
Custom Fields
User
and create a custom column.
2. Look at the number in Field Number.
Field Number is the unique ID of this user custom column.
3. Go to
System Administration
Configuration
System Configuration
CONNECTORS .
4. If your custom data is in the SF People connector, map sfuser.field.customcolumn.<column number>
to the name of the field from the SF People (core) export.
For example, if the SF People (core) export contains sales_region as the column containing sales region, and
the field number of the sales region Learning custom field is 10, then map it as follows.
 Sample Code
# This maps sales_region from SF People (core) to user custom column number
10.
sfuser.field.customcolumn.10=sales_region
5. If your custom data is in the SF Live Profile (extended) export, then you map
sfuser.extendeduser.field.customcolumn.<column number> to the field from the SF Live Profile
export.
For example, if the SF Live Profile (extended) export contains sales_region as the field containing sales region,
and the field number of the sales region Learning custom field is 150, then map it as follows.
44
CONFIDENTIAL
Importing User Data from Platform with User Connector - SF
Field Mapping for User Connector - SF
 Sample Code
# This maps sales_region from SF People (core) to user custom column number
150.
sfuser.extendeduser.field.customcolumn.150=sales_region
6. Click Apply Changes.
Example
In this example, platform contains a custom data object for sales region and another for hiring source. In the
example, these objects are important to Learning to assign courses with an assignment profile based on the sales
region that the user covers and based on how the user was hired (this could be important for onboarding courses,
for example). The sales region is in the SF People (core) export file and the hiring source is in the SF Live Profile
(extended) export. The matching Learning custom column for sales region is 10 and the matching number for
hiring source is 20.
 Sample Code
sfuser.field.customcolumn.10=sales_region
sfuser.extendeduser.field.customcolumn.20=hiring_source
4.6
Copying Values Between Input Columns in User
Connector - SF
In User Connector - SF, you usually change the default copy behavior when you want to reuse the value from
platform data objects in more than one Learning field.
Context
Most customers can keep the default copy settings, but you can use it if you have one platform data object and you
want to map it to more than one Learning field. The connector prevents you from direct mapping, but you can map
one and then use the copy functionality to move the value to the second field.
Procedure
1. Go to SAP SuccessFactors Learning Administration, go to
System Administration
Configuration
System
Configuration , and then edit CONNECTORS.
Importing User Data from Platform with User Connector - SF
Field Mapping for User Connector - SF
CONFIDENTIAL
45
2. Find sfuser.connector.copy.field.mappings.
3. At the end of the values, add a comma and then add your copy command.
A copy command is two mapped fields separated by an equals sign (=). The field on the left must be unmapped
because it is receiving the value. It is the copy to field. The field on the right is mapped and it provides the value.
It is the copy from field.
In this example, we added , REGION_ID=ORG_ID. It is a comma (to separate it from the default copy
commands), a space, and then the command itself. You can read the command as: "Copy the value from
ORG_ID to REGION_ID." Using this copy command, ORG_ID is mapped to a platform data object (like
DEPARTMENT or DIVISION) and REGION_ID is not mapped.
 Sample Code
sfuser.connector.copy.field.mappings=<default commands>, REGION_ID=ORG_ID
4. Click Apply Changes
Example
You cannot, for example, map the platform data object DEPARTMENT to both ORG_ID and REGION_ID:
 Sample Code
# This configuration is incorrect and creates errors on import.
sfuser.field.mapping.data.ORG_ID=DEPARTMENT
sfuser.field.mapping.data.REGION_ID=DEPARTMENT
You can, however, map DEPARTMENT to ORG_ID only and then configure the connector to copy the value from
ORG_ID to REGION_ID. With copy, the configuration does not generate errors but the connector does put the value
of DEPARTMENT in both ORG_ID and REGION_ID.
 Sample Code
# This configuration is correct.
# DEPARTMENT is mapped to only one field (ORG_ID) - REGION_ID is unmapped.
sfuser.field.mapping.data.ORG_ID=DEPARTMENT
sfuser.field.mapping.data.REGION_ID=
# Add your copy command as a comma-separated value after the default copy
commands.
# Copy FROM is on the right side of the = sign. Copy TO is on the left.
# This reads as "Copy the value from ORG_ID to REGION_ID."
sfuser.connector.copy.field.mappings=<default commands>, REGION_ID=ORG_ID
46
CONFIDENTIAL
Importing User Data from Platform with User Connector - SF
Field Mapping for User Connector - SF
4.7
Connector Data Mapping Example
When you map connector data between source and destination, follow this example.
Data mapping is common in User Connector - SF because the data in SAP SuccessFactors platform is generic.
When you import it to SAP SuccessFactors Learning, you map it to the field that you want to use for learning. To
understand the mapping, consider the platform data objects DIVISION and DEPARTMENT.
Division and department mean something generic platform: simply the name of division or the department that the
employee belongs to. Learning, however, uses organizations to assign courses to users and the organization ID is
the most durable way to identify organizations. Division and department are names, however, and names can
change often.
To keep organization assignments through name changes, you typically create a custom data object in platform for
the organization ID and map it to the Learning organization ID. You go to
System Administration
Configuration
System Configuration and then find the place in learning that the data should map to. In this case, it is the
organization ID, or ORG_ID on the Learning side. You map it to the header name from the platform export. In this
case, the custom data comes in the Live Profile export and the header name with the information is
CUSTOM_ORG_ID.
 Sample Code
sfuser.field.mapping.data.ORG_ID=CUSTOM_ORG_ID
For example, here is a code snippet of the CUSTOM_ORG_ID column header in the Live Profile job.
 Sample Code
...,CUSTOM_SALES_REGION,CUSTOM_ORG_ID,CUSTOM_WORKS_COUNCIL,...
CUSTOM_ORG_ID is a custom column header among other custom data. In the example, the feed contains other
custom data like the employees' sales region and whether the employee has a works council.
4.8
Learning Regions
Learning regions are geographic centers that make sense for your physical learning environment: they are the
places where your facilities are located.
Add regions as part of implementing and maintaining your learning facilities. To define your regions, think about
where your training facilities are located. For example, if you have training centers (facilities) in Atlanta, New York,
Berlin, Johannesburg, Beijing, and Singapore, those cities are your regions. Regions allow you to schedule
instructors and facilities into courses at your facilities and recommend to users the closes regional facility.
The main benefit of regions is as a filter in search. Regions are an attribute that administrators and end users can
use as a filter to restrict search results. It is also a way to limit reporting data (to see, for example, the equipment in
and around Atlanta). For example, when administrators needs to identify the instructor for an agenda of a class,
Importing User Data from Platform with User Connector - SF
Field Mapping for User Connector - SF
CONFIDENTIAL
47
they can use the Region criteria to restrict the results of the instructor search to the region where the agendat of
the class is provided.
Regions are not the best way to assign learning with assignment profiles. Assignment profiles most often assign
required courses. Required courses are most often online, not instructor led in a classroom. Because regions are
based on your training facility locations, and therefore for instructor led courses, most customers use address
fields like city, postal code, or country for assignment profiles when they want to assign courses based on users'
geographic locations.
 Note
When you associate an instructor with a region, the system does not prevent administrators from scheduling
those instructors for offerings that take place in facilities outside of the region that is associated with the
instructor.
4.8.1 Why Regions Matter to Facilities and Your Physical
Learning Environment
Put facilities into regions so that when you want to find a place to hold your courses, you can find one in a region
where your users can easily attend the training.
Add facilities to regions as part of implementing and maintaining your physical learning environment. By adding a
facility to a region, you place the training facility within a geography that your organization recognizes. For example,
you might divide your regions by cities where you have a presence: Atlanta, New York, Berlin, Johannesburg,
Beijing, and Mumbai. You understand that you can schedule courses in facilities near or in those cities, so you
associate facilities to the regions (the area around the city).
Later, when a training administrator is scheduling training near those cities, he or she can look up the facilities by
region. Furthermore, users can search for training in their own region (a user near Beijing, for example, can search
for training in the Beijing region.
Add facilities to regions in SAP SuccessFactors Learning by going to
References
Facilities . Manage facilities in
Facilities .
References
Physical Resources
Geography
Regions
4.8.2 Why Regions Matter to Instructors and your Physical
Learning Environment
Put instructors into regions so that when you want to find an instructor, you can find one in a region where your
users can easily attend the training.
Add instructors to regions as part of implementing and maintaining your physical learning environment. By adding
an instructor to a region, you place the instructor within a geography that your organization recognizes. For
example, you might divide your regions by cities where you have a presence: Atlanta, New York, Berlin,
Johannesburg, Beijing, and Mumbai. You understand that you can schedule instructors into courses near or in
those cities, so you associate instructors to the regions (the area around the city).
48
CONFIDENTIAL
Importing User Data from Platform with User Connector - SF
Field Mapping for User Connector - SF
Later, when a training administrator is scheduling training near those cities, they can look up the instructors by
region. Furthermore, users can search for specific courses being taught by instructors in their own region (a user
near Beijing, for example, can search for training in the Beijing region).
Add instructors to regions in SAP SuccessFactors Learning by going to
References
Instructors . Manage facilities in
Facilities .
4.9
References
Geography
Regions
Geography
Regions
SAP SuccessFactors Learning Native Deeplink User
How you set native deeplink controls how Learning recognizes both link redirects and also how it recognizes the
user as native or not native.
Depending on how you set Native Deeplink User, you mark the user as either coming in from Human Experience
Management (HXM) through the connector or a user who is native to learning. Your user base can be mixed, with
some Human Experience Management (HXM) users and some native Learning users.
● If the user is native to Learning and has no record in SAP SuccessFactors platform, set Native Deeplink User to
Yes or true.
● If the user is not managed in Learning but is instead is managed in SAP SuccessFactors platform, set Native
Deeplink User to No or false.
Native Deeplink Effects on URLs
Stand-alone customers' users are tagged as Native Deeplink users. This tag changes the way that URLs are
constructed for the users' deeplinks. If those users later become part of an integrated environment, their URLs
continue to be formatted for a stand-alone environment, and so they break in an integrated environment. By
enabling the redirect, SAP SuccessFactors redirects them from the stand-alone URL to the integrated URL.
Native Deeplink Effects on Delete Inactive Native Users Automatic Process
The delete native inactive users automatic process deletes users who are not part of SAP SuccessFactors platform.
The process uses the value of Native Deeplink as one way to distinguish between platform users and native users. If
you set Native Deeplink incorrectly, the process can skip native users who should be deleted and delete platform
users who should not be deleted.
Importing User Data from Platform with User Connector - SF
Field Mapping for User Connector - SF
CONFIDENTIAL
49
5
Export and Import Jobs Creation for User
Connector - SF
After you make the initial configuration and field mapping of User Connector - SF, you create an export job to pull
the user data out of platform and an import job (connector job) to pull the data into Learning.
When you configure User Connector - SF, you first manage some initial configuration to set up the rules of the
connector, then you configure how fields in platform map to Learning, then you define the data feed schedule from
platform, and then test and troubleshoot the connector.
You create multiple jobs:
● In platform provisioning, you create three types of export jobs to put the export file on the SFTP site.
○ One job to get the changed, core employee information - it runs daily
○ One job to get the full, core employee information - it runs weekly
○ One job to get the full, extended employee information - it runs weekly
● In Learning Administration, you create an import job, what Learning calls a connector job, to import the data
from the SFTP site.
5.1
Types of Employee Export Jobs for User Connector - SF
When you configure the employee export from SAP SuccessFactors platform for User Connector - SF, you schedule
different job types for different times: a full export of two files, a delta export of two files.
To balance performance and data requirements, most customers run three different employee export jobs on
different schedules.
Full Employee Export Job
The full employee export job exports all employee data, regardless of whether it has changed or not. Because it is a
full export, it ensures that any employee data is loaded into Learning, but because it is also a large set of data, it
takes a long time to process. To balance the requirements of full data with the processing time, set up an export job
with Job Type set to Employee Export, and schedule it to run over the weekend.
Delta Employees Export Job
The delta employee export job exports data that has changed for users so that User Connector - SF can import
changes into Learning. This is a partial export. Because it is a partial export, it is a smaller set of data (and faster to
load). To balance the requirements of processing time with data, set up an export job with Job Type set to Delta
Employees Export to run daily and get the latest changed data.
50
CONFIDENTIAL
Importing User Data from Platform with User Connector - SF
Export and Import Jobs Creation for User Connector - SF
Full Live Profile Export Job
The full live profile export job exports all custom employee data, including critical data for Learning, whether the
data has changed or not. Because it is a full export, it ensures that any employee data is loaded into Learning, but
because it is also a large set of data, it takes a long time to process. To balance the requirements of full data with
the processing time, set up an export job with Job Type set to Live Profile Export and schedule it to run weekly over
the weekend.
Delta Live Profile Export Job
The delta live profile export job exports data that has changed for users so that User Connector - SF can import
changes into Learning. This is a partial export. Because it is a partial export, it is a smaller set of data (and faster to
load). To balance the requirements of processing time with data, set up an export job with Job Type set to Delta Live
Profile Export to run daily and get the latest changed data.
5.2
Scheduling Weekly Employee Export Job Type for User
Connector - SF
Run the Employee Export job type weekly for a full export of users from platform for User Connector - SF to catch
all changed data for employees.
Procedure
1. Go to Provisioning, select your company, click Manage Scheduled Jobs, and then click Create New Job
You see the Create New Job page with Job Definition and Job Occurrence & Notification sections.
2. In Job Definition, define the basic attributes of the report.
Attribute
Description
Job Name
This is a recognizable job name to make it easier for you to
find later. For example, type Full Employee Export
for Learning - Weekly
Job Owner
This is the owner of the job. This user must have Role Based
Permissions (RBP) to run this report and receives notifica­
tions for the report.
Job Type
Select Employees Export.
Required for SuccessFactors Learning Sync
Always select Required for SuccessFactors Learning Sync so
that you export the PERSON_GUID and
PERSON_ID_EXTERNAL columns.
Importing User Data from Platform with User Connector - SF
Export and Import Jobs Creation for User Connector - SF
CONFIDENTIAL
51
Attribute
Job Parameters
Description
Character Encoding
Select Unicode (UTF-8).
3. In Server Access, provide the information for the SFTP server where the export process puts the exported data
file.
Option
Description
Host Address
Most customers use their SAP SuccessFactors SFTP server:
select SF hosted SFTP server. If you cannot use the SAP
SuccessFactors SFTP server, type the address with the port.
FTP Login
Type the user ID that SAP SuccessFactors uses to authenti­
cate to the SFTP server. The user ID must have access to the
server and to the file path where you write the data file.
FTP Password
Type the password that SAP SuccessFactors uses to authen­
ticate to the SFTP server.
SFTP Protocol
Select SFTP Protocol.
4. Click Test Connection to test that you added the host, login, and password correctly for the SFTP site.
5. In File Access, provide the information about the directory where SAP SuccessFactors writes the exported data
file.
Option
Description
File Path
The directory path, from the SFTP user ID home, where SAP
SuccessFactors writes the exported data file.
File Name
The file name for the exported data file. Remember to check
your prefix settings and expected multiple file names in
Learning, in the CONNECTORS system configuration file.
Date Format
Select MMddyyyy to match the expected, default configura­
tion in Learning.
File Encryption
Select PGP.
6. Click Test File Put Permission to test the file access settings.
7. Go to Job Occurrence & Notification.
8. In Occurrence, select Recurring, and then in the Recurring Pattern group, set:
Selection
Description
Weekly
This is the full load of data. To balance performance and
data, run this job weekly, not daily.
Every week on
Set this to run on a day of the week instead of a calculated
day.
Saturday
Set this to run on Saturday so that you can run the extended
file on Sunday.
9. In Start Date, check the local time of the server to orient you to time differences and then schedule the job to
start at a time when you expect low server load for your company.
10. Click Create Job.
52
CONFIDENTIAL
Importing User Data from Platform with User Connector - SF
Export and Import Jobs Creation for User Connector - SF
Next Steps
As a quality step, verify that what you added in SAP SuccessFactors platform for the file export matches the
information that Learning expects to find the file for import. Go to SAP SuccessFactors Learning Administration,
and then go to
System Admin
Configuration
System Configuration
CONNECTORS
to verify:
● That the SFTP and directory locations in Learning matches the information you add here
● That your file suffix system in connector.input.file.name.tenant.suffix.* is set and matches the
information you enter here
● That you have the PGP encryption information to read the encrypted file
● That your date format matches the exported format
Related Information
Verifying Hire Date Transformation for User Connector - SF [page 81]
Configuring the Connector FTP Site [page 7]
User Connector - SF People (CORE) Feed Mapping [page 20]
User Connector - SF Live Profile (EXTENDED) Feed Mapping [page 39]
5.3
Scheduling Daily Delta Employees Export Job Type for
User Connector - SF
Run the Delta Employees Export job type daily to export the extended user data from platform for User Connector SF so that you get the extended information for custom columns.
Procedure
1. Go to Provisioning, select your company, click Manage Scheduled Jobs, and then click Create New Job
You see the Create New Job page with Job Definition and Job Occurrence & Notification sections.
2. In Job Definition, define the basic attributes of the report.
Attribute
Description
Job Name
This is a recognizable job name to make it easier for you to
find later. For example, type Delta Core Employee
Data - Daily
Job Owner
Importing User Data from Platform with User Connector - SF
Export and Import Jobs Creation for User Connector - SF
This is the owner of the job. This user must have Role Based
Permissions (RBP) to run this report and receives notifica­
tions for the report.
CONFIDENTIAL
53
Attribute
Description
Job Type
Select Delta Employees Export.
Required for SuccessFactors Learning Sync
Always select Required for SuccessFactors Learning Sync so
that you export the PERSON_GUID and
PERSON_ID_EXTERNAL columns.
Job Parameters
Character Encoding
Select Unicode (UTF-8).
3. In Server Access, provide the information for the SFTP server where the export process puts the exported data
file.
Option
Description
Host Address
Most customers use their SAP SuccessFactors SFTP server:
select SF hosted SFTP server. If you cannot use the SAP
SuccessFactors SFTP server, type the address with the port.
FTP Login
Type the user ID that SAP SuccessFactors uses to authenti­
cate to the SFTP server. The user ID must have access to the
server and to the file path where you write the data file.
FTP Password
Type the password that SAP SuccessFactors uses to authen­
ticate to the SFTP server.
SFTP Protocol
Select SFTP Protocol.
4. Click Test Connection to test that you added the host, login, and password correctly for the SFTP site.
5. In File Access, provide the information about the directory where SAP SuccessFactors writes the exported data
file.
Option
Description
File Path
The directory path, from the SFTP user ID home, where SAP
SuccessFactors writes the exported data file.
File Name
The file name for the exported data file. Remember to check
your prefix settings and expected multiple file names in
Learning, in the CONNECTORS system configuration file.
Date Format
Select MMddyyyy to match the expected, default configura­
tion in Learning.
File Encryption
Select PGP.
6. Click Test File Put Permission to test the file access settings.
7. Go to Job Occurrence & Notification.
8. In Occurrence, select Recurring, and then in the Recurring Pattern group, set:
Selection
Description
Daily
To balance performance and data, run this delta job daily.
Hour
Set the job to run at an hour of the day when you expect low
server load.
Minute
In most cases, you can select zero (0).
9. In Start Date, check the local time of the server to orient you to time differences and then schedule the job to
start at a time when you expect low server load for your company.
54
CONFIDENTIAL
Importing User Data from Platform with User Connector - SF
Export and Import Jobs Creation for User Connector - SF
10. Click Create Job.
Next Steps
As a quality step, verify that what you added in SAP SuccessFactors platform for the file export matches the
information that Learning expects to find the file for import. Go to SAP SuccessFactors Learning Administration,
and then go to
System Admin
Configuration
System Configuration
CONNECTORS
to verify:
● That the SFTP and directory locations in Learning matches the information you add here
● That your file suffix system in connector.input.file.name.tenant.suffix.* is set and matches the
information you enter here
● That you have the PGP encryption information to read the encrypted file
● That your date format matches the exported format
Related Information
Verifying Hire Date Transformation for User Connector - SF [page 81]
Configuring the Connector FTP Site [page 7]
User Connector - SF People (CORE) Feed Mapping [page 20]
User Connector - SF Live Profile (EXTENDED) Feed Mapping [page 39]
5.4
Scheduling Weekly Live Profile Export Job Type for User
Connector - SF
Run the Live Profile Export job type weekly to export the extended user data from platform for User Connector - SF
so that you get the extended information for custom columns.
Procedure
1. Go to Provisioning, select your company, click Manage Scheduled Jobs, and then click Create New Job
You see the Create New Job page with Job Definition and Job Occurrence & Notification sections.
2. In Job Definition, define the basic attributes of the report.
Attribute
Description
Job Name
This is a recognizable job name to make it easier for you to
find later. For example, type Custom Data Employee
Export for Learning - Weekly
Importing User Data from Platform with User Connector - SF
Export and Import Jobs Creation for User Connector - SF
CONFIDENTIAL
55
Attribute
Description
Job Owner
This is the owner of the job. This user must have Role Based
Permissions (RBP) to run this report and receives notifica­
tions for the report.
Job Type
Select Live Profile Export.
Job Parameters
Character Encoding
Select Unicode (UTF-8).
3. In Server Access, provide the information for the SFTP server where the export process puts the exported data
file.
Option
Description
Host Address
Most customers use their SAP SuccessFactors SFTP server:
select SF hosted SFTP server. If you cannot use the SAP
SuccessFactors SFTP server, type the address with the port.
FTP Login
Type the user ID that SAP SuccessFactors uses to authenti­
cate to the SFTP server. The user ID must have access to the
server and to the file path where you write the data file.
FTP Password
Type the password that SAP SuccessFactors uses to authen­
ticate to the SFTP server.
SFTP Protocol
Select SFTP Protocol.
4. Click Test Connection to test that you added the host, login, and password correctly for the SFTP site.
5. In File Access, provide the information about the directory where SAP SuccessFactors writes the exported data
file.
Option
Description
File Path
The directory path, from the SFTP user ID home, where SAP
SuccessFactors writes the exported data file.
File Name
The file name for the exported data file. Remember to check
your prefix settings and expected multiple file names in
Learning, in the CONNECTORS system configuration file.
Date Format
Select MMddyyyy to match the expected, default configura­
tion in Learning.
File Encryption
Select PGP.
6. Click Test File Put Permission to test the file access settings.
7. Go to Job Occurrence & Notification.
8. In Occurrence, select Recurring, and then in the Recurring Pattern group, set:
Selection
Description
Weekly
To balance performance and data, run this job weekly, not
daily.
Every week on
Set this to run on a day of the week instead of a calculated
day.
Sunday
Set this to run on Sunday so that you can run the full export
on Saturday.
9. In Start Date, check the local time of the server to orient you to time differences and then schedule the job to
start at a time when you expect low server load for your company.
56
CONFIDENTIAL
Importing User Data from Platform with User Connector - SF
Export and Import Jobs Creation for User Connector - SF
10. Click Create Job.
Next Steps
As a quality step, verify that what you added in SAP SuccessFactors platform for the file export matches the
information that Learning expects to find the file for import. Go to SAP SuccessFactors Learning Administration,
and then go to
System Admin
Configuration
System Configuration
CONNECTORS
to verify:
● That the SFTP and directory locations in Learning matches the information you add here
● That your file suffix system in connector.input.file.name.tenant.suffix.* is set and matches the
information you enter here
● That you have the PGP encryption information to read the encrypted file
● That your date format matches the exported format
Related Information
Verifying Hire Date Transformation for User Connector - SF [page 81]
Configuring the Connector FTP Site [page 7]
User Connector - SF People (CORE) Feed Mapping [page 20]
User Connector - SF Live Profile (EXTENDED) Feed Mapping [page 39]
5.5
Scheduling Daily Live Profile Export Job Type for User
Connector - SF
Run the Delta Live Profile Export job type daily to export the extended user data from platform for User Connector SF so that you get the extended information for custom columns.
Procedure
1. Go to Provisioning, select your company, click Manage Scheduled Jobs, and then click Create New Job
You see the Create New Job page with Job Definition and Job Occurrence & Notification sections.
2. In Job Definition, define the basic attributes of the report.
Attribute
Description
Job Name
This is a recognizable job name to make it easier for you to
find later. For example, type Custom Data Employee
Export for Learning - Daily
Importing User Data from Platform with User Connector - SF
Export and Import Jobs Creation for User Connector - SF
CONFIDENTIAL
57
Attribute
Description
Job Owner
This is the owner of the job. This user must have Role Based
Permissions (RBP) to run this report and receives notifica­
tions for the report.
Job Type
Select Delta Live Profile Export.
Job Parameters
Character Encoding
Select Unicode (UTF-8).
3. In Server Access, provide the information for the SFTP server where the export process puts the exported data
file.
Option
Description
Host Address
Most customers use their SAP SuccessFactors SFTP server:
select SF hosted SFTP server. If you cannot use the SAP
SuccessFactors SFTP server, type the address with the port.
FTP Login
Type the user ID that SAP SuccessFactors uses to authenti­
cate to the SFTP server. The user ID must have access to the
server and to the file path where you write the data file.
FTP Password
Type the password that SAP SuccessFactors uses to authen­
ticate to the SFTP server.
SFTP Protocol
Select SFTP Protocol.
4. Click Test Connection to test that you added the host, login, and password correctly for the SFTP site.
5. In File Access, provide the information about the directory where SAP SuccessFactors writes the exported data
file.
Option
Description
File Path
The directory path, from the SFTP user ID home, where SAP
SuccessFactors writes the exported data file.
File Name
The file name for the exported data file. Remember to check
your prefix settings and expected multiple file names in
Learning, in the CONNECTORS system configuration file.
Date Format
Select MMddyyyy to match the expected, default configura­
tion in Learning.
File Encryption
Select PGP.
6. Click Test File Put Permission to test the file access settings.
7. Go to Job Occurrence & Notification.
8. In Occurrence, select Recurring, and then in the Recurring Pattern group, set:
Selection
Description
Daily
To balance performance and data, run this delta job daily.
Hour
Set the job to run at an hour of the day when you expect low
server load.
Minute
In most cases, you can select zero (0).
9. In Start Date, check the local time of the server to orient you to time differences and then schedule the job to
start at a time when you expect low server load for your company.
10. Click Create Job.
58
CONFIDENTIAL
Importing User Data from Platform with User Connector - SF
Export and Import Jobs Creation for User Connector - SF
Next Steps
As a quality step, verify that what you added in SAP SuccessFactors platform for the file export matches the
information that Learning expects to find the file for import. Go to SAP SuccessFactors Learning Administration,
and then go to
System Admin
Configuration
System Configuration
CONNECTORS
to verify:
● That the SFTP and directory locations in Learning matches the information you add here
● That your file suffix system in connector.input.file.name.tenant.suffix.* is set and matches the
information you enter here
● That you have the PGP encryption information to read the encrypted file
● That your date format matches the exported format
5.6
Scheduling Learning Connector Jobs
Schedule learning connector jobs daily so that the connector knows when to import data.
Procedure
1. Go to SAP SuccessFactors Learning Administration and then go to
System Administration
Connectors .
2. Find the connector that you want to schedule and select it.
If you want to schedule User Connector - SF, for example, select User Connector - SF.
3. Choose Schedule This Process.
4. Schedule the process to run daily at the least disruptive time to for your business.
 Note
If you schedule multiple connectors to run on an hourly basis, then you can't define the sequence of
executing these jobs.
Importing User Data from Platform with User Connector - SF
Export and Import Jobs Creation for User Connector - SF
CONFIDENTIAL
59
6
Person IDs Connector
SAP SuccessFactors Learning has improved the process for adding Person IDs to Learning so that you can keep
users in sync.
The standard method of integration for user data synchronization between SAP SuccessFactors platform and SAP
SuccessFactors Learning uses the Employee Export from platform and the SF User connector in Learning.
Customers who don't use this standard method of integration were asked to alter their integration mechanism to
account for the <PERSON_GUID> and <PERSON_ID_EXTERNAL> fields. This was challenging for some customers
due to the complexities and cost associated with making such a change.
The Person IDs connector provides a simple method for integrating these two fields that are required for many
suite-wide capabilities.
Customers who are already using the standard integration mechanism or are using an alternate integration method
for these two fields shouldn't enable the Person IDs connector.
 Note
The User and Federal User connectors only support <PERSON_ID_EXTERNAL>. They don't support
<PERSON_GUID>.
6.1
Enabling Person GUID Export
The Person GUID Export is a predelivered business scenario used to export data from SAP SuccessFactors
platform for use with the Person ID connector in SAP SuccessFactors Learning. This option is for customers who
haven't implemented the standard method of data synchronization between SAP SuccessFactors platform and
SAP SuccessFactors Learning, which uses the Employee Export.
Prerequisites
● Role-Based Permissions
● Metadata Framework
Procedure
1. Go to
Admin Center
Business Scenarios .
2. Find Person GUID Export and activate it.
60
CONFIDENTIAL
Importing User Data from Platform with User Connector - SF
Person IDs Connector
3. Choose  (Edit Integration) to configure the scenario.
4. Go to Destination Settings, enter File Server Settings for SFTP Server, and File Folder that are located in the
server to store the generated CSV files.
You need the FTP site later when you set up the Person ID connector in SAP SuccessFactors Learning.
5. Go to Scheduling to set up the job scheduling based on your business needs.
6. Go to Review and Run to see the configuration summary.
7. Choose Save to save the current version.
○ Choose Set Schedule to deploy the current version to the scheduler.
○ Choose Run Now to execute the current version immediately and send file to the destination server without
impacting the schedule.
Next Steps
Check the job execution status in
Admin Center
Execution Manager Dashboard .
Related Information
Using Role Based Permissions
Implementing Metadata Framework
6.2
Setting Up the SAP SuccessFactors Learning Person IDs
Connector
Use the Person IDs connector to synchronize the <PERSON_GUID> and <PERSON_ID_EXTERNAL> fields between
SAP SuccessFactors platform and SAP SuccessFactors Learning.
Procedure
1. Go to SAP SuccessFactors Learning Administration and then go to
Management
System Administration
Security
Role
.
2. Search for the roles you want to add your permissions to.
3. Choose the Edit icon to edit the roles.
4. Go to the Permissions tab and add permissions by selecting Add One or More from List.
5. Add the Edit Person IDs Connector and View Person IDs Connector permissions to all roles.
Importing User Data from Platform with User Connector - SF
Person IDs Connector
CONFIDENTIAL
61
6. Configure the SFTP location. Refer to the topic on Configuring the Connector FTP Site [page 7]
7. Test the FTP connection settings. Refer to the topic on troubleshooting connectors [page 63]
8. Schedule the process by going to
System Administration
Connectors
Person IDs Connector .
 Note
Schedule your process to start after the Person GUID Export ends in the Admin Center.
62
CONFIDENTIAL
Importing User Data from Platform with User Connector - SF
Person IDs Connector
7
Troubleshooting Connectors
Troubleshoot connectors if you see problems in SAP SuccessFactors Learning data and you suspect a connector
problem or if you received an e-mail about a connector problem.
Prerequisites
● Enable the connector archive to save for 3 months
● Enable the connector logs
Procedure
1. Go to Learning Administration, go to
that you want to troubleshoot.
System Administration
Connectors , and then select the connector
 Tip
User Connector - SF is the most common connector for trouble because you run it so frequently. For
validated customers, it’s either User Connector - SF or Item Connector. If you see problems with course
and you integrate with Skillsoft, check Skillsoft Connector.
2. Choose Test FTP Connection to verify that SAP SuccessFactors Learning can reach and use the SFTP site.
The test checks:
○ The URI of the SFTP server or for general errors in connection
○ The username and password configured for the connector
○ The permissions and folder configuration for read access
○ The permissions and folder configuration for write access
To resolve trouble, go to System Administration Configuration System Configuration CONNECTORS
and check the SFTP settings. Also check that your username and password and the permissions on the SFTP
site folders.
3. Choose View Errors to see the errors in the connector and troubleshoot them individually.
4. Choose View Results to see the results of the connector run, including successful jobs.
○ To view the configuration changes for a connector run, choose
Current Configuration changes.
○ To see the columns that the connector processed, choose
Reading following fields from Input file.
View Results
View Results
View Logs . Find the text
View Logs . Find the text
○ To view detailed information for the delta changes that happened during the connector run, choose
Results
View
View Logs . Find the text Update Statistics.
Importing User Data from Platform with User Connector - SF
Troubleshooting Connectors
CONFIDENTIAL
63
○ To access connector report while Connector run is in progress, choose
Connector Run
View Results
Current
Run Detail Report .
Related Information
Update on Null for User Connector - SF [page 80]
Verifying that User Connector - SF Allows Rehires [page 68]
7.1
Connector Prefixes in SAP SuccessFactors Learning
Configuration
In SAP SuccessFactors Learning configuration, the connector prefix defines which connector the configuration
applies to.
Finding the right configuration prefix can be hard because the prefix in
System Configuration
CONNECTORS
System Administration
Configuration
uses abbreviations. This table decodes the prefixes.
Common Connectors and Prefixes
These connectors are very commonly used in most SAP SuccessFactors Learning implementations.
This Connector
Uses This Prefix in CONNECTORS sys­
tem properties
Competency Connector - competency.sf.*
SF
competency.sfcompetency.*
Notes
Unlike other connectors, the file type of the Compe­
tency Connector - SF is *.zip. You can change the file
name in the CONNECTORS system properties file in the
competency.connector.input.file.name5 property.
Item Connector
item.*
Most customers us Item Connector during initial imple­
mentation only.
Learning History
Connector
learninghistory.*
Skillsoft Connector
skillsoft.*
Run Learning History Connector one time during initial
implementation.
This connector is common for customers who have a
Skillsoft integration.
User Connector - SF
64
CONFIDENTIAL
sfuser.*
This connector is required.
Importing User Data from Platform with User Connector - SF
Troubleshooting Connectors
Uncommon Connectors and Prefixes
These connectors are sometimes used in SAP SuccessFactors Learning implementations. They can be used to load
data in bulk from another system.
This Connector
Uses This Prefix in CONNECTORS sys­
tem properties
Admin Connector
admin.*
Domain Connector
domain.*
Organization Connector
organization.*
Notes
Connectors and Prefixes to Ignore
These connectors are so rarely used or they fit such a specific case that most customers can ignore them.
 Note
Connector prefixes continue to use previous terminology. For example, while the term Scheduled Offering
changed to Class, the connector prefix remains scheduleoffering.*.
This Connector
Uses This Prefix in CONNECTORS sys­
tem properties
Alternate Job Code
Connector
alternatejobposition.*
Curriculum Connector
curriculum.*
Job Code Connector
jobposition.*
Organization Owner
Connector
organizationowner.*
Position Connector
position.*
Registration Connector
enrollment.*
Class Connector
scheduleoffering.*
User Connector
user.*
Notes
New customers should be using User Connector - SF
only.
User Connector - Federal federaluser.*
New customers should be using User Connector - SF
only.
User Connector - SF
sfuser.*
New customers should be using User Connector - SF
only.
Importing User Data from Platform with User Connector - SF
Troubleshooting Connectors
CONFIDENTIAL
65
This Connector
User Compensation
Connector
Uses This Prefix in CONNECTORS sys­
tem properties
Notes
usercompensation.*
New customer should not see this configuration. Older
customers might: it applies to legacy Plateau Compen­
sation. Please ignore it.
User Compensation
History Connector
usercomphistory.*
New customer should not see this configuration. Older
customers might: it applies to legacy Plateau Compen­
sation. Please ignore it.
7.2
Connector Log Clean-Up
This is how SAP SuccessFactors Learning cleans up connector logs and how you can retain your own copy for
longer.
The connector log clean-up is an automatic process that removes connector logs that are older than 30 days or
older than 5 job runs, whichever policy retains the logs longer. Connector logs are viewable by administrators with
View Errors and View Results in
System Administration
Connectors
[individual connector] .
The logs are also available by email and FTP site, so if you need to store connectors beyond the limits set in the
connector log clean-up job, we recommend that keep the FTP logs or emailed error detail report. To enable the FTP
logs and email report, go to
settings:
System Administration
Configuration
System Configuration
and check these
● connector.ftp.output.report.enable should be set to true to send the report to the configured FTP site
● connector.report.email.enable should be set to true to send the report to the configured email accounts
The settings associated with the FTP report and emailed report are grouped with the enable settings. We
recommend that you check the associated settings and update them if your policy or process has changed.
7.3
Export Cautions for User Connector - SF
When you configure the user export job in provisioning for User Connector - SF beware of some common issues.
Server Access and File Matching
For each job you create, set the Server Access and File Access to match the locations that User Connector - SF
expects. You set the FTP and file path properties in the CONNECTORS system properties file and the file name for
the User Connector - SF is user_data_<Suffix>.txt where <Suffix> is your SAP SuccessFactors Learning tenant ID.
The suffix is optional but we recommend you use it.
66
CONFIDENTIAL
Importing User Data from Platform with User Connector - SF
Troubleshooting Connectors
 Note
In some uncommon cases, customers set a different suffix in
System Admin
Configuration
System
Configuration CONNECTORS . If you have set a different suffix, you can find it in the
connector.input.file.name.tenant.suffix.override property. In order to use a suffix, the first
property should be set to true and the second should contain the suffix name.
Date Format Mismatching
When you export the files in provisioning, you have a choice of date format. You must match the date format to the
format you set in CONNECTORS.
Scheduling
Schedule your job to run and complete before the User Connector - SF Automatic Process Manager (APM) runs on
the SAP SuccessFactors Learning side. That is, if you set the APM to run at 4 AM, schedule your job to finish by
3:30 AM so that the file exists on the FTP site when the APM runs the connector job. You set the User Connector SF APM in the learning administrator environment,
7.4
System Admin
Connectors
User Connector - SF .
Termination Date Processing for User Connector - SF
User Connector - SF handles termination date through a set of processing rules.
● Termination dates can’t be in the future. If you pass a user in User Connector - SF, and the user's termination
date is after the system date when the connector runs, then the connector rejects the user.
● Termination dates can’t be before hire dates. If you pass a user in User Connector - SF and you make the users'
termination date before the users' hire date, the connector rejects the user.
● You can’t have termination dates for active users. If the NOTACTIVE value is set to N (the user is active), then
the termination date is nullified by the connector. The user remains active and does not get a termination date.
In platform, verify that inactivation is part of your termination process.
● You can easily reverse mistakes in termination date. A null value for terminated date always overwrites the
existing value.
Importing User Data from Platform with User Connector - SF
Troubleshooting Connectors
CONFIDENTIAL
67
7.4.1 Verifying that User Connector - SF Allows Rehires
Verify that User Connector - SF allows rehires so that you can rehire an employee who has left the organization. If
you do not configure it to allow rehires, your learning assignments are likely to fail the second time you hire the
employee.
Context
In the core file for User Connector - SF, platform includes a column called EXIT_DATE. Map it to TERM_DTE has
logic that expects the mapping. When EXIT_DATE passed a value to TERM_DTE in an earlier run but then the user
appears in a later connector run with a null value for with a null value for EXIT_DATE, TERM_DTE nullifies. The user
appears in Learning as rehired.
 Caution
If you map TERM_DTE to another field, TERM_DTE still nullifies when that other field passes a null value, but you
probably do not get the expected result in Learning. We built the nullify logic expecting TERM_DTE to be
mapped to EXIT_DATE.
Procedure
1. Go to SAP SuccessFactors Learning Administration and then go to
Configuration
System Admin
Configuration
System
and then edit CONNECTORS.
2. Verify that you have set sfuser.field.mapping.data.TERM_DTE to EXIT_DATE.
 Sample Code
sfuser.field.mapping.data.TERM_DTE=EXIT_DATE
7.5
Manager Processing for User Connector - SF
User Connector - SF handles manager assignment through a set of processing rules that differ from other user
connectors (third party and Federal).
The manager processing logic works when you map SUPER to MANAGER and STUD_ID to USERID. You map them in
System Administration
Configuration
System Configuration
CONNECTORS .
 Sample Code
sfuser.field.mapping.data.SUPER=MANAGER
68
CONFIDENTIAL
Importing User Data from Platform with User Connector - SF
Troubleshooting Connectors
sfuser.field.mapping.data.STUD_ID=USERID
We protect you from assigning users to managers who do not exist or creating incorrect relationships. Users'
managers, as defined in MANAGER, must be either:
● A user that already exists SAP SuccessFactors Learning.
● A user that you are adding in the current run of User Connector - SF.
If the manager does not exist and you don't add the manager in the same connector run as you make the
assignment, the manager is nullified but the user is added (without a manager). Additionally, the connector nullifies
the manager assignment if any of these occur:
● The manager assignment creates a circular reference. Users cannot be their own manager’s manager. For
example Mary can supervise Mark, but then Mark cannot also supervise Mary.
● Users cannot supervise themselves. We nullify if the manager ID (from MANAGER) matches the user ID (from
USERID) in the same row.
● The manager has a termination date.
7.6
Alternate Manager Processing Logic for User Connector SF
User Connector - SF logs errors and prevents mistakes when you attempt to add alternate managers in a way that
can adversely affect your system.
Avoid Direct Alternate Manager Mapping
In the configuration for User Connector - SF, ignore all mapping fields that begin with
sfuser.field.mapping.data.ALT_SUPER or sfuser.field.mapping.data.REMOVE_ALT_SUPER. They are
for infrequent cases: when customers build a custom way of storing matrix managers and other users who are
alternate managers. They come with their own complex logic. Almost all customers can use standard configuration
for the business result they want: Human Resource Business Partners (HRBP) and matrix managers helping
managers manage their learning. Standard configuration is:
 Sample Code
sfuser.field.mapping.data.TEMP_ALT_SUPER=MATRIX_MANAGER
sfuser.field.mapping.data.HRBP=HR
Alternate Manager Relationships
SAP SuccessFactors Learning protects you from assigning users to alternate managers who don’t exist or creating
incorrect relationships. User Connector - SF doesn't make the alternate manager relationship if:
Importing User Data from Platform with User Connector - SF
Troubleshooting Connectors
CONFIDENTIAL
69
● The alternate manager ID that you pass in the connector file is missing from the Learning database
● The user is missing a primary manager.
● The alternate manager assignment creates a circular reference. Users can’t be their own manager’s manager
(or alternate). For example Mary can supervise Mark, but then Mark can’t also supervise Mary.
● Users can’t supervise themselves. We reject if the alternate manager ID matches the user ID (from USERID) in
the same row.
Alternate Manager Removal
If you pass a null value for any alternate manager field, User Connector - SF doesn’t remove any alternate manager
from the user’s record. The connector removes specific alternate managers using the REMOVE_* fields.
For example, you add an alternate manager by passing the alternate manager's ID in the ALT_SUPER1 column of
the data file. It could be that the user is doing some work for another team and the other team's manager becomes
the user's matrix manager. In Learning terms, the matrix manager is an alternate manager. Later, if the user leaves
the other team and therefore loses the matrix manager, you can’t pass null in ALT_SUPER1 to remove the
relationship. Instead, you must pass the matrix manager's ID again, but in the REMOVE_ALT_SUPER1 column.
7.7
Manager, Matrix Manager, HRBP, and Alternate Manager
Mapping in User Connector - SF
Most customers follow a standard mapping for users' managers: their manager, matrix manager, and Human
Resources Business Manager (HRBP).
In most of Human Experience Management (HXM), you use employees' manager, matrix manager, and HRBP. In
Learning, we understand the matrix manager and HRBP as alternate managers. The mapping can be confusing, but
most customers can follow a standard mapping.
Standard Mapping of Manager to Primary Learning Manager
A Learning manager in Human Experience Management (HXM) Learning is primarily responsible for the learning of
their direct reports, including:
● Approving registration or withdrawal from courses. Not all customers configure registration approval
processes, but among the customers who do configure them, many configure the manager as an approver.
When primary managers change, you can reroute their approvals: associate the new manager with the users'
past, current, and future approvals.
● Managing training for their direct reports. Managers see My Team, where they can, for example, enroll their
direct reports into courses on their behalf.
● Completing third level surveys to show that their direct reports apply what they learned in their courses. Not all
customers use third level surveys, but among those who do, managers are often asked to complete the
surveys.
70
CONFIDENTIAL
Importing User Data from Platform with User Connector - SF
Troubleshooting Connectors
Many customers also empower Human Resources Business Managers (HRBP) and matrix managers to do similar
things. In Learning, these types of managers are called alternate managers. You empower managers through My
Team permissions:
System Administration
Security
Role Management
Permissions .
Map SUPER to MANAGER to pull users' standard managers into their standard manager. In
Configuration
System Configuration
System Admin
CONNECTORS , set:
 Sample Code
sfuser.field.mapping.data.SUPER=MANAGER
Standard Mapping of Matrix Manager to Alternate Learning Supervisor
When users report to an alternative manager for an extended period of time, you can transfer some responsibility
to the alternate manager. Alternate managers are often used in dotted line relationships: matrix managers. A
common example is when employees work on a project where they report to a project manager for the time of the
project but their primary manager remains their manager in the Manager field.
Map TEMP_ALT_SUPER to MATRIX_MANAGER to pull users' matrix managers into an alternate manager. In
System Admin
Configuration
System Configuration
CONNECTORS , set:
 Sample Code
sfuser.field.mapping.data.TEMP_ALT_SUPER=MATRIX_MANAGER
Standard Mapping of HRBP to Alternate Learning Supervisor
In organizations that have Human Resources Business Partners (HRBP), you can create a structure that includes
an HRBP. The HRBP is an alternative manager in Learning: the HRBP shares the responsibility with managers as an
alternate. But the HRBP is categorized differently so that the relationship can be more clearly understood.
Map HRBP to the data object that contains your HRBP user to add HRBP users as alternate managers. In
Admin
Configuration
System Configuration
System
CONNECTORS , set:
 Sample Code
sfuser.field.mapping.data.HRBP=<the data object for your HRBP user>
All other Alternate Learning Supervisors
Map all other alternate managers with sfuser.field.mapping.data.ALT_SUPER*. You can add up to three
additional alternate managers.
Importing User Data from Platform with User Connector - SF
Troubleshooting Connectors
CONFIDENTIAL
71
7.8
Default Process Rules for Activating and Inactivating
learners with User Connector - SF
Most customers use the default User Connector - SF rules for activating and inactivating learners.
When STATUS Contains...
The Result for User Connector - SF is...
ACTIVE or active
The learner is added as active or updates from inactive to ac­
tive and the learner is given a shopping account type as inter­
nal.
ACTIVE_EXTERNAL or active_external
The learner is added as active or updates from inactive to ac­
tive and the learner is given a shopping account type as exter­
nal. External learners are part of your extended enterprise and
so they get external shopping accounts.
INACTIVE or inactive
The learner is added as inactive or updates from active to inac­
tive and the learner is given a shopping account type as inter­
nal.
INACTIVE_EXTERNAL or inactive_external
The learner is added as inactive or updates from active to inac­
tive and the learner is given a shopping account type as exter­
nal. External learners are part of your extended enterprise and
so they get external shopping accounts.
Any other value
The connector rejects the record so that you can check the
logs for inconsistencies.
Results of Inactivating Users in SAP SuccessFactors Learning [page 73]
Deactivate users in SAP SuccessFactors platform and allow User Connector - SF to update the status. Do
not update the active status directly in Learning because the two could get out of sync.
Changing Default Active Behavior in User Connector - SF [page 74]
Change the active mapping for User Connector - SF if you customized how users are marked as active or
inactive in platform.
Enforcing Consistency for Learner Inactivation by Learning Connectors [page 76]
Enforce consistency for learner inactivation by connectors so that the user inactivation process in
connectors follows the same inactivation process as the SAP SuccessFactors Learning Administration
interface.
Remapping Shopping Accounts to Status for User Connector - SF [page 77]
Remap the shopping account status for User Connector - SF if you changed how set active and inactive
users in platform and changed how that maps to Learning (this is rare ).
72
CONFIDENTIAL
Importing User Data from Platform with User Connector - SF
Troubleshooting Connectors
7.8.1 Results of Inactivating Users in SAP SuccessFactors
Learning
Deactivate users in SAP SuccessFactors platform and allow User Connector - SF to update the status. Do not
update the active status directly in Learning because the two could get out of sync.
User Connector - SF inactivates users when STATUS in platform is an inactive status and the connector runs. When
the connector inactivates users, SAP SuccessFactors:
 Note
In rare occasions, some customers change this behavior through a setting.
● Removes the user being inactivated from current and future enrollments
● Removes any item requests that exist for the user being inactivated
● Removes the inactive user from any classes
● Inactivates the related instructor record of the user who is inactivated
● Locks the related administrator for the user who is inactivated
● Removes the inactive user as a contact from classes
● Resets (clears) online items started by the user who is inactivated
 Note
When you inactivate a manager, SAP SuccessFactors does not inactivate users who are direct reports of the
manager.
Parent topic: Default Process Rules for Activating and Inactivating learners with User Connector - SF [page 72]
Related Information
Changing Default Active Behavior in User Connector - SF [page 74]
Enforcing Consistency for Learner Inactivation by Learning Connectors [page 76]
Remapping Shopping Accounts to Status for User Connector - SF [page 77]
Importing User Data from Platform with User Connector - SF
Troubleshooting Connectors
CONFIDENTIAL
73
7.8.2 Changing Default Active Behavior in User Connector - SF
Change the active mapping for User Connector - SF if you customized how users are marked as active or inactive in
platform.
Context
Most customers can skip this task because they do not change how platform marks users as active or inactive.
Change the default active behavior only if you altered how you mark users as active or inactive in platform. That
kind of change is rare.
The default configuration is:
 Sample Code
sfuser.field.transform.data.NOTACTIVE.N=active,active_external,ACTIVE,ACTIVE_EXTE
RNAL
sfuser.field.transform.data.NOTACTIVE.Y=inactive,inactive_external,INACTIVE,INACT
IVE_EXTERNAL
sfuser.field.transform.rule.actionOnInvalid.NOTACTIVE=reject
 Tip
NOTACTIVE can be confusing because it’s framed in the negative. When NOTACTIVE is set to N, then the user is
active.
 Caution
Do not change sfuser.field.transform.rule.actionOnInvalid.NOTACTIVE. You want the connector
to reject unexpected values so that you can see errors and troubleshoot them. If you change its value, you make
troubleshooting harder.
Procedure
1. Go to SAP SuccessFactors Learning Administration, go to
System Administration
Configuration
System
Configuration , and then edit CONNECTORS.
2. Find sfuser.field.transform.data.NOTACTIVE.N and set it to the possible values that User Connector SF could receive in STATUS for active users.
 Note
We assume that you’ve followed the default mapping:
 Sample Code
sfuser.field.mapping.data.NOTACTIVE=STATUS
74
CONFIDENTIAL
Importing User Data from Platform with User Connector - SF
Troubleshooting Connectors
For example, if you customized platform to store ACT for active users in STATUS, then you configure it as
follows:
 Sample Code
sfuser.field.transform.data.NOTACTIVE.N=active,active_external,ACTIVE,ACTIVE_E
XTERNAL,ACT
3. Find sfuser.field.transform.data.NOTACTIVE.Y and set it to the possible values that User Connector SF could receive in STATUS for active users.
 Note
We assume that you’ve followed the default mapping:
 Sample Code
sfuser.field.mapping.data.NOTACTIVE=STATUS
For example, if you customized platform to store NO_ACT for inactive users in STATUS, then you configure it as
follows:
 Sample Code
sfuser.field.transform.data.NOTACTIVE.Y=inactive,inactive_external,INACTIVE,IN
ACTIVE_EXTERNAL,NO_ACT
4. Click Apply Changes.
Next Steps
If you changed how you record active and inactive in platform, and therefore changed the active and inactive
mapping for User Connector - SF, you must also change the shopping cart mapping.
Task overview: Default Process Rules for Activating and Inactivating learners with User Connector - SF [page 72]
Related Information
Results of Inactivating Users in SAP SuccessFactors Learning [page 73]
Enforcing Consistency for Learner Inactivation by Learning Connectors [page 76]
Remapping Shopping Accounts to Status for User Connector - SF [page 77]
Importing User Data from Platform with User Connector - SF
Troubleshooting Connectors
CONFIDENTIAL
75
7.8.3 Enforcing Consistency for Learner Inactivation by
Learning Connectors
Enforce consistency for learner inactivation by connectors so that the user inactivation process in connectors
follows the same inactivation process as the SAP SuccessFactors Learning Administration interface.
Context
When you inactivate learners through any connector, you should set the connector to behave as if a learning
administrator inactivated the user in SAP SuccessFactors Learning Administration: it removes all learning items
from the users' learning plans. Consistent behavior between the connector and SAP SuccessFactors Learning
Administration creates predictable behavior and less troubleshooting.
Procedure
1. Go to SAP SuccessFactors Learning Administration and then go to
System Configuration
System Administration
Configuration
CONNECTORS .
2. Find one of the following, depending on which type of user connector you are using.
○ Find sfuser.connector.inactiveRule.cleanDevPlan if you are using the standard User Connector
- SF to draw user attributes from platform. This is most common.
○ Find user.connector.inactiveRule.cleanDevPlan if you are using the third-party user connector.
○ Find federaluser.connector.inactiveRule.cleanDevPlan if you are using the United States
Federal user connector.
3. If you find the setting, set it to Y.
 Caution
When set to N (the incorrect setting for almost all use cases), then the connector maintains the users'
learning plans even if the user is inactive. SAP SuccessFactors Learning Administration behave differently
than connectors. It is very rare to need a setting of N.
4. If you do not find the setting, then SAP SuccessFactors Learning it is effectively set to Y so you do not need to
take action.
5. Click Apply Changes.
Task overview: Default Process Rules for Activating and Inactivating learners with User Connector - SF [page 72]
Related Information
Results of Inactivating Users in SAP SuccessFactors Learning [page 73]
76
CONFIDENTIAL
Importing User Data from Platform with User Connector - SF
Troubleshooting Connectors
Changing Default Active Behavior in User Connector - SF [page 74]
Remapping Shopping Accounts to Status for User Connector - SF [page 77]
7.8.4 Remapping Shopping Accounts to Status for User
Connector - SF
Remap the shopping account status for User Connector - SF if you changed how set active and inactive users in
platform and changed how that maps to Learning (this is rare ).
Prerequisites
Shopping cart remapping and active inactive remapping are related. You change shopping account mapping only if
you change active and inactive mapping, which is rare.
Context
Most customers can skip this task because they do not change how platform marks users as active or inactive.
Change the default active behavior only if you alter how you mark users as active or inactive in platform. When you
alter how you mark users as active or inactive in platform, it has a downstream effect on shopping account status.
Changes to the active mapping and the shopping cart are rare. The default configuration is:
 Sample Code
sfuser.field.transform.data.SHOPPING_ACCT_TYPE.INTERNAL=active,ACTIVE,inactive,IN
ACTIVE
sfuser.field.transform.data.SHOPPING_ACCT_TYPE.EXTERNAL=active_external,ACTIVE_EX
TERNAL,inactive_external,INACTIVE_EXTERNAL
When User Connector - SF adds or updates users, it imports them as active or inactive from STATUS (by default).
The status from platform also tells User Connector - SF if the user is internal or external. External users have, by
default, the suffix _external. Therefore, by default, any user with a status that ends in _external gets an
external shopping account type.
Procedure
1. Go to SAP SuccessFactors Learning Administration, and go to
System Configuration
System Administration
Configuration
and then edit CONNECTORS.
2. Find sfuser.field.transform.data.SHOPPING_ACCT_TYPE.INTERNAL and set it to the possible values
that User Connector - SF could receive in STATUS for internal users.
Importing User Data from Platform with User Connector - SF
Troubleshooting Connectors
CONFIDENTIAL
77
 Note
We assume that you’ve followed the default mapping:
 Sample Code
sfuser.field.mapping.data.NOTACTIVE=STATUS
For example, if you customized platform to store ACT for active, internal users in STATUS, then you configure it
as follows:
 Sample Code
sfuser.field.transform.data.SHOPPING_ACCT_TYPE.INTERNAL=active,active_external
,ACTIVE,ACTIVE_EXTERNAL,ACT
3. Find sfuser.field.transform.data.SHOPPING_ACCT_TYPE.EXTERNAL and set it to the possible values
that User Connector - SF could receive in STATUS for external users.
 Note
We assume that you’ve followed the default status mapping:
 Sample Code
sfuser.field.mapping.data.NOTACTIVE=STATUS
For example, if you customize platform to store ACT_EXT for active, external users in STATUS, then you
configure it as follows:
 Sample Code
sfuser.field.transform.data.NOTACTIVE.Y=inactive,inactive_external,INACTIVE,IN
ACTIVE_EXTERNAL,ACT_EXT
4. Click Apply Changes.
Task overview: Default Process Rules for Activating and Inactivating learners with User Connector - SF [page 72]
Related Information
Results of Inactivating Users in SAP SuccessFactors Learning [page 73]
Changing Default Active Behavior in User Connector - SF [page 74]
Enforcing Consistency for Learner Inactivation by Learning Connectors [page 76]
78
CONFIDENTIAL
Importing User Data from Platform with User Connector - SF
Troubleshooting Connectors
7.9
How User Connector - SF Processes Custom Data
When you import custom data with User Connector - SF, the connector automatically generates the matching
custom columns and referenced values.
When User Connector - SF encounters a custom field from platform that is not in Learning, it adds the custom field
(custom column in Learning terms) and then adds new values that you pass to the list of referenced values.
Specifically:
● User Connector - SF gives them a number in the COL_NUM column in PA_STUDENT_USER.
● User Connector - SF adds the new value in the USER_VALUE table.
For example, if you use the default mapping for CUSTOM01
(sfuser.field.mapping.data.COL_NUM1_VAL=CUSTOM01), and if a users' value for in CUSTOM01 is ABC, the
value written to COL_NUM is 1 (the first column) and the value written to USER_VALUE on the same row is ABC.
7.10
Time Zone Processing for User Connector - SF
Users time zones need to be processed from platform to Learning because Learning stores time zones differently
than they are stored in platform.
 Caution
Keep the default settings for User Connector - SF because they are the same that the user update event bus
uses. If a user is updated through User Connector - SF and through the event bus, their mapping should be the
same.
When TIMEZONE Contains...
The Result for User Connector - SF is...
EST
The user is added to America/New_York
AST
The user is added to America/Anchorage
CST
The user is added to America/Chicago
MST
The user is added to America/Denver
PST
The user is added to America/Los_Angeles
Time zones in platform can include three letter time zones (for example EST and PST). SAP SuccessFactors
Learning accepts only locale-based time zones like America/New_York or America/Los_Angeles. Therefore, User
Connector - SF has a map that converts three letter time zones to locale time zones.
sfuser.field.transform.data.TIMEZONE.America/New_York=EST
sfuser.field.transform.data.TIMEZONE.America/Anchorage=AST
sfuser.field.transform.data.TIMEZONE.America/Chicago=CST
sfuser.field.transform.data.TIMEZONE.America/Denver=MST
sfuser.field.transform.data.TIMEZONE.America/Los_Angeles=PST
Importing User Data from Platform with User Connector - SF
Troubleshooting Connectors
CONFIDENTIAL
79
7.11
Reference Values Processing in User Connector - SF
In most cases, connectors reject records that have a referenced value that does not already exist.
In this user connector's fields default map, you see a column that flags referenced fields. In most cases, if a field is
referenced, and if you do not provide a reference value that the system can find, the connector rejects the record.
For example, if you have not added a US Dollar (USD) currency in the referenced values, and you try to add a user
with the currency of USD, the system rejects the user record.
7.12
Full Time Mapping for User Connector - SF
Do not change the full time mapping for User Connector - SF.
In SAP SuccessFactors Learning, the user attribute Is Full Time is a legacy attribute. It was added to support
Plateau Compensation, a product that we no longer support. Instead of using Is Full Time to indicate that someone
is a full time user, please use Employee Type instead. Employee Type is a more accurate and more powerful way to
categorize your employees because you can, for example, add employee types of Full Time Contractor and Full
Time Employee: both work a full week but one is an internal employee and the other is a contractor. When you
assign learning, therefore, you can more accurately target the assignment with (for example) full time users who
are internal, full time users who are contractors, or both.
Because Is Full Time is a legacy field in Learning, it is not often used to assign learning, so most customers do not
map it in User Connector - SF. If you use it, however, do not change its value mapping.
 Sample Code
sfuser.extendeduser.field.transform.data.FULLTIME.N=FALSE,false,False,F,N,
0,NO,No,f,n,no
sfuser.extendeduser.field.transform.data.FULLTIME.Y=TRUE,true,True,T,Y,
1,YES,Yes,t,y,yes
7.13
Update on Null for User Connector - SF
Although other connectors use an update on null function, it is not common in User Connector - SF because we
control both the input file from platform and the connector that imports the data to Learning.
Almost all customers can ignore updateOnNull for User Connector - SF because we built the connector with
special settings that help you more easily nullify fields. For example, User Connector - SF uses
sfuser.field.transform.data.SUPER.@NULLIFY@=NO_MANAGER as a special case because SAP
SuccessFactors controls both the export from platform and the import to Learning. We know that when there is no
manager assigned to a customer, the feed includes the value NO_MANAGER, so we nullify it automatically.
All connectors have a property for nullifying values. For User Connector - SF, only certified partners or services
should use it and they should use it to correct data that has previously been loaded - not for another purpose.
80
CONFIDENTIAL
Importing User Data from Platform with User Connector - SF
Troubleshooting Connectors
 Caution
The updateOnNull setting should be used only by Learning certified partners or SAP SuccessFactors services
for data correction. Mistakes adversely affect the data in your system and it can be expensive to correct. Please
ask your Learning certified partner to submit a test plan and to thoroughly test the data correction in a preview
or stage environment before the updateOnNull runs in User Connector - SF with production data. Please also
ask for a plan to end usage of updateOnNull after the data has been corrected.
7.14
Verifying Hire Date Transformation for User Connector SF
Verify hire date transformation for User Connector - SF as the default format from platform format so that the
connector translates the date from platform to Learning.
Context
Very few customers need to change the default hire date transformation. You only need to change it if you
customized the date storage format in platform or in Learning.
 Note
You can also change the date display format, but the display format does not affect the storage format. For
example, dates can display month­first to some locales and day­first to other locales, but the storage format
remains the same.
Procedure
1. Go to SAP SuccessFactors Learning Administration and then go to
Configuration
System Admin
Configuration
System
and then edit CONNECTORS.
2. Find sfuser.field.transform.date.format.HIRE_DTE.
3. Verify that it is the default setting.
 Sample Code
sfuser.field.transform.date.format.HIRE_DTE=MMM-dd-yyyy\ HH\:mm\:ss=MM/dd/yyyy
 Note
If you changed the date format in platform, change the value of
sfuser.field.transform.date.format.HIRE_DTE. But a custom date format is so rare that almost
all customers should simply verify that they have the default setting.
Importing User Data from Platform with User Connector - SF
Troubleshooting Connectors
CONFIDENTIAL
81
4. Click Apply Changes.
Related Information
Scheduling Weekly Employee Export Job Type for User Connector - SF [page 51]
Scheduling Daily Delta Employees Export Job Type for User Connector - SF [page 53]
Scheduling Weekly Live Profile Export Job Type for User Connector - SF [page 55]
82
CONFIDENTIAL
Importing User Data from Platform with User Connector - SF
Troubleshooting Connectors
Important Disclaimers and Legal Information
Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:
●
●
Links with the icon
with SAP) to this:
: You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements
●
The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
●
SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
Links with the icon
: You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such links, you
agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.
Videos Hosted on External Platforms
Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any
advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within the
control or responsibility of SAP.
Beta and Other Experimental Features
Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by SAP at
any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the
experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback
(e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.
Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and
phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example
code unless damages have been caused by SAP's gross negligence or willful misconduct.
Gender-Related Language
We try not to use gender­specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.
Importing User Data from Platform with User Connector - SF
Important Disclaimers and Legal Information
CONFIDENTIAL
83
www.sap.com/contactsap
© 2021 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form
or for any purpose without the express permission of SAP SE or an SAP
affiliate company. The information contained herein may be changed
without prior notice.
Some software products marketed by SAP SE and its distributors
contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for
informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP affiliate company products and services are those that are set forth
in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an
additional warranty.
SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.
Please see https://www.sap.com/about/legal/trademark.html for
additional trademark information and notices.
THE BEST RUN