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 * 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 condition must be used for the JobInfo_FTE_Comp rule? A) B) C) D)
An HR admin/Global Mobility person must create a transfer for an employee. The employee will be moving from Position A in Team A to Position B in Team B. Both managers will have to approve the transfer. How do you configure a two-step workflow so that the approval goes first to the current manager and second to the future manager?
You have updated several position departments using Import and Export data, but the incumbent's data still shows the previous information for the department hris-field. What are some possible causes for this data inconsistency? Note: There are 2 correct answers to this question.
Which method of modifying employee data will trigger an event reason derivation?
How do you create country/region-specific fields (CSF) for a country that does NOT have pre-delivered Legal Entity CSF fields? Note: There are 3 correct answers to this question.
