SAP Knowledge Base Article - Public

2981592 - Event Reason Derivation XML Deperication - Day 1 Considerations


As of the 2H 2020 release, the Event Reason Derivation XML template is deprecated (ECT-133348). This KBA lists considerations to be taken into account once your instance has been migrated. Based on your configuration, some you may have rules created which you did not expect or may need to reorder rules.

This means that you can no longer use XML-based rules to derive Event Reasons for Job Information and Compensation Information. From now on, in those instances which were using the XML based rules, business rules must be used for this purpose. Existing rules in XML will be translated into onSave business rules and automatically migrated for you.

Further information on this Migration can be found in the below repositories:


SAP SuccessFactors Employee Central


For any instances which are using the XML-based approach for Event Reason Derivation, a migration to Business Rules for Event Reason Derivation will be provided.

Please Note: For an instance to be using the XML-based approach the Enable youCalc rules engine for HRIS setting is be enabled in Provisioning.  For these instances only the migration will take place.

The migration script ensures that the required settings are changed, and existing rules in XML are translated into onSave business rules.

Two rules will be created as part of the migration:

  • One for Job Information Event Reason Derivation. This rule will contain all event reason derivation rules for Job Information from the XML.
  • One for Compensation Information Event Reason Derivation. This rule will contain all event reason derivation rules for Compensation Information from the XML.

Both rules will be triggered as onSave business rules on the relevant HRIS Element and will be visible in both Manage Business Configuration UI and the Success Data Model as triggered rules.

To help identify the rules from other rules in your instance, the migrated rules will include the postfix ‘ERD_migrated_rule’ to make it easier for you to review and edit the rule. For example:

  • jobInfoModel_ERD_migrated_rule_1582621769177
  • compInfoModel_ERD_migrated_rule_1582621769177


Day 1 Considerations:

To fully understand the new logic applied when using Business Rules for Event Reason Derivation, it is recommended to review the following page of the documentation: SAP SuccessFactors Employee Central – Employee Central Master: Event Reason Derivation Business Rules.
The logic used is very similar to that of the Event Reason XML but with one notable change. This is with regards to the logic used when changing both Job and Compensation Information in the same transaction.

While the XML used a top down approach, meaning the first matching rule would set the Event Reason used, regardless of weather it was a Job Information or Compensation Information rule. The Business Rules for Event Reason Derivation uses the following logic:

  1. The system tries to get the event reason set on the Job Information entity first. If it is set on the Job Information entity, then the event reason is used.
  2. If no event reason is set on Job Information, the system tries to derive the event reason set on the Compensation Information entity. If it’s set, then the event reason is used.
  3. If the system encounters a case where the event reason is neither set on the Job Information nor on the Compensation Information entity, it raises an error message, and this is displayed on the screen.

Due to this logic, there may be a scenario when you must adjust the migrated rules in order to receive the desired Event Reason. For this reason, it is recommended to carry out post release testing on this feature.

Post Release Testing:

Post the migration you may wish to carry out some testing or sanity checks on the newly created rules. May I suggest the below as some scenarios to include in your testing:

  • Review Manage Business Configuration UI or the Succession Data Model to see the newly created rule triggers. These rules will have the postfix ‘ERD_migrated_rule’ for example: jobInfoModel_ERD_migrated_rule_1582621769177.
    These rules should have an onSave trigger event.
  • Open both rules to review the configuration.
  • Run Check Tools > Employee Central Core > Rules. These checks will not only validate the newly created rules but also all other rules trigger in your system.
  • Carry out Manager Self Service (MSS) Take Action Based on your daily business processes, carry out a series of Job Information and Compensation Information checks to validate the Event Reason Derivation of the business rules. It is important to test creating Job and Compensation Information records from different scenarios, especially the scenario of creating a Job and Compensations Information change in the same transaction.
  • If you would like to understand how the rule is working in more detail, creating a “Business Rule Execution Log” (Rule Trace) may help. The Rule trace can be created for the two migrated rules to review the execution and the Event Reason Derivation. More information on using Rule Traces can be found in the following KBA:
    2257064 – Employee Central - Business Rule Execution Log
  • Production instances the import option of Event Reason Derivation(ERD) has been disabled in provisioning. Customers are requested to perform the opt-in migration from Upgrade Center and then make changes in the migrated ERD business rule.
  • YouCalc feature switch in provisioning has been made invisible. However, if an attempt to enable the Switch for ERD via business rules is made in provisioning directly before the migration is successful, then this option will get unchecked. Implementation Partners will not be able to enable it again as they can't see this switch. Also, if this switch is disabled then opt-in migration option from Upgrade Center will be unavailable.

See Also


ECT-133348, ERD, Event Reason Derivation Data Model, Event Reason Data Model , KBA , LOD-SF-EC-JOB-EVN , Events, Derivation & Employee Status , LOD-SF-EC-CMP-EVN , Events, Derivation & Employee Status , Product Enhancement


SAP SuccessFactors Employee Central 2011 ; SAP SuccessFactors HCM suite all versions