Data Object Tables in Employee Central: Developer Guide - PUBLIC Document Version: 1H 2021 - 2021-07-21

Developer Guide | PUBLIC
Document Version: 1H 2021 – 2021-07-21
Data Object Tables in Employee Central

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

Content
1 Change History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2 Foundation Object Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2.1 Organization Objects A-Z. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
Business Unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Corporate Address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Cost Center. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Department. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Division. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Geozone. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Legal Entity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Location. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Location Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.2 Job-Related Objects A-Z. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Job Classification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Job Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.3 Pay-Related Objects A-Z. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Frequency. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
Pay Calendar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
Pay Component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Pay Component Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
Pay Grade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Pay Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
Pay Range. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
2.4 Other Objects A-Z. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Dynamic Role Assignment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Dynamic Role. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Event Reason. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41
WfConfig. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
wfConfig Contributor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
wfConfig CC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
wf Step Approver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48
3 Person Object Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

3.1 Person Objects A- Z. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Addresses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Biographical Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

2 PUBLIC Content
Dependents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Direct Deposit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Email. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Emergency Contact. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Global Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68
National ID Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71
Payment Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Personal Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Phone Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Social Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92
Work Permit Info. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
4 Employment Object Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

4.1 Employment Objects A - Z. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Compensation Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96
Employee Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Employment Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101
Global Assignment Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Job Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Job Relationships. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
PayComponentNonRecurring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
PayComponentRecurring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Pension Payout Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Termination Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
5 Deprecated Elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Content PUBLIC 3
1 Change History
Learn about changes to the documentation for Data Object Tables in Employee Central in recent releases.
1H 2021
Type of Change Description More Info
Changed Updated information about isContingent Employment Information [page 101]

Worker field.
Changed Updated information about genderCoun Global Information [page 68]

trySpecific field.
2H 2020
What's New Description More Information
Global Information The country/region-specific <Gender> Global Information [page 68]

field is added.
Compensation Information The <is-eligible-for-leave- Compensation Information [page 96]
loading> field is added.
Pay Component Non-Recurring The fields <pay-id> and <offcycle- PayComponentNonRecurring [page 132]
reason> are added.
Personal Information If the changes to employee's personal in Personal Information [page 75]
formation are managed by workflows, to

edit an employee's formal name in
Personal Information block, you must en
able the <is-overridden> field.
Deprecated Elements A new topic listing deprecated elements Deprecated Elements [page 150]
was added.

4 PUBLIC Change History
2 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.

Foundation Object Tables PUBLIC 5
○ 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
per datatype. Instead, you can now assign any number of fields, subject to a maximum of 200 fields, depending
on your requirement to a datatype. 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 datatypes 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 datatypes 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

6 PUBLIC Foundation Object Tables
2.1 Organization Objects A-Z
2.1.1 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 maintain this object.
generic object id: BusinessUnit
Max.
Standard Field ID Field Label Data Type Length Visibility Required How to Use this Field
Yes description Description Translatable 128 As defined No If you need a more detailed
in the Con
description of the business
figure Ob
unit than the Name field
ject Defini-
tion page. can provide, enter it here.
Yes effectiveS- Start Date Date — As defined Yes Enter the date the busi
tartDate in the Con ness unit becomes active.
figure Ob
ject Defini-
tion page.
Yes effecti- End Date Date — As defined No You can also enter the date
veEndDate in the Con the business unit stops be
figure Ob ing active.
ject Defini-
tion page.
Yes effectiveS- Status Enum — As defined Yes Possible values are Active
tatus in the Con and Inactive. Do not con
figure Ob figure this as a picklist.
ject Defini-
tion page.
Yes external Code String 32 As defined Yes Define a unique code by

Code in the Con which the system can dis
figure Ob tinguish the different busi
ject Defini- ness units from each
tion page. other.
Yes headOfUnit HeadOfUnit User — As defined No You can enter the identifier
in the Con of the person heading the
figure Ob business unit.
ject Defini-
tion page.

Max.
Yes name Name Translatable 90 As defined No You can enter a short

in the Con
name for the business unit
figure Ob
here.
ject Defini-
tion page.
2.1.2 Corporate Address
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.
Max.
No start-date Start Date DATE — Both Yes Enter the date when the
corporate address be
comes effective.
No end-date End Date DATE — None No This is the end date the
previous corporate ad
dress stops being effec-
tive. The system calculates
the end date automatically
depending on the start
date entered.
Yes address1 Address 1 STRING 256 None No You can enter the first line
of address here.
Yes address2 Address 2 STRING 256 None No You can enter the second
line of address here.
Yes address3 Address 3 STRING 256 None No You can 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.

Max.
Yes county District STRING 256 None No This is where you enter the
county the company is lo
cated in.
Yes state State STRING 256 None No This is where you enter the
state the company is lo
cated in.
Yes province Province STRING 256 None No This is where you enter the
province the company is
located in.
Yes zip-code Zip Code STRING 256 None No This is 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 lo
cated in.
No custom- Custom STRING 256 None No You can use these fields for
string1–20 Strings 1– data not covered by the
20 fields supplied as stand
ard.
No custom- Custom DATE — None No
date1–10 Dates 1–10
No custom- Customer LONG — None No

long1–20 Numbers 1–
20
No custom- Custom DOUBLE — None No

double1–20 Decimals 1–
20
2.1.3 Cost Center
Cost Center is now an MDF Generic Object. Use the Configure Object Definition page to maintain this object.
generic object id: CostCenter

Max.
Yes costCenter External Ob String 40 As defined No This field contains the cost
ExternalOb
ject ID in the Con center ID in external for
jectId
figure Ob mat. If you have multiple fi-
ject Defini- nancial systems from
tion page. which you upload cost
centers into Employee
Central, make sure that
the cost center IDs are
unique. Usually, down
stream systems like pay
roll do not understand this
unique ID and you have to
provide the cost center ID
in its external format.
Yes costCenter Costcenter User 255 As defined No Specify the cost center
Manager
Manager in the Con manager's identifier here.
figure Ob
ject Defini-
tion page.
Yes description Description Translatable 128 As defined No Specify a description here

in the Con if you need a more detailed
figure Ob description of the cost
ject Defini- center than the one the
tion page. Name field provides. This
field is translated to Eng
lish (US) and the compa
ny's default language.
Yes effectiveS- Start Date Date 255 As defined Yes Specify the date on which
tartDate in the Con the cost center becomes
figure Ob active.
ject Defini-
tion page.
Yes effecti- End Date Date 255 As defined No Specify the date on which
veEndDate in the Con the cost center stops be
ject Defini-
tion page.
Yes effectiveS- Status Enum 255 As defined Yes Possible values are Active
ject Defini-
tion page.

Max.
Yes external Code String 32 As defined Yes Specify a unique code by

figure Ob tinguish the different cost
ject Defini- centers from each other.
tion page.
Yes glState GLState String 32 As defined No This code is assigned to

in the Con
mentCode mentCode account groups, such as
figure Ob
customer receivables or
ject Defini-
tion page. vendor payables to record
transactions, depending
on financial accounts in
volved in such transac
tions. It ensures that total
account data includes all
sub-account transactions.
Yes legalEntity Legal Entity Generic Ob 38 As defined No Specify a legal entity to be
in the Con associated with the cost
ject
figure Ob center. By default, this
ject Defini- field is set to not visible.
tion page. That can be changed in the
object definition.
Yes Name Name Translatable 90 As defined No Specify a short name for

in the Con
the cost center unit here.
figure Ob
This field is translated to
ject Defini-
tion page. English (US) and the com
pany's default language.
Yes parentCost Parent Generic Ob 255 As defined No Cost centers can be hier
Center ject in the Con archical. If this is the case
figure Ob in your business, use this
ject Defini- field to specify a higher-
tion page. level cost center.
2.1.4 Department
Department is now an MDF Generic Object. Use the Configure Object Definition page to maintain this object.
generic object id: Department

Max.
Yes costCenter Cost Center Cost Center — As defined No You can assign the depart
GO in the Con ment to a cost center by
figure Ob entering the cost center
ject Defini- details here.
tion page.
in the Con description of the depart
figure Ob ment than the Name field
ject Defini- can provide, enter it here.
tion page.

figure Ob tinguish the different de
ject Defini- partments from each
tion page. other.
Yes effectiveS- Start Date Date — As defined Yes Enter the date the depart
tartDate in the Con ment becomes active.
figure Ob
ject Defini-
tion page.
veEndDate in the Con the department stops be
ject Defini-
tion page.
ject Defini-
tion page.
Yes headOfUnit Head of De User — As defined No You can enter the depart
in the Con
partment ment head's identifier
figure Ob
here.
ject Defini-
tion page.

in the Con name for the department.
figure Ob
ject Defini-
tion page.

Max.
Yes parentDe Department Department — As defined No You can enter the depart
partment GO in the Con ment that is on the next
figure Ob level up in the cost center
ject Defini- hierarchy.
tion page.
2.1.5 Division
Division is now an MDF Generic Object. Use the Configure Object Definition page to maintain this object.
generic object id: Division
Max.
in the Con description of the division
figure Ob than the Name field can
ject Defini- provide, enter it here.
tion page.

figure Ob tinguish the different divi
ject Defini- sions from each other.
tion page.
Yes effectiveS- Start Date Date — As defined Yes Enter the date the division
tartDate in the Con becomes active.
figure Ob
ject Defini-
tion page.
veEndDate in the Con the division stops being
figure Ob active.
ject Defini-
tion page.

Max.
in the Con
tatus and Inactive. Do not con
figure Ob
figure this as a picklist.
ject Defini-
tion page.
Yes headOfUnit Head of Di User — As defined No You can enter the division
vision in the Con head's identifier here.
figure Ob
ject Defini-
tion page.

in the Con name for the division here.
figure Ob
ject Defini-
tion page.
Yes parentDivi Division Division GO — As defined No You can enter the division
sion in the Con that is on the next level up
figure Ob in the division hierarchy.
ject Defini-
tion page.
2.1.6 Geozone
hris-element id: geozone
Max.
Yes adjustment Adjustment STRING — Both No If the pay range for this ge
Percentage Percentage ozone is to differ by a cer
tain percentage from that
for another geozone, you
can specify the percentage
here.
This field is informational

only and is not used to cal
culate compa ratio or
range penetration.

Max.
Yes description Description STRING 128 Both No If you need a more detailed
description of the geozone
than the Name field can
provide, enter it here.
Yes external Code STRING 32 Both Yes Define a unique code by

Code which the system can dis
tinguish the different geo
zones from each other.
Yes name Name STRING 90 Both No You can enter a short

name for the geozone
here.
Yes start-date Start Date DATE — Both Yes Enter the 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 STRING — Both Yes Possible values are Active
and Inactive. Do not con
ard.

20

20
2.1.7 Legal Entity

Legal Entity is now an MDF Generic Object. Use the Configure Object Definition page to maintain 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.
Max.
Yes countryO Country Country GO — As defined Yes Enter the country that
fRegistra in the Con makes up this geozone.
tion figure Ob
ject Defini-
tion page.
Yes currency Currency Currency — As defined Yes Enter the currency that is
GO in the Con used for this legal entity.
figure Ob
ject Defini-
tion page.
Yes defaultLoca Default Lo location FO — As defined No You can enter a location
tion cation in the Con that applies to all employ
figure Ob ees in this legal entity.
ject Defini-
tion page.
Yes default Default Pay PayGroup — As defined No You can enter a pay group
GO
PayGroup Group in the Con that applies to all employ
figure Ob ees in this legal entity.
ject Defini-
tion page.
in the Con description of the legal en
figure Ob tity than the Name field
tion page.
Yes external Legal Entity String 32 As defined Yes Define a unique code by
Code ID in the Con which the system can dis
figure Ob tinguish the different legal
ject Defini- entities from each other.
tion page.
Yes name Legal Entity Translatable 90 As defined No You can enter a short
Name in the Con name for the legal entity
figure Ob here.
ject Defini-
tion page.

Max.
ject Defini-
tion page.
Yes effectiveS- Start Date Date — As defined Yes Enter the date the legal en
tartDate in the Con tity becomes active.
figure Ob
ject Defini-
tion page.
veEndDate
in the Con when the legal entity stops
figure Ob being active.
ject Defini-
tion page.
Yes standard Standard Decimal — As defined No In this field, you can enter
Weekly Weekly in the Con the number of hours em
Hours Hours figure Ob ployees are expected to
ject Defini- work in this geozone.
tion page.
Yes officialLan- Official Lan String — As defined No If there is an official lan

guage guage in the Con guage for a legal entity,
figure Ob you can enter the ISO code
ject Defini- for that language here.
tion page.
2.1.8 Location
hris-element id: location
Max.
description of the location
than the Name field can

Max.

tinguish the different loca
tions from each other.
Yes loca Location STRING — Both No If you want to assign this

tionGroup Group location to a group, enter
the identifier for the rele
vant group here.

name for the location.
Yes start-date Start Date DATE — Both Yes Enter the date when the lo
cation becomes active.
the location stops being
active.
Yes standard Standard DOUBLE — Both No You can enter the standard
Hours Weekly weekly hours for a loca
Hours tion.
Yes timezone Timezone STRING — Both No You can enter the time
zone for the location.
ard.

20

20

2.1.9 Location Group
hris-element id: locationGroup
Max.
description of the location
group than the short
Name can provide, enter it
here.

tinguish the different loca
tion groups from each
other.

name for the location
group here.
Yes start-date Start Date DATE — Both Yes Enter the date the location
group becomes active.
the location group stops
being active.
ard.

20

20

2.2 Job-Related Objects A-Z
2.2.1 Job Classification
Job Classification is now an MDF Generic Object. Use the Configure Object Definition page to maintain 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.
Max.
Yes defaultEm Employee Picklist 32 As defined No If a customer configured

ployeeClass Class in the Con picklist is added in Job In
figure Ob formation, then that infor
ject Defini- mation is defaulted here.
tion page.
Yes defaultJo Job Level Picklist 32 As defined No If a customer configured

bLevel
in the Con picklist is added in Job In
figure Ob formation, then that infor
tion page.
Yes defaultSu Supervisor Picklist — As defined No If a customer configured

