Specify the SQL statement on which the custom folder will be based.

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. 6-12 Oracle Fusion Middleware Administrators Guide for Oracle Business Intelligence Discoverer How to edit a custom folder’s SQL statement To edit a a custom folder’s SQL statement:

1.

On the Workarea: Data tab , select the custom folder. 2. Choose Edit | Properties to display the Folder Properties dialog . 3. Click the Custom SQL field to display the Custom Folder Properties dialog . Tip : You can resize the Custom Folder dialog to view more of the SQL statement. 4. Make changes as required. 5. Click Validate SQL to ensure you have entered valid SQL. 6. Click OK to validate the SQL statement and save the custom folder. Notes ■ To enable you to create custom folders before the underlying database objects have been created or made available, Discoverer Administrator permits you to save a custom folder even if the SQL is invalid. Note that end users will not be able to query the object until the SQL is valid. ■ Discoverer Administrator analyzes the modified SQL statement to assess the changes you have made. If Discoverer Administrator determines that the changes will affect existing items or create new items, Discoverer Administrator displays the Impact dialog that shows you each item that is affected. Use the Impact dialog to help you decide whether to confirm the changes you have made, make further changes, or abandon the edit. What is complex folder reach through? Complex folder reach through is a mechanism that enables Discoverer Plus and Discoverer Desktop users to add items to their worksheets in addition to those provided in a selected complex folder. When a user selects items from a complex folder, other items in other folders become available for selection. Note that you could achieve the same result by creating joins between the complex folder and its base folders. However, this approach is undesirable because: ■ it might result in poor query performance ■ you will have additional joins to maintain In Discoverer Administrator you can define one or more base folders within a complex folder as ’reach through enabled’. When a Discoverer Plus or Discoverer Desktop user selects an item from the complex folder, the associated reach through enabled base folders become available for selection in a worksheet. Complex folder reach through is particularly useful when using Discoverer with Oracle Applications flexfields that is, user defined items to query a base folder after a complex folder has been created. If the base folder is defined as reach through enabled and new flexfield items can be added to the base folder without having to modify the complex folder definition. Oracle Applications users can select the new flexfield items from the base folder immediately, as they are reach through enabled. Notes ■ A complex folder contains items from one or more base folders. A complex folder enables you to create a combined view of data from multiple folders. This is analogous to a view in the database.