Listing Enhancements and Features for SAP ERP-SAP SuccessFactors Full Cloud Core Hybrid Integration in the 2H 2024 Release

Objective

After completing this lesson, you will be able to describe new enhancements and features released in 2H 2024

New From Date-To Date Where Clause Condition for Employee Central Compound Employee API

We introduced the fromDate-toDateWHERE clause condition to the Compound Employee API in the standard query mode. We added this condition to increase the ease of selecting employees who have changes that become effective in the given time period in the standard query mode.

What's Changed

How It Looks Now

The fromDate-toDateWHERE clause condition is now available in the standard query mode.

Sample Code

Code Snippet

1
FROM CompoundEmployee  WHERE fromDate = to_date(FromDate,'YYYY-MM-DD') AND toDate = to_date(ToDate,'YYYY-MM-DD')

Technical Details

Reference Number	ECT-222613
Product	Employee Central
Module	Integration and Extension
Feature	API
Action	Info only
Enablement	Automatically on
Lifecycle	General Availability
Type	New
Major or Minor	Major
Software Version	2H 2024
Valid as Of	2024-11-13

New Social Accounts Segment in Compound Employee API

We introduced the social_accounts_information segment to the Employee Central Compound Employee API.

The social accounts segment is person-specific.

We introduced this segment to support the extraction of IM_Info HRIS entity data through the Compound Employee API.

Whats Changed

How It Looks Now

Until this current release, there was no segment available to support the extraction of IM_Info HRIS entity data through the Compound Employee API.

Code Snippet

123456789101112131415161718
<queryResponse>
         <result>
            <sfobject>
               <id>123</id>
               <type>CompoundEmployee</type>
               <person>
                 ...
                  <social_accounts_information>
                     <created_by>admin</created_by>
                     <created_on_timestamp>2024-05-10T21:31:10.000Z</created_on_timestamp>
                     <domain>instant_messenger</domain>
                     <im_id>messengerUserId</im_id>
                     <last_modified_by>admin</last_modified_by>
                     <last_modified_on>2024-06-20T14:45:57.000Z</last_modified_on>
                     <url>www.example_instant_messenger.com</url>
                  </social_accounts_information>
               ...
               </person>

Technical Details

Reference Number	ECT-233969
Product	Employee Central
Module	Integration and Extension
Feature	API
Action	Info only
Enablement	Automatically on
Lifecycle	General Availability
Type	New
Major or Minor	Major
Software Version	2H 2024
Valid as Of	2024-11-15

Filtering Out Terminated Employments from Employee Data Replication

Replication of employee data from Employee Central now uses the EMPLOYMENT_END_DATE filter in the WHERE clause of the Compound Employee API to prevent terminated employments from being replicated to SAP S/4HANA or SAP ERP HCM.

The employment end date is set to be on the full transmission start date (FTSD) that you've defined for employee data replication from Employee Central. This means, only employments that have been active for at least one day on or after the FTSD get replicated to SAP S/4HANA or SAP ERP HCM by default. If you want to replicate employments that were terminated before the FTSD, you have the option to turn off the EMPLOYMENT_END_DATE filter. But we recommend you only do this in special cases. For example, when problems occur in your SAP S/4HANA or SAP ERP HCM system because the system also needs employments that were terminated before the FTSD.

By introducing the filter, the payload transferred from Employee Central is reduced, which improves the performance of the replication.

Configuration Requirements

If you use the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on, support package 04 of this add-on must be installed in your SAP S/4HANA system.

If you use the SFSF EC INTEGRATION (PA_SE_IN) add-on, support package 38 of this add-on must be installed in your SAP S/4HANA or SAP ERP HCM system.

Whats Changed

How It Looks Now

In the current version, the incoming payload from Employee Central contains only one employment_information segment by default: The employment_information of the employment that has been active since the FTSD or that was active for at least one day on or after the FTSD.

The following example shows the default behavior in the current version. In this example, the payload contains one employment for the employee, which begins on January 1, 2015. The FTSD is January 1, 2014.

Sample Code:

Code Snippet

