Exploring Appendix C

• For an overview and a list of supported countries, see the Country Specifics for Employee Central Payroll guide.
• Point to point replication, without the use of a middleware, is now available for the integration between Employee Central and Employee Central Payroll for employee master data, absences and, time valuation results (HR Renewal 2.0 SP28).
• There is a new tile on the Home Page in SAP SuccessFactors called ‘Complete Payroll Tasks’ to guide Administrators through the Hiring Process when entering payroll-related information.
• See the SAP Note for what addons are available for Employee Central Payroll.
  • https://launchpad.support.sap.com/#/notes/2167337
• Country-specific fields are replicated from Employee Central Time Off to the Absences (2001) infotype in Employee Central Payroll for Germany and Spain. For Germany, country-specific logic for relationship handling of Time Off records (linking of Absences) is now supported. This is only available for implementation with software component EA-HRRXX as of HR Renewal 2.0 SP28.
• A new address type is now available for global assignments. For example, during an assignment of an employee it may be required to enable distinct residence addresses for home and host assignment to calculate taxes properly or to be able to run payroll in home and host country separately.
• Previously, there was a dedicated Payroll Implementation Check available from the Admin Center.

  From Q1 2018, the Payroll Implementation Check Tool will be available from the Configuration Check Tool in the Admin Center.

  • Three new checks have been added to the Configuration Check Tool in Employee Central Admin Center for time and absence data replication to Employee Central Payroll to help you ensure that the configuration between Employee Central Time Off and Employee Central Payroll is consistent.

• The MDF object Payroll Data Maintenance Task Configuration can be used to configure life and work events for Employee Central Payroll.
• As of EA-HRRXX SP028, Payroll Control Center has the Event Handler functionality. The Event Handler identifies automatically relevant master data changes in the Employee Central Payroll system and validates these changes against the defined policies only for the employees with changes.
• As of EA-HRRXX 608 SP28, Payroll Control Center is integrated with the core functions in the Employee Central Payroll system: Delete Personnel Data (PU00) transaction and Delete Personnel Numbers Completely (RPUDELPN) report. As a result, when an employee is deleted from the system, the related Payroll Control Center data can also be deleted.
• You can also use the report PYD_DLM_DELETE_TOOL in Employee Central Payroll to delete application data related to Payroll Control Center.

• Address Check for non-ECP countries - new check in the Check Tool to ensure consistency of address information in all Employee Central localized countries. This includes ECP and non-ECP countries.
• Check Length for Jobs and Positions - new check in the Check Tool to ensure, that the maximum length for jobs and positions is compiled.
• Minor Updates for Data Model and BSI Checks - the Data Model checks of the Payroll Information application in the Check Tool were updated and enhanced.
• EC Check Tool - Update and Improve Data Model Check, the Data Model checks of the Payroll Information application in the Check Tool were updated and enhanced.
• Wage Type Check Tool - enable oData connection to read data - the Wage Type Check Tool is enhanced with an oData connection.
• Consolidate and provide central access to check tools (IMG) - all mapping check tools are available in the Customizing of Employee Central Payroll.

• You are an Employee Central Payroll customer and Employee Central Payroll is switched on in provisioning

• You use Point-to-Point integration

• You have applied EA-HR Support Package 54 to your Employee Central Payroll system

• You are an Employee Central Payroll customer and Employee Central Payroll is switched on in provisioning

• You use Point-to-Point integration

• You have applied EA-HR Support Package 54 to your Employee Central Payroll system

From the Q4 2018 release, you can configure your own payroll task types at a generic level based on the event reasons defined in Employee Central. A Payroll Data Maintenance Task with the Payroll Data Maintenance Task type EVENT_REASON_NAME is triggered if a new record is created by pressing the Take Action button and the replication of the employee to Employee Central Payroll is successful.

Previously, it was only possible to select standard payroll task types, that is, New Hire, Address Change and Termination.

To use this feature, upgrade your Employee Central Payroll system to the SAP EA-HR SP 60 support package.

