PIDISDUP || PIDINSNO || Record Status Of Instrument Number Range Going Blank
(Doc ID 3039830.1)
Last updated on AUGUST 07, 2024
Applies to:
Oracle Banking Payments - Version 14.6.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
On : 14.6.0.5.0 version, Implementation Support
ACTUAL BEHAVIOR
---------------
PIDISDUP || PIDINSNO || Record Status of instrument number range going blank
It has been noticed that the following fields of MC number range in PIDINSNO is going blank the moment any duplicate instrument is getting issued using and MC number from that particular range:
Record Status
Authorization status
Instrument Type
Code Description
Issue Date
Please note that the Instrument generation has been maintained as manual generation.
EXPECTED BEHAVIOR
---------------------------------
System should show all the field values in PIDINSNO screen.
STEPS
----------
1. Go to PIDISDUP
2. Issue a Duplicate instrument & Save
4. Go to PIDINSNO
Changes
Fix :- Fix provided to retain the fields in the instrument inventory once the duplicate instrument is issued from the particular range.
Components Affected
-------------------
instrumentduplicatekernel.java;instrumentissuetxndao.java;
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |