My Oracle Support Banner

Account Class level Restriction is Enabled for Transction Code which is not Validated while Performing Transaction using DE Multi Journal Entry - DEDMJONL (Doc ID 2620988.1)

Last updated on DECEMBER 17, 2019

Applies to:

Oracle FLEXCUBE Universal Banking - Version 12.0.3 and later
Information in this document applies to any platform.

Symptoms

On : 12.0.3 version, Production Support-SET

ACTUAL BEHAVIOR
---------------
Account Level Restriction is imposed for Specific Transaction Code to be allowed. From Data Entry Screen Any Transaction Code is allowed

EXPECTED BEHAVIOR
-----------------------
If Transaction Code is not allowed then it should be restricted from Data entry Screen

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Perform Data entry using DEDMJONL
2. Enter Account no from Account Class
3. Enter Transaction Code as any other transaction Code
4. On Saving or Authorizing Error should be thrown if transaction code is not allowed

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users can post on other transaction code

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.