My Oracle Support Banner

Incoming Target2 MX PACS.008 Failing In Processing For EndToEndId 'NOTPROVIDED' (Doc ID 3063593.1)

Last updated on DECEMBER 15, 2024

Applies to:

Oracle Banking Payments - Version 14.5.0.0.0 to 14.5.0.0.0 [Release 14]
Information in this document applies to any platform.

Symptoms

ACTUAL BEHAVIOR
---------------
While user attempt to process incoming Target2MX PACS.008 message with End to End Id tag as 'NOTPROVIDED', it wrongly with this record of MT 191 message derived for charge claim; which resulted into wrong payment processed and failed it.

EXPECTED BEHAVIOR
-----------------------
Systems should derived correct message and follow validate payment processing including charges to be claimed.

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

1. Incoming Target2 MX PACS.008 is received with End to End Id tag as 'NOTPROVIDED'.
2. Check GenericWiresCommonTxnNewProcessor.
3. Code then calls AbstractGenericWiresCommonTxnProcessor. Here system checks if there is any record in PXTB_OUT191_MASTER table which has MSG191_TAG21 tag as 'NOTPROVIDED'. Such a record exists (because End to End Id 'NOTPROVIDED' is very common, it is not a unique field as per standards).
4. System wrongly matches these records and derives that the incoming PACS.008 matches with this record of MT 191 message derived for charge claim.
5. Payment processing enters a wrong path and fails entirely.

Changes

 

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


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