DATA IMPORTS

 Importing employee data is an efficient way of adding employees to the system, managing large-scale data
migrations, or handling large scale organization and pay changes.
 In SuccessFactors, you can upload data using the Import feature. Using the Import feature, you can upload
foundation data and employee data.
1. Working with Foundation Data:
 Foundation Objects capture detailed information about company’s organization, pay and job structure.
 Note: When uploading foundation data, it is important to note the associations defined in the data model. A
child object must be uploaded before the parent object is uploaded else the import will fail.
For example, you can have an association between Legal Entity and Department which means that
certain departments can be tied to a specific Legal Entity. When performing an import of Legal Entity,
Department will appear as a column in the import file. For these columns, the external code of the associated
foundation object has to be specified. So, the associated foundation object i.e., Department must be imported
before the Legal Entity foundation object is imported.
 The foundation objects listed on the Import Foundation Data page are determined by the corporate data
model.
 Importing Foundation Data:
a) Admin centerEmployee filesImport foundation data

b) To upload the file, specify the type of import you’d like to do.
c) Specify whether the upload should overwrite existing records or add to existing records. Choose
between Full Purge and Incremental Load.

1
 d) Full purge: Full Load, is a process of completely destroying/deleting the existing data and reloading
it from scratch. A lot of unchanged data is also deleted and reloaded in this process. But a destructive
load (full load) ensures the highest data integrity easily.

Incremental load: Incremental load is a process of loading data incrementally. Only new and
changed data is loaded to the destination. Data that didn’t change will be left alone.
e) In the Choose File field, specify the path to the file.
f) In the File Encoding dropdown, select the relevant encoding applicable.
g) Click Validate Import File Data.
h) Once the file passes the validation checks, upload the file by clicking Import.
1.1. Working with Data Translation:
 Foundation objects is the fundamental data that appears repeatedly throughout the system not just for
the Admin, but also for the employees. Therefore, it is important that this information can be shown in
the user's language.
 To achieve this, you can translate language-specific data of foundation objects, such as the name and
description of the department, business unit, or job classification.
 Depending on the type of the foundation object, the translation process is handled differently for:
a) Job Classification foundation objects (technical name: job Code)
b) All other foundation objects (except job Code)
 Translating data for foundation objects is a 3-step process that includes the following steps:
a) Export or list the translatable foundation data
b) Translate the foundation data
c) Import the translations
 For job code foundation objects:
“Admin centreManage permission rolesClick the permission buttonscroll down to
administrator permissionsManage foundation objectsSelect ‘Import translations’ check box.”

 For other foundation objects:

a) Selected the checkbox Enable Translation of Employee Central Foundation Objects
in Provisioning
b) Enabled generic objects in Provisioning
c) Set up the Corporate Data Model
d) Imported or created foundation objects

2
1.2. Translating foundation data:

After the import, the system decides in which language a foundation object is displayed in this sequence.

a) For job code type foundation objects:

 Get a list with the job Code data that you want to translate. Please note that you can only translate data
that is used in the following job Code fields: name, description, custom string1-20.
These are the HRIS-field IDs used in the Corporate Data Model for the job Code HRIS element.
 Translate the data:
You can send the list with the job Code texts to the translator(s) to have the texts translated.
Create a CSV file in the following format and enter the texts in the company's default language as
well as the translations:

Here’s how to read this file

a) First row- Local ID’s of the languages you want to enter translations for. (You can
find the correct locale ID for each language in Provisioning under Company
Settings for example, en_US for US English, fr_FR for French, and so on).
b) Note that you can only import translations for the language packs activated in
Provisioning.
c) Second row: Names of the locales in English. (Ignore when data is imported)
d) Third row: (Row 3 and below are importable) Here you enter the texts that appear
on the user interface, as well as their translations. Only texts in the following HRIS
fields for job Code are translatable: name, description, custom-string1-20.
 Import the translations:
Admin centerEmployee filesImport translationsChoose field fileBrowse the csv file you
have done beforeClick on import.

3
b) For all other Foundation objects except job codes:
1. Export existing foundation data into a CSV file.
2. Admin centerEmployee filesImport and export dataIn the Download Data Import File
Template field, select ‘FoTranslation’. (In the confirmation popup that asks if you want to fill the
download template with existing data, select Yes.)Go back to admin centerMonitor jobOpen
the download template that starts with ‘FoTranslation_MDFExport’ by clicking Download Status.

This is a sample for what the downloaded CSV file looks like:

 The first two rows are the column titles. The columns define the following:
a) External code: This is a specific external code that the system assigns all instances of
foundation objects that exist in the system. This is not the external code the Admin has
created or imported, but it is the FoTranslation-specific external code that is created when
you enable the foundation object translation in Provisioning.
b) foObject ID (Foundation object id): This is a specific ID that the system assigns all instances
of foundation objects that exist in the system. This ID is created when you enable the
foundation object translation in Provisioning.
c) fo type: This is the type of the foundation object, for example, business unit, job function,
company, and so on.
d) fo field: This column contains the HRIS-field ID for all translatable fields (typically name
and description).
e) Value: The remaining columns that begin with value. and that are followed by the locale ID
for the corresponding language (for example, value.en_US for US English, value.fr_FR for
French) represent one language.

4
3. Translate the foundation data:
You can now send the CSV file to the translator(s) who can edit the file offline and Consolidate the
translations for all required languages in one CSV file.
This is an example for a translated file, the translations are highlighted:

