UNABLE TO SAVE AFTER COPY OF TRANSACTION IN PXDITONL SCREEN (Doc ID 3048895.1)

Last updated on SEPTEMBER 22, 2024

Applies to:

Symptoms

On : 14.7.0.0.0 version, Implementation Support

ACTUAL BEHAVIOR
---------------
UNABLE TO SAVE AFTER COPY OF TRANSACTION IN PXDITONL SCREEN


After click of Copy, changed Transfer amount, removed suppressed flag for Credit confirmation and clicked on Enrich. UETR can be seen but nothing happens on click of save. No message or processing happens.

Note: UETR defaulted is that of the old transaction. On click of copy and removing the UETR manually and then enrich, system is allowing to save.

EXPECTED BEHAVIOR
-----------------------
sometimes due to SWIFT server downtime after switching off (Cut off time), bank manually created Incoming contracts based on the outstanding messages received.

In that case they will use copy option. UETR needs to be deleted on copy, so that fresh UETR is generated on enrich.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Copy an Exisitng Payment from PXDITONL
2. Verify if UETR is deleted on Copy
3. Enrich and Try Save

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot save the Transaction as UETR is not deleted of Old transaction

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.