SMDROLDF :: Cannot close role maintenance if role is mapped to User which are already closed.
(Doc ID 2962451.1)
Last updated on JULY 20, 2023
Applies to:
Oracle FLEXCUBE Universal Banking - Version 14.3.0.0.0 and laterInformation in this document applies to any platform.
Goal
On : 14.3.0.0.0 version, Production Support-SET
Issue Summary
================
Unable to Closed Role maintenance as the Mapped to to User ID's which are in closed Status.
Expected result
===============
System should allow to Close the Role maintenance if no Active User mapped to the Role Maintenance.
Simulation Steps
=========================
a) Create Role Maintenance ROLE_A using SMDROLDF(Role Maintenance Screen)
b) Save and Authorize the Maintenance.
c) Map the Role to Existing User ID in the System using SMDUSRDF
d) Save and Authorize the User Maintenance.
e) Initiate Closure of the User ID using SMDUSRDF
f) Save and Authorize the Closure of User Maintenance.
g) Initiate Closure of the Role Created using SMDROLDF
h) System throws Error SM-ROL-015(Cannot Close the Role. This Role is already associated to some users)
Analysis :
=======================
System is Checking for the role ID to be Closed is mapped to any user. But the Record State of the User is not being Validated.
Solution
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
Goal |
Solution |
References |