Learn, Practice, and Improve with SAP C_THR97_2405 Practice Test Questions

Explanation:

The "Final Review" is an optional step in SAP SuccessFactors Onboarding that allows an administrator or a specific participant group to verify all data collected during the onboarding process (from both the recruiter and the new hire) before the record is sent to Employee Central.

Process Variant Manager (A):
This is the core tool used to define the "backbone" of your onboarding flow. To include a Final Review, you must manually add the Final Review step into your specific process flow (or variant) within the Process Variant Manager. Without this, the step simply won't exist in the sequence.

Assign Responsible Group for Data Review (B):
Because the Final Review is a manual task, the system needs to know who is responsible for completing it. You must create a business rule using the Assign Responsible Group for Data Review scenario to define the specific group (e.g., HR Operations) that will receive this task on their dashboard.

DEFAULT_ONB2_CONFIG (D):
For any task in Onboarding to trigger and appear for a user, the system must evaluate a participation rule. You must link your task participation business rule to the DEFAULT_ONB2_CONFIG (Onboarding Configuration) object. This tells the engine under what conditions the Final Review task should be generated for a specific new hire.

Why the Other Options are Incorrect

C. Enable Final Review in Onboarding General Settings:
There is no "toggle switch" in General Settings to enable this. It is a structural process change that must be configured via the Process Variant Manager.

E. Add the Personal Data Collection step...:
While Personal Data Collection is a valid step, adding it does not create a "Final Review." They are two distinct steps in the process; Personal Data Collection is for the candidate to provide info, while Final Review is for an internal user to audit it.

References

SAP SuccessFactors Onboarding Implementation Guide: Refer to the section "Configuring the Final Review Step," which outlines the use of Process Variant Manager and the specific business rules required.

Explanation:

In SAP SuccessFactors Onboarding, "Email Services" does not have a native "custom token builder" inside the email editor itself. Instead, it leverages the Document Generation engine to fetch and map data from the Onboarding/EC objects.

Document Generation (D):
To create custom tokens, you must first create a "placeholder" template in Document Generation. Even if you aren't actually generating a PDF, this tool acts as the data provider for the email system.

Mapping Fields (C):
Once the template is created in Document Generation, you must perform Document Generation Field Mapping. Here, you link your custom placeholders (tokens) to the actual data fields in the Onboarding or Employee Central data models.

Format {fieldID} (E):
In the Email Services editor, when you want to call that specific piece of data into an email body or subject line, you use the curly bracket syntax (e.g., {PersonalData.firstName}). The system then uses the mapping created in the previous steps to populate the value.

Why the Other Options are Incorrect

A & B (Maintain Onboarding Offboarding Document Templates):
This tool is part of the legacy Onboarding 1.0 architecture or used specifically for Forms/PDFs. For modern Onboarding (2.0) Email Services, the Document Generation framework (MDF-based) is the standard for tokenization. Adding "field names to the content" of a PDF template will not automatically make them available as email tokens.

References:
SAP SuccessFactors Onboarding Implementation Guide: Refer to the section "Using Document Generation for Email Tokens."

Explanation:

While Offboarding is highly configurable using the Process Variant Manager, the standard "out-of-the-box" steps designed to facilitate a smooth departure are:

Manager Review (E):
This is typically the first step after Offboarding is initiated (either from Employee Central or an external system). The manager or an HR admin reviews the termination details, confirms the last working day, and may provide additional info required for the process.

Employee Review (B):
Similar to the "Personal Data Collection" in Onboarding, this step allows the departing employee to review their information, provide a forwarding address, and confirm details related to their departure.

Document Flow (D):
This step handles the generation and signing of necessary termination documents, such as resignation acceptance letters, severance agreements, or non-disclosure reminders. It uses the same e-signature framework (DocuSign or SAP native) as the Onboarding module.

Why the Other Options are Incorrect

A. Additional Data Collection:
While "Personal Data Collection" is a staple of Onboarding, "Additional Data Collection" as a named standard step is not part of the default Offboarding sequence. Data is generally gathered during the Review steps.

C. Compliance Forms:
While compliance is critical, in the context of the standard 2.0 (New) Offboarding process, "Compliance" is a specialized engine often associated with Onboarding-specific tax forms (like the US I-9 or W-4). In Offboarding, legal documents are typically handled via the Document Flow.

References
SAP SuccessFactors Offboarding Implementation Guide: Refer to the "Standard Process Steps in Offboarding" section, which lists the Review and Document steps as the primary milestones.

Explanation:

The Clean Core Dashboard is a strategic tool designed to help customers monitor their adherence to "Clean Core" principles, ensuring their systems remain upgrade-stable and efficient.

Accessed via SAP For Me (B):
The dashboard is hosted on the SAP For Me portal under the "Customer Insights" or "Systems & Provisioning" sections. It provides a centralized view of various metrics, such as extensibility, integration, and data quality, without requiring a direct login to the specific S/4HANA tenant.

