R12:IBY :Format Payment Instructions With Text Output Ends In Error: PSException: An error has occured while updating instruction and payment statuses and marking them as complete. (Doc ID 1513513.1)

Last updated on SEPTEMBER 29, 2016

Applies to:

Oracle Payments - Version 12.0.0 to 12.1.3 [Release 12.0 to 12.1]
Oracle Payables - Version 12.0.0 to 12.1.3 [Release 12.0 to 12.1]
Information in this document applies to any platform.

Symptoms

On app version 12.1.2 : the Format Payment Instructions with Text Output program is ending in error:

Error message
oracle.apps.iby.exception.PSException: An error has occured while updating instruction and payment statuses and marking them as complete.
...
+---------------------------------------------------------------------------+
Start of log messages from FND_FILE
+---------------------------------------------------------------------------+
Enter Mark Complete: Timestamp: &timestamp1
Enter Callout pkg:AP_PMT_CALLOUT_PKG.payments_completed: Timestamp: &timestamp2
...
insert into ap_checks_all - &timestamp3
+---------------------------------------------------------------------------+
End of log messages from FND_FILE
+---------------------------------------------------------------------------+

Customer analysis
The bank account name was over 80 char long, causing the AP_PMT_CALLOUT_PKG package not to write to the ap_checks_all table.
So the error occurs when the internal bank account name is over 80 characters.
Seeking a solution that overcomes this limitation.

Steps
1 - Created an invoice
2 - Paid with Payment Process Request (PPR)
3 - Payment instruction created
4 - Format Payment Instructions concurrent program spawned, but completes in error.

Business impact
Payments are not accounted for.
AP Trial Balance is incorrect.

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms