C_THR81 Employee Central Core Practice Question
An administrator is configuring the Employee Central 'Job Information' portlet. The company requires that when an employee's 'Employee Class' is changed to 'Executive', the 'Bonus Plan' field must be automatically set to 'Executive Plan'. Which configuration achieves this requirement with minimal maintenance?
⚠ Common exam trap
Many candidates confuse picklist dependencies with automatic field population; dependencies only filter options, they do not set values.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Create a business rule that triggers on change of Employee Class and sets the Bonus Plan field to 'Executive Plan' when the new value is 'Executive'.
A business rule on the Job Information object that triggers when Employee Class changes is the most efficient way to automatically set the Bonus Plan field. It ensures immediate consistency, applies to all employees, and requires minimal ongoing maintenance. Other options either do not automate the population or involve inappropriate tools like workflows or picklist dependencies.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Configure a picklist dependency so that the 'Bonus Plan' field only shows 'Executive Plan' when Employee Class is 'Executive'.
Why it's wrong here
Picklist dependencies filter available options in a dropdown based on another field's value, but they do not automatically set a value. The user would still need to manually select 'Executive Plan'. This does not meet the requirement for automatic population and could lead to inconsistent data if the user forgets to select the value.
- ✓
Create a business rule that triggers on change of Employee Class and sets the Bonus Plan field to 'Executive Plan' when the new value is 'Executive'.
Why this is correct
A business rule triggered on the Job Information object when Employee Class changes can conditionally set the Bonus Plan field. This is the standard, low-maintenance approach because it centralizes the logic and automatically applies to all employees without manual intervention. It leverages the platform's rule engine and is easily adjustable if the mapping changes.
- ✗
Use a workflow rule that triggers on save of Job Information and updates the Bonus Plan field.
Why it's wrong here
Workflow rules are designed for approval processes and notifications, not for automatic field updates. They cannot directly set field values on the same record. While a workflow could trigger a subsequent update, it would be indirect and require additional configuration, increasing maintenance and complexity.
- ✗
Set the default value of the 'Bonus Plan' field to 'Executive Plan' and make it read-only for Executives.
Why it's wrong here
Setting a default value applies only to new records, not when an existing employee's Employee Class changes. Making the field read-only based on Employee Class would require conditional field-level security, which is complex and does not automatically populate the value. This approach fails to update existing records and lacks automation.
About these practice questions
One of 108 original C_THR81 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official SAP exam blueprint
This C_THR81 practice question is part of Courseiva's free SAP certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the C_THR81 exam.