From the Q1 2019 release, a feature has been introduced in the Data Replication Configuration. The new field 'Exclude Contingent Workers' allows you to exclude contingent workers from the replication of time data, from Employee Central to Employee Central Payroll or to SAP ERP HCM, even if they meet the filter criteria for this configuration object.

From a technical perspective, no Data Replication Proxy gets created for employees who have the contingent worker Employment Information record and the filter is applied to the Data Replication Configuration.

Employee Central Payroll customers who have implemented Point-to-Point replication should use this configuration setting because no employee master data is replicated for contingent workers with this type of replication.

From the Q2 2019 release, a feature has been introduced...

Previously, with the "Import Jobs and Positions from Employee Central" report only new jobs and positions master data were replicated to Employee Central Payroll. With the Q2 2019 release, the report is enhanced by Org. Units. You can now import all jobs, positions and org. unit master data from Employee Central to Employee Central Payroll into Infotype 0001 (Organizational Assignment).

The organizational objects like position, job and organizational unit are needed for e.g. reporting in Employee Central Payroll.

You are an Employee Central Payroll customer and Employee Central Payroll is switched on in provisioning.

You use Point-to-Point integration.

You have applied EA-HRRXX Support Package 67 to your Employee Central Payroll system.

With the Q2 2019 release new checks have been added to the Check Tool in Employee Central Admin Center.

In the Payroll Information Application new checks are available for checking payroll system configurations and validations checks.

In the Data Replication Application new checks are available for checking status of Data Replication Proxies.

These new checks help you to ensure that the configuration between Employee Central and Employee Central Payroll is consistent.

You are an Employee Central Payroll customer and Employee Central Payroll is switched on in provisioning.

Previously, the logic to map cost center keys from Employee Central to Employee Central Payroll was based on the length of the cost center key in Employee Central. However, this logic only worked for cost center keys with a fixed length. As of Q2 2019, you can enable an enhanced mapping mode that automatically detects and map cost center keys regardless of the length.

Simplification of the implementation of the cost center integration.

You are an Employee Central Payroll customer and Employee Central Payroll is switched on in provisioning

You use Point-to-Point integration

You have applied EA-HRRXX Support Package 67 to your Employee Central Payroll system

With this feature, you can use the Assignment ID External from Employee Information in Employee Central to create a unique personnel number (PERNR) for replication purposes. Please note: Employments in Employee Central need to represent a Personnel Number in Employee Central Payroll.

Since Employee Central is the system of records for all employee relevant data, using Assignment ID External to create personnel numbers ensures that you work with a unique identifier - one single PERNR - throughout all integrated systems.

You are an Employee Central Payroll customer and Employee Central Payroll is switched on in provisioning.

You use Point-to-Point integration.

You have applied EA-HRRXX Support Package 73 to your Employee Central Payroll system.

This new functionality shall only be used by customers that fulfill the following criteria:

The customer has not yet replicated employee master data into the ECP system out of their productive environment.

The customer uses the Assignment Id External from the first day in their productive environment.

Migration processes of old employee master data without Assignment Id External are not in scope.

The customer has not yet used the Assignment Id External for other purposes then the usage as personnel number.

The behavior is switch-able.

The format of the Assignment ID must be identical to the one of the personnel number: It must be numeric and have eight characters. Note that the settings of the sequence are made in Employee Central.

Administrators can define target population criteria to restrict access to Complete Payroll Tasks tile based on user group. So the Administrator can see payroll tasks only for a specific group of employees (by legal entity). To control the access, go to Admin Center → Manage Permission Roles.

As there are many different events now supported in the ‘Complete Payroll Task’ you may want to restrict who can work on the list/tasks.

You are an Employee Central Payroll customer and Employee Central Payroll is switched on in provisioning.

You use Point-to-Point integration.

The Tile ‘complete payroll task’ shall support customers to get the mashups maintained in a process.

Currently the access to the Tile 'Complete Payroll Task' depends only on the ‘Payroll data Maintenance Task’ Permission:

