Data Model Field Information for

Employee Central
Foundation Object Tables
The tables in the list give you the technical information about the foundation
objects we deliver.

Most of the foundation objects include customer-specific fields, listed in the

last rows of each table. These are fields you can customize to use any way
you want, if the foundation objects as delivered do not have all the fields
needed to satisfy your requirements even if, for example, you edit the field
labels. You do not have to use the customer-specific fields, but they are
there if you need them.

Note
Beware that hiding all fields in a block using a business rule is not supported
and will potentially cause unexpected behavior in the system. You must have
at least one field on this object enabled to avoid inconsistent behavior.

For information on how foundation objects are processed in the Corporate

Data Model, including how to create your own foundation objects, refer to
the SAP SuccessFactors Data Model Reference guide.

For an explanation of what foundation objects are, and some links to more
information about them, refer to the SAP SuccessFactors Data Model
Reference guide.

For information on MDF Foundation objects, refer to the Working with MDF
Foundation Objects section of the Implementing Employee Central Core
guide.

Table Columns
Each of the tables has the following columns:
 Standard

If the field appears as part of the standard delivery for the relevant
foundation object, “Yes” appears in this column. “No” appears in the
column if the field is not part of the standard delivery.

 Field ID

Each foundation object consists of one or more fields. This column lists
the technical IDs of the fields. You cannot change this ID.

 Field Label

This is the text that appears in the user interface (UI). You can change
this to suit your own requirements.

 Data Type

HRIS Fields can handle data of various types (for fields of MDF FOs, see
note below.). The options are:

 BIGDECIMAL and DECIMAL

Fields with these data types can handle mathematical

operations.

 BOOLEAN

Fields like this can handle two options. On the UI, the most
common options for such fields are “Yes” and “No”.

 DATE

You can enter dates in fields of this type.

 DOUBLE

Fields with this data type can handle decimal numbers.

 LONG
 Fields with this data type can only contain integers.

 STRING

You can enter a string of characters in fields with this data type.
Where there is a limit on the number of characters in fields like
this, the maximum number of characters allowed is shown in
the Max.Length column.

 Max.Length

Some fields with data type “String” have a limit on the number of
characters you can enter in the string. Where this is the case, this
column shows the relevant maximum.

 Default Visibility

This determines whether the foundation object is visible on the UI and

what you can do in it if it is visible. You can change the default setting
to suit your own requirements, choosing from the following options:

 BOTH: This means the field is visible on the UI for both display
and editing purposes.

 VIEW: This means the field is displayed on the UI, but it cannot
be edited there.

 NONE: The field does not appear on the UI.

 Is Required?

The answer “Yes” in this column indicates that the field is required.
The answer “No” indicates that it is optional.

 How To Use This Field

Here's some help on how to use the fields. For example, if a field needs
additional configuration, you can find the information here.

Note
For MDF Foundation Objects (generic objects), custom fields are no longer
restricted to set number of fields for each data type. Instead, you can now
assign any number of fields, subject to a maximum of 200 fields, depending
on your requirement to a data type. Other points that apply to custom fields
for MDF FOs:

 For each object, you can assign a maximum of 200 custom fields.

 There is no restriction on the name specified for the custom field.

However, as a standard, all names specified will automatically be
prefixed with cust_ to indicate it is a custom field.

 For the different data types you can assign to a field, click the Data
Type dropdown for the field in the Configure Object
Definition page.

 The enum data type cannot be assigned to a custom field. This is

restricted for pre-delivered fields.

 Use the clob data type for fields that require a max length greater than
255. For example, Job Description.

 If you choose to assign one of these data types to a custom field

(boolean, date, datetime, time, autocomplete, picklist, Generic Object,
Foundation Object, attachment and user), do not specify the max
length as the system will automatically take care of this.

Related Information
Corporate Data Model

MDF Foundation Objects

On this page

 Table Columns

 Related Information

Organisation Objects A-Z

Business Unit
Business Unit
Here is a list of the fields available for this element.

BusinessUnit is an MDF Generic Object. Use the Configure Object Definition page
to update this object.

generic object id: BusinessUnit

Standa Field ID Field Data Max. Visibilit Requir How to

rd Label Type Lengt y ed Use this
h Field

Yes description Descripti Translata 128 As No If you

defined
on ble need a
in the
Configu more
re detailed
Object descripti
Definiti on of the
on
business
page.
unit than
the
Name
field can
provide,
enter it
here.

Yes effectiveStart Start Date Date — As Yes Enter the

Date defined date the
in the business
Configu unit
Standa Field ID Field Data Max. Visibilit Requir How to
rd Label Type Lengt y ed Use this
h Field

re becomes
Object active.
Definiti
on page.

Yes effectiveEndD End Date Date — As No You can

ate defined also
in the enter the
Configu date the
re business
Object unit
Definiti stops
on page. being
active.

Yes effectiveStatus Status Enum — As Yes Possible

defined values
in the are
Configu Active
re and
Object Inactive.
Definiti Do not
on page. configur
e this as
a
picklist.

Yes externalCode Code String 32 As Yes Define a

defined unique
in the code by
Configu which
 Standa Field ID Field Data Max. Visibilit Requir How to
rd Label Type Lengt y ed Use this
h Field

re the
Object system
Definiti can
on page. distingui
sh the
different
business
units
from
each
other.

Yes headOfUnit HeadOfU User — As No You can

nit defined enter the
in the identifier
Configu of the
re person
Object heading
Definiti the
on page. business
unit.

Yes name Name Translata 90 As No You can

defined
ble enter a
in the
Configu short
re name for
Object the
Definiti business
on
unit
page.
here.
Was this page helpful?
Corporate Address
Here is a list of the fields available for this element.

hris-element id: corporateAddress

Note
For a country/region-specific setup of corporateAddress, refer to the SAP
SuccessFactors Employee Central Country/Region Specifics Implementation
Guide.

Standar Field ID Field Data Max. Visibilit Require How to Use

d Label Type Lengt y d this Field
h

No start-date Start DATE — Both Yes Enter the

Date date when
the
corporate
address
becomes
effective.

No end-date End DATE — None No This is the

Date end date the
previous
corporate
address
stops being
effective.
The system
calculates
the end date
automaticall
y depending
on the start
Standar Field ID Field Data Max. Visibilit Require How to Use
d Label Type Lengt y d this Field
h

date
entered.

Yes address1 Address STRING 256 None No You can

1 enter the
first line of
address
here.

Yes address2 Address STRING 256 None No You can

2 enter the
second line
of address
here.

Yes address3 Address STRING 256 None No You can

3 enter the
third line of
address
here.

Yes city City STRING 30 Both No This is

where you
enter the
city or town
the
company is
located in.

Yes county District STRING 256 None No This is

where you
enter the
Standar Field ID Field Data Max. Visibilit Require How to Use
d Label Type Lengt y d this Field
h

county the
company is
located in.

Yes state State STRING 256 None No This is

where you
enter the
state the
company is
located in.

Yes province Province STRING 256 None No This is

where you
enter the
province the
company is
located in.

Yes zip-code Zip STRING 256 None No This is

Code where you
enter the
ZIP code of
the place the
company is
located in.

Yes country Country STRING 256 Both Yes This is

where you
enter the
country the
company is
located in.
 Standar Field ID Field Data Max. Visibilit Require How to Use
d Label Type Lengt y d this Field
h

No address21 Custom STRING 256 Both No You can use

-25 Strings these fields
21-25 for data not
covered by
No custom- Custom STRING 256 None No the fields
string1– Strings supplied as
20 1–20 standard.

No custom- Custom DATE — None No

date1–10 Dates 1–
10

No custom- Custome LONG — None No

long1–20 r
Number
s 1–20

No custom- Custom DOUBL — None No

double1– Decimal E
20 s 1–20
Was this page helpful?

Cost Center
Here is a list of the fields available for this element.

Cost Center is now an MDF Generic Object. Use the Configure Object
Definition page to update this object.

generic object id: CostCenter

Stand Field ID Field Label Data Max Visibil Requi How to
ard Type . ity red Use this
Len Field
gth

Yes costCenterExterna External String 40 As No This field

lObjectId
Object ID define contains
d in the cost
the center ID
Config in
ure external
Object format. If
Defini you have
tion multiple
page. financial
systems
from
which
you
upload
cost
centers
into Empl
oyee
Central,
make
sure that
the cost
center
IDs are
unique.
Usually,
downstre
am
systems
Stand Field ID Field Label Data Max Visibil Requi How to
ard Type . ity red Use this
Len Field
gth

like
payroll
do not
understan
d this
unique
ID and
you have
to
provide
the cost
center ID
in its
external
format.

Yes costCenterManag CostcenterM User 255 As No Specify

er
anager define the cost
d in center
the manager'
Config s
ure identifier
Object here.
Defini
tion
page.

Yes description Description Translat 128 As No Specify a

able define descriptio
d in n here if
Stand Field ID Field Label Data Max Visibil Requi How to
ard Type . ity red Use this
Len Field
gth

the you need

Config a more
ure detailed
Object descriptio
Defini n of the
tion cost
page. center
than the
one the
Name
field
provides.
This field
is
translated
to
English
(US) and
the
company'
s default
language.

Yes effectiveStartDate Start Date Date 255 As Yes Specify

define the date
d in on which
the the cost
Config center
ure becomes
Object active.
Defini
tion
Stand Field ID Field Label Data Max Visibil Requi How to
ard Type . ity red Use this
Len Field
gth

page.

Yes effectiveEndDate End Date Date 255 As No Specify

define the date
d in on which
the the cost
Config center
ure stops
Object being
Defini active.
tion
page.

Yes effectiveStatus Status Enum 255 As Yes Possible

define values
d in are
the Active
Config and
ure Inactive.
Object Do not
Defini configure
tion this as a
page. picklist.

Yes externalCode Code String 32 As Yes Specify a

define unique
d in code by
the which
Config the
ure system
Object can
Defini distinguis
tion h the
Stand Field ID Field Label Data Max Visibil Requi How to
ard Type . ity red Use this
Len Field
gth

page. different
cost
centers
from
each
other.

Yes glStatementCode GLStatement String 32 As No This code

define
Code is
d in
the assigned
Config to
ure account
Object groups,
Defini
such as
tion
customer
page.
receivabl
es or
vendor
payables
to record
transactio
ns,
dependin
g on
financial
accounts
involved
in such
transactio
ns. It
ensures
Stand Field ID Field Label Data Max Visibil Requi How to
ard Type . ity red Use this
Len Field
gth

that total
account
data
includes
all sub-
account
transactio
ns.

Yes legalEntity Legal Entity Generic 38 As No Specify a

define legal
Object
d in entity to
the be
Config associate
ure d with
Object the cost
Defini center.
tion By
page. default,
this field
is set to
not
visible.
That can
be
changed
in the
object
definition
.

Yes Name Name Translat 90 As No Specify a

define
able short
d in
Stand Field ID Field Label Data Max Visibil Requi How to
ard Type . ity red Use this
Len Field
gth

the name for

Config
the cost
ure
Object center
Defini unit here.
tion This field
page. is
translated
to
English
(US) and
the
company'
s default
language.

Yes parentCostCenter Parent Generic 255 As No Cost

Object define centers
d in can be
the hierarchi
Config cal. If
ure this is the
Object case in
Defini your
tion business,
page. use this
field to
specify a
higher-
level cost
center.
Was this page helpful?

Department
Here is a list of the fields available for this element.

Department is now an MDF Generic Object. Use the Configure Object

Definition page to update this object.

generic object id: Department

Standa Field ID Field Data Max. Visibilit Requir How to

rd Label Type Lengt y ed Use this
h Field

Yes costCenter Cost Cost — As No You can

Center Center defined assign the
GO in the departme
Configu nt to a
re cost
Object center by
Definiti entering
on page. the cost
center
details
here.

Yes description Descripti Translata 128 As No If you

on ble defined need a
in the more
Configu detailed
re descriptio
Object n of the
Definiti departme
on page. nt than
Standa Field ID Field Data Max. Visibilit Requir How to
rd Label Type Lengt y ed Use this
h Field

the Name
field can
provide,
enter it
here.

Yes externalCode Code String 32 As Yes Define a

defined unique
in the code by
Configu which the
re system
Object can
Definiti distinguis
on page. h the
different
departme
nts from
each
other.

Yes effectiveStart Start Date — As Yes Enter the

Date Date defined date the
in the departme
Configu nt
re becomes
Object active.
Definiti
on page.

Yes effectiveEndD End Date Date — As No You can

ate defined also enter
Standa Field ID Field Data Max. Visibilit Requir How to
rd Label Type Lengt y ed Use this
h Field

in the the date

Configu the
re departme
Object nt stops
Definiti being
on page. active.

Yes effectiveStatus Status Enum — As Yes Possible

defined values are
in the Active
Configu and
re Inactive.
Object Do not
Definiti configure
on page. this as a
picklist.

Yes headOfUnit Head of User — As No You can

defined
Departm enter the
in the
ent Configu departme
re nt head's
Object identifier
Definiti here.
on
page.

Yes name Name Translata 90 As No You can

ble defined enter a
in the short
Configu name for
re the
 Standa Field ID Field Data Max. Visibilit Requir How to
rd Label Type Lengt y ed Use this
h Field

Object departme
Definiti nt.
on page.

Yes parentDepartm Departm Departme — As No You can

ent ent nt GO defined enter the
in the departme
Configu nt that is
re on the
Object next level
Definiti up in the
on page. cost
center
hierarchy.
Was this page helpful?

Division
Here is a list of the fields available for this element.

Division is now an MDF Generic Object. Use the Configure Object

Definition page to update this object.

generic object id: Division

Standa Field ID Field Data Max. Visibilit Requir How to

rd Label Type Lengt y ed Use this
h Field

Yes description Descripti Translata 128 As No If you

on ble defined need a
Standa Field ID Field Data Max. Visibilit Requir How to
rd Label Type Lengt y ed Use this
h Field

in the more
Configu detailed
re descripti
Object on of the
Definiti division
on page. than the
Name
field can
provide,
enter it
here.

Yes externalCode Code String 32 As Yes Define a

defined unique
in the code by
Configu which
re the
Object system
Definiti can
on page. distingui
sh the
different
divisions
from
each
other.

Yes effectiveStart Start Date — As Yes Enter the

Date Date defined date the
in the division
Configu becomes
Standa Field ID Field Data Max. Visibilit Requir How to
rd Label Type Lengt y ed Use this
h Field

re active.
Object
Definiti
on page.

Yes effectiveEndD End Date Date — As No You can

ate defined also
in the enter the
Configu date the
re division
Object stops
Definiti being
on page. active.

Yes effectiveStatus Status Enum — As Yes Possible

defined
values
in the
Configu are
re Active
Object and
Definiti Inactive.
on
Do not
page.
configur
e this as
a
picklist.

Yes headOfUnit Head of User — As No You can

Division defined enter the
in the division
Configu head's
re identifier
 Standa Field ID Field Data Max. Visibilit Requir How to
rd Label Type Lengt y ed Use this
h Field

Object here.
Definiti
on page.

Yes name Name Translata 90 As No You can

ble defined enter a
in the short
Configu name for
re the
Object division
Definiti here.
on page.

Yes parentDivision Division Division — As No You can

GO defined enter the
in the division
Configu that is on
re the next
Object level up
Definiti in the
on page. division
hierarch
y.
Was this page helpful?

Geozone
Here is a list of the fields available for this element.

hris-element id: geozone

Standa Field ID Field Data Max. Visibili Requir How to
rd Label Type Leng ty ed Use this
th Field

Yes adjustmentPerce Adjustm STRIN — Both No If the pay

ntage ent G range for
Percenta this
ge geozone is
to differ
by a
certain
percentage
from that
for
another
geozone,
you can
specify the
percentage
here.

This field
is
informatio
nal only
and is not
used to
calculate
compa
ratio or
range
penetratio
n.

Yes description Descripti STRIN 128 Both No If you

Standa Field ID Field Data Max. Visibili Requir How to
rd Label Type Leng ty ed Use this
th Field

on G need a
more
detailed
descriptio
n of the
geozone
than the
Name
field can
provide,
enter it
here.

Yes externalCode Code STRIN 32 Both Yes Define a

G unique
code by
which the
system
can
distinguish
the
different
geozones
from each
other.

Yes name Name STRIN 90 Both No You can

G enter a
short
name for
the
Standa Field ID Field Data Max. Visibili Requir How to
rd Label Type Leng ty ed Use this
th Field

geozone
here.

Yes start-date Start DATE — Both Yes Enter the

Date date the
geozone
becomes
active.

Yes end-date End Date DATE — None No You can

also enter
the date
the
geozone
stops
being
active.

Yes status Status STRIN — Both Yes Possible

G values are
Active and
Inactive.
Do not
configure
this as a
picklist.

No custom-string1– Custom STRIN 256 None No You can

20 Strings G use these
1–20 fields for
data not
No custom-date1–10 Custom DATE — None No
 Standa Field ID Field Data Max. Visibili Requir How to
rd Label Type Leng ty ed Use this
th Field

Dates 1–
10

No custom-long1–20 Custome LONG — None No

r
Numbers
1–20 covered by
the fields
No custom-double1– Custom DOUB — None No supplied as
20 Decimals LE standard.
1–20
Was this page helpful?

Legal Entity
Here is a list of the fields available for this element.

Legal Entity is now an MDF Generic Object. Use the Configure Object
Definition page to update this object.

generic object id: LegalEntity

Note

For information on country/region-specific fields that were earlier referenced

through legalEntityLocal, refer to the SAP SuccessFactors Employee Central
Country/Region Specifics Implementation Guide.
Standa Field ID Field Data Max. Visibili Requir How to
rd Label Type Leng ty ed Use this
th Field

Yes countryOfRegistr Country Country — As Yes Enter

ation GO defined the
in the country
Configu that
re makes
Object up this
Definiti geozone
on .
page.

Yes currency Currency Currency — As Yes Enter

GO defined the
in the currency
Configu that is
re used for
Object this
Definiti legal
on entity.
page.

Yes defaultLocation Default location — As No You can

Location FO defined enter a
in the location
Configu that
re applies
Object to all
Definiti employe
on es in this
page. legal
entity.
Standa Field ID Field Data Max. Visibili Requir How to
rd Label Type Leng ty ed Use this
th Field

Yes defaultPayGroup Default PayGrou — As No You can

p GO
Pay defined enter a
Group in the pay
Configu group
re that
Object applies
Definiti to all
on employe
page. es in this
legal
entity.

Yes description Descripti Translata 128 As No If you

on ble defined need a
in the more
Configu detailed
re descripti
Object on of the
Definiti legal
on entity
page. than the
Name
field can
provide,
enter it
here.

Yes externalCode Legal String 32 As Yes Define a

Entity defined unique
ID in the code by
Configu which
Standa Field ID Field Data Max. Visibili Requir How to
rd Label Type Leng ty ed Use this
th Field

re the
Object system
Definiti can
on distingui
page. sh the
different
legal
entities
from
each
other.

Yes name Legal Translata 90 As No You can

Entity ble defined enter a
Name in the short
Configu name
re for the
Object legal
Definiti entity
on here.
page.

Yes effectiveStatus Status Enum — As Yes Possible

defined values
in the are
Configu Active
re and
Object Inactive.
Definiti Do not
on configur
page. e this as
Standa Field ID Field Data Max. Visibili Requir How to
rd Label Type Leng ty ed Use this
th Field

a
picklist.

Yes effectiveStartDat Start Date — As Yes Enter

e Date defined the date
in the the legal
Configu entity
re becomes
Object active.
Definiti
on
page.

Yes effectiveEndDate End Date — As No You can

Date defined also
in the enter the
Configu date
re when
Object the legal
Definiti entity
on stops
page. being
active.

Yes standardWeekly Standard Decimal — As No In this

Hours Weekly defined field,
Hours in the you can
Configu enter the
re number
Object of hours
Definiti employe
 Standa Field ID Field Data Max. Visibili Requir How to
rd Label Type Leng ty ed Use this
th Field

