Employee Master Data Replication Information

The replication of employee master data from Employee Central to Employee Central Payroll uses
the Employee Central Compound Employee API and the inbound service interface in Employee Central
Payroll.

Caution

You're not allowed to change the following infotypes manually after they’ve been replicated. If you do,
they’ll be overwritten during the next replication run from Employee Central.

Tip

For mass updates from Employee Central to Employee Central Payroll point-to-point, we recommend that
you follow the procedure described in KBA 2767376 .

Tip

It’s recommended that you’ve enabled the country/region-specific validations for postal address (of the
Home address of an employee), National ID, and bank account in Admin Center in Employee Central.

For more information, refer to the Country/Region-Specifics for Employee Central Payroll guide.

>Personnel Numbers in Employee Central Payroll

On this page

 Detection and Creation of Personnel Number in the Point-to-Point Integration

 Related Information

Describes the different ways personnel numbers are created in the Employee Central Payroll system.

Detection and Creation of Personnel Number in the Point-to-Point Integration

Here is the flow logic for detecting and creating personnel numbers for employees during the replication
process:

Detecting Personnel Numbers

The Employee Central Payroll system checks if a personnel number exists in the Employee key
mapping (HRSFEC_D_EEKEYMP) table based on field BUKRS for all effective (meaning with the highest
sequence number) employee data stored in the Employee Central system:

 A personnel number exists for the employee. The personnel number provided during the replication
is used as personnel number for the employee.

 There’s no personnel number for the employee. The system creates a new personnel number for
the employee.

Creating Personnel Numbers

Personnel numbers are created depending on the value configured for the PERNR switch as described in
the following table:

Selected Description
Value

1 Enables the creation of personnel numbers using Assignment ID from Employee

Central and external number range in Employee Central Payroll. Note that this feature is
 Selected Description
Value

available as of Q4 2019.

Blank Personnel numbers are created as follows:

 Using an internal number range: The next free number included in the internal
numbering is used to create the personnel number.

 Using BAdI HRSFEC_B_CE_EXT_PERNR_MAP: The system provides an external

personnel number that is used as personnel number for the employee data. We
don't recommend that you use this option.

Note

You can override or extend both use cases using BAdI HRSFEC_B_CE_DECIDE_HIRE_REHIRE.

Caution

Adding a new employment in Employee Central Payroll automatically creates a new personnel number
(PERNR) for the employee in Employee Central Payroll.

This logic applies to global assignment and concurrent employment.

Creating Personnel Number Using the Employee Central Assignment ID

Find out about the Customizing settings you need to make in your system for creating personnel number
using the Employee Central field Assignment ID.

Creating Personnel Numbers Using Internal Number Range or BAdI

Find out about the Customizing settings you need to make in your system to create personnel numbers
using internal number range or generate external personnel numbers using
BAdI HRSFEC_B_CE_EXT_PERNR_MAP.

Related Information

Other Useful Business Add-Ins (BAdIs)

>>Creating Personnel Number Using the Employee Central Assignment ID

On this page

 Prerequisites

 Context

 Procedure

 Next Steps

Find out about the Customizing settings you need to make in your system for creating personnel number
using the Employee Central field Assignment ID.
Prerequisites

General considerations before enabling this feature

Customer Type Action

If you’re a new customer for SAP We recommend that you enable this feature.
SuccessFactors Employee
Central and SAP SuccessFactors
Employee Central Payroll

If you’re a customer who has already You can only enable this feature if the following conditions are
implemented SAP SuccessFactors fulfilled:
Employee Central and wish to
 You haven’t replicated employee master data
implement SAP SuccessFactors
to Employee Central Payroll nor used Assignment
Employee Central Payroll in the near
ID data for any other purpose than creating personnel
future
numbers.

 The format of the Assignment ID must be identical to

the format of the Employee Central Payroll personnel
number (PERNR). The ID must be numeric and have
eight characters. Note that the settings of the numeric
sequence are made in Employee Central. For more
information, refer to Generating User IDs.

Caution

If you maintain legal entity changes for existing employment, we don't recommend that you switch on this
feature, as the Assignment ID is valid for the complete employment.

Configuration in Employee Central

Before enabling this feature in Employee Central Payroll, check the following requirements in Employee
Central:

 Creating the Employment Settings Configuration Object and Generating User IDs

 You've set up the selected business rule as described in Rule Scenarios for Employee Central
Core to enable the following mapping:

Employee Employee Central

Central Payroll

Sequence Number range

Business Rule Feature NUMKR

Context

With this feature, you can use the Assignment ID from Employee Information in Employee Central to
create a unique personnel number for replication purposes. Since Employee Central is the system of
records for all employee relevant data, using Assignment ID to create personnel numbers ensures that
you work with a unique identifier - one single personnel number - throughout all integrated systems.
The following graphic provides an overview of the fields mapping from the Employee Central system to
the Employee Central Payroll system:

Procedure

1. Make sure that you’ve enabled the feature by configuring the switch PERNR in the Employee
Central Payroll system.

You can access the table T77S0 from transaction SM30 or in the Customizing for Personnel Management
Personnel Integration Settings for SuccessFactors Employee Central Payroll Activate Payroll
Switches.

Provide the following information in the T77S0 table :

Grou Sem.ab Value Description

p br. abbr.

SFEC PERNR 1 Use Assignment ID external as

PERNR

2. Define the external number range for the feature NUMKR in the Customizing for Personnel
Management Personnel Personnel Administration Basic Settings Maintain Number
Range Intervals for Personnel Numbers.

Next Steps

A unique and consistent personnel number is generated that you use throughout all integrated systems.

>>Creating Personnel Numbers Using Internal Number Range or BAdI

On this page

 Context

 Procedure

 Related Information

Find out about the Customizing settings you need to make in your system to create personnel numbers
using internal number range or generate external personnel numbers using
BAdI HRSFEC_B_CE_EXT_PERNR_MAP.

Context

You can create personnel numbers using the following options:

 Internal number range in the Employee Central Payroll system.

The following graphic provides an overview of the mapping Employee Central system to the Employee
Central Payroll system:

 You use the Change Mapping of External Personnel Number (HRSFEC_B_CE_EXT_PERNR_MAP)

BAdI to generate your own personnel numbers. However, we recommend that you don't use this
option since it can lead to errors because you need to ensure that the personnel numbers are
unique.

The following graphic provides an overview of the fields mapping from the Employee Central system to
the Employee Central Payroll system:
Procedure

1. In the Employee Central Payroll system, make sure that the switch PERNR is set to Blank.

You can access the table T77S0 from transaction SM30 or in the Customizing for Personnel Management
Personnel Integration Settings for SuccessFactors Employee Central Payroll Activate Payroll
Switches.

Provide the following information:

Grou Sem.ab Value Description

p br. abbr.

SFEC PERNR Blank Internal numbering or

BAdI HRSFEC_B_CE_EXT_PERNR_MAP as PERNR

2. Select how you want to customize personnel numbers in your Employee Central Payroll system:

Option Description

Using internal Define the internal number range for the feature NUMKR in the
numbering Customizing for Personnel Management Personnel Personnel
Administration Basic Settings Maintain Number Range Intervals
for Personnel Numbers.

[Not a. Define the external number range for the

recommended feature NUMKR in the Customizing for Personnel
option] External Management Personnel Personnel
personnel number Administration Basic Settings Maintain Number
 Option Description

generated using Range Intervals for Personnel Numbers.

BAdI
b. Change the mapping of external personnel numbers using
BAdI HRSFEC_B_CE_EXT_PERNR_MAP in the Customizing
for Integration Settings for SuccessFactors
Employee Central Payroll Extensibility Business
Add-ins for Point-to-Point Replication

Related Information

Other Useful Business Add-Ins (BAdIs)

>Prohibiting Change of Legal Entity in Any Employment in Employee Central

Help with deciding when you should enable the Prohibiting Change of Legal Entity in Any Employment
in Employee Central.

Read and understand these instructions thoroughly before enabling this feature:

Caution

If you’re a productive Employee Central Payroll customer who maintains legal entity changes for existing
employment, we don't recommend that you switch on this feature. If you do so, data inconsistency might
arise.

If you’re a new Employee Central Payroll customer, we recommend that you enable this feature. However,
before you activate it, we ask you to check your payroll requirements, including all requirements related to
employee history, reporting, communication with the authorities, and so on.

Switching on this feature impacts the behavior of Employee Central Payroll, especially the Employee
Master Data integration. It means that an employee can only be assigned to one legal entity for one single
employment. First, terminate the employment of an employee in Employee Central from the old legal
entity, then rehire with a new employment on the new legal entity. For more information about the feature
and how to set it up in Employee Central , refer to Optional: Prohibiting Change of Legal Entity in Any
Employment and Enforcing New Employment Using Business Rules

Here is a table illustrating the most common use cases:

Use Case Description

Mark Cooper changes from legal entity DE01 to legal 2 personnel numbers are created in Employee
entity DE02 in the same country/region. Central Payroll for each legal entity: DE01 and
DE02.

Mark Cooper changes from legal entity DE01 to legal 2 personnel numbers are created in Employee
entity US01 in a new country/region. Central Payroll for each legal entity: DE01 and
US01

