PXDOTONL - Null Credit Account Currency After Save In NonSTP For Passthrough Payment Transaction (Doc ID 3059772.1)

Last updated on NOVEMBER 20, 2024

Applies to:

Symptoms

ACTUAL BEHAVIOR
---------------
Bank received Target2MX - Swift passthrough payment; which user attempted to modify and enrich by input Credit Account Currency field in PXDOTONL screen. However, while saving payment message, this field is saved as null and doesn't preserve the information from Enrich operation.

EXPECTED BEHAVIOR
-----------------------
System should preserve value selected during enrich operation in screen PXDOTONL for the received Target2MX messages.

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

1. Target2MX - Swift passthough is received in OBPM.
2. Payment can be viewed on PXDOVIEW screen.
3. On action Modify from NonSTP queue, user is directed to PXDOTONL screen.
4. User clicks on Enrich and Credit Account Currency field is populated with EUR currency.
5. On Save this field is saved as null and doesn't preserve the information from Enrich operation.

This payment can be processed, however the Outgoing MT103 message doesn't get generated at all.

OR

1. Swift - Swift passthough is received in OBPM.
2. Payment can be viewed on PXDOVIEW screen.
3. On action Modify from NonSTP queue, user is directed to PXDOTONL screen.
4. User clicks on Enrich and Credit Account Currency field is populated with EUR currency.
5. On Save this field is saved as null and doesn't preserve the information from Enrich operation.
This payment cannot be processed further from Sanction check queue, as the Creditor currency is null.

The common issue for these scenarios is that the Creditor Account Currency doesn't preserve the information with which it is populated during Enrich in NonSTP queue.

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.