1234567891011
<queryCompoundEmployeeResponse>
	<CompoundEmployee>
		<id>278718</id>
			<person>
				...
				<employment_information>
					<start_date>2015-01-01</start_date>
				</employment_information>
			</person>
	</CompoundEmployee>
</queryCompoundEmployeeResponse>

If you disable the use of the employment end date filter, the payload contains two employment_information segments: One for the employment that was terminated before the FTSD and one for the employment that has been active since the FTSD or that was active for at least one day on or after the FTSD.

The following example shows the behavior if you disable the EMPLOYMENT_END_DATE filter in the current version. In this example, the payload contains two employments for the employee. The first was terminated on August 31, 2013. The second employment starts on January 1, 2015. The FTSD is the same in this example: January 1, 2014.

Sample Code:

Code Snippet

12345678910111213141516
<queryCompoundEmployeeResponse>
	<CompoundEmployee>
		<id>278718</id>
			<person>
				...
				<employment_information>
					<end_date>2013-08-31</end_date>
					<start_date>2012-01-01</start_date>
				</employment_information>
				<employment_information>
					<start_date>2015-01-01</start_date>
				</employment_information>
				...
			</person>
	</CompoundEmployee>
</queryCompoundEmployeeResponse>

Technical Details

Reference Number	ECT-230342
Product	Employee Central
Module	Integration and Extension
Feature	ERP Integration
Action	Info only
Enablement	Customer configured
Lifecycle	General Availability
Type	New
Major or Minor	Major
Software Version	2H 2024
Valid as Of	2024-11-15

Purge Status Overview for Data Purge Is Now Default Option in PA_SE_IN Add-On

We now use the purge status overview information provided by the Compound Employee API as the default option when the SAP S/4HANA or SAP ERP HCM system queries employee data that has been purged in Employee Central.

If you need to use the validation against the effective end date filter provided by the Compound Employee API instead of the purge status overview, you can set a parameter in the SAP S/4HANA or SAP ERP HCM system to disable the use of the purge status overview.

Using the DRTMPurgeStatusOverview segment of the Compound Employee API enables the SAP S/4HANA or SAP ERP HCM system to validate detailed purge dates and react accordingly. You don't need to adjust the full transmission start date (FTSD) defined for the replication of employee master data to prevent errors.

Configuration Requirements

Support package 38 of the SFSF EC INTEGRATION (PA_SE_IN) add-on must be installed in your SAP S/4HANA or SAP ERP system.

Note

This change doesn't affect the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on. In the ECS4HCM add-on, using the purge status overview is the only option.

Role-Based Permission Prerequisites

If you grant the Compound Employee API user access only to defined segments, you must add the permission for the DRTMPurgeStatusOverview segment.

Whats Changed

How It Looks Now

In the current version, purge status overview is the default option. In the customizing activity Define Parameters for Employee Master Data and Org. Assignment Query, you can set the parameter No Purge Status Overview to opt out of the default option.

In the current version, the SAP S/4HANA or SAP ERP system uses the purge status overview by default. If you need to, you can opt out of it. When defining the parameters for the employee master data and organizational assignment query, you can select the Do Not Use Purge Status Overview checkbox to enable the validation against the effective end date filter provided by the Compound Employee API.

How It Looked Before

In the previous version, validation against the effective end date filter was the default option. In the customizing activity Define Parameters for Employee Master Data and Org. Assignment Query, you could set the parameter Use Purge Status Overview to opt into using the purge status overview instead.

In the previous version, the SAP S/4HANA or SAP ERP system used the validation against the effective end date filter by default. You could decide to use the purge status overview instead. When defining the parameters for the employee master data and organizational assignment query, you could select the Use Purge Status Overview checkbox to enable use of the DRTMPurgeStatusOverview segment of the Compound Employee API.

Technical Details

Reference Number	ECT-237731
Product	Employee Central
Module	Integration and Extension
Feature	ERP Integration
Action	Info only
Enablement	Customer configured
Lifecycle	General Availability
Type	Changed
Major or Minor	Major
Software Version	2H 2024
Valid as Of	2024-11-15

