My Oracle Support Banner

Costing Process Slow After Upgrading to 12.1 HRMS RUP 3 (Doc ID 1482543.1)

Last updated on FEBRUARY 27, 2019

Applies to:

Oracle Payroll - Version 12.1.3 and later
Information in this document applies to any platform.


The Costing process is slow after upgrading to 12.1 HRMS RUP 3

The TKPROF trace indicates the most expensive query:

select /*+ ORDERED USE_NL(pay_asg) */ distinct pay_pos.person_id, null, null
from pay_payroll_actions pay_pa1,
pay_payroll_actions pay_pa2,
pay_assignment_actions pay_act,
per_all_assignments_f pay_asg,
per_periods_of_service pay_pos
where pay_pa1.payroll_action_id = :payroll_action_id
and pay_pa2.consolidation_set_id = pay_pa1.consolidation_set_id
and pay_pa2.effective_date between
pay_pa1.start_date and pay_pa1.effective_date
and pay_act.payroll_action_id = pay_pa2.payroll_action_id
and pay_asg.assignment_id = pay_act.assignment_id
and pay_pa1.effective_date between
pay_asg.effective_start_date and pay_asg.effective_end_date
and pay_pos.period_of_service_id = pay_asg.period_of_service_id
order by pay_pos.person_id




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.