Click Connect. Oracle Fusion Middleware Online Documentation Library

17-10 Oracle Fusion Middleware Administrators Guide for Oracle Business Intelligence Discoverer 16. Click Finish to create the tables and views for the new Oracle Applications mode EUL and populate them with default data. Discoverer displays a dialog to confirm the creation of the new EUL: 17. Click OK to close the confirmation dialog. Discoverer displays a dialog that gives you the option to install tutorial data into the new EUL. 18. Click Yes or No to specify whether to install the tutorial data. 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. Notes ■ Having created an Oracle Applications EUL you can now: ■ Grant task privileges to an Oracle Applications user so that they have the ability to perform tasks in Discoverer Administrator or Discoverer Plus using this Oracle Applications EUL for more information, see How to specify the tasks an Oracle Applications user or responsibility can perform . ■ Create a new business area using the Oracle Applications tables for further information, see Chapter 5, Creating and Maintaining Business Areas . ■ Grant access to the tutorial business area to Oracle Applications users and responsibilities for more information, see How to specify a user or role responsibility that can access a business area . Granting access to the tutorial business area enables Oracle Applications users and responsibilities to access the sample data. ■ If you did not install the sample data into the Apps Schema, you must grant the select privilege on the sample data tables to the APPS schema owner for more information about granting privileges, see the Oracle Database SQL Reference Guide. The select privilege is required because the APPS schema owner is the database user that is used as the proxy by applications users. Therefore, APPS schema owner must have select access to the sample data tables. ■ You must not use a database user for example, the EUL owner to maintain an Oracle Applications EUL for more information, see Which user should maintain an Oracle Applications EUL? . ■ When you create a new Oracle Applications business area, the schema objects you load into the business area must be based on secure views. This retains the row-level security associated with a specific Oracle Applications responsibility. Ask your Oracle Applications database administrator for further information. ■ You can also create an Applications mode EUL from the command line for more information see create_eul apps_mode . Which user should maintain an Oracle Applications EUL? When you maintain an Oracle Applications EUL in Discoverer Administrator, it is advisable that you do not use a database user for example, the EUL owner. You should use an Oracle Applications user for example, SYSADMIN or Responsibility for example, System Administrator. When you use an Oracle Applications user instead of a database user as the EUL administrator, Discoverer provides correct