on es are
page. expected
to work
in this
geozone
.

Yes officialLanguage Official String — As No If there

Languag defined is an
e in the official
Configu languag
re e for a
Object legal
Definiti entity,
on you can
page. enter the
ISO
code for
that
languag
e here.
Was this page helpful?

Location
Here is a list of the fields available for this element.

hris-element id: location

Standar Field ID Field Data Max. Visibilit Require How to
d Label Type Lengt y d Use this
h Field

Yes description Descriptio STRING 128 Both No If you

n need a
more
detailed
descriptio
n of the
location
than the
Name
field can
provide,
enter it
here.

Yes externalCod Code STRING 32 Both Yes Define a

e unique
code by
which the
system
can
distinguis
h the
different
locations
from
each
other.

Yes locationGro Location STRING — Both No If you

up Group want to
assign
Standar Field ID Field Data Max. Visibilit Require How to
d Label Type Lengt y d Use this
h Field

this
location
to a
group,
enter the
identifier
for the
relevant
group
here.

Yes name Name STRING 90 Both No You can

enter a
short
name for
the
location.

Yes start-date Start Date DATE — Both Yes Enter the

date
when the
location
becomes
active.

Yes end-date End Date DATE — None No You can

also enter
the date
the
location
stops
Standar Field ID Field Data Max. Visibilit Require How to
d Label Type Lengt y d Use this
h Field

being
active.

Yes status Status STRING — Both Yes Possible

values
are
Active
and
Inactive.
Do not
configure
this as a
picklist.

Yes standardHou Standard DOUBL — Both No You can

rs Weekly E enter the
Hours standard
weekly
hours for
a
location.

Yes timezone Timezone STRING — Both No You can

enter the
timezone
for the
location.

No custom- Custom STRING 256 None No You can

string1–20 Strings 1– use these
20 fields for
 Standar Field ID Field Data Max. Visibilit Require How to
d Label Type Lengt y d Use this
h Field

No custom- Custom DATE — None No data not

date1–10 Dates 1– covered
10 by the
fields
No custom- Customer LONG — None No supplied
long1–20 Numbers as
1–20 standard.

No custom- Custom DOUBL — None No

double1–20 Decimals E
1–20
Was this page helpful?

Location Group
Here is a list of the fields available for this element.

hris-element id: locationGroup

Standar Field ID Field Data Max. Visibilit Require How to

d Label Type Lengt y d Use this
h Field

Yes description Descriptio STRING 128 Both No If you

n need a
more
detailed
descriptio
n of the
location
group
Standar Field ID Field Data Max. Visibilit Require How to
d Label Type Lengt y d Use this
h Field

than the
short
Name can
provide,
enter it
here.

Yes externalCod Code STRING 32 Both Yes Define a

e unique
code by
which the
system
can
distinguis
h the
different
location
groups
from each
other.

Yes name Name STRING 90 Both No You can

enter a
short
name for
the
location
group
here.

Yes start-date Start Date DATE — Both Yes Enter the

Standar Field ID Field Data Max. Visibilit Require How to
d Label Type Lengt y d Use this
h Field

date the
location
group
becomes
active.

Yes end-date End Date DATE — None No You can

also enter
the date
the
location
group
stops
being
active.

Yes status Status STRING — Both Yes Possible

values are
Active
and
Inactive.
Do not
configure
this as a
picklist.

No custom- Custom STRING 256 None No You can

string1–20 Strings 1– use these
20 fields for
data not
No custom- Custom DATE — None No covered
date1–10 Dates 1–
 Standar Field ID Field Data Max. Visibilit Require How to
d Label Type Lengt y d Use this
h Field

10

No custom- Customer LONG — None No

long1–20 Numbers
1–20
by the fields
No custom- Custom DOUBL — None No supplied as
double1–20 Decimals E standard.
1–20
Was this page helpful?

Job Related Objects A-Z

Job Classification
Here is a list of the fields available for this element.

Job Classification is now an MDF Generic Object. Use the Configure Object
Definition page to update this object.

generic object id: JobClassification

Note

For information on country/region-specific fields that were earlier referenced

through jobClassLocal, refer to the SAP SuccessFactors Employee Central
Country/Region Specifics Implementation Guide.
Stand Field ID Field Label Data Type Max Visibil Requi How to
ard . ity red Use this
Len Field
gth

Yes defaultEmploye Employee Picklist 32 As No If a

eClass Class define customer
d in configure
the d picklist
Config is added
ure in Job
Object Informati
Defini on, then
tion that
page. informati
on is
defaulted
here.

Yes defaultJobLevel Job Level Picklist 32 As No If a

define customer
d in configure
the d picklist
Config is added
ure in Job
Object Informati
Defini on, then
tion that
page. informati
on is
defaulted
here.

Yes defaultSupervis Supervisor Picklist — As No If a

orLevel Level define customer
Stand Field ID Field Label Data Type Max Visibil Requi How to
ard . ity red Use this
Len Field
gth

d in configure
the d picklist
Config is added
ure in Job
Object Informati
Defini on, then
tion that
page. informati
on is
defaulted
here.

Yes description Description Translatabl 4000 As No If you

e define need a
d in more
the detailed
Config descripti
ure on of the
Object job
Defini classifica
tion tion than
page. the short
name can
provide,
enter it
here.

Yes fulltimeEmploy Is Full Time Boolean — As No Enter

ee Employee define “Yes” to
d in indicate
Stand Field ID Field Label Data Type Max Visibil Requi How to
ard . ity red Use this
Len Field
gth

the that
Config employe
ure es with
Object this
Defini classifica
tion tion
page. work full
time or
“No” to
indicate
that they
work
part time.
No
picklist
required.

Yes effectiveStartD Start Date Date — As Yes Enter the

ate define date the
d in job
the classifica
Config tion
ure becomes
Object active.
Defini
tion
page.

Yes effectiveEndDa End Date Date — As No You can

te
define also
Stand Field ID Field Label Data Type Max Visibil Requi How to
ard . ity red Use this
Len Field
gth

d in enter the
the date the
Config job
ure classifica
Object tion
Defini stops
tion being
page. active.

Yes effectiveStatus Status Enum — As Yes Possible

define values
d in are
the Active
Config and
ure Inactive.
Object Do not
Defini configure
tion this as a
page. picklist.

Yes externalCode Job Code String 32 As Yes Define a

define unique
d in code by
the which
Config the
ure system
Object can
Defini distingui
tion sh the
page. different
Stand Field ID Field Label Data Type Max Visibil Requi How to
ard . ity red Use this
Len Field
gth

job
classifica
tions
from
each
other.

Yes jobFunction Job Function JobFunctio As No You can

n GO define enter the
d in job
the function
Config relating
ure to this
Object job
Defini classifica
tion tion.
page.

Yes name Job Title Translatabl 90 As No You can

e define enter a
d in short
the name for
Config the job
ure classifica
Object tion here.
Defini
tion
page.

Yes parentJobClassi Parent Job JobClassifi — As No You can

Stand Field ID Field Label Data Type Max Visibil Requi How to
ard . ity red Use this
Len Field
gth

fication Classificatio cation GO define enter the

n d in job code
the that is on
Config the next
ure level up
Object in the job
Defini code
tion hierarchy
page. .

Yes payGrade Pay Grade payGrade — As No You can

FO define enter the
d in pay
the grade for
Config this job
ure classifica
Object tion.
Defini
tion
page.

Yes regularTempor Regular/ Picklist 32 As No This

ary Temporary define field
d in indicates
the whether
Config the
ure employe
Object e is
Defini regular
tion or
 Stand Field ID Field Label Data Type Max Visibil Requi How to
ard . ity red Use this
Len Field
gth

page. temporar
y.

Yes standardWeekl Standard Decimal — As No You can

yHours Weekly define enter the
Hours d in standard
the weekly
Config hours for
ure the job
Object classifica
Defini tion.
tion
page.

Yes workerCompC Workers' String 32 As No This is

ode Comp Code define most
d in commonl
the y used in
Config the US.
ure
Object
Defini
tion
page.
Was this page helpful?

Job Function
Here is a list of the fields available for this element.
Job Function is now an MDF Generic Object. Use the Configure Object
Definition page to update this object.

generic object id: JobFunction

Standa Field ID Field Data Max. Visibili Requir How to

rd Label Type Leng ty ed Use this
th Field

Yes description Descripti Translata 128 As No If you

on ble defined need a
in the more
Configu detailed
re descriptio
Object n of the
Definiti job
on function
page. than the
short
name can
provide,
enter it
here.

Yes externalCode Job String 32 As Yes Define a

Function defined unique
ID in the code by
Configu which the
re system
Object can
Definiti distinguis
on h the
page. different
job
functions
Standa Field ID Field Data Max. Visibili Requir How to
rd Label Type Leng ty ed Use this
th Field

from each
other.

Yes effectiveStatus Status Enum — As Yes Possible

defined values are
in the Active
Configu and
re Inactive.
Object Do not
Definiti configure
on this as a
page. picklist.

Yes effectiveStart Start Date — As Yes Enter the

Date Date defined date the
in the job
Configu function
re becomes
Object active.
Definiti
on
page.

Yes effectiveEndD End Date Date — As No You can

defined
ate also enter
in the
Configu the date
re the job
Object function
Definiti stops
on
being
page.
active.
Standa Field ID Field Data Max. Visibili Requir How to
rd Label Type Leng ty ed Use this
th Field

Yes jobFunctionTy Job Picklist 32 As No This is

pe Function defined customer
Type in the configura
Configu ble
re picklist to
Object use if
Definiti classificati
on on or
page. grouping
of job
functions
is
required.

Yes name Name Translata 90 As No You can

ble defined enter a
in the name for
Configu the job
re function
Object here.
Definiti
on
page.

Yes parentJobFunc Parent JobFuncti — As No You can

tion Function on GO defined enter the
Job in the function
Configu code that
re is on the
Object next level
Definiti up in the
 Standa Field ID Field Data Max. Visibili Requir How to
rd Label Type Leng ty ed Use this
th Field

on function
page. code
hierarchy.
Was this page helpful?

Pay Related Objects A-Z

Frequency
Here is a list of the fields available for this element.

hris-element id: frequency

Standa Field ID Field Data Max. Visibili Requir How to

rd Label Type Lengt ty ed Use this
h Field

Yes annualizationFa Annualizati LONG — Both Yes Use this

ctor on Factor field to
record
the
number
of times
in a year
an
employe
e would
be paid
at this
frequenc
Standa Field ID Field Data Max. Visibili Requir How to
rd Label Type Lengt ty ed Use this
h Field

y to
achieve
an
annual
salary.
Example
: Enter
“12” if
the
employe
e is paid
monthly.

Yes description Descriptio STRIN 128 Both No If you

n G need a
more
detailed
descripti
on of the
frequenc
y than
the short
name
can
provide,
enter it
here.

Yes externalCode Frequency STRIN 32 Both Yes Define a

ID G unique
code by
Standa Field ID Field Data Max. Visibili Requir How to
rd Label Type Lengt ty ed Use this
h Field

which
the
system
can
distingui
sh the
different
frequenci
es from
each
other.

Yes name Name STRIN 90 Both No You can

G enter a
name for
the
frequenc
y here.

No custom-string1– Custom STRIN 256 None No You can

20 Strings 1– G use these
20 fields for
data not
No custom-date1– Custom DATE — None No covered
10 Dates 1–10 by the
fields
No custom-long1– Customer LONG — None No
supplied
20 Numbers
as
1–20
standard.

No custom- Custom DOUB — None No

double1–20 Decimals LE
 Standa Field ID Field Data Max. Visibili Requir How to
rd Label Type Lengt ty ed Use this
h Field

1–20
Was this page helpful?

Pay Calendar
Here is a list of the fields available for this element.

Pay Calendar is now an MDF Generic Object. Use the Configure Object
Definition page to update this object.

generic object id: PayCalendar

Stand Field ID Field Data Max Visibi Requi How to Use

ard Label Type . lity red this Field
Len
gth

Yes payGroup Pay STRIN — As Yes Enter the

Group G define code for the
d in pay group
the to which
Confi this pay
gure period
Object applies.
Defini
tion
page.

Yes toPayPeriod.payPeriod Pay DATE — As Yes Enter the

BeginDate
Period define date a given
Begin d in pay period
Stand Field ID Field Data Max Visibi Requi How to Use
ard Label Type . lity red this Field
Len
gth

Date the starts.

Confi Example:
gure First of the
Object month.
Defini
tion
page.

Yes toPayPeriod.payPeriodE Pay DATE — As Yes Enter the

ndDate Period define date a given
End d in pay period
Date the ends.
Confi Example:
gure 16th of the
Object month.
Defini
tion
page.

Yes toPayPeriod.payCheckI Pay DATE — As Yes Enter the

ssueDate Check define date a pay
Issue d in check is
Date the issued for a
Confi pay period.
gure Example:
Object 18th of the
Defini month.
tion
page.
Stand Field ID Field Data Max Visibi Requi How to Use
ard Label Type . lity red this Field
Len
gth

Yes toPayPeriod.cust_payP Pay LONG — As No You can

eriodsPerYear
Period define enter the
s Per d in number of
Year the pay periods
Confi in a year.
gure
Object
Defini
tion
page.

Yes toPayPeriod.offcycle Offcyc BOOL — As No This field

le EAN define indicates
d in whether a
the payroll run
Confi is a special
gure payroll
Object execution in
Defini addition to
tion a regular (or
page. normal)
payroll
execution.

For
example,
for the
month of
December,
the regular
Stand Field ID Field Data Max Visibi Requi How to Use
ard Label Type . lity red this Field
Len
gth

(normal)
payroll
execution is
scheduled
on Dec 28.
On
December
30, an off-
cycle run is
scheduled
to be
executed for
a year-end
bonus.

Yes toPayPeriod.processing Proces STRIN 256 As No You can

RunId
sing G define enter an
Run d in identifier
ID the for pay
Confi processing
gure runs here.
Object
Defini
tion
page.

Yes toPayPeriod.runType Run STRIN 256 As No The list of

Type G define values
d in comes from
the the
 Stand Field ID Field Data Max Visibi Requi How to Use
ard Label Type . lity red this Field
Len
gth

Confi picklist RU
gure NTYPE.
Object
Defini
tion
page.
Was this page helpful?

Pay Component
Here is a list of the fields available for this element.

hris-element id: payComponent

Sta Field ID Fiel Data M Visi Re How to Use this Field

nda d Type ax. bili qui
rd Lab Le ty red
el ng
th

Yes basePayCom Base STRI — Bot No This attribute is only shown when
ponentGroup Pay NG h the Pay Component Type is set to
Com Percentage. It is hidden when the
pone Pay Component Type is set to
nt Amount. In case Pay Component
Gro Type = "Percentage", a Pay
up Component or Pay Component
Group needs to be selected to
define the amount on which
Sta Field ID Fiel Data M Visi Re How to Use this Field
nda d Type ax. bili qui
rd Lab Le ty red
el ng
th

percentage is to be applied.

Yes canOverride Can BOO — Bot No You can enter “Yes” if it will be
Over LEA h possible to override this pay
ride N component for individual
employees to whom it would
otherwise apply, or “No” if it will
not be possible.

Yes currency Curr CUR — Bot No You can specify the currency in
ency REN h which the pay component is paid.
CY

Yes description Desc STRI 12 Bot No If you need a longer description of

ripti NG 8 h the pay component than the short
on name can provide, enter it here.

Yes displayOnSel Disp BOO — Bot No Controls whether this pay

fService lay LEA h component will be displayed in
on N manager self-service
Self
Serv
ice

Yes end-date End DAT — No No You can also enter the date the pay
Date E ne component stops being active.

Yes externalCode Pay STRI 32 Bot Yes Define a unique code by which the
Com NG h system can distinguish the different
pone pay components from each other.
Sta Field ID Fiel Data M Visi Re How to Use this Field
nda d Type ax. bili qui
rd Lab Le ty red
el ng
th

nt
ID

Yes frequencyCo Freq STRI — Bot Yes Specify how often a pay component
de uenc NG h is paid. Example: annually.
y

Yes is-earning Is BOO — Bot No You can specify whether the pay
Earn LEA h component is an earning or a
ing N deduction.

Yes IsRelevantFo Rele BOO — No No Here you can specify if this pay
rAdvancePay vant LEA ne component is used in the advance
ment for N payments process.
Adv
Possible values are Yes and No.
ance

Yes maxFraction Max LON — No No In this field you can define for each
Digits imu G ne pay component how many decimals
m are maximally shown in
Deci the amount field.
mal
You can choose a number from 0 to
Plac
5. If you do not enter any value, the
es
system uses the following value:

1. The value defined for

the maximumFractionD
igits XML attribute that
has been defined
Sta Field ID Fiel Data M Visi Re How to Use this Field
nda d Type ax. bili qui
rd Lab Le ty red
el ng
th

for payComponentRecu
rring or payComponen
tNonRecurring in the
Succession Data Model
2. If the aforementioned XML
attribute has not been
defined, the default value is
3.

Yes name Nam STRI 90 Bot No You can enter a name for the pay
e NG h component.

Yes number Num DOU — Bot Edit This field supports Unit-based pay
ber BLE h components as well as number of
units.
When Number is selected, Unit of
Measure and Rate are shown.

Yes payCompone Pay STRI — Bot Yes Possible values are Amount,
ntType Com NG h Percentage and Number. Do not
pone configure this as a picklist.
nt
For more information on setting up
Typ
number as a possible value, refer to
e
the Creating a Pay
Component topic in the
Implementing Employee
Compensation Data in Employee
Sta Field ID Fiel Data M Visi Re How to Use this Field
nda d Type ax. bili qui
rd Lab Le ty red
el ng
th

Central guide.

Yes payCompone Pay DOU — Bot No You can specify a value for the pay
ntValue Com BLE h component here.
pone
nt
Valu
e

Yes rate Rate DOU — Bot No This field supports Unit-based pay
BLE h components, typically price for
each unit.

Yes recurring Rec BOO — Bot No You can indicate whether the pay
urrin LEA h component is paid regularly or is
g N just a one-time payment.

Yes selfServiceD Self STRI — Bot No Note

escription Serv NG h
This field is only displayed in the
ice
foundation object and will not show
Desc
up anywhere else, even if filled
ripti
with text. It was originally intended
on
to be used as a description for the
Manager Self-Service UI but was
never implemented.

Yes start-date Start DAT — Bot Yes Enter the date the pay component
Date E h becomes active.
Sta Field ID Fiel Data M Visi Re How to Use this Field
nda d Type ax. bili qui
rd Lab Le ty red
el ng
th

Yes status Stat STRI — Bot Yes Possible values are Active and
us NG h Inactive. Do not configure this as a
picklist.

Yes taxTreatment Tax STRI — Bot No You can indicate whether the pay
Trea NG h component is taxed or not.
tmen
The list of values comes from the
t
picklist TAXTREATMENT.

Yes target Targ BOO — Bot No You can enter “Yes” in this field if
et LEA h the pay component is a target figure
N or percentage, or enter “No” if it is
not.

Yes unit-of- Unit STRI — Bot No This field supports Unit-based pay
components, for example, Day,
measure of NG h
Hour, and so on.
Mea
sure

Yes usedForCom Use STRI — Bot No Controls whether this pay

pPlanning d for NG h component will be used by the
Com comp module. Possible values are
p None, Comp, Varpay and Both. Do
Plan not configure this as a picklist.
ning

No custom- Cust STRI 25 No No You can use these fields for data
string1–20 om NG 6 ne not covered by the fields supplied
Strin as standard.
 Sta Field ID Fiel Data M Visi Re How to Use this Field
nda d Type ax. bili qui
rd Lab Le ty red
el ng
th

gs
1–20

No custom- Cust DAT — No No

date1–10 om E ne
Date
s 1–
10

No custom- Cust LON — No No

long1–20 ome G ne
r
Num
bers
1–20

No custom- Cust DOU — No No

double1–20 om BLE ne
Deci
mals
1–20
Was this page helpful?

Pay Component Group

Here is a list of the fields available for this element.

