2706395 - 1811 - Employee Central Release Information FAQ

Component 

ID

Feature

Description

Before & After

Additional Information

Business Rules

LOD-SF-EC-RUL

New rules scenario for rules used in the Hire/Rehire process. Applying the new concept of rules scenario EC will add successively more and more scenarios for rules representing specific use cases.

Why is it important? 
It will make the creation of rules for Hire/Rehire use case a bit more easier and less error prone by reducing the selectable base objects to only those that match the use case.

Before: There was no template or guidance given in the UI to create a HIRE/REHIRE related rule.

After: There is now a new rule scenario/template for Employee Central for the Hiring/Rehiring process.

This will reduce the base objects to the only ones possible to avoid any configuration issues in those business rules.

 Business Rules

LOD-SF-EC-RUL

In the 1811 release, the 'Configure Business Rules' tool has been updated to include a new admin UI. This new UI includes a search feature which will provide filter options to find your business rules easier.

Before: There was only limited functionality for Busines Rules in the 'Configure Business Rules' tool for an admin user to search.

After: A new UI was created over the current 'Configure Business Rules' tool to allow admins to have advanced search funcationality.

Implementing Business Rules in SAP SuccessFactors Handbook

KBA: 2710700

Business Rules

LOD-SF-EC-RUL

Before: onSave rules were triggered twice in case of workflow initiation via Take Action (MSS change), first time when the workflow is derived, and second when the workflow is submitted. This resulted in performance issues and a few functional issues like skipping numbers in sequence generation.

After: This has now been fixed and the rules will only trigger once.

Business Rules

LOD-SF-EC-RUL

Before: onInit rules (used in the Hire wizards only) for grid portlets, such as email & phone information were not working when setting field properties for fields

After: This is now fixed

Job Information

LOD-SF-EC-JOB

Before: Previously in the Termination screen, for job relations, the default was to show the individual transfer for the matrix relations.

After: For Q4 2018, we have adjusted the behavior to move the matrix relations to the upper manager as default. This shows in a drop-down list, where you can select the individual transfer.

In addition, you can also select an option to terminate all job relations or move the employee to another manager with one click.

Managing Employment in Employee Central Handbook

KBA: 2710249

Personal Information

LOD-SF-EC-PER

Empty spaces before or after the number are now automatically removed when the number is saved.

Before: No format validation was given.

After: Empty spaces before or after the number are now automatically removed when the number is saved.

Employee Central Master Handbook

Additional Information: KBA = 2717602

Employee Data Imports

LOD-SF-EC-EDP

Before: Currently when using the Import Employee Data tool to import data such as Job Information, the system will create a Job Name with the time stamp and HRIS Element that was selected for import, but there was no way to know (after submitting the job) the reason or description for that import. I.e., if it was Job Information for a country/region or for a specific process or mass load or correction.

After: Now you can add a Job Description to add a little more information or a reason why the data is being imported using the new, non-mandatory "Job Description" field when importing data via Import Employee Data, for example "Data Correction by Carla Grant".

This can be helpful if you have multiple admins spread across the region/globe.

Employee Central Imports Handbook

KBA 2714257

Employee Data Imports

LOD-SF-EC-EDP

Before: Delete operation was not supported from Compensation Information imports

After: 
1. Deleting Compensation records, it deletes its Pay targets, PCRs as well and adjust the end dates. 
2. Deleting same date Compensation records. It deletes its Pay targets, PCRs. It also adjust the sequence numbers, end dates, latest change for other Compensation and their Pay targets, PCRs for that user. 
3. Forward propagation should not happen during delete. 
4. Rules should not be triggered for delete records.

Employee Central Imports Handbook

Additional Information about Deleting Data via Import

Employee Data Imports

LOD-SF-EC-EDP

Based on enhancements made in 1805, Users can download a template specific to a country from the newly introduced “Select a Country” dropdown. On choosing a country, for example, USA, the system will automatically list all the data fields from the Succession data model and the fields configured in the Country-specific data model for the selected country USA.

