My Oracle Support Banner

In PMDBTVAL, The Batch Validation Is Incorrect Despite The Record Is Closed. (Doc ID 3002408.1)

Last updated on FEBRUARY 22, 2024

Applies to:

Oracle Banking Payments - Version and later
Information in this document applies to any platform.


On : version, Implementation Support

In PMDBTVAL, the batch validation is incorrect despite the record is closed.

Issue Description:
There is a maintenance in PMDBTVAL screen (Debit) where there is a duplicate check for ‘TXN_COUNT’. So uploaded one pain008 with the count of transactions as ‘2’ but even after closing the record in PMDBTVAL, the system is taking that into consideration for the second upload. The record status is ‘Closed’ still validation occurs.

Actual Result: The record is closed in PMDBTVAL still the validation occurs.

Analysis: In code, system is not checking record status to extract duplicate record from PMDBTVAL

 if record is closed in PMDBTVAL , batch duplication check should not occur.

The issue can be reproduced at will with the following steps:
1. Upload pain008 file on day 1
2. Create record in PMDBTVAL with duplicate field as TXN_COUNT
3. Move to date 2
4. Close record in PMDBTVAL
5. Upload pain008 on date 2
6. System checks duplicate because of PMDBTVAL and moves to BO queue


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.