C_THR81 Employee Central Core Practice Question
An EC administrator is configuring a new MDF object called 'Employee Recognition' that must allow multiple records per employee AND be associated to a specific employee via a field. Which configuration should be used to ensure proper linkage to the employee?
⚠ Common exam trap
The trap here is assuming that any field that can store an employee identifier, such as a String or Number field, is sufficient for linking to the Employee object, when only an Association field provides the required referential integrity.
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 field of type 'Association' and set the 'Valid Values' to the Employee object.
The correct approach is to use an Association field type with Valid Values set to the Employee object. This creates a proper linkage between the 'Employee Recognition' MDF object and Employee Central employee records, ensuring data integrity and enabling multiple recognition entries per employee. Other field types do not establish the necessary object relationship.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Create a field of type 'String' and manually enter the employee ID.
Why it's wrong here
A String field would store text, not a true association. It would not enforce referential integrity or enable navigation to the employee record. While it could hold an employee ID, it lacks validation and would not support features like picklists or automatic updates if the employee ID changes. This is not the correct method for linking MDF objects.
- ✓
Create a field of type 'Association' and set the 'Valid Values' to the Employee object.
Why this is correct
An 'Association' field type is specifically designed to link one MDF object to another, such as Employee. By setting Valid Values to the Employee object, the field will reference employee records. This ensures the recognition record is associated with the correct employee, and multiple records can be created per employee because the object is configured as a detail object.
- ✗
Create a field of type 'User' and set the 'Valid Values' to the employee's user ID.
Why it's wrong here
A field of type 'User' is used for system users (e.g., administrators), not for employee records. It would not link to the Employee Central employee data. Valid Values for a User field typically reference user IDs, which are not the same as employee IDs. This would not establish the required association to the employee MDF object.
- ✗
Create a field of type 'Number' and store the employee's numeric ID.
Why it's wrong here
A Number field can store numeric employee IDs but does not create a relationship to the Employee object. It would not provide a lookup or validation against existing employee records. This approach is error-prone and does not leverage MDF association capabilities, making it unsuitable for linking recognition records to employees.
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.