1.

Centralized Services Support Saving Changes on History UI for Dependents

Centralized services are enabled by default to support saving changes on the History UI for dependents.

With Centralized services enabled, saving changes on the History UI of the Dependents block in People
Profile comes with the following benefits:

Forward propagation

When you use the Insert New Record option, the changes are propagated to future records until a future
field value is different from the original field value or there is a data gap.

When you use the Edit option or the Delete option, the changes are not applied to any future records.

Data validation

When you choose the Insert New Record option to add a dependent or update data for existing
dependents, you can only set a new start date for the changes.

Enhanced onSave rules with Dependents or Dependents Model as the base object

For rules assigned to Person Relationships: You can now define Then statements to set field values for
Person Relationships and dependents' all other entities, for example, Biographical Information.

For rules assigned to Personal Information, Global Information, Biographical Information, Address
Information, or National ID Information: You can now define Then statements to set field values only for
the entity to which the rule assigns.

Data access period

The Data Access Period Settings option now applies to the data of dependents. The option controls your
access to historical data of dependents, including their Address Information and Personal Information.
You're only able to access and edit the data that is effective-dated within the set period. For more
information about this option, see Setting Up Data Blocking for Effective Dated Objects (Employee
Central Objects).
Here's a screenshot of the History UI for dependents.

History UI of the Dependents block

Employee Central using Centralized services brings consistent system behaviors, validations, and
functionality across UIs, imports, and APIs.

Configuration Requirements

As an administrator, if you need to opt out of the feature, deselect the setting for this feature Company
System and Logo Settings Enable Centralized Services for Dependents (Applicable for saving changes on
History UI).

2. Centralized Services Support Final Approval of Workflows for Dependents

When users update dependents' information on the Editing UI and the triggered workflow is finally
approved, data changes to the record are now saved on Centralized services.

This enhancement brings the following benefits:

Data consistency

After a record is added, the History UI shows that the record is last updated by the person who added
the record instead of the workflow approvers.

After a record is updated, the History UI shows that the record is last updated by the workflow initiator
instead of the workflow approvers.

Data quality

When you edit data for a dependent, for example, personal information, and the triggered workflow is
approved, start dates for the dependent's other types of information are now automatically aligned. This
alignment also applies to the employee's other dependents.

This enhancement improves data quality and user experience by ensuring consistent UI behaviors and
preventing data issues when creating and editing data for dependents.

3. Non-Eligible Dependents Are Not Allowed To Enroll Into Insurance Plans

When you import the list of dependents for enrollment and if there are non-eligible dependents
included in the CSV file, then the system won't allow you to import.

The restriction applies when you're trying to import the dependents information. When you import a
CSV file containing non-eligible dependents for enrollment, then the system displays an error with the
details of the non-eligible dependents.

We've enhanced this feature so that you can import only the eligible dependents for enrollment into
insurance plans.

4. Deprecation of Consolidated Dependents Import

The Consolidated Dependents import 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.

Milestone Date Definition

End of June 2, The deprecation milestone after which SAP stops enhancing a
 Milestone Date Definition

Development 2023 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 November The deprecation milestone after which SAP does not fix bugs or
Maintenance 17, 2023 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 June 2, The deprecation milestone when a feature is no longer available

2024 for productive use. You should now be using an alternative
method for your business scenario.

Deprecation Details

We're deprecating Consolidated Dependents import because it's not supported by Centralized services.
To import data for dependents, we recommend using separate import templates, including the Person
Relationship template, Personal Information template, National ID Information template, and other
templates for importing personal details about dependents. The reason is that all these imports are
supported by Centralized services to bring you better data quality and more consistent behaviors.