Which statement best describes the correct costing hierarchy sequence for a costed element?

• A. Element Eligibility, Payroll, Department, Job or Position, Person, Element Entry
• B. Payroll, Department, Job or Position, Element Eligibility, Person, Element Entry
• C. Payroll, Element Eligibility, Department, Job, Position, Person, Element Entry
• D. Payroll, Person Element Entry, Department, Job or Position, Person, Element Eligibility

Answer: (C)

The thing being tested is the order in which Oracle Payroll Cloud looks up costs for a costed element—the costing hierarchy. The correct sequence starts with the payroll context, because cost calculations are tied to a specific payroll run. Right after that, Element Eligibility determines whether the element applies to the worker in that scenario; if the element is eligible, that cost source is used. If not, the system then checks organizational dimensions in order of specificity: department first, then job or position, then the person themselves. If no higher-level cost source provides a value, the system finally falls back to the actual element entry, which can specify a cost at the line-item level. This cascading order lets you set broad costs at organizational levels and override them with more specific, individual-level costs only when needed, with the element entry providing the last resort.

Other sequences don’t fit this flow. Placing Element Eligibility after other levels or introducing unusual terms like a combined “Person Element Entry” misrepresents how the hierarchy is evaluated, and checking Element Entry earlier would bypass the progressive specificity intended by the cascade.