hris-element id: payComponentGroup

Standa Field ID Field Data Max. Visibil Requir How to
rd Label Type Leng ity ed Use this
th Field

Yes currency Currenc CURREN — Both No You can

y CY specify
the
currency
in which
the pay
compone
nts in
this
group
are paid.

Yes description Descript STRING 128 Both No If you

ion need a
more
detailed
descripti
on of the
pay
compone
nt group
than the
short
name
can
provide,
enter it
here.

Yes end-date End DATE — None No You can

Date also
Standa Field ID Field Data Max. Visibil Requir How to
rd Label Type Leng ity ed Use this
th Field

enter the
date the
pay
compone
nt group
stops
being
active.

Yes externalCode Pay STRING 32 Both Yes Define a

Compon unique
ent code by
Group which
ID the
system
can
distingui
sh the
different
pay
compone
nt
groups
from
each
other.

Yes name Name STRING 90 Both No You can

enter a
short
name for
Standa Field ID Field Data Max. Visibil Requir How to
rd Label Type Leng ity ed Use this
th Field

the pay
compone
nt group.

Yes showOnCompUI Display BOOLEA — Both No You can

on N choose
Comp whether
UI to have
the pay
compone
nt group
displaye
d on the

Yes start-date Start DATE — Both Yes Enter the

Date date the
pay
compone
nt group
becomes
active.

Yes status Status STRING — Both Yes Possible

values
are
Active
and
Inactive.
Do not
configur
e this as
Standa Field ID Field Data Max. Visibil Requir How to
rd Label Type Leng ity ed Use this
th Field

a
picklist.

Yes systemDefined System BOOLEA — None No You can

Defined N enter
“Yes” in
this field
if the
system
generate
s pay
compone
nt
groups
for you,
based on
other
data, or
“No” if
they are
created
manually
.

Yes useForComparatio Use for BOOLEA — Both No You can

Calc Compar N choose
atio whether
Calculati the pay
on compone
nt group
should
Standa Field ID Field Data Max. Visibil Requir How to
rd Label Type Leng ity ed Use this
th Field

be used
as part of
the comp
ratio
calculati
on.

Yes useForRangePenet Use for BOOLEA — Both No You can

ration Range N enter
Penetrati “Yes” if
on this pay
compone
nt group
can be
used to
determin
e how
far into a
given
pay
range an
employe
e has
progress
ed or
“No” if
it is not
used for
that.

No custom-string1–20 Custom STRING 256 None No You can

 Standa Field ID Field Data Max. Visibil Requir How to
rd Label Type Leng ity ed Use this
th Field

Strings use these

1–20 fields for
data not
No custom-date1–10 Custom DATE — None No covered
Dates 1– by the
10 fields
supplied
No custom-long1–20 Custome LONG — None No
as
r
standard.
Number
s 1–20

No custom-double1– Custom DOUBLE — None No

20 Decimal
s 1–20
Was this page helpful?

Pay Grade
Here is a list of the fields available for this element.

hris-element id: payGrade

Standar Field ID Field Data Max. Visibilit Require How to

d Label Type Lengt y d Use this
h Field

Yes description Descriptio STRING 128 Both No If you

n need a
more
detailed
Standar Field ID Field Data Max. Visibilit Require How to
d Label Type Lengt y d Use this
h Field

descriptio
n of the
pay grade
than the
short
name can
provide,
enter it
here.

Yes end-date End Date DATE — None No You can

also enter
the date
the pay
grade
stops
being
active.

Yes externalCode Pay Grade STRING 32 Both Yes Define a

ID unique
code by
which the
system
can
distinguis
h the
different
pay
grades
from
Standar Field ID Field Data Max. Visibilit Require How to
d Label Type Lengt y d Use this
h Field

each
other.

Yes name Name STRING 90 Both No You can

enter a
short
name for
the pay
grade.

Yes paygradeLev Pay Grade LONG — Both No You can

el Level use this
field to
enter the
level of
the
relevant
pay
grade.
For
example,
level 1
for a new
starter.

Yes start-date Start Date DATE — Both Yes Enter the

date the
pay grade
becomes
active.

Yes status Status STRING — Both Yes Possible

 Standar Field ID Field Data Max. Visibilit Require How to
d Label Type Lengt y d Use this
h Field

values
are
Active
and
Inactive.
Do not
configure
this as a
picklist.

No custom- Custom STRING 256 None No You can

string1–20 Strings 1– use these
20 fields for
data not
No custom- Custom DATE — None No covered
date1–10 Dates 1– by the
10 fields
supplied
No custom- Customer LONG — None No
as
long1–20 Numbers
standard.
1–20

No custom- Custom DOUBL — None No

double1–20 Decimals E
1–20
Was this page helpful?

Pay Group
Here is a list of the fields available for this element.
Pay Group is an MDF Generic Object. Use the Configure Object
Definition page to update this object.

generic object id: PayGroup

Stand Field ID Field Label Data Ma Visibi Requ How to Use

ard Type x. lity ired this Field
Len
gth

Yes dataDelimiter DataDelimiter String 32 As No Note

define
This field is
d in
not used
the
by Employee
Confi
Central.
gure
Objec
t
Defini
tion
page.

Yes decimalPoint DecimalPoint String 32 As No Note

define
This field is
d in
not used
the
by Employee
Confi
Central.
gure
Objec
t
Defini
tion
page.

Yes description Description Transla 128 As No If you need a

table define more detailed
Stand Field ID Field Label Data Ma Visibi Requ How to Use
ard Type x. lity ired this Field
Len
gth

d in description of
the the pay group
Confi than the short
gure name can
Objec provide, enter
t it here.
Defini
tion
page.

Yes earliestChange Earliest Date — As No Define the

Date Change Date define earliest date
(for Payroll) d in for which
the payroll
Config relevant
ure changes can
Objec be made for
t an employee
Defini assigned to
tion this pay
page. group.

Yes effectiveStart Start Date Date — As Yes Enter the date

Date define the pay group
d in becomes
the active.
Confi
gure
Objec
t
Defini
tion
Stand Field ID Field Label Data Ma Visibi Requ How to Use
ard Type x. lity ired this Field
Len
gth

page.t
h

Yes effectiveEndD End Date Date — As No You can also

ate define enter a date
d in the pay group
the stops being
Confi active.
gure
Objec
t
Defini
tion
page.

Yes effectiveStatus Status Enum — As Yes Possible

define values are
d in Active and
the Inactive. Do
Confi not configure
gure this as a
Objec picklist.
t
Defini
tion
page.

Yes externalCode Pay Group ID String 32 As Yes Define a

define
unique code
d in
the by which the
Stand Field ID Field Label Data Ma Visibi Requ How to Use
ard Type x. lity ired this Field
Len
gth

Config system can

ure
distinguish
Objec
t the different
Defini pay groups
tion from each
page. other.

Yes lag Lag Numbe — As No Indicates the

r define number of
d in pay periods
the that the
Confi employee is
gure paid in
Objec arrears. If the
t employee is
Defini paid current,
tion set the lag to
page. 0. This
information is
stored
in Employee
Central to be
transmitted to
payroll.

Yes name Name Transla 90 As No You can enter

table define a short name
d in for the pay
the group.
Confi
Stand Field ID Field Label Data Ma Visibi Requ How to Use
ard Type x. lity ired this Field
Len
gth

gure
Objec
t
Defini
tion
page.

Yes paymentFrequ Payment Founda 38 As No Specify how

encyFO Frequency tion often a pay
define
Object group is paid.
d in
the
Confi
gure
Objec
t
Defini
tion
page.

Yes paymentFrequ PayFrequency Picklist 32 As No Specify how

ency define often a pay
d in group is paid.
the
Note
Confi
gure This field is
Objec obsolete. Use
t the new
Defini paymentFreq
tion uencyFO
page. field.
Stand Field ID Field Label Data Ma Visibi Requ How to Use
ard Type x. lity ired this Field
Len
gth

Yes payrollVendor PayrollVendor String 32 As No If your

Id ID define company uses
d in an external
the contractor to
Confi process its
gure payroll, enter
Objec the
t contractor's
Defini ID here.
tion
page.

Yes primaryContac PrimaryContac String 256 As No You can enter

tEmail tEmail define an e-mail
d in address for
the the group's
Confi main contact.
gure
Objec
t
Defini
tion
page.

Yes primaryContac PrimaryContac String 256 As No You can enter

tId tID define the identifier
d in of the main
the contact for
Confi this group.
gure
Stand Field ID Field Label Data Ma Visibi Requ How to Use
ard Type x. lity ired this Field
Len
gth

Objec
t
Defini
tion
page.

Yes primaryContac PrimaryContac String 256 As No You can enter

tName tName define the name of
d in the group's
the main contact.
Confi
gure
Objec
t
Defini
tion
page.

Yes secondaryCont SecondaryCon String 256 As No You can enter

actEmail tactEmail define an e-mail
d in address for
the the group's
Confi secondary
gure contact.
Objec
t
Defini
tion
page.
Stand Field ID Field Label Data Ma Visibi Requ How to Use
ard Type x. lity ired this Field
Len
gth

Yes secondaryCont SecondaryCon String 256 As No Enter the

actId tactID define identifier of
d in the secondary
the contact for
Confi this group.
gure
Objec
t
Defini
tion
page.

Yes secondaryCont SecondaryCon String 256 As No You can enter

actName tactName define the name of
d in the group's
the secondary
Confi contact.
gure
Objec
t
Defini
tion
page.

Yes weeksInPayPe WeeksInPayPe Numbe — As No You can

riod riod r define specify how
d in many weeks a
the pay period for
Confi this group
gure should last.
 Stand Field ID Field Label Data Ma Visibi Requ How to Use
ard Type x. lity ired this Field
Len
gth

Objec
t
Defini
tion
page.
Was this page helpful?

Pay Range
Here is a list of the fields available for this element.

hris-element id: payRange

Standa Field ID Field Data Type Max. Visibili Requir How to

rd Label Lengt ty ed Use this
h Field

Yes currency Currency CURREN 256 Both No You can

CY specify the
currency in
which the
pay range
is
indicated.

Yes description Descripti STRING 128 Both No If you need

on a more
detailed
description
Standa Field ID Field Data Type Max. Visibili Requir How to
rd Label Lengt ty ed Use this
h Field

of the pay
range than
the short
name can
provide,
enter it
here.

Yes end-date End Date DATE — None No This is the

end date
the
previous
pay range
stops being
effective.
The
system
calculates
the end
date
automatica
lly
depending
on the start
date
entered.

Yes externalCod Pay STRING 32 Both Yes Define a

e Range ID unique
code by
which the
Standa Field ID Field Data Type Max. Visibili Requir How to
rd Label Lengt ty ed Use this
h Field

system can
distinguish
the
different
pay ranges
from each
other.

Yes frequencyC Frequenc STRING — Both Yes Define

ode y how often
a pay
component
is paid —
for
example,
annually.

The list of
values
comes
from the
frequency
foundation
object.

Yes maximumPa Maximu DOUBLE — Both No Enter the

y m Pay maximum
pay for this
pay range,
for
example:
80,000.
Standa Field ID Field Data Type Max. Visibili Requir How to
rd Label Lengt ty ed Use this
h Field

Yes midPoint Mid DOUBLE — Both No Enter the

Point mid point
for this pay
range that
lies
between
the
minimum
and the
maximum
pay, for
example:
75,000.

Yes minimumPa Minimu DOUBLE — Both No Enter the

y m Pay minimum
pay for this
pay range,
for
example:
70,000.

Yes name Name STRING 90 Both No You can

enter a
short name
for the pay
range.

Yes start-date Start DATE — Both Yes Enter the

Date date the
pay range
 Standa Field ID Field Data Type Max. Visibili Requir How to
rd Label Lengt ty ed Use this
h Field

becomes
effective.

Yes status Status STRING — Both Yes Possible

values are
Active and
Inactive.
Do not
configure
this as a
picklist.

Yes custom- Custom STRING 256 None No You can

string1–20 Strings use these
1–20 fields for
data not
Yes custom- Custom DATE — None No covered by
date1–10 Dates 1– the fields
10 supplied as
standard.
Yes custom- Customer LONG — None No
long1–20 Numbers
1–20

Yes custom- Custom DOUBLE — None No

double1–20 Decimals
1–20
Was this page helpful?

Other Objects A-Z

Dynamic Role Assignment
Here is a list of the fields available for this element.

hris-element id: dynamicRoleAssignment

Standa Field ID Field Data Max. Visibil Requir How to Use this
rd Label Type Leng ity ed Field
th

Yes business Business STRI — Both No The list of values

Unit Unit NG comes from the
business unit
foundation objects
that are available in
the system.

Yes company Legal STRI — Both No The list of values

Entity NG comes from the
legal entity
foundation objects
that are available in
the system.

If you don't need

this field, you can
set the visibility
to “none”.

Yes costCente Cost STRI — Both No The list of values

r Center NG comes from the cost
center foundation
objects that are
available in the
system.
Standa Field ID Field Data Max. Visibil Requir How to Use this
rd Label Type Leng ity ed Field
th

If you don't need

this field, you can
set the visibility
to “none”.

Yes departme Departme STRI — Both No The list of values

nt nt NG comes from the
department
foundation objects
that are available in
the system.

If you don't need

this field, you can
set the visibility
to “none”.

Yes jobCode Job STRI — Both No The list of values

Classifica NG comes from the job
tion classification
foundation objects
that are available in
the system.

If you don't need

this field, you can
set the visibility
to “none”.

Yes location Location STRI — Both No The list of values

NG comes from the
Standa Field ID Field Data Max. Visibil Requir How to Use this
rd Label Type Leng ity ed Field
th

location foundation
objects that are
available in the
system.

If you don't need

this field, you can
set the visibility
to “none”.

Yes payGrade Pay STRI — Both No The list of values

Grade NG comes from the pay
grade foundation
objects that are
available in the
system.

If you don't need

this field, you can
set the visibility
to “none”.

Yes payGroup Pay STRI — Both No The list of values

Group NG comes from the pay
group foundation
objects that are
available in the
system.

If you don't need

this field, you can
set the visibility
Standa Field ID Field Data Max. Visibil Requir How to Use this
rd Label Type Leng ity ed Field
th

to “none”.

Yes person Approver STRI — Both No Depending on what

NG you have selected in
the resolverTyp
e field, you can
either select a
dynamic group here,
a position, or a
specific person as
workflow approver.
For the person, the
list of values comes
from the users that
have been created in
the system.

Yes resolverT Approver STRI — Both Yes In this field, you

ype Type NG define who should
approve the
workflow request.
The possible values
are:

 Person

 Dynamic
Group

 Position (if
Position
Management
 Standa Field ID Field Data Max. Visibil Requir How to Use this
rd Label Type Leng ity ed Field
th

is enabled)

This field is always

mandatory and
visible; you can only
change the label.
Was this page helpful?

Dynamic Role
Here is a list of the fields available for this element.

hris-element id: DynamicRole

Standar Field ID Field Data Max. Visibilit Require How to

d Label Type Lengt y d Use this
h Field

Yes description Descriptio STRING 128 Both No If you

n need a
more
detailed
descriptio
n of the
dynamic
role than
the short
name can
provide,
enter it
Standar Field ID Field Data Max. Visibilit Require How to
d Label Type Lengt y d Use this
h Field

here.

Yes externalCod Code STRING 32 Both Yes Define a

e unique
code by
which the
system
can
distinguis
h the
different
dynamic
roles
from each
other.

Yes name Name STRING 90 Both No You can

enter a
short
name for
the
dynamic
role.

No custom- Custom STRING 256 None No You can

string1–20 Strings 1– use these
20 fields for
data not
No custom- Custom DATE — None No covered
date1–10 Dates 1– by the
10
 Standar Field ID Field Data Max. Visibilit Require How to
d Label Type Lengt y d Use this
h Field

No custom- Customer LONG — None No

long1–20 Numbers
1–20

No custom- Custom DOUBL — None No fields

double1–20 Decimals E supplied as
1–20 standard.
Was this page helpful?

Event Reason
Here is a list of the fields available for this element.

hris-element id: eventReason

Stand Field ID Field Data Max Visibi Requi How to Use this Field
ard Label Type . lity red
Len
gth

Yes descripti Descrip STRI 128 Both No If you need a more

on tion NG detailed description of
the event reason than the
short name can provide,
enter it here.

Yes emplStat EmplSt STRI 45 None No You can use this field to
us atus NG enter the change in
status that is causing the
relevant event. Example:
“Termination” if the
Stand Field ID Field Data Max Visibi Requi How to Use this Field
ard Label Type . lity red
Len
gth

relevant employee has

left the company.

Yes end-date End DATE — None No You can also enter the
Date date the event reason
stops being active.

Yes event Event STRI 45 Both Yes Use this field to describe
NG the event covered by this
event reason.

Yes external Code STRI 32 Both Yes Define a unique code by

Code NG which the system can
distinguish the different
event reasons from each
other.

Yes implicit- Follow- STRI 32 None No You can use this field to
position- Up NG specify which event
action Activity reasons trigger a follow-
in up activity on the
Position assigned position, such
as reclassification or
transfer.

This field is relevant

when you have activated
Position Management.
The list of values comes
from the predefined
picklist positionAct
Stand Field ID Field Data Max Visibi Requi How to Use this Field
ard Label Type . lity red
Len
gth

ionType.

Yes inside- Display STRI 256 Both No You can define which
work- in NG event reason should be
experien Internal displayed in the Internal
ce Job Job History block in the
History Employee Profile.

Yes name STRI 90 Both No You can enter a short

NG name for the event
reason.

Yes payroll- Payroll STRI 4 Both No This field is required for

event Event NG payroll integration with
SAP ERP. It is used to
store additional events to
those delivered by SAP
SuccessFactors. Leave
the maximum length to
4. For more information,
refer to the Employee
Central
Payroll Implementation
Guide.

Yes start-date Start DATE — Both Yes Enter the date the event
Date reason becomes active.

Yes status Status STRI — Both Yes Possible values are

NG Active and Inactive. Do
 Stand Field ID Field Data Max Visibi Requi How to Use this Field
ard Label Type . lity red
Len
gth

not configure this as a

picklist.

No custom- Custom STRI 256 None No You can use these fields
string1– Strings NG for data not covered by
20 1–20 the fields supplied as
standard.
No custom- Custom DATE — None No
date1–10 Dates
1–10

No custom- Custom LONG — None No

long1–20 er
Number
s 1–20

No custom- Custom DOUB — None No

double1– Decima LE
20 ls 1–20
Was this page helpful?

WfConfig
Here is a list of the fields available for this element.

hris-element id: wfConfig

Standa Field ID Field Data Max. Visibili Requir How to Use
rd Label Type Lengt ty ed this Field
h

Yes description Descripti STRING 128 Both No If you need a

on more
detailed
description
of the
WFConfig
than the short
name can
provide,
enter it here.

Yes escalation Escalatio Generic — Both No You can use

n Object this for the
auto-
escalation
feature based
on the
Escalation
MDF object.

Yes externalCo Code STRING 32 Both Yes Define a

de unique code
by which the
system can
distinguish
the different
workflow
configuration
s from each
other.
Standa Field ID Field Data Max. Visibili Requir How to Use
rd Label Type Lengt ty ed this Field
h

Yes future- Alternate STRING — Both No See note

for future-
dated- Workflo
dated-
alternate- w alternate-
workflow workflow a
fter table.

Yes is-cc-link- Redirect BOOLE — Both No See note

to- CC Users AN for is-cc-
approval- to link-to-
page Workflo approval-
w page below
Approval table.
Page

Yes is- Is BOOLE — Both No See note

for is-
delegate- Delegate AN
delegate-
supported Supporte supported a
d fter table.

Yes name Name STRING 90 Both No You can

enter a short
name for this
WfConfig.

Yes remind- Remind LONG — Both No See note

for remind-
indays in Days
indays after
table.

Yes custom- Custom STRING 256 None No You can use

string1–20 Strings these fields
 Standa Field ID Field Data Max. Visibili Requir How to Use
