Importing Learners With The User Connector: Confidential Document Version: 2H 2020 - 2020-10-09

CONFIDENTIAL
Document Version: 2H 2020 – 2020-10-09
Importing Learners with the User Connector

© 2020 SAP SE or an SAP affiliate company. All rights reserved.
THE BEST RUN

Content
1 Engage Certified Partner to Import Data to SAP SuccessFactors Learning . . . . . . . . . . . . . . . . . . . 4
2 About User Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2.1 User Connector Header Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.2 User HRBP and Alternate Manager Data Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.3 Adding Additional Custom Columns in User Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
2.4 Running Multiple Data Files with User Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.5 General Processing Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Active and Inactive Processing for User Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Verifying that User Connector - SF Allows Rehires. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Alternate Manager Processing Logic for User Connector - SF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
New User Notification Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Reference Values Processing in User Connector - SF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

2 CONFIDENTIAL Content
What's New for User Connector
Read what's new for the User Connector guide.
Q3 2016 - Present
The following table summarizes changes to this guide for recent releases.
What's New Description More Info
Initial Publication in Q3 2016 The User Connector guide is for imple

menting the User Connector with SAP
SuccessFactors Learning

What's New for User Connector CONFIDENTIAL 3
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 may 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 may 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.

4 CONFIDENTIAL Engage Certified Partner to Import Data to SAP SuccessFactors Learning
2 About User Connector
Read about using connectors to sync users in an SAP SuccessFactors integrated environment.
The user connector (User Connector) imports user data through a connector. It is the standard user connector.
The system has two other user connectors: Federal and SF (for Federal customers and integrated customers).
2.1 User Connector Header Mapping
View the default map for User Connector data file between the header column and its data, along with notes, rules,
and other information.
When you create your data file, it must be named as follows, where <Suffix> is your tenant ID. In some uncommon
cases, customers set a different suffix in System Administration 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.
Data file name: user_data_<Suffix>.txt
 Note
The "LMS Database Column Name" is provided for readers who are familiar with user configuration in SAP
SuccessFactors Learning. For example, if you are familiar with other user connectors, you might recognize
"NOTACTIVE" as the active flag in the SAP SuccessFactors Learning tables.
LMS Character
LMS Database Column Name Description and Rules LMS Data Type Length in Bytes
NOTACTIVE Required to be present in the input file. De Alpha Numeric Y or N only (Boo
faults to N if null or invalid. lean)
N = Make active
Y = Make inactive
See Active and Inactive Processing for User

Connector [page 17] for more information.
STUD_ID Required to be present in the input file. The Alpha Numeric 90

unique user ID. If the ID does not exist in the
system, the system creates a new user re
cord.
FNAME The given name of the user. Alpha Numeric 150

About User Connector CONFIDENTIAL 5
LMS Character
LNAME The family name of the user. Alpha Numeric 150
MI Alpha Numeric 90
GENDER The value of this field must be M for Male or F Alpha Numeric 1
for Female.
EXTERNAL_ID This is a unique identifier of a person. It will Alpha Numeric 90

eventually be used as the display identifier of
a user record in the LMS.
JP_ID If the provided Job Code ID does not exist in Alpha Numeric 150
LMS DB, it will be created automatically.
This field is referenced in the database.
JP_DESC Only used if provided Job Position ID in same Alpha Numeric 300
row does not exist in LMS DB and is created
automatically. If Job Position ID already ex
ists in LMS DB, provided Job Position De
scription will not overwrite or nullify existing
value.
JOB_TITLE Job Title is not directly associated with Job Alpha Numeric 300
Position ID in LMS DB.
Job Title is not directly associated with Job

Code ID in LMS DB
ROLE_ID For new User records: for an invalid or no role Alpha Numeric
then the connector defaults to the value in
the configuration file. If a role is invalid or not
supplied, the existing role is retained.
JL_ID If provided Job Location ID does not exist in Alpha Numeric 90

LMS DB, it will be created automatically.
JL_DESC Only used if provided Job Location ID in same Alpha Numeric 120
automatically. If Job Location ID already ex
ists in LMS DB, provided Job Location De
scription will not overwrite or nullify existing
value.

6 CONFIDENTIAL About User Connector
LMS Character
DMN_ID If provided Domain ID does not exist in LMS Alpha Numeric 90

