The process of creating and utilizing custom tokens for SAP SuccessFactors Onboarding emails involves a sequence of steps across different admin tools. The token is technically created using the Document Generation framework. First, a placeholder (e.g., [[CustomToken]]) is defined within a template using Document Generation - Manage Document Template (D). Next, this placeholder is mapped to a specific data source (such as a field from the data model or the output of a business rule) via Document Generation - Manage Document Template Mapping (E). This mapping step is what formally creates the token. Finally, to make the token functional in an email, it must be inserted into a notification template within Email Services (B). Therefore, all three tools are integral to the end-to-end process.

A. Maintain Onboarding and Offboarding Document Templates: This tool is part of the legacy Onboarding 1.0 system and is not used for creating tokens in the current version of SAP SuccessFactors Onboarding.

C. Configure Business Rules: While a business rule can be used to calculate the value that a custom token displays, it is only one of many possible data sources. The tool itself does not create the token; it provides data for it.

1. SAP Help Portal: Implementing with SAP SuccessFactors Onboarding

Section: "Creating Custom Tokens for Onboarding".

This official guide explicitly outlines the procedure

stating users must first use "Manage Document Template" to create a placeholder and then "Manage Document Template Mapping" to map the placeholder to a data field. This directly supports options D and E as the core creation steps.

2. SAP Help Portal: Implementing with SAP SuccessFactors Onboarding

Section: "Configuring Email Notifications for Onboarding".

This section details the use of "Email Services" to configure the email templates where tokens are used. It states

"You can use standard and custom tokens to include employee-specific or company-specific information in the email notification." This confirms that Email Services (B) is the tool where the created token is applied for use within emails.

In SAP SuccessFactors Onboarding, process variants are used to define different onboarding experiences for various groups of new hires. To create an onboarding process that omits the "Review New Hire Data" step, an administrator must configure a new process variant. Within the configuration of this variant, they can select which standard steps to include or exclude. By simply not adding the "Review New Hire Data" step to the variant's workflow, any new hire assigned to this process variant will bypass that step entirely. This is the correct and standard configuration method for structurally altering the process flow.

A. Cancel the Review New Hire Data task from the Onboarding dashboard: This is a manual, one-time action for a specific new hire's active process. It does not change the underlying process configuration for future hires.

B. Define a business rule using the Update Onboarding or Offboarding Process Object scenario: Business rules are primarily used for dynamic assignments, data validation, or setting due dates, not for defining the fundamental inclusion or exclusion of steps in a process structure.

D. Skip the step by selecting the option from the Action menu in the Onboarding dashboard: Similar to canceling, this is a manual intervention performed on an in-flight process for a single individual, not a permanent configuration change to the process itself.

1. SAP Help Portal

SAP SuccessFactors Onboarding

"Creating a Process Variant": This official guide details the procedure for setting up process variants. It states

"You can create a process variant to define a different set of tasks for a specific group of new hires... In the Process Steps section

you can add

remove

or reorder the tasks that are part of the process variant." This directly supports that removing a step like "Review New Hire Data" is done during variant creation.

2. SAP Help Portal

SAP SuccessFactors Onboarding

"Standard Tasks in Onboarding and Offboarding": This document lists "Review New Hire Data" as a standard

configurable task. The ability to include or exclude such standard tasks is a core feature of process variant configuration

confirming that this is the correct level for the required change.

3. SAP Help Portal

SAP SuccessFactors Onboarding

"Managing Onboarding and Offboarding Tasks": This section describes the administrative actions available on the Onboarding Dashboard

such as skipping or reassigning tasks. It frames these as manual interventions for active processes

which distinguishes them from the initial process configuration described in the correct answer.

In the context of SAP SuccessFactors Onboarding and its integration with Employee Central, transfer events are primarily triggered by changes to an employee's core job and compensation data. These events are crucial for initiating the crossboarding (internal hire) process. Business rules are configured to monitor the jobInfo (Job Information) and compInfo (Compensation Information) entities. When a manager performs an action like a promotion, transfer, or pay change, the corresponding records in jobInfo and compInfo are updated. This update acts as the trigger, or "transfer event," that initiates the appropriate Onboarding workflow for the internal employee movement.

A. globalInfo: Changes to globalInfo typically represent updates to country-specific personal data, not organizational or job-related transfers that would trigger a crossboarding process.