rd Label Type Lengt ty ed this Field
h

1–20 for data not

covered by
Yes custom- Custom DATE — None No the fields
date1–10 Dates 1– supplied as
10 standard.

Yes custom- Customer LONG — None No

long1–20 Numbers
1–20

Yes custom- Custom DOUBL — None No

double1– Decimals E
20 1–20

Note for: remind-in-days

This field is relevant when you set up reminder notifications with individual
time spans for different workflow foundation objects. Enter the number of
days after which the workflow approver is reminded to take action on a
pending workflow.

Note that if you set up the time span for reminder notifications at quartz job
level, you do not need to set up this field in the Corporate Data Model as the
system will ignore any entries made in this field.

Note for: is-delegate-supported

Select Yes to enable manual delegation or auto delegation of workflows.

For auto delegation, all incoming workflow requests are automatically

redirected to the delegate the user has selected in the My Info tile. For
manual delegation, the approver can delegate the current workflow request
for the current workflow step to any system user. The approver can revoke
this delegation later. If the delegate declines the delegation, the workflow
request is assigned back to the approver.

Note: This field is only supported when the workflow step approver type
is Role and approver is configured with Employee, Employee
Manager, Employee Manager Manager, or Employee HR. It is not
applicable when the workflow step is configured with multiple approver roles,
such as dynamic role, dynamic group or job relationship type roles (matrix
manager, custom manager, second manager and additional manager).

Note for: future-dated-alternate-workflow

You can configure an alternate workflow that is used for future-dated

records; if there are no future-dated records, or if this field has an invalid
value, the main workflow is used. The list of values contains the workflow
foundation objects defined in the system.

Note for: is-cc-link-to-approval-page

When a workflow is completed, CC users are informed by e-mail or

notification that contains a link. This field defines to which page this link
leads to.

If you select Yes, the link leads the CC users to the workflow approval page.
If you select No, the link leads the CC users to the Employment
Information page.

Was this page helpful?

wfConfig Contributor
Here is a list of the fields available for this element.

hris-element id: wfConfigContributor

Standa Field ID Field Data Max. Visibili Requir How to Use
rd Label Type Lengt ty ed this Field
h

Yes actorRole Contribut STRIN — Both Yes Select one of

or G the following
contributors:

 Employ
ee

 Employ
ee
Manag
er

 Employ
ee
Manag
er
Manag
er

 Employ
ee HR

 Matrix
Manag
er

 Custom
Manag
er

 Second
Manag
er
Standa Field ID Field Data Max. Visibili Requir How to Use
rd Label Type Lengt ty ed this Field
h

 Additio
nal
Manag
er

Yes actorType Contribut STRIN 32 Both Yes Select one of

or Type G the following
contributor
types:

 Role

 Dynam
ic Role

 Dynam
ic
Group

 Person

 Positio
n

No context Context STRIN 32 Both No When the

G transaction that
requires an
approval
implies a
manager
change, the
Standa Field ID Field Data Max. Visibili Requir How to Use
rd Label Type Lengt ty ed this Field
h

context allows
you to
determine
which manager
has to approve:

 Source
(the
initial
manage
r)

 Target
(the
new
manage
r)

No description Descripti STRIN 128 Both No If you need a

on G more detailed
description of
the WFConfig
Contributor
than the short
name can
provide, enter
it here.

No externalCo Code STRIN 32 Both Yes Define a

de G unique code by
which the
 Standa Field ID Field Data Max. Visibili Requir How to Use
rd Label Type Lengt ty ed this Field
h

system can
distinguish the
different config
contributors
from each
other.

No name Name STRIN 90 Both No You can enter a

G short name for
this config
contributor.
Was this page helpful?

wfConfig CC
Here is a list of the fields available for this element.

hris-element id: wfConfigCC

Standa Field ID Field Data Max. Visibili Requir How to Use

rd Label Type Lengt ty ed this Field
h

Yes actorRole CC Role STRIN — Both Yes Select one of

G the following
CC roles:

 Employ
ee

 Employ
Standa Field ID Field Data Max. Visibili Requir How to Use
rd Label Type Lengt ty ed this Field
h

ee
Manag
er

 Employ
ee
Manag
er
Manag
er

 Employ
ee HR

 Matrix
Manag
er

 Custom
Manag
er

 Second
Manag
er

 Additio
nal
Manag
er

Yes actorType CC Role STRIN 32 Both Yes Select one of

Standa Field ID Field Data Max. Visibili Requir How to Use
rd Label Type Lengt ty ed this Field
h

Type G the following

CC role types:

 Role

 Dynam
ic Role

 Dynam
ic
Group

 Person

 Externa
l Email

 Positio
n

No context Context STRIN 32 Both No When the

G transaction that
requires an
approval
implies a
manager
change, the
context allows
you to
determine
which manager
has to approve:
Standa Field ID Field Data Max. Visibili Requir How to Use
rd Label Type Lengt ty ed this Field
h

 Source
(the
initial
manage
r)

 Target
(the
new
manage
r)

No description Descripti STRIN 128 Both No If you need a

on G more detailed
description of
the CC Role
than the short
name can
provide, enter
it here.

No externalCo Code STRIN 32 Both Yes Define a

de G unique code by
which the
system can
distinguish the
different CC
Roles from
each other.
 Standa Field ID Field Data Max. Visibili Requir How to Use
rd Label Type Lengt ty ed this Field
h

No name Name STRIN 90 Both No You can enter a

G short name for
this CC Role.
Was this page helpful?

wf Step Approver
Here is a list of the fields available for this element.

hris-element id: wfStepApprover

Standa Field ID Field Data Max. Visibili Requir How to Use

rd Label Type Lengt ty ed this Field
h

Yes actionType Edit STRIN 256 None No See note for

actionType
Transacti G below.
on

Yes approverRo Approver STRIN — Both Yes Select one of

le Role G the following
approver roles:

 Emplo
yee

 Emplo
yee
Manag
er

 Emplo
Standa Field ID Field Data Max. Visibili Requir How to Use
rd Label Type Lengt ty ed this Field
h

yee
Manag
er
Manag
er

 Emplo
yee HR

 Matrix
Manag
er

 Custom
Manag
er

 Second
Manag
er

 Additio
nal
Manag
er

Yes approverTy Approver STRIN 32 Both No Select one of

pe Type G the following
approver types:

 Role
Standa Field ID Field Data Max. Visibili Requir How to Use
rd Label Type Lengt ty ed this Field
h

 Dynam
ic Role

 Dynam
ic
Group

 Positio
n

Yes context Context STRIN 32 Both No When the

G transaction that
requires an
approval
implies a
manager
change, the
context allows
you to
determine
which manager
has to approve:

 Source
(the
initial
manage
r)

 Target
(the
 Standa Field ID Field Data Max. Visibili Requir How to Use
rd Label Type Lengt ty ed this Field
h

new
manage
r)

Yes skipType No String 32 Both No See note for

Approver SkipType
Behavior below.

Note for actionType

When you create a new workflow, you have to define if the workflow step
approver can edit the submitted workflow. The options are:

 No Edit: The approver cannot edit an already submitted workflow.

This is the standard option for an approver.

 Edit with Route Change: The approver can edit an already

submitted workflow. The edited workflow will then go through the
approval process again from the beginning.

 Edit without Route Change: The approver can edit an already

submitted workflow. The edited workflow will then continue with the
next step approver.

Note for skipType:

Define how the system should react when there is an empty position or
dynamic group:

 Stop the Workflow Workflow step is considered as mandatory step.

 Skip this Step Workflow step is skipped. This is the default system
behavior
Both options are applied when:

1. Workflow step approver is not assigned in case of Role, and Dynamic

Role with person resolver type.

2. Workflow step position has no incumbents in case of Position.

3. Workflow step dynamic group has no members in case of Dynamic

Group.

4. Workflow step dynamic role is assigned to an empty position or an

empty dynamic group.

Was this page helpful?

Person Object Tables

The tables in the list below give you the technical information about the
person objects and their fields that are relevant for Employee Central.

You can define these in the Succession Data Model and the country/region-
specific Succession Data Model with the XML file or Manage Business
Configuration tool. You can find more information on these data models in
the Setting Up the Succession Data Model and Setting up
Country/Region-Specific Data Models sections of the Implemening
Employee Central Core guide.

Note

Beware that hiding all fields in a block using a business rule is not supported
and will potentially cause unexpected behavior in the system. You must have
at least one field on this object enabled to avoid inconsistent behavior.

When you refer to the following tables, consider the following:

 The standard XML file for the data models contains only a subset of
these fields, but you can use all the fields listed in these tables, for
example, to override default attributes.
  Those fields listed in the tables, but not in the Succession Data Model,
still appear on the UI if their default visibility is set to “both”. If you
want to hide those fields, add them to the corresponding data model
and set the visibility to “none”.
 For start-date, end-date, event-reason and event-reason-code,
you cannot change the default visibility. That means even if you
change the visibility in the XML file for the Succession Data Model, the
system ignores this and the default visibility as listed in these tables is
considered.
 Fields listed in the standard XML files, but not in these tables, are not
relevant for Employee Central 2.0. You should leave their visibility
to “none”. Exceptions to this rule are customer-specific fields that you
can use as needed.

Related Information
Addresses

Biographical Information

Dependents

Email

Emergency Contact

Global Information

National ID Information

Personal Information

Phone Information

Social Accounts

Work Permit Info

Direct Deposit

Was this page helpful?

Addresses
Here is a list of the fields available for this element.

Addresses (hris-element-
id: homeAddress)
The fields of this element are defined in the country/region-specific
Succession Data Model.

Hide/Show Columns


 Standard Field ID Fie

Filter: [No Selection]

Standard Field ID Field Data Max. Default Is How To Use This Field
Label Type Lengt Visibility Required?
h

Yes item-id Item ID LONG None No This field is used for

internal purposes.
Do not use it in the data
model. Even if it is used, it
won't be visible on the UI.

No address- Address STRING 30 None No Do not configure this field

type Type
in the data model as some
other data type.

The list of values comes

from the
picklist addressType.
The preconfigured list of
values contains the
following:
 Standard Field ID Fie

Filter: [No Selection]

Standard Field ID Field Data Max. Default Is How To Use This Field
Label Type Lengt Visibility Required?
h

 Home
 Mailing
 Benefits
 Payroll

You can add more values

to the
picklist addressType by
exporting and importing
the picklist using the
admin tools.

Yes address1- Address STRING 256 Both No You can enter 25 lines for
25 1–25 address here.

Yes city City STRING 256 Both No This is where you enter the
 Standard Field ID Fie

Filter: [No Selection]

Standard Field ID Field Data Max. Default Is How To Use This Field
Label Type Lengt Visibility Required?
h

city or town the employee

lives in.

Yes county County STRING 256 Both No This is where you enter the
county the employee lives
in.

Yes state State STRING 256 Both No This is where you enter the
state the employee lives
in.

No province Province STRING 256 Both No This is where you enter the
province the employee
lives in.

Yes zip-code Zip Code STRING 256 Both No This is where you enter the
ZIP code of the place the
 Standard Field ID Fie

Filter: [No Selection]

Standard Field ID Field Data Max. Default Is How To Use This Field
Label Type Lengt Visibility Required?
h

employee lives in.

Yes country Country STRING 256 Both Yes The list of values comes
from the predefined
picklist <country>.

Note

You must not configure

any picklist or child
picklist for
the <country> field, as this
field is hard-coded in the
system.

If you want to define

country/region-specific
 Standard Field ID Fie

Filter: [No Selection]

Standard Field ID Field Data Max. Default Is How To Use This Field
Label Type Lengt Visibility Required?
h

addresses, configure the

fields for the
corresponding country or
region in
the homeAddress HRIS
element in the
country/region-specific
Succession Data Model.

No address1– Alt1 STRING 256 None No You can enter 25 lines for
alt1 (lines Address1
the address in alternate
1–25)
languages here, for
example, the employee's
native languages.

Address information can

 Standard Field ID Fie

Filter: [No Selection]

Standard Field ID Field Data Max. Default Is How To Use This Field
Label Type Lengt Visibility Required?
h

be displayed in up to two
alternate language fields. A
link to the alternate
language fields is
displayed in "Edit" mode,
and the non-alternate
language fields are already
filled with the home
address information that
has been entered before.

Page Size:

10





Showing 10 of 42

 Previous
 1
 2
 3
 ...
 5
 Next

Alternate Fields
Two sets of alternate languages are supported for Addresses. Alternate fields
can be enabled in the Succession Data Model rather than in the
Country/Region-Specific Data Model. Country/Region-Specific settings would
be ignored for alternate fields. Each alternate field represents some existing
parent field in the element model in alternate script. The alternate fields take
the visibility and permission from the parent fields. If any of the alternate
fields have entries, they can be displayed on the screen. However, in edit
mode, these fields are automatically hidden.

On this page

 Addresses (hris-element-id: homeAddress)

 Alternate Fields

Was this page helpful?

Biographical Information
Here is a list of the fields available for this element.
Biographical Information (hris-
element-id: personInfo)
Hide/Show Columns


 Standard Field ID

Filter: [No Selection]

Standar Field ID Field Label Data Type Max. Default Is How To Use This Field
d Lengt Visibility Required?
h

Yes attachment- Attachments LONG Both No If the biographical

id info of an employee
has a document such
as birth certificate,
this can be uploaded
in this field.

Yes birth-name Birth Name STRING 128 Both No You can enter the
employee's birth
name here, for
example: Smith.

This field is required

if you use payroll
integration with SAP
 Standard Field ID

Filter: [No Selection]

Standar Field ID Field Label Data Type Max. Default Is How To Use This Field
d Lengt Visibility Required?
h

ERP.

Note: If you have

specified a formal
name format (using a
birth-name) for your
legal entity and want
to replicate to SAP
ERP, leave this field
in hris-element-id:
personlInfo empty
and specify the birth-
name in the hris-
element-id:
personalInfo instead
 Standard Field ID

Filter: [No Selection]

Standar Field ID Field Label Data Type Max. Default Is How To Use This Field
d Lengt Visibility Required?
h

Yes country-of- Country/Region COUNTRY 100 Both No You can enter the
birth Of Birth
employee's country
of birth here.

By default, the list of

values come from the
predefined MDF
object
"Country/Region".

Yes date-of- Date Of Birth DATE Both No You can enter the
birth employee's date of
birth here.
 Standard Field ID

Filter: [No Selection]

Standar Field ID Field Label Data Type Max. Default Is How To Use This Field
d Lengt Visibility Required?
h

Yes date-of- Date Of Death DATE None No You can enter the
death employee's date of
death here.

Yes person-id- Person Id STRING 32 Both No This field contains

external the employee ID. You
can manually assign
employee IDs or
have system-
generated IDs. When
you use system-
generated IDs, set
the visibility
to “view” and add
the
attribute allow-
import=”true”.
 Standard Field ID

Filter: [No Selection]

Standar Field ID Field Label Data Type Max. Default Is How To Use This Field
d Lengt Visibility Required?
h

Yes place-of- Place Of Birth STRING 100 Both No You can enter the
birth
town the employee
was born, for
example: Chicago.

This field is required

if you use payroll
integration with SAP
ERP.

Yes region-of- Region Of Birth STRING 100 Both No You can enter the
birth administrative
district where the
employee was born.
This is a free text
field.
 Standard Field ID

Filter: [No Selection]

Standar Field ID Field Label Data Type Max. Default Is How To Use This Field
d Lengt Visibility Required?
h

Note

The behavior of this

field changes when
payroll integration is
enabled in your
instance. The system
will dynamically
change the field
behavior based on the
value given in
the <country of
birth> field. Also,
depending on
the <country of
 Standard Field ID

Filter: [No Selection]

Standar Field ID Field Label Data Type Max. Default Is How To Use This Field
d Lengt Visibility Required?
h

employment>, this
field may be made
mandatory. For more
information, refer to
the end of this
document.

Yes per-person- Person UUID STRING 32 None No This field contains a

uuid
unique identifier of
employees or their
dependents, which
you can use to
integrate Person Data
with other modules
like Onboarding,
 Standard Field ID

Filter: [No Selection]

Standar Field ID Field Label Data Type Max. Default Is How To Use This Field
d Lengt Visibility Required?
h

Learning, Recruiting,
Talent, and so on.
You can manually
assign a value or
have system-
generated IDs.

To use with data

imports, set the
visibility
to “view” and add
the
attribute allow-
import=”true”.
 Standard Field ID

Filter: [No Selection]

Standar Field ID Field Label Data Type Max. Default Is How To Use This Field
d Lengt Visibility Required?
h

Note

Once this field is

populated with a
value, it cannot be
changed.

No custom- Custom Strings STRING 256 None No You can use this field
string1–20 1–20 for data not covered
by the standard
fields.

Page Size:

10



Showing 10 of 13

 Previous
 1
 2
 Next

Region of Birth
When payroll integration is enabled, the system may dynamically change
region of birth field and override the data model configuration. The following
is a list of areas or countries affected by the behavior changes.

Provisioning

The dynamic behavior of the <region-of-birth> field will be activated only

when the instance the Enabled Payroll Integration or Enable Employee
Central Payroll feature is switched on in Provisioning.

Remember

As a customer, you don't have access to Provisioning. To complete tasks

in Provisioning, contact your implementation partner or Account Executive.
For any non-implementation tasks, contact Product Support.
Countries Supported
 Country If Country of If Picklist ID used
(Country Employment Country
Code) matches, of Birth
convert field matches,
to convert
mandatory? field to a
picklist
field?

Italy (ITA) Yes Yes PROVINCE_ITA

France Yes Yes DEPARTMENT_FRA

(FRA)

Venezuela Yes Yes REGION_VEN

(VEN)

Brazil No Yes STATE_BRA

(BRA)

Chile No Yes REGION_CHL

(CHL)

Mandatory or Not

Italy France Venezuela Brazil Chile Other

region-of- True True True Value Value Value

birth is in data in in
mandatory model data data
value = model model
 Picklist or Not

Italy France Venezuel Brazil Chile Other

a

region-of-birth is picklist True True True True True Value in data

value = model

If no picklist ID is mentioned in the data model, then whenever the <country

of birth> chosen is any of the five countries, the region-of-birth field will be
converted to a picklist field with corresponding picklist ID (which is different
for each of the five countries). For other countries, the field will remain as a
free text. If a picklist ID is mentioned in the data model, then the region-of-
birth field will always be a picklist field irrespective of the value in country of
birth. The picklist ID will also remain same as the one mentioned in the data
model.

Imports

When importing values, ensure that the correct values are filled out in the template.

 If the <region of birth> field has been assigned a picklist in the data
model, then the standard procedure for working with fields with picklist
assignment must be followed while filling the import file

 If the field does not have any picklist assigned to it in the data model, then

 If payroll integration is activated and <country of birth> is one of

the five countries mentioned earlier, then use the external code
of the corresponding picklist value while filling the import file
 Otherwise, you need to use free text while filling the import file

Current Behavior

 The picklist IDs are hard-coded in the system. They cannot be

changed!
  The behavior is based on the current active effective-dated Job Information
record. So, the behavior can change for a user who has multiple job
information records when the country of employment changes.

 This works only on Employee Profile page, and only for the employees, not
their dependents.

 Does not work in the New Hire process.

 Does not work for future hires since this is based on the current active
job information record.
 You must enter a country of birth for the country of employment - you
cannot leave it empty.

On this page

 Biographical Information (hris-element-id: personInfo)

 Region of Birth

Was this page helpful?

Dependents
Here is a list of the fields available for this element.

Dependents (hris-element-
id: personRelationshipInfo)
Hide/Show Columns



 

Standard Field ID

Filter: [No Selection]

Standar Field ID Field Label Data Type Max. Default Is How To Use This
d Lengt Visibilit Required
h y ?

Yes item-id Item ID LONG None No This field is used for intern
purposes. Do not use it in
model. Even if it is used, i
visible on the UI.

Yes attachment-id Attachments LONG No No If the dependent of an emp

document such as birth cer
this can be uploaded using

