C_THR81 Employee Central Core Practice Question
An Employee Central administrator is configuring the 'Job Information' portlet and needs to ensure that the field 'Employee Class' is automatically populated based on the selected 'Company' and 'Business Unit'. The administrator wants to use a business rule to set the default value. Which trigger type should be used for this business rule?
⚠ Common exam trap
A common mix-up: candidates confuse OnChange with OnSave or OnInit, assuming any trigger can set default values, but only OnChange reacts to field changes before save.
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
The OnChange trigger evaluates a business rule when a designated field's value changes, enabling dynamic updates to other fields on the same object. In this scenario, selecting a Company or Business Unit should immediately populate Employee Class, which requires the rule to execute during data entry, not after save. OnChange is designed for this dependency, ensuring the field is set before the user submits the form.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
OnSave
Why it's wrong here
OnSave triggers after the user saves the record, so it cannot set a default value before the user sees the form. It is used for validation or post-save actions, not for dynamic defaulting. In this scenario, the requirement is to populate a field based on other selections, which must happen before save, so OnSave is incorrect.
- ✓
OnChange
Why this is correct
OnChange triggers when a specified field changes, allowing the rule to set another field's value dynamically. Here, when Company or Business Unit changes, the rule can set Employee Class. This meets the requirement to automatically populate based on selections. OnChange is the correct trigger for dependent defaulting.
- ✗
OnPostSave
Why it's wrong here
OnPostSave triggers after the record is saved, so it cannot set a field value before save. It is used for actions like sending notifications or updating related objects after save. Since the requirement is to populate Employee Class before the user saves, OnPostSave is not appropriate.
- ✗
OnInit
Why it's wrong here
OnInit triggers when the rule is first loaded, not when a field changes. It is used to set initial values on page load, but it will not react to subsequent changes in Company or Business Unit. Therefore, it cannot dynamically update Employee Class based on user selections, making it unsuitable for this scenario.
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.