Reviewing the What's New Information in the 2H 2023 Release

Objectives

After completing this lesson, you will be able to:

  • Identify key Employee Central 2H 2023 features and enhancements

SAP SuccessFactors Employee Central Core 2H 2023 Stay Certified Information

Employee Central Quick Actions in Microsoft Teams

With the integration of SAP SuccessFactors and Microsoft 365, Manage My Data and Manage My Team are available for users as quick actions for tailored employee self-service (ESS) and manager self-service (MSS) in Microsoft Teams.

You can use Employee Central Quick Actions to tailor template for ESS and MSS transactions. Based on that, users can find the quick actions from the main menu of the SAP SuccessFactors message extension in Teams. Users can perform these specific tasks with the quick actions:

  • Change Chosen Name
  • Change Pronouns
  • Change Legal Name
  • Change Location
  • Change Job
  • Change Working Time
  • Change Contract End Date
  • Change Cost Center
  • Change Probation
  • Transfer
  • Promotion
  • View Cost Center
  • View Location
  • View Job
  • View Legal Name
  • View Marital Status

Whether a task is available to users and whether it's located in Manage My Data or Manage My Team depend on the settings configured in Admin Center.

If you've configured an approval workflow for a task of the "change" type in Admin Center, approvers will receive approval cards in Teams once approval requests are triggered.

Data changes made in Teams are synchronized to users' SAP SuccessFactors system in real time.

We developed this feature to enable users to easily manage their personal and team information in everyday business social scenarios.

Configuration Requirements

  • You've enabled the SAP SuccessFactors app for Microsoft Teams.

  • You have an Employee Central license.
  • The Employee Central Quick Actions feature is enabled.
  • Manage My Data is enabled in Admin Center > Manage Home Page > Quick Actions.
  • Manage My Team is enabled in Admin Center > Manage Home Page > Quick Actions.

Technical Details

Reference NumberWRK-333
ProductEmployee Central
ModuleEmployee Data
Feature
  • Work Tech
  • Job Information
  • Personal Information
ActionInfo only
EnablementCustomer configured
Link to DemoEmployee Central Quick Actions in Microsoft Teams
LifecycleGeneral Availability
TypeNew
Major or MinorMajor
Business Process VariantNot Applicable
Software Version2H 2023
Valid as Of2023-11-17
Latest Document Revision2023-10-13

Related InformationEnabling the SAP SuccessFactors App for Microsoft TeamsUsing Employee and Manager Self-Service in the SAP SuccessFactors AppEmployee Central Quick Actions

Enhanced Execution of HRIS Sync Jobs Triggered by Data Import or API Operations

Previously, an HRIS Sync job triggered by data import or API operations ran immediately. Now, the job waits up to 10 minutes before starting so that all data changes through data import or API operations during the waiting time are synchronized through a single job execution.

To view the status of the job request automatically created for the HRIS Sync job, go to the Admin Center > Scheduled Job Manager > Job Scheduler tab.

This change optimizes resource allocation for job execution and improves overall system stability.

Technical Details

Reference NumberECT-222315
Product
  • Employee Central
  • Compensation
Module
  • Employee Data
  • Compensation
  • Variable Pay
FeatureHRIS Sync
ActionInfo only
EnablementAutomatically on
Link to Demo 
LifecycleGeneral Availability
TypeChanged
Major or MinorMinor
Business Process VariantNot Applicable
Software Version2H 2023
Valid as Of2023-11-17
Latest Document Revision2023-10-13

Related Information

Triggering HRIS Sync

Centralized Services Support Manager Self-Service Changes for Global Assignments

Centralized services now support adding a global assignment from the Manager Self-Service (MSS) Take Action > Add Global > Assignment menu and from the Manage Pending Hires tool. Centralized services now also supports editing, ending, and obsoleting an employee's global assignment using the Manager Self-Service (MSS)Take Action > Manage Global Assignment menu.

Global Assignment using MSS on Centralized services comes with the following benefits:

User Interface Changes

When adding a global assignment, the Start Date, Company, and Event Reason fields are shown in that order at the top of the page by default.

The screenshot here shows how the fields display when Centralized services aren’t enabled.

Message Handling

In cases where there are issues after a user tries to save their changes, warning, and error messages are now grouped by entity and subgrouped by severity and can also be filtered.

Rules

  • When adding, editing, or ending a global assignment, for both Home and Host Assignments, onSave rules for Job Information as source element are supported.
  • When adding a global assignment, onInit and onChange rules for Employee Information, and Employee Information Model as source element are supported.
  • When adding a global assignment, onInit rules on Start Date, Company, and Event Reason fields are no longer supported.
  • onView rules are no longer supported.

Cross-Entity Rules

  • When adding, editing, or ending a global assignment, cross-entity rules with Job Information as source element and Employment Information, Compensation Information, Recurring Pay Components, Non-Recurring Pay Components, or Job Relationships as target element are supported on Home Assignment records.
  • When editing a global assignment, cross-entity rules with Job Information as source element and Job Relationship or Compensation Information as target element are triggered only if a Job Information record exists on the same date or before the Job Relationship or Compensation Information start date when saving a Host Assignment. If not, you receive an error.
  • When adding, editing, or ending a global assignment, cross-entity rules with Job Information or Compensation Information as the source element and Employment Information as the target element for Host Assignment are no longer supported.

Workflow

  • When ending a global assignment, preference is always given to a Global Assignment Information workflow configuration. If no Global Assignment Information workflow configuration is found, then the system checks whether a Job Information workflow configuration exists and uses that configuration to trigger the workflow.
  • When updating an Add Global Assignment workflow, the system doesn’t check if the user has the Edit permission for User PermissionsManage DataGlobal Assignment DetailsGlobal Assignment Add permission. This means that a user is able to update any of the global assignment details even if they don’t have this permission.

Position Management

If Position Management is enabled, when adding a global assignment, you can decide on the allocation of direct reports, meaning that you can decide whether incumbents stay with the current manager or move to the new hire. Here's an example of the allocation of direct reports change.

Position Follow-up Processes

The system now carries out all the relevant position validations when a global assignment is added, edited, ended, or set to obsolete. These validations check the position every time you do any of these actions, and ensure employees can only be assigned to positions that meet the validation criteria. This helps achieve data consistency and avoids overstaffing by enforcing capacity control.

Follow-up processes for Position Management now automatically run in the background when you add, edit, end, or set a global assignment to obsolete for an employee. These follow-up processes are different for each of those actions. For more information, refer to Follow-Up Processes After Saving Global Assignment given in the Related Information section.

When an error occurs during one of the follow-up processes, the system saves all the successfully processed data for that process. For example, if an error occurs during Hierarchy Adaptation, the direct reports that were processed without any errors still get the new manager. An email is sent to the user who saved the global assignment. If there is a workflow for the action and an error occurs in one of the processes after the workflow for the action was approved, the email is sent to the user who initially initiated the action, not the workflow approver. The system also creates an admin alert of the Position Follow-Up Processes type. The alert includes information that helps you identify and fix the errors, such as the name of the failed follow-up process and the name of the user whose initial global assignment was saved. You can also delete the admin alert manually.

There are a number of changes to the position follow-up processes after editing and ending a global assignment, and setting a global assignment to obsolete:

