C_THR81 Employee Central Core Practice Question
An administrator needs to create a new MDF object to track employee visas. The object must store visa type, issue date, expiry date, and a document attachment. The administrator wants to ensure that when a visa record is created, the expiry date cannot be earlier than the issue date. Which validation rule type should be used in the MDF object configuration?
⚠ Common exam trap
The trap here is assuming that field-level validation properties can compare values across fields, when they can only validate the field in isolation.
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 of type 'onSave' that compares the two dates and throws an error if expiry is before issue.
To enforce that the expiry date is not earlier than the issue date, a business rule on the MDF object with an onSave trigger is required. The rule can compare the two date fields and throw an error if the condition is violated. This is the standard approach for cross-field validation in MDF objects, as simple field properties cannot reference other fields.
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 expiry date field as a required field and rely on users to enter it correctly.
Why it's wrong here
Making the field required only ensures it is populated; it does not validate the relationship between the two dates. Users could still enter an expiry date earlier than the issue date. This option does not provide any validation logic, so it fails to meet the requirement.
- ✗
Configure a picklist dependency between issue date and expiry date.
Why it's wrong here
Picklist dependencies are used to filter values in picklist fields based on another picklist's selection. They do not apply to date fields and cannot enforce date comparisons. This option is irrelevant to the requirement of validating that expiry is not before issue.
- ✓
Create a business rule of type 'onSave' that compares the two dates and throws an error if expiry is before issue.
Why this is correct
Business rules with an onSave trigger can validate field values and prevent saving if conditions are not met. In this case, the rule would compare the expiry date to the issue date and raise an error if the expiry is earlier. This is the standard method for implementing cross-field validation in MDF objects in Employee Central.
- ✗
Use the 'Validation' property on the expiry date field to enforce it must be after the issue date.
Why it's wrong here
The Validation property on a field allows simple validations like minimum or maximum values, but it cannot reference another field dynamically. It cannot compare to the issue date, which varies per record. Therefore, this property cannot enforce the cross-field rule required in the 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.