How to Assign a Security Role to an OFSA 4.5 Client Data Object or User Defined Table
(Doc ID 159742.1)
Last updated on MAY 18, 2017
Applies to:Oracle Financial Data Manager - Version 4.5 and later
Information in this document applies to any platform.
Oracle Financial Services Applications (OFSA) - Version 4.5
Oracle Financial Data Manager - Version: 4.5
Note: All OFSA 4.5 products have reached sustaining support.
How to assign a security role to a client data object or user created table. This is required if the table or object is to be used within the OFSA applications.
If an object is created without assigning a role to it, even though it has been properly registered and classified, other users will not be able to process with this object. From the Oracle Financial Services Installation and Configuration Guide, Release 4.5, Chapter 14 FDM Security, page 14-5 through 14-6,
"Client Data Objects include any objects not created by the initial
installation of the FDM database. This category of objects is comprised of
objects created by administrators as well as the LEDGER_STAT table.....It is
the administrator's job to create roles to provide privileges on Client Data
Objects to the users. By default, users have no database privileges on these
tables, except for users that migrated from a 3.5 or 4.0 database. All users
require access to these objects in order to perform their duties."
After creating, registering, and classifying a Client Data object, the FDM administrator's next task is to assign the object to a security role. There are several different types of roles to choose from. The object can be assigned to either a seeded role or to an user defined role. All roles fall into one of two distinct categories, Internal or External. Follow the directions below to complete the tasks needed for users to be able to use a new Client Data object within OFSA.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!