SAP C-THR81-2311 Value Pack (Frequently Bought Together)

Your customer would like to automate its company's HR transactions. This includes auto-populating fields to reduce data entry errors and automating approvals during self-service transactions.
You are asked to create the following rules based on your customer's requirements:
* Three event reason derivation rules (ERD1, ERD2, ERD3)
* A separate catch-all event reason derivation rule (ERD-Catch)
* A workflow derivation rule based on event reasons (WFD)
* A rule to auto-populate the Job Title. Pay Grade, and Employee Class field values in the Job Information whenever the job code is changed (Defauit_JobClass)
* A rule to use AddressChange workflow for any address change requests (WFD_Address)
* A cross-entity rule to auto-calculate the Base_Salary amount based on ) changes to the FTE value for any event other than Hire or Rehire (Joblnfo_FTE_Comp) Answer the questions to ensure the event reasons and workflow rules adhere to SAP SuccessFactors recommended practices.
Which clause meets the WFD_Address rule requirement?

• A.
  
• B.
  
• C.
  
• D.
  

You want the Timezone field to be pre-populated when the location record is changed in Job Info. How do you configure this?

• A. Base Object: Location; Assigned to Timezone field as onChange
• B. Base Object: Job Information; Assigned to Timezone field as onChange
• C. Base Object: Location; Assigned to Timezone field as onSave
• D. Base Object: Job Information; Assigned to Location field as onChange

Which of the following are possible options when working with SAP SuccessFactors Employee Central employee identifiers? Note: There are 3 correct answers to this question.

• A. A user can have multiple user ids.
• B. A user can have only one user id.
• C. Once generated, you CANNOT change a user id.
• D. Once generated, you CANNOT change a person id external.
• E. A user can have only one person id external.

How do you set the Event Reason Derivation rule to ensure event reasons are NOT overwritten?

• A. Set the IF statement to check if the event reason value is NOT NULL and set the THEN statement as blank.
• B. Set the IF statement to check if the event reason value is NULL and set the THEN statement as blank.
• C. Set the IF statement to Always True and set the THEN statement as blank.
• D. Set the IF statement to check if the event reason value is blank and set the THEN statement to NULL.

This is a global customer and HR admins will be assigned based on legal entity. The HR admins should be getting approval workflows from their target population. How can you define this in one workflow?

• A. Create a dynamic role for each legal entity and assign the Resolver as the head of the legal entity.
• B. Create permission groups for each legal entity and assign them to the HR admin role.
• C. Create a dynamic role using the Legal Entity filter and assign the Resolver type as dynamic group.
• D. Create dynamic groups per each legal entity and add the necessary approver steps.