PGDINRTN - System Validating 'Instrument Date' Instead Of 'Clearing Date' Of PGDITONL Banker's Cheque (Doc ID 3051699.1)

Last updated on OCTOBER 10, 2024

Applies to:

Symptoms

On : 14.7.0.0.0 version, Production Support

PGDINRTN - System validating 'Instrument Date' instead of 'Clearing Date' of PGDITONL banker's chequ

Banker's cheque(BC) can be issues at any point of time and goes for clearing at any day.

We have maintained nothing for 'Stale Period'(Months and Days) in PGDINSCD(Instrument Code Deatailed) for banker's cheque(BC).

Also, we maintained 'Return Days': "1" in PGDNWMNT(Clearing Network Detailed) for banker's cheque(BC) clearing network code.

During return PGDINRTN system should validate 'ReturnByDate' based on 'Clearing Date' and not 'Instrument Date'.

System is calculating 'ReturnByDate' based on PGDITONL 'Instrument Date': + PGDNWMNT 'Return Days".


Expectations:

System should allow the return in PGDINRTN and calculate the 'ReturnByDate' based on PGDITONL 'Clearing Date' + PGDNWMNT 'Return Days'.

ERROR
-----------------------------

"PC-TXP-042": "Transaction cannot be returned/refunded after Return/Refund by date".




STEPS
-----------------------
The issue can be reproduced at will with the following steps:

1) Created 'Instrument Number' for 'Instrument Code' : 'BC' in PIDINSIS(Instrument Issue Detailed), details as,
'Instruction Date' : "2023-02-26"

2) Create new PGDITONL(Inbound Clearing Transaction), details as,
'Instrument Date': "2023-02-26"
'Clearing Date': "2024-06-01"

3) Created new PGDINRTN(Return or Reversal of Inbound Clearing), details as,
  "returnDate":"2024-06-01"
  'Clearing Date': "2024-06-01"
Instrument Date : "2023-02-26"


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
users needs system to use clearing date for the Return days calculation

Changes

Cause

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