This request is to allow multiple countries to be selected, so that data fields from SDM corresponding to the selected countries can be downloaded in one attempt.

Employee Central Imports Handbook

Employee Data Imports

LOD-SF-EC-EDP

Before: The switch "suppress updates of Identical records is enabled". When identical records are inserted from Imports for entities like Job Info,personal info,employment info and person info with only the Start date and/or the sequence number changed, there was no validation. We used to insert a new record with identical data.

After: "The switch "suppress updates of Identical records is enabled". If identical records are inserted from Imports for entities like Job Info,personal info,employment info and person info with only the Start date and/or the sequence number changed, then we suppress the data. We will not insert a new record as it does not result in any effective change in history.

Employee Data Imports

LOD-SF-EC-EDP

Before: Previously, users were unable to import both HOME and HOST Assignments in the same import file

After: Importing both HOME and HOST Assignments in a single import is now possible after 1811

Business Configuration UI

LOD-SF-EC-BCI

Before: Previously, if there was a conflict in the configuration between the SDM and the candidate profile XML, the hiring process came to a halt. For example, a field may be configured as required in the Succession Data Model XML > Background Element but is configured as not required in the Candidate Profile XML > Background Element.

After: To prevent a configuration error, a warning is now reported when you save the element information in BCUI, alerting you to the inconsistencies and prompting you to update candidate profile configurations.

HRIS Sync

LOD-SF-EC-HRS

Sometimes users would like to sync data to userinfo-element rather than standard-element.

If the sources have an entity-type, (for example, phoneInfo may have entity-type like Home, Business, etc), the user should indicate which entity type is expected to be synchronized.

Before this fix, the entity-type specified in the data-model was ignored.

Before: When customers sync data to custom userinfo-element rather than standard-element the sync was not validating the value for entity-type against entity-type specified in the data-model xml.

After: This has been corrected

Ad Hoc Reporting

LOD-SF-EC-REP

Before: Previously, fields 'employee-notice-period' and 'name-format-code' are not available in the Person and Employement Export domain.

After: These fields are now available to use in Ad Hoc Reporting

Component 

ID

Feature

Description

Before & After

Additional Information

Workflows

LOD-SF-EC-WFL

With a new permission ‘Manage Workflow Assignments’ a new feature ‘Assign to Me’ is introduced. The users belong to dynamic group with this permission would be able to assign workflow to themselves, to see who in this dynamic group has assigned workflow, as well as remove the assignment from themselves or other members of the dynamic group.

Why is it important? 
In case when a group of users assigned to process the workflow, it could happen that multiple users process the same workflow in parallel. If workflow requires additional alignment and communication (like workflows which go through a worker’s council hearing)  unless we have some indication that this workflow is already in process, another user could start to process this workflow. This enhancement will give a visibility in the process of workflow and increase the efficiency of the team processing workflow.

Before: There was no way to identify whether someone else in the Dynamic Group was working on a workflow

After: Now you can use the "Assign to me" feature to flag that a workflow is already assigned, in the Dynamic Group scenario

Workflows

LOD-SF-EC-WFL

The search on the following screen Global Assignments/Concurrent Employment

• Stalled Workflows – Change Approver
• Auto-delegate
• Manual delegate
• Workflows Foundation Screen
• Contributor
• CC Role
• Dynamic Role Assignment

EC Alerts

LOD-SF-EC-ALR

Often customers create Alerts/Notifications based on the rule that later become obsolete.  After the rule delete/edit there is a need to delete the alerts/notifications that were created before and were not sent yet.

Why is it important? 
Until this enhancement the customers were not able to delete those alerts on their own. Customers would need to open a ticket for Workflow Engineering team to delete those obsolete alerts/notifications that were not sent yet. With this enhancement customers will be able to manage  all alerts/notifications that are yet to be sent via Admin Center. This will significantly improve the efficiency of business users

Before: If there was a need to delete existing Alerts from an instance, this could only be done as an "all or nothing" scenario, via Engineering script