Yes is- Accompanyi BOOLEA Both No When you add a global ass
accompanyin ng N
g-dependent you can select this field in
the Dependents block to d
 Standard Field ID

Filter: [No Selection]

Standar Field ID Field Label Data Type Max. Default Is How To Use This
d Lengt Visibilit Required
h y ?

a dependent joins the empl

the global assignment.

Possible values are Yes an

You must have activated G

Assignments in the Admin

Yes is-address- Copy BOOLEA 3 Both No If the address of an employ

same-as- Address from N dependent is the same as th
person Employee employee’s address, you c
select Yes to copy the add
information for the depend
employee's address subseq
changes, this change is not
in the dependent's address
information unless you
select Yes again.
 Standard Field ID

Filter: [No Selection]

Standar Field ID Field Label Data Type Max. Default Is How To Use This
d Lengt Visibilit Required
h y ?

Note
With Centralized services
employee addresses aren't
dependents if any incorrec
address information is fou

Yes is-beneficiary Is BOOLEA Both No When you add pension pay

Beneficiary N
can select this field to dete
whether a dependent is the
beneficiary of an employe
payout in the event of that
death. Possible values
are Yes and No.

You must have activated P

 Standard Field ID

Filter: [No Selection]

Standar Field ID Field Label Data Type Max. Default Is How To Use This
d Lengt Visibilit Required
h y ?

Payouts.

Yes relationship- Relationship STRING 50 Both Yes You have to define the rela
type
the dependent to the emplo

The list of values comes fr

picklist personRelatio
ype. Possible values are:

 Child

 Stepchild

 Child of Domestic
 Standard Field ID

Filter: [No Selection]

Standar Field ID Field Label Data Type Max. Default Is How To Use This
d Lengt Visibilit Required
h y ?

 Spouse

 Registered Partner

 Divorced Spouse

 Father

 Mother

 Brother

 Sister

 Related Persons
 Standard Field ID

Filter: [No Selection]

Standar Field ID Field Label Data Type Max. Default Is How To Use This
d Lengt Visibilit Required
h y ?

 Domestic Partner

No related- Related STRING None No This field represents the pe

person-id- Person Id
external External external of a dependent.

This field is invisible on th

only used in import templa
adding and updating data f
dependents.

The system generated rela

Ids external follow this
pattern: <employee's
ID>_d<sequence num
 Standard Field ID

Filter: [No Selection]

Standar Field ID Field Label Data Type Max. Default Is How To Use This
d Lengt Visibilit Required
h y ?

No custom- Custom STRING 256 None No You can use these fields fo
string1–20 Strings 1–20 covered by the fields supp
standard.

No custom- Custom DATE None No You can use these fields fo

date1–20 Dates 1–20 covered by the fields supp
standard.

No custom- Custom LONG None No You can use these fields fo

long1–20 Numbers 1– covered by the fields supp
20 standard.

Page Size:

10



Showing 10 of 11

 Previous
 1
 2
 Next

Was this page helpful?

Email
Here is a list of the fields available for this element.

Email (hris-element-id: emailInfo)

Hide/Show Columns



 Standard Field ID

Filter: [No Selection]

Standar Field ID Field Data Type Max. Default Is How To Use This Field
d Label Lengt Visibility Required?
h

Yes email- Email STRING 100 Both Yes Enter an email address
address Address here.

Yes email- Email STRING 32 Both Yes Enter the type of email
type Type
address. The list of values
comes from the predefined
picklist ecMailType an
d uses the following
values:

 Personal

 Business

Yes isPrimary Is BOOLEAN 1 Both No Indicate if the email

Primary address is the primary one.
Possible values
are Yes and No.
 Standard Field ID

Filter: [No Selection]

Standar Field ID Field Data Type Max. Default Is How To Use This Field
d Label Lengt Visibility Required?
h

No custom- Custom STRING 256 None No You can use this field for
string1– Strings data not covered by the
20 1–20 standard fields.

No custom- Custom DATE None No You can use this field for
date1–10 Dates 1– data not covered by the
10 standard fields.

No custom- Custom LONG None No You can use this field for
long1–20 Numbers data not covered by the
1–20 standard fields.

No custom- Custom DOUBLE None No You can use this field for
double1– Decimals data not covered by the
20 1–20 standard fields.

Showing 7 of 7

Was this page helpful?

 Emergency Contact
Here is a list of the fields available for this element.

Emergency Contact (hris-element-

id: emergencyContactPrimary)

Stand Field ID Field Label Data Ma Defaul Is How To Use This Field
ard Type x. t Requir
Len Visibili ed?
gth ty
Filte Search Search Filter: Fil Sear Filte Search Column
r: [N Column Column [No ter ch r: [No
o Selecti :[ Colu Selecti
Selecti on] No mn on]
on]
Sel
ect
ion
]
Yes isDepende Depende BOOLEA None No Define whether the person
nt nt N
is a dependent of the
employee.
 Possible values
are Yes and No.
Yes isEmergen Emergen BOOLEA None No Define whether the person
cyContact cy N
Contact is an emergency contact of
the employee.

Possible values
are Yes and No.
Yes address Address STRING 10 Both No Enter the address of the
00 contact.
Yes dateOfBirt Date of DATE None No Enter the date of birth of
h Birth the contact.
Yes email eMail STRING 10 None No Enter the email address of
0 the contact person.
Yes ecNameAlt Name in STRING 25 None No Enter the name of the
1 Alternate 6 contact in alternate
Characte languages.
r1
Yes ecNameAlt Name in STRING 25 None No Enter the name of the
2 Alternate 6 contact in alternate
Characte languages.
r2
Yes phone Phone STRING 25 Both No Enter the phone number of
6 the contact person.
Yes second- Second STRING 25 Both No If the contact person has an
phone Phone 6 additional phone number,
you can add it here.
Yes isAddSame Copy BOOLEA None No Indicate whether the
AsEmploye Address N
e from emergency contact has the
Employe same address as the
e employee.

If the value is set to Yes, the

address is copied from the
employee's home address,
even if there are multiple
address types listed for the
employee.
No primary_fla Primary STRING 1 Both No One of the contacts you
g enter in this block must be
the primary emergency
 contact. Possible values
are Yes and No.
Yes gender Gender STRING 2 None No You can define the gender
of the contact here. The list
of values comes from a
predefined picklist.
Yes relationshi Relations STRING 50 Both Yes You can define the
p hip relationship of the contact
person with the employee.
The relationship can be
child, spouse, and so on.
The list of values comes
from the predefined
picklist relation.
Yes name Name STRING Both No You can enter the full name
of the contact person.
Yes isDisabled Disabled BOOLEA None No You can indicate if the
N
dependent is disabled or
not.

Possible values
are Yes and No.
Yes isStudent Student BOOLEA None No You can indicate whether
N
the dependent is a student.

Possible values
are Yes and No.
No custom- Custom STRING 25 None No You can use this field for
string2–20 Strings 6 data not covered by the
2–20 standard fields.
No custom- Custom DATE None No You can use this field for
date1–10 Dates 1– data not covered by the
10 standard fields.
No custom- Custom LONG None No You can use this field for
long1–20 Numbers data not covered by the
1–20 standard fields.
No custom- Custom DOUBL None No You can use this field for data not
double1– Decimals E covered by the standard fields.
20 1–20
Yes custom- Emergen STRING 25 None No You can use this field for
string1 cy 6 data not covered by the
Contact standard fields.
Custom
String 1
 Global Information
Here is a list of the fields available for this element.

Global Information (hris-element-

id: globalInfo)
The fields of this element are defined in the country/region-specific
Succession Data Model

Stand Field ID Field Label Data Ma Defaul Is How To Use This Field
ard Type x. t Requir
Len Visibili ed?
gth ty
Filte Search Search Filter: Fil Sear Filte Search Column
r: [N Column Column [No ter ch r: [No
o Selecti :[ Colu Selecti
Selecti on] No mn on]
 on] Sel
ect
ion
]
No country Country/ COUNT Both Yes The country/region-specific
Region RY
fields shown as global
information depend on the
country you select here.

Note
You must not configure any
picklist or child picklist for
the <country> field, as this
field is hard-coded in the
system.
No end-date End Date DATE None No This is the end date the
previous global information
stops being effective. The
system calculates the end
date automatically
depending on the start date
entered.
Yes attachmen Attachme LONG None No This field is used for
t-id nts employees to upload
documents about
country/region-specific
personal information.
Yes genderCou Gender STRING 25 None No To collect country/region-
ntrySpecifi 6
c specific information related
to genders, enable this field
and define a picklist that
contains the gender options
for a country/region.

The picklist ID must follow

the format of gender_XXX,
where XXX is a 3-letter ISO
country/region code. Picklist
IDs in any other format are
 ignored by the system.

It is recommended to leave
the <Gender> field
in Personal
Information empty if you
choose to edit the
country/region-specific field.

Remember
Predefined picklists of the
country/region-specific
gender field are available
for Germany and India.

See the picklists with

ID gender_DEU and gender_
IND from Employee
Central Master Picklists.
For more information,
see Employee Central
Country/Region Specifics.
Note
All configuration files
for Employee Central, for
example, master data
models, master picklists, as
well as country/region-
specific files, have moved
from the SAP Help Portal to
the Software Download

Center .
No genericStri Generic STRING 25 None No The data covered by these
ng1–30 String 6 fields is country/region-
specific. You can find the
fields defined for the
corresponding
 country/region in the
Country/Region-Specific
Succession Data Model.
These fields are defined
by SAP SuccessFactors; you
can't add your own generic
fields.
No genericDat Generic DATE None No The data covered by these
e1–20 Date fields is country/region-
specific. You can find the
fields defined for the
corresponding
country/region in the
Country/Region-Specific
Succession Data Model.
These fields are defined
by SAP SuccessFactors; you
can't add your own generic
fields.
No genericNu Generic LONG None No The data covered by these
mber1–40 Number fields is country/region-
specific. You can find the
fields defined for the
corresponding
country/region in the
Country/Region-Specific
Succession Data Model.
These fields are defined
by SAP SuccessFactors; you
can't add your own generic
fields.
No custom- Custom STRING 25 None No You can use this field for
string1–30 Strings 6 data not covered by the
1–30 standard fields.
No custom- Custom DATE None No You can use this field for
date1–20 Dates 1– data not covered by the
20 standard fields.
No custom- Custom LONG None No You can use this field for
long1–20 Numbers data not covered by the
1–20 standard fields.
No custom- Custom DOUBL 1 None No You can use this field for
double1– Decimals E data not covered by the
20 1–20 standard fields.

Page Size:
 10


Showing 10 of 11

 Previous
 1
 2
 Next

Related Information
Country/Region Specifics in Employee Central

National ID Information
Here is a list of the fields available for this element.

National ID Info (hris-element-

id: nationalIdCard)
Stand Field ID Field Label Data Ma Defaul Is How To Use This Field
ard Type x. t Requir
Len Visibili ed?
gth ty
Filte Search Search Filter: Fil Sear Filte Search Column
r: [N Column Column [No ter ch r: [No
o Selecti :[ Colu Selecti
Selecti on] No mn on]
on]
Sel
ect
ion
]
Yes attachmen Attachme LONG Both No If the national ID card of an
t-id nts employee has a document
such as passport or other ID
card, this can be uploaded
in this field.
Yes card-type National STRING 25 Both Yes Depending on the
Id Card 6
Type country/region selected, the
corresponding national ID
card type is displayed in
this field, for example:

 Social Security
Number (for USA)
 Social Insurance
Number (for Canada)

Yes country Country/ STRING 10 Both Yes Select the country/region in

Region 0 which the national ID has
been assigned from the list
of countries.
Yes isPrimary Is BOOLEA 1 Both Yes Indicate which national ID is
Primary N the primary one.
Yes national-id National STRING 25 Both No Enter the number of the
ID 6
national ID in the
corresponding format, for
 example:999–999–999

Note
If you allow temporary IDs
in the system, you can set
the national-id field to
optional. Otherwise, you
must set the field to
mandatory.

You set up the

country/region-specific
format in the
Country/Region-Specific
Succession Data Model,
where you also define if the
user input is validated
against a specific format.
Yes isTemporar Temporar BOOLEA 1 None No Indicate that a temporary
y y ID N national ID is available.
Available
Yes temporary- Temporar STRING 25 None No Enter temporary national
id y ID 6 IDs for employees if they
don't have a valid national
ID during the hiring process.
Same as national IDs,
admins should enter the
temporary IDs in the
requested format. There's
no data validation for this
field.
Yes start-date Start 25 Both No Enter the start date of the
Date 6 validity period.
Note
This field has been
deprecated and should no
longer be used.
Yes end-date Both No Enter the start date of the
validity period.
 Note
This field has been
deprecated and should no
longer be used.
Yes notes Note STRING 40 Both No This is a text field where the
00
user can enter additional
information if required.

Note
This field can't be displayed
on the Employee Profile.
Yes cpam-id Cpam ID STRING 25 None No This field is specific to
6 France.
Yes deuev- Deuev STRING 25 None No This field is specific to
code Code 6 Germany.
No custom- Custom STRING 25 None No You can use this field for
string1–20 Strings 6 data not covered by the
1–20 standard fields.
No custom- Custom DATE None No You can use this field for
date1–10 Dates 1– data not covered by the
10 standard fields.
No custom- Custom LONG None No You can use this field for
long1–20 Numbers data not covered by the
1–20 standard fields.
No custom- Custom DOUBL None No You can use this field for
double1– Decimals E data not covered by the
20 1–20 standard fields.

Personal Information
Here is a list of the fields available for this element.

Personal Information (hris-element-

id: personalInfo)
Stand Field ID Field Label Data Ma Defaul Is How To Use This Field
ard Type x. t Requir
Len Visibili ed?
gth ty
Filte Search Search Filter: Fil Sear Filte Search Column
r: [N Column Column [No ter ch r: [No
o Selecti :[ Colu Selecti
Selecti on] No mn on]
on]
Sel
ect
ion
]
Yes aboriginal- Aborigina BOOLEA None No
person l Person N
Yes attachmen Attachme LONG None No
t-id nts

Yes birth- Birth STRING 12 Both No Here you can enter the
name-alt1 Name 8
Alt1 employee's birth name in
an alternate language.

Note
The birth name must first
be enabled to use the
 alternate language fields.
The admin must also be
given permissions for the
alternate language fields.
Yes birth- Birth STRING 12 Both No Here you can enter the
name-alt2 Name 8
Alt2 employee's birth name in
an alternate language.

Note
The birth name must first
be enabled to use the
alternate language fields.
The admin must also be
given permissions for the
alternate language fields.
Yes birth-name Birth STRING 12 Both No Here you can enter the
Name 8
employee's birth name.

This field is required if you

use payroll integration
with SAP ERP.

Note
If you've specified a formal
name format (using a birth-
name) for your legal entity
and want to replicate to SAP
ERP, specify the birth name
in the HRIS
element personalInfo and
leave birth-name field in
the HRIS
element personInfo empty.
Yes bilinguism- Bilinguali STRING 25 None No
code sm Code 6
Yes business- Business STRING 12 None No Here you can enter a
first-name First 8
Name business first name that
 may be needed in some
countries or regions. For
example, if an employee
keeps using an original
name in business after the
official name is changed,
you can enter the original
name as the business
name.
Yes business- Business STRING 12 None No Here you can enter a
last-name Last 8 business last name that
Name may be needed in some
countries or regions. For
example, if an employee
keeps using an original
name in business after the
official name is changed,
you can enter the original
name as the business
name.
Yes business- Business STRING 12 None No Here you can enter a
first-name- First 8 business first name in an
alt1 Name alternate language that
Alt1 may be needed in some
countries or regions.
Yes business- Business STRING 12 None No Here you can enter a
last-name- Last 8 business last name in an
alt1 Name alternate language that
Alt1 may be needed in some
countries or regions.
Yes business- Business STRING 12 None No Here you can enter a
first-name- First 8 business first name in an
alt2 Name alternate language that
Alt2 may be needed in some
countries or regions.
Yes business- Business STRING 12 None No Here you can enter a
last-name- Last 8 business last name in an
alt2 Name alternate language that
Alt2 may be needed in some
countries or regions.
Yes certificate- Certificat DATE Both No Here you can enter the start
start-date e Start date of the certificate that
Date confirms that the employee
is challenged.
Yes certificate- Certificat DATE Both No Here you can enter the end
end-date e End date of the certificate that
Date confirms that the employee
is challenged.
Yes challenge- Challeng STRING 1 Both No Here you can select if the
status e Status
employee is challenged.

Possible values
are Yes and No.

Yes community Communi STRING 25 None No

- ty 6
backgroun Backgrou
d nd
Yes country-of- Country/ STRING 25 None No
birth Region of 6
Birth
Yes date-of- Date of DATE None No
birth Birth
Yes display- Display STRING 12 Both No Here you can enter the
name Name 8
display name of the
employee. For example, if
an employee with the
official Chinese name
Shengjie chooses to be
called Jason, you can enter
Jason as the display name.

Note
This field is not used in General
Display Name. General Display
Name uses a standard element in
Succession Data Model -
displayName. For more
information, see Field
Requirements for the User Data
File.

Yes display- Display STRING 12 Both No Here you can enter an

name-alt1 Name 8 employee's display name in
Alt1 a second language.
Yes display- Display STRING 12 Both No Here you can enter an
name-alt2 Name 8 employee's display name in
Alt2 a third language.
Yes date-of- Date of DATE None No
death Death
Yes dateOfFirst Date of DATE None No
EntryInFra First
nce Entry in
France
Yes disabled- Disabled BOOLEA None No
veteran Veteran N
No end-date End Date DATE None No This is the end date the
previous personal
information stops being
effective. The system
calculates the end date
automatically depending on
the start date entered.
Yes expected- Expected DATE None No
retirement- Retireme
date nt Date
Yes first-name First STRING 12 Both Yes Enter the employee's first
Name 8 name here.
Yes first-name- Alt1 First STRING 12 Both No You can enter the
alt1 Name 8
employee's name in
alternate languages used
by the employee's native
language.

You can enter the first

name in alternate language
1 here.

Yes first-name- Alt2 First STRING 12 Both No You can enter the first
alt2 Name 8 name in alternate language
2 here.
Yes formal- Formal STRING 12 Both No Here you can enter the
name Name 8
employee's formal name.

For external user

integration in Learning, set
this to not mandatory.
Yes formal- Formal STRING 12 Both No Here you can enter an
 name-alt1 Name 8 employee's formal name in
Alt1 a second language.
Yes formal- Formal STRING 12 Both No Here you can enter an
name-alt2 Name 8 employee's formal name in
Alt2 a third language.
Yes gender Gender STRING 2 Both No Do not configure this field
as a picklist.

For external user

integration in Learning, set
this field to optional.

The list of values of this

field is system-defined. By
default, the values
are Male and Female. You
can enable the following
five values for the field from
the Upgrade Center:

 Male
 Female
 Unknown
 Undeclared
 Other

To enable this list:

1. Go to Upgrade
Center Optional
Upgrades.

2. Select Enhancement
to Gender Values –
Inclusion of
Additional Gender
Values.

Note
The changes by the
 upgrade can be
reversed within 10
days. To reverse
changes, in the
Upgrade Center,
select View
Recently
Completed
Upgrades. On the
Completed Upgrades
page,
select Undo against
Enhancement to
Gender Values.

For rules to validate

country/region-specific
genders, see Local Gender
Rules.
25 None No
6
12 Both No Here you can enter an
8 employee's initials, for
example: J.D.
12 Both No Here you can customize the
8
employee's name format,
by selecting the country
whose name format you
wish to use. You can do this
by clicking on Options.

Remember
If the changes to
employee's personal
information are managed
by workflows, to edit an
employee's formal name
 in Personal