Replication of Newly Hired Employees Who Go on Long-Term Leave on the Hire Date

You can now make settings to reflect the following situation in the SAP S/4HANA system: You hire a new employee in Employee Central, and the employee starts a long-term absence (for example, for medical reasons) on the same day that they're hired.

In the current version, you can configure SAP S/4HANA for replication of newly hired employees who go on long-term leave on the hire date. A long-term leave that starts on the hire date of an employee is replicated from Employee Central and processed in SAP S/4HANA in the same way as a no-show. The configuration is almost the same. The difference is that in the no-show case, the employee is not with the company. In the case of a long-term leave starting on the hire date, the employee is with the company. They have a different employment status and their organizational assignments look different than in the no-show case.

Configuration Requirements

Support package 4 of the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on must be installed in your SAP S/4HANA system.

Technical Details

Reference Number	ECT-231969
Product	Employee Central
Module	Integration and Extension
Feature	ERP Integration
Action	Info only
Enablement	Customer Configured
Lifecycle	General Availability
Type	New
Major or Minor	Minor
Software Version	2H 2024
Valid as Of	2024-11-15

Connecting Multiple Employee Central Instances to Same Client of the SAP S/4HANA System

Recall that as of the 1H 2024 release you can connect multiple Employee Central instances to the same client of your SAP S/4HANA system. For example, if your company has different legal entities that require separate management of employee data and therefore separate instances of SAP SuccessFactors Employee Central, but you want to ensure that common processes, such as payroll that you run in SAP S/4HANA, run consistently for all your employees.

Use this feature if you use separate Employee Central instances and want to continue to run payroll in the same SAP S/4HANA system for all your employees. For each Employee Central instance that you connect, you set up the replication separately.

Core hybrid customers such as service providers who provide payroll in an SAP S/4HANA system and other HR capabilities in Employee Central or conglomerates with different legal entities managed in separate Employee Central instances have asked for this feature. Migration of employee data from one SAP S/4HANA client to different Employee Central instances is also supported

Configuration Requirements

Support package 3 of the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on must be installed in your SAP S/4HANA system.

If you use the external assignment ID in Employee Central, you must configure your business rules so that the external assignment ID is unique across all Employee Central instances.

Whats Changed

Connecting Multiple Employee Central Instances

Mapping of Employee Central Instance ID to Enable Connection of Multiple Employee Central Instances

Job Scheduler for Employee Data Migration Settings

How It Looks

In the current version, you can connect multiple Employee Central instances to the same client of your SAP S/4HANA system. If you enable the corresponding constant in your SAP S/4HANA system, the system ensures that data is replicated to and from a specific Employee Central instance. It adds the Employee Central instance ID to the employee key mapping and employee staging area. Existing programs such as the staging area viewer or the processing program for replication requests are enhanced with the Employee Central instance ID to ensure that the SAP S/4HANA system knows which instance of SAP SuccessFactors Employee Central manages the data of the employee in question. We provide a new program to insert your existing Employee Central instance ID into the employee key mapping to prepare your system for connecting further Employee Central instances.

The Business Integration Builder (BIB) framework is enhanced with additional configurations to let you decide the target Employee Central instance for the legal entities. Based on this configuartion, the migration of employee data to Employee Central is handled such that the employee is sent only to the intended Employee Central instance using the correct transformation template group. Accordingly the delta migration programs are also adjusted to support this behaviour.

We also provide a new integration package with the value mapping SAP SuccessFactors Employee Central Integration with SAP ERP or SAP S/4HANA: System Mapping for this feature in SAP Cloud Integration. You use this value mapping to define which SAP SuccessFactors Employee Central instance is to be addressed by your integration flows, depending on the Employee Central instance ID that the corresponding web service transfers from the SAP S/4HANA system.

Restriction

Note

You cannot use point-to-point replication of time management data from Employee Central in the current version if you enable this feature. You can also replicate or migrate organizational objects from only one Employee Central instance currently. Using multiple Employee Central instance is not supported in Side-by-Side deployment option.