After: Now customers can manage all Pending Alerts that are created in the instance. Alerts can either be individually deleted, or on mass.

Component 

ID

Feature

Description

Before & After

Additional Information

Position Management

LOD-SF-EC-POS

A new version of the rule function ‘Is Position below User's position in Hierarchy’ is available. This rule function can be used when creating new positions e.g. as lower-level position in the position org chart.

Now 2 rule functions exist:

• Is Position Below User's Position In Hierarchy (Old Version)
• Is Position Below User's Position In Hierarchy (New Version)

Before: The old version of this Rule Function cannot be used to create new positions - for example, when adding lower-level positions in the position org chart.

After: The new version of this Rule Function can be used to create new positions - for example, when adding lower-level positions in the position org chart.

Position Management

LOD-SF-EC-POS

Before: It was possible to enter a date for BizX Daily Rules Processing Batch, which would then allow the Automated Daily Hierarchy Adaption part of the job to check the entire position hierarchy from a certain date, and correct the reporting hierarchy. This would lead to performance issues with the job running for large amounts of time, and this was never the intention of the job originally.

After: Automated Daily Hierarchy Adaption is now only performed on the date which the job is executed on

Position Management

LOD-SF-EC-POS

Before: Incorrect data could be saved but the internal ID of the position was displayed.

After: The position validity is being checked and a corresponding message shown.

Component 

ID

Feature

Description

Before & After

Additional Information

Company Structure Overview

LOD-SF-EC-CSO

A new Favorite (star) icon is added to the UI when the Company Structure, Entity Type and Object have been selected.

Before: This feature wasn't available

After: It is possible to create and manage favorites in your company structure overviews.

Component 

ID

Feature

Description

Before & After

Additional Information

Service Center

LOD-SF-EC-SRV

It is now possible to use the employee details replication from Employee Central to C4C through SuccessFactors Integration Center.

Before: Previously, you could replicate employee data by integrating SAP Hybris Cloud for Service with SuccessFactors Employee Central Service Center using SAP HANA Cloud Integration.

After: Now, as an alternative you can also use the employee details replication from SuccessFactors Employee Central to SAP Hybris Cloud for Service through SuccessFactors Integration Center. To achieve this you must contact your PS and must also select some RBP permission settings to enable Integration Center.

Service Center

LOD-SF-EC-SRV

Before: Load time for AskHR tickets were significantly longer

After: In Employee Central Service Center application on the Tickets Overview page by default you can now see the first 5 tickets. If you want to see more you have to click on the show more button.

In case less than 5 tickets are available for this employee you will see all tickets (max. 5) immediately. The new behavior will help your employees to focus on the most relevant/ recently updated tickets first and contributes to a better performance of the application.

Component 

ID

Feature

Description

Before & After

Additional Information

Time Off

LOD-SF-EC-TIM

From Q4 onwards new time off customers get only this new user interface. Existing time off customers get an upgrade option to switch the new UI on. There is a transition phase till mid-2019 where the old time off UI can be used. Mid 2019 there will be a mandatory switch.

Benefits of the new time off leave request UI:

• new, modern, mobile-app like user interface
• possibility to create recurring absences now provided for employees, too
• split and delimit of absences now provided for employees, too 

Time Off

LOD-SF-EC-TIM

Before: Prior to 1808 release, TimeAccountSnapshot entity is classified as restricted / internal cannot be used publicly in API

After: TimeAccountSnapshot entity has been added to public namespace and is now available for public usage in API

Implementing Employee Central Time Off

KBA: 2711536

Time Off

LOD-SF-EC-TIM

This is an enhancement for data protection and privacy. It is now possible to block time account details (time account postings) for permanent time accounts. This means you can set a time period where users don´t see the single time accounts posting in the time admin workbench for a permanent time account (time accounts without end date).

Before: Time account details for permanent time accounts could not be blocked

After: With this feature it is now possible to block time account details for permanent time accounts, independently from the time account object

Component 

ID

Feature

Description

Before & After