D. employmentInfo: While employmentInfo contains key dates, the dynamic event-driven changes related to an employee's role, pay, and position are captured in jobInfo and compInfo.

1. SAP Help Portal

Implementing and Managing Onboarding

"Setting Up Crossboarding": This guide explicitly details the configuration of a business rule on the Job Information (jobInfo) element to trigger the crossboarding process. It states

"You create a business rule to define the conditions that trigger the Crossboarding process for an internal hire... The base object for this rule must be Job Information." This confirms jobInfo as a primary trigger.

2. SAP Help Portal

Implementing Employee Central Core

"Job Information": This document outlines that the jobInfo entity is the central place for recording all job-related changes

including transfers

promotions

and other organizational movements. It states

"Job Information tracks all job-related changes for an employee." These changes are the foundation for transfer events.

3. SAP Help Portal

Implementing Employee Central Core

"Events and Event Reasons": This section explains how event reasons are linked to changes in jobInfo and compInfo. A transfer event is defined by an event reason

which is directly tied to modifications in these two entities. For example

a "Transfer" event reason will always involve a change to the employee's jobInfo and often their compInfo.

The standard SAP SuccessFactors Offboarding process is a configurable workflow designed to manage an employee's departure. The process includes several key steps assigned to different stakeholders. "Manager Review" is a step where the manager completes tasks like planning knowledge transfer and confirming asset return. "Employee Review" is the step for the departing employee to complete their tasks, such as an exit interview or reviewing final documents. "Document Flow" represents the generation, signing, and management of essential offboarding documents, like a certificate of service or final pay statements. These are all integral parts of the standard offboarding workflow.

A. Additional Data Collection: This is a standard step within the SAP SuccessFactors Onboarding process, used to gather further details from a new hire.

C. Compliance Forms: This is a standard step within the SAP SuccessFactors Onboarding process, where new hires complete legally required forms (e.g., I-9, W-4).

1. SAP Help Portal

"Implementing and Managing Offboarding": The guide details the Offboarding process structure. In the "Offboarding Process" section

it describes the assignment of tasks to various stakeholders

including the manager and the employee

which correspond to the "Manager Review" and "Employee Review" steps. The "Document Generation" feature is also a core component described

aligning with "Document Flow". (Document available on help.sap.com for the relevant SAP SuccessFactors release

e.g.

2H 2023).

2. SAP Help Portal

"Implementing and Managing Onboarding": This guide outlines the standard Onboarding process steps. The "Onboarding Process Overview" section explicitly lists "Additional Data Collection" and "Compliance" as distinct steps in the new hire journey

confirming they are not part of the standard Offboarding process. (Document available on help.sap.com for the relevant SAP SuccessFactors release

e.g.

2H 2023).

The Process Variant Manager in SAP SuccessFactors Onboarding is a tool used to configure and customize the sequence of steps for different onboarding processes. It allows administrators to add several types of steps to tailor the experience for various new hire groups. Among the available options, "Create New Hire Tasks" (assigning specific to-do items), "Additional Onboarding Data Collection" (gathering information beyond what was collected in recruiting), and "Compliance Forms" (processing country-specific legal and tax forms like I-9 or W-4) are all standard, configurable steps that can be managed within a process variant.

B. New Employee: "New Employee" represents the subject or participant of the onboarding process, not a configurable step or task that can be added to the process flow.

D. New Hire Verification: This is a general activity, not a distinct, configurable step. Verification activities are embedded within other standard steps, such as "Review New Hire Data" or the completion of compliance forms.

1. SAP Help Portal

SAP SuccessFactors Onboarding

"Configuring Onboarding and Offboarding Processes": This official guide details the components of an onboarding process. It explicitly lists the types of steps that can be added

including custom data collection

compliance tasks

and the creation of new hire tasks. The guide states

"You can create and manage different variants of your onboarding and offboarding programs... You can add or remove process steps based on your business requirements."

Reference Section: "Process Variant Manager" and "Process Steps in Onboarding and Offboarding."

2. SAP Help Portal

SAP SuccessFactors Onboarding

"Implementing and Managing Onboarding": This implementation guide provides a comprehensive overview of the available process steps. It describes the configuration of "Additional Data Collection" for gathering custom information

"Compliance Settings" for managing legal forms

and the "Onboarding Tasks" which can be assigned to various stakeholders.

Reference Section: "Chapter: Configuring Processes