But in the mean time we have many different events, many people who are working on the list/tasks. Therefore it is needed to have the possibility to define a Specific Target Population.

Target groups can only be defined based on legal entities. There are plans to enhance this further.

Context

Use the Restrict Access to the complete payroll tasks tile to Specific Target Population permission to grant access restricted to specific target groups. This permission is not enabled by default. This means, by default all admins who have the access to Complete Payroll Tasks permission granted have unrestricted access to all records. If you don't want to restrict this access to specific target groups, no additional actions are required. You can just leave the Restrict Access to Payroll Data Maintenance Task to Specific Target Population permission disabled and don't need to make any complementary settings for generic objects or role-based permissions.

As of Q4 2019, you can activate switch WKWDY to enable errors to be raised if you leave working days per week empty in Employee Central and no Planned Working Time (0007) infotype is created during the replication. If you do not activate switch WKWDY, errors are not raised.

Customers want to avoid that a missing IT0007 Planned Working Time is only detected in the payroll run. An error should already been raised during the replication of the Employee Master Data. Therefore we added a new switch to enable messages to be raised for the empty Working Days per Week replication scenario.

You are an Employee Central Payroll customer and Employee Central Payroll is switched on in provisioning

You use Point-to-Point integration

EA-HRRXX Support Package 73 is applied to Employee Central Payroll system

Prior to this enhancement, if the field Working Days Per Week was empty, then infotype 0007 was not created. Some customers complained that the status of the employee master data replication was successful. Only during the payroll run the customer recognized that infotype 0007 wasn’t created. To change this behavior, by raising an error message the customer must implement either the Employee or the Employment BAdI (ABAP Knowledge required).

Background: In the initial ECP years, it was considered to be likely that there are scenarios/employees where the information in Employee Central is not sufficient to create IT0007 correctly. This would have been employees with complicated/variable work schedules. For those, IT0007 was supposed to be maintained in ECP directly, hence replication had to be prevented. The field working days per week was chosen to identify these cases.

For casual workers without a fixed work schedule, it is not possible to maintain meaningful values for the field "working days per week" in EC. Therefore, customers wish to leave it empty or enter '0', but this leads to a failed replication of infotype 0007. The goal of this topic is to successfully replicate infotype 0007 with zero working days per week for casual workers with a solution where the customer doesn't need to implement a BADI.

Currently, if working days per week is 0, IT0007 will not be replicated. There is a t77s0 switch which decides if a warning message or error message should be raised in this case. In this design, a further switch value will be added to the existing switch which indicates that the IT0007 should be replicated even if the working days per week is 0. The new switch value will be '2' because of unity with the values of other t77s0 switches. To be compatible, the value 'X' should still be possible and it still means raising an error message. The next table shows details of the t77s0 switch:

Customers define a work schedule rule on EC side and want to replicate planned working time to IT2003 in ECP based on the defined work schedule rule, instead of having to maintain the corresponding work schedule rule on ECP side. Currently, customers use a dummy work schedule rule (dummy24x7) which has average hours and working days 0. After the update of IT0007 is executed, customers implement the BAdI HRPAD00INFTYBL to overwrite the calculated hours from the infotype framework. The requirement for this scenario is to enable that the entered value of hours and days in EC should be saved in IT0007 and no BAdI implementation should be necessary.

As of Q4 2019, a new tool is available to search and display the replication status of employees replicated from Employee Central to Employee Central Payroll. You can run the tool using transaction HRSFEC_REPL_STATUS. This helps you especially during the implementation of Employee Central Payroll.

It generates a list of replication status according to your selection criteria. You can export this list as a spreadsheet. From this list, you can directly navigate to the Application Log (transaction SLG1) to identify errors that occur during the replication of employee master data and to the Web Service Utilities (transaction SRTUTIL). In the detailed view of service messages, you can simulate, download and display the results as a table.

You are an Employee Central Payroll customer and Employee Central Payroll is switched on in provisioning