Grant Access to Partners (D):
SAP allows customers to manage permissions for the dashboard. Since many customers rely on implementation partners to maintain their systems, customers can explicitly grant access to their designated Partner contact persons so they can monitor "Clean Core" compliance and remediate issues.

Why the Other Options are Incorrect

A. Customers can use the dashboard in dev, test, and production:
While the dashboard analyzes data from these environments, it is not an "in-app" tool used within the tenants themselves. It is a cloud-based reporting interface external to the specific tenant landscapes.

C. It can be used in all SAP S/4HANA Cloud editions:
Currently, the Clean Core Dashboard is specifically tailored for SAP S/4HANA Cloud, public edition and SAP S/4HANA Cloud, private edition. It is not universally applicable to all legacy or on-premise "editions" in the same standardized format provided through SAP For Me.

References:

SAP Support Portal: Search for "Clean Core Dashboard in SAP For Me" to see the access requirements and permission settings.

Explanation:

To achieve a Clean Core, SAP recommends using cloud-compliant, stable, and well-defined APIs that allow for "side-by-side" extensibility. This ensures that integrations do not break during automated system upgrades.

OData (A):
This is the primary recommendation for modern SAP integrations. OData (Open Data Protocol) is REST-based and provides a standardized way to query and manipulate data. It is the backbone of SAP Fiori and SAP Business Technology Platform (BTP) integrations.

SOAP (B):
While older than OData, SOAP (Simple Object Access Protocol) is still considered a "Clean Core" compliant integration type when using White-listed Enterprise Services. These services are officially supported and stable, ensuring the core remains "clean" from custom-coded modifications.

Why the Other Options are Incorrect

C. RFC (Remote Function Call):
RFCs are often considered "unmanaged" or "legacy" in a cloud context. While still used, they are not the recommended path for a Clean Core because they often require direct access to the backend and lack the standardized web-protocol wrappers found in OData or SOAP.

D. IDoc (Intermediate Document):
IDocs are a legacy SAP technology. While very common in on-premise systems, they are not "Cloud Native." For a Clean Core strategy, SAP pushes users toward Event-Based architectures or OData services rather than the asynchronous, file-like structure of IDocs.

References
SAP Extensibility Guide for SAP S/4HANA Cloud: Highlights the shift from "Classic" integrations (RFC/IDoc) to "Clean" integrations (OData/SOAP).

Explanation:

To prevent the Offboarding dashboard from becoming cluttered with completed or cancelled records, SAP SuccessFactors uses a two-part automated mechanism to move records to the archive.

Business Rule (C):
You must first define the logic that tells the system which records are eligible for archiving. This rule typically checks for conditions such as the "Process Status" being equal to "Completed" or "Cancelled," and can include a specific number of days after the termination date. This rule is then assigned to the Offboarding Configuration object.

Scheduled Batch Job in Provisioning (D):
While the business rule identifies the "who," the batch job provides the "when." A consultant must set up a specific background job in Provisioning (the backend administrative tool) called "Offboarding Auto Archive." This job runs on a recurring schedule (e.g., daily) to process all records that meet the criteria defined in your business rule.

Why the Other Options are Incorrect

A. Create a scheduled batch job from the front-end:
Most heavy-duty data processing and archiving jobs in SuccessFactors are still managed via Provisioning rather than the "Scheduled Job Manager" in the Admin Center (front-end), especially for the core Offboarding module logic.

B. Enable Archive & Print in Provisioning:
This is a legacy feature primarily associated with the older Onboarding 1.0 architecture or specific document handling. It does not control the modern Offboarding 2.0 task archiving process.

References
SAP SuccessFactors Offboarding Implementation Guide: Refer to the "Archiving Offboarding Tasks" section, which details the requirement of the OBD2_Config object and the backend job.

Explanation:

In SAP SuccessFactors Onboarding, "Email Services" does not create tokens independently. Instead, it relies on the Document Generation framework to "bridge" data from the system into the email.

Document Generation - Manage Document Template (D):
You use this tool to create the base template where you define your custom placeholders (e.g., [[CUSTOM_VACATION_DAYS]]). This acts as the container for your tokens.

Document Generation - Manage Document Template Mapping (E):
After creating the template, you must map those placeholders to actual data fields. This tool allows you to link your custom token to a specific field in the Onboarding or Employee Central data model.

Business Rules (C):
Business rules are often required during the mapping process (Option E) to define complex logic for a token. For example, if you want a token to display a value based on a "calculated" condition rather than a static field, you write a business rule to determine that value.

Why the Other Options are Incorrect

A. Maintain Onboarding Offboarding Document Templates:
This is primarily used for PDF/Form generation (often associated with legacy Onboarding 1.0) and is not the standard tool for creating tokens for the modern Email Services.

B. Email Services:
This is the tool where you use the tokens (by inserting them into the email body), but it is not the tool where you create or define the underlying data mapping for custom tokens.

References
SAP SuccessFactors Onboarding Implementation Guide: See the section "Configuring Custom Tokens for Email Services."