Mark Cooper changes from legal entity DE01 to legal 3 personnel numbers are created in Employee
entity DE02, then back to DE01 in the same
 Use Case Description

country/region. Central Payroll: 2 for DE01 and one for DE02

Mark Cooper changes from legal entity DE01 to US01, 3 personnel numbers are created in Employee
and then back to DE01 in a new country/region. Central Payroll: 2 for DE01 and one for US01

>Data Models in Employee Central and in Employee Central Payroll

On this page

 The Data Models and the Employee Master Data Replication

 Related Information

Here is an overview of concepts and data models.

The Central Person (CP) object type corresponds to the natural person while the Personnel Number
(PERNR) is a number assigned to the employee by the Employee Central Payroll system during the hiring
process. Note that one person can have many personnel numbers, in such cases, you use the Reference
Personnel Number (0031) infotype to link them together as illustrated in the following graphic:

The Data Models and the Employee Master Data Replication

In order for payroll to be legally compliant, a personnel number needs to be created if the country/region
of employment changes. By default, the system automatically creates a personnel number in Employee
Central Payroll whenever the employee is assigned to a new company code (BUKRS). You can select other
company codes/legal entities using the Change mapped Infotype Data Business Add-in as described
below:
Important aspects to keep in mind:

 Multiple employments of one single employee in Employee Central lead to multiple distinct
personnel numbers in Employee Central Payroll, because each employment has distinct timelines
for Job Information, Compensation Information and so on.

 Employee Central allows changes within individual employments that leads to the creation of new
personnel numbers in Employee Central Payroll, for example organizational changes like the legal
entity. In general, the decision in which cases organizational changes lead to the creation of new
personnel numbers must be based on legal requirements, company policies, and the company's
fiscal structure.

Related Information

Implementing BAdIs to Enhance Already Mapped Master Data

>Job Information - Infotypes 0000, 0001, 0007, 0008, 0016

Here you find an overview of all Job Information fields covered by generic replication. These fields allow
you to map Job Information of an employee from Employee Central to the corresponding infotype field
in Employee Central Payroll.

Job Information - Infotype 0000

Here you find an overview of generic fields. These fields allow you to map Job Information of an employee
from Employee Central to Employee Central Payroll.

Job Information - Infotype 0001

Here you find an overview of generic fields. These fields allow you to map Job Information of an employee
from Employee Central to Employee Central Payroll.

Job Information - Infotype 0007

Here you find an overview of generic fields. These fields allow you to map Job Information of an employee
from Employee Central to Employee Central Payroll.

Job Information - Infotype 0008

Here you find an overview of generic fields. These fields allow you to map Job Information of an
employee from Employee Central to Employee Central Payroll.

Job, Position, and Org. Unit

Location

Mapping Company to Company Code

>>Job Information - Infotype 0000

Here you find an overview of generic fields. These fields allow you to map Job Information of an employee
from Employee Central to Employee Central Payroll.

Job Information (Infotype 0000)

Employee Central Payroll Employee Central

IT00 Mandat Max Data Type Defaul Is Code Fiel Field Mandat Pickl
00 ory? . for code t- Value d ID Label ory? ist
Targ Len value Mappi Mapping ID
et gth mapping ng country/re
Mode gion-
specific?

MAS Yes 2 EVENT No even Perso No -

SN t nal
event
code

MAS Yes 2 EVENT_REA Custo No even Event No -

SG SON mer t- Reaso
Table reas n
on

Note

The Employment status field can't be mapped. The Employment Status field of
infotype Actions (0000) is derived from the personal actions configured in table T529A.
>>>Event

Here is the information about all mapping options to enable the replication of events from Employee
Central to actions in Employee Central Payroll.

The table gives you technical information on how the replication process of Events from Employee
Central to Actions in Employee Central Payroll works.

Event Types Mapping Description

Standard Direct mapping Configuring

(nonconfigurable) Country/Region-Specific
Events Rehiring on the Same
Day

Defining If the standard doesn't meet your requirements, you Actions

Customer-Specific must configure your own actions in Employee Central
Events Payroll.

Remember

If you create your own Actions, make sure that you’ve

copied and enhanced the technical user template to
ensure a successful communication betweenEmployee
Central and Employee Central Payroll.

Generated Events Helps you to generate events to meet payroll business Artificial Actions
requirements.

Payroll Events Helps you to refine the standard mapping of events Payroll Event
into more specific events.

Absence Time A task is created when replicating absences to infotype Using Payroll Unified
Types 2001. Configuration

Replication of Absences

Configuring Standard and Country/Region-Specific Mapping for Employee Central Events in the
Employee Central Payroll System

Find out how to make settings for standard and country/region-specfic code value mapping.

Artificial Actions

Artificial actions are actions that are automatically added during the replication of events and event
reasons from Employee Central.

Replication of No-Shows from Employee Central

See how to replicate No-shows from Employee Central to Employee Central Payroll.

Replication of No-Show Rehire From Employee Central

The following describes the two ways of configuring the replication of no-show rehires in an Employee
Central Payroll system.

Payroll Event

Payroll events allow you to refine event reasons into more specific events in Employee Central for
replication purposes.

Multiple Events Per Day

See how you enable the replication of multiple events per day from Employee Central.

Troubleshooting Job Information

Here's a look at some issues you might encounter in the Job Information and what you can do to fix them.

>>>>Configuring Standard and Country/Region-Specific Mapping for Employee Central Events in

the Employee Central Payroll System

On this page

 Prerequisites

 Context

 Procedure

 Next Steps

 Related Information

Find out how to make settings for standard and country/region-specfic code value mapping.

Prerequisites

Employee Central has events for the Job Information block. Field Event of the Job Information block is
replicated to infotype Actions (0000) in the Employee Central Payroll system.

In addition, make sure that the Mult. Actions checkbox is marked in Configure Compound Employee
API Query under Customizing for Personnel Management Integration Settings for SuccessFactors
Employee Central Configuration of Point-to-Point Replication.

To replicate events from Employee Central, make sure that you have enabled Additional Actions as
described in Multiple Events Per Day and defined the corresponding personnel action in the Employee
Central Payroll system.

Context

In Employee Central, each Hire, Rehire, Terminate, Begin, End of global assignment event is assigned to a
fixed constant. The standard includes the following direct mapping:

Event in Employee Action in Employee Central

Central Payroll

H - Hire 01 - Hiring
 Event in Employee Action in Employee Central
Central Payroll

26 - Termination 10 - Leaving

R - Rehire 12 - Re-entry into company

GA - Global Assignment 01 - Hiring

EGA - End Global 10 - Leaving

Assignment

Procedure

1. Go to your Employee Central Payroll system.

2. Go to table T529A by specifying SM30. This step is mandatory to prevent errors in the infotype
framework.

Here's a picture of the T529A table to show you the standard code value mapping for Actions that must
be included in every replication of master data.

3. Check and, if necessary, create an inactive hire action:

Valu
Field Name e

Function Code 1 or
7

Employment 0
Status
 4. Go to table T530 by specifying SM30.

5. [Optional] Check and, if necessary, create the reason for the action.

6. Check the standard delivery for field EC Data type Event in Display Code Value Mapping as
Delivered by SAP (SAP table T77SFEC_CVPROPS) in Customizing for Personnel
Management Integration Settings for SuccessFactors Employee Central
Payroll Assignment of Code Values For Point-to-Point Replication.

Caution

Don't modify the standard code value mapping.

7. Choose Maintain Properties for Code Value Mapping (customer table T77SFEC_CVPROPC) in
Customizing for Personnel Management Integration Settings for SuccessFactors
Employee Central Payroll Assignment of Code Values For Point-to-Point Replication and
proceed as follows:

 If the EC Data type Event isn't yet mapped using the Customer Code Value Mapping,
here is what you need to do:

Change the SAP code value mapping properties for field Employee Central data type Event at least
using Customer Code Value Mapping.

a. [MANDATORY] Choose Maintain Code Value Mapping (table T77SFEC_CVMAPC) in

Customizing for Personnel Management Integration Settings for
SuccessFactors Employee Central Payroll Assignment of Code Values For
Point-to-Point Replication. Copy all records for Event from SAP
table T77SFEC_CVMAPS.

b. Once done, add the new mapping for Event 26 to your new termination action.

 If the Employee Central data type Event is already mapped using the Custom code value
mapping, add the new mapping for Event 26 to your new termination action.

The following tables provide examples of an international and country/region-specific mapping for
the Termination event:

Example

Configuration of International Code Value Mapping Properties in T77SFEC_CVPROPC

Data Type ISO End Start Alt. Country/Region Mode

in Employee Code Date Date List dependent
Central

EVENT 31.12.99 01.01.18 Mapping via

99 00 customer table
identical
mapping

Configuration of Standard Code Value Mapping in T77SFEC_CVMAPC

Data Type ISO Alt. list Employee ERP Code Value

in Employee Central Code Central Code
 Configuration of International Code Value Mapping Properties in T77SFEC_CVPROPC

Data Type ISO End Start Alt. Country/Region Mode

in Employee Code Date Date List dependent
Central

Value

EVENT 26

Example

Configuration of Code Value Mapping Properties in T77SFEC_CVPROPC for Italy

Data Type ISO End Start Alt. Country/Region Mode

