C_THR81 Employee Central Core Practice Question
An Employee Central administrator is configuring the 'Event Reason' foundation object. The company wants to derive the event reason automatically when an employee's Job Information is updated, based on the type of change (e.g., promotion, transfer, termination). Which configuration approach should the administrator use to meet this requirement?
⚠ Common exam trap
The trap here is assuming that event reasons can be automatically derived through picklist filtering or scheduled jobs, when in fact they require a business rule to evaluate the change context.
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 on the Job Information object that sets the event reason based on the change type, and associate it with the 'onSave' event.
The correct approach is to use a business rule on the Job Information object that triggers on save. This allows the system to evaluate the changed fields and automatically set the appropriate event reason. It ensures real-time, accurate derivation without manual intervention, meeting the requirement for automatic determination based on the type of change.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use a workflow rule to send a notification to the HR team to manually update the event reason after the job change.
Why it's wrong here
This approach relies on manual intervention, which is error-prone and does not meet the requirement for automatic derivation. Workflow notifications are for alerting, not for setting field values. The scenario asks for automatic determination based on the change type, so a manual step is not acceptable.
- ✗
Set up a scheduled job that runs nightly to update event reasons based on the latest job information changes.
Why it's wrong here
A nightly batch job would delay the event reason assignment and may not capture the context of the change accurately. Event reasons are typically required at the time of the transaction. Scheduled jobs are suitable for periodic data syncs, not for real-time derivation during job changes. This would create a lag and potential data inconsistency.
- ✗
Configure the Event Reason object with a picklist that filters values based on the employee's country.
Why it's wrong here
Filtering event reasons by country does not automatically derive the correct reason based on the type of job change. It only limits available options, requiring manual selection. The requirement is to derive the reason automatically, not to restrict the list. Picklist filtering is useful for data validation but not for dynamic assignment based on change context.
- ✓
Create a business rule on the Job Information object that sets the event reason based on the change type, and associate it with the 'onSave' event.
Why this is correct
A business rule on Job Information triggered on save can evaluate the changed fields and assign the appropriate event reason. This is the standard way to derive event reasons dynamically during job data changes, ensuring accuracy and reducing manual selection. It leverages the rule engine's ability to inspect previous and current values.
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.