My Oracle Support Banner

Payment Upload Staging Search Fails for Payment Staging Records Having More Than 20 Payment Advises (Doc ID 2645925.1)

Last updated on MARCH 05, 2020

Applies to:

Oracle Financial Services Revenue Management and Billing - Version and later
Information in this document applies to any platform.


On RMB v2., Payment Upload Staging Search fails for payment staging records having more than 20 payment advises.

We have custom batch jobs that update payment upload staging tables.
Also PUPL framework batch job has successfully created payments. We do not have any issue in batch jobs.
But when we search from UI we get error. Spl logs show the exceptions details.

- 781400-142031-1 2020-01-09 08:56:32,754 [[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'] ERROR (program.service.AbstractRecordWebConverter) Cannot process 21 rows in list PAY_UPLD_STG with max size 20
com.splwg.shared.common.LoggedException: Cannot process 21 rows in list PAY_UPLD_STG with max size 20
at com.splwg.shared.common.LoggedException.raised( [spl-shared-]
at [spl-base-]
at [spl-base-]
at [spl-base-]
at [spl-basesupport-]

The issue can be reproduced at will with the following steps:
1. Go to Main Menu > Financials > Payment Upload Staging
2. Search by external transmission id and select staging record having more than 20 payment advice
3. Search fails.

For ext_transmit_id and ext_reference_id to be used in step#2, run below SQL:
- select ext_source_id, ext_transmit_id, ext_batch_id, ext_reference_id, count(1) from cisadm.CI_PAY_ST
where ext_transmit_id like 'BOA%'
group by ext_source_id, ext_transmit_id, ext_batch_id, ext_reference_id
having count(1) > 20
order by ext_transmit_id




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

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