Request To Change The Placement Of IPopTxnCodeRuleParam In AccEntryPostingProcessor.class.
(Doc ID 3072566.1)
Last updated on FEBRUARY 25, 2025
Applies to:
Oracle Banking Payments - Version 14.5.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
On : 14.5.0.0.0 version, Implementation Support
ACTUAL BEHAVIOR
---------------
Request to change the placement of IPopTxnCodeRuleParam in AccEntryPostingProcessor.class.
Since in Patchset 13, During reversal of MX Payment, we are unable to access the call to IPopTxnCodeRuleParam hook in AccEntryPostingProcessor.class during accounting as accountingQueueDto.getNarrativeRequest() is null during reversal. So requesting to change the placement of hook above the if condition of accountingQueueDto.getNarrativeRequest() in AccEntryPostingProcessor.class.
EXPECTED BEHAVIOR
-----------------------
Change the placement of IPopTxnCodeRuleParam in AccEntryPostingProcessor.class.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Generate the MX payment
2. Reverse the payment.
3. Verify the access to IPopTxnCodeRuleParam hook in AccEntryPostingProcessor.class.
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot access the call to IPopTxnCodeRuleParam hook.
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 |