detecting Report (Analysis) Orphans in OBIEE

A Dashboard typically represent a combination of different Reports to provide summary information about a Business Process or Sub-Process e.g. with HR: A Recruiting Dashboard may contain Reports about hiring sources and the respective Time to Hire or a Dashboard provides Reports about certain balance information E.g. current capital in Fixed Assets. Over time these Reports may be replaced or exchanged and many reports may only be created for Testing purposes. The management of all these Reports becomes very difficult and the IT Department may want to understand the structure of the Web Catalog in terms of Report usage on Dashboard and Report Orphans. The Oracle BI Sample App provides a example of how this can be implemented under the Lifecycle and Admin section:

image

 

Pre-built Reports exist that Analyse the structure of the Webcat to determine unused Analysis:

image

These samples require to execute scripts on the BI instance, which is also documented within the Sample App Image under /app/oracle/SAScripts/ReferenceChecker.

Advertisements

BI Publisher now available with OAC

Until today, Oracle BI Publisher was only available as a (SaaS) bundle with Oracle Fusion Applications Cloud and OTBI, see also a previous Article. However, with Oracle Analytics Cloud, Oracle BI Publisher is now also available as a “first degree” Platform Cloud Service (PaaS) giving more flexibility especially in terms of Data Sources. This allows to create highly formatted Reports/Documents such as Invoices, Purchase Orders, Dunning Letters without the context of Oracle Fusion Applications Cloud.

See the full announcement here.

Issue when using Report prompts within OTBI Answers and OTBI Fusion

A strange Issue exists with OTBI in terms of Report prompts. If a User adds a prompt directly within the Report, the prompts appear correctly within BI Answers. However, if the same Report is opened from within Oracle Cloud, the prompts are not shown to the User.

Prompts added to Report:

image

Prompts appearing in BI Answers of OTBI when running (opening) the Report:

image

However, when opening the same Report from Fusion (OTBI embedded) the Report executes without showing the prompts, even though the prompt has been specified as “required”:

image

When clicking on the “Edit” button of the Fusion Catalogue Browser, the following warning message is being displayed:

image

The standard provides prompted Analysis usually of Type “Dashboard”, hence this Issue is not applying for standard content. E.g. the Analysis on Department details also provides filters as Dashboard prompts:

image

Translation of multi-lingual attributes within Oracle Fusion Cloud and OTBI

Oracle Fusion Cloud allows to enable text fields as multi lingual enabled attributes. As part of the batch upload process e.g. from Fusion Product Hub, these enabled attributes can be specified within different languages:

image 

Within Oracle Fusion Cloud, these attributes are displayed in  the respective Language of the logged in User. These is also true for OTBI. E.g. for US the respective item description is displayed in US:

image

If a user logges into OTBI with RUS language, the item description is automatically displayed with RUS description:

image

understanding calculation for Days of Absence

To Analyse the Days of Absence for Workers, the Absence information is extracted and loaded into a dedicated Star (W_ABSENCE_EVENT_F) of the BI Applications data model. A simple Report on the days of Absence and absence occurrences looks like the following from the Report Builder (Answers):

image

This can also be restricted to a individual worker and a specific time period by applying additional filters in the Report Builder:

image

This Report then return the following filtered results:

image

This is based on the Fact for Absence:

image

The Absence Days are calculated based on the DAYS_DURATION column for the selected period from 2017/07/06 until 2017/07/17. Thus, each duration will be counted for the selected period regardless of the start or end date of a an Absence event (First column). If the worker was not scheduled to work of a certain days such as 7.7. and 8.7. then these days will not be counted as days of Absence. The Absence occurrences are calculated on the ABS_OCCRNC_DAY column.