You use Point-to-Point integration

EA-HRRXX Support Package 73 is applied to Employee Central Payroll system

If you've enabled the reporting of new hires as no-shows in SAP SuccessFactors Employee Central, this information is now transferred to your Employee Central Payroll system.

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 reason is 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 processing accordingly.

With the new feature, you can implement the business case and no longer need a workaround.

The latest Synchronization Support Package EA-HR must be installed in your Employee Central Payroll system.

Replication of No-Shows from Employee Central | SAP Help Portal

You can now replicate planned working time and temporary time information from Employee Central Time Management to the Substitutions (2003) infotype.

Because of the replication of planned working time, payroll processes that depend on planned working times can be included in the payroll driver execution.

We built this integration scenario to reduce configuration efforts and stop double maintenance of work schedules in both systems. In this way, data consistency is guaranteed and risks of erroneous payroll calculations due to inaccurate time management data are mitigated.

The latest Synchronization Support Package EA-HR must be installed in your Employee Central Payroll system.

https://help.sap.com/docs/SAP_SUCCESSFACTORS_EMPLOYEE_CENTRAL_PAYROLL/6267c9dbd7114f0da47b39c1b4cf0367/045b072df0894f6cb5955f94dde1243d.html

We enabled the replication of Imputed Income and Employeer Contribution for the benefits type Insurance.

Imputed income and employer contribution are taken into account in the payroll process.

Please note that imputed income is only relevant for the United States.

The latest Synchronization Support Package EA-HR must be installed in your Employee Central Payroll system.

The point-to-point integration between Employee Central and Employee Central Payroll enables now an automatic handling of the secondary infotype record creation.

This enhancement has been developed to resolve the following problems:

• If you have mapped Employee Central data to both the primary and secondary infotypes, the Employee Central Payroll point-to-point integration works as expected.
• However, if you couldn’t map Employee Central data to a secondary infotype, it might generate replication errors.

Synchronization Support Package EA-HR SP93 must be installed in your Employee Central Payroll system.

In the current version, the point-to-point replication framework enables the creation of empty secondary infotype records when there’s no corresponding mapping between Employee Central and Employee Central Payroll. The applicable cases are identified in an automatic and generic way.

This rule function returns the next possible date for which payroll-specific date changes are allowed for an employee assigned to a pay group.

We developed this feature to prevent:

• Employees from entering past dated bank account changes
• Administrator and business users from entering past dated payroll-specific data.

Synchronization Support Package EA-HR SP93 must be installed in your Employee Central Payroll system.

You can now activate certain new features delivered for the replication of master data starting from your chosen effective date.

We developed this feature to resolve the following problems:

• When a new feature is introduced for a field in the point-to-point integration, it can impact previously replicated data and cause retroactive errors.
• It wasn't possible to control when and for which data the new feature became active.

Synchronization Support Package EA-HR SP93 must be installed in your Employee Central Payroll system.

In the current version, you can define a start date for, the MASSN/MASSG Change on Hire Date Using Time Dependent scenario:

You can now define additional key figures in Pay Statement (direct). These key figures are displayed along with basic key figures (gross, payout amount) in the Payroll Information section of Employee Files for employee's latest pay date.

When you choose the payment amount or the Pay Statement link, the overview of pay statements is displayed.

We introduced custom key figures for Pay Statement (direct) to enable customers to create key figures according to their company and employee needs.

At least, Synchronization Support Package EA-HR SP86 must be installed in your Employee Central Payroll system and Pay Statement (direct) integration must be configured.

As an employee, you have the Employee Files ﹥ Payroll Information permission to view the Payroll Information section in Employee Profile. In addition, you have the Payroll Permission ﹥ Payroll Self Service that allows you to view your pay statement.

Please note that access to pay statements is controlled by corresponding Employee Central Payroll roles.

You can now replicate custom fields of the Employee Time object to fields of infotype 2001.

