Applying Intelligent Services and Events

Objective

After completing this lesson, you will be able to identify Intelligent Services and Events within Recruiting.

Intelligent Services within Recruiting

Intelligent Services leverage tight integration between modules and the ability to predict the next step in an HR transaction to simplify how HR is run. When these events occur in one part of the suite, other areas are made aware of it and can react accordingly. For example, when a manager goes on a leave of absence, her open job requisitions are automatically reassigned, her learning courses are postponed, and her goals are updated, without the need for any manual intervention.

Intelligent Services are designed to connect and predict transactions resulting from a change. Intelligent Services give users more end-to-end control over events, which significantly reduce the involvement and the expense of HR shared services within an organization.

Intelligent Services begin as events that are published in one area of the SAP SuccessFactors HCM Suite. Customer defined rules create a ripple effect throughout the Suite. Any SAP SuccessFactors product can trigger and publish an event, such as manager, employee, and job information changes, employee absences, or new hires and terminations. Any other product, either SAP SuccessFactors or third-party, can subscribe to any published event. Whenever that event is triggered by the publishing product, those subscribed products automatically receive notification of the event, with information relevant to the change.

In addition, the administrator can use the Event Center dashboard to view event details and monitor event status. Administrators can also configure and manage the external event notifications to facilitate data integration with third-party systems.

Events within Recruiting

  • Requisitions Reassigned

    Job requisitions can be reassigned for each operator role on a template when the original operator takes a leave of absence (including short-term or long-term disability).

    Each Job Requisition template can be configured to reassign requisitions for each operator role on the template. For each role, if employees in that role go on leave, the requisition is reassigned to the on-leave employee's Next-Level Manager.

    Based on admin settings, it is also possible to reassign the requisitions to a Specified User, instead of the Next-Level Manager. To-Dos associated with the requisition are also reassigned, and a summary e-mail is sent to the employee and Next-Level Manager describing which requisitions were successfully reassigned and which ones failed to be reassigned.

  • Update of Job Requisition

    This event is published when an approved or closed job requisition is updated. Onboarding activity is updated when changes are made to a job requisition, and email notifications are sent to the new hire and hiring manager.

  • Update of Job Application

    This event is published when a job application is updated and the applicant is in an applied state. Onboarding activity is updated when changes are made to a job application, and email notifications are sent to the new hire and hiring manager.

    When a change is made to relevant candidate data, even after initialization of onboarding, the data is automatically kept consistent, and the onboarding process is adjusted accordingly. If the Hiring Manager, HR Manager, or New Hire buddy changes, the Onboarding step is reassigned to the newly responsible user.

  • Approval of Offer Detail

    This event is published after the final approval step on an offer detail. Onboarding activity is updated after the final approval step of an offer detail, and email notifications are sent to the new hire and hiring manager.

    When a change is made to relevant candidate data, even after initialization of onboarding, the data is automatically kept consistent, and the onboarding process is adjusted accordingly. If the Hiring Manager, HR Manager, or New Hire buddy changes, the Onboarding step is reassigned to the newly responsible user.