in Employee Code Date Date List dependent
Central

EVENT IT 31.12.99 01.01.18 Mapping via

99 00 customer table
identical
mapping

Configuration of Code Value Mapping in T77SFEC_CVMAPC for Italy

Data Type ISO Alt. list Employee ERP Code Value

in Employee Central Code Central Code
Value

EVENT IT 26 10

8. Save your changes.

Next Steps

You can replicate events to infotype 0000. The replication is successful if the event is replicated to the
corresponding employment status in the Actions (0000) infotype on the selected date and for the selected
country/region.

Related Information

Assignment of Code Values

>>>>Artificial Actions

On this page

 Prerequisites

 Context
  Scenarios Where Artificial Actions Are Added

 Filtering of Events and Event Reasons

 Filling Gaps to Comply with Payroll Requirements

 Organizational Reassignment: Special Case

 Related Information

Artificial actions are actions that are automatically added during the replication of events and event
reasons from Employee Central.

Prerequisites

Make sure that the configuration for personal actions is ready in your Employee Central Payroll system. For
more details, refer to the Related Information.

Context

During the replication process, events and event reasons not mapped using the standard code value
mapping aren’t added to the Actions (0000) and/or Additional Actions (0302) infotypes. In addition,
personnel actions like Hire, Rehire, Termination, and Organizational Reassignment are always
required whenever employee master data is replicated. These actions impact mainly the employment
status of an employee, that is, Active or Inactive during the whole payroll process, including reporting.

Scenarios Where Artificial Actions Are Added

Here is an overview of scenarios where artificial actions are added during the replication process of events
from Employee Central to Employee Central Payroll:

Filtering of Events and Event Reasons

Some Employee Central events are filtered out because they aren’t mapped. During the replication
process, an artificial IT 0000 record is added for the relevant date, where required.

Filling Gaps to Comply with Payroll Requirements

 If more than one event is added to the Job Information on a day it is replicated - although it’s
entered as last event -, it’s included in the replication process (as "highest sequence number").
In Employee Central, an artificial action is added to comply with the payroll requirements.

Example

If there’s no Hiring in the Job Information and in the Actions (0000) infotype, it’s added as artificial action
to the date of the first Job Information record replicated to Employee Central.

Example

Rehiring an employee: The following actions are added to the Actions (0000) infotype artificially to fill the
following gaps:

 A Termination at the end date of the Job Information where the gap starts,

 A Rehire to fill the duration in which the gap ends.

 ref

 For Intercompany Transfer, refer to Two Status Changing Event Reasons on the Same Day .

 If organizational changes like a move to a new company, a change of location or an assignment to a

new payroll area occur in IT0000, an Organizational Reassignment action is always artificially
added in Employee Central.
  If a gap is detected between the start and end hire date in a Job Information record and no
Termination or Rehire actions exist in the Job Information in Employee Central, artificial actions are
added to fill the gaps in Employee Central.

Note

A standard code value mapping is available for Employee Central events like Hire, Rehire, Termination,
Beginning of global assignment and End of global assignment.

Organizational Reassignment: Special Case

Since no predefined Employee Central events exist for this action, the Organizational
Reassignment (02) action is artificially added during the replication process.

To overwrite the Organizational Reassignment (02) action, make the following settings in
the T77S0 table:

Related Information

Configuring Standard and Country/Region-Specific Mapping for Employee Central Events in the Employee
Central Payroll System

>>>>Replication of No-Shows from Employee Central

On this page

 Prerequisites

 Context

 Procedure

 Results

 Related Information

See how to replicate No-shows from Employee Central to Employee Central Payroll.

Prerequisites

Employee Central has event NS (No-shows) for the Job Information block. Note that field Event of
the Job Information block is replicated to infotype 0000 in Employee Central Payroll.

To replicate No-shows from Employee Central, make sure that you have enabled Additional Actions as
described in Multiple Events Per Day and defined an inactive hire personnel action in the Employee Central
Payroll system.

In addition, make sure that the Mult. Actions checkbox is marked in Configure Compound Employee
API Query under Customizing for Personnel Management Integration Settings for SuccessFactors
Employee Central Configuration of Point-to-Point Replication.

Note

 It's also possible to replicate No-shows without Additional actions being activated under the
following conditions:
  The personnel number (PERNR) isn't created: The employee is hired in an inactive status.

 The personnel number (PERNR) is created: The status can't be changed from active to
inactive, and vice versa.

 For the United Kingdom, when an employee has payroll results for a payroll period that fits at event
date, replicating No-shows isn’t possible.

Tip

If you don't want to use this feature, assign your employees to a payroll area that isn't included in the
payroll run.

Context

Some hired employees ignore their signed contracts and don't show up to start work.

Because the person is technically hired in the system, you can consider them as No-show and set their
status to inactive in Employee Central. When you report No-shows in Employee Central, the corresponding
event and event reason are now transferred to your Employee Central Payroll system and processed there
as a personnel action type. If an employee in Employee Central is marked as No-show, Employee Central
Payroll sets the employee status to Inactive so that the changes are reflected in the payroll process
accordingly.

Procedure

1. Go to your Employee Central Payroll system.

2. Go to table T529A by specifying SM30. This step is mandatory to prevent errors in the infotype
framework.

3. Check and, if necessary, create an inactive hire action:

Valu
Field Name e

Function Code 1 or
7

Employment 0
Status

4. Here is an example about the configuration of an inactive/withdrawn hire action:

Acti F Employm Spec. P E ES Info Updat Updat

on C ent Payme Gro e IT e IT
Status nt up 0000 0302
Status

HI 1 0 1 Checkb Checkb Checkb 10 Checkb Checkb

ox is ox is ox is ox is ox is
selecte selecte selecte selecte selecte
d. d. d. d. d.
 5. The employment status of your employee must reflect the mechanism of being active and later
inactive in the corresponding infotype 0000 record on the hire date.

6. Go to table T530 by specifying SM30.

7. [Optional] Check and, if necessary, create the reason for the action.

8. Check the standard delivery for field EC Data type Event in Display Code Value Mapping as
Delivered by SAP (SAP table T77SFEC_CVPROPS) in Customizing for Personnel
Management Integration Settings for SuccessFactors Employee Central
Payroll Assignment of Code Values For Point-to-Point Replication.

Caution

Don't modify the standard code value mapping.

9. Choose Maintain Properties for Code Value Mapping (customer table T77SFEC_CVPROPC) in
Customizing for Personnel Management Integration Settings for SuccessFactors
Employee Central Payroll Assignment of Code Values For Point-to-Point Replication and
proceed as follows:

 If the EC Data type Event isn't yet mapped using the Customer Code Value Mapping,
here is what you need to do:

Change the SAP code value mapping properties for field Employee Central data type Event at least
using Customer Code Value Mapping.

a. [MANDATORY] Choose Maintain Code Value Mapping (table T77SFEC_CVMAPC) in

Customizing for Personnel Management Integration Settings for
SuccessFactors Employee Central Payroll Assignment of Code Values For
Point-to-Point Replication. Copy all records for Event from SAP
table T77SFEC_CVMAPS.

Note

The mapping of the Data Type in Employee Central NS event to the ERP Code value NS is required to
enable the No-show feature.

b. Once done, add the new mapping for Event NS to your new inactive hire action.

 If the Employee Central data type Event is already mapped using the Custom code value
mapping, add the new mapping for Event NS to your new inactive hire action.

The following tables provide examples of an international and country/region-specific mapping for the No-
shows event:

Example

Configuration for International and country/region-specific [Italy] Code Value Mapping

Properties in T77SFEC_CVPROPC

Data Type ISO End Start Alt. Country/Region Mode

in Employee Code Date Date list dependent
Central

EVENT 31.12.99 01.01.18 Mapping via

99 00 customer table
 Configuration for International and country/region-specific [Italy] Code Value Mapping
Properties in T77SFEC_CVPROPC

Data Type ISO End Start Alt. Country/Region Mode

in Employee Code Date Date list dependent
Central

identical
mapping

EVENT IT 31.12.99 01.01.18 Checkbox is

99 00 selected.