Position Follow-Up Processes

ActionFollow-up ProcessCurrent BehaviorPrevious Behavior
Edit Global Assignment"To Be Hired" AdaptationThe system inserts a new record as of the new start or end date on the home position, changing the "To Be Hired" value. In all steps, the "To Be Hired" Status Adaptation setting in Position Management Settings for assigning or unassigning employees to or from a position are respected.
  • If the new start date is after the old one, the system corrects the old record.
  • If the new start date is before the old one, the old position record can become empty because of forward propagation.

The system corrected the effective start date of the record by which the "To Be Hired" value was changed on the home position as of the previous start or end date. That is, if a correction was possible. If a correction wasn’t possible, for example because of other changes to the record, the system inserted a new record as the new start or end date. The "To Be Hired" Status Adaptation setting in Position Management Settings wasn't respected.
End Global AssignmentMatrix Relationships to Job Relationships SynchronizationThe system synchronizes matrix relationships to job relationships for the host assignment.The system didn’t synchronize matrix relationships to job relationships for the host assignment.
Set Global Assignment to ObsoleteMatrix Relationships to Job Relationships SynchronizationThe system synchronizes matrix relationships to job relationships for the host assignment.The system didn’t synchronize matrix relationships to job relationships for the host assignment.
Set Global Assignment to Obsolete"To Be Hired" Adaptation

The behavior for the host position remains unchanged.

The behavior for the home position is now aligned with the one for the host position: The system does the "To Be Hired" adaptation as of the start date of the obsolete global assignment for the home and host position, respecting the "To Be Hired" Status Adaptation setting in Position Management Settings for assigning and unassigning an employee to or from a position.

The record on which the "To Be Hired" value was changed on the home position, when adding the global assignment, was deleted if possible. If this wasn't possible, for example because of other changes on the record, the system corrected the record. The "To Be Hired" Status Adaptation setting in Position Management Settings wasn't respected.

Employee Central using Centralized services targets consistency regarding system behavior, validations, functionalities across UIs, imports, and APIs. We've made this enhancement for Position Management to decouple main actions from position follow-up processes. This allows the system to significantly improve the performance of MSS changes to Job Information and Job Relationships. Additionally, you can successfully save a main action even if errors occur in position follow-up activities.

Configuration Requirements

As an administrator, if you need to opt out of the feature, the setting for this feature is Admin Center > Company System and Logo Settings > Enable Centralized Services for Global Assignment (Applicable for Add, Edit, End and Obsolete actions from UI).

Note
For important information about the Centralized services overall release strategy, please review the Employee Central Innovation Alert in the SAP SuccessFactors Customer Community.

Role-Based Permission Prerequisites

You have the permission to Edit for User Permissions Manage Data Global Assignment Details Global Assignment Add permission. You have the Admin Alert Object Permissions > Position Follow-Up Admin Alert permission.

What's Changed

In the current version, the position follow-up processes automatically run in the background when a global assignment is added, edited, ended, or set to obsolete. You don't have to wait for the system to finish all these processes before continuing your work. The behavior of some processes has changed for different actions, and are described in the previous table.

In the previous version, you had to wait for the system to finish the follow-up processes before a global assignment was saved.

Technical Details

Reference NumberECT-214690
ProductEmployee Central
Module
  • Employee Data
  • Company Organization
Feature
  • Global Assignment
  • Organizational Management
ActionRecommended
EnablementAutomatically on
Link to Demo 
LifecycleGeneral Availability
TypeNew
Major or MinorMajor
Business Process VariantNot Applicable
Software Version2H 2023
Valid as Of2023-11-17
Latest Document Revision2023-10-13

Related Information

Global Assignments OverviewFollow-Up Processes After Saving Global AssignmentGlobal Assignment in Centralized Services

Centralized Services Support for Hire and Rehire Including Fixed Term Contract

Centralized services now support Hire and Rehire of an employee including Fixed Term Contract (FTC). Hire and Rehire flows (excluding FTC) are also supported when using the Manage Pending Hires tool.

Hire, Rehire, and Fixed Term Contract scenarios on Centralized services come with the following benefits:

  • Forward Propagation

    Forward propagation is now supported for Rehire scenarios as well as Hire and Rehire scenarios for Onboarding. Forward propagation isn’t supported for Fixed Term Contracts.

  • Message Handling

    In cases where there are issues after a user tries to save their changes, warning, and error messages are now grouped by entity and sub-grouped by severity and can also be filtered.

  • Validations

    If you have the User Permissions > National ID (Restricted to only country/region of legal entity) enabled, we now validate that the country/region for national ID is same as the legal entity country/region.

  • We now update the Last Modified Source on all entities that are saved as part of the hire, rehire, and FTC transactions. For hire and rehire including FTC the Last Modified Source is "Hire Process". For FTC termination record, the Last Modified Source is "Fixed Term Contract Termination".
  • The Recruiting follow-up processes for candidates during hire and rehire now happens asynchronously.
  • Work permit entity is now an employment-based entity, instead of being a person-based entity, which means that when rehiring an employee using Rehire with New Employment, the system doesn't display any existing work permit records for this person.
  • Fixed Term Contracts (FTC)

    When adding an FTC between two existing FTCs, we now show the Hire Date and Termination Date of the latest FTC in the Employment Details block. This was done to ensure that the Hire Date and Termination Date in Job information History are in sync with the Hire Date and Termination Date in Employment Details.

  • Position Follow-up Processes

    Position follow-up processes now automatically run in the background when you add or rehire an employee, or add a Fixed Term Contract. The behavior of the different follow-up processes doesn’t change.

    The follow-up processes run in the background in this order:
    1. Reclassification
    2. Take Over Direct Reports
    3. Hierarchy Adaptation
    4. Synchronization between Matrix Relationships and Job Relationships
    5. To Be Hired Status Adaptation for the Position

When an error occurs during one of the follow-up processes, the system saves all the successfully processed data for that process. For example, if an error occurs during Hierarchy Adaptation, the direct reports that were processed without any errors still get the new manager.

The system sends an email to the user who initiated the action. If there is a workflow for the action and an error occurs in one of the processes after the workflow for the action was approved, the email is sent to the user who initially initiated the action, not the workflow approver. The system also creates an admin alert of the Position Follow-Up Processes type. This alert includes information that helps you identify and fix the errors, such as the name of the specific follow-up process that failed, and the name of the user for whom the initial action was saved. Under Actions > Admin Alerts, you can re-trigger the follow-up process after you've resolved the errors. The system then automatically deletes the admin alert. You can also delete the admin alert manually.

Note
When an error occurs, none of the subsequent processes in the sequence are executed. For example, if an error occurs during the Synchronization between Matrix Relationships and Job Relationships, then the "To Be Hired" Status Adaptation for the Position doesn't take place. When you fix the error and retrigger the affected process, the process that initially failed runs again, as well as all subsequent processes.

Employee Central using Centralized services targets consistency regarding system behavior, validations, functionalities across UIs, imports, and APIs. We've made this enhancement for Position Management to decouple main actions from position follow-up processes. This allows the system to significantly improve the performance of MSS changes to Job Information and Job Relationships. Additionally, you can successfully save a main action even if errors occur in position follow-up activities.