pervisorLe Level in the Con picklist is added in Job In
vel figure Ob formation, then that infor
tion page.
in the Con description of the job clas
figure Ob sification than the short
ject Defini- name can provide, enter it
tion page. here.
Yes fulltimeEm Is Full Time Boolean — As defined No Enter “Yes” to indicate that
ployee Employee in the Con employees with this classi
figure Ob fication work full time or
ject Defini- “No” to indicate that they
tion page. work part time. No picklist
required.

Max.
Yes effectiveS- Start Date Date — As defined Yes Enter the date the job clas
tartDate in the Con sification becomes active.
figure Ob
ject Defini-
tion page.
veEndDate
in the Con the job classification stops
figure Ob being active.
ject Defini-
tion page.
ject Defini-
tion page.
Yes external Job Code String 32 As defined Yes Define a unique code by
figure Ob tinguish the different job
ject Defini- classifications from each
tion page. other.
Yes jobFunction Job Func JobFunction As defined No You can enter the job func
tion GO in the Con tion relating to this job
figure Ob classification.
ject Defini-
tion page.
Yes name Job Title Translatable 90 As defined No You can enter a short
in the Con name for the job classifica-
figure Ob tion here.
ject Defini-
tion page.
Yes parentJob Parent Job JobClassifi- — As defined No You can enter the job code
Classifica Classifica- cation GO in the Con that is on the next level up
tion tion figure Ob in the job code hierarchy.
ject Defini-
tion page.
Yes payGrade Pay Grade payGrade — As defined No You can enter the pay
FO in the Con grade for this job classifi-
figure Ob cation.
ject Defini-
tion page.

Max.
Yes regularTem Regular/ Picklist 32 As defined No This field indicates

porary Temporary in the Con whether the employee is
figure Ob regular or temporary.
ject Defini-
tion page.
Yes standard Standard Decimal — As defined No You can enter the standard
Weekly Weekly in the Con weekly hours for the job
Hours Hours figure Ob classification.
ject Defini-
tion page.
Yes worker Workers' String 32 As defined No This is a custom configura-

CompCode Comp Code in the Con ble picklist to list codes for
figure Ob Workman's Compensa
ject Defini- tion. This is most com
tion page. monly used in the US.
2.2.2 Job Function
Job Function is now an MDF Generic Object. Use the Configure Object Definition page to maintain this object.
generic object id: JobFunction
Max.
in the Con description of the job func
figure Ob tion than the short name
tion page.
Yes external Job Func String 32 As defined Yes Define a unique code by
Code tion ID in the Con which the system can dis
figure Ob tinguish the different job
ject Defini- functions from each other.
tion page.

Max.
ject Defini-
tion page.
Yes effectiveS- Start Date Date — As defined Yes Enter the date the job
tartDate in the Con function becomes active.
figure Ob
ject Defini-
tion page.
in the Con
veEndDate the job function stops be
figure Ob
ing active.
ject Defini-
tion page.
Yes jobFunction Job Func Picklist 32 As defined No This is customer configu-

Type tion Type in the Con rable picklist to use if clas
figure Ob sification or grouping of
ject Defini- job functions is required.
tion page.
Yes name Name Translatable 90 As defined No You can enter a name for
in the Con the job function here.
figure Ob
ject Defini-
tion page.
Yes parentJob Parent JobFunction — As defined No You can enter the function
Function Function GO in the Con code that is on the next
Job figure Ob level up in the function
ject Defini- code hierarchy.
tion page.
2.3 Pay-Related Objects A-Z
2.3.1 Frequency
hris-element id: frequency

Max.
Yes annualiza Annualiza LONG — Both Yes Use this field to record the
tionFactor tion Factor number of times in a year
an employee would be paid
at this frequency to ach
ieve an annual salary. Ex
ample: Enter “12” if the
employee is paid monthly.
description of the fre
quency than the short
name can provide, enter it
here.
Yes external Frequency STRING 32 Both Yes Define a unique code by

Code ID which the system can dis
tinguish the different fre
quencies from each other.
Yes name Name STRING 90 Both No You can enter a name for
the frequency here.
ard.

20

20
2.3.2 Pay Calendar
Pay Calendar is now an MDF Generic Object. Use the Configure Object Definition page to maintain this object.
generic object id: PayCalendar

Max.
Yes payGroup Pay Group STRING — As defined Yes Enter the code for the pay
in the Con group to which this pay pe
figure Ob riod applies.
ject Defini-
tion page.
Yes toPayPer Pay Period DATE — As defined Yes Enter the date a given pay
iod.payPer
Begin Date in the Con period starts. Example:
iodBegin
figure Ob First of the month.
Date
ject Defini-
tion page.
Yes toPayPer Pay Period DATE — As defined Yes Enter the date a given pay
iod.payPer End Date in the Con period ends. Example: 16th
iodEndDate figure Ob of the month.
ject Defini-
tion page.
Yes toPayPer Pay Check DATE — As defined Yes Enter the date a pay check
iod.pay Issue Date in the Con is issued for a pay period.
CheckIssue figure Ob Example: 18th of the
Date ject Defini- month.
tion page.
Yes toPayPer Pay Periods LONG — As defined No You can enter the number
iod.cust_pay
Per Year in the Con of pay periods in a year.
PeriodsPer
figure Ob
Year
ject Defini-
tion page.
Yes toPayPer Offcycle BOOLEAN — As defined No This field indicates

iod.offcycle
in the Con whether a payroll run is a
figure Ob special payroll execution in
ject Defini- addition to a regular (or
tion page. normal) payroll execution.
For example, for the month

of December, the regular
(normal) payroll execution
is scheduled on Dec 28. On
December 30, an off-cycle
run is scheduled to be exe
cuted for a year-end bo
nus.

Max.
Yes toPayPer Processing STRING 256 As defined No You can enter an identifier
iod.proces
Run ID in the Con for pay processing runs
singRunId
figure Ob here.
ject Defini-
tion page.
Yes toPayPer Run Type STRING 256 As defined No The list of values comes
iod.runType
in the Con from the picklist
figure Ob RUNTYPE.
ject Defini-
tion page.
2.3.3 Pay Component
hris-element id: payComponent
Max.
Yes basePay Base Pay STRING — Both No This attribute is only

Compo Component shown when the Pay Com
nentGroup Group ponent Type is set to Per
centage. It is hidden when
the Pay Component Type
is set to Amount. In case
Pay Component Type =
"Percentage", a Pay Com
ponent or Pay Component
Group needs to be se
lected to define the
amount on which percent
age is to be applied.
Yes canOverride Can Over BOOLEAN — Both No You can enter “Yes” if it will
ride be possible to override this
pay component for individ
ual employees to whom it
would otherwise apply, or
“No” if it will not be possi
ble.

Max.
Yes currency Currency CURRENCY — Both No You can specify the cur
rency in which the pay
component is paid.
Yes description Description STRING 128 Both No If you need a longer de
scription of the pay com
ponent than the short
name can provide, enter it
here.
Yes displayOn Display on BOOLEAN — Both No Controls whether this pay

SelfService Self Service component will be dis
played in manager self-
service
the pay component stops
being active.
Yes external Pay Compo STRING 32 Both Yes Define a unique code by
Code nent ID which the system can dis
tinguish the different pay
components from each
other.
Yes frequency Frequency STRING — Both Yes Specify how often a pay
Code component is paid. Exam
ple: annually.
Yes is-earning Is Earning BOOLEAN — Both No You can specify whether

the pay component is an
earning or a deduction.
Yes IsRelevant Relevant for BOOLEAN — None No Here you can specify if this
ForAdvance Advance pay component is used in
Payment the advance payments
process.
Possible values are Yes and

No.

Max.
Yes maxFrac Maximum LONG — None No In this field you can define
tionDigits Decimal Pla for each pay component
ces how many decimals are
maximally shown in the
amount field.
You can choose a number

from 0 to 5. If you do not
enter any value, the sys
tem uses the following
value:
1. The value defined for

the
maximumFraction
Digits XML attrib
ute that has been de
fined for
payComponentRec
urring or
payComponentNon
Recurring in the
Succession Data
Model
2. If the aforementioned
XML attribute has not
been defined, the de
fault value is 3.
Yes name Name STRING 90 Both No You can enter a name for
the pay component.
Yes number Number DOUBLE — Both Edit This field supports Unit-
based pay components as
well as number of units.
When Number is selected,

Unit of Measure and Rate
are shown.

Max.
Yes payCompo Pay Compo STRING — Both Yes Possible values are
nentType nent Type Amount, Percentage and
Number. Do not configure
this as a picklist.
For more information on

setting up number as a
possible value, refer to the
Creating a Pay Component
topic in the Implementing
Employee Compensation
Data in Employee Central
guide.
Yes payCompo Pay Compo DOUBLE — Both No You can specify a value for
nentValue nent Value the pay component here.
Yes rate Rate DOUBLE — Both No This field supports Unit-

based pay components,
typically price per unit.
Yes recurring Recurring BOOLEAN — Both No You can indicate whether

the pay component is paid
regularly or is just a one-
time payment.
Yes selfService Self Service STRING — Both No

 Note
Description Description
This field is only dis
played in the founda
tion object and will not
show up anywhere
else, even if filled with
text. It was originally
intended to be used as
a description for the
Manager Self-Service
UI but was never im
plemented.
Yes start-date Start Date DATE — Both Yes Enter the date the pay
component becomes ac
tive.

Max.
Yes taxTreat Tax Treat STRING — Both No You can indicate whether
ment ment the pay component is
taxed or not.
The list of values comes

from the picklist
TAXTREATMENT.
Yes target Target BOOLEAN — Both No You can enter “Yes” in this
field if the pay component
is a target figure or per
centage, or enter “No” if it
is not.
Yes unit-of- Unit of STRING — Both No This field supports Unit-

based pay components,
measure Measure
for example, Day, Hour,
and so on.
Yes usedFor Used for STRING — Both No Controls whether this pay
CompPlan Comp Plan component will be used by
ning ning the comp module. Possible
values are None, Comp,
Varpay and Both. Do not
configure this as a picklist.
ard.

20

20
2.3.4 Pay Component Group
hris-element id: payComponentGroup

Max.
Yes currency Currency CURRENCY — Both No You can specify the cur
components in this group
are paid.
description of the pay
component group than the
short name can provide,
enter it here.
the pay component group
stops being active.
Yes external Pay Compo STRING 32 Both Yes Define a unique code by
Code nent Group which the system can dis
ID tinguish the different pay
component groups from
each other.

name for the pay compo
nent group.
Yes showOn Display on BOOLEAN — Both No You can choose whether to

CompUI Comp UI have the pay component
group displayed on the
component group be
comes active.
Yes systemDe System De BOOLEAN — None No You can enter “Yes” in this
fined fined field if the system gener
ates pay component
groups for you, based on
other data, or “No” if they
are created manually.

Max.
Yes useForCom Use for BOOLEAN — Both No You can choose whether
paratioCalc Comparatio the pay component group
Calculation should be used as part of
the comp ratio calculation.
Yes useForRan Use for BOOLEAN — Both No You can enter “Yes” if this
gePenetra Range Pene pay component group can
tion tration be used to determine how
far into a given pay range
an employee has pro
gressed or “No” if it is not
used for that.
ard.

20

20
2.3.5 Pay Grade
hris-element id: payGrade
Max.
grade than the short name
can provide, enter it here.

Max.
the pay grade stops being
active.
Yes external Pay Grade STRING 32 Both Yes Define a unique code by
grades from each other.

name for the pay grade.
Yes paygradeLe Pay Grade LONG — Both No You can use this field to
vel Level enter the level of the rele
vant pay grade. For exam
ple, level 1 for a new
starter.
grade becomes active.
ard.

20

20
2.3.6 Pay Group

Pay Group is now an MDF Generic Object. Use the Configure Object Definition page to maintain this object.
generic object id: PayGroup

Max.
Yes dataDeli DataDeli String 32 As defined No

 Note
miter miter in the Con
figure Ob This field is not used
ject Defini- by Employee Central.
tion page.
Yes decimal Decimal String 32 As defined No

 Note
Point Point in the Con
figure Ob This field is not used
ject Defini- by Employee Central.
tion page.
in the Con description of the pay
figure Ob group than the short name
tion page.
Yes earliest Earliest Date — As defined No Define the earliest date for
ChangeDate Change in the Con which payroll relevant
Date (for figure Ob changes can be made for
Payroll) ject Defini- an employee assigned to
tion page. this pay group.
Yes effectiveS- Start Date Date — As defined Yes Enter the date the pay
tartDate in the Con group becomes active.
figure Ob
ject Defini-
tion page.th
Yes effecti- End Date Date — As defined No You can also enter a date
veEndDate in the Con the pay group stops being
figure Ob active.
ject Defini-
tion page.
ject Defini-
tion page.
Yes external Pay Group String 32 As defined Yes Define a unique code by
in the Con
figure Ob
ject Defini-
tion page. groups from each other.

Max.
Yes lag Lag Number — As defined No Indicates the number of

in the Con pay periods that the em
figure Ob ployee is paid in arrears. If
ject Defini- the employee is paid cur
tion page. rent, set the lag to 0. This
information is stored in
Employee Central to be
transmitted to payroll.

in the Con name for the pay group.
figure Ob
ject Defini-
tion page.
Yes payment PayFre Picklist 32 As defined No Specify how often a pay

Frequency quency in the Con group is paid.
figure Ob
ject Defini-
tion page.
Yes payrollVen PayrollVen String 32 As defined No If your company uses an

dorId dorID in the Con external contractor to
figure Ob process its payroll, enter
ject Defini- the contractor's ID here.
tion page.
Yes primary Primary String 256 As defined No You can enter an e-mail ad
ContactE ContactE in the Con dress for the group's main
mail mail figure Ob contact.
ject Defini-
tion page.
Yes primary Primary String 256 As defined No You can enter the identifier
ContactId ContactID in the Con of the main contact for this
figure Ob group.
ject Defini-
tion page.
Yes primary Primary String 256 As defined No You can enter the name of
Contact Contact in the Con the group's main contact.
Name Name figure Ob
ject Defini-
tion page.