In the previous version, you could connect only one Employee Central instance to a client of your SAP S/4HANA system.

Technical Details

Reference Number	ECT-225231
Product	Employee Central
Module	Integration and Extension
Feature	ERP Integration
Action	Info only
Enablement	Customer Configured
Lifecycle	General Availability
Type	New
Major or Minor	Major
Software Version	1H 2024
Valid as Of	2024-05-17

Connecting Multiple Employee Central Instances to Same Client of SAP S/4HANA Now Includes Organizational Object Replication

You can now also replicate organizational objects from different SAP SuccessFactors Employee Central instances when connecting multiple Employee Central instances to the same client of your SAP S/4HANA system.

In the previous version, we provided this feature for employee data. Now, we're also including organizational objects.

Core hybrid customers have asked for this feature. For example, service providers who provide payroll in an SAP S/4HANA system and other HR capabilities in Employee Central or conglomerates with different legal entities managed in separate Employee Central instances.

Configuration Requirements

Support package 4 of the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on must be installed in your SAP S/4HANA system.

Your SAP S/4HANA system must have the following minimum stack level:

SAP S/4HANA 2022: Support Package Stack 4 or higher
SAP S/4HANA 2023: Feature Package Stack 2 or higher

Also implement the SAP Note 3454026 in your system.

Whats Changed

Enable this feature with the constant ERP to EC/EC to ERP: Connect Multiple EC Instances. When it is enabled, the system adds the Employee Central instance ID, for example, in the replication request viewer and the processing program for replication requests. With a new preparation program, you add your existing Employee Central instance ID in the key mapping table. With a new value mapping in SAP Cloud Integration, you map your Employee Central instance IDs to the address and credentials to be used by the integration flows in the middleware.

How It Looks Now

If you enable this feature with the constant ERP to EC/EC to ERP: Connect Multiple EC Instances, which we already provided in the previous version, the system adds the Employee Central instance ID in tables and existing programs where it's needed to let the SAP S/4HANA system know which instance of SAP SuccessFactors Employee Central manages the data of the given organizational object. We also provide programs and customizing activities that you can use to prepare and configure the organizational object replication for connecting multiple instances.

The value mapping Mapping of Employee Central Instance ID to Enable Connection of Multiple Employee Central Instances in SAP Cloud Integration, which we provided in the previous version, is now also used by the integration flow for replication of organizational objects from Employee Central.

Note

We've renamed the integration package that contains this value mapping to SAP SuccessFactors Employee Central Integration with SAP S/4HANA: System Mapping.

Restriction

You cannot use point-to-point replication of time management data from Employee Central in the current version if you enable this feature.

In the previous version, you could migrate or replicate organizational objects to and from only one SAP SuccessFactors Employee Central instance even if you enabled the connection of multiple SAP SuccessFactors Employee Central instances to your SAP S/4HANA system.

Technical Details

Reference Number	ECT-231966
Product	Employee Central
Module	Integration and Extension
Feature	ERP Integration
Action	Info only
Enablement	Customer Configured
Lifecycle	General Availability
Type	New
Major or Minor	Major
Software Version	2H 2024
Valid as Of	2024-11-15

Enhancements to Tool to Identify Employees for Temporary Exclusion from Inbound Processing in SAP S/4HANA

We've made enhancements to the program called by the Identify to Exclude from Processing (ECPAO_IN_EE_EXCP) transaction, which we provided in the previous release version.

We've made a change to the Identify Employee Records for Temporary Exclusion from Processing (ECPAO_IN_EE_EXCEPTIONS) program. Now, there's a period of time before the program starts to run, during which the program doesn't analyze replication requests for exceptions. Also, entries in the Packages of Employee IDs to Identify Employees w. Exception table that were created by the program more than 30 days ago are now automatically deleted when a new processing run of employee replication requests starts.

We've made this change to simplify the handling of the program and to reduce the required manual activities.

Configuration Requirements

Support package 4 of the SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on must be installed in your SAP S/4HANA system.

Whats Changed