Configuration for International and country/region-specific [Italy Code Value Mapping

in T77SFEC_CVMAPC

Data Type ISO Alt. list Employee ERP Code Value

in Employee Central Code Central Code
Value

EVENT NS HI

EVENT IT NS HI

10. Save your changes.

Results

You can replicate No-shows to the Actions (0000) infotype. The replication is successful if a No-show is
replicated to an Inactive/Withdrawn employment status in the corresponding infotype 0000 record on
the hiring date.

Related Information

Reporting No-Show New Hires

>>>>Replication of No-Show Rehire From Employee Central

The following describes the two ways of configuring the replication of no-show rehires in an Employee
Central Payroll system.

Context

In your Employee Central system, you have rehired employees. Now, you want to report them as No-shows
and take action Report No-show on the same date as the rehire date.

Replication of No-Show Rehire Using Artificial Actions (Standard)

During the replication process, the system removes the previous personal action and extends the previous
infotype Actions (0000) record in the Employee Central Payroll system. The two events Rehire and No-
show are filtered out and not displayed in infotype 0302.

Replication of No-Show Rehire Using Payroll Events

The following describes the customizing in your Employee Central Payroll system.

>>>>>Replication of No-Show Rehire Using Artificial Actions (Standard)

During the replication process, the system removes the previous personal action and extends the previous
infotype Actions (0000) record in the Employee Central Payroll system. The two events Rehire and No-
show are filtered out and not displayed in infotype 0302.

Related Information

Artificial Actions

>>>>>Replication of No-Show Rehire Using Payroll Events

On this page

 Context

 Procedure

 Results

 Related Information

The following describes the customizing in your Employee Central Payroll system.

Context

In your Employee Central, you have rehired employees. You want to report them as No-shows by taking
action Report No-show on the same date as the rehire date. In your Employee Central Payroll, you want
to see the two events Rehire and No-show in infotype 0302. Here is what you need to do to so that both
events are displayed in infotype 302:

1. Create an event reason for event Rehire with payroll event filled by IR

2. Create an event reason for event Report No-show with payroll event filled by NR

For the two new events, you need to configure two new personal actions for the payroll
events NR and IR as well.

Procedure

1. In Employee Central Payroll go to transaction SM30.

2. Enter table T529A in field Table/View, and press Maintain.

3. To set up two new actions in table T529A choose New Entries, and enter the following.
 Actio Name of F Customer- Employment Special Update
n Action Type C specific Status Payment IT0000
Status Status

IR Rehire 0 n/a n/a n/a Field is

cancelled by no checked.
show

NR Rehire No Show 0 n/a n/a n/a Field is

checked.

4. Save your changes.

5. To set up reasons for actions in view V_T530 choose New Entries, and enter the following.

Actio Name of Action Type Reason for

n Action

IR Rehire cancelled by no n/a

show

NR Rehire No Show n/a

6. Choose Maintain Code Value Mapping (customer table T77SFEC_CVMAPC) in Customizing

for Personnel Management Integration Settings for SuccessFactors Employee Central
Payroll Assignment of Code Values For Point-to-Point Replication:

Data Type in Employee Employee Central Code ERP Code

Central Value Value

EVENT IR IR

EVENT NR NR

7. Save you changes.

8. In your Employee Central system, enter both events reasons in the relevant Employee Central Job
Information so that you can start the replication of the inactive employment status of the
employee who had the status Active (Rehired) before.

Results

In the Employee Central Payroll system, both events Rehire and No-show are displayed in infotype 0302
for the same day.

Related Information

Reporting no-show New Hires

>>>>Payroll Event
On this page

 Context

 Related Information

Payroll events allow you to refine event reasons into more specific events in Employee Central for
replication purposes.

Context

To ensure a successful replication of two status changing event reasons on the same day for the same
personnel number, you configure payroll events. For more information, see Creating Event Reasons
for Employee Central.

As a result, when you choose an event reason in the Job Information block that has a payroll event
assigned to it, Employee Centrall sends the payroll event to Employee Central Payroll instead of the event.

Caution

Don’t change events or payroll events for event reasons that were valid in the past. Changes of this kind
can lead to retroactive payroll calculation and can’t be imported into Employee Central Payroll.

Replication Scenarios Using Payroll Events

Here are some replication scenarios that illustrate how to use payroll events.

Related Information

Creating Event Reasons for Employee Central

>>>>>Replication Scenarios Using Payroll Events

Here are some replication scenarios that illustrate how to use payroll events.

Two Status Changing Event Reasons on the Same Day

You want to move your employee from legal entity A to legal entity B within the same employment.

Paid and Unpaid Leave

You want to break down the event Leave of Absence into paid and unpaid leave.

Configuring Country/Region-Specific Rehiring on the Same Day

Let's take Russia as example on how to set up terminating and rehiring on the same day.

Related Information

Troubleshooting Two Different Employment Statuses on the Same Day

>>>>>>Two Status Changing Event Reasons on the Same Day

You want to move your employee from legal entity A to legal entity B within the same employment.

Let's assume that no Termination action was explicitly added. The system detects the gap and generates
a termination using an artificial action. As a consequence, you get two statuses on the same day that
result from a generated termination action for entity A and a rehire action for entity B entered on the same
day. In addition, you want to use the same personnel number (PERNR) and ensure that the status of your
employee is Active on the same day of the change.

Example
In Spain, the direct payment system (sistema de liquidación directa, SLD, in Spanish) is an electronic
system through which companies and the Spanish Social Security exchange files to level the databases of
both parties, so that the social security actively runs the invoicing process.

Make sure that you've defined a payroll event in Employee Central and configured table T529A accordingly
for your rehired employees to prevent from split errors in payroll. For more information, refer to
KBA 2150947 .

Caution

A company transfer to a new country/region within the current employment isn’t supported.

Settings in Employee Central

An overview of which settings you need to make in Employee Central to set up the replication of two status
changing event reasons on the same day.

Settings in Employee Central Payroll

Let's look at the steps involved to set up the replication of two status changing event reasons on the same
day in Employee Central Payroll.

>>>>>>>Settings in Employee Central

On this page

 Prerequisites

 Procedure

An overview of which settings you need to make in Employee Central to set up the replication of two status
changing event reasons on the same day.

Prerequisites

Make sure that you’ve made all required settings as described in Creating Event Reasons for Employee
Central.

Note

Payroll events overrule predefined event like Hire, Rehire, Termination of the Job Information block.

Procedure

1. Go to Admin Center Manage Organization, Pay and Job Structures.

2. Select Create New: Event Reason.

3. Provide all the following information in the Job Information block for the following event reasons:

 Event Termination (26)

Field Value

Event Reason ID Org assgt Termination

Event Reason Name org assignment

Termination
 Field Value

Status Active

Event Termination

Payroll Event 02

Display in Internal Job History Yes

portlet

 Event Rehire (R)

Field Value

Event Reason ID Org assgt rehire

Event Reason Name org assignment

rehire

Status Active

Event Rehire

Payroll Event 02

Display in Internal Job History Yes

portlet

4. Save your settings

>>>>>>>Settings in Employee Central Payroll

Let's look at the steps involved to set up the replication of two status changing event reasons on the same
day in Employee Central Payroll.

Procedure

1. Go to your Employee Central Payroll system.

2. Go to table T529A by specifying SM30. This step is mandatory to prevent errors in the infotype
framework.

3. Create an Organizational Reassignment action:

 Actio Name of FR (Function Employmen Special Chec Customer-
n Action character t Status Payment k Specific
for action) Status Status

02 Organizational 0
Reassignment

4. [MANDATORY] Choose Maintain Code Value Mapping (table T77SFEC_CVMAPC) under

Customizing for Personnel Management Integration Settings for SuccessFactors Employee
Central Payroll Assignment of Code Values For Point-to-Point Replication

The mapping of the Data Type in Employee Central 02 event to the ERP Code value 02 is required to
enable the replication of your employee.

5. Once done, add the new mapping for Event 02 to your new action: Organizational Reassignment.

6. Save your settings

>>>>>>Paid and Unpaid Leave

You want to break down the event Leave of Absence into paid and unpaid leave.

In Employee Central, create event reasons for each and assign a value to the payroll event. Then assign
the event reasons to the event Leave of Absence.

In the Employee Central Payroll system, make sure that payroll events are mapped to the corresponding
actions in table T529A.

Now, whenever you choose the event Leave of Absence and the respective event reason, the system
sends whichever value is in the Payroll Event field: Paid or Unpaid.

You want to break down the event Leave of Absence into paid and unpaid leave.

In Employee Central, create event reasons for each and assign a value to the payroll event. Then assign
the event reasons to the event Leave of Absence.

In the Employee Central Payroll system, make sure that payroll events are mapped to the corresponding
actions in table T529A.

Now, whenever you choose the event Leave of Absence and the respective event reason, the system
sends whichever value is in the Payroll Event field: Paid or Unpaid.

>>>>>>Configuring Country/Region-Specific Rehiring on the Same Day

On this page

 Context

 Procedure

 Next Steps

Let's take Russia as example on how to set up terminating and rehiring on the same day.

Context

In some contries/regions like in Russia, it’s required by law to terminate and rehire employees on the same
day.
Remember

As a rule, it isn’t allowed to terminate and rehire an employee at the same time because the status is
then Active and Inactive at the same time in Employee Central Payroll.

Example

This situation can lead to inconsistent data replication from Employee Central to Employee Central Payroll.
Following is a list of the error messages that you receive depending on whether or not the switch EVSUP
from the ADMIN Group is activated for additional actions in the T77S0 table:

 Switch EVSUP is ON: Employee is active since...

 Switch EVSUP is OFF: Don’t add more than 1 employment status changing actions at same day &1.

Procedure

1. In Employee Central, choose the Rehire with new employment event.

Make sure that you’ve defined the corresponding payroll event for this event.

2. In Employee Central Payroll, make sure that the settings made in the T529A table cover the legal
requirements.

Example

3. [MANDATORY] Choose Maintain Code Value Mapping (table T77SFEC_CVMAPC) under

Customizing for Personnel Management Integration Settings for SuccessFactors Employee
Central Payroll Assignment of Code Values For Point-to-Point Replication to map
the Data Type in Employee Central event to the ERP Code value accordingly.

Next Steps

With these settings, you can replicate rehired employees according to Russian legal requirements.

>>>>>Multiple Events Per Day

On this page

 Prerequisite: Enabling the Replication of Multiple Events Per Day

 Things to Consider Before Enabling the Replication

 Related Information

See how you enable the replication of multiple events per day from Employee Central.

Prerequisite: Enabling the Replication of Multiple Events Per Day

You need to make the following settings in the Employee Central Payroll system:
 1. Run the RPUEVSUP report for all personnel numbers. The report automatically activates
the EVSUP switch so that additional actions are written to infotype 0302. Before doing so, check the
settings in the T529A table to make sure that actions (MASSN) are written into infotype 0000 and
0302.

2. [OPTIONAL] Mark the Mult. Actions checkbox in Configure Compound Employee API
Query under Customizing for Personnel Management Integration Settings for
SuccessFactors Employee Central Payroll Configuration of Point-to-Point Replication.

Things to Consider Before Enabling the Replication

 The infotype framework doesn’t support the replication of multiple employee status changing
events like hire or fire, on one day. You get an error message and the replication fails. For more
information, see Troubleshooting Two Different Employment Statuses on the Same Day.

Note

Due to time constraint 1, you can only update one event/action to infotype 0000 per day. If more than one
is added on one day, the event with the highest priority is added. You can prioritize the actions in
view V_529A_B with the field ORDNR. The Action with the lowest ORDNR has the highest priority. For
these actions, there’s only one entry in infotype 0302, no matter how often a day an event is entered in
the Job Information.

 Infotype 0000 has time constraint 1: No overlaps and no gaps are permitted from the hire date to
the highest end date (December 31, 9999).

 Infotype 0302 has time constraint 3: Overlaps are allowed. It means, if the action is customized to
be filled into infotype 0302 only, you can add as many events as wanted.

Related Information

Troubleshooting Two Different Employment Statuses on the Same Day

>>>>>Troubleshooting Job Information

Here's a look at some issues you might encounter in the Job Information and what you can do to fix them.

Troubleshooting Two Different Employment Statuses on the Same Day

How to solve situations where employees are Active and Inactive on the same day.

Hiring with Two Job Information Records

How to troubleshoot hiring with two Job Information records.

How to Correct Job Information Data

Understand the difference between using the Edit and Make Correction features when correcting Job
Information data in Employee Central.

>>>>>>Troubleshooting Two Different Employment Statuses on the Same Day

On this page

 What's the Issue?

 What You Can Do

How to solve situations where employees are Active and Inactive on the same day.

What's the Issue?

Depending on whether or not the switch EVSUP from the ADMIN Group is activated for additional actions in
the T77S0 view, you get the following messages:

 Switch EVSUP is ON: Employee is active since...

 Switch EVSUP is OFF: Don’t add more than 1 employment status changing actions at same
day &1

Reasons

There are several different reasons for the errors:

 After the mapping, two personal actions, for example Termination and Rehire, exist on the same
day for the same personal number. As a consequence, the employee is Inactive and Active on the
same day in the Employee Central Payroll system. The Actions (0000) infotype forbids such a case,
that is, two different employment statuses on the same day.

 An intercompany transfer is maintained for an employee for which the hire date of the employment
in the new legal entity and the termination date in the previous legal entity are the same. This
leads to replication errors because an employee can’t be active and inactive on the same date.

What You Can Do

Here is what you can do to correct the errors:

1. Create an employment for the new company. Before creating it, remove the last Job
Information record of the previous employment that caused the error.

Note

We strongly recommend that you maintain the termination in the previous employment and rehire the
employee in Employee Central using the Rehire with new employment event.

2. Configure a payroll event for only one employment. For more information, refer to Two Status
Changing Event Reasons on the Same Day

>>>>>>Hiring with Two Job Information Records

On this page

 What's the Issue?

 What You Can Do

How to troubleshoot hiring with two Job Information records.

What's the Issue?

If you receive the following errors, it may be caused by hiring an employee with two Job
Information records.

Error Message Text

Invalid combination of action type 01/action

reason PP

Start date before initial entry date

 Error Message Text

(31.12.9999)

Here are the details of each record causing the error:

Record Start End Eve Event Reason Sequence Code Value

Date Date nt Number Mapping

Personal 1.1.201 1.1.2018 H New Hire isn’t mapped. As a 0 Event H is

action 1 8 consequence, there’s no mapped to
event reason defined for this Hiring action
action. 1.

Personal 1.1.201 31.12.99 5 Data Change is mapped to 1 Event 5 is

action 2 8 99 action reason PP. mapped to
Hiring action
2.

Personal action 2 is used for the hire because the Job Information record is considered as active.
However, since event 5 is mapped to the Organizational Change action and not the hire action, action 1
is automatically inserted as default personal action. As a result, you receive the error Invalid
combination of action type 01/action reason PP because this combination isn’t allowed in
the T530 table.

What You Can Do

To fix the error, select one of the following options:

 Delete the second job information record using the job information history. Replicate the hire once
again. Once the hire is replicated successfully, insert the second record again.

 Define a new event reason for the Data Change event. This event must be allowed for the
corresponding hire action. Note that you fill the Payroll event field with an event reason code NOT
mapped to any personal action.

 If you decide to keep the records causing the error, go to SM30, enter the V_T530 view. Define the
hiring action and action reason accordingly.

>>>>>>How to Correct Job Information Data

On this page

 What's the Issue?

 What You Can Do

Understand the difference between using the Edit and Make Correction features when correcting Job
Information data in Employee Central.

What's the Issue?

If you receive an error message that says Succession of the same action of type &1 is not
supported, the reason may be that you use the Edit standard feature to create a job information. In fact,
you create it at the same time as the existing employment.

What You Can Do

Correct the Job Information record using the Make Correction feature. Select an event and event
reason for the Job Information. Usually, as an HR admin, you select a Data Change event or an event
including a payroll event for a mapped organizational change personal action.

>>Job Information - Infotype 0001

On this page

 Job Information (Infotype 0001)

 Infotype 0001 Fields That Are Automatically Filled

 Related Information

Here you find an overview of generic fields. These fields allow you to map Job Information of an employee
from Employee Central to Employee Central Payroll.

Job Information (Infotype 0001)

Employee Central Payroll Employee Central

IT0 Manda Ma Data Type Defa Is Code Field Field Manda Picklist
001 tory? x. for Code ult- Value ID Label tory? ID
Tar Len Value Map Mapping
get gth Mapping ping Country/
Mod Region
e Specific?

BTR Yes 4 - - - location Locatio No -

TL n

WE
RKS

BUK Yes 4 - - - compan Compa No -

RS y ny

KOS No 10 - - - cost- Cost No -

TL center Center

PER Yes 1 EMPLOYEE_ Custo No employ Employ No employee

SG CLASS mer ee- ee Class
Table class Class

PER Yes 2 EMPLOYME Custo Yes employ Employ No employm

 Employee Central Payroll Employee Central

IT0 Manda Ma Data Type Defa Is Code Field Field Manda Picklist
001 tory? x. for Code ult- Value ID Label tory? ID
Tar Len Value Map Mapping
get gth Mapping ping Country/
Mod Region
e Specific?

SK NT_TYPE mer ment- ment entType

Table type Type

ANS No 2 CONTRACT_ Custo Yes contrac Contrac No contractT

VH TYPE mer t-type t Type ype
Table
or
Identi
cal
Mapp
ing

STE No 8 - - - job- Job Yes -

LL code Classific
ation

PLA No 8 - - - position Position No -

NS

ORG No 8 - - - busines Busines No -

EH s unit s Unit

depart Depart
ment ment

division Division

Infotype 0001 Fields That Are Automatically Filled

The field... ...is derived from...

Administrator Group (SBMOD) the country grouping (MOLGA) that belongs to the
country code of the work agreement item.

Administrator the first entry in table T526, belonging to the

personnel area defined by
(SACHP)
the PERMANENT_ESTABLISHMENT_ID of the work
 agreement item.

Organizational Key cost center and personnel area.

(VDSK1)

Note

If you want to modify feature VDSK1, use

BAdI Change mapped infotype 0001
data (HRSFEC_B_CE_CHANGE_IT0001).

Related Information

Implementing BAdIs to Enhance Already Mapped Master Data

>>>Known Issue: Inconsistent Assignment of Personnel Area to Company Code

On this page

 What's the Issue?

 What You Can Do

How to correct an inconsistent assignment of personnel area to company code.

What's the Issue?

If you receive the message that says Inconsistency for assignment of personnal area &1 to
company code &2, it may be caused by an inconsistent assignment of the personnel area to the
company code.

Note

To ensure a successful replication of employee data, a personnel area must be assigned to a company
code. The personnel area feeds the first characters of the location mapping key. The company code must
be mapped to a legal entity in Employee Central.

What You Can Do

Correct the data in Employee Central or go to Employee Central Payroll. Modify the inconsistent
assignment in the V_T500P view, if appropriate, maintain the assignment in the view if the assignment is
missing.

Job Information - Infotype 0007

Here you find an overview of generic fields. These fields allow you to map Job Information of an employee
from Employee Central to Employee Central Payroll.
>>Job Information (Infotype 0007)

Employee Central Payroll Employee Central

IT00 Mandat Max Data Defa Is Code Field ID Field Mandat Pickl
07 ory? . Type ult- Value Label ory? ist
Targ Len for Mapp Mapping ID
et gth Code ing Country/R
Value Mode egion
Mapp Specific?
ing

TEILK No 1 - - - is-fulltime- Fulltim No -

employee e
emplo
yee
indicat
or

WKW Yes 4 - - - workingDaysP Worki No -

DY erWeek ng
days
per
week

SCHK No 8 - - - workschedule- Work No -

Z code Sched
ule

Note

The EMPCT (Employment percent) field is calculated by the infotype framework. If EMPCT is lower than
100, the TEILK and DYSCH fields are set by default. In this case, TEILK is overwritten although the
employee is determined as is full time employee.

How to Exclude Infotype 0007 from Replication

See how to exclude infotype 0007 from the replication.

Using the Payroll Switch Weekly Workday Information (WKWDY)

Controlling the replication of infotype 0007 by enabling the switch WKWDY.

Enabling the Replication of Casual Workers

See how to enable the replication of casual workers from Employee Central.

Working Hours

See how working hours are replicated from Employee Central.

Work Schedule ID

Working Week

There are two ways to determine the value for Working Week WWEEK:

>>>How to Exclude Infotype 0007 from Replication

On this page

 Context

 Related Information

See how to exclude infotype 0007 from the replication.

Context

Here are the options you can select to exclude infotype 0007 from the replication process:

1. In your Employee Central Payroll system, use the Infotype Filter to filter out infotype 0007. For more
information on filtering infotypes, see Infotype Filtering.

2. In your Employee Central system, leave the Working Days per Week field empty and make sure
that the switch WKWDY doesn’t have the value 2.

Related Information

Filtering by Infotype
>>>Using the Payroll Switch Weekly Workday Information (WKWDY)

Controlling the replication of infotype 0007 by enabling the switch WKWDY.

Procedure

1. In your Employee Central Payroll system, go to the T77S0 table by specifying transaction SM30.

2. Select Position then enter SFEC in the Group Name field and WKWDY in the Semantic
abbr. field.

3. Activate the switch by selecting the value from the drop-down list of the Value abbr. field.

The following table gives information on the values you can choose:

Value of Description
Switch
WKWDY

Empty If the Working Days Per Week field is empty, the infotype 0007 is not
replicated. The value Blank means that the system sends a warning
message.

1 If the Working Days Per Week field is empty, the infotype 0007 is not
replicated. The value 1 means that the system sends an error message.

2 [Only relevant for the casual workers scenario]: If the Working Days Per
Week field is empty for the selected personnel numbers (PERNRs), the
replication of infotype 0007 is successful.

4. Save your settings.

>>>Enabling the Replication of Casual Workers

On this page

 Prerequisites

 Context

 Procedure

See how to enable the replication of casual workers from Employee Central.

Prerequisites

Make some important initial settings in Employee Central before replicating casual workers to Employee
Central Payroll:

 Leave intentionally the Working Days per Week field empty in the Job Information block.

 Leave the Standard weekly hours field empty and don't use extensibility when setting the hours.
  Define a work schedule in Employee Central for casual workers.

 In Work Schedule Replication Exclusion, create a list to include work schedule rules for casual
workers. For more information, see Work Schedule Replication Exclusion List

 In the Employee Central Payroll system, select 2 to activate the switch WKWDY.

Context

You can replicate zero working days for casual workers who don’t have a working pattern in Employee
Central. It means that an infotype 0007 can be created in Employee Central Payroll.

Procedure

1. Specify a work schedule rule for casual workers.

For more information about the settings in Employee Central Payroll, see KBA 2990393 .

2. Create the code vale mapping for SCHKZ in Maintain Code Value Mapping in the Customizing
for Integration Settings for SuccessFactors Employee Central Payroll Assignment of
Code Values For Point-to-Point Replication.

Mapping in T77SFEC_CVMAPC

Data type in Employee ISO Alt. Employee Central Code ERP Code
Central code list Value Value

WORK_SCHEDULE_RULE AU CASUAL CASUAL

3. Save your settings.

>>>Working Hours

On this page

 Replication by Default

 Replication using Basic Extensibility

 Dummy Work Schedule

 Related Information

See how working hours are replicated from Employee Central.

Replication by Default

The following fields are calculated automatically by the system, as described in the table:

Infoty Field Name Infotype Is calculated using:

pe Field

0007 Daily working ARBST Employee Central standard weekly hours divided
hours by Employee Central working days per week

0007 Employment EMPCT Daily working hours (ARBST) and Work Schedule Rule (SCHKZ)
 Infoty Field Name Infotype Is calculated using:
pe Field

percent

0007 Weekly working WOSTD Employment percentage (EMPCT) multiplied by the respective
hours values as defined in table T508A for work schedule.
MOSTD
Monthly
JRSTD
working hours

Annual working
hours

Note

In Employee Central, you should ensure the entries for working hours (standard-hours) or days
(workingDaysPerWeek) make sense, for example, don’t enter more than 7 days for a working week.

Note

It’s important that feature WRKHR has been maintained correctly. Go to transaction PE03 in Employee
Central Payroll and make sure it looks like this:

Replication using Basic Extensibility

Alternatively, you can use basic extensibility to replicate to infotype 0007 fields for Working Hours:

Example

You can map the Standard Weekly Hours field in Job information to the WOSTD field using basic
extensibility. Then, you include this field as calculation basis in feature WRKHR set to W/X. WOSTD is
mapped from the Standard Weekly Hour field. All other working hours fields like ARBST, MOSTD,
JRSTD are derived from the calculation.

You can make the following settings:

This Makes this field

setting... editable...

W/X Working Hours per

Week
 This Makes this field
setting... editable...

M/X Working Hours per

Month

Y/X Working Hours per Year

Dummy Work Schedule

Working hours aren’t automatically calculated by the system.

Planned working times are replicated to infotype 2003. It’s required to specify a dummy work schedule rule
in infotype 0007. How to handle infotype 0007 is provided in KBA 2984800 .

Related Information

Basic Extensibility: Mapping Employee Central Fields to Infotypes

Extensibility

Defining Dummy Work Schedule

>>>Work Schedule ID

On this page

 Deriving the Work Schedule from Settings in Employee Central Payroll

 Related Information

To set up replication of Work Schedule ID to infotype 0007 you have to create mapping in
table T77SFEC_CVMAPC to Employee Central Payroll value SCHKZ.

Infotype 0007 is created from the mapping table using the Work Schedule Rule.

Deriving the Work Schedule from Settings in Employee Central Payroll

If the Employee Central value or * (asterisk) is mapped to space in table T77SFEC_CVMAPC, table T508A is
evaluated with parameters based on Personnel Area and Personnel Subarea of infotype 0001.

 If NORM is found in table T508A, infotype 0007 is created with Work Schedule NORM.

 If NORM is not found in table T508A, then infotype 0007 is created based on the first hit in
table T508A after sorting by SCHKZ.

Related Information

Assignment of Code Values

>>>Working Week

There are two ways to determine the value for Working Week WWEEK:

 In the Employee Central, add a custom field to Job Information and map it using Basic Extensibility
to Employee Central Payroll.

 In the Employee Central Payroll system, use the WWEEK feature and implement
BAdI HRSFEC_B_CE_CHANGE_IT0007 to change the already mapped infotype data for infotype 0007.
For more information, refer to the system documentation.
Note

It isn’t enough to just maintain the WWEEK feature. If you don't implement the BAdI as well, the data is
ignored by the replication.

Related Information

Extensibility

>>Job Information - Infotype 0008

Here you find an overview of generic fields. These fields allow you to map Job Information of an
employee from Employee Central to Employee Central Payroll.

Job Information - Infotype 0008

Employee Central Payroll Employee Central

IT0 Mandat Max Data Type Defau Is Code Field ID Fie Mandat Pickl
008 ory? . for Code lt- Value ld ory? ist
Tar Len Value Mappi Mapping La ID
get gth Mapping ng Country/R bel
Mode egion
Specific?

TRF Yes 2 PAY_SCALE_A Custo Yes payScaleA Pay No -

GB REA mer rea scal
Table e
are
a

TRF Yes 2 PAY_SCALE_T Custo Yes payScaleT Pay No -

AR YPE mer ype scal
Table e
typ
e

TRF No 8 PAY_SCALE_G Custo Yes payScaleG Pay No -

GR ROUP mer roup scal
Table e
gro
up

TRF No 2 PAY_SCALE_L Custo Yes payScaleL Pay No -

ST EVEL mer evel scal
Table e
lev
el
Capacity Utilization Level

Full-Time Equivalent (FTE)

Find out how to replicate the Employee Central Full-time Equivalent (FTE) field to the Basic Pay (0008)
infotype.

>>>Capacity Utilization Level

On this page

 Default Replication Logic

 Fill Infotype 0008 with Employee Central Custom Fields from Compensation Information

 Fill Infotype 0008 with Employee Central Custom Fields from Job Information

 Related Information

Default Replication Logic

The Infotype Framework defaults the infotype 0008 fields Capacity Utilization Level, Work
Hours/Period, and Annual Salary based on the content of infotype 0007 field Employment percent.

Fill Infotype 0008 with Employee Central Custom Fields from Compensation Information

The following fields are filled with custom fields.

Properties and Length of the Fields

Employee Central Payroll

IT0008 Mandatory? Max. Length

Target

TRFGR No 8

TRFGB Yes 2

TRFAR Yes 2
 Properties and Length of the Fields

Employee Central Payroll

IT0008 Mandatory? Max. Length

Target

TRFST No 2

BSGRD Yes 5

DIVGV Yes 5

STVOR No 8

ANSAL No 15

EIN01 No 3

CPIND No 1

Fill Infotype 0008 with Employee Central Custom Fields from Job Information

The following fields are filled with custom fields:

Properties and Length of the Fields

Employee Central Payroll

IT0008 Mandatory? Max. Length

Target

BSGRD Yes 5

DIVGV Yes 5

STVOR No 8
 Properties and Length of the Fields

Employee Central Payroll

IT0008 Mandatory? Max. Length

Target

ANSAL No 15

ANCUR No 5

CPIND No 1

Related Information

Basic Extensibility: Mapping Employee Central Fields to Infotypes

>>>Full-Time Equivalent (FTE)

Find out how to replicate the Employee Central Full-time Equivalent (FTE) field to the Basic Pay (0008)
infotype.

Here are the options for mapping the FTE field to the BSGRD and DIVGV fields of the Basic Pay (0008)
infotype:

Option Description

Direct Mapping of the value Example

Field FTE

You want to map the FTE field from Employee Central to

the BSGRD (Capacity Utilization Level) field of IT0008 in Employee
Central Payroll. Note that the BSGRD field is only filled with a
percentage. For that reason, create a custom field to multiply
the Employee Central FTE by 100. By doing so, you ensure that
field BSGRD is filled with a percentage.

In the V_HRSFEC_EXTMAP view, press F4 in each column to select

the respective value. For example, press F4 in the Employee
Central Node Name column. You get the list of EC node names,
select job_information.
 Option Description

Employee EC Element Infoty Field Data Type

Central No pe in Employ
de Name ee Central

job- custom_doubl 0008 BSGR

information e2 D

Caution

For Brazil and India DIVGV is an obligatory field in

table T588MFPROPS. Activate both fields in
the V_T588MFROPC view.

Note

If one of the BSGRD or DIVGV fields from infoype 0007 is empty,

the framework calculates it using the standard logic.

If you want to keep the BSGRD field empty, use basic extensibility
in the V_HRSFEC_EXTMAP view so that the calculation is skipped
even if the field is empty.

If you want to keep the DIVGV field empty, use

either V_HRSFEC_EXTMAP or enable the Time-Dependent
Replication Framework so that the calculation is skipped even if the
field is empty. For more information, refer to Enabling Time-
Dependent Replication Framework.

For more information on how to map standard fields, refer to Basic

Extensibility: Mapping Employee Central Fields to Infotypes .

Advanced Mapping of the For more information, refer to Implementing BAdIs to Enhance
value Already Mapped Master Data.

If more information is needed

than the one provided with the
basic mapping, implement
BAdI HRSFEC_B_CE_CHANGE_IT00
08. BAdIs overrule the existing
settings.

>>Job, Position, and Org. Unit

Switch the replication of Job, Position, and Org. Unit on in table T77S0.

1. Go to transaction SM30.

2. Enter table / view V_T77S0.

3. Click Maintain.
 4. Click New entries.

5. Enter the following data:

 Group: SFEC

 Semantical abbreviation (sem.abbr): JBPS

 Value abbreviation (Value abbr): X

>>>Checking and Creating Jobs, Positions and Org. Units

On this page

 Prerequisites

 Context

 Procedure

 Results

Find out how to run the RP_HRSFEC_JOB_POS_REPL report. Additionally, there’s a local version of this
report RP_HRSFEC_JOB_POS_REPL_WCS available for Brazil, Canada, and Hong Kong.

Prerequisites

 You must make an entry in fields Code, Title, (either in required languages or default), and Start
Date in Employee Central for MDF objects Job Classification, Position, Business
Unit/Department/Division. The replication report ignores the object if any of these fields are not
filled.

Note

Since Employee Central is the primary system, the objects must always be available for successful
replication. Deleting and not entering the title of objects in Employee Central may result in missing objects
in Employee Central Payroll database tables if a correction is made due to inconsistencies.

 Before you run this report, make sure that Organizational Management Integration isn’t enabled.

 For replicating Org. Units, you have to set the switch for group SFEC and semantic
abbreviation OURPL accordingly.

 For the automated run, you have to set the Connection Data using the Configuration Report
(RP_HRSFEC_PTP_CONFIGURATION) for Employee Central Payroll.

 For the manual run, you must first export job, position, and org.unit data from Employee Central. To
export this data, search for Import and Export Data in search field of the Employee
Central system. Choose Export Data, specify the object you want to export, and export. For Org.
Units, you must select the object (business unit, department, or division) you’ve defined in the
switch.

Note

For CBO codes Brazil, check the Include Dependencies flag before exporting positions.

 Only if you want to use external numbering for Jobs, Positions and Org. Units: Set the switch for
group SFEC and semantic abbreviation EXJPO.

Context
You use the Check and Create Jobs, Positions, and Org. Units report (RP_HRSFEC_JOB_POS_REPL) to import
all the Employee Central job, position, and org. unit master data to Employee Central Payroll. You can also
check, if some data is missing or incorrect.

Note

The texts for job, position, and org. unit master data are stored in standard tables. Therefore, the text
length is limited to maximum 25 characters. You can’t change this length. If you exceed the maximum
length of 25 characters, the texts get truncated.

There are two ways of running this report:

 Automatically: Run the report in the background and schedule it regularly. If you have multiple
languages, create one variant for each language and schedule a background job for each variant.

 Manually: Run the report separately for each language.

Procedure

1. Select Automated or Manual, depending on how you want to run the report.

2. For the Automated run, provide following data:

a. Under Importing Language, enter the language that is used for the import.

b. Set the flag for Job Description, Position Description, and/or Org. Unit Description to
specify the descriptions to be replicated. Specify at least one of these checkboxes before
you can run the report.

c. Set the flag for Display Output before Change, if you want to display the output first
before proceeding manually. The checkbox is ignored, when running the report in the
background.

3. For the Manual run, provide following data:

a. Under Importing Language, enter the language used in the files.

b. Under Import Jobs File, Import Positions File and/or Import Org. Unit File, select the
CSV file that you’ve exported from Employee Central. Specify at least one of these files
before you can run the report.

c. Set the flag for With extra ERP only entries, if you also want to show the equivalent
entries that exist only in Employee Central Payroll.

d. Set the flag for Hide all entries that are OK, if you want to hide entries that don’t require
any further changes.

4. (Optional) Select your own variant of this report under Layout Variant.

5. Run the report.

Results

Any entries that are missing or incorrect are highlighted in red. The standard screen layout is as follows:

 Object indicates, if the entry refers to a job, position or org. unit.

 Mapping exists or not.

 Job OK, which indicates whether all job properties in Employee Central Payroll are the same as
in Employee Central.
  Job definition properties (ID, Description, Start Date, End Date) are displayed, which are derived
from T513 table.

 Position OK indicates whether all position properties in Employee Central Payroll are the same as
in Employee Central.

 Position definition properties are displayed, which are derived from T528b table, such
as ID, Description, Start Date, and End Date.

 Org. Unit OK indicates, whether all Org. Unit properties in Employee Central Payroll are the same
as in Employee Central.

 Org. Unit definition properties are displayed, which are derived from T527X table, such
as ID, Description, Start Date, and End Date.

>>Location

In Employee Central, location is represented by an instance of the foundation object Location. For every
location, you need to create a personnel subarea in Employee Central Payroll including information for
the personnel area and related customizing settings. The codes for personnel subareas are checked and
maintained with table T001P.

In the inbound service, mapping entries in table T77SFEC_KMAPPEST are required. Access this table in the
Customizing activity Assign External Place of Work Keys to Internal Place of work Keys.

Related Information

Assigning Key Mapping of Organizational Data

>>Mapping Company to Company Code

On this page

 Prerequisites

 Context

 Procedure

 Related Information

Prerequisites

To map the Company from the Job Information block to the Company code in the Employee Central
Payroll system, make sure that organizational master data exists in the Employee Central Payroll. For more
information, see Assigning Key Mapping of Organizational Data.

Context

In Employee Central, Company is represented by an instance of the Legal Entity foundation object. For
every company, you need to create a company code in Employee Central Payroll including the customizing
settings needed for payroll processing. The company codes are checked and maintained with table T001.

Note

Mapping entries are required if the length of the element company is longer than 4 characters.

Procedure

1. In the Employee Central Payroll system, go to transaction SPRO and choose SAP Reference IMG.

2. Choose Assign External Company Code Keys to Internal Company Code

Keys (T77SFEC_KMAPCOMC) under Customizing for Personnel Management Integration
 Settings for SuccessFactors Employee Central Payroll Assignment of Key Mapping of
Organizational Data to map Employee Central Company ID with Company code.

Data is replicated based on the following sequence:

a. At least one company is specified in the Company field. Otherwise, an error message is
raised and the replication process stops.

b. A company code is mapped to a given company.

c. A company code is mapped to a default company. Use * to search if a company exists

in Employee Central.

d. If the length of the company is 4, map the company code to the company.

e. If nothing is found during the replication process, an error message is raised asking you to
make the required settings.

Related Information

Assigning Key Mapping of Organizational Data

>>Compensation Information - Infotype 0001

Here you find an overview of generic fields. These fields allow you to map Compensation Information of an
employee from Employee Central to Employee Central Payroll.

Employee Central Payroll Employee Central

IT00 Mandat Max. Data Type Defaul Is Code Mandat Fiel Fiel Pickl
01 ory? Len for Code t- Value ory? d d ist
Targ gth Value Mappi Mapping ID Lab ID
et Mapping ng Country/Re el
Mode gion-
Specific?

ABK Yes 2 PAYROLL_GR Custo Yes No pay Pay -

RS OUP mer - Gro
Table gro up
up

Note

To enable the replication of this data to Employee Central Payroll, set in the Succession Data Model
the Pay Group field as mandatory in Compensation Information. The Pay Group field is no longer
needed in Job Information for the employee master data replication.

>>Biographical Information - Infotype 0002 and 709

Here you find an overview of generic fields. These fields allow you to map Biographical Information of an
employee from Employee Central to Employee Central Payroll .
Mapping Table for Infotype 0002

Employee Central Payroll Employee Central

IT000 Mand Max. Data Defa Is Code Field Field Mandator Pickli
2 atory? Leng Type ult- Value ID Label y? st ID
Targe th for Map Mapping
t code ping Country/
valu Mod Region-
e e Specific?
map
ping

GBDA Yes 8 - - - date-of- Date of No -

T birth Birth

GBLN No 3 - - - country Country/ No -

D -of- Region of
birth birth

GBOR No 40 - - - place- Place of No -

T of-birth birth

NAME No 40 - - - birth- Birth Name No -

2 name

GBDE No 3 - - - region- Region of For IT and -

P of-birth Birth FR

Mapping Table for Infotype 0709

Employee Central Payroll Employee Central

IT0709 Mand Max Data Defaul Is Code Field ID Field Mand Pick
Target atory? . Type t- Value Label atory? list
Len for Mappi Mappin ID
gth code ng g
valu Mode Country
e /Region-
map Specific
ping ?

person-id- Yes 20 - - - employee_i Person Yes -

external d_external ID
 Mapping Table for Infotype 0002

Employee Central Payroll Employee Central

IT000 Mand Max. Data Defa Is Code Field Field Mandator Pickli
2 atory? Leng Type ult- Value ID Label y? st ID
Targe th for Map Mapping
t code ping Country/
valu Mod Region-
e e Specific?
map
ping

Remembe
r

We
recommen
d you to
set the
visibility
of person-
id-external
to view in
HRIS
element pe
rsonInfo of
the
Succession
Data
Model.

Note

For Concurrent Employment: Activate the CCURE PIDGN or CCURE PIDSL switches to set up the personnel
external ID in the initial screen for master data maintenance like PA30.

Remember

We recommend you to set the visibility of person-id-external to view in HRIS element personInfo of the
Succession Data Model.

Related Information

Enabling Concurrent Employment in Employee Central Payroll

>>Personal Information - Infotype 0002

Here you find an overview of generic fields. These fields allow you to map Personal Information of an
employee from Employee Central to Employee Central Payroll.
Employee Central Payroll Employee Central Additional
Information

IT0 Mand Ma Data Def Is Code Field Fiel Mand Pickl

00 atory x. Type ault Value ID d atory ist
2 ? Le for - Mappin Labe ? ID
Tar ng Code Ma g l
get th Value ppi Countr
Mappi ng y/Regio
ng Mo n-
de Specifi
c?

FA No 1 MARIT - - marit Marit No -

MS AL- al- al
T STATU status statu
S s

FA No 8 - - - marit Marit No -
MD al al
T status statu
since s
since

SPR Yes 1 - - - native Nativ No langu Use the two

SL - e age character ISO
prefer prefe 639 language
red- rred codes as
lang lang provided
uage in Employee
Central and also
supported
in Employee
Central Payroll. If
an error is raised
during the
replication, check
the language
codes available
in table T002 in
the Employee
Central
Payroll system.

GE No 1 GENDE SAP No gende Gend No Gend The outbound

SC R tabl r er er service sends the
H e values M = male
and F=female.
Do not associate
Employee Central Payroll Employee Central Additional
Information

IT0 Mand Ma Data Def Is Code Field Fiel Mand Pickl

00 atory x. Type ault Value ID d atory ist
2 ? Le for - Mappin Labe ? ID
Tar ng Code Ma g l
get th Value ppi Countr
Mappi ng y/Regio
ng Mo n-
de Specifi
c?

this field with a

picklist. The
values are
automatically
mapped using
the inbound
service.

In this case, no
additional
mapping is
required.

NA No 40 - - - birth- Birth No -
ME name Nam
2 e

VO No 40 - - - firstN Give No -
RN ame n
A nam
e

NA No 40 - - - third- Third No -
CH name Nam
2 e

NA Yes 40 - - - lastNa Famil No -

CH me y
N nam
e

MID No 40 - - - middl Middl No -

NM eNam e
e nam
Employee Central Payroll Employee Central Additional
Information

IT0 Mand Ma Data Def Is Code Field Fiel Mand Pickl

00 atory x. Type ault Value ID d atory ist
2 ? Le for - Mappin Labe ? ID
Tar ng Code Ma g l
get th Value ppi Countr
Mappi ng y/Regio
ng Mo n-
de Specifi
c?

VO No 15 NAME_ - - name- Prefi No nam

RS PREFIX prefix x epre
W , fix
mappe
d via
SAP
table

VO No 15 NAME_ - - partn Partn No nam

RS PREFIX er- er epre
2 , name- Nam fix
mappe prefix e
d via Prefi
SAP x
table

NA No 15 NAME_ SAP No name Suffi No -

MZ SUFFIX tabl Suffix x
U e

AN Yes 1 SALUTA SAP No saluta Salut No salut The Employee

RE TION tabl tion ation ation Central field salu
D e tation is
associated to the
picklist
ID salutation.
In Employee
Central, the
external codes
for this picklist ID
are filled with the
values Mr and
 Employee Central Payroll Employee Central Additional
Information

IT0 Mand Ma Data Def Is Code Field Fiel Mand Pickl

00 atory x. Type ault Value ID d atory ist
2 ? Le for - Mappin Labe ? ID
Tar ng Code Ma g l
get th Value ppi Countr
Mappi ng y/Regio
ng Mo n-
de Specifi
c?

Ms.

Caution

Set this field to

mandatory
in Employee
Central.

TIT No 15 - - - title Title No -

LE

INIT No 10 - - - initial Initia No -

S s ls

NA Yes 3 - - - nation Natio No -

TIO ality nalit
y

RU Yes 40 - - - Nickn Prefe No - You can activate

FN ame rred the MAP_PREFER
M Nam RED_NAME switc
e h in the case
described
in Enabling Time-
Dependent
Replication
Framework

Note

If you’re having problems with country/region-specific replication, meaning, you aren't seeing the correct
country/region-specific screens, ensure that the feature IVWID is set for infotype 0002.

The mapping can vary depending on the country or region of the employee. Additionally, mandatory
settings can vary per country or region. For more information, see the Country/Region Specifics for
Employee Central Payroll guide.
Note

 When a gender is maintained in the Global Information block for an employee, replicate that
gender. If not, replicate the gender mentioned in the Personal Information block.

 •The third gender is currently supported in following countries; Australia,Austria,India,Germany,

New Zealand, Argentina,United States of America,Canada, and Mexico.

 For any country specific gender replication, refer to the Country/Region Specifics for Employee
Central Payroll guide.

>>National ID Card - Infotype 0002

Here you find an overview of generic fields. These fields allow you to map National ID Card of an employee
from Employee Central to Employee Central Payroll.

Employee Central Payroll Employee Central

IT0 Mandat Max Data Defa Is Code Field ID Field Mandat Pickl
002 ory? . Type ult- Value Label ory? ist
Tar Len for Mapp Mapping ID
get gth Code ing Country/R
Value Mode egion-
Mapp Specific?
ing

- Yes - - - - nationalId Country/ - -

Card region

PERI Yes 20 - - - national- - -

D id

No further mapping is required.

Note

Only national-ids that are flagged as primary in Employee Central are replicated to infotype 0002.

Note

Temporary ID from national-id block in Employee Central is replicated to Employee Central

Payroll when IS_TEMPORARY field is set as true in Employee Central.

Note

national-id is required for replication for Canada, Czech Republic, Finland, France, Spain, Sweden, the
United Kingdom, and the United States.

For Brazil, national-ids are NOT replicated.

Note

Certain country/region versions use additional secondary infotypes for national-id: Austria, Egypt, India,
Malaysia, Oman, Mexico, and Singapore (infotype 0185), Brazil (infotype 0465), Japan (infotype 0140), and
Russia (infotype 0037). These additional infotypes aren’t yet supported for replication, except that Pan
Card information for India is replicated into infotype 0185. For information about PAN Card replication for
India, see SAP Note 2126080. Replication to infotype 0185 is supported for China, Hong Kong, Thailand,
United Arab Emirates, and Saudi Arabia.