SuccessFactors Employee Central H2 2022 release provides exciting innovations across SAP SuccessFactors Employee Central H2 2022 that can help you transform your HR operations, increase employee engagement, and deliver results.
Don’t miss out SuccessFactors Employee Central H2 2022 on all the great innovations and enhancements. Here are a few key updates you should consider for SuccessFactors Employee Central
H2 – 2022 Release Schedule
- Preview Release – October 28 , 2022
- Production Release – December 9 , 2022
1. General Updates to Foundation Objects
There are two updates to legacy foundation objects, a new warning message and a user-interface cleanup.
- New warning message. The system warns the user that deleting or deactivating a foundation object leads to inconsistencies in employee data. If an object references that foundation object, the object reference breaks. Please check relationships to other objects and to employee data before deleting or deactivating a foundation object. For more information about deleting foundation objects, refer to the Related Information section.
- UI cleanup. We’re removing all MDF-based foundation objects from the Manage Organization, Pay and Job Structures UI because you can’t manage them here.
We’ve made these enhancements to prevent inconsistencies in employee data and to simplify our UI.
How It Looks Now – Warning Message
In the current version, the system warns the user when they try to deactivate or delete a foundation object. The system displays an enhanced warning message when the user tries to delete a foundation object.
In the current version, the Legal Entity, Pay Group, Department, Business Unit, Job Function, Job Classification, Cost Center, Pay Calendar, Division, and Currency Exchange Rate foundation objects have been removed from the user interface.
In the previous version, the Legal Entity, Pay Group, Department, Business Unit, Job Function, Job Classification, Cost Center, Pay Calendar, Division, and Currency Exchange Rate foundation objects were still on the user interface. However, you couldn’t manage these objects on that user interface. You had to use the Manage Data UI instead.
Technical Details
| Reference Number | ECT-96709 |
| Product | Employee Central |
| Module | Employee Central |
| Feature | Business Configuration |
| Action | Info only |
| Configuration Type | Universal |
| Lifecycle | General Availability |
| Type | Changed |
| Major or Minor | Minor |
| Software Version | 2H 2022 |
| Valid as Of | 2022-12-09 |
2. Tooltip Added for HRIS Elements and Fields
We’ve added a tooltip for standard HRIS elements and fields on the Business Configuration UI.
The tooltip provides meaningful information that helps administrators to use each field in the configuration.
Technical Details
| Reference Number | ECT-185336 |
| Product | Employee Central |
| Module | Employee Central |
| Feature | Business Configuration |
| Action | Info only |
| Configuration Type | Universal |
| Lifecycle | General Availability |
| Type | New |
| Major or Minor | Minor |
| Modular Business Process | Not Applicable |
| Software Version | 2H 2022 |
| Valid as Of | 2022-12-09 |
3. HRIS Actions from the Business Configuration UI is Deleted
Most of the HRIS Actions from Business Configuration UI (BCUI) that are currently not used in configuration of the People Profile will be deleted on December 9, 2022.
Key Dates
Future dates are subject to change.
| Milestone | Date | Definition |
|---|---|---|
| End of Development | May 20, 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 | May 20, 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 | December 9, 2022 | 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
To clean up the BCUI, most of the HRIS Actions from the section that isn’t used in configuration of People Profile are removed from Admin Center >> Manage Business Configuration >> HRIS Actions.
This is a screenshot of the HRIS Actions section in the current version.
Here’s a screenshot of the HRIS Actions section in the previous version.
Technical Details
| Reference Number | ECT-186891 |
| Product | Employee Central |
| Module | Employee Central |
| Feature | Business Configuration |
| Action | Info only |
| Configuration Type | Universal |
| Lifecycle | Deleted |
| Type | Changed |
| Major or Minor | Not Applicable |
| Modular Business Process | Not Applicable |
| Software Version | 2H 2022 |
| Valid as Of | 2022-12-09 |
4. Data Model to Business Configuration UI Sync Enhancements
Previously, when uploading the Succession Data Model and country/region-specfic Succession Data Model from Provisioning, several configuration changes from XML did not sync to Business Configuration UI (BCUI). This caused differences between BCUI and data model. To maintain consistent configurations between XML and BCUI and to achieve harmonized behavior with BCUI, the data model has now been enhanced.
| Modifications in the Data Model | Lead to the Following Synchronization in BCUI |
|---|---|
| Deleting an HRIS field from an HRIS element in the Succession Data Model. Example If you delete job-code from the jobInfo element. Note Deleting HRIS fields from the person type Contingent Worker isn’t synchronized to BCUI. | The HRIS field is also deleted from the corresponding person type configurations associated with the HRIS element. Example job-code is also deleted from jobInfo_onboardee, jobInfo_employee. |
| Deleting an HRIS field from a Localized HRIS Element in country/region-specfic Succession Data Model. Example If you delete job-code from the jobInfo_USA element. Note Deleting HRIS fields from the person type Contingent Worker isn’t synchronized to BCUI. | The corresponding HRIS field is also deleted from the person type configurations associated with the Localized HRIS element. Example job-code is also deleted from jobInfo_USA_onboardee, jobInfo_USA_employee. |
| Deleting an HRIS element in Succession Data Model. Example If you delete the jobInfo element. | The HRIS element and the person type configurations associated with the HRIS element are disabled. Example jobInfo, jobInfo_onboardee, and jobInfo_employee are disabled. |
| Deleting a Localized HRIS Element in country/region-specfic Succession Data Model. Example If you delete the jobInfo_USA element. | The Localized HRIS element and the person type configurations associated with the element are deleted. Example jobInfo_USA, jobInfo_USA_onboardee, and jobInfo_USA_employee are deleted. |
| Modifying the required attribute of an HRIS field in the base element from no to yes in the Succession Data Model and country/region-specfic Succession Data Model. Example If you change the required attribute of job-code to yes in the element jobInfo. Note Modifying the attribute in the Contingent Worker and Dependent person types aren’t synchronized to BCUI. | The Mandatory attribute of the HRIS field is set to Yes in the base element and the associated person type configurations. Example The Mandatory value of job-code is set to Yes in jobInfo, jobInfo_onboardee, and jobInfo_employee. |
| Modifying the enabled attribute of an HRIS field in the base element from yes to no in the Succession Data Model and country/region-specfic Succession Data Model. Example If you change the enabled attribute of job-code to no in the element jobInfo. Note Modifying the attribute in the Contingent Worker person type aren’t synchronized to BCUI. | The Enabled attribute of the HRIS field is set to No in the base element and the corresponding person type configurations. Example The Enabled value of job-code is set to No in jobInfo, jobInfo_onboardee, and jobInfo_employee. |
| Modifying the visibility attribute of an HRIS field in the base element from view to edit, or none to edit in the Succession Data Model and country/region-specfic Succession Data Model. Example If you modify the visibility attribute of job-code to EDIT in the element jobInfo. Note Modifying the attribute in the Contingent Worker and Dependent person types aren’t synchronized to BCUI. | The Visibility attribute of the HRIS field is set to EDIT in all the corresponding person type configurations. Example The Visibility value of job-code is set to EDIT in jobInfo, jobInfo_onboardee, and jobInfo_employee. |
We introduced these improvements to prevent data inconsistencies in BCUI whenever the XML is modified.
Technical Details
| Reference Number | ECT-191813 |
| Product | Employee Central |
| Module | Employee Central |
| Feature | Data Models |
| Action | Info only |
| Configuration Type | Universal |
| Lifecycle | General Availability |
| Type | Changed |
| Major or Minor | Minor |
| Modular Business Process | Not Applicable |
| Software Version | 2H 2022 |
| Valid as Of | 2022-12-09 |
5. New Validation Checks in Business Configuration UI
Business Configuration UI now raises additional warnings when you save changes to HRIS elements in the configuration. These messages provide necessary troubleshooting information and help administrators prevent misconfigurations in the system.
Additionally, a new warning message is introduced when users upload the Succession Data Model from Provisioning. The system warns users when the data model includes deprecated HRIS elements that don’t have any functionality tied to it. Users need to remove these elements manually from the data model.
We’ve introduced new warning messages to convey:
- Automatic changes that occur in the configuration when users::
- Disable HRIS elements and country/region-specific HRIS elements from the configuration.
- Associate an invalid trigger rule to HRIS elements in the configuration.
- Instructions to update the configuration manually when users:
- Use the deprecated Job Information fields in the configuration.
We added these warnings to prevent data inconsistencies in the system.
Technical Details
| Reference Number | ECT-206287 |
| Product | Employee Central |
| Module | Employee Central |
| Feature | Data Models |
| Action | Info only |
| Configuration Type | Universal |
| Lifecycle | General Availability |
| Type | Changed |
| Major or Minor | Minor |
| Modular Business Process | Not Applicable |
| Software Version | 2H 2022 |
| Valid as Of | 2022-12-09 |
6. Hire Date Corrections No Longer Allowed in Job Information History UI
The system no longer allows you to change the hire date of a user in the Job Information History UI. You can however still change a rehire date for a user rehired with their old employment record.
Hire date changes can be done using the Hire Date Correction tool.
Technical Details
| Reference Number | ECT-204070 |
| Product | Employee Central |
| Module | Employee Central |
| Feature | Job Information |
| Action | Info only |
| Configuration Type | Universal |
| Lifecycle | General Availability |
| Type | Changed |
| Major or Minor | Major |
| Modular Business Process | Hire to Retire |
| Software Version | 2H 2022 |
| Valid as Of | 2022-12-09 |
7. Deprecation of Event Reason Derivation Using XML
The legacy method of deriving event reasons for Job Information and Compensation Information using an XML template has reached end of maintenance on May 21, 2021, and will be deleted on December 09, 2022.
Key Dates
| Milestone | Date | Definition |
|---|---|---|
| End of Development | May 21, 2021 | 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 | May 21, 2021 | 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 | December 09, 2022 | 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
Event Reason Derivation using XML has now been deleted. Business rules are now the preferred method for deriving event reasons for Job Information and Compensation Information.
Technical Details
| Reference Number | ECT-161692 |
| Product | Employee Central |
| Module | Employee Central |
| Feature | Mass Changes |
| Action | Info only |
| Configuration Type | Universal |
| Link to Demo | Not Applicable |
| Lifecycle | Deleted |
| Type | Changed |
| Modular Business Process | Not Applicable |
| Software Version | 2H 2022 |
| Valid as Of | 2022-12-09 |
Thanks & Regards,
Anipe Abraham,
Sr. #SAP #SuccessFactors Consultant | Employee Central | Employee Central Payroll | Recruitment Management l Onboarding | PMGM | Sap Hcm | Corporate Trainer.
Note: the purpose of the blogs that i write on my personal website is in order to help the consultants and students who are trying to learn new things .i write it as per my personal interest , hope all my blogs are helpful and its just for learning use .to help you with most up to date content in SAP SuccessFactors . By Anipe Abraham