Note

We revised the topic to clarify that we do not validate Foundation Objects and Generic Objects in Job Information.

Configuration Requirements

By default, this setting is automatically on in your system. As an administrator, if you need to opt out of the feature, the setting for this feature is Admin Center > Company System and Logo Settings > Enable Centralized Services to Add New Employee, Add New Employee for Fixed Term, and Rehire Inactive Employee.

To enable use of Manage Pending Hires with Onboarding, go to Admin Center > Onboarding General Settings > Submit Onboarding Data Using Centralized Services. By default, this setting is automatically on in your system.

Note

For important information about the Centralized services overall release strategy, please review the Employee Central Innovation Alert in the SAP SuccessFactors Customer Community.

Role-Based Permission Prerequisites

You have the Admin Alert Object Permissions > Position Follow-Up Admin Alert permission.

What's Changed

Last Modified Source

In the current version, one of the changes is that the Last Modified Source is now updated on all entities. Screenshots here show the Last Modified Source for a Hire and Fixed Term Contract.

Position Follow-up Processes

In the current version, the position follow-up processes automatically run in the background when you add or rehire an employee, or add a fixed-term contract. You don't have to wait for the system to finish all these processes before continuing your work. The behavior of each process hasn't changed.

In the previous version, you had to wait for the system to finish the follow-up processes before the employee was added or rehired, or a fixed-term contract was added.

Technical Details

Reference NumberECT-214694
ProductEmployee Central
Module
  • Employee Data
  • Company Organization
Feature
  • Hire, Rehire, and Termination
  • Organizational Management
ActionRecommended
EnablementAutomatically on
Link to Demo 
LifecycleGeneral Availability
TypeChanged
Major or MinorMajor
Business Process VariantNot Applicable
Software Version2H 2023
Valid as Of2023-11-17
Latest Document Revision2023-10-20

Related InformationManaging Regular EmploymentAdding a New EmployeeAdding a New Employee with a Fixed-Term ContractHire, Rehire, and, Fixed Term Contract Hire in Centralized ServicesFollow-Up Processes After Saving an Internal HireForward Propagation in Job InformationLast Updated by Source Details in History UIsEnhancements to Data Review Processes in OnboardingWork Permit Block Now Employment BasedManage Pending Hires Tool3379111 - New Hire Rule Execution in 2H 2023

More Employee Central Jobs on Job Scheduler in Scheduled Job Manager

You can now create, manage, and monitor more types of scheduled jobs for Employee Central in the Scheduled Job Manager admin tool. These jobs are now available only in the Admin Center and are no longer available in Provisioning.

The following are new job types on the Job Scheduler and Job Monitor tabs.

Job TypeDescriptionNotes
Position Management Daily Hierarchy Adaptation JobWhen hierarchies aren't in sync, you can schedule this job to set the correct manager based on the position hierarchy.The Position Management Daily Hierarchy Adaptation Job was available on the Job Monitor tab. Now it's also available in the Job Scheduler tab.
Off Cycle Event Batch Processing JobWith the help of an Off Cycle Event Batch, you can configure your system to execute a customized set of instructions in the background for transactions that are recurring. As a result, the periodic requirement for manually updating the employee records is practically eliminated.The BizX Daily Rule Processing Batch job is now renamed to Off Cycle Event Batch Processing Job.
Note
  • To see a list of supported job types, go to Scheduled Job Manager > Job Scheduler and open the Job Type menu.
  • Job types that aren't available in Scheduled Job Manager can still be managed in Provisioning.

This enhancement is part of an ongoing effort to make Scheduled Job Manager the central self-service tool for managing and monitoring scheduled jobs.

Role-Based Permission Prerequisites

You have the following permission:

  • Administrator > Admin Center Permissions > Monitor Scheduled Jobs
  • Administrator > Admin Center Permissions > Manage Scheduled Jobs

Technical Details

Reference NumberECT-219021
ProductEmployee Central
Module
  • Company Organization
  • Process Automation
Feature
  • Organizational Management
  • Data Import and Export
ActionInfo only
EnablementAutomatically on
Link to Demo 
LifecycleGeneral Availability
TypeChanged
Major or MinorMinor
Business Process VariantNot Applicable
Software Version2H 2023
Valid as Of2023-11-17
Latest Document Revision2023-10-13

Related Information

Managing Scheduled Jobs in Admin CenterSetting Up Automated Daily Hierarchy AdaptationNotes on Some Common Job Types

Enhancements to Duplicate Check

We’ve enhanced the Duplicate Check feature to improve rehiring of contingent workers and improve data privacy.

The changes to the user interface are as follows:

For contingent workers:

  • Duplicate Check pop-up window now clearly identifies the type of employment as Contingent Worker.
  • You can only rehire a contingent worker with new employment. Hence, we’ve renamed the Accept Match button to Rehire with New Employment.
  • The renaming of the Accept Match button makes the Rehire as a different user? pop up window redundant. This window no longer appears when rehiring the contingent worker.

For users with Finnish national ID:

Duplicate Check now masks the Legislatively Sensitive Personal Data in the national ID.

This enhancement provides better user experience when rehiring a contingent worker. The changed masking pattern makes the Legislatively Sensitive Personal Data in the Finnish national ID secure.

Role-Based Permission Prerequisites

