R12: AP: Build Payments Request (IBYBUILD) Fails With The Following In The Request Log "Payment Document 'Xxxxxxx' With Payment Doc Id N Has Been Locked From Payments Workbench"
(Doc ID 2760241.1)
Last updated on SEPTEMBER 07, 2023
Applies to:
Oracle Payables - Version 12.2.10 and laterInformation in this document applies to any platform.
Symptoms
The Build Payments request (IBYBUILD) fails with an error.
Steps to reproduce:
Create a PPR entering all pertinent attributes.
Review the Selected Scheduled Payments page.
Click the Submit button. This will submit the Build request.
The Build request fails with .the following in the request log:
IBY_CHECKNUMBER_PUB.assignCheckNumbers:Payment document 'Xxxxxxx' with payment doc id N has been locked from payments workbench
IBY_CHECKNUMBER_PUB.assignCheckNumbers:Processing cannot continue because payment document is unavailable (locked).
IBY_CHECKNUMBER_PUB.assignCheckNumbers:Changing the status of the payment instruction to
IBY_CHECKNUMBER_PUB.processPaperPayments:Check numbering did not succeed.
IBY_CHECKNUMBER_PUB.performCheckNumbering:Check numbering process did not succeed. Raising exception ..
IBY_CHECKNUMBER_PUB.assignCheckNumbers:Processing cannot continue because payment document is unavailable (locked).
IBY_CHECKNUMBER_PUB.assignCheckNumbers:Changing the status of the payment instruction to
IBY_CHECKNUMBER_PUB.processPaperPayments:Check numbering did not succeed.
IBY_CHECKNUMBER_PUB.performCheckNumbering:Check numbering process did not succeed. Raising exception ..
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 |