DB, it will be created automatically. The Con
nector will not create or update parent rela
tionships, or update existing Domain records.
If null, defaults to Default User Domain.
DMN_DESC Only used if provided Domain ID in same row Alpha Numeric 300
does not exist in LMS DB and is created auto
matically. If Domain ID already exists in LMS
DB, provided Domain Description will not
overwrite or nullify existing value.
ORG_ID If provided Organization ID does not exist in Alpha Numeric 90

LMS DB, it will be created automatically. The
Connector will not create or update parent
relationships, or update existing Org records.
ORG_DESC Only used if provided Organization ID in same Alpha Numeric 300

automatically. If Org ID already exists in LMS
DB, provided Org Description will not over
write or nullify existing value.
EMP_TYP_ID If provided Employee Type ID does not exist Alpha Numeric 90

in LMS DB, it will be created automatically.
EMP_TYP_DESC Only used if provided Employee Type ID in Alpha Numeric 120

same row does not exist in LMS DB and is
created automatically.
EMP_STAT_ID If provided Employee Status ID does not exist Alpha Numeric 90

in LMS DB, it will be created automatically.
EMP_STAT_DESC Only used if provided Employee Status ID in Alpha Numeric 120

created automatically. If Employee Status ID
already exists in LMS DB, provided Employee
Status Description will not overwrite or nullify
existing value.
ADDR Address. Alpha Numeric 600
CITY City. Alpha Numeric 300
STATE State. Alpha Numeric 150

LMS Character
POSTAL Postal Code. Alpha Numeric 150
CNTRY The connector rejects the record if the Alpha Numeric

Country value is not valid.
REGION_ID The following are valid region ID values: Alpha Numeric
This field is referenced in the database. The connector rejects the record if the Region
ID is not valid.
EMAIL_ADDR If the customer uses email validation in the Alpha Numeric 384
system, please take the validation rules into
consideration when preparing and sending
user data. The LMS email validation settings
will not be applied during Connector run.
HIRE_DTE If Hired Date is later than the system date Date & Time
when the connector runs, record will be re
jected (Hired Date cannot be in the future).
Format the datetime as MON-DD-YYYY

HH24:MI:SS
The connector can accept futrue hire dates if

allowFutureHireDates is set to true in
LMS_ADMIN. The user status is set in the
NOTACTIVE value in the data file.
TERM_DTE If Terminated Date is later than the system Date & Time
date when the connector runs, or if Termi
nated Date is earlier than the Hired Date in
the input file the record will be rejected (Ter
minated Date cannot be in the future and
cannot be an earlier date than the Hired
Date).
If the Notactive value is set to N then the ter

mination date is nullified by the connector.
A NULL value for this field always overwrites

this field’s existing value.
Format the datetime as: MON-DD-YYYY

HH24:MI:SS

LMS Character
SUPER This needs to reference to an existing user ID Alpha Numeric

