Oracle9i Discoverer Administrator Administration Guide Version 9.0.2 Part Number A90881-02 |
|
This chapter explains how Discoverer supports access to Oracle Applications databases using Oracle Applications security and contains the following topics:
Oracle Applications are Oracle's integrated enterprise resource planning (ERP) and customer relationship management (CRM) solutions. Oracle Applications enable companies to run and manage their worldwide operations from a central site. For further information see http://www.oracle.com/.
Oracle Applications responsibilities are akin to database roles. They are an abstraction to which privileges can be assigned and which can apply to many users. Oracle Applications responsibilities are used to control Oracle Applications users functional and data access.
An Oracle Applications user connects to an Oracle Applications database and chooses a single Oracle Applications responsibility. Each Oracle Applications responsibility can have a set of privileges associated with it.
This means that an Oracle Applications user will by default assume the task privileges granted to the chosen responsibility (for more information see "How to specify the Oracle Applications users/responsibilities who can perform a specific task"). To change responsibility but keep the same user you must reconnect.
Discoverer supports the following features for Oracle Applications:
An Oracle Applications mode EUL is a Discoverer End User Layer based on an Oracle Applications schema (containing the Oracle Applications FND (Foundation) tables and views). Oracle Applications EULs employ Oracle Applications user names and responsibilities whereas standard EULs use database users and roles.
The only database user (i.e. non-Oracle Applications user) that can connect to an Oracle Applications mode EUL is the EUL owner. The EUL owner is the database user that is used to create the EUL. However, the EUL owner can grant administration privileges to Oracle Applications users. The authorized Oracle Applications users can then connect to the Oracle Applications mode EUL using Discoverer Administrator.
Many Oracle Applications tables and views are user-sensitive, and will return different results depending on which user/responsibility is used to access these tables/views. Discoverer correctly runs queries that respect these user-sensitive tables and views.
When connecting to Discoverer as an Oracle Applications user/responsibility, Discoverer will automatically connect to the correct schema (either APPS or APPS_MRC) to support Oracle Applications instances that have implemented the multiple reporting currencies feature.
Using Discoverer with Oracle Applications multiple organizations support enables you to work with data from more than one organization. Discoverer end users can query and analyze data from a set of organizations to which they have been granted access. The folders in the EUL you are connecting to must be based on Oracle Business Views (available in Oracle Applications 11i).
These features are only available when Discoverer is running in Oracle Applications mode. In other words, when Discoverer is running with an Oracle Applications mode EUL against an Oracle Applications database.
To start Discoverer as an Oracle Applications user the following conditions must be met:
The following differences apply in Discoverer when running in Oracle Applications mode:
When you run Discoverer in Oracle Applications mode the "Connect to Oracle9i Discoverer Administrator dialog (for Oracle Applications users)" will either display or not display the Oracle Applications user check box.
For more information, see "How to configure the Connect dialog for Oracle Applications users".
The following conditions apply when the Connect dialog is configured for Oracle Applications users:
Once you have entered details into the Connect dialog and clicked OK a Responsibilities dialog is displayed and you can choose the responsibility with which to connect (if the Oracle Applications user you are connecting with has more than one responsibility).
You can bypass the Choose a Responsibility dialog by entering both the Oracle Applications user and the responsibility into the Username field in the form 'user:responsibility'.
When you run Discoverer Administrator as an Oracle Applications user, then the Discoverer Privileges and Security dialogs display Oracle Applications user names and responsibilities. You can assign privileges and security to Oracle Applications user names and responsibilities. When you run Discoverer Administrator as a database user then the Discoverer Privileges and Security dialogs display database users and database roles.
For more information about using privileges to control access to information, see Chapter 7, "About Discoverer and security".
As the Discoverer manager of an Oracle Applications mode EUL you must be aware of the following:
When a Discoverer end user uses a workbook that accesses Oracle Applications secure views, the user might see different results on different machines (even when using the same connection information) if the machines have different local language (NLS) settings.
When using Oracle Applications secure views, the local language setting of the machine affects the data retrieved by Discoverer. Discoverer will display data consistently across machines with the same language setting.
To change a machines local language setting (on Windows NT), choose Start | Settings | Control Panel | Regional Settings and change the language value.
For more information on secure views, see Chapter 20, "How to use query prediction with secure views".
You can also define a language setting (NLS) for a user, responsibility, application or site using the Profiles setting in Oracle Applications. For more information see the Oracle Applications documentation.
Before you connect to Oracle Discoverer as an Oracle Applications user, you must configure the Connect dialog to default to Oracle Applications users.
To configure the Connect dialog for Discoverer Administrator and Discoverer Desktop:
When you use the Options dialog: Connections tab and you select either the Connect to applications EULs radio button or the Connect to both standard and applications EULs radio button you can enter values into these fields, but Discoverer uses default values if you do not. The fields and default values are as follows:
If you do not know the values to enter into the above fields contact your Oracle Applications database administrator.
You create an Oracle Applications EUL in two ways:
To create an Oracle Applications EUL using the Create EUL dialog:
For example, dba/dbapassword@oracleappsdb.
Note: You must not specify the user name of an Oracle Applications user. The EUL owner is always a database user.
Note: The Oracle Applications user Connect dialog may display the Oracle Applications User check box. For more information see "How to configure the Connect dialog for Oracle Applications users".
This is where you create a new database user and Oracle Applications EUL.
then select a user from the drop down list in the User field
then enter a user name, password/confirmation for the new user
Note: The EUL owner is always a database user. Please specify a database user.
Hint: We recommend that you select the Grant access to PUBLIC check box to grant public access to your EUL tables.
If you want to explicitly give access to your EUL tables do not select the Grant access to PUBLIC check box. If you do not select the Grant access to PUBLIC check box you will need to grant access to your EUL tables manually.
Hint: Ask your Oracle Applications database administrator if you are not sure.
Discoverer displays a dialog to confirm the creation of the new EUL:
Discoverer displays a dialog that gives you the option to install tutorial data into the new EUL.
Discoverer displays a dialog that gives you the option to reconnect to the database as the owner of the new Oracle Applications EUL you have just created, or to remain connected as the DBA.
You can grant task privileges to all Oracle Applications users in one action by using the Public user.
To grant task privileges to all Oracle Applications users:
The Privileges dialog contains the Public user. The public user is not an Oracle Applications user but represents all Oracle Applications users. You can grant a privilege to every Oracle Applications user by granting that privilege to the Public user. You can subsequently modify individual users' privileges as required.
For more information, see Chapter 7, "How to specify the tasks a user or role (responsibility) can perform".
This task describes how to grant (or deny) access permission for business areas to specific users or responsibilities.
For information about Oracle Applications responsibilities, see "What are Oracle Applications responsibilities?".
Note: When completing the following task there is a notable difference between what Oracle database users and Oracle Applications users will see in the dialog:
For more information about this task see Chapter 7, "How to specify a user or role (responsibility) that can access a business area".
This task describes how to specify which business areas a specific Oracle Applications user or responsibility can access.
For information about Oracle Applications responsibilities, see "What are Oracle Applications responsibilities?"
Note: When completing the following task there is a notable difference between what Oracle database users and Oracle Applications users will see in the dialog:
For information about this task see Chapter 7, "How to specify the business areas a user or role (responsibility) can access".
This section describes how to specify the tasks a specific user or responsibility can perform.
For information about Oracle Applications responsibilities, see "What are Oracle Applications responsibilities?".
Note: When completing the following task there is a notable difference between what Oracle database users and Oracle Applications users will see in the dialog:
For information about this task see Chapter 7, "How to specify the tasks a user or role (responsibility) can perform".
This section describes how to specify the users or responsibilities that can perform a specific task.
For information about Oracle Applications responsibilities, see "What are Oracle Applications responsibilities?".
Note: When completing the following task there is a notable difference between what Oracle database users and Oracle Applications users will see in the dialog:
For information about this task see Chapter 7, "How to specify a user or role (responsibility) to perform a specific task".
|
Copyright © 2002 Oracle Corporation. All Rights Reserved. |
|