SAP SuccessFactors Onboarding supports a variety of features to streamline the onboarding process for new hires, rehires, and internal transfers. These features enhance user experience, ensure compliance, and integrate with other systems.

According to the SAP SuccessFactors Onboarding Implementation Guide:

External HRIS integration with internal hire process(Option B): Onboarding supports integration with external HRIS systems to facilitate processes like internal hires, allowing data to be transferred seamlessly via APIs or middleware.

Document generation and e-signature(Option D): Onboarding includes robust document management capabilities, such as generating forms and enabling e-signatures (e.g., via DocuSign) to collect signatures from new hires or managers.

Data collection of new hire personal information(Option E): A core feature of Onboarding is the ability to collect personal and job-related information from new hires through steps like Personal Data Collection and Additional Data Collection.

Option A (Global reassignment of employees) is incorrect because global assignments are managed in Employee Central, not directly in Onboarding, though Onboarding can support related processes. Option C (Management of contingent workers) is incorrect because contingent worker management is primarily handled in Employee Central, not Onboarding.

Assigning theReview New Hire Datastep to a hiring manager in SAP SuccessFactors Onboardingrequires configuring permissions and business rules to ensure the manager is responsible for reviewing the new hire’s data.

According to the SAP SuccessFactors Onboarding Implementation Guide:

Set up role-based permissions(Option B): Role-based permissions must be configured inManage Permission Rolesto grant the hiring manager access to theReview New Hire Datatask. This includes permissions likeAccess New Hire DataandUpdate New Hire Data.

Set rule SAP_ONB2_HMReviewCheck to True(Option C): TheSAP_ONB2_HMReviewCheckbusiness rule, configured inConfigure Business Rules, must be set toTrueto assign the Review New Hire Data step to the hiring manager. This rule triggers the task assignment based on the manager’s role.

Option A (Create a custom HRIS element as an MDF object) is incorrect because HRIS elements are not required for assigning this step. Option D (Add an HRIS element in the user data file) is incorrect because user data files are used for data import, not for task assignment.

SAP SuccessFactors integrates with Qualtrics to collect and report survey data for both Onboarding and Offboarding processes. Specifically, Qualtrics is used to gather employee experience data, such as new hire feedback during Onboarding and exit survey responses during Offboarding.

According to the SAP SuccessFactors Onboarding and Offboarding Integration Guide:

Qualtrics collects the new hire experiences and reports the results(Option D). During the Onboarding process, Qualtrics surveys are triggered to collect feedback from new hires about their onboarding experience. The results are analyzed and reported through Qualtrics dashboards.

Qualtrics collects the exit survey information and reports the results(Option A). In the Offboarding process, Qualtrics is used to send exit surveys to terminating employees, collecting data on their reasons for leaving and overall experience. The results are aggregated and reported in Qualtrics.

Option B is incorrect because Onboarding does not directly collect new hire experiences; Qualtrics handles the survey collection. Option C is incorrect because Offboarding does not collect exit survey data itself; Qualtrics is responsible for both collection and reporting.

TheEmail Servicestool in SAP SuccessFactors Onboarding enables administrators to configure email notifications for onboarding participants, supporting communication throughout the process. Several features enhance the flexibility and functionality of these notifications.

According to the SAP SuccessFactors Onboarding Configuration Guide:

Create new email templates with business and locale-specific rules content(Option B): Administrators can create custom email templates inEmail Servicesand define content based on business rules or locale-specific requirements, ensuring relevant messaging for different regions or scenarios.

Configure reminder notifications to control the frequency of reminder messages(Option C): Email Services allows configuration of reminder notifications, including setting the frequency (e.g., daily or weekly) to prompt users to complete overdue tasks.

Attach documents to email notifications(Option E): Documents, such as onboarding forms or instructions, can be attached to email notifications to provide new hires or managers with necessary materials directly in the email.

Option A (Delete a preconfigured email template) is incorrect because preconfigured templates are system-defined and cannot be deleted, though they can be disabled or customized. Option D (Trigger an onboarding task) is incorrect because tasks are triggered by business rules or process steps, not directly by Email Services.

Standard business rules in SAP SuccessFactors Onboarding are used to automate and control data collection processes, ensuring that the right data is collected and validated at the appropriate steps.

According to the SAP SuccessFactors Onboarding Implementation Guide:

ONB2_HMReviewCheck(Option B): This rule assigns theReview New Hire Datastep to the hiring manager and ensures that the data collected (e.g., personal or job information) is reviewed for accuracy.

ONB2_ECDataCollectionCheck(Option C): This rule validates data collected during the Personal Data Collection step, ensuring it aligns with Employee Central requirements and is complete before proceeding.

ONB2_CustomDataCollectionCheck(Option E): This rule is used to validate data collected in custom data collection steps, such as those using custom MDF objects, ensuringcompliance with defined criteria.

