A person has one Payroll Relationship and two assignments. Each assignment has two different departments. Each department is associated with a…

The Oracle Payroll costing hierarchy determines which costing information takes precedence. To override the default costing derived from the two different departments, you must define costing at a more specific level for the person. The Person-Payroll Relationship level is more specific than the Department level and will apply a single cost center to all assignments and earnings for that person. The Element Entry level is the most specific level in the hierarchy; setting costing here for all of the person's elements would also override the department-level costing and consolidate all costs to the specified cost center.

B. Payroll level costing is lower in the hierarchy than Department level costing. Therefore, the department costing would override the payroll costing, failing to meet the requirement.

C. This statement is incorrect. The costing hierarchy is a fundamental feature of Oracle Payroll designed specifically to allow for overrides at multiple levels.

1. Oracle Cloud HCM - Implementing Payroll Core

Chapter: Payroll Costing

Section: Costing Hierarchy.

This section details the complete costing hierarchy. It explicitly lists the levels in order of precedence

showing that Element Entry and Person-Payroll Relationship levels are more specific than the Department level

and will therefore override it. It also shows the Payroll level is less specific than the Department level. The order is: Element Entry

Person Element

Person Assignment

Person-Payroll Relationship

Position

Job

Department

Payroll

Element

Legal Employer.

2. Oracle Cloud HCM - Using Payroll

Chapter: Payroll Costing

Section: Payroll Costing of a Person.

This document explains how to set up costing for a person at different levels

including the payroll relationship and element entry. It states

"You can enter costing at different levels for a person. The application uses the most detailed level first. For example

if you enter costing at the assignment and payroll relationship levels

the application uses the assignment level costing." This confirms that setting costing at a more specific level (like A or D) overrides a general level (like Department).