Deleting a User/Group from Shared Services Does Not Delete it from the Essbase Security File

(Doc ID 1388447.1)

Last updated on MARCH 02, 2018

Applies to:

Hyperion Essbase - Version and later
Information in this document applies to any platform.
***feb 2,2015***


If a user/group is deleted using Hyperion Shared Services (HSS) after deprovisioning the user/group, it does not delete this user/group from the Essbase.sec file.

Thus if a user or group was provisioned for filter access, that access is removed from Essbase, but it can not be restored/recreated unless it is manually deleted from the Essbase.sec file using MaxL.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms