You learned that event and event Reasons are mandatory for job and compensation Information-related transactions. When managers initiate a transaction, they manually choose the appropriate event and event reason, making it error-prone and the resulting reports unreliable.
To streamline this process, Event Reason Derivation (ERD) rules can be set up for customers so that the system automatically determines the correct event reason according to the changes made to an employee's data. The employee status is updated, if necessary, depending on the event reason.
Implementing ERD requires more effort before going live but greatly improves transaction accuracy, especially for Manager Self Service.
If you choose not to use ERD, the Event and Event Reason will always be chosen by the user initiating the transaction. For Job Information edit and history transactions without ERD, managers and admins only have access to events with at least one event reason for which they have Edit permission.
Business rules can still be configured to tie the event reason chosen to a workflow configuration, to ensure the transaction goes through the appropriate approval process before it is active.
Event Reason Derivation on Imports
To have the event reason derived during imports, you must enable the Enable Business Rules for selected entities permission for imports.
If a value is entered in the event reason column of the import template, it takes precedence over the Employee Reason Derivation by the onSave rule. If the column is empty, the event reason is derived by the onSave business rule.