Max.
Yes secondary Secondary String 256 As defined No You can enter an e-mail ad
ContactE ContactE in the Con dress for the group's sec
mail mail figure Ob ondary contact.
ject Defini-
tion page.
Yes secondary Secondary String 256 As defined No Enter the identifier of the
ContactId ContactID in the Con secondary contact for this
figure Ob group.
ject Defini-
tion page.
Yes secondary Secondary String 256 As defined No You can enter the name of
Contact Contact in the Con the group's secondary
Name Name figure Ob contact.
ject Defini-
tion page.
Yes weeksInPay WeeksIn Number — As defined No You can specify how many
Period PayPeriod in the Con weeks a pay period for this
figure Ob group should last.
ject Defini-
tion page.
2.3.7 Pay Range
hris-element id: payRange
Max.
Yes currency Currency CURRENCY 256 Both No You can specify the cur
range is indicated.
range than the short name

Max.
Yes end-date End Date DATE — None No This is the end date the
previous pay range stops
being effective. The sys
tem calculates the end
date automatically de
pending on the start date
entered.
Yes external Pay Range STRING 32 Both Yes Define a unique code by
ranges from each other.
Yes frequency Frequency STRING — Both Yes Define how often a pay
Code component is paid — for
example, annually.

from the frequency foun
dation object.
Yes maximum Maximum DOUBLE — Both No Enter the maximum pay

Pay Pay for this pay range, for ex
ample: 80,000.
Yes midPoint Mid Point DOUBLE — Both No Enter the mid point for this
pay range that lies be
tween the minimum and
the maximum pay, for ex
ample: 75,000.
Yes minimum Minimum DOUBLE — Both No Enter the minimum pay for
Pay Pay this pay range, for exam
ple: 70,000.

name for the pay range.
range becomes effective.
Yes custom- Custom STRING 256 None No You can use these fields for
20

Max.
Yes custom- Custom DATE — None No fields supplied as stand

date1–10 Dates 1–10 ard.
Yes custom- Customer LONG — None No

20
Yes custom- Custom DOUBLE — None No

20
2.4 Other Objects A-Z
2.4.1 Dynamic Role Assignment
hris-element id: dynamicRoleAssignment
Max.
Yes businessU Business STRING — Both No The list of values comes

nit Unit from the business unit
foundation objects that are
available in the system.
Yes company Legal Entity STRING — Both No The list of values comes
from the legal entity foun
dation objects that are
If you don't need this field,

you can set the visibility to
“none”.

Max.
Yes costCenter Cost Center STRING — Both No The list of values comes
from the cost center foun

“none”.
Yes department Department STRING — Both No The list of values comes

from the department foun

“none”.
Yes jobCode Job Classifi- STRING — Both No The list of values comes
cation from the job classification
foundation objects that are

“none”.
Yes location Location STRING — Both No The list of values comes

from the location founda
tion objects that are availa
ble in the system.

“none”.
Yes payGrade Pay Grade STRING — Both No The list of values comes
from the pay grade foun

“none”.

Max.
Yes payGroup Pay Group STRING — Both No The list of values comes
from the pay group foun

“none”.
Yes person Approver STRING — Both No Depending on what you

have selected in the
resolverType field,
you can either select a dy
namic group here, a posi
tion, or a specific person
as workflow approver. For
the person, the list of val
ues comes from the users
that have been created in
the system.
Yes resolver Approver STRING — Both Yes In this field, you define who
Type Type should approve the work
flow request. The possible
values are:
● Person
● Dynamic Group
● Position (if Position
Management is ena
bled)
This field is always manda

tory and visible; you can
only change the label.
2.4.2 Dynamic Role
hris-element id: DynamicRole

Max.
description of the dynamic
role than the short name

tinguish the different dy
namic roles from each
other.

name for the dynamic role.
ard.

20

20
2.4.3 Event Reason
hris-element id: eventReason
Max.
grade than the short name

Max.
Yes emplStatus EmplStatus STRING 45 None No You can use this field to
enter the change in status
that is causing the relevant
event. Example: “Termina
tion” if the relevant em
ployee has left the com
pany.
the event reason stops be
ing active.
Yes event Event STRING 45 Both Yes Use this field to describe
the event covered by this
event reason.

tinguish the different event
reasons from each other.
Yes implicit-po Follow-Up STRING 32 None No You can use this field to
sition-action Activity in specify which event rea
Position sons trigger a follow-up ac
tivity on the assigned posi
tion, such as reclassifica-
tion or transfer.
This field is relevant when

you have activated Posi
tion Management. The list
of values comes from the
predefined picklist
positionActionType
.
Yes inside-work- Display in STRING 256 Both No You can define which event
experience Internal Job reason should be dis
History played in the Internal Job
portlet History block in the Em
ployee Profile. This block is
a custom background
block on the Employee
Files page.

name for the event reason.

Max.
Yes payroll- Payroll STRING 4 Both No This field is required for

event Event payroll integration with
SAP ERP. It is used to store
additional events to those
delivered by SAP Success
Factors. Leave the maxi
mum length to 4. For more
information, refer to the
Employee Central Payroll
Implementation Guide.
Yes start-date Start Date DATE — Both Yes Enter the date the event
reason becomes active.
ard.

20

20
2.4.4 WfConfig
hris-element id: wfConfig

Max.
description of the WFCon
fig than the short name
Yes escalation Escalation Generic Ob — Both No You can use this for the
ject auto-escalation feature
based on the Escalation
MDF object.

tinguish the different work
flow configurations from
each other.
Yes future- Alternate STRING — Both No See note for future-dated-

alternate-workflow after
dated-alter Workflow
table.
nate-work
flow
Yes is-cc-link-to- Redirect CC BOOLEAN — Both No See note for is-cc-link-to-

approval- Users to approval-page below ta
page Workflow ble.
Approval
Page
Yes is-delegate- Is Delegate BOOLEAN — Both No See note for is-delegate-

supported after table.
supported Supported

name for this WfConfig.
Yes remind-in Remind in LONG — Both No See note for remind-in

days after table.
days Days
Yes custom- Custom STRING 256 None No You can use these fields for
ard.
Yes custom- Custom DATE — None No
Yes custom- Customer LONG — None No

20

Max.
Yes custom- Custom DOUBLE — None No

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.
2.4.5 wfConfig Contributor
hris-element id: wfConfigContributor

Max.
Yes actorRole Contributor STRING — Both Yes Select one of the following
contributors:
● Employee
● Employee Manager
Manager
● Employee HR
● Matrix Manager
● Custom Manager
● Second Manager
● Additional Manager
Yes actorType Contributor STRING 32 Both Yes Select one of the following
Type contributor types:
● Role
● Dynamic Role
● Dynamic Group
● Person
● Position
No context Context STRING 32 Both No When the transaction that

requires an approval im
plies a manager change,
the context allows you to
determine which manager
has to approve:
● Source (the initial

manager)
● Target (the new man
ager)
No description Description STRING 128 Both No If you need a more detailed

description of the WFCon
fig Contributor than the
short name can provide,
enter it here.
No external Code STRING 32 Both Yes Define a unique code by

tinguish the different con
fig contributors from each
other.

Max.
No name Name STRING 90 Both No You can enter a short

name for this config con
tributor.
2.4.6 wfConfig CC
hris-element id: wfConfigCC
Max.
Yes actorRole CC Role STRING — Both Yes Select one of the following
CC roles:
● Employee
Manager
● Employee HR
● Matrix Manager
● Custom Manager
● Second Manager
Yes actorType CC Role STRING 32 Both Yes Select one of the following
Type CC role types:
● Role
● Dynamic Role
● Dynamic Group
● Person
● External Email
● Position

Max.
No context Context STRING 32 Both No When the transaction that

has to approve:

manager)
ager)
No description Description STRING 128 Both No If you need a more detailed

description of the CC Role
than the short name can
No external Code STRING 32 Both Yes Define a unique code by

tinguish the different CC
Roles from each other.
No name Name STRING 90 Both No You can enter a short

name for this CC Role.
2.4.7 wf Step Approver
hris-element id: wfStepApprover
Max.
Yes actionType Edit Trans STRING 256 None No See note for actionType be
low.
action

Max.
Yes approver Approver STRING — Both Yes Select one of the following
Role Role approver roles:
● Employee
Manager
● Employee HR
● Matrix Manager
● Custom Manager
● Second Manager
Yes approver Approver STRING 32 Both No Select one of the following

Type Type approver types:
● Role
● Dynamic Role
● Dynamic Group
● Position
Yes context Context STRING 32 Both No When the transaction that

has to approve:

manager)
ager)
Yes skipType No Approver String 32 Both No See note for SkipType be
Behavior low.
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.

3 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
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.
3.1 Person Objects A- Z
3.1.1 Addresses
Addresses (hris-element-id: homeAddress)

Person Object Tables PUBLIC 51
The fields of this element are defined in the country-specific Succession Data Model.
Standard Field ID Field Label Data Type Max. Default Vis Is Re How To Use This Field
Length ibility quired?
Yes item-id Item ID LONG — None No This field is used for inter
nal 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.

from the picklist
addressType. The pre-
configured list of values
contains the following:
● Home
● Mailing
● Benefits
● Payroll
You can add more values

to the picklist
addressType by export
ing and importing the pick
list using the Admin Tools.
Yes address1-20 Address1-20 STRING 256 Both No You can enter 20 lines for
address here.
Yes city City STRING 256 Both No This is where you enter the
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.

52 PUBLIC Person Object Tables
Yes zip-code Zip Code STRING 256 Both No This is where you enter the
ZIP code of the place the
employee lives in.
Yes country Country STRING 256 Both Yes The list of values comes
from the predefined pick
list <country>.
 Note
You must not config-
ure any picklist or
child picklist for the
<country> field, as
this field is hard-coded
in the system.
If you want to define coun

try-specific addresses,
configure the fields for the
corresponding country in
the homeAddress HRIS-
element in the country-
specific Succession Data
Model.
No address1– Alt1 ad STRING 256 None No You can enter 20 lines for
alt1 (lines dress1 the address in alternate
1-20) characters here.
Address information can

be displayed in up to two
alternate character fields.
A link to the alternate
character fields is dis
played in “Edit” mode, and
the non-alternate charac
ter fields are already filled
with the home address in
formation that has been
entered before.
No city-alt1 Alt1 City STRING 256 None No You can enter the city or
town in alternate character
1 here.

No state-alt1 Alt1 State STRING 256 None No You can enter the state in
alternate character 1 here.
No province- Alt1 Prov STRING 256 None No You can enter the province
alt1 ince in alternate character 1
here.
No county-alt1 Alt 1 County STRING 256 None No You can enter the county in
No zip-code- Alt1 Zip STRING 256 None No You can enter the zip code
alt1 Code in alternate character 1
here.
No country-alt1 Alt1 Country STRING 256 None No You can enter the country
in alternate character 1
here.
No address1– Alt2 Ad STRING 256 None No You can enter 20 lines for
alt2 (lines dress1 address in alternate char
1-20) acter 2 here.
No city-alt2 Alt2 City STRING 256 None No You can enter the city in al
ternate character 2 here.
No state-alt2 Alt2 State STRING 256 None No You can enter the state in
No province- Alt12 Prov STRING 256 None No You can enter the province
alt2 ince in alternate character 2
here.
No county-alt2 Alt 2 County STRING 256 None No You can enter the county in
No zip-code- Alt2 Zip STRING 256 None No You can enter the zip code
alt2 Code in alternate character 2
here.
No country-alt2 Alt2 Coun STRING 256 None No You can enter the country
try in alternate character 2
here.

Yes attachment- Attach LONG — Both No

 Note
id ments
This field can be
added either to the
SDM or the CSF SDM.
If the field is added to
SDM, then it is availa
ble for all countries.
Attachments can be up

loaded using this field.
Yes emp-users- Employ STRING 50 None No This field is filled with the
sys-id ment Users users_sys_id of the em
Sys ID ployee on a global assign
ment when a host country
address is created, thereby
linking the address to the
employment.
 Note
This field is never visi
ble on the UI.
No end-date End Date DATE — None No This is the end date the
previous home address
stops being effective. The
system calculates the end
date automatically de
entered.
Yes notes Note STRING 4000 Both No This is a text field where
the user can enter addi
tional information if re
quired.
 Note
This field can't be dis
played on the Em
ployee Profile.

ard.
No custom- Custom LONG — None No

20

20
No custom- Custom STRING 256 None No

string1-20- Strings 1-20
alt1 in Language
1

date1-10-alt1 Dates 1-10 in
Language 1

long1-20- Numbers
alt1 1-20 in Lan
guage 1

double1-20- Decimals
alt1 1-20 in Lan
guage 1
string1-20- Strings 1-20 data for the second lan
alt2 in Language guage not covered by the
ard.
date1-10- Dates 1-10 in
alt2 Language 2


double1-20- Decimals
alt2 1-20 in Lan
guage 2

long1-20- Numbers
alt2 1-20 in Lan
guage 2
No script Script STRING 128 None No Picklist ID is LANGUAGE

SCRIPTNAME
No script-alt1 Script in STRING 128 None No
Language 1
No script-alt2 Script in STRING 128 None No

Language 2
 Note
Two sets of alternate languages are supports for Addresses. Alternate fields can be enabled in the Succession
Data Model rather than in the Country-Specific Data Model. CSF 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.
3.1.2 Biographical Information
Biographical Information (hris-element-id: personInfo)
Yes attachment- Attach LONG — Both No If the biographical info of

id ments an employee has a docu
ment such as birth certifi-
cate, this can be uploaded
in this field.

Yes birth-name Birth Name STRING 128 Both No You can enter the employ
ee’s birth name here, for
example: Smith.
This field is required if you

use payroll integration with
SAP ERP.
Note: If you have specified

