C_THR81 Employee Central Core Practice Question
A SuccessFactors administrator is configuring the Employee Central Foundation Object 'Department' and needs to prevent employees from selecting obsolete department codes that are no longer in use, while preserving the historical assignments on existing employee records. What is the recommended approach in Employee Central?
⚠ Common exam trap
The trap here is assuming that obsolete Foundation Object values must be deleted, when Employee Central's design preserves referenced records and expects status changes instead.
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 status of the obsolete Department records to Inactive in the Manage Data interface.
Setting the Department Foundation Object record to Inactive is the correct way to retire a value while preserving existing employee assignments. Inactive records remain valid for historical references but are excluded from the selection list for new entries, which directly satisfies both parts of the requirement.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Delete the obsolete Department records from the Manage Data interface.
Why it's wrong here
Deleting Foundation Object records is blocked when they are referenced by existing employee Job Information records; even if deletion were possible, it would break historical reporting and data integrity. Deletion is not the mechanism for retiring values while preserving history.
- ✓
Set the status of the obsolete Department records to Inactive in the Manage Data interface.
Why this is correct
Inactivating the Department Foundation Object record prevents it from appearing in the picklist for new assignments while keeping it available for existing employee Job Information records that already reference it. This is the standard EC pattern for retiring Foundation Object values without breaking historical data.
- ✗
Configure a business rule that hides the Department field when an obsolete code is selected.
Why it's wrong here
Hiding the field after selection does not prevent the obsolete value from being chosen and saved. The requirement is to stop obsolete codes from being selectable for new assignments, which a post-selection visibility rule cannot achieve.
- ✗
Create a new Department picklist and assign it to the Job Information Department field.
Why it's wrong here
The Department field in Job Information is backed by the Department Foundation Object, not a generic picklist. Replacing it with a picklist would break the object relationship, MDF associations, and reporting that depends on the Foundation Object structure.
About these practice questions
This C_THR81 question is part of Courseiva's 108-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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.