Specify whether to match the case of text data using the Match Case check box as

12-8 Oracle Fusion Middleware Administrators Guide for Oracle Business Intelligence Discoverer 3. Click Yes at the confirmation screen to remove the condition permanently. The condition is removed from the business area. Note : When Discoverer users next re-open workbooks that use a deleted condition, or refresh the worksheets using the deleted condition, previously filtered out data will be available to the Discoverer end users. Example conditions The following examples show how conditions are used in Discoverer Administrator. For more examples of conditions, see the Oracle Fusion Middleware Users Guide for Oracle Business Intelligence Discoverer Plus. Example 1: Using a condition to find data for the year 2002 To create a condition that returns only data for the year 2002, enter the following in the Formula area of the New Condition dialog: Example 2: Using a condition to find sales in the last seven days To create a condition that only returns the sales in the last seven days using the calculated item, “Transaction Age in Days”, enter the following in the Formula area of the New Condition dialog: Note that the Transaction Age calculated item has the following formula FLOOR SYSDATE - Transaction Date This type of condition is sometimes described as a “rolling window” condition because the “window” of rows it returns changes from day to day. Example 3: Using a condition to find shipments in Quarter 3 To create a condition that only returns shipments made in quarter 3 Q3 regardless of year using the calculated item, ’Ship Quarter’, enter the following in the Formula area of the New Condition dialog: Note that the Ship Quarter calculated item has the following formula: EUL_DATE_TRUNCShip Date, “Q” Item Condition Value Year = 2002 Item Condition Value Transaction Age in days 7 Item Condition Value Ship Quarter = ’Q3’ Creating and Maintaining Conditions 12-9 About outer joins and the DisableAutoOuterJoinsOnFilters registry setting If you define an outer join between two tables, make sure you are aware of how conditions filters and the DisableAutoOuterJoinsOnFilters Discoverer registry setting can combine to affect the rows of data returned by an end user query. You define an outer join between two tables to display: ■ rows in a master table for which there are no corresponding rows in a detail table ■ rows in a detail table for which there are corresponding rows in a master table For example, you might want to display: ■ department names and their employees, but also include the department names that have no employees ■ employee names and their departments, but also include the employee names that do not belong to a department In SQL, the outer join is signified by the plus + symbol. Discoverer includes outer joins in SQL: ■ when explicitly defined in Discoverer Administrator For more information, see the Edit Join dialog: Options tab . ■ automatically under some circumstances For example, Discoverer automatically creates outer joins in the SQL for end user queries that contain conditions. When running a query that contains a condition, users will sometimes want the results to: ■ include values from one table that have no corresponding values in a table to which it is joined by an outer join ■ not include values from one table that have no corresponding values in a table to which it is joined by an outer join The DisableAutoOuterJoinsOnFilters registry setting enables you to disable the use of automatically generated outer joins when conditions are used in end user queries. The table below summarizes the examples that follow: The following examples illustrate how outer joins, conditions, and the value of the DisableAutoOuterJoinsOnFilters registry setting can affect the rows of data returned from an end user query. For more information about Discoverer registry settings, see Chapter 21, Discoverer Registry Settings . Example No. Condition applied? Value of DisableAutoOuterJoinsOnFilters All values displayed Example 1 No 0 or 1 Yes Example 2 Yes No Example 3 Yes 1 Yes 12-10 Oracle Fusion Middleware Administrators Guide for Oracle Business Intelligence Discoverer Example 1: No condition applied This example illustrates the results returned when you execute a query against two tables, where the master and detail tables are joined with an outer join. Discoverer displays: ■ rows of data from the master table dept and detail table emp ■ rows of data from the master table dept where no data exists for the detail table emp The query is defined using the following SQL statement, where the outer join is signified by the plus + symbol: select dname, ename, job from dept, emp where dept.deptno = emp.deptno+; The results returned from the query above will not change whether you switch the DisableAutoOuterJoinsOnFilters registry setting on or off. Example 2: Condition applied to query and DisableAutoOuterJoinsOnFilters set to 1 switched off This example applies a condition to the query in Example 1 and the DisableAutoOuterJoinsOnFilters registry setting is switched off. Discoverer displays: ■ the data specified in the condition Discoverer does not display: ■ master rows for which there is no detail data The following SQL statement is used, where the outer join is signified by the plus + symbol: select dname, ename, job from dept, emp where dept.deptno = emp.deptno+ and job = CLERK; DNAME ENAME JOB SALES GRIMES DIRECTOR SALES PETERS MANAGER SALES SCOTT CLERK SUPPORT MAJOR MANAGER SUPPORT SCOTT CLERK ADMIN MARKETING DISTRIBUTION DNAME ENAME JOB SALES SCOTT CLERK SUPPORT SCOTT CLERK