A few notable items from the H2 2025 SuccessFactors update:
Enhancements to Employee Central Quick Actions
Quick Actions for Change Legal Name and View Legal Name
It is now possible to add the “preferred name” field to the template as needed for either company or country requirements.
Fixed-Term Contract – Enhanced Position Validation during Hire
Employee central will extend its Position Management validations (Position Status, Multiple Incumbents, FTE) to Fixed Term Contract hires on both the hire date and contract end date to ensure position data remains accurate. For companies that rely on many Fixed Term employees this validation is a welcome update.
New Work Order Requires New Employment
A long overdue update to the Contingent Worker module, is the “New Work Order Requires New Employment”. Previously if a contingent workers work order needed to lengthened or shortened, the HR teams would often directly edit the work order to update the SCWK and ECWK rows in Job info.
This often had unintended consequences, including the deletion of either the SCWK or ECWK row, or the incorrect termination date would still remain visible in Employment Data.
When “New Work Order Requires New Employment” is enabled, a new employment record is automatically created in Employee Central whenever you add a new Work Order for a Contingent Worker.
This applies to rehire scenarios, where the previous Work Order is inactive, and to overlapping assignments, where the previous Work Order remains active. By linking each Work Order to a separate employment record, you simplify tracking and prevent data inconsistencies.
Not unsurprising is this feature is automatically enabled for all new customer instances, as editing work orders has many unintended consequences in many EC instances. For customers already using Contingent Workforce functionality in Employee Central, this will remain as an optional upgrade.
This enhancement will also allow the synchronization of Work Order details to Job Information using business rules and apply validation mechanisms to prevent errors during Work Order updates.
Enhancements to the Run Details for HRIS Sync Jobs
The HRIS sync job has always been a somewhat opaque multi step process, with multiple KBAs in SAP Support explaining parts of the entire process. In an attempt to better share HRIS Sync jobs details in the Scheduled Job Manager admin tool, you can now view details, which will expand on the following details:
- You can now view the number of users whose user info elements (userinfo-element), standard elements in the SM_USER_INFO table, standard elements in the USERS_SYSINFO or USERS_INFO tables, and user record elements (user-info-record-key) are changed. Previously, it only showed the total number of users whose data has been synced.
- A new “Sync Details” report provides deeper insights for each user. The report includes: person ID, user ID, display name, sync reason, sync result, field name, field data source, previous field value, updated field value, and any associated messages.
Property customString1 Now Filterable in OData API PerPersonal
customString1 property can now be used as a filter when querying the PerPersonal OData API ,allowing the retrieval of a list of PerPersonal records based on custom criteria.
Property lastDateWorked Now Filterable in OData APIs EmpEmployment and EmpEmploymentTermination
You can now use the lastDateWorked property as a filter when querying the OData APIs EmpEmployment and EmpEmploymentTermination – especially helpful for refining queries to only terminations for downstream applications to revoke access.
New Thresholds for Employee Central Compound Employee API
New thresholds for the Employee Central Compound Employee API have been announced. Over the past few years, SAP has warned that excessive API consumption would be throttled – but even with these updates, the threshold remains high. To help monitor over usage, SAP rolled out the new Response Thresholds Admin Alert allowing you to monitor API calls that exceed 80% of the new limits.
Recently, Ive worked on improving, an Employee Central API query, which individually queried SF by personID external, hourly. In 30 days, with 5,000 employees and an hourly query, this would result in 3,600,000 queries in a month. Tailoring the query, and using pagination of 1,000 employees per call, the number of monthly queries can be reduced by 99% to 5,600 with very little effort. Even the unimproved query wouldn’t hit the new thresholds!
Ive found the SAP KBA “SFAPI Best Practices” specifically addresses this and provides some other tips.
The new API thresholds are as follows:
- The maximum size for a SOAP request is 5 MB. The maximum size for a SOAP response is 300 MB.
- For each API call, the Employee Central Compound Employee API limits the number of records that can be returned to:
- 50,000 records for each MDF segment
- 300,000 records for each HRIS entity
- 400,000 total records
- 300 MB response size
New Report to Automate OAuth Configuration
A new report was created to ease and automate OAuth configuration, simplifying the setup process by reading the certificates and importing them to the relevant transactions in SAP SuccessFactors Employee Central Payroll, reducing manual steps.
The report, RP_HRSFEC_PAY_OAUTH_CONFIG is used to automate the OAuth 2.0 connection between SAP SuccessFactors Employee Central and SAP SuccessFactors Employee Central Payroll. The report creates SAML identity providers, OAuth 2.0 clients, and certificate mappings, and then uploads the required certificates to the trust manager, increasing efficiency and minimize OAuth configuration issues.
This is in conjunction with the depreciation of using basic authentication in Employee Central Payroll.
Deprecation of Employee Central SFAPIs Except CompoundEmployee API
After long last – the SOAP-based SFAPIs for Employee Central, with the exception of the stalwart Compound Employee API, will be deleted on November 20, 2026 in preference for ODATA APIs