Introduction

In many organizations, the probation period is designed to give both the employer and the employee a fair window to assess performance, cultural fit, and overall suitability for the role. But what happens when that evaluation period is interrupted? Employee absences, especially due to short term sickness, can significantly reduce the time available for meaningful observation, leaving managers with incomplete information at the end of the probation timeline.

To address this, some companies adopt a policy of extending the probation period by the exact number of days an employee was absent during that time. While the intent is straightforward, the execution can quickly become complex. Tracking absence days, recalculating end dates, and ensuring consistency across the organization often leads to manual effort, errors, and compliance risks.

This is where SAP SuccessFactors Employee Central (EC) can play a crucial role. By leveraging automation and business rules, organizations can seamlessly adjust probation end dates based on recorded absences, ensuring fairness, accuracy, and operational efficiency. In this blog, we’ll explore how to design and implement an automated approach to extending probation periods when short term sick leave occurs, helping HR teams move from manual tracking to a more intelligent, system-driven process.

Proposed Solution

The proposed solution is based on standard SuccessFactors functionalities, namely Intelligent Services Center (ISC), Integration Center (IC), and Business Rules.

In this scenario, whenever a short-term sickness absence is recorded, an Employee Time event triggers a process to evaluate whether the employee is still within the probation period and, if so, automatically extend the probation end date in the Job Information portlet.

Below is a step-by-step guide to building it.

Step 1: Navigate to Integration Center and click “My Integrations” to start creating your IC job.

Step 2: Now click on “+ Create” and select “More Integration Types”.

Step 3: In this step, you need to define the integration type. For this scenario, select the options as shown in the screenshot below. Once selected, click “Create.”

Step 4: On the first screen of the IC job, you are required to provide a name, a description, and a page size. Below is an example from a demo system. Once these fields are defined, click “Next.”

Step 5: Next, navigate to the “Configure Fields” tab and, from the menu in the top-right corner, select the “Switch to Field Mapping View” option.

On this page, we first define the destination table, for this scenario, we use “Job Information.”

Next, we configure the mapping from the “Employee Time” table to Job Information. As shown in the screenshot below, only two fields are directly mapped: “Event Date,” which is mapped to the absence “End Date,” and “User ID,” mapped to the “User ID” from the source table.

These mappings are created easily by dragging and dropping fields from the source table on the left to the corresponding fields in the destination table on the right.

Step 6: Next, switch to “Detail View” using the option in the top-right menu.

We will now define fields that do not have a direct mapping but instead require a default value. To do this, locate the “Sequence Number” field in the table on the right. Select it, then in the left panel assign a value greater than 2, for example, 9.

Setting a number higher than 2 helps prevent potential errors. If, on the same day, the job attempts to create a new time slice in Job Information while another record already exists, the system will use this higher value to generate an additional sequence number. It’s important to note that the final sequence may not necessarily be 9, as the system intelligently determines the correct sequence based on existing records.

Now we complete the second action in this step by assigning a default value to the “Event Reason” field for this scenario.

Note: It is recommended to create a dedicated event reason for this use case to avoid unintentionally triggering the business rule (which we will configure later) in other situations.

Step 7: We have now completed the creation of our IC job, so click “Save” as shown in the screenshot.

Step 8: In this step, we will assign the IC job we created to the ISC. Navigate to the Intelligent Services Center page, search for the event “Employee Short Term Disability,” and click to open it.

Step 9: Create a new flow if one already exists for this event. Click “Integration” from the right-hand menu, which will add a new line in the center of the page. Set the “Timing” to “When event is published.” Then, use the three-dot menu (highlighted in green) to save your changes.

Note: It is also advisable to create an ISC rule that limits the process to employees whose probation status is neither completed nor failed (or based on any other criteria relevant to your organization).

Step 10: In this step, we will create our first business rule, which will trigger the Intelligent Services Center event. To do this, navigate to the “Configure Object Definition” transaction and select the “Employee Time” object.

Click to create a new rule, following the example below. Once the rule is created, assign it on Save in the object and then save the object.

Note: The absence type used in the rule example is for demonstration purposes only. Please ensure you use the absence type relevant to your organization.

Step 11: Our final step is to create a business rule that calculates the new probation end date considering the number of days the employee was on sick leave.

To do this, navigate to “Manage Business Configuration” > “Job Information.” In edit mode, scroll to the bottom of the page. On the last line, click to create a new business rule as shown below. Once the rule is created, assign it to the onSave event in the portlet and save your changes.

Conclusion

By combining Intelligent Services Center (ISC), Integration Center (IC), and Business Rules, we have demonstrated how SAP SuccessFactors can be configured to automate the extension of probation periods based on employee sick leave. This approach ensures that any absence occurring during the probation period is accurately reflected by extending the end date accordingly, eliminating the need for manual adjustments.

Beyond improving administrative efficiency, this solution also enhances fairness and consistency in HR processes, ensuring that all employees are evaluated over an equivalent active working period. It reduces the risk of human error, strengthens compliance with internal policies, and provides a scalable framework that can be adapted to other absence-driven scenarios.

Finally, this use case illustrates the power of SAP SuccessFactors standard tools when combined thoughtfully. With the right configuration, organizations can transform complex HR requirements into automated, transparent, and maintainable processes that support both HR teams and employees alike.

I hope this solution helps you improve your Employee Central setup. Feel free to reach out or comment if you have questions, or if you’d like to share how you’ve tackled probation extensions due to employees absences in your own environment.