Job Information is one of the most important entities within SAP SuccessFactors Employee Central Solution. It is important to get the configuration of this entity right and hence It is essential to understand various concepts associated with its configuration correctly.
It is an effective dated entity and contains information about the Organization Structure, Position, Job and Pay structure, Supervisor, Employment Contract details etc. applicable for each employee. Information/values stored in Job information fields also affect other solutions like Time Management, Position Management, Compensation Information etc. and hence configuration of this entity must consider requirements in other related areas.
One of the basic concepts in Job information is that of Event Reasons. Event Reasons provide the possibility to record date-wise changes in employment-related information of an employee. These are associated with ‘Events’ which are pre-delivered by SAP SuccessFactors.
Incorrect configuration of Event Reasons may arise due to any of the following reasons:
1. Employee Status associated with Event Reason
Every event reason must have an event and appropriate employee status assigned to it except when it is a data change event, in which case the employee status remains blank. Getting employee status wrong can lead to issues like an employee may become visible after termination, an eligible employee may become unavailable for HR processes etc.
2. Event Reason Permissions
While new event reasons can be created, Events are pre-delivered by SAP. It is important that a user is appropriately permissioned for an event reason. For example, If a manager is permissioned to ‘Change job and compensation Info’ of his direct reports, ‘Edit’ permission for associated event reasons needs to be provided else the changes will fail.
When a custom event reason is created, one needs to remember to provide permission for these as well.
3.Incorrect Event Reason Derivation Rules
Automated event and event reason derivation using business rules need to be enabled in provisioning. Automated event reason derivation ensures data consistency as there is no way to assign a wrong event or event reason to a specific transaction. Event reason derivation helps to simplify the process for users. Thus, it is recommended to implement event reason derivation using business rules.
A new rule scenario ‘Event Reason Derivation’ is available under ‘Employee Central Core’ to create business rules for event reasons derivation. Ensure to use this scenario to pull appropriate base objects while creating the rule.
It’s important to understand that the conditions are executed in the sequence they are written and if a true condition is met, associated event reason is set and further rule execution stops. The sequence of conditions is important while creating the rule. One needs to have more specific and restrictive conditions in the beginning while gradually moving towards more generic conditions.
A sample rule to set event reason as “Location Change” / “Cost Center Change” is shown below. When a user edits location/cost center in an employee’s record, based on below rule, the system automatically identifies the associated event reason and updates the same when the record is saved.
Order of event reasons in the rule is important, e.g., if both cost center and location are changing at the same time, system will assign the location change event reason as per above rule because system doesn’t evaluate further conditions if one true condition is executed
4.Event Reason Business Rule Assignment
Event Reason Business Rule needs to be assigned as onSave rule in the Manage Business Configuration UI under Job information or Compensation Information HRIS element depending on the base object type selected. This is saved in the Succession Data Model (SDM) for the corresponding entity. Assignment to wrong HRIS element will not trigger the rule.
There are certain scenarios in which event derivation is not applicable, i.e., hiring, termination, add global assignment, leave of absence, add concurrent employment. One needs to select the reasons manually in these cases. Event Reason Derivation only gets executed for changes in Job Information and compensation information records done through MSS UI and Employee Data Imports (and APIs which runs through the imports coding internally) and not for changes done through ‘History’ UI.
To know about other aspects of configuration like country-specific Event Reasons, FTE calculations, cross-entity rules, Refresh Compensation Required feature, Forward Propagation, TimeIn Calculations etc please refer to the Implementation Design Principle SAP SuccessFactors Employee Central: Job Information Entity Configuration Considerations.
For structured guidance and advice on how to address challenging customer requirements please visit the Implementation Design Principles for SAP SuccessFactors Solutions page on SuccessFactors customer community
It is an effective dated entity and contains information about the Organization Structure, Position, Job and Pay structure, Supervisor, Employment Contract details etc. applicable for each employee. Information/values stored in Job information fields also affect other solutions like Time Management, Position Management, Compensation Information etc. and hence configuration of this entity must consider requirements in other related areas.
One of the basic concepts in Job information is that of Event Reasons. Event Reasons provide the possibility to record date-wise changes in employment-related information of an employee. These are associated with ‘Events’ which are pre-delivered by SAP SuccessFactors.
Incorrect configuration of Event Reasons may arise due to any of the following reasons:
1. Employee Status associated with Event Reason
Every event reason must have an event and appropriate employee status assigned to it except when it is a data change event, in which case the employee status remains blank. Getting employee status wrong can lead to issues like an employee may become visible after termination, an eligible employee may become unavailable for HR processes etc.
2. Event Reason Permissions
While new event reasons can be created, Events are pre-delivered by SAP. It is important that a user is appropriately permissioned for an event reason. For example, If a manager is permissioned to ‘Change job and compensation Info’ of his direct reports, ‘Edit’ permission for associated event reasons needs to be provided else the changes will fail.
When a custom event reason is created, one needs to remember to provide permission for these as well.
3.Incorrect Event Reason Derivation Rules
Automated event and event reason derivation using business rules need to be enabled in provisioning. Automated event reason derivation ensures data consistency as there is no way to assign a wrong event or event reason to a specific transaction. Event reason derivation helps to simplify the process for users. Thus, it is recommended to implement event reason derivation using business rules.
A new rule scenario ‘Event Reason Derivation’ is available under ‘Employee Central Core’ to create business rules for event reasons derivation. Ensure to use this scenario to pull appropriate base objects while creating the rule.
It’s important to understand that the conditions are executed in the sequence they are written and if a true condition is met, associated event reason is set and further rule execution stops. The sequence of conditions is important while creating the rule. One needs to have more specific and restrictive conditions in the beginning while gradually moving towards more generic conditions.
A sample rule to set event reason as “Location Change” / “Cost Center Change” is shown below. When a user edits location/cost center in an employee’s record, based on below rule, the system automatically identifies the associated event reason and updates the same when the record is saved.
Order of event reasons in the rule is important, e.g., if both cost center and location are changing at the same time, system will assign the location change event reason as per above rule because system doesn’t evaluate further conditions if one true condition is executed
4.Event Reason Business Rule Assignment
Event Reason Business Rule needs to be assigned as onSave rule in the Manage Business Configuration UI under Job information or Compensation Information HRIS element depending on the base object type selected. This is saved in the Succession Data Model (SDM) for the corresponding entity. Assignment to wrong HRIS element will not trigger the rule.
There are certain scenarios in which event derivation is not applicable, i.e., hiring, termination, add global assignment, leave of absence, add concurrent employment. One needs to select the reasons manually in these cases. Event Reason Derivation only gets executed for changes in Job Information and compensation information records done through MSS UI and Employee Data Imports (and APIs which runs through the imports coding internally) and not for changes done through ‘History’ UI.
To know about other aspects of configuration like country-specific Event Reasons, FTE calculations, cross-entity rules, Refresh Compensation Required feature, Forward Propagation, TimeIn Calculations etc please refer to the Implementation Design Principle SAP SuccessFactors Employee Central: Job Information Entity Configuration Considerations.
For structured guidance and advice on how to address challenging customer requirements please visit the Implementation Design Principles for SAP SuccessFactors Solutions page on SuccessFactors customer community
- SAP Managed Tags:
| User | Count |
|---|---|
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