Information block, you
must enable the <is-
overridden> field with
the Manage Business
Configuration tool or the
XML file.
Yes last-name Last STRING 12 Both Yes Enter the employee's last
Name 8 name here.
Yes last-name- Alt1 Last STRING 12 Both No You can enter the last name
alt1 Name 8 in alternate language 1
here.
Yes last-name- Alt2 Last STRING 12 Both No You can enter the last name
alt2 Name 8 in alternate language 2
here.
Yes marital- Marital PICKLIS Both No The list of values comes from the
status Status T
predefined
picklist ecMaritalStatus an
d contains the following values:

 Married

 Single

 Divorced

 Widow

 Unknown

 Cohabitation

 Separated

 Head of Household

 Partnership

 Cohabitation with
Contract (Netherlands)
  Cohabitation without
Contract (Netherlands)

 PACS (France)

For external user integration

in Learning, set this to not
mandatory.

Yes middle- Middle STRING 12 Both No You can enter the

name Name 8 employee's middle name
here, if existing.
Yes middle- Alt1 STRING 12 Both No You can enter the middle
name-alt1 Middle 8 name in alternate language
Name 1 here.
Yes middle- Alt2 STRING 12 Both No You can enter the middle
name-alt2 Middle 8 name in alternate language
Name 2 here.
Yes medal- Medal BOOLEA None No
veteran Veteran N
Yes name- Name STRING 12 Both No Here you can specify the
format Format 8 format of the employee's
name.
Yes name- Name STRING 12 Both No Users can select the name
format- Format 8 format code from a list of
code Code values at employee level.
The list shown in this field is
linked to the name format
configuration object
of Employee Central. Each
format that is defined in this
object is shown in the field
and the user can decide (on
employee level) which
format is to be applied to
their name.
Yes name- Prefix PICKLIS 12 Both No Here you can select an
prefix T 8 honorary title before the
employee's name if
applicable, for example van
or van der, and so on. The
list of values come from a
predefined
picklist nameprefix. This
field is getting converted
 from a free text to a picklist
field. To get more details on
how to do the conversion,
refer to the announcement
"New Picklist for Name
Prefix Field" under Optional
Upgrades in Upgrade
Center.
Yes nationality Nationalit STRING 12 Both No You can enter the
y 8
employee's nationality here,
for example:

 Germany
 USA

This field is required if you

use payroll integration
with SAP ERP.

For external user

integration in Learning, set
this to not mandatory.

Note
There are validations in the
system to check the
Nationality, Second
Nationality and Third
Nationality fields avoid that
incorrect data is entered in
the fields. Nationality and
Second Nationality cannot
have the same value in
both fields. The Third
Nationality can only be
entered if there is also a
Second Nationality.

If the information in the

 Nationality fields is provided
from an external system
such
as Recruiting and/or Onboar
ding 1.0 please make sure
that the corresponding
source nationality fields are
mapped to the right target
fields with the right
meaning. Also make sure
that the nationality fields do
not have the same value in
all the nationality fields.
Yes native- Native STRING 25 Both No You can enter the preferred
preferred- Preferred 6
lang Lang native language of the
employee.

The list of values comes

from the predefined
picklist Language. The
external code is the ISO 639
code for each language.
Stick to the ISO codes if you
consider integration
with SAP ERP.
Yes notes Note STRING 40 Both No This is a text field where the
00
user can enter additional
information if required.

Note
This field can't be displayed
on the Employee Profile.
Yes partner- Partner STRING 12 Both No Here you can enter the
name Name 8 name of your partner.
Yes partner- Partner PICKLIS 12 Both No Here you can select an
name- Name T 8 honorary title before the
prefix Prefix employee's partner's name
 if applicable, for example
van or van der, and so on.
The list of values come from
a predefined picklist
nameprefix.
Yes preferred- Preferred STRING 12 Both No You can enter the
name Name 8
employee's chosen name or
nickname.

You can also set the field

label as Chosen Name.
Yes protected- Protected BOOLEA 0 None No
veteran Veteran N
Yes religion Religion STRING 25 None No
6
Yes script Languag STRING 12 Both No You can enter the language
e Script 8 script.
Yes script-alt1 Languag STRING 12 Both No You can enter the language
e Script 8 script for the first alternate
language.
Yes script-alt2 Languag STRING 12 Both No You can enter the language
e Script 8 script for the second
alternate language.
Yes second- Second STRING 12 Both No If the employee has a
nationality Nationalit 8
y second nationality, you can
enter it in this field.

Note
There are validations in the
system to check the
Nationality, Second
Nationality and Third
Nationality fields avoid that
incorrect data is entered in
the fields. Nationality and
Second Nationality cannot
have the same value in
both fields. The Third
Nationality can only be
entered if there is also a
 Second Nationality.

If the information in the

Nationality fields is provided
from an external system
such
as Recruiting and/or Onboar
ding 1.0 please make sure
that the corresponding
source nationality fields are
mapped to the right target
fields with the right
meaning. Also make sure
that the nationality fields do
not have the same value in
all the nationality fields
Yes second- Second STRING 12 None No Enter the employee's
last-name Last 8 second last name here.
Name
Yes separated- Separate BOOLEA None No
veteran d Veteran N
Yes since Marital DATE 12 Both No You can enter the date
Status 8 since when the marital
Since status you indicated in the
field marital-status is
valid.
Yes salutation Salutatio STRING 12 None No The list of values comes
n 8
from the predefined
picklist salutation and
contains the following
standard fields:

 Mr
 Mrs
 Ms

Yes second- Second STRING 12 Both No Here you can enter the
title Title 8
second title, for
example: Phil. as the
 second title of Dr. Phil. John
Smith.

The list of values comes

from the predefined
picklist secondtitle.
Yes suffix Suffix STRING 12 None No You can enter a name
8
suffix, such as Jr, Sr, PhD,
and so on.

The list of values comes

from the predefined
picklist namesuffix.
Yes third- Third STRING 12 Both No If the employee has a third
nationality Nationalit 8
y nationality, you can enter it
in this field.

Note
There are validations in the
system to check the Nationality,
Second Nationality and Third
Nationality fields avoid that
incorrect data is entered in the
fields. Nationality and Second
Nationality cannot have the same
value in both fields. The Third
Nationality can only be entered if
there is also a Second Nationality.

If the information in the

Nationality fields is provided
from an external system such
as Recruiting and/or Onboarding
1.0 please make sure that the
corresponding source nationality
fields are mapped to the right
target fields with the right
 meaning. Also make sure that the
nationality fields do not have the
same value in all the nationality
fields

Yes third-name Third STRING 25 Both No If the person has a third

Name 6 name, you can enter that
here.
Yes third- Third STRING 25 Both No If the person has a third
name-alt1 Name 6 name, you can enter that
here for the first alternate
language.
Yes third- Third STRING 25 Both No If the person has a third
name-alt2 Name 6 name, you can enter that
here for the second
alternate language.
Yes title Title STRING 12 Both No Here you can enter an
8
employee's title, for
example: Dr. for Dr. John
Smith.

The list of values comes

from the predefined
picklist title.
Yes veteran Veteran BOOLEA None No
N
Yes visible- Visible BOOLEA None No
minority Minority N
No custom- Custom STRING 25 None No You can use this field for
string1–30 Strings 6 data not covered by the
1–30 standard fields.
No custom- Custom DATE None No You can use this field for
date1–20 Dates 1–
20 data not covered by the
standard fields

No custom- Custom LONG None No You can use this field for
long1–20 Numbers
1–20 data not covered by the
standard fields.

No custom- Custom DOUBL None No You can use this field for
double1– Decimals E
 20 1–20 data not covered by the
standard fields.

Note
Two sets of alternate languages are supported for Personal Information.
Alternate fields can be enabled in the Succession Data Model rather than in
the Country/Region-Specific Data Model. Country/Region-Specific settings
would be ignored for alternate fields. Each alternate field represents some
existing parent field in the element model in alternate script. The alternate
fields take the visibility and permission from the parent fields. If any of the
alt fields have entries, they can be displayed on the screen. However, in edit
mode, these fields are automatically hidden.

Phone Information
Here is a list of the fields available for this element.

Phone Information (hris-element-

id: phoneInfo)
Stand Field ID Field Label Data Ma Defaul Is How To Use This Field
ard Type x. t Requir
Len Visibili ed?
gth ty
Filte Search Search Filter: Fil Sear Filte Search Column
r: [N Column Column [No ter ch r: [No
o Selecti :[ Colu Selecti
Selecti on] No mn on]
on]
Sel
ect
ion
]
Yes country- Country STRING 32 Both No You can enter the country code
code Code here, for example, 0049 for
Germany.
Yes area-code Area STRING 32 Both No You can enter the code for the
Code region or state here.
Yes phone- Phone STRING 10 Both Yes You can enter the phone
number Number 0 number here.
Yes extension Extension STRING 32 Both No You can enter the extension of
the phone number here.
Yes isPrimary Is BOOLEA 1 Both No You can indicate which phone
Primary N number is the primary one.
Yes phone- Phone STRING 10 Both Yes The list of values comes from
type Type 0
the picklist ecPhoneType and
contains the following values:

 Home
 Business
 Billing
 Cell
 Fax
 Private Mobile
 Other
  Shipping

No custom- Custom STRING 25 None No You can use this field for data
string1–20 Strings 6 not covered by the standard
1–20 fields.
No custom- Custom DATE None No You can use this field for data
date1–10 Dates 1– not covered by the standard
10 fields.
No custom- Custom LONG None No You can use this field for data
long1–20 Numbers not covered by the standard
1–20 fields.
No custom- Custom DOUBL None No You can use this field for data
double1– Decimals E not covered by the standard
20 1–20 fields.

Social Accounts
Here is a list of the fields available for this element.

Social Accounts (hris-element-

id: imInfo)

Stand Field ID Field Label Data Ma Defaul Is How To Use This Field
 ard Type x. t Requir
Len Visibili ed?
gth ty
Filte Search Search Filter: Fil Sear Filte Search Column
r: [N Column Column [No ter ch r: [No
o Selecti :[ Colu Selecti
Selecti on] No mn on]
on]
Sel
ect
ion
]
Yes domain Domain STRING Both Yes You can select the instant
messaging domain for your
social account, for example,
Yahoo Messenger, AOL Instant
Messenger, and so on.

You can add more domains to

the predefined
picklist imdomain.
Yes im-id Instant STRING 10 Both Yes You can enter the ID that
Messagin 0 identifies the user in the
g ID instant messaging application.
Yes url URL STRING 25 Both No You can enter the
6 corresponding URL to the
instant messaging domain
here.
No custom- Custom STRING 25 None No You can use this field for data
string1–20 Strings 6 not covered by the standard
1–20 fields
No custom- Custom DATE None No You can use this field for data
date1–10 Dates 1– not covered by the standard
10 fields.
No custom- Custom LONG None No You can use this field for data
long1–20 Numbers not covered by the standard
1–20 fields.
No custom- Custom DOUBL None No You can use this field for data not
double1– Decimals E covered by the standard fields.
20 1–20
 Work Permit Info
Here is a list of the fields available for this element.

Work Permit Info (hris-element-

id: workPermitInfo)

Stand Field ID Field Label Data Ma Defaul Is How To Use This Field
ard Type x. t Requir
Len Visibili ed?
gth ty
Filte Search Search Filter: Fil Sear Filte Search Column
r: [N Column Column [No ter ch r: [No
o Selecti :[ Colu Selecti
Selecti on] No mn on]
on] Sel
ect
ion
]
No attachmen Attachme ATTACH Both No You can upload a copy of the
t-id nts MENT work permit document in
different formats, for
example, .doc, .ppt, .png, and
so on.
Yes country Country STRING 25 Both Yes This field is used to capture the
6
country/region for which the
document is valid.

The list of values comes from

the predefined
picklist ISOCountryList.
Yes document- Documen STRING 25 Both Yes The type of the document for
type t Type 6
which the ID needs to be
captured is given in this field.

The list of values comes from

the predefined cascading
picklist permitdoctype, which
is filtered based on the
country/region selected in
the country field. As you can
use this field country/region
dependent, you can create
country/region-dependent
values by using the
picklist ISOCountryList as
parent picklist in Picklist
Center.
Yes document- Documen STRING 25 Both No You can enter the title of the
title t Title 6 document.
Yes document- Documen STRING 25 Both Yes You can enter the number of
number t Number 6 the document.
No entity-type Entity- STRING 32 None No Note
type
In Employee Central V1, 3
entity types were supported.
With Employee Central V2,
only 1 (Work Eligibility) is
supported and the other types
are obsolete. So this field is
always automatically set to
Work Eligibility.

Since only 1 type is supported,

this is always set to not visible
in the system.
Yes expiration- Expiratio DATE Both No The work permit document is
date n Date valid until this date.
Yes issuing- Issuing STRING 25 Both No You can enter the authority
authority Authority 6 that issued the document.
Yes issue-date Issue DATE Both Yes Enter the date when the
Date document was issued.
Yes issue-place Issue STRING 25 Both No You can enter the place where the
Place 6 document was issued.

Yes is- Validated BOOLEA Both No You can indicate if the

validated N document has been validated
by somebody. Possible values
are Yes and No.
Yes notes Note STRING 40 Both No This is a text field where the
00
user can enter additional
information if required.

Note
This field can't be displayed on
the People Profile.
No custom- Custom STRING 25 None No You can use this field for data
string1–20 Strings 6 not covered by the standard
1–20 fields.
No custom- Custom DATE None No You can use this field for data
date1–10 Dates 1– not covered by the standard
10 fields.
No custom- Custom LONG None No You can use this field for data
long1–20 Numbers not covered by the standard
1–20 fields.
No custom- Custom DOUBL None No You can use this field for data
double1– Decimals E not covered by the standard
20 1–20 fields.

Direct Deposit
Direct Deposit is now replaced by the Payment Information and Payment
Information Detail Generic Objects.

Direct Deposit (hris-element-id: directDeposit)

For more information, refer to the Employee Central Payment

Information guide for details.

Employment Object Tables

The tables in the list below give you the technical information about the
employment objects and their fields that are relevant for Employee Central.

You can define these in the Succession Data Model and the
Country/RegionSspecific Succession Data Model. You can find more
information on these data models in the Setting Up the Succession Data
Model and Setting up Country/Region-Specific Data Models sections of
the SAP SuccessFactors Data Model Reference guide.

Note

Beware that hiding all fields in a block using a business rule is not supported
and will potentially cause unexpected behavior in the system. You must have
at least one field on this object enabled to avoid inconsistent behavior.

When you refer to the following tables, consider the following:

  The standard XML file for the data models contains only a subset of
these fields, but you can use all the fields listed in these tables, for
example, to override default attributes.
 Those fields listed in the tables, but not in the Succession Data Model,
still appear on the UI if their default visibility is set to “both”. If you
want to hide those fields, add them to the corresponding data model
and set the visibility to “none”.
 For start-date, end-date, event-reason and event-reason-code,
you cannot change the default visibility. That means even if you
change the visibility in the XML file for the Succession Data Model, the
system ignores this and the default visibility as listed in these tables is
considered.
 Fields listed in the standard XML files, but not in these tables, are not
relevant for Employee Central. You should leave their visibility
to “none”. Exceptions to this rule are customer-specific fields that you
can use as needed.

Related Information
Succession Data Model (SDM)

Employment Object A-Z

Compensation Information
Here is a list of the fields available for this element.

Compensation Information (hris-element-id: compInfo)

Stand Field ID Field Label Data Ma Defaul Is How To Use This Field
ard Type x. t Requir
Len Visibili ed?
gth ty
Filte Search Search Filter: Fil Sear Filte Search Column
r: [N Column Column [No ter ch r: [No
o Selecti :[ Colu Selecti
Selecti on] No mn on]
on]
Sel
ect
ion
]
Yes benefits- Benefits DOUBL — None No This field is to show the
benefits calculation for
rate Rate E employees who have highly
variable compensation, for
example, employees who work
on commission. This
calculation determines their
benefit coverage.
Yes compa- Compa- DOUBL — View No This field is calculated by the
ratio ratio E system; leave the visibility
on “view”.
Yes compensat Compens LONG 12 None No You can define the
8
ion- ation compensation structure
structure Structure assigned to the employee
here.
No event- Event- UNDEFI — Both No If you have defined event
reason- reason- NED reason foundation objects, this
code code field contains the external code
of those event reasons.
Yes job-level Job Level STRING 25 Both No This field is not in use
6 for Employee Central 2.0 and
must be configured with
visibility “none”.
Yes is-eligible- Is Eligible BOOLEA — None No You can indicate if the
for- For N employee is eligible for
benefits Benefits benefits. Possible values
are Yes and No.
Yes is-eligible- Is Eligible BOOLEA — None No You can indicate if the
for-car For Car N employee is eligible for a
 company car. Possible values
are Yes and No.
Yes is-eligible- Is Eligible BOOLEA — None No You can indicate if the
for-leave- for Leave N employee is eligible for leave
loading Loading loading. Possible values
are Yes and No.
Yes is-highly- Is Highly BOOLEA — None No Here you indicate if an
compensat Compens N employee is highly
ed- ated compensated. Possible values
employee Employe are Yes and No.
e
Yes is-insider Insider As BOOLEA — None No This field helps you to track
Defined N insider trading on the stock
By market. You can define if an
Statute employee has access to insider
information and is thus
considered an insider
according to the local insider
law, for example, the Securities
Exchange Act in the USA.

Possible values
are Yes and No.
Yes notes Note STRING 40 Both No This is a text field where the
00 user can enter additional
information if required.
Yes pay-group Pay STRING — None No You can define the pay group
Group of the employee here.

If you have defined pay group

foundation objects, this field
contains the external code of
those pay groups.

Caution
Do not add picklists for this
 field.
Yes pay-type Pay Type STRING 25 Both No The list of values for the pay
6 type is predefined by
picklist PayType. Possible
values are salaried,
commissioned, and so on.
Yes payroll-id Payroll Id STRING 64 None No Here you can enter the ID of
the payroll that is used to
compensate the employee.
Yes payroll- Payroll STRING 32 None No Here you can enter the ID of
system-id System the payroll system used for
Id compensating the employee.
Yes pensionabl Pensiona DOUBL — None No You can enter an amount that
e-salary ble E defines the employee's
Salary pensionable salary.
Yes proration- Proration BIGDECI 34 None No This field includes the factor for
factor
Factor MAL proration to be applied during
calculations.
Yes range- Range DOUBL — View No This field is calculated by the
penetratio Penetrati E system; leave the visibility
n on on “view”.
es salary Salary SALARY — Both No This field is obsolete and
should not be used
in Employee Central. It must be
configured with
visibility “none”.

This field has been replaced by

Recurring Pay Components. If
you require a field for currency
or salary, you can create a
custom field.
Yes salaryRate Salary STRING 50 Both No This field is obsolete and
Type Rate should not be used
Type in Employee Central. It must be
configured with
 visibility “none”.

If you require a field for

currency or salary, you can
create a custom field.
Yes salaryRate Salary LONG — Both No This field is obsolete and
Units Rate should not be used
Units in Employee Central. It must be
configured with
visibility “none”.

If you require a field for

currency or salary, you can
create a custom field.
Yes salaryCurr Currency STRING 20 Both No This field is obsolete and
encyCode should not be used
in Employee Central. It must be
configured with
visibility “none”.

If you require a field for

currency or salary, you can
create a custom field.
Yes seq- Sequenc LONG — Both No This field tells you the
sequence of transactions for
number e that day, for example, 1 of 2, 2
Number of 2. This field is only required
for import, and will appear in
the import template if you
have enabled the field.
No custom- Custom STRING 25 None No You can use these fields for
data not covered by the fields
string1– Strings 6 supplied as standard.
100 1–100
No custom- Custom DATE — None No
date1–30 Dates 1–
30
No custom- Custom LONG — None No
long1–20 Numbers
 1–20
No custom- Custom DOUBL — None No
double1– Decimals E
20 1–20

Note
In compensation information as well as recurring and non-recurring
payments, fields of type DOUBLE can now be hidden. To do this, set the pii
field to TRUE (pii="true"). This allows the users to decide for themselves
what information is visible and prevents unauthorized eyes from seeing the
information by mistake.

Employee Information
Here is a list of the fields available for this element.

Employee Information (hris-element-id: userAccountInfo)

