SAP C_THR97_2411 - SAP Certified Associate - Implementation Consultant - SAP SuccessFactors Onboarding

Auto-archiving Offboarding tasks in SAP SuccessFactors ensures that completed tasks are stored efficiently, maintaining system performance and compliance with data retention policies. This process involves configuring rules and scheduling jobs to automate archiving.

According to the SAP SuccessFactors Offboarding Configuration Guide:

Create a business rule that identifies the Offboarding tasks to archive(Option B): A business rule is configured inConfigure Business Rulesto define criteria for identifying completed Offboarding tasks (e.g., tasks older than a specified period) that are eligible for archiving.

Create a scheduled batch job from Provisioning that archives the Offboarding tasks(Option D): A scheduled batch job is set up inProvisioningto automatically archive the identified Offboarding tasks based on the business rule, ensuring regular cleanup of the system.

Option A (Create a scheduled batch job from the front-end system) is incorrect because batch jobs for archiving are configured in Provisioning, not the front-end system (Admin Center). Option C (Enable Archive & Print in Provisioning) is incorrect because Archive & Print is unrelated to task archiving; it pertains to document generation.

To map document fields to custom data collection fields in SAP SuccessFactors Onboarding, you need to link the fields in the uploaded document template to the fields in a custom MDF (Metadata Framework) object used for data collection. This is done through theMaintain Onboarding and Offboarding Document Templatestool in Admin Center.

According to the SAP SuccessFactors Onboarding Implementation Guide:

Choose the MDF custom object as the base object(Option A): The custom MDF object, created inConfigure Object Definitions, serves as the base object for the data collection fields. You select this object to map its fields to the document template.

Select the fields from the MDF custom object in the Target Field column(Option C): In the mapping configuration, you specify the target fields from the MDF custom object that correspond to the document fields, ensuring data is correctly captured.

Select Direct in the Mapping Type column(Option D): TheDirectmapping type is used to establish a one-to-one relationship between the document field and the MDF object field, allowing data to flow directly from the form to the system.

Option B (Select Rule in the Mapping Type column) is incorrect because theRulemapping type is used for dynamic calculations or conditions, not for standard field mapping. Option E (Create a business rule) is incorrect because business rules are used for validation or triggering actions, not for mapping document fields to MDF fields.

Adding a Final Review step in SAP SuccessFactors Onboarding ensures that all collected data is reviewed before completing the process. This step can be configured through specific tools and settings to assign responsibilities and enable the feature.

According to the SAP SuccessFactors Onboarding Implementation Guide:

Add the Final Review step using Process Variant Manager(Option A): TheProcess Variant Managerallows administrators to customize the onboarding process by adding a Final Review step, defining its tasks and sequence within the process flow.

Define a business rule using the Assign Responsible Group for Data Review(Option B): A business rule, configured inConfigure Business Rules, is used to assign the Final Review step to a responsible group (e.g., HR or hiring manager) to ensure the appropriate users review the data.

Enable Final Review in Onboarding General Settings(Option C): The Final Review step must be enabled inOnboarding General Settingsto activate it as part of the onboarding process, allowing it to be included in the process flow.

Option D (Add the task participation configuration business rule to the DEFAULT_ONB2_CONFIG) is incorrect because task participation is managed through specific rules, not theDEFAULT_ONB2_CONFIGobject. Option E (Add the Personal Data Collection step) is incorrect because Personal Data Collection is a separate step, not related to adding a Final Review step.