My Oracle Support Banner

Default Charge Bearer SHA Is Getting Populated For All Common Group Messages In Sanction Xml (Doc ID 2599827.1)

Last updated on DECEMBER 18, 2020

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
---------------
Default charge bearer 'SHA' is getting populated for all common group messages in the sanction xml in both current and input section.
Fix required for the population of charge bearer for all common group messages.

EXPECTED BEHAVIOR
-----------------------
'SHA' should not be populated for common group as its a applicable for them. We should be blank.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1) Inject any incoming common group message in Oracle Banking Payments like MT191.
2) The transaction will move into sanction queue.
3) Check the sanction request xml.


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, even if SHA is not applicable then too its populated

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
Cause
Solution
References


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