In the Identify Employee Records to Exclude from Processing program, you can choose Change Selection to change the number of minutes before now for which records should not be analyzed. You can choose Delete Analysis Date to remove entries from the Packages of Employee IDs to Identify Employees w. Exception table. But the system also removes records from this table that were created more than 30 days ago.

How It Looks Now

In the current version, we've introduced a time delay for the identification program. When you call the Identify from Processing(ECPAO_IN_EE_EXCP) transaction, the program shows all exceptions that have occurred since the beginning of the previous day by default. Now, the system excludes the last 15 minutes before the start of the identification program from the analysis for exceptions. We exclude the last 15 minutes because the processing of replication requests may run at the same time as the identification program. If the programs run at the same time, entries are temporarily displayed in the list of exceptions and disappear again. As this is confusing, we go back 15 minutes to make sure that exceptions are only shown for replication requests for which processing is completed. You can change the number of minutes.

To optimize the performance of the analysis, the SAP S/4HANA system creates virtual packages of person GUIDs in the Packages of Employee IDs to Identify Employees w. Exception(ECPAO_IN_EXC_PKG) table, which it analyzes together for exceptions. In the current version, the identification program now automatically deletes entries from this table that were created more than 30 days ago when a new processing run of employee replication requests starts.

In the previous version, the identification program analyzed all replication requests that were processed since the beginning of the previous day. If the processing of replication requests was just running, you may have found that entries were temporarily displayed in the list of exceptions and disappeared again.

You also had to regularly delete the entries from the Packages of Employee IDs to Identify Employees w. Exception table yourself so that the table didn't become overloaded over time.

Technical Details

Reference Number	ECT-232179
Product	Employee Central
Module	Integration and Extension
Feature	ERP Integration
Action	Info only
Enablement	Customer Configured
Lifecycle	General Availability
Type	Changed
Major or Minor	Minor
Software Version	2H 2024
Valid as Of	2024-11-15

Deprecation of Create ESS Users for Employees Replicated from Employee Central Report

The report Create ESS Users for Employees Replicated from Employee Central(PAOCF_EC_ESS_USER_UPDATE) has reached end of maintenance on October 1, 2022 and will be deleted on November 15, 2024.

Key Dates

Future dates are subject to change.

Milestone	Date	Definition
End of Development	April 15, 2022	The deprecation milestone after which SAP stops enhancing a product or part of a product. You can continue to use the software, but you should begin planning for a time when it will no longer be available for use. We still fix high-priority bugs.
End of Maintenance	October 14, 2022	The deprecation milestone after which SAP does not fix bugs or deliver patches for the software. SAP continues to answer your how-to questions. We strongly encourage you to adopt an alternative method for your business scenario.
Deleted	November 15, 2024	The deprecation milestone when a feature is no longer available for productive use. You should now be using an alternative method for your business scenario.

Deprecation Details

We have deprecated the report Create ESS users for employees replicated from Employee Central (PAOCF_EC_ESS_USER_UPDATE) because SAP ERP users are handled by SAP ERP user management tools. For use cases where you need to create specific SAP ERP ESS users manually, you can use the transaction Set Up and Maintain ESS Users (HRUSER).

If you are currently still using the report Create ESS users for employees replicated from Employee Central to create SAP ERP ESS users manually, please use the SAP ERP transaction Set Up and Maintain ESS Users instead.

Note

We changed the Deleted date from April 14, 2023 to November 15, 2024 because the report wasn't deleted on April 14, 2023. But it is deprecated, so please do no longer use it. Use transaction Set Up and Maintain ESS Users instead.

Additional Resources

For more information about using transaction Set Up and Maintain ESS Users (HRUSER), refer to Setting Up and Maintaining ESS Users.

Technical Details

Reference Number	ECT-139247
Product	Employee Central
Module	Integration and Extension
Feature	ERP Integration
Action	Recommended
Enablement	Automatically on
Lifecycle	Deprecated
Type	Changed
Major or Minor	Minor
Software Version	2H 2021 1H 2022 2H 2022 1H 2023 2H 2023 1H 2024 2H 2024
Valid as Of	2024-11-15

Go to Course