3280407 - Manual Mass Change of Basic Rules to Application-Specific Scenarios – FAQ

From the 2H 2022 Release a new enhancement includes Manual Mass Change of Basic Rules to Application-Specific Scenarios.

You can now change Basic rules to application-specific rule scenarios for several rules at once.

This is now possible for rules that can be converted to application-specific scenarios of the following modules:

• 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)
    
    Note
    As in the previous release, a warning is raised whenever you try assigning a new basic rule scenario to Accrual rule, Hire Rule, Interim Update Rule, Period-End-Processing Rule, and Take Rules.

The current warning message will be converted into an error in a future release.

• 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)

For full details on this enhancement please review the following page:

What’s New Viewer: Manual Mass Change of Basic Rules to Application-Specific Scenarios

SAP SuccessFactors: Employee Central

FAQ

Q: Why can’t I see the Quick Fix Option in the Check Tool?
A: To see the Quick Fix option in the Check you must have the prerequisite permissions, the following Administrator  Check Tool permissions:

• Access Check Tool

• Allow Configuration Export

• Allow Check Tool Quick Fix

Q:When the rule is migrated why is the “updated by” data in the Rule updated?
A: In order for the migration to be completed the rule scenario must be updated this requires a change to the rule and so the “updated by” audit data will be updated. The Admin User who executed the quick fix as part of the migration check will show as the user who updated the rule. The “updated on” information will show the date the Quick Fix was performed.

Q: Can we revert to the original “updated by” data in the Rule after the migration has completed.
A: No, once the migration has completed for the rule, the original “updated by” data from before the migration can not be reverted and displayed.

Q: Why are some rules not able to be migrated by the check tool checks?
A: This can occur to various reason primarily the system is unable to confirm the correct basic scenario or a configuration issue exists with the rule. In order to migrate the rule, you must manually review the rule in Configure Business Rules, resolve any configuration issues if they exist and manually convert the rule scenario.

Q: Our business rules set both Event Reason and Workflow derivation, why is one of the set conditions being removed if we try to migrate the rule?  
A: It is not a supported configuration to have both Event Reason and Workflow Derivation in the same business rule. Event Reason and Workflow Derivation rules must be configured separately, and it is recommended to use the dedicated rule scenario for each one.
If you have a rule which contains both Event Reason and Workflow derivation, we recommend not migrating your rule via the check tool until you can review and create a separate rule for each derivation.

• More details on the Event Reason Deviation logic can be found in the following section of the guide:
  Implementing Employee Central Core: Event Reason Derivation Business Rules
• More details on the Workflow Reason Deviation logic can be found in the following section of the guide:
  Implementing and Managing Workflows: Triggering Workflows with Business Rules

Q: What happens if we don't migrate our rules? 
A: In the future it is planed to remove the basic scenario from instances, however in which Release this will occur if not yet confirmed. It will be clearly documented in the What's New Viewer prior to the Release when this will occur. As for the 2H 2022 Release this will not happen. You therefore are able to make these changes at a time that suits your business need. Not all scenarios are currently offered under this check, but for those which are covered, we do recommend that you begin to change scenario in this Release to get the best experience and validation with the rules. 

Release Issue: 

Please be aware of the following issue with the Migration Check Tool. 

• EC Alert and Notification Business Rules are currently being recommend to migrate to the Rule Scenario "Trigger Workflows" which is incorrect. They should be migration to the Rule Scenario "Generate Alerts".
• The issue will be fixed via patch PTCH-40039 (b2211p9) on 26th Dec 2022 for Preview and 29th Dec 2022 for Production Environment
• You will not be able to auto-migration these rules via the check tool, it will be suggested to manually migrate them. If you choose to do so, please use the Rule Scenario "Generate Alerts". 

2H 2022, b2211, WorkflowsNoBasicRules, EventReasonDerivationNoBasicRules, TimeTypeNoBasicRule, TimeAccountTypeNoBasicRules, Manual Mass Change of Basic Rules to Application-Specific Scenarios, basic rule, rule scenarios, rule scenario, TLS-25119, ECT-211437, CS20220004571187, PTCH-40039 , KBA , LOD-SF-EC , Employee Central , LOD-SF-EC-TIM , Time Off , LOD-SF-EC-WFL , Workflows - Configuration, Tools, Objects & Rules , LOD-SF-EC-JOB-EVN , Events, Derivation & Employee Status , Product Enhancement