Stand Field ID Field Label Data Ma Defaul Is How To Use This Field
ard Type x. t Requir
Len Visibili ed?
gth ty
Yes user-name User STRING 32 None Yes You can enter a unique user
Name name for new employees
during the hire process. This
value is also displayed on
the Username field on the
Talent Profile page.

If this field has

visibility=”both”, but no value
is entered during the new hire
process, the system copies
over the value from
the Person Id field. This is
also the standard behavior
if userAccountInfo is not
contained in the Succession
Data Model.
 Employment Information
Here is a list of the fields available for this element.

Employment Information (hris-element-id: employmentInfo)

Stan Field ID Field Data Ma Defaul Is How To Use This Field

dard Label Type x. t Requir
Len Visibili ed?
gth ty
Yes assignment- Assign STRING 25 Both Yes This is an identifier for the
id-external ment ID 6 employment of a user and can
externa be used for integrations with
l external systems. It is unique
and case-sensitive.
This is a multipurpose field that
can be used for different
scenarios
Yes benefits- Benefits DATE — Both No This is the start date from
eligibility- Eligibilit which the employee is eligible
start-date y Start for benefits.
Date
Yes company New STRING 25 Both Yes This field is required when you
Assign 6 have enabled Concurrent
ment Employment.
Compa Here you define the company
ny
where the concurrent
employment takes place; it can
be the same company as
specified for the existing
employment.
Yes companyExit Compa DATE — None Yes It is important to have this field
Date ny Exit filled out when an employee
Date leaves the company. From this
date, the legal obligation
period for when to purge the
 user can be calculated.
Yes eligibleForSto Eligible BOOLEA — Both No You can indicate if the
ck for N employee is eligible for stock.
Stock
Possible values
are Yes and No.
No employeeFirs Employ BOOLEA 10 None No The field indicates whether this
tEmployment ee's N is the employee’s first
First employment or not.
Employ
ment
Yes firstDateWor First STRING 25 Both No You can enter the employee’s
ked Date 6 first date at the company here.
Worked
If you use payroll integration
with SAP ERP, this field is
required for legal reporting in
the USA.
Yes initialOptionG Initial LONG — Both No This is the initial number of
rant Option options granted to the
Grant employee.
Yes initialStockGr Initial LONG — Both No This is the initial number of
ant Stock stocks granted to the
Grant employee.
No isContingent Is BOOLEA 1 View No This field is used to denote that
Worker Conting a user is an external worker.
ent N
Note
Worker
Only enable this field if
contingent workforce is
enabled in your system.

If the isContingentWorker field

is present in employmentInfo
HRIS Element, ensure that its
Visibility property is set
to View and Allow Import is set
to Yes to avoid validations
 while saving your changes.
Yes isECRecord Is EC FIXED 1 Both No This field is system generated
Record
and is used to
differentiate Employee
Central users from other
Employee Profile users who
have no Employee
Central data.

For an Employee Profile user

the value is set to 0.

If a user is created using the

Hire Wizard or any Employee
Central Employment wizard
(Add New Employee, Manage
Pending Hire, Add Contingent
Worker, Add Global
Assignment, Add Concurrent
Employment), this value will be
set to 1, to indicate that they
are an Employee Central user.

If a user is created from an

import, they have to have their
data imported in the correct
sequence to be marked as
an Employee Central user and
have the value set to 1.

If they are not imported in the

correct order, the system will
not mark them as an Employee
Central user and they will not
be included in Employee
Central functions, for example,
 their data will not be synced in
the HRIS Sync.

The only way to correct this is

to FULL PURGE import their
data in the correct order.

The field is not visible in the UI

and can either be reported on
using Advanced Reporting or
checked in the Integration
Center.
Yes isPrimary Is BOOLEA — Both No Note
Primary N You cannot use this field
because it has been
deprecated.
Yes jobCredit Job STRING — Both No The job credit corresponds to
Credit the seniority an employee can
acquire before joining the
company.
Yes jobNumber Employ STRING — View No This field has significance when
ment Id we implement multiple jobs
concept, until then it is
defaulted to 1.
Yes originalStart Original DATE — Both No If the employee has been
Date Start working for the company
Date before, enter the date of the
first hire in the organization in
this field.
No notes Note STRING 40 Both No This is a text field where the
00 user can enter additional
information if required.
Yes prevEmploye Previou STRING — Both No This field shows the previous
eId s employee ID if the employee
Employ has been at the company
 ment ID before. The new ID differs from
the old ID, because the
employee is considered as a
new hire, even if the employee
has worked for the same
company before.
Yes primaryEmpl Primary DATE — None No This is a transient field used for
Employ
oymentDate ment Concurrent Employment, when
Date updating primary and
secondary employments.
Yes professionalS Professi DATE — Both No You can use this field to track
dates for professional
erviceDate onal experience.
Service
Date
Yes seniorityDate Seniorit DATE — Both No This is the date from which
y Start seniority should be calculated.
Date
Yes serviceDate Service DATE — Both No You can use this date to
grandfather service to rehired
Date employees. In rare cases, a job
credit is given to an employee
and service date is adjusted.
For example, if an employee is
rehired with less than a 6-
month break, the service date
is set to the original hire date.
Yes start-date Hire DATE — Both Yes Enter the date of the current
Date hire for an employment.
Yes sourceOfRec Source STRING — None Yes This field is required for
ord of integration between Employee
Record Central and SAP ERP as well
to Integration Center.

The list of values comes from

the sourceOfRecord picklist.
The picklist must contain the
values "EC", "ONB", as well as
any values for each external
 system where employee data
is recorded. For technical
reasons, the values for the
picklist cannot contain
commas.

Picklists are in the Software

Download Center.
Note
All configuration files
for Employee Central, for
example, master data models,
master picklists, as well as
country/region-specific files,
have moved from the SAP Help
Portal to the Software

Download Center .

You update picklists in Admin

Center Picklist Center.

No custom- — STRING 25 None No You can use these fields for

string1–15 6 data not covered by the fields
and custom- supplied as standard.
string21–80
No custom- — DATE — None No
date1–5,
custom-
date21–30,
custom-
date41-65
No custom- — LONG — None No
long1–10
No custom- — DOUBL — None No
double1–10 E
 Note
The <isRehire> field is a transient field used during import when a user is
created for the Rehire with New Employment scenario. This value is not
saved to the database, it is only needed for the import.

Global Assignment Details

Here is a list of the fields available for this element.

Global Assignment Details (hris-element-id: globalAssignmentInfo)

To use the Global Assignment Details block, you have to turn on Global Assignments in the
Admin Center.
Standar Field ID Field Label Data Ma Defaul Is How To Use This Field
d Type x. t Requir
Len Visibili ed?
gth ty
Yes assignme Assignmen STRING 25 Both Yes This is an identifier for the
ntIDExter t ID 6 employment of a user and can
nal external be used for integrations with
external systems. It is unique
and case-sensitive.
Yes assignme Assignmen STRING 12 Both Yes Select the type of the global
nt-type t Type 8 assignment. The list of values
comes from the
picklist global_assignment_typ
e.
Yes company Company STRING 25 Both Yes Enter the company the
6 employee goes to for the global
assignment. You can choose
from the companies that are
available in the system.
Yes end-date Actual End DATE — Both Yes When you end a global
Date assignment, you need to specify
the actual end date. The date
cannot be empty.
Yes planned- Planned DATE — Both Yes Enter the date when the global
end-date End Date assignment is supposed to end.
No payroll- Payroll End DATE — Both No The date of the last payroll for
end-date Date the global assignment.
No custom- — STRING 25 None No You can use these fields for data
string101– 6 not covered by the fields
115 and supplied as standard.
custom-
The first 5 customer—specific
string116–
field numbers are used to add a
120
global assignment, the last 5
No custom- — DATE — None No
custom field numbers are used
date31–35
to end a global assignment.
and
custom-
date36–40
No custom- — LONG — None No
long21–25
and
custom-
long26–30
No custom- — DOUBL — None No
double21– E
25 and
custom-
double26–
30

Job Information
 Here is a list of the fields available for this element.

Job Information (hris-element-id: jobInfo)

Note
If a field is not defined in the data model, it cannot be used in business rules.
Remember
As a customer, you don't have access to Provisioning. To complete tasks in Provisioning, contact
your implementation partner or Account Executive. For any non-implementation tasks, contact
Product Support.

Standard Field ID Field Label Data Max. Defau Is How To Use This Field
Type Lengt lt Requir
h Visibil ed?
ity
No acquired- Acquired- STRING — Non No You can enter the former
from- from- e company the employee used to
company company work in before joining the
current company.
No attachme Attachme LONG — Non No Use this field to upload any
nt-id nt-id e attachments.
Yes business- Business STRING — Non Yes If you have defined business
unit Unit e unit foundation objects, this
field contains the external code
of those business units.
Yes company Company STRING — Non Yes This is the company or legal
e entity where the employee is
hired.

The country/region of the legal

entity determines the
country/region-specific
attributes displayed in the Job
Information block.

If you have defined legal entity

 foundation objects, this field
contains the external code of
those legal entities.
Yes company- Company STRING — Non No If an employee leaves the
company, you can track the
leaving- Leaving e new company of the employee.
for For
Yes contract- Contract DATE 0 Both No Enter the date in which the
end-date End Date contract ends.
Yes cost- Cost STRING — Non No If you have defined cost center
center Center e foundation objects, this field
contains the external code of
those cost centers.
Yes country- Country/ STRING 256 View No This field contains the
of- Region country/region the company is
company located in. The values are
derived from the country/region
(territory ID) of the legal entity,
showing the values from the
picklist ISOCountryList. The
field cannot be edited. Fields in
the section Job
Information can use the
picklist ISOCountryList as
parent picklist, for example for
the hris-field notice-period. In
this case it is mandatory that
the field country-of-
company is visible in the same
block as the field using this
picklist as parent picklist.
Yes default- Default STRING — Non No This field is relevant for
overtime- Overtime e the Employee Central
compensa Compensa Payroll Time Sheet.
tion- tion
Set this field to define the form
variant Variant
 of the overtime compensation
received by employees
Yes departme Departme STRING 128 Both No If you have defined department
nt nt foundation objects, this field
contains the external code of
those departments.
Yes division Division STRING 128 Both No If you have defined division
foundation objects, this field
contains the external code of
those divisions.

This field is synced to the

standard element 'division' in
the Employee Profile.
Yes dynamic- Dynamic STRING 256 Both No For the payroll time sheet, you
break- Break can specify that a dynamic
config- Configurat break rule is applied on days
code ion where no breaks are configured
in the employee’s work
schedule. For those days, a
dynamic break rule will
automatically create breaks
after a specific number of hours
of working time.
Yes eeo-class EEO Class STRING 256 Both No You can define the class for
equal employment
opportunities.

The list of values comes from

the predefined picklist eeo-
class.
Yes employee- Employee STRING 256 Non No This field indicates if the worker
class Class e is an employee, a contractor, an
intern, and so on.

The list of values comes from

 the predefined
picklist EMPLOYEECLASS.
employee- Employee PICKLIS 256 Both No Here you can specify the notice
notice- Notice T period the employee must give
period Period or follow when he/she wants to
quit their job (leave the
company).

Note
This field can be used with a
cascading picklist. You can
enable this in Manage
Business Configuration. If
you do that, you must assign
the <country-of-company> as
the parent picklist.

In the Picklist Center, the

picklist ID must be edited to
accept country-/region-specific
values. Assign the
ISOCountryList picklist ID to
the <Parent Picklist> field
Yes employee- Employee STRING 100 Both No You can define whether the
type Type employee type is hourly,
salaried, exception hourly, not
applicable, and so on.

The list of values comes from

the predefined
picklist employee-type
Yes employme Employme STRING 32 Non No This is a customer configurable
picklist to track types of
nt-type nt Type e employment, for example,
apprentice, full-time, and so on.
No emplStatu EmplStatu STRING — Non No This is a fixed picklist to
indicate employment status, for
s s e example, Active, Paid Leave,
 Unpaid Leave, Suspended,
Terminated, and so on.
This cannot be changed by the
customer.
No event Event STRING — Both No This field indicates the event
that has led to the change of
the job information.

The list of values comes from

the predefined picklist event.
You can change the labels for
the events in this picklist, but
you cannot add additional
events.
No event- Event- LONG — Both No This is the reason for the
reason reason- change of the job information.
code
If you have defined event
reason foundation objects, this
field contains the external code
of those event reasons.
No expected- Expected- DATE — Non No If an employee is on a leave of
absence, then this field can be
return- return- e used to record the planned
date date return date.
Note
This field will only be displayed
for leave of absence job history
records.
Yes fte FTE DOUBL — Non No This is a calculated field that
E e cannot be updated manually. It
is hard coded in the system that
FTE is calculated according to a
cascading logic based on the
default working hours (position,
job, location, legal entity).

FTE stands for “full-time

 equivalent” and indicates an
employee's working hours or a
legal entity's standard working
hours.
No hire- Hire- STRING — Non No This field can be used to track
the source of the hire, for
source source e example, internet ad or
newspaper ad.
No hire- Hire- STRING — Non No This is a customer configurable
picklist. This is a sub-grouping
source- source- e of the Hire Source field. If the
details details source was a newspaper, then
this field can be used to say
which newspaper.
Yes holiday- Holiday STRING — Non No This field is relevant for Time
calendar- Calendar e Off.
code
A holiday calendar shows the
public holidays for a given
period and country/region.

If you have defined holiday

calendar generic objects, this
field contains the external code
and name of those holiday
calendars
Yes is- Competiti BOOLEA — Non No Set this field to indicate
competiti on Clause N e whether a competition clause
on-clause- has been defined for the
active employee. A competition clause
is an agreement restricting an
employee who leaves the
enterprise from acquiring
employment with a competitor
within a specific industry, or
period of time.

Possible values are Yes and No.

Yes is-eligible- Is Eligible BOOLEA — Non No This field was previously used
to indicate whether the
for-benefit For N e employee is eligible for
Benefit company benefits.
This information should now be
set in Compensation
Information.
Yes is-eligible- Is Eligible BOOLEA — Non No This field was previously used
to indicate whether the
for-car For Car N e employee is eligible for a
company car.
This information should now be
set in Compensation
Information.
Yes is-eligible- Is Eligible BOOLEA — Non No You can indicate whether the
employee is eligible for a
for- For N e company financial plan.
financial- Financial
plan Plan
Yes is-fulltime- Is Fulltime BOOLEA — Non No You can indicate if the
employee Employee N e employee is a full-time
employee.

Possible values are Yes and No.

No is-home- Is-home- BOOLEA — Non No You can indicate if the
worker worker N e employee works from home.
Yes is-shift- Is Shift BOOLEA — Non No This is where you indicate if the
employee Employee N e employee works in shift.
Yes is-side- Sideline BOOLEA — Non No This field indicates if the
line-job- Job N e employee is allowed to take up
allowed Allowed a sideline job supplementary to
the employee's main
occupation.

Possible values are Yes and No.

No is- Is- BOOLEA — Non No You can use this field to
indicate whether an employee
volunteer volunteer N e is a volunteer.
Yes job-code Job STRING 128 Both Yes This is the job classification of
Classificat
 ion the employee.

If you have defined job

classification foundation
objects, this field contains the
external code of those job
classifications.

This field is synced to the

standard element 'jobCode' of
the Employee Profile.
Yes job-title Job Title STRING 256 Both No This field is synced to the
standard element 'title' of the
Employee Profile.

You can use an onChange rule

to default the values for the Job
Title from the respective Job
Classification field, as well as an
onSave rule to keep those
values in in sync.
No job- Job- LONG — Non No This field can be used to track
the job requisition ID in a
request- request- e recruiting system.
number number
Yes local-job- Local Job STRING 256 Non No Here you can enter the local job
title Title e title if it differs from the
company-wide used job title.
Yes location Location STRING 128 Both No If you have defined location
foundation objects, this field
contains the external code of
those locations.
Yes manager- Manager STRING 256 Non No This is customer configurable
picklist to categorize manager
category Category e types.
Yes manager- Superviso HRIS_FI 384 Both No You can choose from the list of
id r NDUSE existing users in the system to
R identify the employee's
 manager. This information is
then used to build the Org
Chart.

This field is synced to the

standard element 'managerId'
of the Employee Profile.
Yes notes Note STRING 4000 Both No This is a text field where the
user can enter additional
information if required.
No notice- Notice STRING 256 Both No In this field you define the
period Period amount of time that must be
given, by either an employer or
an employee, before the date
on which the work agreement is
terminated. The list of values
comes from the predefined
picklist NOTICEPERI.

As you can use this field

country/region specific, you can
create country/region-specific
values by using the
picklist ISOCountryList as
parent picklist.
Yes pay-grade Pay Grade STRING 256 Non No If you have defined pay grade
e foundation objects, this field
contains the external code of
those pay grades.
Yes payScaleA Pay Scale STRING 256 Non No This is the pay scale area to
rea Area
e which the employee is
assigned.

If you have defined pay scale

area generic objects, this field
contains the external code of
 those pay scale areas.

Note
Customers who use a picklist
for this object should migrate
this picklist to foundation
objects using the Provisioning
job “Initialize migration of
picklist fields payscale area and
type to MDF objects”. New
customers should not use a
picklist for this field.
Yes payScaleT Pay Scale STRING 256 Non No This is the pay scale type to
ype Type
e which the employee is
assigned.

If you have defined pay scale

type generic objects, this field
contains the external code of
those pay scale types.

Note
Customers who use a picklist
for this object should migrate
this picklist to foundation
objects using the Provisioning
job “Initialize migration of
picklist fields payscale area and
type to MDF objects”. New
customers should not use a
picklist for this field.
Yes payScaleG Pay Scale STRING 256 Non No This is the pay scale group to
roup Group
e which the employee is
assigned.

If you have defined pay scale

 group generic objects, this field
contains the external code of
those pay scale groups.
Yes payScaleL Pay Scale STRING 256 Non No This is the pay scale level to
evel Level
e which the employee is
assigned.

If you have defined pay scale

level generic objects, this field
contains the external code of
those pay scale levels.
No pm-form PM Form DECIMA 34 Non No This field stores the ID of a
L
e Performance Management form
that was generated as the
result of a SmartSuite event.
This is used for integration with
the Talent module. The field is
for technical purposes only and
shouldn't be displayed on the
Job Information UI, meaning no
view or edit permissions should
be granted for this field. This
isn't supported and will lead to
the unwanted generation of a
new form every time a Job
Information record with an
existing value is edited in the
History UI.
Yes position Position LONG — Non No This field is only shown when
e you have activated Position
Management.
Note
If Right to Return is enabled for
Global Assignment, Leave of
Absence, or Higher Duties, and
 if an employee has status
"dormant", then
the Position field is not forced
to be filled in the Job
Information, even if the field is
mandatory.
Yes probation- Probation DATE — Non No Here you enter the end date of
period- ary Period e the employee's probationary
end-date End Date period.
Yes radford- Radford STRING 128 Both No These are standardized job
codes from the Radford
jobcode JobCode consulting company.
Yes refresh- Enable STRING 128 Both Yes The new property indicates
comp- Compensa whether the corresponding field
required tion needs to trigger the refresh of
Refresh compensation information when
there is a change in the job
information.
Yes regular- Regular/ STRING 32 Non No This field indicates whether the
temp Temporar e employee is regular or
y temporary.

The list of values comes from

the predefined
picklist regular-temp.
Yes seq- Sequence LONG — Both Yes This field tells you the sequence
of transactions for that day, for
number Number example, 1 of 2, 2 of 2.
Yes shift-code Shift Code STRING 256 Non No The shift code indicates in
e which shift the employee works
in.
Yes shift- Shift DOUBL — Non No This field indicates the
compensation multiplier for
factor Percent E e working a specific shift, for
example, 1.5 for a weekend day
or holiday.
Yes shift-rate Shift Rate DOUBL — Non No This field indicates the
differential for a specific shift,
E e for example, on a weekend or
 holiday