When employees request time off, they have to fill out a number of standard fields. If these standard fields don't cover the unique requirements at your company, you can create custom fields. These custom fields can be mapped to fields of infotype 2001 and replicated in the standard Employee Central Payroll using point-to-point integration.

We developed this feature to make the replication more robust in terms of flexibility and localization.

Synchronization Support Package EA-HR SP93 must be installed in your Employee Central Payroll system

Automatic Deletion of Infotype Substitutions (2003) When Moving the Hire Date to the Future

We now provide an automatic deletion of infotype 2003 when customers move the hire date to the future within the Planned working time replication scenario.

This feature corrects errors that occurred in the payroll when the employee’s hire date was moved to a later date in the planned working time replication scenario to infotype Substitutions (2003).

Synchronization Support Package EA-HR SP93 must be installed in your Employee Central Payroll system.

You can now configure country/region-specific code value mapping for a No-Shows event in order to replicate it to a country/region-specific inactive hiring action in the Employee Central Payroll system.

We built this enhancement to meet the needs of customers who want to replicate country/region-specific No-Shows (NS) events to inactive hiring actions in the Employee Central Payroll system.

Synchronization Support Package EA-HR SP99 must be installed in your Employee Central Payroll system.

Here are the required settings to make to enable the replication of a country/region-specific No-show event to an inactive hire action:

1. Set up an inactive hire action in table T529A.
2. Specify the properties for the code value mapping, especially the ISO Code in table T77SFEC_CVPROPC.
3. Map the Italian NSEvent to the ERP Code value HI.

You can now use basic extensibility to replicate into Internal Order and WBS Element fields of Cost Distribution (0027) infotype.

We built this feature to overcome the limitation that custom fields configured on Public Sector Employee Cost Assignment block weren’t replicated to Employee Central Payroll.

Synchronization Support Package EA-HR SP99 must be installed in your Employee Central Payroll system.

We have created a new integration framework to replicate data captured in the Onboarding Compliance forms into the Employee Central Payroll infotypes. The United Kingdom Starter Checklist form on SAP SuccessFactors Onboarding is now integrated with Employee Central Payroll infotypes Tax Data (0065) and Court Orders (0070).

A new standard integration framework is delivered in the Employee Central Payroll system. It enables the mapping of Onboarding Compliance form fields to infotype fields and provides a replication service that can be scheduled to bring Compliance data of active employees automatically into Employee Central Payroll infotypes.

We built this feature to resolve the following problems:

• As part of the Onboarding process, the collection of Compliance data is often mandatory, including some payroll relevant data. However, it doesn’t get updated to Employee Central Payroll master data automatically.
• As a result of this gap, manual activities are required, and the same data is entered twice, once in the Onboarding Compliance forms and once in the Employee Central Payroll mashups.

Synchronization Support Package EA-HR SP93 must be installed in your Employee Central Payroll system.

New Hires in the United Kingdom have to submit the Starter Checklist form. They provide data in the SAP SuccessFactors Onboarding Starter Checklist form. This data is automatically replicated to the Tax Data GB (0065) and Court Orders GB (0070) infotypes once they’ve become a new employee in the Employee Central System.

Link to demo: https://sapvideoa35699dc5.hana.ondemand.com/?entry_id=1_6wrqf72y

We have introduced an improvement in how Data Replication Proxies are generated in response to changes in Time Account data.

Like in previous releases, Time Account changes still generate Data Replication Proxies, but now a Time Account change only raises an event.

The event is processed asynchronously by an event subscriber that then generates a proxy.

We built this enhancement based on the concept that is already used productively for Planned Working Time replication.

Synchronization Support Package EA-HR SP99 must be installed in your Employee Central Payroll system.

You have the Admin Alerts Object Permissions → Time Account Replication Admin Alert permission.

In Payroll Unified Configuration, payroll administrators can configure tasks of time type Absence for Payroll Tasks.

With this feature, payroll administrators receive tasks based on time type as Absence in Complete Payroll Tasks. Payroll administrators can also filter employees using time type of classification Absence.