Additional Information

Time Sheet

LOD-SF-EC-TMS

Allows a flexible deduction of breaks starting from the recorded working time of the employee

Helps to adhere to lots of country regulations where employees are not allowed to work longer than 6 hours without a break

Before: Only “fix breaks” are possible in EC Time. Fix breaks are defined in the workschedule with fix clock times like for example from 12:00 – 13:00. When an employee starts work on 11:00 the break gets generated already after 1 hour of working time.

After: A break gets automatically generated after a configured duration of working time has passed.

For example: break deduction of 30 minutes after 6 hours of working time and another 15 minutes after 9 hours of working time.

Implementing Employee Central Payroll Time Sheet

KBA: 2711760

Time Sheet

LOD-SF-EC-TMS

Time Sheet Object provides more information on the data that is contained within a time sheet. These new parameters are:

• Absences: Is set to yes when at least one absence is recorded in the time sheet
• Manual entries: Is set to yes when at least one manual time recording (attendance, break, on call or allowance) is recorded in the time sheet
• Imported entries: Is set to yes when at least one via the “external time data service” imported time record (attendance, break or on call) is in the time sheet
• Generated entries: Is set to yes when at least one system generated time record (attendance or break) is in the time sheet
• Time Recording Method: Contains the time recording method of the employee in the time sheet period (positive, negative or overtime)

Before: This information was not available in the time sheet

After: The time sheet object contains new fields giving more information on the time sheet content. This fields can be used in reporting as a selection for example on time sheets where the planned work schedule time is not fully covered by recorded times.

Component 

ID

Feature

Description

Before & After

Additional Information

Advances

LOD-SF-EC-AAD

Before: One common rule for entire advances feature

After: Users can now create multiple rules for each advance

Implementing and Configuring Advances in Employee Central

• Defining Eligibility
• Setting Up Advances Eligibility Rule

Global Benefits

LOD-SF-EC-GBF

Before: There was limited functionality to add hyperlinks to benefits. Hyperlinks were only available while employee is enrolling in a benefit.

After: Employees will have access to benefit information and provider directories before enrolling to make an informed decision, and after enrolling, to assist employees with making changes when a life and/or work event occurs.

In the People Profile page, generic hyperlinks may be added for those benefits not configured in the system. This provides an access point to 3rd party providers, Jam, etc.

Global Benefits

LOD-SF-EC-GBF

A Framework in saving plans to handle Proration of eligibility amount.

The proration can be for:

• new employees
• Current employees that wants to make changes to their contributions.
• Life event changes - employee can move from employee to family or vice verse

Before: This feature did not exist prior to 1811

After: New or enrolled employees are able to change their per pay period contributions at any time during the benefit year, with an option to cap their annual contributions. The system determines how many pay periods are remaining in the plan year, and offers the legally mandated IRS choices to the plan participant based on their health insurance enrollment tier.

Global Benefits

LOD-SF-EC-GBF

Before: This feature did not exist priot to 1811

After: iOS users will have the ability to view and submit eligible benefit claims, see status of submitted claims from the mobile app. The user can take a picture of a receipt, or submit a receipt already on the mobile device. Employee may also view claims history submitted. This feature will improve user experience and it will provide an easier access to proves reimbursements or claims on the go.

Component 

ID

Feature

Description

Before & After

Additional Information

Suite Integration

LOD-SF-EC-INT

For customers using the standard integration between Recruiting, Onboarding, and Employee Central, you can now directly add concurrent employment in the Managing Pending Hires screen. This will pull data directly from Onboarding for the recruit to avoid additional data entry. The HR admins can then review, edit, and save the concurrent employment in Employee Central.

Before: There was currently no support for Concurrent Employment in Manage Pending Recruits.

After: With this new feature implementation an additional "Add CE" button will be displayed in the Manage Pending Recruits Screen based on information from ONB1.

On click of the "Add CE" button users will navigate automatically to the "Add New Concurrent Employment" page with information from ONB1 pre-populated on the screen. Users can choose to review, edit and save the concurrent employments in EC.