You have the Administrator Permissions > Manage Hires > Rehire Inactive Employee (by 'match in New Hire)' permission.

You have the Administrator Permissions > Manage Hires > Rehire Inactive Employee with New Employment (by 'match in New Hire)' permission.

What's Changed

Type of Employment

In the current version, as shown in the screenshot, the type of employment is clearly identified as Contingent Worker.

In the previous version, the type of employment for a contingent worker wasn’t shown.

In the previous version, the Rehire as a different user? pop-up window was shown.

In the current version, the Legislatively Sensitive Personal Data of the national ID for Finland is masked.

In the previous version, the last four digits of the national ID were visible, which meant that Legislatively Sensitive Personal Data wasn’t masked.

Technical Details

Reference NumberECT-218412
ProductEmployee Central
Module
  • Employee Data
  • Contingent Workforce
FeatureContingent Workforce
ActionInfo only
EnablementAutomatically on
Link to Demo 
LifecycleGeneral Availability
TypeChanged
Major or MinorMajor
Business Process VariantNot Applicable
Software Version2H 2023
Valid as Of2023-11-17
Latest Document Revision2023-10-13

Related Information

Rehiring as a Contingent WorkerIdentity - FinlandValidation Rules - Finland

Centralized Services Support Manager Self-Service Changes for Concurrent Employment

Centralized services now support adding a concurrent employment using the Manager Self-Service (MSS) Take Action > Add Concurrent Employment menu and from the Manage Pending Hires tool.

Concurrent Employment using MSS on Centralized services comes with the following benefits:

  • Message Handling

    In cases where there are issues after a user tries to save their changes, warning, and error messages are now grouped by entity and sub-grouped by severity and can also be filtered.

  • Position Follow-Up Activities

    When a concurrent employment is saved, the following processes now run in the background:

    • Hierarchy Adaptation

    • To-Be-Hired status adaptation for the position

    • Position Reclassification

    • Synchronization between Matrix Relationships and Job Relationships

  • If Position Management is enabled, when adding a concurrent employment, you can decide on the allocation of direct reports, meaning that you can decide whether incumbents stay with the current manager or move to the new hire.
  • Workflows

    • For pending Concurrent Employment workflows, the Job Relationships section is now shown to the user.
    • When updating an Add Concurrent Employment workflow, we don’t check if the user has the Edit permission for User Permissions > Employee Data > Employment Details > Add new Employment permission. This means that a user is able to update any of the concurrent employment details even if they don’t have this permission.
  • Event Reasons

    All Hire event reasons are shown in the drop-down list.

  • Locale

    When adding a concurrent employment, the system uses the default company locale rather than the locale of the logged-in user.

There are a few changes from legacy behavior:

  • FTE Calculation for onSave Rules

    If the standard-hours field is enabled in the configuration, the system will always calculate the FTE based on Job Information Standard Hours vs Object Standard Hours (Legal Entity or Location or Job Classification) depending on the configuration. This ensures that the FTE value is never zero. However, if you have manually updated the FTE value or set it using a rule to a value other than null or zero, it will not be overwritten by the automated calculation.

  • onView Rules

    onView rules are no longer supported.

  • Cross-Entity Rules

    Cross-entity rules with Employment Information as the source element and Compensation Information, Recurring Pay Components, Non-Recurring Pay Components, or Job Relationships as the target element are no longer supported.

    Note

    This means that some rules in your system may need to be checked and updated, as well as new rules created.

    For more information, refer to the Cross-Entity Rules with Centralized Services.

  • When adding a Concurrent Employment, country/region-specific fields configured for Employment Information are now displayed.

Here's an example of the fields shown to the administrator in the Add Concurrent Employment page.

Employee Central using Centralized services targets consistency regarding system behavior, validations, functionalities across UIs, imports, and APIs.

Configuration Requirements

As an administrator, if you need to opt out of the feature, the setting for this feature is Admin Center > Company and Logo Settings > Enable Centralized Services to Add Concurrent Employment on the Manager Self-Service UI (and Enable Configurable Concurrent Employment).

For important information about the Centralized services overall release strategy, please review the Employee Central Innovation Alert in the SAP SuccessFactors Customer Community.

Role-Based Permission Prerequisites

You have the permission to Edit for User Permissions > Employee Data Employment Details > Add new Employment permission. You have the Admin Alert Object Permissions Position Follow-Up Admin Alert permission.

Technical Details

Reference NumberECT-224568
ProductEmployee Central
ModuleEmployee Data
FeatureConcurrent Employment
ActionRecommended
EnablementAutomatically on
Link to Demo 
LifecycleGeneral Availability
TypeChanged
Major or MinorMajor
Business Process VariantNot Applicable
Software Version2H 2023
Valid as Of2023-11-17
Latest Document Revision2023-10-13

Related Information

Centralized Services in Employee CentralManager Self-Service (MSS) Supported on Centralized ServicesFollow-Up Processes After Saving Concurrent EmploymentCalculating FTEEnhanced Message HandlingConcurrent Employment with Centralized ServicesConfiguring Concurrent EmploymentChanging an Employee's Hire Date in Employee Central

New Attachment Field for Global Information

You can now choose to enable the field attachment-id in the HRIS element globalInfo for any country or region.

The new field allows users to upload country/region-specific documents for employees and their dependents, enabling companies to better meet local compliance requirements.

Role-Based Permission Prerequisites

After you enable the attachment-id field for a country or region, you must have the User > Employee Central Effective Dated Entities > Personal Information > <country/region code>-Attachments permission to view or edit the attachments.

How It Looks Now

Technical Details

Reference NumberECT-210488
ProductEmployee Central
ModuleEmployee Data
Feature
  • Personal Information
  • Country/Region Specifics
ActionInfo only
EnablementCustomer configured
Link to Demo 
LifecycleGeneral Availability
TypeNew
Major or MinorMinor
Business Process VariantNot Applicable
Software Version2H 2023
Valid as Of2023-11-17
Latest Document Revision2023-10-13

Related Information

Global InformationEnabling Attachments for Personal Information Entities

Universal Updates for Centralized Services

We have introduced universal support for some of the Centralized services entities. These entities are no longer governed by the configuration option.

The following table lists all the previously delivered universal items in addition to the current release items marked as 2H 2023 in the Release column.

Universal Entities on Centralized Services

For more information about the overall release strategy for Centralized services, review the Employee Central Innovation Alert in the SAP SuccessFactors Customer Community.

Employee Central using Centralized services targets consistency regarding system behavior, validations, functionalities across UIs, imports, and APIs. With this enhancement, you have access to the supported Centralized services entities by default.

What's Changed

In the current version, the Centralized services entities are made available by default.

In the previous releases, the listed Centralized services were available by enabling them in the Admin Center.

Technical Details

Reference NumberECT-216114
ProductEmployee Central
ModuleEmployee Data
Feature
  • Data Import and Export
  • Employee Central Compensation
  • Hire, Rehire, and Termination
  • Pending Hires
  • Public Sector Management
ActionInfo only
EnablementAutomatically on
Link to Demo 
LifecycleGeneral Availability
TypeChanged
Major or MinorMajor
Business Process VariantNot Applicable
Software Version2H 2023
Valid as Of2023-11-17
Latest Document Revision2023-10-13

Related Information

Centralized Services for Employee Data ImportsCentralized Services in Employee CentralCentralized Services Support Termination Details Imports with Pension Payouts

New Compensation Structure Object

In SAP SuccessFactors Employee Central, we are working to improve setting up and managing complex pay structures. This allows companies to specify pay structures for different locations, legal entities, as well as for different types of workers.

Using the Compensation Structure object in Manager Self-Services and the Compensation History UI allows you to:

  • Define a sort order of how pay components are displayed in the UI

  • Select only those pay components that are assigned to the compensation structure

  • Prevent mandatory pay components from being removed from an employee's compensation

  • Prorate compa ratio and range penetration more flexibly

    We have added configuration for proration to allow you to choose between FTE, a proration factor, or no proration.

Caution
You still need to use use business rules for the calculation of pay components.

We are improving the experience to guide managers while editing compensation data along predefined compensation structures.

Configuration Requirements

For proration, you have enabled the Admin Center > Company Settings > Calculate Range Penetration and Compa Ratio even if one or more of these fields (FTE, Proration Factor, or Standard Weekly Hours) are not set or are zero setting. This setting existed previously but the name has been updated.

You must use the Pay Scale Type and Pay Scale Area MDF objects.

Note
Since standard MDF objects exist for Pay Scale Type and Pay Scale Area, we recommend that you migrate from the pay scale picklists of the Job Information fields for Pay Scale Type and Pay Scale Area to MDF to avoid double data maintenance. For more information, refer to the Deprecation of Pay Scale Picklist Fields topic.

To use the new Compensation Structure field, add it to the Compensation Information element in Manage Business Configuration, ensure it is visible, and grant permissions for its use.

Once an admin has permissions to create a comp structure object, then they can create Compensation Structure objects in Manage Data.

To use the new Proration Factor field, you can add it to the Compensation Information element in Manage Business Configuration, ensure it is visible, and the grant permissions for its use.

Role-Based Permission Prerequisites

You have the Administrator > Manage Compensation Structure Objects > Compensation Structure permission. You also have permission to edit/view the Compensation Structure item.

You have the Administrator > Manage Compensation Structure Objects > Compensation Structure.Pay Components permission. You also have permission to edit/view the Pay Components required for the Compensation Structure.

What's Changed

How It Looks Now

In the current version, you can create an MDF object and assign recurring pay components to specify the structure.

In the previous version, this object did not exist.

Technical Details

Reference NumberECT-208195
ProductEmployee Central
ModuleEmployee Data
FeatureEmployee Central Compensation
ActionInfo only
EnablementCustomer configured
Link to Demo 
LifecycleGeneral Availability
TypeNew
Major or MinorMajor
Business Process VariantNot Applicable
Software Version2H 2023
Valid as Of2023-11-17
Latest Document Revision2023-10-13

Related Information

Configuring the Compensation Structure Object

Deprecation of Pay Scale Picklist Fields

Support for pay scale picklists of the Job Information fields Pay Scale Type and Pay Scale Area will reach End of Maintenance on November 17, 2023and will be Deleted on May 17, 2024.

Key Dates

Future dates are subject to change.

MilestoneDateDefinition
End of DevelopmentJune 2, 2023The 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 MaintenanceNovember 17, 2023The 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.
DeletedMay 17, 2024The 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

Since standard MDF objects exist for Pay Scale Type and Pay Scale Area, we recommend that you migrate from the pay scale picklists of the Job Information fields for Pay Scale Type and Pay Scale Area to MDF which helps to avoid double data maintenance. You can also benefit from MDF-based features such as extensibility, ease of data maintenance by HR Admins, reporting capabilities, workflows, rules, role-based permissions, and so on.

Note

You don't have to migrate if:

  • You don't have picklists assigned to Pay Scale Area and Pay Scale Type in the Succession and Country/Region-Specific Succession Data models.

  • You've added values for Pay Scale Area and Pay Scale Type in Manage Data.

A self-service job Admin Center > Scheduled Job Manager > Initialize migration of picklist fields payscale area and type to mdf objects is available for this migration.

Additional Resources

For more information about migrating the values of the pay scale picklist fields to MDF, refer to:

Technical Details

Reference NumberECT-203910
ProductEmployee Central
ModuleEmployee Data
FeatureEmployee Central Compensation
ActionRecommended
EnablementAutomatically on
Link to DemoNot Applicable
LifecycleDeprecated
TypeChanged
Major or Minor 
Business Process VariantNot Applicable
Software Version
  • 1H 2023
  • 2H 2023
  • 1H 2024
Valid as Of2024-05-17
Latest Document Revision2023-10-13

Change History

DateWhat ChangedReason
April 21, 2023Initial publication 
Oct 13, 2023NoteAdded a note to let you know when not to migrate from the pay scale picklists to MDF objects.

Mappings to Standard Element UserId Ignored During HRIS Sync

When you configure HRIS Sync mappings in the Succession Data Model, if you map HRIS fields to the standard element userId, these mappings will be ignored during HRIS Sync and the data won't be synced to userId.

As a unique and stable identifier for each user in the system, User ID is not changeable. This enhancement is to ensure smooth running of the sync job and prevent potential system issues that could result from such mappings.

Technical Details

Reference NumberECT-215965
ProductEmployee Central
ModuleEmployee Data
FeatureHRIS Sync
ActionInfo only
EnablementAutomatically on
Link to Demo 
LifecycleGeneral Availability
TypeChanged
Major or MinorMinor
Business Process VariantNot Applicable
Software Version2H 2023
Valid as Of2023-11-17
Latest Document Revision2023-10-13

Related Information

Rules for Configuring HRIS Sync MappingsDifferentiating Between Person ID, UUID, User ID, and Assignment ID

Centralized Services Support Termination Details Imports with Pension Payouts

Centralized services now support Termination Details data imports when Pension Payouts is enabled. These services are applicable to data imports initiated from the Import Employee Data page or OData APIs.

Termination Details Imports with Pension Payouts on Centralized services comes with the following benefits:

  • You’re no longer able to initiate a termination workflow for an employee on global assignment or with Pension Payouts with a pending termination workflow. You’re only able to trigger a termination for employees with a completed or cancelled termination workflow. Previously, this validation only existed for regular employment.
  • You can now only terminate a regular employment with Terminate event. Previously, you were able to use pension payout events when terminating regular employments.
  • You can now only terminate an employee with Pension Payouts with End Pension Payouts event. Previously, you were able to use Terminate event for employees with Pension Payouts.
  • You can now have only the changed End Pension Payout record in Job Information when there is any change to the Pension Payout End Date. Previously, you were able to see the End Pension Payout record with the original End Date as well as with the changed End Date. The changed End Date may be before or after the original End Date.

Here's the Import Employee Data page showing the Termination Details import selected.

Employee Central using Centralized services targets consistency regarding system behavior, validations, functionalities across UIs, imports, and APIs.

Technical Details

Reference NumberECT-214692
ProductEmployee Central
ModuleEmployee Data
Feature
  • Hire, Rehire, and Termination
  • People Profile
ActionInfo only
EnablementAutomatically on
Link to Demo 
LifecycleGeneral Availability
TypeChanged
Major or MinorMinor
Business Process VariantNot Applicable
Software Version2H 2023
Valid as Of2023-11-17
Latest Document Revision2023-10-13

Related Information

Termination Details ImportsEvents in Employee CentralTermination Using Imports

Deprecation of Suppress Switch in Company System and Logo Settings

The Suppress update of identical records during Employee Central import for supported entities setting in Company System and Logo Settings page will reach end of maintenance on June 2, 2023 and will be deleted from the code by November 17, 2023.

Key Dates

Future dates are subject to change.

MilestoneDateDefinition
End of DevelopmentJune 2, 2023The 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 MaintenanceJune 2, 2023The 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.
DeletedNovember 17, 2023The 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

In 1H 2023, the Suppress update of identical records during Employee Central import for supported entities setting will still be available for use and its behavior is enabled by default for all Employee Central instances. However, we're removing the setting from Company System and Logo Settings in 2H 2023 . We’ll be deprecating this setting to improve data consistency and performance by ensuring that duplicate records aren’t added with the data imports.

Once the setting is removed, employee data imports have the suppression enabled by default and there is no option to disable it.

Note

ODATA V2 APIs continue to support the suppressUpdateOfIdenticalData parameter. For more information, refer to thesuppressUpdateOfIdenticalData topic in the SAP SuccessFactors API Reference Guide (OData V2) guide.

Technical Details

Reference NumberECT-215843
ProductEmployee Central
ModuleEmployee Data
FeatureMass Changes
ActionInfo only
EnablementAutomatically on
Link to DemoNot Applicable
LifecycleDeprecated
TypeChanged
Major or Minor 
Business Process VariantNot Applicable
Software Version
  • 1H 2023
  • 2H 2023
Valid as Of2023-11-17
Latest Document Revision2023-10-13

Change History

DateWhat ChangedReason
April 21, 2023Initial publication. 
October 13, 2023We added a note ODATA APIs. .The APIs continue to support the suppression parameter.

Work Permit Block Now Employment Based

By default, the Work Permit block on People Profile now shows data based on a user's employment. This enhancement affects employees who have multiple employment records, such as global assignment or concurrent employment records. With employment-based Work Permit blocks, employees only view work permit records related to their current employment and need to switch to other employment records to view additional work permit records. We also provided a new option in Admin Center for customers who want to turn off the enhancement and view the data on person level. With the enhancement turned off, they can, as they did in previous releases, view work permit records related to all their employment records after logging into any account corresponding to those employment records. Changing the Work Permit block to employment-based reduces confusion and improves consistency in how we process and present work permit data.

Configuration Requirements

The enhancement is enabled by default. To disable it, deselect the option Keep the Work Permit block in People Profile user-based at Admin Center > Company System and Logo Settings.

What's Changed

How It Looks Now

The Work Permit block is now employment based by default. It shows just one record, which is related to the employee’s current employment.

How It Looked Before

Previously, the Work Permit block was person based. It would show two records related to the two employment records of the employee.

Related Information

Work PermitsUser-based Work Permit Block Going Universal in First Half of 2024

Add to Transport Bundle in Employee Central

You can add Business Configuration UI configurations and Foundation Objects to a bundle and transport them using Configuration Transport Center.

The Add to Transport Bundle option is now available for:

Refer to the following table for additional information regarding the Add to Transport option.

FeatureWhere?Notes
Business ConfigurationIn the View page of the HRIS Element in Business Configuration UI, choose Add to Transport Bundle, under the Take Action dropdown.You can add HRIS Elements, HRIS Actions or Employee Profile Elements to a bundle to transport data to a target system using Configuration Transport Center.
Foundation ObjectsIn theManage Organization, Pay and Job Structures page, search for the foundation object (for example, Location). In the Take Action dropdown, choose Add to Transport Bundle.You can transport data of Legacy Foundation Objects using Configuration Transport Center.

We've added this enhancement in the Business Configuration UI and Foundation Data Objects page to eliminate manual configuration efforts in the paired target system.

Configuration Requirements

You've created a transport bundle in Configuration Transport Center.

Role-Based Permission Prerequisites

You have the Administrator > Manage Foundation Objects > Transport Legacy Foundation Data

You have the Administrator > Configuration Transport Center > Access to transport configurations.

What's Changed

How It Looks Now

Technical Details

Reference NumberECT-224492
ProductEmployee Central
ModuleProcess Automation
Feature
  • Business Configuration
  • Configuration Transport Center
ActionInfo only
EnablementAutomatically on
Link to Demo 
LifecycleGeneral Availability
TypeNew
Major or MinorMajor
Business Process VariantHire to Retire
Software Version2H 2023
Valid as Of2023-11-17
Latest Document Revision2023-10-13

Related Information

Adding Configurations for Business Configuration UI to a Transport BundleAdding Legacy Foundation Objects to a Transport Bundle

Enhanced Rule Handling for Event Reason Derivation and Workflow Derivation Rules

We have updated the order in which the system processes the event reason derivation rules and workflow derivation rules that are created from their specific rule scenarios.

The system now processes the onSave rules based on the order defined in the Manage Business Configuration with the exception that the rules configured for event reason derivation and workflow derivation from the rule scenarios are executed after all the other rules are executed. Previously, the system processed the onSave rules based on the order in which the rules were listed in Manage Business Configuration.

Here is the new order in which the onSave rules will be executed:

  • For rule for Personal Information, where event reason derivation is not applicable, here is the order: National ID rules and Workflow Derivation rules.

  • For rules for Job information, here is the order: Job information rules, Event Reason Derivation rules, and Workflow Derivation rules.

  • For saving changes made from Manager Self-Serivce for both Job Information and Compensation Information, here is the order: Job Information rules, Compensation Information rules, Event Reason Derivation rules for Job information, Workflow Derivation rules for Job Information, Event Reason Derivation rules for Compensation Information, Workflow Derivation rules for Compensation Information.

The rule handling is changed for the following transactions:

  • Manager Self-Serivce: for changes made to Job Information, Compensation Information, Recurring Pay Components, Non-Recurring Pay Components, Termination Details, Global Assignments, and Concurrent Employment

  • Add New Employee: for New Hire, Rehire, and Fixed-Term Contract scenarios

  • People Profile: for changes made to Personal and Global Information, Address Information, National ID Information, Work Permit Information, and Biographical Information

  • Hint

    We recommend to only configure one scenario-based rule for workflow derivation in HRIS elements.

    We recommend to only configure one event reason derivation scenario-based rule in Job Information or Compensation Information.

This change does not impact cross-entity rules.

This system change is done so that the event reason derivation and workflow derivation rules always pick up all the calculations and updated field values before derivation to ensure correctness and reduce errors.

Technical Details

Reference NumberECT-221576
ProductEmployee Central
ModuleProcess Automation
FeatureBusiness Rules
ActionInfo only
EnablementAutomatically on
Link to Demo 
LifecycleGeneral Availability
TypeChanged
Major or MinorMinor
Business Process VariantNot Applicable
Software Version2H 2023
Valid as Of2023-11-17
Latest Document Revision2023-10-13

Related Information

Event Reason Derivation Business Rules

Workflow Auto-Delegation by Groups

Users can now delegate their workflows by groups, if they don't want to delegate them all to one person.

To take advantage of the new enhancement, you define workflow groups in Manage Data, by bundling similar or related workflow requests into groups. Employees can then choose these groups and appoint a delegatee for each of them when setting up auto-delegation through the Delegate My Workflows quick action. Likewise, HR admins can use these groups when setting up auto-delegation on behalf of other employees. Users can appoint delegatees for up to three groups (including the default "All Others" group). As they've done in previous versions, they can choose to delegate all workflow requests to one single person.

The Delegate My Workflows Dialog, with New Option to Delegate by Workflow Groups

With this enhancement, your organization has a more organized approach towards workflow delegation and your users have the flexibility to appoint multiple delegatees to take care of their requests.

Configuration Requirements

To make sure that users can delegate workflows by groups, you must have created at least one workflow group in Manage Data.

Role-Based Permission Prerequisite

Delegators have the view permission to Auto Delegate Group at Administrator Permissions > MDF Foundation Objects.

Technical Details

Reference NumberECT-118367
ProductEmployee Central
ModuleProcess Automation
FeatureWorkflows
ActionInfo only
EnablementCustomer configured
Link to DemoSetting Up Auto-Delegation by Workflow Groups
LifecycleGeneral Availability
TypeNew
Major or MinorMajor
Business Process VariantNot Applicable
Software Version2H 2023
Valid as Of2023-11-17
Latest Document Revision2023-10-13

Related Information

Auto-Delegation Groups

Deprecation of XML File (YouCalc Rules) Based Workflow Triggering

The feature of triggering workflows through XML files (YouCalc rules) will reach the End of Development on November 17, 2023 and be deleted on November 17, 2025.

Key Dates

Future dates are subject to change.

MilestoneDateDefinition
End of DevelopmentNovember 17, 2023The 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 MaintenanceNovember 15, 2024The 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.
DeletedNovember 14, 2025The 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

Until 1H 2023, customers can trigger workflows through imported XML files or through business rules. Starting from the 2H 2023 release, new customers will be prevented from importing XML files to trigger workflows; they can only trigger workflows through business rules. Meanwhile, we recommend that existing customers migrate their existing rules from XML files to business rules before the Deleted date.

Using XML files to trigger workflows requires access to Provisioning and demands high skill levels of users. Business rules, which are defined by users themselves in Admin Center, offer a more intuitive and more flexible way to perform the same job.

Additional Resources

Technical Details
Reference NumberECT-219827
ProductEmployee Central
ModuleProcess Automation
FeatureWorkflows
ActionRequired
EnablementAutomatically on
Link to DemoNot Applicable
LifecycleDeprecated
TypeChanged
Major or Minor 
Business Process VariantNot Applicable
Software Version
  • 2H 2023
  • 1H 2024
  • 2H 2024
  • 1H 2025
  • 2H 2025
Valid as Of2025-11-14
Latest Document Revision2023-10-13
Change History
DateWhat ChangedReason
November 17, 2023Initial publication. 

Enhancements to View Job Details

You can view details of a job request by clicking the job name in Scheduled Job Manager. We made several enhancements to the job details pop-up and added a new job details page.

Here are the details:

Where's the changeBeforeAfter
Job Details popupAfter you clicked the name of a job request, the Job Details popup displayed. All the job details were in this small popup.In the Job Details popup, we added a new button, View More Details. After clicking this button, you’ll be redirected to a page of more job details. You can see basic job request information in the Job Details popup, and see detailed information in the new View Job Details page, for example, FTP configuration and notification information.
If there were multiple times of a day in theTime field, there was no note to inform you the time zone of the times.You can see a note informing you the time zone of the values in the Time field.
In the Schedule Information section, the label was Month.The label is now Months. Because multiple values are supported in this field.
In the Schedule Information section, the label was Day.The label is now Days. Because multiple values are supported in this field.
New pageIn Job Details popup, there was a Recipients field.We changed the label into Additional Recipients on the View Job Details page. Because the email address of a job owner isn’t listed in this field.
Previously, you couldn't see job parameter information in job details.Now, if the job type supports job parameters, you can also see job parameters in the Job Definition section on the View Job Details page.

We made the enhancement to provide you with more job details in a smoother flow.

How It Looks Now

Previously, there was no View More Details button on the Job Details popup.

Technical Details

Reference NumberPLU-6831
ProductPlatform
ModulePlatform
FeatureScheduled Jobs
ActionInfo only
EnablementAutomatically on
Link to Demo 
LifecycleGeneral Availability
TypeChanged
Major or MinorMajor
Business Process VariantNot Applicable
Software Version2H 2023
Valid as Of2023-11-17
Latest Document Revision2023-10-13

Related Information

Managing Scheduled Jobs in Admin Center

Deprecation of Basic Rule Creation

The possibility to create new rules using the 'Basic' rule scenario will reach the end of maintenance on November 17, 2023 and will be deleted on June 2, 2024.

Key Dates

Future dates are subject to change.

MilestoneDateDefinition
End of DevelopmentJune 2, 2023The 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 MaintenanceNovember 17, 2023The 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.
DeletedJune 2, 2024The 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're deprecating the ability to create new rules using the 'Basic' rule scenario because this method doesn’t provide any guidance or guardrails, is very error-prone, and leads to a lot of rule misconfigurations. With the 1H 2024 release, all new rules must be created with an application-specific rule scenario, since the 'Basic' rule scenario will not be available on the Create New Business Rule page anymore. From the 2H 2023 release, you now receive the warning that the 'Basic' rule scenario will be deprecated and that you should choose an application-specific scenario instead. You should only continue with the 'Basic' rule scenario in cases where none of the application-specific scenarios meet your needs.

All existing rules using the 'Basic' rule scenario are still supported and executed; there is no change to these existing rules.

To create new rules, you must now use the application-specific rule scenarios that are already available. These application-specific rule scenarios provide guidance on the supported objects and actions as well as provide new features that are not available for rules using the 'Basic' rule scenario.

For more information about application-specific rule scenarios and how to move existing basic rules to the corresponding scenario, refer to Creating Business Rules.

Additional Resources

For more information about the benefit of using dedicated rule scenarios or how to move basic rules to the corresponding scenario, refer to the Display Assignment Information and other enhancements based on Rule Scenarios and 2H 2022 Release Enhancements in the Area of Business Rulesblogs.

Technical Details
Reference NumberRUL-9869
ProductPlatform
ModulePlatform
FeatureBusiness Rules
ActionRecommended
EnablementAutomatically on
Link to DemoNot Applicable
LifecycleDeprecated
TypeChanged
Major or Minor 
Business Process VariantNot Applicable
Software Version
  • 1H 2023
  • 2H 2023
  • 1H 2024
Valid as Of2024-05-17
Latest Document Revision2023-08-25
Change History
DateWhat ChangedReason
August 25, 2023Initial publication.This topic wasn't published as expected on Friday, August 18 for technical reasons. We are republishing the initial copy on August 25.
September 15, 2023We updated the text to ensure consistency in saying 'Basic' rule scenario.We wanted to improve consistency in communication.

Warning Message When Creating a Rule for the Basic Rule Scenario

When you select the Basic rule scenario to create a business rule, you now receive the warning that the Basic rule scenario will be deprecated and that you should choose an application-specific scenario instead. You should only continue with the Basic scenario in cases where none of the application-specific scenarios meet your needs.

For more information about the deprecation of the Basic rule scenario, refer to the Deprecation of Basic Rule Creation topic.

Rules based on application-specific rule scenarios have reduced risk of misconfiguration and the process of rule creation is simpler.

What's Changed

How It Looks Now

Technical Details

Reference NumberRUL-10100
ProductPlatform
ModulePlatform
FeatureBusiness Rules
ActionInfo only
EnablementAutomatically on
Link to Demo 
LifecycleGeneral Availability
TypeChanged
Major or MinorMajor
Business Process VariantNot Applicable
Software Version2H 2023
Valid as Of2023-11-17
Latest Document Revision2023-10-13

Related Information

Overview of Application-Specific Rule Scenario DocumentationRule Scenarios

Enhanced Main Navigation Menu

We've enabled some visual changes to the main navigation menu by default.

The following changes are automatically enabled:

  • The menu includes icons that represent each product area.

  • The menu is organized into three sections: Home, standard links to the main product areas, and custom links that are configured in your system.

  • Standard links are now sorted alphabetically, based on the user's locale.

This feature improves usability and user experience.

Configuration Requirements

These enhancements are enabled by default. You can disable them by deselecting the Show icons and use alphabetical order in the main navigation menu setting on the Company System and Logo Settings page.

Note
Although currently these changes can be turned off, we encourage all customers to prepare to adopt them in the future.

What's Changed

How It Looks Now

In the current version, by default, the main navigation menu includes icons, is organized in sections, and lists items in alphabetical order.

Technical Details

Reference NumberWEF-120022
ProductPlatform
ModulePlatform
FeatureGlobal Page Header
ActionInfo only
EnablementAutomatically on
Link to Demo 
LifecycleGeneral Availability
TypeNew
Major or MinorMinor
Business Process VariantNot Applicable
Software Version2H 2023
Valid as Of2023-11-17
Latest Document Revision2023-10-13

Related Information

Disabling Icons and Sections in the Main Navigation Menu

New Status Icon For Assignment of Scenario-Based Rules in Business Rules Admin Page

In the Business Rules Admin page, in the Assigned column, we have added a new assignment status and icon in cases where the rule assignment information cannot be retrieved by the system. This allows the system to also provide more details about the reason why no status is displayed.

The Assigned column in the Business Rules Admin Page shows the information whether a scenario-based rule is assigned or not. With that information, it is much easier to find rules that are currently not assigned or find out where rules are assigned. Additionally, by selecting the icon, the system helps in assigning the rule correctly or take you to the correct UI to unassign the rule. For basic rules, the system does not display any assignment information at all.

We added the new status and icon to avoid confusion between basic rules and scenario-based rules without a status.

What's Changed

Technical Details

Reference NumberRUL-7159
ProductPlatform
ModulePlatform
FeatureBusiness Rules
ActionInfo only
EnablementAutomatically on
Link to Demo 
LifecycleGeneral Availability
TypeNew
Major or MinorMajor
Business Process VariantNot Applicable
Software Version2H 2023
Valid as Of2023-11-17
Latest Document Revision2023-10-13

Related Information

Business Rules Admin PageExporting List of Business Rules Including Assignment Information

Employee Central Quick Actions for Employee and Manager Self-Services

You can now define Employee Central Quick Actions using templates for commonly used Employee Self-Service and Manager Self-Services. Using the templates, you can tailor use cases for your company and country/region-specific requirements.

Note
We have updated the Role-Based Permission Prerequisites section to remove the note about field-level permissions. We have included a link to the topic where the complete list of required permissions is listed.

A template allows you to combine the relevant fields from multiple data models for the same base entity that are required for a specific use case as well as limit the number of fields shown to the user to the ones relevant for a given use case. For each pre-delivered use case, you can create up to 5 templates. Each Quick Action allows a definiton of 5 standard and custom fields (including country/region-specific fields) in total, as well as the effective date field.

Here are the supported use cases:

  • Change Chosen Name

  • Change Contract End Date

  • Change Cost Center

  • Change Job

  • Change Legal Name

  • Change Location

  • Change Probation

  • Change Pronouns

  • Change Working Time

  • Promotion

  • Transfer

  • View Cost Center

  • View Job

  • View Legal Name

  • View Location

  • View Marital Status

Once you have set up the templates and set the permissions, they are available for use from the following locations:

  • Web Application:
    • To view or change their own information, an employee selects the new Manage My Data quick action on the home page.

    • To view or change information for their reports, a manager selects the Manage My Team quick action on the home page.

    • People Profile > Actions
    • Quickcard > Employee Details > Show Actions and Links

  • Mobile Application (iOS and Android):
    • To view or change their own information, an employee selects the Manage My Data quick action on the home page.

    • To view or change information for their reports, a manager selects Team > More Actions

  • Joule
  • Microsoft Teams
  • SAP Work Zone

Existing configurations for your business processes are accepted by the system, for example, for workflow derivation or event reason derivation.

For business rule handling, the system executes onChange rules for target fields, even if they are not visible in the UI.

The system also ensures that the data model field attribute Visibility cannot be changed from View to Edit or the Mandatory attribute cannot be changed from Yes to No or the reverse.

The templates simplify the Manager and Employee Self-Service experience by providing guidance and hiding complexity, since the amount of fields displayed are reduced to meet the use-case-specific needs.

Configuration Requirements

To enable this feature, navigate to Admin Center Manage > Employee Central Settings > Person, Employment and Worker Type > Employee Central Quick Actions.

To show Manage My Data and Manage My Team quick actions on the home page, enable them at Admin Center > Manage Home Page > Quick Actions.

Role-Based Permission Prerequisites

You have the Administrator Permissions > Manage Business Configuration > Employee Central Quick Action Template permission to configure the template..

You have the User Permissions > Employee Central Quick Actions permission for each template. Permissions must be granted to the target user group for each template created.

For the full list of the required permissions, refer to the Configuring an Employee Central Quick Action Template topic.

What's Changed

Template Configuration for Use Case

How It Looks Now 

Use Case in the Home Page

How It Looks Now

Technical Details

Reference NumberECT-216101
Product
  • Employee Central
  • Platform
  • SAP SuccessFactors Work Zone
Module
  • Employee Data
  • Platform
Feature
  • Job Information
  • Personal Information
  • Home Page
  • People Profile
  • Quickcards
  • Work Tech
  • Mobile Applications
  • Joule
ActionRecommended
EnablementCustomer configured
Link to Demo

Employee Central Quick Actions in SAP SuccessFactors Mobile App

Employee Central Quick Actions

LifecycleGeneral Availability
TypeNew
Major or MinorMajor
Business Process VariantNot Applicable
Software Version2H 2023
Valid as Of2023-11-17
Latest Document Revision2023-10-20

Related Information

Configuring an Employee Central Quick Action TemplateUse Cases for Employee Central Quick ActionsEmployee Central Quick Actions Available in SAP SuccessFactors Work Zone CardsEmployee Central Quick Actions in Microsoft TeamsEmployee Central

Work Permit Block Now Employment Based

By default, the Work Permit block on People Profile now shows data based on a user's employment.

This enhancement affects employees who have multiple employment records, such as global assignment or concurrent employment records. With employment-based Work Permit blocks, employees only view work permit records related to their current employment and need to switch to other employment records to view additional work permit records. We also provided a new option in Admin Center for customers who want to turn off the enhancement and view the data on person level. With the enhancement turned off, they can, as they did in previous releases, view work permit records related to all their employment records after logging into any account corresponding to those employment records.

Changing the Work Permit block to employment-based reduces confusion and improves consistency in how we process and present work permit data.

Configuration Requirements

The enhancement is enabled by default. To disable it, deselect the option Keep the Work Permit block in People Profile user-based at Admin Center > Company System and Logo Settings.

What's Changed

How It Looks Now

The Work Permit block is now employment based by default. It shows just one record, which is related to the employee’s current employment.

SC_30

How It Looked Before

Previously, the Work Permit block was person based. It would show two records related to the two employment records of the employee.

Technical Details

Reference NumberECT-218207
ProductEmployee Central
ModuleEmployee Data
FeatureWork Permits
ActionRecommended
EnablementAutomatically on
Link to Demo 
LifecycleGeneral Availability
TypeNew
Major or MinorMajor
Business Process VariantNot Applicable
Software Version2H 2023
Valid as Of2023-11-17
Latest Document Revision2023-10-13

Related Information

Work PermitsUser-based Work Permit Block Going Universal in First Half of 2024

Supplementary Resources

The following are useful supplementary resources for the 2H 2023 release:

Stay Informed! Second Half 2023 SAP SuccessFactors Release Details. This blog post is dedicated to keeping Partners informed about the 2H 2023 Release.

SAP SuccessFactors 2H 2023 Release Highlights. Note that you might need to register to access the following content: Discover key innovations in the SAP SuccessFactors second half 2023 release.

Monthly Global Delivery Enablement Highlights

Log in to track your progress & complete quizzes