1Z0-548 · Question #34
The XYZ Organization has two leave types: Special Leave and Vacation Leave. Whenever leave is applied for, regardless of the leave type used, the accrual must be reduced from the same accrual plan…
The correct answer is B. Create two leave types and associate the same element to both the leave types. Attach this C. Add both the leave types in the net calculation rules of the accrual plan with the net effect on. Options B and C represent the two standard Oracle HCM configuration approaches for linking multiple leave types to a single accrual plan. Option B works by associating both leave types with the same absence element - since the accrual plan is attached to the element, any leave…
Question
The XYZ Organization has two leave types: Special Leave and Vacation Leave. Whenever leave is applied for, regardless of the leave type used, the accrual must be reduced from the same accrual plan, i.e. the Annual Leave Accrual Plan. Identify the two ways in which this can be achieved.
Options
- ACreate two accrual plans with the same name and associate the two leave types with the accrual
- BCreate two leave types and associate the same element to both the leave types. Attach this
- CAdd both the leave types in the net calculation rules of the accrual plan with the net effect on
- DBoth the leave types need to be created with absence reason: Annual Leave Accrual Plan.
- EEnable the Additional Absence Details DFF in the Absence Entry Form and store the accrual plan
How the community answered
(60 responses)- A2% (1)
- B83% (50)
- D10% (6)
- E5% (3)
Explanation
Options B and C represent the two standard Oracle HCM configuration approaches for linking multiple leave types to a single accrual plan. Option B works by associating both leave types with the same absence element - since the accrual plan is attached to the element, any leave type using that element will automatically reduce the same accrual balance. Option C works from the accrual plan side: by adding both leave types as entries in the plan's net calculation rules with a negative net effect, the plan itself knows to deduct from its balance whenever either leave type is used.
Why the distractors fail: A is wrong because naming two separate plans identically doesn't merge them - they remain distinct plans and the problem is unsolved. D is wrong because "absence reason" is a descriptive classification field, not a mechanism for routing accrual deductions. E is wrong because a DFF (Descriptive Flexfield) is a data storage tool; storing accrual plan info in a custom field doesn't trigger any system deduction logic without custom development.
Memory tip: Think of it as "meet in the middle" - B connects both leave types to the element (bottom-up), while C tells the accrual plan to recognize both leave types (top-down). Either way, the two sides get connected.
Topics
Community Discussion
No community discussion yet for this question.