Bug With Amendment Of Sender To Receiver Info 3 At Non-STP Queue (Doc ID 2908212.1)

Last updated on NOVEMBER 21, 2022

Applies to:

Symptoms

On : 14.5.0.0.0 version, Production Support

ACTUAL BEHAVIOR
---------------
Bug with Amendment of Sender to Receiver Info 3 at Non-STP queue

We have noticed a bug in the system behavior for the processing of Incoming Cross-Border Payments through the Non-STP queue.

We have performed the maintenance at Non STP Amend Allowed Fields to allow all fields as amendable for the Function ID PXDITONL once an incoming Cross-Border Payment goes to the Non-STP queue. However, field Sender to Receiver Information 3 specifically seems to not be amendable, while all other fields can be amended as per the maintenance done at Non STP Amend Allowed Fields screen.


EXPECTED BEHAVIOR
-----------------------
On screen PXDITONL in 72:sender to receive info section field Sender to Receiver Information 3 should be amendable

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Incoming Target 2 Transfer is pushed to Non-STP queue
2. We try to modify this payment from the Non-STP queue.
3. Sender to Receiver Information 3 field is not amendable.
4. All other Sender to Receiver Information fields are amendable, but only Sender to Receiver Information 3 is not amendable.
5. The maintenance for allowing the amendable fields for Non-STP at Function ID PXDITONL includes the Sender to Receiver Information 3 field.

Changes

 Updated the PMTM_NON_STP_AMEND_FIELDS to synchronize field names and description.

Cause

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