Is Oracle’s Vision Corp Guilty of Gender Inequality? An OBIEE Analysis to Investigate Reports

Brian BurdiCase Studies, Industry Trends, Oracle, Technical TipsLeave a Comment


Allegations of Vision Corporation’s activity in gender salary discrimination is something that Oracle’s Vision Corp takes very seriously and have been generous enough to open up all of their information for independent analysis by the public. We will begin an investigation of their full time employee’s salary information to see if the allegations of gender salary discrimination are prevalent in this corporation. We will be using OBIEE to investigate. The first thing we will look at is a generated table and pie chart that calculates the number of employees by their gender. We can see that there is a … Read More

Enabling the Auto-Complete Prompt Functionality in OBIEE

Brian BurdiOracle, Technical TipsLeave a Comment

user interface form

OBIEE has an auto-complete prompt feature which when enabled allows users to begin typing a selection in the prompts and OBIEE will suggest and highlight the matching prompt values. This option is only available on the “Choice List” when “Enable user to type values” is selected. When the following code is implemented will also allow the auto-complete to be case insensitive. 1. Navigate to: 1 $MW_HOME/instances/instance1/config/OracleBIPresentationServicesComponent/coreapplication_obips1$MW_HOME/instances/instance1/config/OracleBIPresentationServicesComponent/coreapplication_obips1 2. Open instanceconfig.xml file (make a backup of the file prior to making any changes). 3. Add the following code between the <ServerInstance> … </ServerInstance><ServerInstance> … </ServerInstance> tags: <Prompts> <MaxDropDownValues>256</MaxDropDownValues> <AutoApplyDashboardPromptValues>true</AutoApplyDashboardPromptValues> <AutoSearchPromptDialogBox>true</AutoSearchPromptDialogBox> <AutoCompletePromptDropDowns> … Read More

Advanced Filtering in OBIEE 11g

Brian BurdiTechnical Tips1 Comment

As an extension of the last post about filters and selection steps, we will focus our attention on writing logical SQL statements to help write more flexible ways to limit our data writing case statements. If you want to write logical SQL for the where clause in the query we will have to use the filtering option over the selection steps because we’re able to convert filters into SQL which we can customize or we can add a SQL statement straight to the filter without converting it. [message_box title=”NOTE” color=”yellow”]Once you convert a filter to SQL you will not be … Read More

OBIEE 11g Dashboard Prompt Creation

Brian BurdiTechnical TipsLeave a Comment

The use of a dashboard prompt allows you to embed both the filters from the analysis and the analysis on the same page.  Some of the main reasons to use a dashboard prompt are that it allows the user to customize his or her analysis output, allows more flexibility when wanting to change the parameters of a report, and can be reused with different analyses. An inline prompt does not allow these options and navigates the user to see the report within the analysis and not the dashboard. It is much more rigid than the dashboard prompt. Creating a dashboard … Read More

OBIEE 11g Selection Steps and Filters: Their Differences and How to Use the Two

Brian BurdiTechnical TipsLeave a Comment

Selection steps and filters in OBIEE 11g analyses overall serve a similar purpose by limiting the data for the user. Filters are applied before the query is aggregated meaning that it could affect calculations and measures because the query is affected. Whereas selections steps are applied after the query is aggregated meaning that the only thing that is affected is what the user will see, this will not affect calculations and measures. Filters can be applied to attribute and measure columns while selection steps can be applied to attribute and hierarchical columns.  The selection steps work incrementally so you should … Read More

A Comparison of OBIEE Drill Downs vs. Hierarchical Columns in 11.1.1.x

Brian BurdiBusiness Strategy, Technical Tips3 Comments

Choosing between a hierarchical columns or using a drill down depends on the purpose of the analysis, they both have positive qualities to them. Hierarchical columns allow the user to expand the column to reveal more information on the report but it also gives the option to condense the column back without affecting the selection of the data for the column. If the drill down column is used, the user will not be able to revert back to the original grouping when the dashboard was first opened because it affects both the selection steps and filters. Hierarchical columns will appear … Read More

When to Use an OBIEE Analysis or BI Publisher Report?

Brian BurdiTechnical TipsLeave a Comment

BI Publisher Reports and Analyses are backbone pieces to help meet a business’s BI needs. They are both very flexible for their respective purposes. Being able to combine these pieces on a dashboard in a clear concise manner will give the end users an effective report. [divider] [space height=”20″] [toggle_box] [toggle_item title=”Analysis”] Requires no previous knowledge of the table structure because of predefined subject areas. Gives end users the ability to write ad-hoc reports Can create an analysis from scratch or modify an existing one on a dashboard. Users can save or share their customizations and export to various formats Can be … Read More

Formatting a Field Globally in OBIEE 11g

Brian BurdiTechnical Tips1 Comment

Some fields will have a standard way of being formatted, such as a date DD-MMM-YYYY or a dollar amount being set $x,xxx.xx. Having to format the field each time that a user wants to use it becomes quite burdensome and gives a developer more room for error if they are formatting the field each time it is used. The saying “work smarter, not harder” comes to mind with this solution. For this example we will globally change the format of the field “revenue” to the format $x,xxx.xx. Let’s open an analysis and for the sake of seeing the format prior … Read More