Option A (ONB2_InternalHire_Configuration) is incorrect because it configures internal hire processes, not data collection specifically. Option D (ONB2_PreDay1AccessCheck) is incorrect because it controls access before the start date, not data collection processes.

The SAP SuccessFactors Offboarding process includes a series of standard steps to ensure a structured exit process for employees leaving the organization. These steps involve tasks for the offboardee, manager, and other stakeholders.

According to the SAP SuccessFactors Offboarding Implementation Guide:

Employee Review(Option B): This step allows the offboardee to review and update their personal information or complete exit-related tasks, such as filling out an exit survey.

Document Flow(Option D): This step involves routing documents (e.g., exit forms, acknowledgments) for review or e-signature, ensuring all necessary paperwork is completed.

Manager Review(Option E): The manager reviews the offboardee’s data, completes tasks like approving knowledge transfer plans, and ensures all exit requirements are met.

Option A (Additional Data Collection) is incorrect because it is primarily an Onboarding step, not standard in Offboarding. Option C (Compliance Forms) is incorrect because, while forms may be part of Document Flow, it is not a distinct standard step in the Offboarding process.

Role-based permissions (RBPs) in SAP SuccessFactors Offboarding are specific to tasks unique to the offboarding process, distinguishing them from onboarding or other modules. These permissions ensure that only authorized users can perform offboarding-specific activities.

According to the SAP SuccessFactors Offboarding Configuration Guide:

Knowledge Transfer Plan(Option A): This permission allows users (e.g., managers or HR) to create and manage knowledge transfer plans, a task specific to offboarding to ensure critical knowledge is shared before an employee leaves.

Asset Task(Option D): This permission enables users to manage tasks related to the return of company assets (e.g., laptops, badges), which is a common offboarding activity.

Option B (Document Flow) is incorrect because document flow permissions apply to both onboarding and offboarding for managing document routing and signatures. Option C (Meeting Task) is incorrect because meeting-related tasks are not specific to offboarding and can apply to other modules.

Integrating an external HRIS with SAP SuccessFactors Onboarding requires configuring data transfers and aligning the data model to ensure seamless onboarding processes.

According to the SAP SuccessFactors Onboarding and Integration Guide:

Import Employee Data using Integration Center or OData APIs(Option B): Employee data from the external HRIS must be imported into SuccessFactors usingIntegration CenterorOData APIsto create onboarding records and populate fields like personalInfo or jobInfo.

Configure the Onboarding data model(Option C): The Onboarding data model must be configured to map fields from the external HRIS to SuccessFactors entities (e.g., personalInfo, jobInfo), ensuring data compatibility.

Create an export of new hire data using Integration Center or OData APIs(Option E): New hire data may need to be exported back to the external HRIS for synchronization, usingIntegration CenterorOData APIsto maintain consistency.

Option A (Create an export using only a middleware system) is incorrect because exports can use Integration Center or APIs, not just middleware. Option D (Configure all the Event Reasons) is incorrect because only relevant event reasons (e.g., hire, termination) need configuration, not all.

Creating a custom task for an onboarding program in SAP SuccessFactors Onboarding involves defining a new task structure and associating it with the program. This typically requires using Metadata Framework (MDF) objects to store task-related data.

According to the SAP SuccessFactors Onboarding Implementation Guide:

Create a custom MDF object(Option A): A custom MDF object is created inConfigure Object Definitionsto define the fields and structure of the custom task (e.g., task name, due date, or assignee).

Link the custom MDF object to the custom task(Option B): The custom MDF object is linked to the task in the onboarding program configuration (e.g., viaProcess Variant ManagerorManage Onboarding Programs) to ensure the task is included in the process flow.

Option C (Configure the visibility of the custom MDF object) is incorrect because visibility is configured for data collection steps, not directly for tasks. Option D (Create a UI in Manage Configuration UI) is incorrect because creating a UI is optional for administrative purposes and not required for task creation.

Custom tokens in SAP SuccessFactors Onboarding email templates allow dynamic insertion of data, such as a new hire’s name or start date, into notifications. These tokens are configured using specific tools to map and reference data fields.

According to the SAP SuccessFactors Onboarding Implementation Guide:

Map the field names on the document template to fields defined in Onboarding(Option C): InDocument Generation - Manage Document Template Mapping, administrators map document fields to MDF objects or other data sources, enabling tokens to pull the correct data into emails.

Create a document template using Document Generation(Option D): TheDocument Generation - Manage Document Templatetool is used to create templates that include custom tokens, which can be referenced in email notifications.

Use format {fieldID} to add custom tokens in the subject or body of the email in Email Services(Option E): InEmail Services, administrators add custom tokens using the {fieldID} format to dynamically insert data into the email subject or body.

Option A (Create a document template for custom tokens using Maintain Onboarding and Offboarding Document Templates) is incorrect because this tool is for uploading forms, not creating tokens. Option B (Add field names on the content of the document template) is incorrect because field names are mapped, not manually added to the template content.