My Oracle Support Banner

Message Is Processed In PQSICLRQ-PQDCANRP With Disallowed Character In Response Message. (Doc ID 2657587.1)

Last updated on MAY 12, 2021

Applies to:

Oracle Banking Payments - Version 14.3.0.0.0 and later
Information in this document applies to any platform.

Symptoms

On : 14.3.0.0.0 version, Implementation Support

ACTUAL BEHAVIOR
---------------
SWIFT Message type 196 is processed with invalid character.

EXPECTED BEHAVIOR
-----------------------
As the Resultant action is mapped as Reject in PMDSPCHR, For invalid character message should have been rejected with proper error message.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Maintain the allowed charter list in PMDALCHR for SWIFT message type.
2. Map the allowed character list in PMDSPCHR with SWIFT network type. Resultant Action as - Reject and no value for Default Replacement character.
3. Create Cross border incoming message by injecting MT103 message.
4. Process the transaction from Sanction or any other applicable queue.
5. Inject MT192 message for cancellation of swift message.
6. Process the same from Sanction queue if applicable.
7. Check for the transaction detail in PQSICLRQ - Inbound Cancellation Request Queue.
8. Perform any operation on the screen Interim/Accept/Reject by providing invalid character in 76/77 or 79 field. for e.g. @

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.