This feature will work with based on the standard integrations set up between RCM, ONB1 and EC

Suite Integration

LOD-SF-EC-INT

Before: Internal Hire start date, "When do you want the changes to take effect?", for any user was current date, and not the hire date from RCM or ONB.

After: Internal hire date of the user will now be the same as the job start date coming to EC from RCM or ONB.

Suite Integration

LOD-SF-EC-INT

Before: While executing the Transfer for a Manage Pending Hire, the direct reports were transferred but reassigned to a new manager on the transfer date +1

After: The transfer date of direct reports will be same as hire date of Internal hire user. Behavior will also be same in case of Internal Hire user being in Job Relationship of other users. Job Relationship Transfer to higher manager or Other manager will be effective on the hire date of Internal Hire user

Suite Integration

LOD-SF-EC-INT

Before: If a candidate being hired from ONB to EC (or RCM to EC) had Dependent Global Info, after the hiring was completed, the Dependents Global Info was not saved.

After: Dependents Global Info will be retained as per the data provided by candidate/onboardee.

Component 

ID

Description

Before & After

Additional Information

People Profile UI

LOD-SF-EP-PP3

With this enhancement, a customer will be able to encrypt the selected user ID in the URL when viewing People Profile. For example, customers will be able to prevent the display of personal identifiers of their employees when using Employee Profile.

This option is enabled via Provisioning setting "Encrypt User ID in URL"

People Profile UI

LOD-SF-EP-PP3

Further improvements to the display of information in the Compensation section of the People Profile, including:

• Use of a responsive table to display pay components in a grid layout in edit mode
• Merging of Total Compensation History block into the Compensation Information block
• Use of a carousel to display Total Compensation History graphics

People Profile UI

LOD-SF-EP-PP3

Before: Compensation graphs not displayed correctly

After: Fixes a display issue that the Compensation Graphs in People Profile were not visible or not user friendly.

People Profile UI

LOD-SF-EP-PP3

Before: Application error occurs when entering effective date

After: New record can be created without error - Fixes an issue in  he configuration of the Succession Data Model that caused application errors in the Job Information record.

People Profile UI

LOD-SF-EP-PP3

Before: Picklist entry incorrectly selected without user input

After: Picklist working as expected - This fixes a problem that occurred when new options were added to picklists on the people profile Formal Educaton section. When users then went to select an option in the picklist, the new entry was highlighted without being selected.

People Profile UI

LOD-SF-EP-PP3

Before: Error occurs when selecting person as Incumbent of Parent Position

After: Application error no longer occurs - Fixes an issue where the system threw an application error for changes to the Incumbent of Parent Position because the Reporting Line was used as leading hierarchy.

People Profile UI

LOD-SF-EP-PP3

Before: Profile not loading when viewing another user's profile

After: Profiles are displayed correctly - Resolves an issue in People Profile where the page was not showing up any data when users logged in as "sfadmin" and then visited someone else's profile.

People Profile UI

LOD-SF-EP-PP3

Before: Supervisor field drop down displayed blank job title

After: Job title displayed correctly - Fixes an issue in People Profile where the Supervisor field drop-down in the Job Info subsection did not show Job Title like it did in v12 Profile.

People Profile UI

LOD-SF-EP-PP3

Before: Only last effective dated record is displayed

After: All records are displayed in Change History - Fixes an issue where not all the historical data records were present in the Change History section in the People Profile.

People Profile UI

LOD-SF-EP-PP3

Before: Global Information (country specific fields) not displayed in Personal Info

After: Data displayed as expected - Fixes an issue that caused country-specific Global Information data not to display in PP3 user profile or on the history tab even though data is entered.

People Profile UI

LOD-SF-EP-PP3

Before: When editing or changing a record in Org Info history, an application error occurs when changing Company field

After: Error no longer occurs - Fixes an issue that was causing the system to throw an error when the company value was changed from Employment Information > Organization Information > History > Edit/Insert New Record.