System Should Not Allow Update Of Personal Payment Method After Payment Is Processed
(Doc ID 1350761.1)
Last updated on APRIL 24, 2023
Applies to:
Oracle Payroll - Version 11.5.10.2 to 12.2 [Release 11.5 to 12.2]Information in this document applies to any platform.
Symptoms
Bank Account details of a Payment Method are updated in the past, when several payrolls have already used that Payment Method.
Example: There is an employee who has had several payruns and the pay has been paid to a specific bank account. The problem arises when the bank account details of the payment method that is used is updated after the payruns have been run, but with an date track date before the payruns. As a result, if the SOEs are queried, they will show that the pay was transferred to the new bank account, rather than the bank account it was originally paid to.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1) It is now December.
2) This employee has had payruns since January and all the pay has been paid to Bank account 12345.
3) Then date track to July, and update the Payment Method Bank Account details from 12345 to 77788, using UPDATE mode.
4) Then all SOEs from July will show that the pay has been deposited to Account 77788, rather than 12345.
Cause
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
Symptoms |
Cause |
Solution |
References |