" specifically the subsections on "Custom Data Collection

" "Compliance Settings

" and "Onboarding Tasks."

The "Administrate Onboarding or Offboarding Content" permission is the specific Role-Based Permission (RBP) required to grant an administrator access to the Onboarding/Offboarding Dashboard via the Admin Center. This dashboard is the central administrative tool used to configure and manage various aspects of the Onboarding and Offboarding processes, such as process variants, email templates, document templates, and other content-related settings. Without this permission, the link to the tool will not be visible or accessible in Admin Center.

A. Manage Onboarding or Offboarding: This permission allows a user to initiate the onboarding/offboarding process for employees and manage their progress, but it does not grant access to the administrative configuration tools.

C. Onboarding Admin Configuration Item: This is not a standard or valid permission name within the SAP SuccessFactors Onboarding RBP framework for accessing the primary administrative tools.

D. Show Onboarding Tasks Status on the Dashboard: This permission controls the visibility of the Onboarding tasks status tile on the user's homepage, which is different from accessing the configuration tools in Admin Center.

1. SAP Help Portal

Implementing and Managing SAP SuccessFactors Onboarding: "Role-Based Permissions for Onboarding". This guide explicitly states

"To access the Onboarding Dashboard (New) or Offboarding Dashboard (New) from Admin Center

you need to grant the Administrate Onboarding or Offboarding Content permission." It further clarifies that the "Manage Onboarding or Offboarding" permission is for initiating the process. (Document Version: 2H 2023).

2. SAP Help Portal

Implementing and Managing SAP SuccessFactors Onboarding: "Permission Category: Manage Onboarding or Offboarding". This section details the sub-permissions. It lists Administrate Onboarding or Offboarding Content with the description: "Grants access to the Onboarding Dashboard (New) or Offboarding Dashboard (New) from Admin Center." (Document Version: 2H 2023).

Granting Onboarding access to a future manager of an internal hire in SAP SuccessFactors requires two key configuration steps. First, the system's data model must be configured to recognize the "Future Manager" relationship. This is achieved by ensuring the appropriate relationship type exists in the jobRelType picklist. Second, Role-Based Permissions (RBP) must be configured. This involves creating a permission role with the necessary Onboarding permissions and assigning this role to the standard dynamic group "Future Manager (Internal Hire)," which automatically includes users designated as future managers for internal new hires.

B. This is incorrect because permissions are not assigned directly to a group. In the RBP framework, permissions are bundled into a role, and the role is then granted to a group.

D. This option is redundant and less precise than option A. While it describes the correct general process, option A correctly identifies the specific, standard dynamic group name, "Future Manager (Internal Hire) group."

1. SAP Help Portal

Implementing and Managing Onboarding

"Granting Permissions to Onboarding Participants": This guide outlines the standard procedure for RBP in Onboarding. It specifies creating a permission role and granting it to a permission group. It explicitly mentions using the "Future Manager (Internal Hire)" group for this specific scenario. This validates option A.

2. SAP Help Portal

Implementing and Managing Onboarding

"Permission Groups for Onboarding": This section details the standard dynamic groups available for Onboarding. It confirms the existence and purpose of the "Future Manager (Internal Hire)" group

which is foundational to the process described in option A.

3. SAP Help Portal

Implementing Employee Central Core

"Job Relationships" and "jobRelType": This documentation explains that relationship types used for RBP dynamic groups

such as "Future Manager" (standard code EH)

are defined in the jobRelType picklist. This configuration is a prerequisite for the dynamic group to function correctly

thus validating the action described in option C.

The Read Audit feature in SAP SuccessFactors Onboarding is designed to log access to sensitive personal data to comply with data privacy regulations. The scope of this audit specifically includes documents that are configured to contain sensitive data, the content of email notifications sent during the Onboarding process, and any custom data collected from new hires. This custom data is typically stored in Metadata Framework (MDF) custom objects configured for the Onboarding process. The feature ensures that any read access to this specific set of sensitive information is tracked and reportable.

A. All documents: The Read Audit feature does not log access to all documents by default; it specifically targets only those documents that are marked as containing sensitive personal data.

E. Data from Recruiting Management and Employee Central: The Onboarding Read Audit feature is scoped to data processed within the Onboarding module. Data residing in Recruiting Management or Employee Central is covered by their respective audit logs.

1. SAP Help Portal

