C_THR81 Employee Central Core Practice Question
A consultant is configuring the 'Employment Type' Foundation Object. The company wants to ensure that when an employee is terminated, the Employment Type remains valid for historical reporting but cannot be selected for new hires. Which approach should the consultant take?
⚠ Common exam trap
The trap here is thinking that deleting the record or adding a validation rule is the way to retire a value, when the native mechanism is to set the record's status to inactive.
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
✓
Set the Employment Type record's status to inactive.
Inactivating the Employment Type record is the correct approach. It removes the value from selection lists for new entries while keeping it available for existing and historical employee records, which preserves reporting integrity. Deleting the record, removing the field, or relying on a validation rule would either destroy history or fail to prevent selection cleanly.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Set the Employment Type record's status to inactive.
Why this is correct
Setting a Foundation Object record to inactive removes it from selection lists for new entries while preserving it for existing and historical records. This satisfies the requirement that the value remains valid for historical reporting but cannot be chosen for new hires. Inactivation is the standard lifecycle mechanism for Foundation Object records in Employee Central.
- ✗
Delete the Employment Type record once it is no longer used.
Why it's wrong here
Deleting the record would remove it from historical employee data, breaking reporting and potentially causing errors in records that reference it. Employee Central retains historical values for a reason, and deleting Foundation Object records that are in use is not supported without impacting data integrity. The requirement is to prevent future selection, not to erase history.
- ✗
Create a business rule that blocks selection of the Employment Type for new hires only.
Why it's wrong here
A business rule could validate the value on new hires, but it is a more complex and less reliable approach than using the record's status. It would not remove the value from the selection list, so users could still attempt to choose it. The native mechanism for retiring a Foundation Object value is inactivation, not a validation rule.
- ✗
Remove the Employment Type field from the Job Information portlet configuration.
Why it's wrong here
Removing the field from the portlet would hide it entirely, including for historical records, and would not allow the value to be retained for reporting. It also affects all employees, not just new hires. The requirement is to stop future selection while keeping history, which field removal cannot achieve.
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.