Synchronization Support Package EA-HR SP99 must be installed in your Employee Central Payroll system.

In Spain when an employee takes sick leave, illness related data is required by the government. So, Absences (Infotype 2001) and (FDI Message Data (Infotype 0768) or Delt@ (Infotype 0968), depending on Absences (Infotype 2001) subtype) should be maintained. A task is created in Complete Payroll Tasks as soon as the absence data is replicated.

Need link for this demo from the SME.

The Trigger Data Replication Proxy Deletion Job allows you to delete proxies that are no longer needed in Employee Central Payroll.

This feature offers an easier and more efficient way to delete the obsolete proxies as part of system maintenance. Where previously you achieved this result using the Import Data function, that was rather cumbersome, now you have a designated feature.

Synchronization Support Package EA-HR SP99 must be installed in your Employee Central Payroll System.

We now provide an automatic logic to avoid unnecessary replication attempts when the Employee Central Payroll systems are non-productive systems. After 150 failed attempts at replication, the next attempt is set to 1000 years into the future, that is, no further attempt is done.

We built this enhancement to help customers, especially hyperscalers, to avoid unnecessary loads when triggering replication to Employee Central Payroll non-productive systems for which the replication failed 150 attempts.

Configuration Requirements

Synchronization Support Package EA-HR SP99 must be installed in your Employee Central Payroll system.

You can now configure single sign-on as well as multifactor authentication for Employee Central Payroll users. You do this by using the SAP Secure Login Client through the SAP GUI.

This new feature provides your users greater security when accessing the Employee Central Payroll system.

Setting up the SAP Secure Login Client to access Employee Central Payroll will involve:

• Requesting a New SAP PKI Certificate Service Tenant
• Configuring SAP PKI Certificate Service in Secure Login Client
• Updating Secure Network Connection (SNC) Name for the Users

Push replication to Employee Central Payroll for events like Hire, Rehire or Terminate was already supported in previous releases. We've enhanced the push replication framework so that the user who executes the Web Service is not required to have the same authorizations as the technical user who sets up the point-to-point replication.

We built this feature to resolve the following problems:

With the necessary setup, it was possible to immediately trigger a push replication to Employee Central Payroll for Service Event Bus events (SEB events) like Hire, Rehire or Terminate. However, in the previous state, the user who triggered the push Web Service was required to have extensive authorizations to perform the actual replication job.

As a result, this was an authorization issue. This enhancement provides additional configuration (recommended setup) where you can choose to use the replication user for the execution of the point-to-point replication job.

For Employee Central Payroll, Support Package EA-HR SPA6 must be installed in your system.

The connection setup for the point-to-point replication (from Employee Central to Employee Central Payroll) can now be configured to authenticate with X.509 certificates.

The context of this enhancement is as follows:

You can now configure the point-to-point replication to work with SSL certificates (X.509 certificates). To assist with this process, the point-to-point configuration report (transaction HRSFEC_PTP_CONFIG) has been enhanced with a new option. The certificates are pushed automatically into the Employee Central Payroll system and can be imported manually into Employee Central.

Support Package EA-HR SPA6 must be installed in your system.

As of June 1, 2022, the operations team will automatically push the necessary Employee Central Payroll infrastructure for certificate handling.

You can now use the My Forms (Fiori 2.0) app in Employee Central Payroll, if country/region-specific forms are delivered.

With the My Forms (Fiori 2.0) app, you can display different HR-related form types relevant for you and your country/region of employment.

We provide this feature to ease employees the access to a specific form in PDF format. Employees can also download and print a selected PDF form.

In order to implement the My Forms (Fiori 2.0), your system landscape has to be enabled for SAP Fiori and meet the required product version stack:

Required Back-End Product (Product Version Stack): SAP Fiori 2.0 for SAP ERP HCM (12 (12/2020))

Front-End Components Delivered with (Product Version Stack): SAP Fiori 2.0 for SAP ERP HCM ( 12 (12/2020))