(or one that will be added in the current input
file as defined in the User ID column #2.
The value provided will be nullified if:
● It creates a circular reference (User can

not be their own supervisor’s supervi
sor)
● If the supervisor matches the User ID in
the same row.
● The supervisor (user) does not already
exist in the LMS.
● The supervisor (user) has a Terminated
Date.
RESUME_LOCN Alpha Numeric 600
COMMENTS Admin facing free form text. Alpha Numeric 2000
ACCT_ID If provided Account Code does not exist in Alpha Numeric 90

LMS DB, it will be created automatically as a
record in the user’s domain.
PHON_NUM1 This is a phone number for the user. Alpha Numeric 120
PHON_NUM1_DESC This value is required if Phone Number 1 is Alpha Numeric 300

provided.

provided.

provided.
COL_NUM1_VAL This is a custom column value. By default, Alpha Numeric 120

the user connector is set up for fifteen cus
tom columns, numbered 10-150 counting by
10. You can add additional custom columns
through the CONNECTORS configuration.

LMS Character









LMS Character







LMS Character
TIMEZONE Default Time Zone preference for the user. Alpha Numeric
Connector will update or not update this
value based upon the configuration file set
ting.
The connector rejects the record if the Time

Zone value is not valid.
Make sure you are using a time zone that is

being displayed by the LMS. If necessary, use
the user.field.transform.data.TIMEZONE
property to map the incoming time zone to
an LMS time zone.
LOCALE Default Locale preference for the user. The Alpha Numeric
locale preference sets the date/number for
mat preferences.
CAN_USE_ORG_ACT This allows user’s to access the account co Alpha Numeric Y or N (Boolean)
des available to their linked organization ID
for chargebacks.
CURRENCY_CODE Default Currency Preference for the user. Alpha Numeric

Connector will not update Currency for exist
ing records as the user may modify the pref
erence via the UI.
If null defaults to configuration value. If the

value is invalid then the record is rejected.
ACCT_DESC Only used if the provided Account Code ID in Alpha Numeric 120
same record will be created by the connector.
If Account Code ID already exists in LMS DB,
provided Account Code Description will not
overwrite or nullify the existing value.
JP_EFF_DTE If Job Position Change Date is later than the Date & Time
system date when the connector runs, record
is rejected. The Job Position Change Effective
Date cannot be in the future.
Format the datetime as: MON-DD-YYYY

HH24:MI:SS

LMS Character
MAPPED_ADMIN_ID Provides mapping between User ID and Ad Alpha Numeric

min ID so that this user sees both the Home
and Admin tabs.
Must be a valid Admin ID. If this value does

not map to an administrator ID then the re
cord is rejected.
MAPPED_INST_ID Must be a valid Instructor ID. If this value Alpha Numeric

does not map to an instructor ID then the re
cord is rejected. Provides mapping between
User ID and Instructor ID.
ALT_SUPER1 Alternate Manager Processing Logic for User Alpha Numeric

Connector - SF [page 18]


REMOVE_ALT_SUPER1 Alternate Manager Processing Logic for User Alpha Numeric



SHOPPING_ACCT_TYPE This is the shopping account type. INTERNAL or EX

TERNAL
If null, defaults to the FINANCIAL configura
tion default.
ENABLE_SHOPPING_ACCT This is the shopping account type. Alpha Numeric Y or N (Boolean)
If null, defaults to Y.
PTG_USER Only used for Talent Gateway. Alpha Numeric Y or N (Boolean)
POS_NUM_ID This is the job position ID. Alpha Numeric
INCLUDE_IN_GOVT_REPORTING Applies to French government reporting. Alpha Numeric Y or N (Boolean)

LMS Character
LGL_ENTITY_2483_ID This is the Legal Entity ID used for French Alpha Numeric 90
government reporting. If provided Legal En
tity ID does not exist in LMS DB, it will be cre
ated automatically.
LGL_ENTITY_2483_DESC Only used if provided Legal Entity ID in same Alpha Numeric 300
automatically.
LGL_COUNTRY_ID Only used if provided Legal Entity ID in same Alpha Numeric

automatically. If provided, it must be a valid
country ID.
EMP_CLASS_2483_ID This is the Employee Class ID used for French Alpha Numeric 90
government reporting. If provided Employee
Class ID does not exist in LMS DB, it will be
EMP_CLASS_2483_DESC Only used if provided Legal Entity ID in same Alpha Numeric 300
automatically.
HOURLY_RATE This is the hourly rate used for French gov Numeric
ernment reporting.
HOURLY_RATE_CURRENCY This is the hourly rate currency used for Alpha Numeric
French government reporting. This must be a
valid currency ID.
REGULAR_TEMP_ID This is the Regular Temp ID used as an addi Alpha Numeric 90

tional user attribute. If provided Regular
Temp ID does not exist in LMS DB, it will be
REGULAR_TEMP_DESC Only used if provided Regular Temp ID in Alpha Numeric 300

FULLTIME This is an additional user attribute. Alpha Numeric Y or N (Boolean)
NATIVE_DEEPLINK_USER This indicates whether the user can access Alpha Numeric Y or N (Boolean)
native deep links.
ADJUSTED_HOURLY_RATE This is used for 2483 French government re Alpha Numeric Y or N (Boolean)
porting. It is the adjusted hourly rate.

LMS Character
ADJUSTED_HOURLY_RATE_CUR This is used for 2483 French government re Alpha Numeric Y or N (Boolean)
RENCY porting. It is the adjusted hourly rate’s cur
rency.
AGE This is used for 2483 French government re Alpha Numeric Y or N (Boolean)
porting. It is the user’s age.
DISABILITY_CLASSIFICATION_ID This is used for 2483 French government re Alpha Numeric Y or N (Boolean)
porting. It is the user’s disability classifica
tion.
BIRTH_DATE This is used for 2483 French government re Alpha Numeric Integer
porting. It is the user’s birthdate in order to

determine the user's age.
2.2 User HRBP and Alternate Manager Data Mapping
View the User HRBP and Alternate Manager map for User Connector data file between the header column and its
data, along with notes, rules, and other information.
When you create your data file, it must be named as follows, where <Suffix> is your tenant ID. In some uncommon
cases, customers set a different suffix in System Administration 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.
Data file name: user_manager_data_<Suffix>.txt
This input file supports mapping a user to an alternate manager or an HRBP manager. The LMS supports up to a
total of 200 alternate managers and HRBPs. This file, when present, is processed by the user connector.
 Note
It’s possible to run the standard User Connector and User Connector - Federal with only the
user_manager_data.txt file.
 Note
The "LMS Database Column Name" is provided for readers who are familiar with user configuration in SAP
SuccessFactors Learning. For example, if you are familiar with other user connectors, you might recognize
"NOTACTIVE" as the active flag in the SAP SuccessFactors Learning tables.

LMS Character
STUD_ID Required to be present in the input file. The Alpha Numeric 90

unique user ID. If the ID doesn’t exist in the
system, the system creates a new user re
cord.
MANAGER Required to be present in the input file. Refer Alpha Numeric N/A
ence field. The connector rejects the record if
the Manager value isn’t a valid user ID
REMOVE_ALT_SUPER This removes the manager from the user ID. Alpha Numeric Y or N only (Boo
Defaults to N. lean)
Options are:
Y = removes the manager from the user
N = adds the manager to the user
ALT_SUPER_TYPE Required to be present in the input file. This Alpha Numeric A or H only (Boo
is the alternate manager type. lean)
Options are:
A = this is an alternate manager
H = this is an HRBP
2.3 Adding Additional Custom Columns in User Connector
Read how you can add additional custom columns through the user connector.
The custom column table expands. Each row is a column number and value. This allows you to add additional
custom columns, not just the number specified in the map. You must configure the connector to support additional
custom columns.
In the System Admin Configuration System Configuration CONNECTORS system properties file, you find
the following configuration:
user.field.customcolumn.<col_num>=<field mapping from input file>
The col_num is the custom column number as set up in the LMS. The field mapping from input file is the input field
that you are mapping to this custom column. For example, you want to add custom columns 200, 300, 400, and
500 then you would add this to the properties file:
user.field.customcolumn.200=<field mapping from input file>


2.4 Running Multiple Data Files with User Connector
Read how you can run more than one file in the user connector.
You can run multiple user files through a single connector run. Type a sequence number after the .txt portion of the
filename. For example, if you had two files to process in a single run then you would name the two separate files as:
user_data.txt.1 and user_data.txt.2. The connector processes each file separately. This causes the connector to
output a report for each file it processes.
2.5 General Processing Rules
2.5.1 Active and Inactive Processing for User Connector
View the process and rules for marking users as active or inactive with User Connector.
Active and Inactive Flag
In the User Connector, the active and inactive flag is controlled by a value of N or Y. This connector looks at only one
criterion for determining whether a record will be created or updated to active or inactive:
● If “NOTACTIVE” value = N, record will be created Active (or existed records will be updated to Active).
● If “NOTACTIVE” value = Y, record will be created Inactive (or existed records will be updated to Inactive).
The Result of Inactivating Users
These rules are displayed for informational purposes and cannot be modified. When a user is inactivated (you
inactivate a user through the NOTACTIVE field), the system:
● 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
● Does not inactivate users who are direct subordinates to the user getting inactivated
● 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 schedule offerings
● Resets (clears) online items started by the user who is inactivated

2.5.2 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 System Admin Configuration System
Configuration 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
2.5.3 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:
● 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.
2.5.4 New User Notification Settings
View the notification settings for new users created through the connectors.
New users created from the connector receive the notification settings defined in System Admin Configuration
User Settings .

2.5.5 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.

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 : 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
with SAP) to this:
● 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 genderspecific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.

