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

Cross-entity Business Rules using the Employment Information base object to Compensation Information, Recurring Pay Components, Non-Recurring Pay Components, or Job Relationships are ignored.

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental." 

• SAP Successfactors HXM Suite 
• SAP Successfactors Employee Central

Centralized services now supports changes made to an employee's termination information record when changes are made in the Manager Self-Service (MSS) Take Action > Terminate menu and Termination Details Import using Import Employee Data.

With this feature, there are a few behavior changes for the Cross-entity rules:

• Employment Information as Source Element (Deprecated / Unsupported)
• 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.
• Note: This means that some rules in your system may need to be checked and updated, as well as new rules created as the unsupported rule results will be ignored. Please make the changes to these rules by June 2nd, 2023.
• For more information, refer to the Cross-Entity Rules with Centralized Services.

Please Note: If you need more time to adjust your business rules, you can turn off the ‘Enable Centralized Services to Save Changes on the Manager Self-Service UI for Termination Details’ and/or ‘Enable Centralized Services for Termination Details (Applicable only for data imports from UI and API)’ setting in Company System and Logo Settings. However, please note that this feature will be universal in 2H 2023.

Example 1: Basic Employment Details Rule with Set Command for Compensation (Pay Component Recurring)

• Please see the example below of an existing rule which will need to be changed as it will no longer be supported, and the rule result will be ignored:
  
  

• Here is an example (below) of the same rule using the Job Information Model base object. This is the recommended/supported approach to configure the rule. To create the new rule using the Rule Scenario with Job Information Model as the base object, navigate to Configure Business Rules > Create New Rule > Employee Central Core > Trigger Cross-Entity Rules.

  

Example 2: Basic Employment Details Rule with Create Command for Compensation Information:

• Please see the example below of an existing rule which will need to be changed as it will no longer be supported, and the rule result will be ignored:
  This is a Basic Employment Details Rule with Create Command for Compensation Information.
  
  
• This rule will be ignored as it is a Basic Rule. In addition
  • 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.
  • This means you will need to recreate the rule with Job Information Model as the Base object with the Scenario > Cross Entity 

• Please note that Cross-entity rules with Job Information or Compensation Information as the target must only use the Set command, which always results in the creation of a new record. Do not use the Create command to create a new record.
  This is documented, for more information, refer to the Cross-Entity Rules with Centralized Services.

• Here is an example (below) of the same rule using the Job Information Model base object. This is the recommended/supported approach to configure the rule. To create the new rule using the Rule Scenario with Job Information Model as the base object, navigate to Configure Business Rules > Create New Rule > Employee Central Core > Trigger Cross-Entity Rules.
  

Example 3: Basic Job Information Rule with Create Command for Compensation Information:

• Please see the example below of an existing rule which will need to be changed as it will no longer be supported, and the rule result will be ignored:
  This is a Basic Job Information Rule with Create Command for Compensation Information.

• Please note that Cross-entity rules with Job Information or Compensation Information as the target must only use the Set command, which always results in the creation of a new record. Do not use the Create command to create a new record.
  This is documented, for more information, refer to the Cross-Entity Rules with Centralized Services.
  
  
  
• When you try to migrate this rule you will see a warning for this create setting as per the below screenshot:
  
  
  
• When you select Submit and finish migrating the Rule Scenario, then on view of the rule you will see the following error:
  
  
  
• If you select the "Edit Rule" option you can then edit the rule to use the supported Set command instead of the Create command.
  
  
• Here is an example (below) of the same rule using the Job Information Model base object with the Scenario> Cross-Entity:
  

FAQ: 

Q: How do I know if our rules are impacted?
A: There may be many rules configured like this in your instance, but a change is only required in those rules which are trigger in your Data Model/Manage Business Configuration. 
These rules can be highlighted by following the below steps.

Manage Business Configuration

1. Navigate to Manage Business Configuration > jobInfo
2. Review the list of onSave Business Rules
3. For any rules which are cross entity, review if the rule is created with the Basic Scenario and is updating information in a different HRIS Element.
4. Once you have highlighted the list of rules that need to be updated you can migrate the rules using the “Change Scenario” option on the rule.
5. Repeat steps 1-4 for onChange rules
6. Repeat steps 1-5 for employmentInfo

Q: How do I know where the Create, Set or Delete command is supported?
A: Please review the corresponding tables in the guide which highlights in what rules the Create, Set or Delete command can be used. The tables will show for which Base Object and Target Object Combination the commands can be used for:  Cross-Entity Rules with Centralized Services

Q: Do I have to recreate my rule or can I migrate them?
A:  The rules can be either migrated using the “Change Scenario” button on the Business Rule or they can be recreated. Please note if you recreate the rule you will need to update the rule trigger to point to the new rule.

Q: How do I identify the Source Element of the Rule?
A: The Source Element is also known as the Base Object of the rule. This can be found in the Parameters section of the Rule or in the “Base Object” column in Manage Business Configuration for the rule trigger.

Q: How do I identify the Target Element of the Rule?
A: The Target Element of the rule, is the Element that is being update in the Then conditions of the rule.

Q: If we migrate a rule using "Change Scenario" option on the rule, why can I only select Model Base Objects?
A: Model Base Object Rules are the recommend Base Object for Business Rules. Due to this the "Change Scenario" only offers Model Base Object for Business Rules that are being migrated.

Q: Can I use the Assigned Column in Configure Business Rules to determine if the impacted rules are assigned? 
A: The impacted rules will be created with the Basic Rule Scenario, this scenario is not respected in the Assigned Column and will not show if a Basic Rule is assigned or not, this is one of the benefits of ensuring your rule is created on the correct scenario.

Q: Will all impacted rules be visible in the check tool for rule Migration? 
A: No, not all impacted rules will be available in the check tool for rule migration. The check tool, currently only highlights rules for specific target Scenarios:

• Time Off: Rules
• All rules that use the object Time Account Type are assigned to an application-specific rule scenario. (TimeAccountTypeNoBasicRules)
• All rules that use the object Time Type are assigned to an application-specific rule scenario. (TimeTypeNoBasicRule)
• Employee Central Core: Rules
• All rules for workflows are assigned to an application-specific rule scenario. (WorkflowsNoBasicRules)
• All rules for event-reason derivation are assigned to an application-specific rule scenario. (EventReasonDerivationNoBasicRules)

• Cross-Entity Rules with Centralized Services
• What's New Viewer: Centralized Services Support Manager Self-Service Changes to Termination Details
• What's New Viewer: Centralized Services Support Termination Details Imports

2305, EC, Employee Central, Centralized Services, Termination Details, Cross-Entity, Cross Portlet , KBA , LOD-SF-EC-EMP , Employment Information (Employment Details) , LOD-SF-EC-CMP , Compensation Information & One-Time Bonus , How To