In the Employee Central Payroll system, it is possible to check the status of the executed employee replication from Employee Central using the transaction HRSFEC_REPL_STATUS (report RP_HRSFEC_REPLICATION_STATUS).

We've added the following features:

• The report now displays the differences in the XML files between Employee Central data used in the current replication and Employee Central data used in the last successful replication.
• The report also displays the history of the Employee Central data nodes in the format of master data nodes when there are changes to time slices.

These enhancements enable better troubleshooting when employee master data replication issues occur. Customers can now clearly see which data changes might have caused replication errors.

Synchronization Support Package EA-HR SPB2 must be installed in your Employee Central Payroll system.

Please note that, while the Employee Central side of this feature is available, you can't use the feature as a whole until the support package mentioned is released. Note also that the full documentation won't be available until then either.

Identity Authentication Services (IAS) for Employee Central payroll systems is now simplified and automated by using the SuccessFactors Upgrade Center.

SAP Cloud Identity Services - Identity Authentication is a public cloud service for secure authentication and single sign-on for SAP cloud and on-premise applications. It can act as an identity provider or be used as a proxy to integrate with the existing single sign-on infrastructure of a customer.

Previously, customers had to follow a number of procedures and manual steps to enable Identity Authentication services for Employee Central Payroll. We've built this feature to simplify the steps where customer can upgrade directly wihtin the Upgrade Center.

• Employee Central Payroll is enabled from Provisioning.
• SAP System Configuration is configured with payroll system and client.
• Payroll System Configuration is configured with the SAP System configuration set.
• SuccessFactors is already integrated with Identity Authentication Services.

You can now retrieve the complete pay calendar information details like the pay period begin date, check date, end date, and pay group information.

We built this feature to improve usability. The customer can now retrieve multiple dates from the pay calendar.

• Employee Central Payroll is enabled from provisioning.
• The Pay Calendar MDF object is enabled.
• Pay period details are maintained in the Pay Calendar MDF object.

Push replication to Employee Central Payroll was supported in previous releases for events like Hire, Rehire, or Terminate using basic authentication. In Employee Central, the prerequisite setup was done using the Event Notification Subscription tool. Starting from 2H 2022, you manage these events using the new Event Subscription Management tool that supports basic or X.509 certificate-based authentication.

With this feature, the security of this connection is improved by enabling the usage of X.509 certificates.

The setting for this feature is to enable the new Event Subscription Management tool in Employee Central.

This feature creates more continuous data records and prevents splits in master data records from being generated when the full transmission start date (FTSD) is moved into the future

The point-to-point Employee master data replication from Employee Central to Employee Central Payroll uses a key-date called the full transmission start date (FTSD) that is defined at the beginning of the project implementation. All master data records with an end date before the FTSD are filtered out by the replication framework. After the go-live, it is recommended that you move the FTSD into the future from time to time to reduce data volume and improve performance.

We're closing a gap by preventing that sometimes unneeded splits of infotype time slices are created when the full transmission start date (FTSD) is moved into the future.

The application log now contains data about push replication.

Push replication happens immediately and is useful for job events like hire, rehire, and termination. It is now possible to analyze technical errors, for example, missing authorizations that occur during push replication runs using the Application Log (transaction SLG1) in the Employee Central Payroll system.

In the current version, data about the push replication is available in the Application log (SLG1). In addition, the log shows errors for the relevant users provided by the push replication framework: the user who executes the Web Service or the technical user who sets up the point-to-point replication.

We've introduced a new mapping logic to support the replication of two new SAP SuccessFactors Employee Central Time Management objects to the Substitution (2003) infotype, namely Holiday Category and Holiday Work Pattern. Previously, the mapping logic consisted in mapping the SAP SuccessFactors Employee Central Time Management public holiday classes FULL, HALF, and NONE to the Employee Central Payroll public holiday classes.