Implementing and Managing Onboarding

"Read Audit in SAP SuccessFactors Onboarding": This guide explicitly states

"Read Audit in SAP SuccessFactors Onboarding captures read access to sensitive personal data of new hires. The data captured includes custom data collected from new hires

documents that contain sensitive personal data

and email notifications sent to new hires."

2. SAP Help Portal

Implementing Read and Change Audit Logging in SAP SuccessFactors

"Onboarding" section: This document details the scope of audit logging across the SuccessFactors suite. In the section for Onboarding

it confirms that the Read Audit functionality covers "Custom Data Collection objects

" "Documents with sensitive personal data

" and "Email notifications."

The Email Services feature within SAP SuccessFactors Onboarding is a robust tool for managing communications with new hires and internal stakeholders. It allows administrators to create new, highly customized email templates that can use business rules to dynamically populate content based on factors like the new hire's location, job, or other data (B). The system also supports configuring reminder notifications, enabling administrators to define the frequency and number of reminders sent for pending tasks, ensuring timely completion (C). Furthermore, it provides the functionality to attach relevant documents, such as welcome packets or policy forms, directly to the email notifications, enhancing the onboarding experience (E).

A. Delete a preconfigured email template:

Standard, preconfigured email templates delivered by SAP cannot be deleted to maintain system integrity. They can only be deactivated. Only custom-created templates can be deleted.

D. Trigger an onboarding task:

Email notifications are a result of a task being triggered or a process step being reached; they do not trigger the tasks themselves. Tasks are initiated by the Onboarding process flow and associated business rules.

1. SAP Help Portal: Implementing and Managing Onboarding - Email Services:

Reference for B

C

E: The "Email Services" section details the capabilities. It explicitly mentions creating custom email templates ("Creating a Custom Email Template")

using business rules for dynamic content

configuring reminders ("...you can configure the frequency of reminder notifications...")

and adding attachments ("Adding Attachments to Email Notifications").

Reference for A: The section "Managing Email Templates" clarifies that standard templates have a "Deactivate" option

while custom templates have a "Delete" option. This confirms preconfigured templates cannot be deleted.

Reference for D: The "Onboarding Process Configuration" sections describe how processes

steps

and business rules trigger tasks

while the "Email Services" section describes how notifications are sent in response to these triggers.

2. SAP Help Portal: Implementing and Managing Onboarding - Creating a Custom Email Template:

Reference for B: This guide provides step-by-step instructions on creating new email templates and using placeholders and business rules to insert locale-specific and business-specific content. "You can create custom email templates to be used in email notifications that are sent to the participants of an onboarding or offboarding process."

3. SAP Knowledge Base Article (KBA) 2874812 - How to configure Onboarding E-mail notifications - Onboarding:

Reference for C

E: This KBA outlines the configuration steps for email notifications

including setting up reminders and managing attachments for email templates within the Onboarding module. It confirms these are standard

configurable features.

The SAP SuccessFactors Onboarding rehire verification is a two-stage process designed for accuracy. The first check is triggered immediately upon the initiation of the Onboarding process, using the initial data provided (e.g., from SAP SuccessFactors Recruiting). This allows for early identification of a potential rehire. A second, more definitive check is executed after the new hire completes and submits the Personal Data Collection step. This second check uses more comprehensive and verified data, such as National ID, provided directly by the new hire, to confirm the rehire status before proceeding with the final hiring actions.

A. The check is performed at the Review New Hire Data step: This is incorrect. The rehire check occurs before this step to provide the reviewer with information about the candidate's potential rehire status.

B. The check is performed during Manage Pending Hires: This is incorrect. The Onboarding rehire check is designed to happen earlier in the process, before the candidate reaches the Manage Pending Hires tool in Employee Central.

1. SAP Help Portal

Implementing and Managing Onboarding

"Rehire with Onboarding": This official guide explicitly states the two trigger points for the rehire check. It details the process flow: "The rehire check is performed at two stages in the Onboarding process: When you initiate onboarding for a new hire. After the new hire completes the Personal Data Collection step."

2. SAP Help Portal

Implementing and Managing Onboarding

"Rehire Verification": This section details the configuration and logic of the rehire check process

confirming that the system performs checks at both initiation and after the new hire provides their personal data. It clarifies that the first check uses data from the source (like Recruiting) and the second uses the new hire's submitted data.