Important Disclaimers and Legal Information CONFIDENTIAL 21
www.sap.com/contactsap
© 2020 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

Importing Learners With The User Connector: Confidential Document Version: 2H 2020 - 2020-10-09

Uploaded by

Copyright:

Available Formats

Importing Learners With The User Connector: Confidential Document Version: 2H 2020 - 2020-10-09

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Importing Learners With The User Connector: Confidential Document Version: 2H 2020 - 2020-10-09

Uploaded by

Copyright:

Available Formats

CONFIDENTIAL

Document Version: 2H 2020 – 2020-10-09

Importing Learners with the User Connector

THE BEST RUN

1 Engage Certified Partner to Import Data to SAP SuccessFactors Learning . . . . . . . . . . . . . . . . . . . 4

2 About User Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Importing Learners with the User Connector

Read what's new for the User Connector guide.

What's New Description More Info

Initial Publication in Q3 2016 The User Connector guide is for imple­

Importing Learners with the User Connector

Importing Learners with the User Connector

2.1 User Connector Header Mapping

Data file name: user_data_<Suffix>.txt

See Active and Inactive Processing for User

STUD_ID Required to be present in the input file. The Alpha Numeric 90

FNAME The given name of the user. Alpha Numeric 150

Importing Learners with the User Connector

LNAME The family name of the user. Alpha Numeric 150