a formal name format (us
ing 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: per
sonalInfo instead.
Yes country-of- Country Of COUNTRY 100 Both No You can enter the employ
birth Birth ee's country of birth here.

list country.
Yes date-of- Date Of DATE — Both No You can enter the employ
birth Birth ee's date of birth here.
Yes date-of- Date Of DATE — None No You can enter the employ
death Death ee's date of death here.
Yes person-id- Person Id STRING 32 Both No This field contains the em
external ployee ID. You can man
ually assign employee IDs
or have system-generated
IDs. When you use system-
generated IDs, set the visi
bility to “view” and add
the attribute allow-
import=”true”.

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

SAP ERP.
Yes region-of- Region Of STRING 100 Both No Enter the region where the
birth Birth employee was born. This is
a free text field.
 Note
The behavior of this
field changes when
payroll integration is
enabled in your in
stance. The system
will dynamically
change the field be
havior based on the
value given in the
<country of
birth> field. Also, de
pending on the
<country of
employment>, this
field may be made
mandatory. For more
information, refer to
the end of this docu
ment.

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

uuid UUID unique identifer of employ
ees or their dependents,
which you can use to inte
grate Person Data with
other modules like On
boarding, Learning, Re
cruiting, Talent, and so on.
You can manually assign a
value or have system-gen
erated IDs.
To use with data imports,

set the visibility to
“view” and add the at
tribute allow-
import=”true”.
 Note
Once this field is
populated with a
value, it cannot be
changed.
ard.

20

20
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.
Countries Supported
If Country of Employment If Country of Birth matches,

matches, convert field to convert field to a picklist
Country (Country Code) mandatory? field? Picklist ID used
Italy (ITA) Yes Yes PROVINCE_ITA
France (FRA) Yes Yes DEPARTMENT_FRA
Venezuela (VEN) Yes Yes REGION_VEN
Brazil (BRA) No Yes STATE_BRA
Chile (CHL) No Yes REGION_CHL
Mandatory or Not
Italy France Venezuela Brazil Chile Other
region-of-birth is True True True Value in data Value in data Value in data
mandatory model model model
value =
Picklist or Not
Italy France Venezuela Brazil Chile Other
region-of-birth is True True True True True Value in data

picklist 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 from the backend. 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.
● Does not work in the New Hire process. It works only on Employee Profile page, and only for the employees, not
their dependents.
● Does not work for future hires since this is based on the current active job information record.
● Does not work properly if the country of birth for the country of employment is null/empty.
3.1.3 Dependents
Dependents (hris-element-id: personRelationshipInfo)
Yes item-id Item ID LONG — None No This field is used for inter
on the UI.
Yes attachment- Attach LONG — No No If the dependent of an em

id ments ployee has a document
such as birth certificate,
this can be uploaded using
this field.
Yes is-accompa Accompany STRING — Both No When you add a global as
nying-de ing signment, you can select
pendent this field in the
Dependents block to deter
mine if a dependent joins
the employee on the global
assignment.

No.
You must have activated

Global Assignments in the
Admin Center.

Yes is-address- Copy Ad BOOLEAN 3 None No If the address of an em

same-as- dress from ployee’s dependent is the
person Employee same as the employee’s
address, you can select
Yes to copy the address in
formation for the depend
ent. If the employee’s ad
dress subsequently
changes, this change is not
reflected in the depend
ent's address information
unless you select Yes
again.
Yes is-benefi- Is Benefi- BOOLEAN — Both No When you add pension

ciary ciary payouts, you can select
this field to determine
whether a dependent is
the beneficiary of an em
ployee’s pension payout in
the event of that employ
ee's death. Possible values
are Yes and No.
You must have activated

Pension Payouts.

Yes relationship- Relationship STRING 50 Both Yes You have to define the rela
type tionship of the dependent
to the employee.

from the picklist
personRelationship
Type. Possible values are:
● Child
● Stepchild
● Child of Domestic
Partner
● Spouse
● Registered Partner
● Divorced Spouse
● Father
● Mother
● Brother
● Sister
● Related Persons
● Domestic Partner
ard.

20

20
3.1.4 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.

3.1.5 Email
Email (hris-element-id: emailInfo)
Yes email-ad Email Ad STRING 100 Both Yes Enter an email address
dress dress here.
Yes email-type Email Type STRING 32 Both Yes Enter the type of email ad
dress. The list of values
comes from the prede
fined picklist
ecMailType and uses
the following values:
● Personal
● Business
Yes isPrimary Is Primary BOOLEAN 1 Both No Indicate if the email ad

dress is the primary one.
No.
ard.

20

20
3.1.6 Emergency Contact
Emergency Contact (hris-element-id: emergencyContactPrimary)

Yes address Address STRING 1000 Both No You can enter the address
of the dependent here.
This field is only available
for dependents.
Yes dateOfBirth Date of Birth DATE — None No You can enter the date of
birth of the dependent
here. This field is only
available for dependents.
Yes ecNameAlt1 Name in Al STRING 256 None No You can enter the name of
ternate the dependent in alternate
Character 1 characters. This field is
only available for depend
ents.
Yes ecNameAlt2 Name in Al STRING 256 None No You can enter the name of
ternate the dependent in alternate
Character 2 characters. This field is
only available for depend
ents.
Yes email eMail STRING 100 None No You can enter the email
address of the contact per
son or dependent here.
Yes gender Gender STRING 2 None No You can define the gender
of the dependent here.
when the person identified
in the Primary Emergency
Contact block is a depend
ent. The list of values
comes from a predefined
picklist.
Yes isAddSa Copy Ad BOOLEAN — None No You can indicate whether
meAsEm dress from the dependent has the
ployee Employee same address as the em
ployee. This field is only

No.

Yes isDepend Dependent BOOLEAN — None No Define whether the person

ent is a dependent of the em
ployee.

No.
Yes isDisabled Disabled BOOLEAN — None No You can indicate if the de
pendent is disabled or not.
for dependents.

No.
Yes isEmergen Emergency BOOLEAN — None No Define whether the person

cyContact Contact is an emergency contact of
the employee.

No.
Yes isStudent Student BOOLEAN — None No You can indicate whether

the dependent is a stu
dent. This field is only

No.
Yes name Name STRING — Both No You can enter the full name
of the contact person or
dependent here.
Yes phone Phone STRING 256 Both No Enter the phone number of
the contact person or de
pendent here.
Yes second- Second STRING 256 Both No If the contact person or

phone Phone dependent has a second
phone number, you can
add it here.
No pri Primary STRING 1 Both No One of the contacts you

mary_flag enter in this block must be
the primary emergency
contact. Possible values
are Yes and No.

Yes relationship Relationship STRING 50 Both No You can define the rela
tionship of the contact
person or dependent with
the employee. The rela
tionship can be child,
spouse, and so on. The list
predefined picklist
relation.
Yes custom- Emergency STRING 256 None No You can use these fields for
string1 Contact data not covered by the
Custom fields supplied as stand
String 1 ard.
No custom- Custom STRING 256 None No

string2–20 Strings 2–
20


20

20
3.1.7 Global Information
Global Information (hris-element-id: globalInfo)

The fields of this element are defined in the country/region-specific Succession Data Model.
No country Country/ COUNTRY Both Yes The country/region-spe

Region cific fields shown as global
information depend on the
country you select here.
 Note
You must not config-
ure 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 informa
tion stops being effective.
The system calculates the
end date automatically de
entered.

Yes gender Gender STRING 256 None No To collect country/region-

Country
specific information re
Specific
lated to genders, enable
this field and define a pick
list that contains the gen
der 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 ig
nored by the system.
It is recommended to leave
the <Gender> field in
Personal Information
empty if you choose to
maintain the country/
region-specific field.
 Remember
Predefined picklists of
the country/region-
specific gender field
are available for Ger
many and India.
See the picklists with

ID gender_DEU and
gender_IND from
SAP Help Portal
SAP SuccessFactors
Employee Central
Configuration
Employee Central
Master Picklists . For

more information, see
Employee Central
Country/Region Spe
cifics.

No generic Generic STRING 256 None No The data covered by these

String1–30 String fields is country/region-
specific. You can find the
No generi Generic DATE None No fields defined for the cor
cDate1–20 Date responding country/region
in the Country/Region-
No generi Generic LONG None No
Specific Succession Data
cNumber1– Number
Model. These fields are de
40
fined by SAP SuccessFac
tors; you can't add your
own generic fields.
ard.
No custom- Custom DATE None No
No custom- Custom LONG None No

20
No custom- Custom DOUBLE None No

20
3.1.8 National ID Information
National ID Info (hris-element-id: nationalIdCard)
Yes attachment- Attach LONG — Both No If the national ID card of an

id ments employee has a document
such as passport or other
ID card, this can be up
loaded in this field.

Yes card-type National Id STRING 256 Both Yes Depending on the coun
Card Type try/region selected, the
corresponding national ID
card type is displayed in
this field, for example:
● Social Security Num

ber (for USA)
● Social Insurance
Number (for Canada)
Yes country Country STRING 100 Both Yes Select the country/region
in which the national ID
has been assigned from
the list of countries.
Yes isPrimary Is Primary BOOLEAN 1 Both No Indicate which national ID

is the primary one.
Yes isTemporary Temporary BOOLEAN 1 None No Indicate that a temporary

ID is available.
ID Available
Yes national-id National Id STRING 256 Both No Enter the number of the
national ID in the corre
sponding format, for ex
ample:
999–999–999
 Note
If you use only the Na
tional ID field, then it
can be set as a re
quired field. If you al
low temporary IDs in
the system, then Na
tional ID must not be
set to required.
You set up the country/

region-specific format in
the country-specific Suc
cession Data Model, where
you also define if the user
input is validated against a
specific format.

Yes temporary- Temporary STRING 256 None No Enter the temporary ID.
ID
id
Yes start-date Start Date — — Both No Enter the start date of the
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.
quired.
 Note
played on the Em
ployee Profile.
Yes cpam-id Cpam ID STRING 256 None No This field is specific to

France.
Yes deuev-code Deuev Code STRING 256 None No This field is specific to Ger
many.
ard.


20

20
3.1.9 Payment Information
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.
The fields of this element are defined in the Succession Data Model.
Yes payment- Payment STRING 20 None No This field is required if you

method Method have activated payroll inte
gration. It indicates how an
employee gets paid, for ex
ample:
● By bank transfer
● By check
● Cash
For more information

about how to set up payroll
integration, refer to the
SuccessFactors Em
ployee Central Payroll
guide.

3.1.10 Personal Information
Personal Information (hris-element-id: personalInfo)
Yes aboriginal- Aboriginal BOOLEAN None No

person Person
Yes attachment- Attach LONG None No

id ments
Yes birth-name- Birth Name STRING 128 Both No Here you can enter the
alt1 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 al
ternate language
fields.
Yes birth-name- Birth Name STRING 128 Both No Here you can enter the
alt2 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 al
ternate language
fields.

Yes birth-name Birth Name STRING 128 Both No Here you can enter the
employee's birth name.

SAP ERP.
Note: If you have specified

a formal name format (us
ing a birth-name) for your
legal entity and want to
replicate to SAP ERP,
specify the birth-name in
the hris-element-id: per
sonalInfo and leave birth-
name field in hris-element-
id: personlInfo empty.
Yes bilinguism- Bilingualism STRING 256 None No

code Code
Yes business- Business STRING 128 None No Here you can enter a busi
first-name First Name ness first name that may
be needed in some coun
tries or regions. For exam
ple, 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.
last-name Last Name ness last name that may
be needed in some coun
tries or regions. For exam
ple, 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.
first-name- First Name
ness first name in an alter
alt1 Alt1
nate language that may be
needed in some countries
or regions.

last-name- Last Name ness last name in an alter
alt1 Alt1 nate language that may be
or regions.
first-name- First Name ness first name in an alter
or regions.
last-name- Last Name ness last name in an alter
or regions.
Yes certificate- Certificate DATE — Both No Here you can enter the
start-date Start Date start date of the certificate
that confirms that the em
ployee is challenged.
Yes certificate- Certificate DATE — Both No Here you can enter the end
end-date End Date date of the certificate that
confirms that the em
ployee is challenged.
Yes challenge- Challenge STRING 1 Both No Here you can select if the
status Status employee is challenged.

No.
Yes community- Community SRING 256 None No

background Background
Yes country-of- Country/ STRING 256 None No

birth Region of
Birth
Yes date-of- Date of Birth DATE None No

birth

Yes display- Display STRING 128 Both No Here you can enter the dis
name Name play name of the em
ployee. For example, if an
employee with the official
Chinese name Shengjie
prefers to be called Jason,
you can enter Jason as the
display name.
Yes display- Display STRING 128 Both No Here you can enter an em
name-alt1 Name Alt1 ployee's display name in a
second language.
Yes display- Display STRING 128 Both No Here you can enter an em
name-alt2 Name Alt2 ployee's display name in a
third language.
Yes date-of- Date of DATE None No

death Death
Yes dateOfFirst Date of First DATE None No

EntryIn Entry in
France France
Yes disabled- Disabled BOOLEAN None No

veteran Veteran
No end-date End Date DATE None No This is the end date the
previous personal informa
tion stops being effective.
The system calculates the
end date automatically de
entered.
Yes expected- Expected DATE None No

retirement- Retirement
date Date
Yes first-name First Name STRING 128 Both Yes Enter the employee's first
name here.

Yes first-name- Alt1 First STRING 128 Both No You can enter the employ
alt1 Name ee's name in alternate
characters used by the
employee's native lan
guage.
You can enter the first

name in alternate charac
ter 1 here.
Yes first-name- Alt2 First STRING 128 Both No You can enter the first
alt2 Name name in alternate charac
ter 2 here.
Yes formal- Formal STRING 128 Both No Here you can enter the
name Name employee's formal name.
For external user integra

tion in Learning, set this to
not mandatory.
Yes formal- Formal STRING 128 Both No Here you can enter an em
name-alt1 Name Alt1 ployee's formal name in a
second language.
Yes formal- Formal STRING 128 Both No Here you can enter an em
name-alt2 Name Alt2 ployee's formal name in a
third language.

Yes gender Gender STRING 2 Both No The list of values is sys

tem-defined and can only
be enabled by the admin
using the Upgrade Center.
Do not configure this as a

picklist.

not mandatory.
Possible values are:
● Male
● Female
● Unknown
● Undeclared
● Others
To enable this list
from the Upgrade
Center:
1. Log on to Provi
sioning and se
lect the Admin
2.0 and Enable
Compensation
Admin 2.0
checkboxes.
2. Save your
changes.
3. Navigate to the
Upgrade Center.
4. Under Optional
Upgrades, select
Enhancement to
Gender Values –
Inclusion of Ad
ditional Gender
Values.
Note: The
changes applied
by the upgrade
can be reversed
within 10 days. To
reverse changes,

in the Upgrade
Center, select
View Recently
Completed Up
grades. On the
Completed Up
grades page, se
lect Undo against
Enhancement to
Gender Values.
Yes healthcare- Healthcare STRING 256 None No

no Number
Yes initials Initials STRING 128 Both No Here you can enter an em
ployee's initials, for exam
ple: J.D.
Yes is-overrid Customize STRING 128 Both No Here you can customize
den Name For the employee's name for
mat mat, by selecting the
country whose name for
mat you wish to use. You
can do this by clicking on
Options.
 Remember
If the changes to em
ployee's personal in
formation are man
aged by workflows, to
edit an employee's for
mal 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 Name STRING 128 Both Yes Enter the employee's last
name here.

Yes last-name- Alt1 Last STRING 128 Both No You can enter the last
ter 1 here.
Yes last-name- Alt2 Last STRING 128 Both No You can enter the last
ter 2 here.
Yes marital-sta Marital Sta STRING Both No The list of values comes
tus tus from the predefined pick
list ecMaritalStatus
and contains the following
values:
● Married
● Single
● Divorced
● Widow
● Unknown
● Cohabitation
● Separated
● Head of Household
● Partnership
● Cohabitation with
Contract (Nether
lands)
● Cohabitation without
Contract (Nether
lands)
● PACS (France)

not mandatory.
Yes middle- Middle STRING 128 Both No You can enter the employ
name Name ee's middle name here, if
existing.
Yes middle- Alt1 Middle STRING 128 Both No You can enter the middle
name-alt1 Name name in alternate charac
ter 1 here.
Yes middle- Alt2 Middle STRING 128 Both No You can enter the middle
name-alt2 Name name in alternate charac
ter 2 here.

Yes medal-vet Medal Vet BOOLEAN None No

eran eran
Yes name-for Name For STRING 128 Both No Here you can specify the
mat mat format of the employee's
name.
Yes name-for Name For STRING 128 Both No Users can select the name
mat-code mat Code format code from a list of
values at employee level.
The list shown in this field
is linked to the name for
mat configuration object
of Employee Central. Each
format that is defined in
this object is shown in the
field and the user can de
cide (on employee level)
which format is to be ap
plied to their name.
Yes name-prefix Prefix PICKLIST 128 Both No Here you can select an
honorary title before the
employee's name if appli
cable, for example van or
van der, and so on. The list
of values come from a pre
defined 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 Op
tional Upgrades in Up
grade Center.

Yes nationality Nationality STRING 128 Both No You can enter the employ
ee's nationality here, for
example:
● Germany
● USA

SAP ERP.

not mandatory.
 Note
There are validations
in the system to check
the Nationality, Sec
ond 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 ex
ternal system such as
Recruiting and/or On
boarding 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 na
tionality fields do not
have the same value in

all the nationality

fields.
Yes native-pre Native Pre STRING 256 Both No You can enter the prefer
ferred-lang ferred Lang red native language of the
employee.

list Language. The exter
nal code is the ISO 639
code for each language.
Stick to the ISO codes if
you consider integration
with SAP ERP.
quired.
 Note
played on the Em
ployee Profile.
Yes partner- Partner STRING 128 Both No Here you can enter the
name Name name of your partner.
Yes partner- Partner PICKLIST 128 Both No Here you can select an
name-prefix Name Prefix honorary title before the
employee's partner's
name if applicable, for ex
ample van or van der, and
so on. The list of values
come from a predefined
picklist nameprefix.
Yes preferred- Preferred STRING 128 Both No You can enter the employ
name Name ee's preferred name or
nickname.
Yes protected- Protected BOOLEAN None No

veteran Veteran
Yes religion Religion STRING 256 None No

Yes script Language Both No You can enter the language

Script script.
Yes script-alt1 Language Both No You can enter the language

Script script for the first alternate
language.
Yes script-alt2 Language Both No You can enter the language

Script script for the second alter
nate language.

Yes second-na Second Na STRING 128 Both No If the employee has a sec
tionality tionality ond nationality, you can
enter it in this field.
 Note
ond Nationality and
Second Nationality
Nationality.
provided from an ex
boarding 1.0 please
make sure that the
mapped to the right
right meaning. Also
all the nationality
fields.
Yes second-last- Second Last STRING 128 None No Enter the employee's sec
Name
name ond last name here.
Yes separated- Separated BOOLEAN None No

veteran Veteran

Yes since Marital Sta DATE 128 Both No You can enter the date
tus Since since when the marital sta
tus you indicated in the
field marital-status
is valid.
Yes salutation Salutation STRING 128 None No The list of values comes
list salutation and
contains the following
standard fields:
● Mr
● Mrs
● Ms
Yes second-title Second Title STRING 128 Both No Here you can enter the
second title, for example:
Phil. as the second title
of Dr. Phil. John Smith.

list secondtitle.
Yes suffix Suffix STRING 128 None No You can enter a name suf
fix, such as Jr, Sr, PhD, and
so on.

list namesuffix.

Yes third-nation Third Na STRING 128 Both No If the employee has a third
ality tionality nationality, you can enter it
in this field.
 Note
ond Nationality and
Second Nationality
Nationality.
provided from an ex
boarding 1.0 please
make sure that the
mapped to the right
right meaning. Also
all the nationality
fields.
Yes third-name Third Name 256 Both No If the person has a third
name, you can enter that
here.

Yes third-name- Third Name 256 Both No If the person has a third
alt1 name, you can enter that
here for the first alternate
language.
Yes third-name- Third Name 256 Both No If the person has a third
alt2 name, you can enter that
here for the second alter
nate language.
Yes title Title STRING 128 Both No Here you can enter an em
ployee's title, for example:
Dr. for Dr. John Smith.

list title.
Yes veteran Veteran BOOLEAN None No
Yes visible-mi Visible Mi BOOLEAN None No

nority nority
Yes custom- Preferred STRING 256 Both No You can enter the employ
string1 Name ee's preferred name here.
ard.

20

20
 Note
Two sets of alternate languages are supports for Personal Information. Alternate fields can be enabled in the
Succession Data Model rather than in the Country-Specific Data Model. CSF 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.

3.1.11 Phone Information
Phone Information (hris-element-id: phoneInfo)
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 Code STRING 32 Both No You can enter the code for
the region or state here.
Yes phone-num Phone Num STRING 100 Both Yes You can enter the phone
ber ber number here.
Yes extension Extension STRING 32 Both No You can enter the exten
sion of the phone number
here.
Yes isPrimary Is Primary BOOLEAN 1 Both No You can indicate which

phone number is the pri
mary one.
Yes phone-type Phone Type STRING 100 Both Yes The list of values comes
from the picklist
ecPhoneType and con
tains the following values:
● Home
● Business
● Billing
● Cell
● Fax
● Private Mobile
● Other
● Shipping
ard.


20

20
3.1.12 Social Accounts
Social Accounts (hris-element-id: imInfo)
Yes domain Domain STRING 100 Both No You can select the instant
messaging domain for
your social account, for ex
ample, Yahoo Messenger,
AOL Instant Messenger,
and so on.
You can add more domains

to the predefined picklist
imdomain.
Yes im-id Instant Mes STRING 100 Both Yes You can enter the ID that
saging ID identifies the user in the
instant messaging applica
tion.
Yes url URL STRING 256 Both No You can enter the corre
sponding URL to the in
stant messaging domain
here.
ard.


20

20
3.1.13 Work Permit Info
Work Permit Info (hris-element-id: workPermitInfo)
No attachment- Attach ATTACH — Both No You can upload a copy of

id ments MENT the work permit document
in different formats, for ex
ample, .doc, .ppt, .png, and
so on.
Yes country Country STRING 256 Both No This field is used to cap
ture the country/region for
which the document is
valid.

list ISOCountryList.
Yes document- Document STRING 256 Both No The type of the document
type Type for which the ID needs to
be captured is given in this
field.

from the predefined cas
cading picklist
permitdoctype, which
is filtered based on the
country/region selected in
the country field.

Yes document- Document STRING 256 Both No You can enter the title of
title Title the document.
Yes document- Document STRING 256 Both No You can enter the number
number Number of the document.
No entity-type Entity-type STRING 32 None No

 Note
In Employee Central
V1, 3 entity types were
supported. With Em
ployee Central V2,
only 1 (Work Eligibility)
is supported and the
other types are obso
lete. So this field is al
ways automatically set
to Work Eligibility.
Since only 1 type is

supported, this is al
ways set to not visible
in the system.
Yes expiration- Expiration DATE — Both No The work permit docu

date Date ment is valid until this
date.
Yes issuing-au Issuing Au STRING 256 Both No You can enter the authority
thority thority that issued the document.
Yes issue-date Issue Date DATE — Both Yes Enter the date when the
document was issued.
Yes issue-place Issue Place STRING 256 Both No You can enter the place
where the document was
issued.
Yes is-validated Validated BOOLEAN — Both No You can indicate if the

document has been vali
dated by somebody. Possi
ble values are Yes and No.

quired.
 Note
played on the Em
ployee Profile.
ard.

20

20

4 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-specific 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
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
Succession Data Model (SDM)
4.1 Employment Objects A - Z
4.1.1 Compensation Information
Compensation Information (hris-element-id: compInfo)

96 PUBLIC Employment Object Tables
Yes benefits- Benefits DOUBLE — None No This field is to show the

benefits calculation for
rate Rate
employees who have
highly variable compensa
tion, for example, employ
ees who work on commis
sion. This calculation de
termines their benefit cov
erage.
Yes compa-ratio Compa-ratio DOUBLE — View No This field is calculated by

the system; leave the visi
bility on “view”.
No event-rea Event-rea UNDEFINED — Both No If you have defined event

son-icode son-icode reason foundation objects,
this field contains the ex
ternal code of those event
reasons.
Yes flsa-status US FLSA STRING 256 Both No This field is moving to the
Status country-specific data
model as it is US-specific.
Yes job-level Job Level STRING 256 Both No This field is not in use for
Employee Central 2.0 and
must be configured with
visibility “none”.
Yes is-eligible- Is Eligible BOOLEAN — None No You can indicate if the em
for-benefits For Benefits ployee is eligible for bene
fits. Possible values are Yes
and No.
for-car For Car ployee is eligible for a com
pany car. Possible values
are Yes and No.
for-leave- for Leave ployee is eligible for leave
loading Loading loading. Possible values
are Yes and No.
Yes is-highly- Is Highly BOOLEAN — None No Here you indicate if an em

compen Compen ployee is highly compen
sated-em sated Em sated. Possible values are
ployee ployee Yes and No.

Employment Object Tables PUBLIC 97
Yes is-insider Insider As BOOLEAN — None No This field helps you to

Defined By track insider trading on the
Statute stock market. You can de
fine if an employee has ac
cess to insider information
and is thus considered an
insider according to the lo
cal insider law, for exam
ple, the Securities Ex
change Act in the USA.

No.
quired.
Yes pay-group Pay Group STRING — None No You can define the pay
group of the employee
here.
If you have defined pay

group foundation objects,
ternal code of those pay
groups.
 Caution
Do not add picklists
for this field.
Yes pay-type Pay Type STRING 256 Both No The list of values for the
pay type is predefined by
picklist PayType. Possi
ble 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 em
ployee.

Yes payroll-sys Payroll Sys STRING 32 None No Here you can enter the ID
tem-id tem Id of the payroll system used
for compensating the em
ployee.
Yes pensiona Pensionable DOUBLE — None No You can enter an amount

ble-salary Salary that defines the employ
ee's pensionable salary.
Yes range-pene Range Pene DOUBLE — View No This field is calculated by

tration tration the system; leave the visi
bility on “view”.
Yes salary Salary SALARY — Both No This field is not in use for
Employee Central 2.0 and
In Employee Central 1.0,

this field was a combina
tion of
salaryRateType,
salaryRateUnits and
salaryCurrencyCode
. This field has been re
placed with Recurring Pay
Components in Employee
Central 2.0.
Yes salaryRate Salary Rate STRING 50 Both No This field is not in use for
Type Type Employee Central 2.0 and
Yes salaryRa Salary Rate LONG — Both No This field is not in use for
teUnits Units Employee Central 2.0 and
Yes salaryCur Currency STRING 20 Both No This field is not in use for
rencyCode Employee Central 2.0 and

Yes seq-number Sequence LONG — Both No This field tells you the se
quence of transactions for
Number
that day, for example, 1 of
2, 2 of 2. This field is only
required for import, and
will appear in the import
template if you have ena
bled the field.
ard.

20

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.
4.1.2 Employee Information
Employee Information (hris-element-id: userAccountInfo)

Yes user-name User Name STRING 32 None Yes You can enter a unique
user name for new em
ployees during the hire
process. This value is also
displayed on the
Username field on the Tal
ent Profile page.
If this field has visibil

ity=”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 Suc
cession Data Model.
4.1.3 Employment Information
Employment Information (hris-element-id: employmentInfo)
See also Termination Information table further below
Yes assignment- Assignment STRING 256 Both Yes This is an identifier for the
id-external ID external employment of a user and
can be used for integra
tions with external sys
tems. It is unique and
case-sensitive.
This is a multipurpose field

that can be used for differ-
ent scenarios.
Yes benefits-eli- Benefits Eli DATE — Both No This is the start date from
gibility- gibility Start which the employee is eli
start-date Date gible for benefits.

Yes company New Assign STRING 256 Both Yes This field is required when
ment Com you have set up Concur
pany rent Employment in Provi
sioning.
Here you define the com

pany where the concurrent
employment takes place; it
can be the same company
as specified for the exist
ing employment.
Yes companyEx Company DATE — None Yes It is important to have this

itDate Exit Date field filled out when an em
ployee leaves the com
pany. From this date, the
legal obligation period for
when to purge the user
can be calculated.
Yes eligibleFor Eligible for BOOLEAN — Both No You can indicate if the em
Stock Stock ployee is eligible for stock.

No.
No employee Employee's BOOLEAN 10 None No The field indicates whether

FirstEm First Em this is the employee’s first
ployment ployment employment or not.
Yes firstDate- First Date STRING 256 Both No You can enter the employ
Worked Worked ee’s first date at the com
pany here.
If you use payroll integra

tion with SAP ERP, this
field is required for legal
reporting in the USA.
Yes initialOp Initial Op LONG — Both No This is the initial number of
tionGrant tion Grant options granted to the em
ployee.
Yes initialStock Initial Stock LONG — Both No This is the initial number of
Grant Grant stocks granted to the em
ployee.

No isContin Is Contin BOOLEAN 1 View No This field is used to denote

gentWorker gent Worker that a user is an external
worker.
 Note
Only enable this field if
contingent workforce
is enabled in your sys
tem.
If the isContingent
Worker field is present
in employmentInfo
HRIS Element, ensure
that its Visibility prop
erty is set to View and
Allow Import is set to
Yes to avoid valida
tions while saving your
changes.

Yes isECRecord Is EC Record FIXED 1 Both No This field is system gener

ated and is used to differ-
entiate Employee Central
users from other Em
ployee 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 Em
ployee Central Employ
ment wizard (Add New
Employee, Manage Pend
ing Hire, Add Contingent
Worker, Add Global Assign
ment, Add Concurrent Em
ployment), this value will
be set to 1, to indicate that
they are an Employee Cen
tral 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 sys
tem will not mark them as
an Employee Central user
and they will not be in
cluded in Employee Cen
tral functions, for example,
their data will not be
synced in the HRIS Sync.
The only way to correct

this is to FULL PURGE im
port their data in the cor
rect order.

The field is not visible in

the UI and can either be re
ported on using Advanced
Reporting or checked in
the Integration Center.
Yes isPrimary Is Primary BOOLEAN — Both No

 Note
You cannot use this
field because it has
been deprecated.
Yes jobCredit Job Credit STRING — Both No The job credit corresponds
to the seniority an em
ployee can acquire before
joining the company.
Yes jobNumber Employ STRING — View No This field has significance

ment Id when we implement multi
ple jobs concept, until then
it is defaulted to 1.
Yes original Original DATE — Both No If the employee has been

StartDate Start Date working for the company
before, enter the date of
the first hire in the organi
zation in this field.
No notes Note STRING 4000 Both No This is a text field where

quired.
Yes prevEm Previous STRING — Both No This field shows the previ
ployeeId Employ ous employee ID if the em
ment ID ployee has been at the
company 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 com
pany before.

Yes primaryEm Primary Em DATE — None No This is a transient field

ployment
ployment used for Concurrent Em
Date
Date ployment, when updating
primary and secondary
employments.
Yes professio Professional DATE — Both No You can use this field to
track dates for professio
nalService Service Date
nal experience.
Date
Yes seniority Seniority DATE — Both No This is the date from which
Date Start Date seniority should be calcu
lated.
Yes serviceDate Service Date DATE — Both No You can use this date to
grandfather service to re
hired employees. In rare
cases, a job credit is given
to an employee and serv
ice date is adjusted. For ex
ample, 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 DATE — Both Yes Enter the date of the cur
rent hire for an employ
ment.

Yes sourceOfRe Source of STRING — None Yes This field is required for in
cord Record tegration between Em
ployee Central and SAP
ERP as well to Integration
Center.

from the sourceOfRecord
picklist. The picklist must
contain the values "EC",
"ONB", as well as any val
ues for each external sys
tem where employee data
is recorded.
Picklists are found on the

SAP Help Portal on the
SAP SuccessFactors Em
ployee Central page under
Implement
Configuration Employee
Central Master Picklists .
You update picklists in
Admin Center Picklist
Center .
No custom- — STRING 256 None No You can use these fields for
string1–15 data not covered by the
and custom- fields supplied as stand
string21–80 ard.
No custom- — DATE — None No

date1–5,
custom-
date21–30,
custom-
date41-65
No custom- — LONG — None No

long1–10
No custom- — DOUBLE — None No

double1–10

4.1.4 Global Assignment Details
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.
Yes assignmen Assignment STRING 256 Both Yes This is an identifier for the
tIDExternal ID external employment of a user and
can be used for integra
tions with external sys
tems. It is unique and
case-sensitive.
Yes assignment- Assignment STRING 128 Both Yes Select the type of the
type Type global assignment. The list
picklist
global_assignment_
type.
Yes company Company STRING 256 Both Yes Enter the company the
employee goes to for the
global assignment. You
can choose from the com
panies that are available in
the system.
Yes end-date Actual End DATE — Both Yes When you end a global as
Date signment, you need to
specify the actual end
date.
Yes planned- Planned End DATE — Both Yes Enter the date when the
end-date Date global assignment is sup
posed to end.
No payroll-end- Payroll End DATE — Both No The date of the last payroll
date Date for the global assignment.
string101– data not covered by the
115 and cus fields supplied as stand
tom- ard.
string116–
The first 5 customer—spe
120
cific field numbers are

To use the Global Assignment Details block, you have to turn on Global Assignments in the Admin Center.
No custom- — DATE — None No used to add a global as

date31–35 signment, the last 5 cus
and custom- tom field numbers are
date36–40 used to end a global as
signment.
long21–25
and custom-
long26–30

double21–
25 and cus
tom-dou
ble26–30
4.1.5 Job Information
Job Information (hris-element-id: jobInfo)
Max. Default Vis Is Re

Standard Field ID Field Label Data Type Length ibility quired? How To Use This Field
No acquired- Acquired- STRING — None No You can enter the former

from-com from-com company the employee
pany pany used to work in before join
ing the current company.
No additional- Additional- HRIS_FIN 384 None No This field was previously

used to enter an additional
manager manager DUSER
manager for the employee.
No address Address LONG — None No

 Note
This field has been
deprecated and
should no longer be
used.

Yes amount-of- Amount Of DOUBLE — None No This field was previously

used to indicate whether
financial- Financial
an employee is eligible for
plan Plan
the financial plan, you can
indicate the amount that is
planned.
 Note
This field is now obso
lete.
No attachment- Attachment- LONG — None No Use this field to upload any

id id attachments.
Yes business- Business STRING — None Yes If you have defined busi
unit Unit ness unit foundation ob
jects, this field contains
the external code of those
business units.
Yes company Company STRING — None Yes This is the company or le
gal entity where the em
ployee is hired.
The country of the legal

entity determines the
country-specific attributes
displayed in the Job
Information block.
If you have defined legal

entity foundation objects,
ternal code of those legal
entities.
Yes company- Company STRING — None No If an employee leaves the

company, you can track
leaving-for Leaving For
the new company of the
employee.
Yes contract- Contract DATE 0 Both No Enter the date in which the
end-date End Date contract ends.

Yes cost-center Cost Center STRING — None No If you have defined cost
center foundation objects,
ternal code of those cost
centers.
Yes country-of- Country STRING 256 View No This field contains the
company country the company is lo
cated in. The values are
derived from the country
(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 exam
ple 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 us
ing this picklist as parent
picklist.
Yes default- Default STRING — None No This field is relevant for the
overtime- Overtime Employee Central Payroll
compensa Compensa Time Sheet.
tion-variant tion Variant
Set this field to define the
form of the overtime com
pensation received by em
ployees.
Yes department Department STRING 128 Both No If you have defined depart
ment foundation objects,
ternal code of those de
partments.

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,
break-con Break Con you can specify that a dy
fig-code figuration namic break rule is applied
on days where no breaks
are configured in the em
ployee’s work schedule.
For those days, a dynamic
break rule will automati
cally 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 op
portunities.

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

list EMPLOYEECLASS.
employee- Employee PICKLIST 256 Both No Here you can specify the
notice-pe Notice Pe notice period the em
riod riod ployee must give or follow
when he/she wants to quit
their job (leave the com
pany).

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.

list employee-type.
Yes employ Employ STRING 32 None No This is a customer configu-

rable picklist to track types
ment-type ment Type
of employment, for exam
ple, apprentice, full-time,
and so on.
No emplStatus EmplStatus STRING — None No This is a fixed picklist to in

dicate employment status,
for example, Active, Paid
Leave, Unpaid Leave, Sus
pended, Terminated, and
so on.
This cannot be changed by

the customer.
Yes ern-number Employee LONG — None No

 Note
Record
Number This field is now obso
lete.
No event Event STRING — Both No This field indicates the

event that has led to the
change of the job informa
tion.

list event. You can
change the labels for the
events in this picklist, but
you cannot add additional
events.

No event-rea Event-rea LONG — Both No This is the reason for the

son son-code change of the job informa
tion.
If you have defined event

reason foundation objects,
ternal code of those event
reasons.
No expected- Expected- DATE — None No If an employee is on a

leave of absence, then this
return-date return-date
field can be used to record
the planned return date.
 Note
This field will only be
displayed for leave of
absence job history re
cords.
Yes fte FTE DOUBLE — None No This is a calculated field

that 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, le
gal entity).
FTE stands for “full-time

equivalent” and indicates
an employee's working
hours or a legal entity's
standard working hours.
No govt-grant- Govt-grant- DOUBLE 4000 None No

 Note
amount amount
This field has been
deprecated and
should no longer be
used.

No hire-source Hire-source STRING — None No This field can be used to

track the source of the
hire, for example, internet
ad or newspaper ad.
No hire-source- Hire-source- STRING — None No This is a customer configu-

rable picklist. This is a sub-
details details
grouping of the Hire
Source field. If the source
was a newspaper, then this
field can be used to say
which newspaper.
Yes holiday-cal Holiday Cal STRING — None No This field is relevant for
endar-code endar Time Off.
A holiday calendar shows

the public holidays for a
given period and country.
If you have defined holiday

calendar generic objects,
ternal code and name of
those holiday calendars.
Yes hr-manager HR Manager STRING None No

 Note
This field is not sup
ported by Employee
Central and should
never be enabled for
it.
This field does not appear

on the UI. Leave the visibil
ity to “none” to prevent
this field from showing up
in the role-based permis
sions setup.
Yes interna Interna STRING 256 None No

 Note
tional-org- tional Org
code Code This field is depre
cated and should no
longer be used.

Yes is-competi Competition BOOLEAN — None No Set this field to indicate

tion-clause- Clause whether a competition
active clause has been defined
for the employee. A com
petition clause is an agree
ment restricting an em
ployee who leaves the en
terprise from acquiring
employment with a com
petitor within a specific in
dustry, or period of time.

No.
Yes is-cross- Is Cross BOOLEAN — None No You can indicate if the em
border- Border ployee is a cross-border
worker Worker worker.

No.
Yes is-eligible- Is Eligible BOOLEAN — None No This field was previously

for-benefit For Benefit
the employee is eligible for
company benefits.
This information should

now be set in Compensa
tion Information.
Yes is-eligible- Is Eligible BOOLEAN — None No This field was previously

for-car For Car
a company car.
This information should

now be set in Compensa
tion Information.
Yes is-eligible- Is Eligible BOOLEAN — None No You can indicate whether

for-finan For Financial
a company financial plan.
cial-plan Plan
Yes is-fulltime- Is Fulltime BOOLEAN — None No You can indicate if the em
employee Employee ployee is a full-time em
ployee.

No.

No is-home- Is-home- BOOLEAN — None No You can indicate if the em

worker worker ployee works from home.
Yes is-primary Is Primary BOOLEAN — None No This field was previously

used to track the primary
job if an employee had
multiple jobs in the com
pany.
This can now be tracked in

the UI for Concurrent Em
ployment by setting main
and secondary employ
ment.
Yes is-shift-em Is Shift Em BOOLEAN — None No This is where you indicate
ployee ployee if the employee works in
shift.
Yes is-side-line- Sideline Job BOOLEAN — None No This field indicates if the
job-allowed Allowed employee is allowed to
take up a sideline job sup
plementary to the employ
ee's main occupation.

No.
No is-volunteer Is-volunteer BOOLEAN — None No You can use this field to in
dicate whether an em
ployee is a volunteer.
Yes job-code Job Classifi- STRING 128 Both Yes This is the job classifica-
cation tion of the employee.
If you have defined job

classification foundation
objects, this field contains
job classifications.

standard element 'jobCo
de' of the Employee Pro
file.
Yes jobEntry Job Entry DATE — None No This field shows when an
Date Date employee started in a job.
You can change this field
manually.

Yes job-title Job Title STRING 256 Both No This field is automatically
filled with the job title de
fined in the job classifica-
tion foundation object.

standard element 'title' of
the Employee Profile.
No job-request- Job-re LONG — None No This field can be used to

track the job requisition ID
number quest-num
in a recruiting system.
ber
Yes local-job-ti Local Job Ti STRING 256 None No Here you can enter the lo
tle tle cal job title if it differs from
the company-wide used
job title.
Yes location Location STRING 128 Both No If you have defined loca
tion foundation objects,
ternal code of those loca
tions.
Yes manager Manager STRING None No This field does not appear
on the UI. Leave the visibil
ity to “none” to prevent
this field from showing up
in the role-based permis
sions setup.
Yes manager- Manager STRING 256 None No This is customer configu-

rable picklist to categorize
category Category
manager types.
Yes manager-id Supervisor HRIS_FIN 384 Both No You can choose from the
DUSER list of existing users in the
system to identify the em
ployee's manager. This in
formation is then used to
build the Org Chart.

standard element 'mana
gerId' of the Employee Pro
file.

quired.
No notice-pe Notice Pe STRING 256 Both No In this field you define the
riod riod amount of time that must
be given, by either an em
ployer or an employee, be
fore the date on which the
work agreement is termi
nated. The list of values
comes from the prede
fined picklist
NOTICEPERI.
As you can use this field

country dependent, you
can create country-de
pendent values by using
the picklist
ISOCountryList as
parent picklist.
Yes pay-grade Pay Grade STRING 256 None No If you have defined pay
grade foundation objects,
ternal code of those pay
grades.

Yes pay-group Pay Group STRING 256 None No This field is not to be used.
Leave the visibility to
“none” to prevent this
field from showing up in
the role-based permission
setup.
 Note
This field is depre
cated and should no
longer be used. In ad
dition, this field is not
supported for any fea
tures released after Q1
2017.
Do not use this field if

you are integrating
with Employee Central
Payroll or SAP HCM
Suite. Instead, please
use the field pay-
group in Compensa
tion Information.

Yes paySca Pay Scale STRING 256 None No This is the pay scale area
leArea Area
to which the employee is
assigned.

scale area foundation ob
pay scale areas.
 Note
Customers who use a
picklist for this object
should migrate this
picklist to foundation
objects using the Pro
visioning job “Initialize
migration of picklist
fields payscale area
and type to MDF ob
jects”. New customers
should not use a pick
list for this field.

Yes payScale Pay Scale STRING 256 None No This is the pay scale type
Type Type
assigned.

scale type foundation ob
pay scale types.
 Note
Customers who use a
picklist for this object
should migrate this
picklist to foundation
objects using the Pro
visioning job “Initialize
migration of picklist
fields payscale area
and type to MDF ob
jects”. New customers
should not use a pick
list for this field.
Yes paySca Pay Scale STRING 256 None No This is the pay scale group
leGroup Group
assigned.

scale group foundation ob
pay scale groups.
Yes payScaleLe Pay Scale STRING 256 None No This is the pay scale level
vel Level
assigned.

scale level foundation ob
pay scale levels.
Yes position Position LONG — None No This field is only shown

when you have activated
Position Management.

Yes positionEn Position En DATE — None No This field shows when the
tryDate try Date incumbent has taken on a
position. You can change
this field manually.
This field is only shown

Yes probation- Probation DATE — None No Here you enter the end
period-end- ary Period date of the employee's
date End Date probationary period.
Yes radford-job Radford STRING 128 Both No These are standardized job
codes from the Radford
code JobCode
consulting company.
Yes refresh- Enable STRING 128 Both Yes The new property indi
comp-re Compensa cates whether the corre
quired tion Refresh sponding field needs to
trigger the refresh of com
pensation information
when there is a change in
the job information.
Yes regular- Regular/ STRING 32 None No This field indicates

temp Temporary whether the employee is
regular or temporary.

list regular-temp.
Yes seq-number Sequence LONG — Both Yes This field tells you the se
quence of transactions for
Number
that day, for example, 1 of
2, 2 of 2.
Yes shift-code Shift Code STRING 256 None No The shift code indicates in
which shift the employee
works in.
Yes shift-factor Shift Per DOUBLE — None No This field indicates the
compensation multiplier
cent
for working a specific shift,
for example, 1.5 for a
weekend day or holiday.

Yes shift-rate Shift Rate DOUBLE — None No This field indicates the dif
ferential for a specific shift,
for example, on a weekend
or holiday.
Yes sick-pay- Sick Pay STRING 256 Both No This field indicates if the
supplement Supplement employee gets an addi
tional payment when on
sick leave. Continued pay
is affected when an em
ployee is unable to work.

list SICKPAYSUPP. As
you can use this field
country dependent, you
can create country-de
pendent values by using
the picklist
ISOCountryList as
parent picklist.
Yes standard- Standard DOUBLE — None No You can define the stand
hours Weekly ard weekly hours the em
Hours ployee is supposed to
work. This should be the
same amount as defined in
the employee's contract.
Yes supervisor- Supervisor STRING 256 None No This is a customer configu-

rable picklist for custom
level Level
ers who want to categorize
supervisory levels.

Yes timeInJob Time In Job STRING 256 None No This field shows how long
an employee has been in a
job. This time is calculated
by the system and shows
the time difference be
tween the current date (or
the end date for history re
cords) and the Job Entry
Date. For example, the
time an employee spends
on maternity leave is
added to the Time In Job.
You cannot change this

value.
Yes timeInPosi Time In Po STRING 128 None No This field shows how long
tion sition the incumbent has been in
a position. This time is cal
culated by the system and
shows the time difference
between the current date
(or the end date for history
records) and the Position
Entry Date. You cannot
change this value.
This field is only shown

Yes time-record Time Re STRING — None No This field is relevant for the
ing-admissi cording Ad Employee Central Payroll
bility-code missibility Time Sheet.
This field allows you to de

fine time recording admis
sibility rules for individual
employees - controlling
whether employees can
amend time sheet data in
the past and whether they
can amend already-ap
proved time sheets.

ing-profile- cording Pro Employee Central Payroll
code file Time Sheet.
The Time Recording Profile

contains employee-spe
cific settings for the Em
ployee Central Payroll
Time Sheet.
It sets the time recording

method and the time valu
ation rules which are used
for this employee. If you
have defined time record
ing profile generic objects,
those time recording pro
files.
Note: If the Employee Cen

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

ing-variant cording Var Employee Central Payroll
iant Time Sheet.
Employees record their

time in the Employee Cen
tral Payroll Time Sheet us
ing one of the following
time recording variants:
Clock Time-Based Re

cording - Time recording
based solely on the en
tered start and end times
of work within a specified
period, for example, per
day.
Duration-Based Record
ing - Time recording based
solely on the duration of
the work recorded for a
specific period, for exam
ple, in hours and minutes
for a given day of work.
Yes time-type- Time Profile STRING — None No This field is relevant for
profile-code Time Off.
Different time types, such

as work, vacation, and paid
time off (PTO) can be as
signed to a single struc
ture, called the time pro
file. This time profile is
then assigned to employ
ees 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.

Yes track-id Track Id STRING 32 None No This field was previously

used to track different em
ployments within the com
pany. It is typically no lon
ger used.
Yes workingDay Working STRING 256 Both No You can enter the number
sPerWeek Days Per of working days per week.
Week It is not a working sched
ule.
The number must be

smaller than or equal 7. For
example:
● 5
● 3.5

SAP ERP.
Yes work-period Work Period STRING 100 None No This field belongs to the
Standard Weekly Hours
field to denote how many
hours an employee should
work each week.
Yes worksched Work STRING — None No This field is relevant for

ule-code Schedule Time Off.
It defines how an employ

ee’s total work time is div
ided. For example, an em
ployee might be scheduled
to work 40 hours a week,
comprising 5 days of 8
hours each.
If you have defined work

schedule generic objects,
those work schedules.

Yes custom- Custom STRING 256 None No Do not use the type at
string1 String 1 tribute for this custom
string (neither
type=“foundation
object” nor
type=”generic
object” nor
type=”worker”).
ard.

20

20
Yes companyEn Company DATE — View No See [Note #1] below.
tryDate Entry Date
Yes timeInCom Time In STRING 256 View No

pany Company
Yes locationEn Location En DATE — View No

tryDate try Date
Yes timeInLoca Time In Lo STRING 256 View No

tion cation
Yes departmen Department DATE — View No

tEntryDate Entry Date
Yes timeInDe Time In De STRING 256 View No

partment partment
Yes payScaleLe Pay Scale DATE — No

velEntry Level Entry
Date Date

Yes timeInPay Time In Pay STRING 256 View No

ScaleLevel Scale Level
Yes hireDate Hire Date DATE — No See [Note #2] below.
Yes termination Termination DATE — No

Date Date
Yes leaveOfAb Leave Of Ab DATE — No

senceStart sence Start
Date Date
Yes leaveOfAb Leave of Ab DATE — No

senceRe sence Re
turnDate turn Date
[Note #1]
The following fields are set in case company, location, department or pay scale level changes:
● Company Entry Date

● Location Entry Date
● Department Entry Date
● Pay Scale Level Entry Date
The following transient fields are calculated and displayed in the History UI, Employment Info page and MSS:
● Time in Company
● Time in Location
● Time In Department
● Time In Pay Scale Level
In case of a change in company, location, department, or pay scale level, the company/location/department/pay
scale level entry date is calculated, propagated to future job records and saved to the database. The entry dates for
company, location, department, pay scale level are saved to the DB only if fields are configured in SDM or country-
specific SDM.
To use at least one of the new entry date fields in existing job info records, run the Initialize additional entry date
fields in job info job. You can find this in Provisioning under "Manage Scheduled Jobs”.
Initialization of entry date fields in existing job info records has the following impact:
1. If the value of the field has already been set through the UI, this value will be overwritten.
2. If the customers first use a subset of the new fields and run the job and later they want to use an additional field
of the new entry date fields, they have to run the job again. However, do note that the value of all date fields will
be overwritten.
If customers do not change any of the entry dates in UI, this will not have any effect, since the calculation in UI
and in the job is the same. But if customers have overwritten some fields, these values will be overwritten after
running the job.
3. Only fields configured in SDM or CSFSDM will be written by the job.
[Note # 2]

The Hire Date, Termination Date, Leave of Absence Start Date, and Leave of Absence Return Date fields are
automatically filled with the effective start date in case a job info record is created/changed/deleted based on
its triggering event: Hire, Rehire, Termination, Leave of Absence and Return to Work.
In case the Job Info’s effective start date is changed in a record with one of the above-mentioned events, the
hire date/termination date /leave of absence start date/leave of absence return date is newly set according to
the new effective start date.
In Job Info History, the date fields are propagated to future records until a new record with a suitable event
(Hire, Rehire, Termination, Leave of Absence, Return to Work) is created. In case a job info record is deleted, the
date fields are propagated from the “closest underlying” job info records.
During new hire, no event-based date fields are set. The hire/rehire date is set automatically in employment
details and job info history. For these date fields, there is no TimeIn calculation.
 Note
[1] The date fields are only saved to the database if they are configured in the SDM or the country/region-
specific SDM.
[2] For now, the setting of Leave of Absence Start Date and Leave of Absence Return date fields only works
with the "old" LOA/RLOA application, and not with Time Off/LOA.
Some points about initialization of new entry date fields for existing job info records:
○ If customers want to use at least one of the new entry date fields, they have to run a job, which
initializes the fields for existing records in database.
○ The job writes the entry date fields in the same way as the UI logic.
○ If the fields already have a value (for example, a value set in UI), this value will be overwritten.
○ If the customers first use a subset of the new fields and run the job and later they want to use an
additional field of the new entry date fields, they have to run the job again. But the values of all entry
date fields will be overwritten. If customers didn’t change any entry date in UI, this will not have any
effect, since the calculation in UI and in the job is the same. But if customers have overwritten some
fields, these values will be overwritten after running the job.
○ Only fields configured in SDM or Country/Region-Specific SDM will be written by the job.
○ To use at least one of these date fields in existing job info records, run the Initialize additional entry date
fields in job info job. You can find this in Provisioning under "Manage Scheduled Jobs”.
4.1.6 Job Relationships
Job Relationships (hris-element-id: jobRelationsInfo)

Yes relationship- Relationship STRING 100 Both Yes Here you choose the type
type Type of 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 en
hancing the picklist CSV
file.
Yes rel-user-id Name STRING 384 Both Yes You can select the manag
er's name from the list of
existing users in the sys
tem.
string1–20 string 1 to data not covered by the
ard.

20

20
4.1.7 PayComponentNonRecurring
PayComponentNonRecurring (hris-element-id: payComponentNonRecurring)

No action- Action- — None No This field is used for inter

enum enum nal purposes. Do not use it
on the UI.
No action-id Action-id LONG — None No This field is used for inter

on the UI.
Yes alternative- Alternative STRING 256 Both No You can assign an alterna
cost-center Cost Center tive cost center to the non-
recurring payment by en
tering 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-delete Specifies if BOOLEAN — None No This field is used for inter

delete is al nal purposes. Do not use it
lowed for a in the data model. Even if it
record is used, it won't be visible
on the UI.

Yes base-pay- Base Pay STRING — None No You can specify for pay
component Component components of type PER
CENTAGE of what exactly
the pay component is a
percentage, for example,
bonus = 10% of base sal
ary. Once this field is filled
for a pay component defi-
nition, all employee pay
components must use this
value of the base pay com
ponent group field (it can
not be overwritten).
 Note
If you enable this field
as editable in the em
ployee UIs, the value
help will offer you all
the pay component
groups to which the
pay component you
are editing are as
signed. So for exam
ple, you would get the
pay component group
“Total annual earn
ings” offered as a pos
sible base pay compo
nent group for em
ployee pay component
base salary, bonus,
and car allowance.
Set to View to be dis

played on the UI or
None. Do not set it to
Both.

Yes calculated- Calculated Double — View No ● For pay components

amount Amount of 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
of type NUMBER, the
the number entered in
the employee pay
component multiplied
by a rate read from ei
ther the pay scale
level or from the pay
component (FO) defi-
nition.
 Note
If the rate in the
payscalelevel is
not available, the
rate specified in
the Foundation
Object is used.
No created-by Created-by STRING 100 None No This field is used for inter
on the UI.
No created-on Created-on DATE — None No This field is used for inter

on the UI.

Yes currency- Currency STRING 20 Both Yes Select the currency the
code Code pay component is issued
in from the list of curren
cies provided in this field.
No item-id Item-id LONG — None No This field is used for inter

on the UI.
No last-modi Last-modi STRING 100 None No This field is used for inter
fied-by fied-by nal purposes. Do not use it
on the UI.
No last-modi Last-modi DATE — None No This field is used for inter

fied-on fied-on nal purposes. Do not use it
on the UI.
Yes non-recur End Date of DATE default None No This field has the visibility
ring-pay-pe the Related ‘none’ by default. So if the
riod-end- Period customers require these
date fields, then they need to
change the data model to
have the visibility set to
‘both’. The field values will
be replicated to SAP ERP if
payroll is enabled.
Yes non-recur Start Date DATE default None No This field has the visibility
ring-pay-pe of the Re ‘none’ by default. So if the
riod-start- lated Period customers require these
date fields, then they need to
change the data model to
have the visibility set to
‘both’. The field values will
be replicated to SAP ERP if
payroll is enabled.

Yes number-of- Number of DOUBLE — Both No The value specified in this

units field is multiplied with the
Units
rate from the payscalelevel
defined in Job Information.
In case the payscalelevel is
not available, the value
specified in this field is
multiplied with the rate de
fined for the Foundation
Object, which is then dis
played in the calculated-
amount field.
Yes offcycle-rea- OffCycle Picklist — None No

 Note
son 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 ex
ternal code of the picklist
has to be mapped in the
Code Value Mapping
(T77SFEC_CVMAPC ) ta
ble in Employee Central
Payroll.
Yes pay-compo Type STRING — Both Yes If you have defined pay
nent-code component foundation ob
pay components.
No pay-compo Pay-compo STRING 38 None No Choose Amount, Percent

age or Number.
nent-type nent-type
Yes pay-date Issue Date DATE — Both Yes The date the compensa
tion 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 differenti-

ate 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 spe
cial characters, such as
‘@’, ‘#’, ‘$’, ‘%’, ‘^’, ‘&’, ‘*’, ‘?’,
can be used to indicate the
specific payment to be
treated as planned offcycle
if the Payroll Control Cen
ter is implemented.
When the ID is not en

tered, the specific pay
ment will be treated as ad
hoc offcycle payment if the
Payroll Control Center is
implemented.
Yes sent-to-pay Sent To Pay DATE — None No The date the compensa
tion information is sent to
roll roll
payroll.
No sequence- Sequence STRING 38 View Yes This field is required for

number Number importing data. If you ena
ble this field, the allow im
port property is defaulted
to True.
Yes tax-treat Tax Treat STRING 32 None No This field shows whether
the pay component is
ment ment
taxed or not.

Yes unit-of- Unit of Generic Ob — Both No Displays the unit that is
measure Measure ject (Unit of used. For example, kg,
Measure ac pound, pieces, and so on.
cording to
UN/CEFACT
Recommen
dation
20/21)
Yes value Amount DOUBLE — Both Yes Here you define the
amount of the component
in numbers.
ard.

20

50
 Note
4.1.8 PayComponentRecurring
PayComponentRecurring (hris-element-id: payComponentRecurring)

No action- Action- — None No This field is used for inter

enum enum nal purposes. Do not use it
on the UI.
No action-id Action-id LONG — None No This field is used for inter

on the UI.
No allow-delete Specifies if BOOLEAN — None No This field is used for inter

delete is al nal purposes. Do not use it
lowed for a in the data model. Even if it
record is used, it won't be visible
on the UI.

Yes base-pay Base Pay STRING — None No You can specify for pay
component Component components of type PER
CENTAGE of what exactly
percentage, for example,
bonus = 10% of base sal
ary. Once this field is filled
for a pay component, 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 em
ployee UIs, the value
help will offer you all
the pay component
groups to which the
pay component you
are editing are as
signed. So for exam
ple, you would get the
pay component group
“Total annual earn
ings” offered as a pos
sible base pay compo
nent group for em
ployee pay component
base salary, bonus,
and car allowance.

Yes calculated- Calculated Double — View No ● For pay components

amount Amount of type AMOUNT, the
set to the amount.
Note that you cannot
use a rule to automat
ically set this value.
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.
of type NUMBER, the
the number entered in
the employee pay
component multiplied
by a rate read from ei
ther the pay scale
level or from the pay
component founda
tion object definition.
 Note
If the rate in the
pay scale level is
not available, the
rate specified in
the foundation
object is used.
No compensa Compensa LONG — None No This field is used for inter

tion-id tion-ID nal purposes. Do not use it
on the UI.

No created-by Created-by STRING 100 None No This field is used for inter
on the UI.
NO created-on Created-on DATE — None No This field is used for inter

on the UI.
Yes currency- Currency STRING 32 Both Yes Here you select the cur
code rency of the pay compo
nent. The values come
from the list of currencies.
Yes deferralper Deferral Per DOUBLE — None No This field is used for inter
centage centage nal purposes. Do not con
figure the visibility.
No end-date End Date DATE — None No This field is used for inter
on the UI.
Yes frequency Frequency STRING 30 Both No This is the frequency in

Code which the pay component
is paid, for example,
monthly, annual, bi-
weekly, and so on.
If you have defined fre

quency foundation ob
frequencies.
No is-earning Is-earning BOOLEAN 1 None No This field is used for inter

nal purposes. Do not con
Yes is-target Is Target BOOLEAN 1 None No This field shows whether

target figure or percent
age.

No item-id Item-id LONG — None No This field is used for inter

on the UI.
No last-modi Last-modi STRING 100 None No This field is used for inter
fied-by fied-by nal purposes. Do not use it
on the UI.
No last-modi Last-modi DATE — None No This field is used for inter

fied-on fied-on nal purposes. Do not use it
on the UI.
Yes no-changes- No Changes DATE — None No This is a calculated, transi

until-date Until This ent field on the UI. It shows
Date the date when a change is
planned for a pay compo
nent.
Yes number-of- Number of DOUBLE — Both No The value specified in this

units field is multiplied with the
Units
rate from the payscale
level defined in Job Infor
mation. In case the pay
scale level is not available,
the value specified in this
field is multiplied with the
rate defined for the Foun
dation Object which is
then displayed in the cal
culated-amount field.
Yes pay-compo Pay Compo STRING — Both Yes Enter the pay component
nent nent that makes up the employ
ee's total compensation,
like base salary.

component foundation ob
pay components.

Yes pay-compo Pay Compo STRING 38 None No Choose Amount, Percent

age or Number.
nent-type nent Type
Yes paycomp Amount DOUBLE — Both Yes Here you define the
value amount of the component
in numbers.
Yes sent-to-pay Sent To Pay DATE — None No This field is used for inter
roll roll Date nal purposes. Do not con
No seq-number Seq-number LONG — None No This field is used for inter

nal purposes. Do not con
Yes tax-treat Tax Treat STRING — None No This field is used for inter
ment ment nal purposes. Do not con
Yes unit-of- Unit of Generic Ob — Both No Displays the unit which is
measure Measure ject (Unit of used. For example, kg,
Measure ac pound, pieces, and so on.
cording to
UN/CEFACT
Recommen
dation
20/21)
ard.

20

20

 Note
4.1.9 Pension Payout Details
Pension Payout Details (hris-element-id: pensionPayoutsInfo)
Yes company Pension Pro STRING 256 Both Yes Enter the pension provider
vider that pays the pension pay
out. You can select from
the pension providers you
have created as company
foundation object in the
system.
Yes end-date Actual End DATE — Both Yes When you end a pension
Date payout, you have to enter
the actual end date of the
pension payout.
Yes payroll-end- Payroll End DATE — Both Yes Enter the payroll end date.
date Date This might differ from the
end date of the pension
payout.
Yes planned- End Date DATE — Both No Enter the end date when
end-date the pension payout is sup
posed to end. This does
not end the pension pay
out automatically.
Yes start-date Start Date DATE — Both Yes Enter the start date of the
pension payout.

string101– data not covered by the
115 and cus fields supplied as stand
tom- ard.
string116–
The first 5 custom field
120
numbers are used to add a
pension payout, the last 5
No custom- — DATE — None No
custom field numbers are
date31–35
used to end a pension pay
and custom-
out.
date36–40

long21–25
and custom-
long26–30

double21–
25 and cus
tom-dou
ble26–30
4.1.10 Termination Information
Termination Information (part of hris-element-id: employmentInfo)
Yes benefit- Benefits DATE — Both No Benefits are granted until

sEndDate End Date this date. By default, this is
the same date as the ter
mination date, unless you
change it here.
No bonus Bonus Pay DATE — Both No Bonus pays are being paid
PayExpira Expiration until this date. By default,
tionDate Date this is the same date as
the termination date, un
less you change it here.

Yes eligiblefor Eligible for BOOLEAN — Both No This field indicates that the
SalContinu Salary Con employee is eligible for sal
ation tinuation ary continuation. Possible
values are Yes and No.
Yes end-date Termination DATE — View Yes Enter the end date of the
Date employee's working con
tract with the company.
Yes lastDate Last Date DATE — Both No The last day the employee
Worked Worked worked for the company.
By default, this is the same
date as the termination
date, unless you change it
here.
Yes okToRehire Ok to Rehire BOOLEAN — Both No If the employee can be re

hired, set this field to Yes.
Yes payrollEnd Payroll End DATE — Both No The last payroll for this
Date Date employee. By default, this
is the same date as the ter
change it here.
Yes regretTermi Regret Ter BOOLEAN — Both No If this termination is a loss

nation mination for the organization, set
this field to Yes.
Yes salary-end- Salary End DATE — Both No Salary is paid until this
date Date date. By default, this is the
same date as the termina
tion date, unless you
change it here.
Yes StockEnd Stock End DATE — Both No Stocks are granted until
Date Date this date. By default, this is
the same date as the ter
change it here.

string16 to Strings 16– data not covered by the
custom- 20 fields supplied as stand
string20 ard.
Custom
and custom-
Strings 81–
string81–
100
100

date6 to Dates 6–20
custom-
Custom
date20
Dates 66–
90

long11 to Numbers
custom- 11–20
long20

double11 to Decimals
custom- 11–20
double20

5 Deprecated Elements
The following elements are deprecated and must not be used in the data models.
● BonusInfo
● CompAdjustInfo
● DirectDeposit
● JobInfoLocal
● LeaveOfAbsence
● NameInfo
● PayrollInfo
● RelInfo
● StatusInfo
● WorkEligabilityInfo

150 PUBLIC Deprecated Elements
Important Disclaimers and Legal Information
Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:
● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements
with SAP) to this:
● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such links, you
agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.
Videos Hosted on External Platforms

Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any
advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within the
control or responsibility of SAP.
Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by SAP at
any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the
experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback
(e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.
Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and
phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example
code unless damages have been caused by SAP's gross negligence or willful misconduct.
Gender-Related Language
We try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.

Important Disclaimers and Legal Information PUBLIC 151
www.sap.com/contactsap
© 2021 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form

or for any purpose without the express permission of SAP SE or an SAP
affiliate company. The information contained herein may be changed
without prior notice.
Some software products marketed by SAP SE and its distributors

contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for

informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP affiliate company products and services are those that are set forth
in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an
additional warranty.
SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.
Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.
THE BEST RUN

Data Object Tables in Employee Central: Developer Guide - PUBLIC Document Version: 1H 2021 - 2021-07-21

Uploaded by

Copyright:

Available Formats

Data Object Tables in Employee Central: Developer Guide - PUBLIC Document Version: 1H 2021 - 2021-07-21

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Data Object Tables in Employee Central: Developer Guide - PUBLIC Document Version: 1H 2021 - 2021-07-21

Uploaded by

Copyright:

Available Formats

Developer Guide | PUBLIC

Document Version: 1H 2021 – 2021-07-21

Data Object Tables in Employee Central

THE BEST RUN

2 Foundation Object Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

3 Person Object Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Data Object Tables in Employee Central

4 Employment Object Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

5 Deprecated Elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Data Object Tables in Employee Central

Type of Change Description More Info

Changed Updated information about isContingent­ Employment Information [page 101]

Changed Updated information about genderCoun­ Global Information [page 68]

What's New Description More Information

Global Information The country/region-specific <Gender> Global Information [page 68]

Compensation Information The <is-eligible-for-leave- Compensation Information [page 96]

loading> field is added.

reason> are added.

formation are managed by workflows, to

Data Object Tables in Employee Central

Each of the tables has the following columns:

Data Object Tables in Employee Central

Corporate Data Model

Data Object Tables in Employee Central

2.1.1 Business Unit

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

generic object id: BusinessUnit

Yes external­ Code String 32 As defined Yes Define a unique code by

Data Object Tables in Employee Central

Yes name Name Translatable 90 As defined No You can enter a short

2.1.2 Corporate Address

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

hris-element id: corporateAddress

Data Object Tables in Employee Central

No custom- Customer LONG — None No

No custom- Custom DOUBLE — None No

2.1.3 Cost Center

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

generic object id: CostCenter

Data Object Tables in Employee Central

Yes description Description Translatable 128 As defined No Specify a description here

Data Object Tables in Employee Central

Yes external­ Code String 32 As defined Yes Specify a unique code by

Yes glState­ GLState­ String 32 As defined No This code is assigned to

Yes Name Name Translatable 90 As defined No Specify a short name for

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

generic object id: Department

Data Object Tables in Employee Central

Yes external­ Code String 32 As defined Yes Define a unique code by

Yes name Name Translatable 90 As defined No You can enter a short

Data Object Tables in Employee Central

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

generic object id: Division

Yes external­ Code String 32 As defined Yes Define a unique code by

Data Object Tables in Employee Central

Yes name Name Translatable 90 As defined No You can enter a short

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

hris-element id: geozone

This field is informational

Changed Updated information about isContingent Employment Information [page 101]

Changed Updated information about genderCoun Global Information [page 68]

Yes external Code String 32 As defined Yes Define a unique code by

Yes external Code String 32 As defined Yes Specify a unique code by

Yes glState GLState String 32 As defined No This code is assigned to

Yes external Code String 32 As defined Yes Define a unique code by

Yes external Code String 32 As defined Yes Define a unique code by

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

Yes officialLan- Official Lan String — As defined No If there is an official lan

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

Yes loca Location STRING — Both No If you want to assign this

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

Yes defaultEm Employee Picklist 32 As defined No If a customer configured

Yes defaultJo Job Level Picklist 32 As defined No If a customer configured

Yes defaultSu Supervisor Picklist — As defined No If a customer configured

Yes regularTem Regular/ Picklist 32 As defined No This field indicates

Yes worker Workers' String 32 As defined No This is a custom configura-

Yes jobFunction Job Func Picklist 32 As defined No This is customer configu-

Yes external Frequency STRING 32 Both Yes Define a unique code by

Yes toPayPer Offcycle BOOLEAN — As defined No This field indicates

Yes basePay Base Pay STRING — Both No This attribute is only

Yes displayOn Display on BOOLEAN — Both No Controls whether this pay