R12:AP Bank Account Number Need Validation To Prevent More Than 30 Char Entry (Doc ID 1196478.1)

Last updated on MARCH 04, 2024

Applies to:

Goal

Found that when supplier bank account is of length more thank 30 Char, it lead to some errors while processing payments.

For example: Print record status request ends with error

FND LOG
Fnd.plsql.APP_EXCEPTION.RAISE_EXCEPTION.dict_auto_log "APP-SQLAP-10000:
ORA-12899: value too large for column ""AP"".""AP_CHECKS_ALL"".""BANK_ACCOUNT_NUM"" (actual: 32, maximum: 30)
occurred in AP_PMT_CALLOUT_PKG.payments_completed with parameters (Complted Payments Group id = <ID>)
while performing the following operation: insert into ap_checks_all"

As this entry is happening through standard form/page (as follow).  we need to introduce new
validation to restrict user entering more than specified characters (i.e. 30 Char only)

 -Navigate to Supplier workbench
 -Query supplier
 -Navigate to Banking details
 -Update first bank account number
 -Click update
 -The following message received
 "The changes to the banking details have been saved"
 
Remarks
There is a validation applied when creating Internal bank account (from following path Setup>Payment>Bank Accounts) so why does this same validation not exist when updating External bank account (from supplier workbench)?

Solution

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