My Oracle Support Banner

Payment Upload Validation Algorithm does not Validate the Match Value which Causes Error in Batch Run (Doc ID 2347999.1)

Last updated on MARCH 19, 2019

Applies to:

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


On RMB v2. against FW version

Payment Upload validation algorithm does not validate the match value and causing many unwanted invalid records at the end.

We are using the base payment upload functionality with the validation algorithm setup as C1-PUPLVALID.
This algo has the 'Is Match Type Validation Required (Y/N)' set to Y. However, when we upload a file with invalid match value data, the validation does not flag it as error.
It gets processed by the payment upload batch job PUPL and then creates a payment event with status as error.

The expectation is that since the algorithm already has the flag set to Y, it should fail the process of payment upload and does not allow to be processed by PUPL in the first place.
It should validate the record before moving to next stage.

The issue can be reproduced at will with the following steps:
1. Click on one of the Payment Event Information link

Note that Match value is not validated before the records move to staging even though validation algorithm has the parameter set to Y.

The issue has the following business impact:
Due to this issue, it is causing many payment event records to be created in error state and no easy way to delete or correct them.




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.