/support/notes/service/sap_logo.png){kind=logo}
SAP Knowledge Base Article - PublicSymptom
- Admin Opt-in/Admin Opt-out Centralized Services Switches can be enabled or disabled from: Admin Center > Company System and Logo Setting
- List of high impact Centralized Services/ Service Layer issues around MSS (Manager Self-Service),Termination UI and Internal Hire.
Environment
SAP SuccessFactors Employee Central
Resolution
Following is list of high impact Centralized Services/ Service Layer issues around MSS (Manager Self-Service),Termination UI and Internal Hire.
Please contact support for any questions you have with Centralized services issues in 1H 2023 by following the steps mentioned in 3086778
| Centralized Services Settings | Description | Current Status |
| Termination UI | Basic Termination Business Rule to create/delimit/delete pay components stopped working with switch 'Enable Centralized Services to Save Changes on the Manager Self-Service UI for Termination Details' enabled | This is expected behavior. 1. Cross-entity rules where Employment Information is the source element with Compensation Information, Recurring Pay Components, Non-Recurring Pay Components, or Job Relationships as the target element are no longer supported. From employment information, a cross entity rule to only Job Information is supported. 2. Cross-entity rules where Job Information is the source element with Employment Information, Compensation Information, Recurring Pay Components, Non-Recurring Pay Components, or Job Relationships as the target element are supported using the Cross-Entity Rules rule scenario. Please be informed that you have to adopt this behavior change and re-enable the centralized services setting. Please refer KBA 3338090 - Cross-Entity Business Rules using Employment base object to Compensation Info, Recurring Pay Components, Non-Recurring Pay Components, or Job Relationships is not supported |
| Termination UI | For termination, there is a workflow rule in Employment Info with no approvers and another workflow rule in Job information with approvers. Upon termination, customer's expectation was to trigger the rule placed in Job Information, but the one placed in Employment Info got triggered. | This is expected behavior. Preference is always given to an Employment Information workflow configuration. If no Employment Information workflow configuration is found, then the system checks whether a Job Information workflow configuration exists and uses that configuration to trigger the workflow. |
| Termination UI | onSave rules on Job Information with the Rule Scenario "Trigger Cross-Entity Rules" are now triggered. | This is expected behavior. Cross Entity onSave rules on Job Information with the Rule Scenario "Trigger Cross-Entity Rules" are now triggered. As a workaround, disable the rules from being triggered by using the Rule Context: Termination UI. More details can be found in the KBA - 3342687 - Job Information Cross Entity Rules are now Triggered when Terminating a User with Centralized Services. |
| MSS - Job,Compensation | FTE is set to Zero when changes are made in Job information via Take action | Fixed and patched (PTCH-41196) - b2305p7 (12-Jun-23 Preview) After the final approval in a Job Info workflow with job information changes, the full-time equivalent (FTE) value was set to zero (0), instead of using the FTE value from the previous record. This is fixed now. In this case, the value of FTE is retained as per the previous record. |
| Termination UI | Pay Component is deleted unexpectedly when terminating a user with centralized services. | Fixed and patched ( PTCH-41464) - b2305p13 (24-Jul-23 Preview) This issue happened when there is a cross-portlet business rule with Job Info/Job Info Model as Base object and the rule is meant to delete a Pay Component onSave. Instead of deleting only the specific Pay Component, system deletes all Pay Components. This is fixed now. In this case, only the specific pay component will be deleted. |
| MSS - Job,Compensation | Event & Event Reason Blank in Custom Email Notification post 1H 2023 Release | Fixed and patched (PTCH-41422) - b2305p13 (24-Jul-23 Preview) In custom document generation workflow notification, both Event and Event Reason return blank. This is fixed now. In email notifications for workflows for CC participants, the EVENT and EVENT_REASON tags are now displaying correctly with Centralized services enabled. |
| Internal Hire | Internal hire processed from Manage pending hire(MPH) onboarding not removed from Manage pending hire list after internal hire process | Fixed and patched (PTCH-41464) - b2305p13 (24-Jul-23 Preview) During Internal Hire, when making NO changes to an Employment Information and creating a workflow and later approving it is not yielding the expected results for an Internal Hire candidate. Also, the candidate is not disappearing off the MPH listing page. This is fixed now. In such cases, Workflow approval works fine and the candidate disappears from the MPH listing page. |
| MSS - Job,Compensation | Error on updating any field via Take action (MSS UI), below error is shown when Job Info and Compensation Info are selected. Error: “Validation of recurring pay component failed: Pay component type is null for pay component with external code ABC | Fixed and patched (PTCH-41365) - b2305p9 (26-Jun-23 Preview) There was an issue where only successful payloads were looped, resulting in errors on pay component type. This is fixed now. |
| Internal Hire | Deleted Pay Components re-appear in Workflow for Internal Hire from MPH | Fixed and patched (PTCH-41464) - b2305p13 (24-Jul-23 Preview) Pay Components that are removed/updated in MPH are reappearing on the workflow page when an Internal Hire is onboarded. This is fixed now. In such cases, Deleted pay components are removed. |
| MSS - Job,Compensation | MSS when changing multiple entites for example Job and Comp, changes made by onSave rules in Compensation Information are not taken into account when Job Information onSave Rules are processed - impacting Workflow and Event Reason Derivation |
This is expected behavior. |
| MSS - Job,Compensation | Error on changing Position on Job Information through Take action(MSS action) Error Message: "Unexpected state of the system. If problem persist please contact administrator" | Fixed and patched (PTCH-41348) - b2305p13 (b2305p15 (7-Aug-23 Preview) When executing matrix relation sync, when the matrix relation picklist does not have any matching value in the job relation it does not execute matrix relation sync and shows a system error. This is handled now to show a proper readable message. The issue can be fixed by correcting the picklists. You can check it in the Check Tool > Position Management > All values available in the Position Matrix Relationship Picklist are also available in Job Relationship Picklist. (PositionMatrixPicklistCheck). |
| MSS - Job,Compensation | Pay Components are removed/deleted when internal hires are recruited through Manage Pending Hire. | Fixed and patched (PTCH-41464) - b2305p13 (24-Jul-23 Preview) For internal hires/recruits onboarded via Manage Pending Hire UI unchanged pay components are deleted from Compensation Information. Same issue as for Termination, so PTCH-41464 caters for both Termination and Internal Hire/MPH scenario. Pay component recurring Workflow attributes created during Termination/Internal Hire are only the changes in the Pay component recurring. When there are no changes no attributes related to Pay component recurring are created. To fix this, we loaded the Pay component recurring from the previous timeslice for persistence. |
| Termination UI | Employee Status field is not evaluated correctly in termination rule | Fixed and patched (PTCH-40931) - b2305p6 (5-Jun-23 Preview) A termination rule with base object as Employment details model to check if the Employee Status is equal to T and then trigger the workflow. However, workflow is not triggered as rule trace shows that system is evaluating the Employee Status as A instead of T. This is fixed now. |
| MSS -Termination | When user is on a LOA with RTR config unassigning Position details, validation error appears on termination "Position is a required field and cannot be blank" when CS switch "Enable Centralized Services to Save Changes on the Manager Self-Service UI for Termination Details" is enabled |
Will be enhanced with 2H 2023 release. Workaround available. |
| MSS - Job,Compensation | MSS Identical Record Suppression is not displayed when several entities are selected, but there is no change to Job Information |
Will be enhanced with 2H 2023 release. |
| MSS - Job,Compensation | Error on saving Job Information via Take action / Edit (pencil icon). Error message: "Unexpected state of the system. If problem persist please contact administrator." | Planned to be enhanced with 2H 2023 release. Workaround available. Issue is : Unable to terminate employee with an active Leave of Absence as system shows an Error: "Position is required field and cannot be blank" Workaround: Update the Actual Return Date of the absence to before the date of the Termination. |
| MSS - Job,Compensation Termination UI | XML workflow: Catch All workflow triggered for Termination - CS1H2023 |
Will be fixed with 2H 2023 release. Workaround available. |
| MSS - Job,Compensation | End Dated Payments: Multiple Compensation Information Records Created When Adding Recurring Pay Components With Same End Date | Fixed and patched (PTCH-41080) - b2305p6 (5-Jun-23 Preview) When defining end dates for Recurring Pay Components in a Compensation Information record (Take Action > Change Job and Compensation Information > Compensation Information), if two or more Pay Components have the same end date defined, the system creates multiple records for the day after the end date, but only one of these records (the '1 of 2' record) shows the Pay Components being deleted; the other record is empty with no changes. This is fixed now. |
| Termination UI | CSF employmentDetails rules are not triggering during termination with CS switch enabled "Enable Centralized Services to Save Changes on the Manager Self-Service UI for Termination Details" | Fixed and patched (PTCH-41313) - b2305p8 (19-Jun-23 in Preview and 22-Jun-23 in Production). CSF employmentDetails rules were not triggered during termination with CS switch "Enable Centralized Services to Save Changes on the Manager Self-Service UI for Termination Details" enabled. This is fixed now, rules configured on CSF employment details are triggered during Termination UI Save action. |
| Internal Hire | Error when defining end dates for pay components in Compensation information or while saving end-dated payments in first Compensation Information time slice | Fixed and patched (PTCH-41080) - b2305p6 (5-Jun-23 Preview) Multiple Pay component recurring having same payment end date was not handled. Duplicate Comp slices were created in this case on new date. It is fixed now and in such cases duplicates are no longer created. |
| General | Rule to get Pay component value for context user is getting the newly changed value instead of previous value | This is expected behavior. Documentation has been updated Values for Left Expressions In rules, if you use the context > current user navigation system will pick the current payload value with Centralized Services. |
| MSS - Job,Compensation | Error on save of Compensation Information "Could not find corresponding compensation row for start date <date>" When setting effective date with a rule | Fixed and patched (PTCH-41449) - b2305p6 (b2305p11 (10-Jul-23 Preview) On Save rules for the Compensation Information which are setting the effective start date of the entity is throwing a validation error. error: Could not find corresponding compensation row for start date <date> This is fixed now. Added logic to support onSave Rules for CompInfo and Pay Component Recurring setting correct start date of the Pay Component Recurring objects after rule processing. |
| Termination UI | Basic Scenario onSave Rules from Job Information which Update Another Entity are Incorrectly Triggered During Termination with Centralized Services | Fixed and patched (PTCH-41596) - b2305p15 (7-Aug-23 Preview) With Centralized Services for Termination UI, Basic scenario 'onSave' Job Information rules (source) which update Compensation Information, Pay Component Recurring, Pay comp non-recurring and job relationship were being triggered. This should not be triggered as per expectation as only the rules with Cross Entity Rules scenario should work. This is fixed now. |
| MSS - Job,Compensation | Warning Message - You have selected a deduction pay component after 1H release 2023 | Fixed and patched (PTCH-41352) - b2305p9 (26-Jun-23 Preview) A validation was introduced in 1H 2023, to prevent the use of a Deduction Pay Component and also the expectation was to change isEarning from 'No' to 'Yes' (via script). Due to widespread impact, this validation was reverted and patched. This Warning Message - 'You have selected a deduction pay component', will no longer appear. |
| Following are some of the open issues which are being internally discussed actively. This KBA will be updated once we receive more information. | ||
| Centralized Services Settings | Description | Current Status |
| MSS - Job,Compensation | PayComponentRecurring not updated using rule when manager update direct reportees compensation information - CS1H2023 | Engineering team has fixed with 2H 2023 (b2311) release in preview environment on 20th Oct 2023 and in production environment on 17th Nov 2023 KBA 3349892 - Compensation information not updating pay component using rule when manager update or approve the same - 1H 2023 |
| MSS - Job,Compensation | HTML codes displayed in raise message rules, when CS is enabled. |
|
| MSS - Job,Compensation | Forward Propagation reverting a change when Enable Centralized Services to Save Changes on the Manager Self-Service UI for Change Job and Compensation Info is enabled | This issue is fixed with 2H 2023 (b2311) release which will be available from on 20 Oct 2023 in Preview and from on 17 Nov 2023 in Production Environment. 3347839 - The Forward Propagation reverting a change when Enable Centralized Services to Save Changes on the Manager Self-Service UI for Change Job and Compensation Info is Enabled. |
See Also
3342189 - Field X is a required field and cannot be blank error when Terminating a User
3358988 - Job to Position sync not triggered when changes to job info made through cross-entity rule and Centralized Services switch enabled - CS1H2023 - Planned to be fixed with 2H 2023 (b2311) release in preview environment on 20th Oct 2023 and in production environment on 17th Nov 2023.
3365149 - All matrix relationships not syncing to job relationships when changing the position from MSS UI - CS1H2023
3339502 - Position is not removed from Job History when 'Deactivate position' as 'Yes' with 'Enable Centralized Services to Save Changes on the Manager Self-Service UI for Termination Details' option enabled - CS1H2023
Keywords
Centralized Services/ Service Layer issues, CS1H2023, CS2H2023 , KBA , LOD-SF-EC , Employee Central , LOD-SF-EC-JOB , Job Information , LOD-SF-EC-CMP , Compensation Information & One-Time Bonus , Problem
Product
SAP SuccessFactors Employee Central all versions
/support/notes/service/facebook.svg)
/support/notes/service/twitter.svg)
/support/notes/service/youtube.svg)
/support/notes/service/linkedin.svg)
/support/notes/service/instagram2.svg)