My Oracle Support Banner

Maker And Checker Id Are Not Populated In Sanction Request Xml For Inbound Direct Debit Refund Flow (Doc ID 2653830.1)

Last updated on APRIL 04, 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
---------------
Maker and Checker id are not populated in sanction Request xml for Inbound Direct Debit Refund Flow

EXPECTED BEHAVIOR
-----------------------
Maker and checker should be sent as the USER/Checker who initiates a refund from PCDIRFND screen.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1)Process SDD Core pacs.003 and liquidate the Transaction upon required approvals
2)Initiate Refund from PCDIRFND screen and Refund will be initiated in Un authorized status
3)Authorize the refund record from another user
4)validate the sanction queue details fro queue action log for Refund Transaction details

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot verify audit details.

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


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