C_THR81 Employee Central Core Practice Question
A consultant is configuring the Employee Central 'Job Information' portlet. The company requires that when an employee's 'Employee Class' is set to 'Executive', the 'Bonus Plan' field becomes mandatory. The consultant decides to use a business rule on the Job Information object. Which trigger event should the business rule use to enforce this requirement?
⚠ Common exam trap
The trap here is assuming that OnSave is the correct event for all validations; however, conditional mandatory fields require OnChange to react dynamically as the user edits the record.
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
✓
OnChange
To conditionally make a field mandatory based on another field's value, the business rule should trigger on the change of the controlling field. The OnChange event on the 'Employee Class' field allows the rule to set the 'Bonus Plan' field as required immediately, ensuring the user cannot save without providing the bonus plan when the employee class is executive.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
OnChange
Why this is correct
The OnChange event triggers when a specified field changes, such as 'Employee Class'. This allows the business rule to immediately set the 'Bonus Plan' field as mandatory when 'Employee Class' becomes 'Executive'. This dynamic behavior ensures the user is prompted to fill the field before saving, which is exactly what the scenario requires.
- ✗
OnSave
Why it's wrong here
The OnSave event fires when the Job Information record is saved, but it may not be the best choice for making a field mandatory based on another field's value. The requirement is to enforce mandatory status dynamically; using OnSave might allow the user to save without filling the field if the rule is not properly designed to validate before save. However, in Employee Central, making a field mandatory conditionally is typically done with a rule that triggers on change and sets the field as required.
- ✗
OnPostSave
Why it's wrong here
OnPostSave executes after the record is saved. Making a field mandatory after save is too late; the data is already persisted. The requirement is to prevent saving without the bonus plan when the employee class is executive. Therefore, a post-save event cannot enforce the mandatory field at the point of data entry.
- ✗
OnInit
Why it's wrong here
OnInit fires when the Job Information portlet is initialized, before any user interaction. It cannot react to a user changing the 'Employee Class' field. Therefore, it is unsuitable for conditionally making another field mandatory based on user input. The rule would not trigger when the employee class is changed, so the mandatory requirement would not be enforced.
About these practice questions
Courseiva writes every C_THR81 question from scratch — 108 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. 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.