Quickpay Pre-Payments ( PAYWSRQP) Errors: APP-PAY-07268 Operation started but not finished
(Doc ID 338412.1)
Last updated on DECEMBER 03, 2019
Applies to:Oracle Payroll - Version 126.96.36.199 and later
Information in this document applies to any platform.
The QuickPay Pre-payments concurrent job takes approximately 3-6 hours to complete
The following message is displayed on the QuickPay form when starting PrePayments:
Steps to Reproduce:
1. Navigate to FastPath -> QuickPay
2. Search for Employee Number in the Search By Number section
3. Perform a Regular QuickPay Run
4. When the Regular QuickPay successfully completes, click Start PrePayments
5. Message APP-PAY-07268 Operation started but not finished received after approximately 1 minute.
Based on the uploaded trace file the following query appears to causing the process to not complete in a timely manner and therefore the following error is thrown:
"APP-PAY-07268 Operation started but not finished"
SELECT fnd_number.number_to_canonical(/*+ RULE*/ nvl(sum(fnd_number.canonical_to_number(TARGET.result_value) * FEED.scale),0) ) FROM pay_run_result_values TARGET , pay_balance_feeds_f FEED , pay_run_results RR , pay_assignment_actions ASSACT , pay_assignment_actions BAL_ASSACT , pay_payroll_actions PACT , pay_payroll_actions BACT , pay_assignment_actions PPASSACT , pay_payroll_actions PPACT , pay_action_interlocks INTLCK2 where BAL_ASSACT.assignment_action_id = :ASSIGNMENT_ACTION_ID and BAL_ASSACT.payroll_action_id = BACT.payroll_action_id and FEED.balance_type_id = :U1 + DECODE(TARGET.INPUT_VALUE_ID, NULL ,0,0) and FEED.input_value_id = TARGET.input_value_id and nvl(TARGET.result_value,'0') != '0' and TARGET.run_result_id = RR.run_result_id and RR.assignment_action_id = ASSACT.assignment_action_id and ASSACT.payroll_action_id = PACT.payroll_action_id and PACT.effective_date between FEED.effective_start_date and FEED.effective_end_date and RR.status in ('P','PA') and BACT.action_type in ('P','U', 'R', 'Q') and PPASSACT.assignment_action_id = pay_core_utils.get_pp_action_id(BACT.action_type, BAL_ASSACT.assignment_action_id) and PPASSACT.payroll_action_id = PPACT.payroll_action_id and PPACT.action_type in ('P', 'U') and nvl(PACT.future_process_mode, 'Y') = 'Y' and PPASSACT.assignment_action_id = INTLCK2.locking_action_id and INTLCK2.locked_action_id = ASSACT.assignment_action_id and pay_core_utils.include_action_in_payment(BACT.action_type, BAL_ASSACT.assignment_action_id, ASSACT.assignment_action_id) = 'Y' and NOT EXISTS (SELECT NULL FROM pay_payroll_actions RPACT , pay_assignment_actions RASSACT , pay_action_interlocks RINTLK where ASSACT.assignment_action_id = RINTLK.locked_action_id and RINTLK.locking_action_id = RASSACT.assignment_action_id and RPACT.payroll_action_id = RASSACT.payroll_action_id and RPACT.action_type = 'V')
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