• 1 Full Public Holiday
• 2 Half Public Holiday
• 0 No Public Holiday
• Employee Central entity HolidayCategory introduced and mapped to Payroll entity Holiday Class.
• Employee Central entitesHolidayCategory and HolidayWorkPattern mapped to Payroll entity Day Type. For that purpose we introduced a general mapping table for two dependent Employee Central types to one Payroll type.
• Entire range of holiday classes and day types are allowed (including custom defined).
• Work Schedule Day Model Variants also introduced in EC; the planned working times of the variants are replicated to Payroll when applicable.
• Compatibility considerations when configuring the mapping: KBA3315379

We’ve added the Legal Entity List field to the Payroll System Configuration (PSC) MDF object to allow the connection of one Employee Central system to several SAP Payroll solutions.

With this new enhancement, we can now configure multiple PSCs for a single country/region and connect each PSC of that country/region to a different SAP Payroll solution based on the legal entity. Depending on the created configuration, the employee data belonging to different Legal Entities are replicated into the corresponding Payroll Systems. This leads to the following consequences:

• The Payroll Information portlet in the employee profile page always displays the UI mashups based on the legal entity specified in the PSC.
• The Complete Payroll Tasks page is enhanced to display the combined set of tasks for all legal entities within the country/region.
• The Payroll System Information page is enhanced to display the support package of the respective Employee Payroll system which is relevant for the legal entity.

Allow global customers to choose per legal entity within one country/region the most suitable SAP Payroll solution. For example, in legal entity A you run Employee Central Payroll and in legal entity B you decided to use the partner managed cloud offering for Employee Central Payroll. Both legal entites can be assigned to the same country/region.

The SAP System Configuration object allows you to open mashups in a new tab on the employee's profile page. This ensures compatibility with browser providers discontinuing support for third-party cookies.

We've created a new dropdown field in the SAP System Configuration object called Open Infotypes and Payroll Control Center in a new tab. Selecting Yes in this field would allow you to open mashups in a new tab in the employee profile page. After this field is activated, when the employees choose the required mashups from the employee profile page, they will open in a new tab.

Certain browser providers are discontinuing support for third-party cookies on their browsers due to concerns about user data tracking and privacy implications. They are doing this to comply with different laws created to avoid the tracking of browsing behavior by advertising companies. This change may result in the disruption of mashups being displayed.

A new scenario is now available in Cloud Integration Automation Service for SAP SuccessFactors Employee Central Payroll: "Configuring Pay Statement (direct) Integration". The guided workflow contains instructions for manual and automated tasks to enable a easy and quick integration configuration setup for pay statement (direct) integration including the required oAuth configuration.

We developed this feature to make it easier for customers to enable or migrate to the recommended pay statement (direct) integration for SAP SuccessFactors Employee Central Payroll.

• You have a SAP SuccessFactors Employee Central Payroll license.
• Your BTP subaccount is subscribed to the Cloud Integration Automation Service in the Cloud Foundry environment.

Your user has been assigned the Integration Monitor, Integration Expert, and Integration Administrator CIAS roles.

We added the Download Public Key field in the point-to-point configuration report that makes it possible to download the public key of X.509 certificates. You can then upload X.509 certificates in the Employee Central Security Center to enable certificate-based authentication.

Previously, the public key of the certificate needed to be downloaded using transaction STRUST. The process that could generate errors is now seamless and simple.

For Employee Central Payroll, Synchronization Support Package SPD2 must be installed in your system.

SAP SuccessFactors Employee Central Payroll is now integrated with Joule, allowing employees to easily access their pay statement data such as a pay statement summary including the pay date, payout amount, and gross amount. They can also directly access the pay statement as a PDF and any payment history from active employment. Using natural language, users can ask Joule to display payment information or pay statements for a certain date, month, or year.

• You've enabled Joule for SAP SuccessFactors.
• You have an SAP SuccessFactors Employee Central Payroll license.
• Pay statement (direct) integration is enabled in your SAP SuccessFactors Employee Central instance.
• Synchronization support package EA-HR SP86 or above is installed in your Employee Central Payroll system.

You have been granted the relevant permissions under User Permissions Payroll Permissions Payroll Self Service.