4. Import the translations:

Admin centerEmployee filesImport and export dataIn the Import portlet, in the type field
select ‘FoTranslation’in the file field browse the translated csv filein the file encoding field
select the character set that is appropriate for the languages that you want to importpurge
typeFull purgeclick validate and then import.

5. After the import, the system decides in which language a foundation object is displayed in this
sequence:
 The system checks whether the foundation data is available in the logon language of the user.
This is the language the user has selected under Options Change Language.
 If there is no translation in the logon language, the system shows the default language that has
been set in Provisioning under Company SettingsDefault Language.
 If there is no translation in the default language, the system looks for a translated term in US
English.

5
2. Employee data import:
 Employee objects include information about person and employment data of an employee. This is also
referred to HR data objects. When you're importing employee data into Employee Central, the sequence of
the import counts.
You need to perform the data upload in the order,
a) Create user account
b) Create persons in the system
c) Upload employment information
d) Upload job information
e) Upload compensation information (such as base salary, bonus etc)
f) Upload personal information
a) Create user account:
 Basic import: This is a required import
 Extended import: Additional information stored by the system related to user accounts. The first
import that must be performed. When you run a Basic Import, user accounts are created for all users
whose data is to be uploaded. This is optional and can be done later.
 Background import: Additional information stored by the system related to user accounts.
This is optional and can be done later.
b) Create persons in the system:
 Biographical information import: The first import that must be performed. When you run a Basic
import once the user accounts are ready, each user account must be populated with biographical
information. When this is done ‘persons’ are created in the system.
 This is a required import.
c) Upload employment information:
 Employment details import: Run this import to upload employment information. This is a required
import.
 Work eligibility: Run this import to upload information about employee work eligibility. This
includes information like the employee’s passport details and citizenship. This is optional and can
be imported later.

d) Upload job information:

 Job history import: The job history template includes information about the current assignment.
Since the country information of the employee also depends on the job information it is the required
import.
 Job relationships: This import uploads information about other managers that the employee works
with. For example, Matrix Manager and HR Manager. Note that information about the employee's
Direct Manager is not captured in this file. This is optional and can be imported later.
6
 e) Upload compensation information:
 Compensation info: Run this import to upload information about the employee’s salary. Note that
this must be done before importing the pay components of an employee. This is because the
recurring import is dependent on the Compensation Info Import. While this import can be done
later, it is recommended that this import be done to ensure employee information uploaded is
complete.
 Pay component recurring: Uploads information about the recurring part of the employee’s pay. This
must be done. To complete the Compensation Info Import, this is a required import.
 Pay component non-recurring: Uploads information about the non-recurring part of the employee’s
pay. This is optional and can be done later.
f) Upload personal information:
 Personal information: This is a required import
 Global information: Run this import to upload country-specific information about the employees.
 Phone information: About the employee’s contact phone numbers (optional import and it can be
done later).
 Email information: About the employee’s email ID’s
 Social accounts info: About the employee’s Social information like linked In and facebook.
 National ID info: About the employee’s Identification number like social security number for US
and PAN card for India.
 Direct deposit: Run this import to upload information about the employee’s bank account to which
the salary will be credited.
 Addresses: About employee’s Address.
 Emergency contact: About an employee’s emergency contacts.
3. Maintain hire date when creating a new user:
When you're importing data for a new user in Employee Central, ensure that initial records of Job Information,
Personal Information and Compensation Information (with the Hire event) start date matches the Employment
Details Hire Date. This is because Employee Central (EC) is an effective-dated system.
4. Suppressing Duplicate inserts while importing employee data:
 Admins can suppress duplicate inserts or unchanged updates while importing Personal Information,
Employment Details, Job History and Biographical Information entities at the company level using the
Suppress update of identical records during Employee Central import for supported entities option.
 Admin centerCompany settings Company system logo settingsselect suppress update of identical
records during employee central import for supported entitiesclick save company system settings.

7
5. Importing Employee Data:
 You can now use the new Import Employee Data page to download templates and upload your import
files.
 Downloading import templates: Admins can download a template on the Import Employee Data page
and provide all the required information in the downloaded template before uploading the user data file.
Admin centerUpdate user informationImport employee datafrom ‘Select the action you want to
perform’ dropdown menu select download templatefrom select an entity dropdown menu, choose a
template you want to downloadClick generate template.

 Uploading import files:

Admin centerUpdate user informationImport employee data from ‘Select the action you want
to perform’ dropdown menu select import data templatefrom ‘select an entity’ dropdown menu
choose the template that you want to uploadin the purge type select ‘full load’ or ‘increment load’
typein the choose field click ‘browse’ and select the path of the filefrom the file encoding drop
down select the relevant encoding applicablein the file local dropdown specify the localevalidate
import dataimport data.
 Configuring Basic User Options While Uploading the Basic Import Template:
Admins can automatically insert a new manager as a part of the review process, remove inactive
employees from the in-progress documents, or update Compensation or Variable forms while
importing the Basic Import entity.
Admin centerUpdate user informationImport employee data from ‘Select the action you want
to perform’ dropdown menu select import data templatefrom ‘select an entity’ dropdown menu
choose the template basic importclick ‘more options’ next to basic imports fieldselect the options
as requiredclick oknow, upload the basic import template.

8
Step1:

Step2: