Maker & Checker Are Populated Incorrectly For NR Cancellation In SNCK (Doc ID 2733515.1)

Last updated on JUNE 22, 2021

Applies to:

Symptoms

On : 14.3.0.0.0 version, Implementation Support

ACTUAL BEHAVIOR
---------------
1. System does not ask for authorization and the record gets cancelled.
2. The maker and checker updated in the sanction xml is SYSTEM.

EXPECTED BEHAVIOR
-----------------------
1. System should ask for authorization of the transaction on cancellation from NR queue.
2. Maker and checker should be populated correctly.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1) Select any transaction from Network resolution queue.
2) Cancel the transaction from NR queue using a non auto auth user
3) System does not ask for authorization and the record gets cancelled. System should ask for authorization of the transaction on cancellation from NR queue.
4) Upon cancellation, the transaction goes for sanction scanning in OBPM.
5) The maker and checker updated in the sanction xml is SYSTEM.
6) It should be the user who perform the cancel and authorization action from the queue.


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, On cancel from NR queue, system did not process the transaction correctly.

Changes

Cause

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