Event & Event Derivation Rules

 

Event & Event Derivation Rules

 What is Event?

Employee Hire to Retire/ In between Employee Life cycle many big events happens for Example:

Event (Actions)

Event Reasons

Assignment Assignment Completion Job Change Completion of Probation Data Change Demotion Furlough Hire Job Reclassification Leave of Absence (used for time off activities) Pay Rate Change Position Change Probation Promotion Rehire Return from Disability Return to Work (used for time off activities) Suspension Termination Transfer Add Global Assignment End Global Assignment Obsolete Start Pension Payout

Why hiring an employee Business Expansion Replacement Death Retirement

 

Below are the screenshots of Events list.

Once you upload the standard picklist/the events will appear in the Picklist.

In SAP SF, the event labels can be changed but the external codes cannot be changed at configuration time. If it is changed the entire system will be corrupted.

In SF we cannot create any custom events we have to use the standard events which are available. In SF there are 29 events which are pre-defined.

For any custom events, SF provided to change the existing event label and we can use, but intent remains same.

What are Event Reasons?

Event reason is an activity derived from events that drives changes in employee data. Actions taken in the Employment Profile are based on the client requirement.

Event reasons is also a Foundation Object. We can search action as Manage Organization, Pay & Job Structure >> Create New Event Reason.

Provide the values for the following fields:

>>Effective as of     - From when should the event reason be effective or visible in the system.

>>Event Reason Id - A unique id for the event reason

>>Event Reason Name - Name for the event reason

>>Status - Event Reason status (Active/Inactive)

>>Event - The event that needs to be mapped to the event reason (The events are defined in Picklist Management)

>>Employee Status – The status of the employee when this event reason is selected in his job info portlet.

We can create end number of Event Reasons in Event ID’s and always select the Active Option.

Once you have created the event reason, you will then have to permission the event reason by doing the following

Admin Center > Manage Permission Roles

Choose a role > Click Permission

Search action as Manage Permission Roles >> Permission Role List << Configure Business Rules >> Create New Rule >> Basic >> Role Name.

Go to the Employee Data Section > Event Reason > Grant Permission to Event Reason > Save

How do we create Business Rules in SuccessFactors? Go to Admin Center >> Configure Business Rules

In Basic Object you have two drop down values:

• Job Information (Change Field)
• Job Information Model (Specific Value) For Event Reasons Always go with this option.

Go to Manage Business Configuration >> Job Information

These are the basic understanding of Event and Event Derivation Rules Concept.