Yes standard- Standard DOUBL — Non No You can define the standard
hours Weekly E e weekly hours the employee is
Hours supposed to work. This should
be the same amount as defined
in the employee's contract.
Yes supervisor Superviso STRING 256 Non No This is a customer configurable
picklist for customers who want
-level r Level e to categorize supervisory levels.
Yes time- Time STRING — Non No This field is relevant for
recording- Recording e the Employee Central
admissibili Admissibil Payroll Time Sheet.
ty-code ity
This field allows you to define
time recording admissibility
rules for individual employees -
controlling whether employees
can amend time sheet data in
the past and whether they can
amend already-approved time
sheets.
Yes time- Time STRING — Non No This field is relevant for
recording- Recording e the Employee Central
profile- Profile Payroll Time Sheet.
code
The Time Recording Profile
contains employee-specific
settings for the Employee
Central Payroll Time Sheet.

It sets the time recording

method and the time valuation
rules which are used for this
employee. If you have defined
time recording profile generic
objects, this field contains the
external code and name of
 those time recording profiles.

Note: If the Employee Central

Payroll Time Sheet is enabled in
Provisioning, the Time
Recording Profile can only be
entered and saved together
with the other three Time
Off fields in job information.
Yes time- Time STRING — Non No This field is relevant for
recording- Recording e the Employee Central
variant Variant Payroll Time Sheet.

Employees record their time in

the Employee Central
Payroll Time Sheet using one of
the following time recording
variants:

Clock Time-Based
Recording - Time recording
based solely on the entered
start and end times of work
within a specified period, for
example, each day.

Duration-Based Recording -
Time recording based solely on
the duration of the work
recorded for a specific period,
for example, in hours and
minutes for a given day of work.
Yes time-type- Time STRING — Non No This field is relevant for Time
profile- Profile e Off.
code
Different time types, such as
 work, vacation, and paid time
off (PTO) can be assigned to a
single structure, called the time
profile. This time profile is then
assigned to employees so that
they know, for example, how
much time off they can take
and what kind.

If you have defined time profile

generic objects, this field
contains the external code and
name of those time profiles.
No triggerMat User BOOLEA n/a Non No You can use this field if you've
rixRelatio defined. N e
nSync You define enabled matrix relationship
the label sync in Position Management
on the Settings, but would like to skip
BCUI
when it.
adding
the field
to the Job
Informatio
n model
Yes workingD Working STRING 256 Both No You can enter the number of
aysPerWe Days Per working days each week. It is
ek Week not a working schedule.

The number must be smaller

than or equal 7. For example:

 5
 3.5

This field is required if you use

payroll integration with SAP
ERP.
Yes work- Work STRING 100 Non No This field belongs to the
Standard Weekly Hours field to
 period Period e denote how many hours an
employee should work each
week.
Yes worksche Work STRING — Non No This field is relevant for Time
dule-code Schedule e Off.

It defines how an employee’s

total work time is divided. For
example, an employee might be
scheduled to work 40 hours a
week, comprising 5 days of 8
hours each.

If you have defined work

schedule generic objects, this
field contains the external code
and name of those work
schedules.
Note
To view the details of the work
schedule, you should have the
View permission for Work
Schedule and Work Schedule
Day Model under User Time
Management Object
Permissions.
Yes custom- Custom STRING 256 Non No Do not use the type attribute
string1 String 1 e for this custom string
(neither type=“foundation
object” nor type=”generic
object” nor type=”worker”).
No custom- Custom STRING 256 Non No You can use these fields for
string2– Strings 2– e data not covered by the fields
160 160 supplied as standard.
No custom- Custom DATE — Non No
date1–50 Dates 1– e
50
No custom- Custom LONG — Non No
long1–20 Numbers e
1–20
No custom- Custom DOUBL — Non No
double1– Decimals E e
20 1–20
Yes companyE Company DATE — View No For more information, refer to
ntryDate Entry the Entry-Based Date Fields
Date section of Entry Dates, Event-
Yes timeInCo Time In STRING 256 View No Based Dates, and TimeIn
mpany Company Calculation for Job Information.
Yes locationEn Location DATE — View No
tryDate Entry
Date
Yes timeInLoc Time In STRING 256 View No
ation Location
Yes departme Departme DATE — View No
ntEntryDa nt Entry
te Date
Yes timeInDep Time In STRING 256 View No
artment Departme
nt
Yes jobEntryD Job Entry DATE — View No
ate Date
Yes timeInJob Time In STRING 256 View No
Job
Yes positionEn Position DATE — View No
tryDate Entry
Date
Yes timeInPosi Time In STRING 256 View No
tion Position
Yes payScaleL Pay Scale DATE — View No
evelEntry Level
Date Entry
Date
Yes timeInPay Time In STRING 256 View No
ScaleLeve Pay Scale
l Level

Yes hireDate Hire Date DATE — View No For more information, refer to
Yes terminatio Terminati DATE — View No the Event-Based Date Fields
nDate on Date section of Entry Dates, Event-
Yes leaveOfAb Leave Of DATE — View No Based Dates, and TimeIn
senceStar Absence Calculation for Job Information.
tDate Start Date
Yes leaveOfAb Leave of DATE — View No
senceRetu Absence
rnDate Return
Date

Job Relationships
Here is a list of the fields available for this element.

Job Relationships (hris-element-id: jobRelationsInfo)

Standar Field ID Field Label Data Ma Defaul Is How To Use This Field
d Type x. t Requir
Len Visibili ed?
gth ty
Yes relationshi Relationshi STRING 10 Both Yes Here you choose the type of
p-type p Type 0 relationship. The list of values
comes from the predefined
picklist jobRelType. Possible
 values are:

 HR manager
 Matrix manager
 Custom manager
 Second manager
 Additional manager
 Delegate A
 Delegate B

You can also add more types of

manager by enhancing the
picklist CSV file.
Yes rel-user-id Name STRING 38 Both Yes You can select the manager's
4 name from the list of existing
users in the system.
No custom- Custom STRING 25 None No You can use these fields for data
string1–20 string 1 to 6 not covered by the fields
20 supplied as standard.
No custom- Custom DATE — None No
date1–10 Dates 1–10
No custom- Custom LONG — None No
long1–20 Numbers
1–20
No custom- Custom DOUBL — None No
double1– Decimals E
20 1–20
No custom- — STRING 25 None No You can use these fields for data
string101– 6 not covered by the fields
115 and supplied as standard.
custom-
The first 5 customer—specific
string116–
field numbers are used to add a
120
global assignment, the last 5
No custom- — DATE — None No
custom field numbers are used
date31–35
to end a global assignment.
and
 custom-
date36–40
No custom- — LONG — None No
long21–25
and
custom-
long26–30
No custom- — DOUBL — None No
double21– E
25 and
custom-
double26–
30

PayComponentNonRecurring
Here is a list of the fields available for this element.

PayComponentNonRecurring (hris-element-id: payComponentNonRecurring)

Standar Field ID Field Label Data Ma Defaul Is How To Use This Field
d Type x. t Requir
Len Visibili ed?
gth ty
No action- Action- — None No This field is used for internal
enum enum purposes. Do not use it in the
data model. Even if it is used, it
won't be visible on the UI.
No action-id Action-id LONG — None No This field is used for internal
purposes. Do not use it in the
data model. Even if it is used, it
won't be visible on the UI.
Yes alternativ Alternative STRING 25 Both No You can assign an alternative
e-cost- Cost 6 cost center to the non-recurring
center Center payment by entering the cost
 center here.

This field is relevant for payroll

integration. For more
information, refer to the SAP
SuccessFactors Employee
Central Payroll guide.
No allow- Specifies if BOOLEA — None No This field is used for internal
delete delete is N purposes. Do not use it in the
allowed for data model. Even if it is used, it
a record won't be visible on the UI.
Yes base-pay- Base Pay STRING — None No You can specify for pay
componen Componen components of type
t t PERCENTAGE of what exactly
the pay component is a
percentage, for example, bonus
= 10% of base salary. Once this
field is filled for a pay
component definition, all
employee pay components must
use this value of the base pay
component group field (it cannot
be overwritten).
Note
If you enable this field as
editable in the employee UIs, the
value help will offer you all the
pay component groups to which
the pay component you are
editing are assigned. So for
example, you would get the pay
component group “Total annual
earnings” offered as a possible
base pay component group for
employee pay component base
salary, bonus, and car
 allowance.

Set to View to be displayed on

the UI or None. Do not set it to
Both.
Yes calculated Calculated Double — View No
 For pay components of
-amount Amount
type AMOUNT, the
calculated amount is set
to the amount

 For pay components of

type PERCENTAGE, the
calculated amount is the
amount of the
corresponding base pay
component group
multiplied with the
percentage which is
stored in the field amount

 For pay components of

type NUMBER, the
calculated amount is the
number entered in the
employee pay component
multiplied by a rate read
from either the pay scale
level or from the pay
component (FO) definition.

Note
If the rate in the
payscalelevel is not
available, the rate
specified in the
Foundation Object is used.
No created- Created-by STRING 10 None No This field is used for internal
by 0 purposes. Do not use it in the
 data model. Even if it is used, it
won't be visible on the UI.
No created- Created-on DATE — None No This field is used for internal
on purposes. Do not use it in the
data model. Even if it is used, it
won't be visible on the UI.
Yes currency- Currency STRING 20 Both Yes Select the currency the pay
code Code component is issued in from the
list of currencies provided in this
field.
No item-id Item-id LONG — None No This field is used for internal
purposes. Do not use it in the
data model. Even if it is used, it
won't be visible on the UI.
No last- Last- STRING 10 None No This field is used for internal
modified- modified- 0 purposes. Do not use it in the
by by data model. Even if it is used, it
won't be visible on the UI.
No last- Last- DATE — None No This field is used for internal
modified- modified- purposes. Do not use it in the
on on data model. Even if it is used, it
won't be visible on the UI.
Yes non- End Date DATE def None No This field has the visibility ‘none’
recurring- of the aul by default. So if the customers
pay- Related t require these fields, then they
period- Period need to change the data model
end-date to have the visibility set to
‘both’. The field values will be
replicated to SAP ERP if payroll is
enabled.
Yes non- Start Date DATE def None No This field has the visibility ‘none’
recurring- of the aul by default. So if the customers
pay- Related t require these fields, then they
period- Period need to change the data model
start-date to have the visibility set to
 ‘both’. The field values will be
replicated to SAP ERP if payroll is
enabled.
Yes number- Number of DOUBL — Both No The value specified in this field is
of-units multiplied with the rate from the
Units E payscalelevel defined in Job
Information. In case the
payscalelevel is not available,
the value specified in this field is
multiplied with the rate defined
for the Foundation Object, which
is then displayed in the
calculated-amount field.
Yes offcycle- OffCycle Picklist — None No Note
reason Reason You only need to use this field if
you use Payroll Control Center.

The value of this field gives the

reason for the offcycle payment.

The valid offcycle reasons need

to be specified in a picklist. The
external code of the picklist can
be any value except blank. The
external code of the picklist has
to be mapped in the Code Value
Mapping (T77SFEC_CVMAPC )
table in Employee Central
Payroll.
Yes pay- Type STRING — Both Yes If you have defined pay
componen component foundation objects,
t-code this field contains the external
code of those pay components.
No pay- Pay- STRING 38 None No This field is used for internal
purposes. Do not configure the
componen component visibility.
t-type -type
Yes pay-date Issue Date DATE — Both Yes The date the compensation is
issued.
Yes pay-id Pay ID Picklist — None No Note
 You only need to use this field if
you use Payroll Control Center.

The ID is used to differentiate

batches of offcycle payroll runs.

The ID values need to be

specified in a picklist. They
cannot be in the ranges of 0-9,
A-Z and ‘!’. Only special
characters, such as ‘@’, ‘#’, ‘$’,
‘%’, ‘^’, ‘&’, ‘*’, ‘?’, can be used
to indicate the specific payment
to be treated as planned offcycle
if the Payroll Control Center is
implemented.

When the ID is not entered, the

specific payment will be treated
as adhoc offcycle payment if the
Payroll Control Center is
implemented.
Yes reference- Reference LONG — None No This field is relevant for payroll
ID
id integration. For more
information, refer to the SAP
SuccessFactors Employee
Central Payroll guide.
Yes sent-to- Sent To DATE — None No
The date the compensation
payroll Payroll
information is sent to payroll.
No sequence- Sequence STRING 38 View Yes This field is required for
number Number importing data. If you enable
this field, the allow import
property is defaulted to True.
Yes tax- Tax STRING 32 None No This field shows whether the pay
component is taxed or not.
treatment Treatment
Yes unit-of- Unit of Generic — Both No Displays the unit that is used.
measure Measure Object For example, kg, pound, pieces,
 (Unit of and so on
Measur
e
accordi
ng to
UN/CEF
ACT
Recom
mendati
on
20/21)
Yes value Amount DOUBL — Both Yes Here you define the amount of
E the component in numbers.
No custom- Custom STRING 25 None No
You can use these fields for data
string1–20 Strings 1– 6
not covered by the fields
20
supplied as standard.
No custom- Custom DATE — None No
date1–10 Dates 1–10
No custom- Custom LONG — None No
long1–20 Numbers
1–20
No custom- Custom DOUBL — None No
double1– Decimals E
50 1–50

Note
In compensation information as well as recurring and non-recurring
payments, fields of type DOUBLE can now be hidden. To do this, set the pii
field to TRUE (pii="true"). This allows the users to decide for themselves
what information is visible and prevents unauthorized eyes from seeing the
information by mistake.
 Payment Information
Here is a list of the fields available for this element. Payment Information
(hris-element-id: paymentInfo)

Note
To use the Payment Information block with payroll integration, you have to turn on
payroll integration in Provisioning. Alternatively to use Payment Information without
payroll integration, choose “Enable Direct Deposit as a Payment Method in Payment
Information even if Payroll Integration is not enabled” in Provisioning and ensure
that the Generic Objects setting is also selected.

Remember
As a customer, you don't have access to Provisioning. To complete tasks
in Provisioning, contact your implementation partner or Account Executive. For any
non-implementation tasks, contact Product Support.

The fields of this element are defined in the Succession Data Model.
Stan Field ID Field Label Data Type Max. Defau Is How To Use This Field
dard Lengt lt Requi
h Visibil red?
ity
Yes paymen Payment STRING 20 Non No This field is required if you have
t- Method e activated payroll integration. It
method indicates how an employee gets paid,
for example:

 By bank transfer

 By check

 Cash

For more information about how to set

up payroll integration, refer to
the SuccessFactors Employee
 Central Payroll guide.

Pension Payout Details

Here is a list of the fields available for this element.

Pension Payout Details (hris-element-id: pensionPayoutsInfo)

Standar Field ID Field Data Type Ma Defaul Is How To Use This Field
d Label x. t Requir
Len Visibili ed?
gth ty
Yes company Pension STRING 25 Both Yes Enter the pension provider that
Provide 6 pays the pension payout. You
r can select from the pension
providers you have created
as company foundation object in
the system.
Yes end-date Actual DATE — Both Yes When you end a pension payout,
End you have to enter the actual end
Date date of the pension payout.
Yes payroll- Payroll DATE — Both Yes Enter the payroll end date. This
end-date End might differ from the end date of
Date the pension payout.
Yes planned- End DATE — Both No Enter the end date when the
end-date Date pension payout is supposed to
end. This does not end the
pension payout automatically.
Yes start-date Start DATE — Both Yes Enter the start date of the
Date pension payout.
No custom- — STRING 25 None No You can use these fields for data
string101– 6 not covered by the fields
115 and supplied as standard.
custom-
string116–
120
No custom- — DATE — None No
The first 5 custom field numbers
date31–35
are used to add a pension
and
payout, the last 5 custom field
custom-
numbers are used to end a
date36–40
pension payout.
No custom- — LONG — None No
long21–25
and
custom-
long26–30
No custom- — DOUBLE — None No
double21–
25 and
custom-
double26–
30

Termination Information
Here is a list of the fields available for this element.

Termination Information (part of hris-element-id: employmentInfo)

Standar Field ID Field Data Type Ma Defaul Is How To Use This Field
d Label x. t Requir
Len Visibili ed?
gth ty
No attachme Attach LONG — None No This field shows any
nt-id ment-id attachments from Job
Information.
Yes benefitsEn Benefits DATE — Both No Benefits are granted until this
dDate End date. By default, this is the same
Date date as the termination date,
unless you change it here.
No bonusPay Bonus DATE — Both No Bonus pays are being paid until
 Expiration Pay this date. By default, this is the
Date Expirati same date as the termination
on Date date, unless you change it here.
Yes eligiblefor Eligible BOOLEAN — Both No This field indicates that the
SalContin for employee is eligible for salary
uation Salary continuation. Possible values
Continu are Yes and No.
ation
Yes end-date Termina DATE — View Yes Enter the end date of the
tion employee's working contract
Date with the company.
Yes lastDateW Last DATE — Both No The last day the employee
orked Date worked for the company. By
Worked default, this is the same date as
the termination date, unless you
change it here.
Yes okToRehir Ok to BOOLEAN — Both No If the employee can be rehired,
e Rehire set this field to Yes.
Yes payrollEnd Payroll DATE — Both No The last payroll for this
Date End employee. By default, this is the
Date same date as the termination
date, unless you change it here.
Yes regretTer Regret BOOLEAN — Both No If this termination is a loss for
mination Termina the organization, set this field
tion to Yes.
Yes salary- Salary DATE — Both No Salary is paid until this date. By
end-date End default, this is the same date as
Date the termination date, unless you
change it here.
Yes StockEnd Stock DATE — Both No Stocks are granted until this
Date End date. By default, this is the same
Date date as the termination date,
unless you change it here.
No custom- Custom STRING 25 None No You can use these fields for data
string16 Strings 6 not covered by the fields
 to 16–20 supplied as standard.
custom-
Custom
string20
Strings
and
81–100
custom-
string81–
100
No custom- Custom DATE — None No
date6 to Dates
custom- 6–20
date20
Custom
Dates
66–90
No custom- Custom LONG — None No
long11 to Number
custom- s 11–20
long20
No custom- Custom DOUBLE — None No
double11 Decimal
to s 11–20
custom-
double20

Note
If the attachment field is configured for Job Information, then attachments
are shown in the related Job Information record in the History UI.

However, if the attachments field is not configured for Job Information or the
logged-in user does not have permission to view or edit that field, but the
workflow initiator added the attachments to Job Information, then system
loads the attachment into the Employment Information attachments field in
the Termination UI.
Deprecated Fields
The following elements are deprecated and must not be used in the data
models.

Job Information
 Additional-Manager

 Address

 Amount-of-Financial-Plan

 Custom-Manager

 ERN-Number

 Govt-Grant-Amount

 HR-Manager

 International-Org-Code

 Is-Primary

 Manager

 Manager-Employment-ID

 Matrix-Manager

 Pay-Group

 Second-Manager

 Time-Account-Profile-Code

 Track-ID

Compensation Information
  BonusInfo

 CompAdjustInfo

 DirectDeposit

 JobInfoLocal

 LeaveOfAbsence

 NameInfo

 PayrollInfo

 RelInfo

 StatusInfo

 WorkEligibilityInfo

Change History
Learn about changes to the documentation for Data Model Field Information
in Employee Central in recent releases.

Note

All configuration files for Employee Central, for example, master data
models, master picklists, as well as country/region-specific files, have moved

from the SAP Help Portal to the Software Download Center .

1H 2024 - Present
Type of Change Description More Info
None We did not update this
document.

2H 2023
 Type of Change Description More Info
Feb 16, 2024
Changed We revised the Dependents
information about
Dependents. The count
of custom strings is 20.
Changed We revised the Emergency Contact
information about
Emergency Contact. The
field Relationship is a
required field.
Changed We revised the Dependents
information about
Dependents. The count
of custom strings is 20.
Nov 10, 2023
Changed The fields in the Emergency Contact
Emergency Contact
block that were only
available for dependents
are now available for all
contacts.
Oct 13, 2023
Changed We have moved the Foundation Object
Change History to the Tables
end of the guide.
New We added a Global Information
field attachment-id for
global information.