optional Select one or more joins and click OK.

Creating and Maintaining Folders 6-11 Tip : To save the changes you make as you make them, select the Automatically save changes after each edit check box. With this option selected, you do not have to click OK or Apply. 4. Click OK to save the changes you have made. Notes ■ You can assign a folder to more than one business area. However, there is only ever one definition of the folder in the EUL and that definition is shared by all the business areas to which the folder is assigned. If you modify the folder definition, the change is reflected in all the business areas to which the folder is assigned. For more information, see About sharing folders across business areas . ■ You can change a folder’s name at any time because Discoverer Administrator identifies folders using unique identification labels called identifiers for more information, see What are identifiers? . Changing a folder’s name does not alter the structure of the business area. However, folder names must be unique within the EUL. Note also that item names must be unique within a particular folder. ■ If you change the name of an item, this might affect the names of secondary elements for example, joins, hierarchies, hierarchy nodes, item classes that have the Auto generate name property set to Yes for more information, see About generating and updating EUL item names automatically . ■ You can change the database user that owns the database object on which a simple folder is based without changing the name of the object itself. For example, you might want to do this when moving from a development to a production environment. To change the database user, click the button beside the Owner field to display the Choose user or tableview dialog and specify the new database user. ■ You can base a simple folder on a tableview without specifying the database user that owns that tableview. You might want to do this: ■ to enable different Discoverer Plus users to access database tablesviews that have the same name but which exist in their own database users for example, for Oracle Applications users ■ to createmaintain an EUL for which the tables or table owners are not yet available ■ to createmaintain an EUL to which you as the Discoverer Manager do not have access ■ to move the EUL between different databases where the person who owns the data is different To base a simple folder on a tableview without specifying the database user name, clear the Owner field. When the Owner field is left blank, Discoverer Administrator generates SQL that does not include the owner before the table name. For example, if the Owner field contains the name of the schema that owns the tableview, the generated SQL statement might be: select column from owner.table If you clear the Owner field, the generated SQL statement would be: select column from table If the object is not in the current schema, a warning is displayed.