EXTERNAL_ID This is a unique identifier of a person. It will Alpha Numeric 90

Job Title is not directly associated with Job

JL_ID If provided Job Location ID does not exist in Alpha Numeric 90

Importing Learners with the User Connector

DMN_ID If provided Domain ID does not exist in LMS Alpha Numeric 90

If null, defaults to Default User Domain.

ORG_ID If provided Organization ID does not exist in Alpha Numeric 90

ORG_DESC Only used if provided Organization ID in same Alpha Numeric 300

EMP_TYP_ID If provided Employee Type ID does not exist Alpha Numeric 90

EMP_TYP_DESC Only used if provided Employee Type ID in Alpha Numeric 120

EMP_STAT_ID If provided Employee Status ID does not exist Alpha Numeric 90

EMP_STAT_DESC Only used if provided Employee Status ID in Alpha Numeric 120

ADDR Address. Alpha Numeric 600

CITY City. Alpha Numeric 300

STATE State. Alpha Numeric 150

Importing Learners with the User Connector

POSTAL Postal Code. Alpha Numeric 150

CNTRY The connector rejects the record if the Alpha Numeric

REGION_ID The following are valid region ID values: Alpha Numeric

Format the datetime as MON-DD-YYYY

The connector can accept futrue hire dates if

If the Notactive value is set to N then the ter­

A NULL value for this field always overwrites

Format the datetime as: MON-DD-YYYY

Importing Learners with the User Connector

SUPER This needs to reference to an existing user ID Alpha Numeric

The value provided will be nullified if:

● It creates a circular reference (User can­

RESUME_LOCN Alpha Numeric 600

COMMENTS Admin facing free form text. Alpha Numeric 2000

ACCT_ID If provided Account Code does not exist in Alpha Numeric 90

PHON_NUM1_DESC This value is required if Phone Number 1 is Alpha Numeric 300

PHON_NUM2_DESC This value is required if Phone Number 2 is Alpha Numeric 300

PHON_NUM3_DESC This value is required if Phone Number 3 is Alpha Numeric 300

COL_NUM1_VAL This is a custom column value. By default, Alpha Numeric 120

Importing Learners with the User Connector

COL_NUM2_VAL This is a custom column value. By default, Alpha Numeric 120

COL_NUM3_VAL This is a custom column value. By default, Alpha Numeric 120

COL_NUM4_VAL This is a custom column value. By default, Alpha Numeric 120

COL_NUM5_VAL This is a custom column value. By default, Alpha Numeric 120

Initial Publication in Q3 2016 The User Connector guide is for imple

If the Notactive value is set to N then the ter

● It creates a circular reference (User can

MAPPED_ADMIN_ID Provides mapping between User ID and Ad Alpha Numeric

SHOPPING_ACCT_TYPE This is the shopping account type. INTERNAL or EX

REGULAR_TEMP_ID This is the Regular Temp ID used as an addi Alpha Numeric 90