Tuesday, February 28, 2012

Combined New metadata repository features in Oracle BI EE 11g Release (11.1.1.6) include


11.1.1.6:


  • Ability to Limit and Offset Rows Returned
  •  Identify Query Candidates with Oracle BI Summary Advisor
  • Integrate the Administration Tool with a Third-Party Source Control Management
       System
  • Streamlined MUD Merge Process
  • Automated Repository Patching Process
  • Support for Aggregate Persistence in a Cluster
  • FIRST_PERIOD and LAST_PERIOD Time Series Functions
  • Ability to Print the Physical and Business Model Diagrams

11.1.1.5:

·        Access to Oracle OLAP Data Sources
·        Access to TimesTen Data Sources
·        Ability to Connect to SAP/BW Data Sources Using a Native Connection
·        New Diagramming Capability
·        Validation Utility to Validate Metadata Objects in a Repository

11.1.1.3:

  • New SampleApp.rpd Demonstration Repository
  •  Hierarchy Objects in the Presentation Layer
  • Support for Unbalanced (Ragged) and Skip-Level Hierarchies
  • Support for Parent-Child Hierarchies
  • Creating Subject Areas for Logical Stars and Snowflakes
  • Multicurrency Support
  • Generating and Applying XML Patch Files
  • Enhancements for Multiuser Development and Repository Lifecycle Management
  • Metadata Repository File Encryption
  • Metadata Repository File Compression
  • Embedded Database Functions
  • SQL Functions for Time Series Calculations and Level-Based Measures
  • Support for SELECT_PHYSICAL
  • Support for Calculated Members
  • Access to Essbase Data Sources
  • Access to Hyperion Financial Management Data Sources
  • Access to ADF Business Component Data Sources

  • Access to Oracle RPAS Data Store Through ODBC
  • Ability to Connect to Oracle Database Through OCI
  • Support for Dragging and Dropping XMLA Objects
  • Support for Using a Standby Database with Oracle Business Intelligence
  • Aggregate Persistence Auto-Indexing
  • Pruning Utility to Delete Unwanted Repository Objects
  • Ability to Defer Execution of Session Variable Initialization Blocks
  • Improved Usability in the Administration Tool


More detailed explanation of these features can be found in the following oracle Documentation
Source: oracle.com

http://docs.oracle.com/cd/E23943_01/bi.1111/e10540/whatsnew.htm#sthref8

Monday, February 27, 2012

List of Bug Fixes in OBIEE11.1.1.6

Hi Friends,

Got the link from http://sranka.wordpress.com. Really helpful. Thanks to Sunil!!!.

Link : http://sranka.wordpress.com/2012/02/26/obiee-11-1-1-6-bug-fixes/

Thanks
Venkat

Monday, February 13, 2012

How to convert a DatekeyNo to date at RPD Level and at OBIEE Answers Part-1

Hi,

Issue : How to convert a DatekeyNo  to  date at RPD Level and at OBIEE Answers

Often We run in to circumstances in OBIEE where we need to present Date_key_no field from database which has data-type number ( For Ex: 20120113)  in to 01/13/2012 date.


Let us see how to convert this filed in to Date(01/13/2012) at the RPD level and answers. When I ran into this issue I refereed couple of OTN Forums and blogs but not able to use any of those solution directly.
So here is the solution that works for me and hopefully for you too.

Answers Level : 

Field  from database :  

Code to use in Answers to convert into Date :


Substring(cast("Attributes"."Hmfinaldate" as character(30))  FROM 5 FOR 2) ||'/'||Substring(cast("Attributes"."Hmfinaldate" as character(30)) FROM 7 FOR 2)||'/'||Substring(cast(“Attributes"."Hmfinal date" as character(30)) FROM 1 FOR 4)

In the above code Attributes"."Hmfinaldate" is table.columnname.

Out Put :  Please see the screenshot below




RPD LEVEL :  

a) Using Existing Logical column concept(BMM LAYER) 


When I use the code here in  BMM layers using logical columns. It is  throwing some Invalid expression. I don't understand what is the problem. May be some issue in the tool (or) Concatenate doesn't work at this level. verified the format but there is nothing wrong with the format.





b) Using Physical columns : I used same above code with reference to physical columns.This code works fine.

SUBSTRING( CAST ("[GDW] GDW PHYSICAL".""."DWSGDW01"."DWV12006_ORD_POM_FACT_A(POM)"."HM_DELIVERY_FINAL_DT_KEY_NO" AS CHARACTER ( 30 )) FROM 5 FOR 2) || '/' ||  SUBSTRING( CAST ("[GDW] GDW PHYSICAL".""."DWSGDW01"."DWV12006_ORD_POM_FACT_A(POM)"."HM_DELIVERY_FINAL_DT_KEY_NO" AS CHARACTER ( 30 )) FROM 7 FOR 2) || '/' ||  SUBSTRING( CAST ("[GDW] GDW PHYSICAL".""."DWSGDW01"."DWV12006_ORD_POM_FACT_A(POM)"."HM_DELIVERY_FINAL_DT_KEY_NO" AS CHARACTER ( 30 )) FROM 1 FOR 4)



 Thanks
Venkat
The Article is also posted at our company blog :  http://blog.aptude.com/blog-1










Thursday, February 9, 2012

How to Restrict the Values in OBIEE PROMTS

It is common practice to have year and month promts on the OBIEE reports.

One can set a default year and month by creating a dynamic variable in the RPD (or) using SQL Results. When users want to see the  year-2(2010) or  year-1(2011) one he has to scroll down. When he scrolls down he will see all the rows in the column.

For ex  : The below screenshot shows all the values  in the column





Issues: How to Restrict the values in the Promt to show current year, current year-1, current year-2 when user scrolls down

Solution:  In the following screen, under the "show" field select "SQLRESULTS"   use the following code
Code :
SELECT "Order Dates"."Order Calendar Year" FROM "BOM-RNA Analysis" where "Order Dates"."Order Calendar Year" =YEAR(CURRENT_DATE)
union
 SELECT "Order Dates"."Order Calendar Year"-1 FROM "BOM-RNA Analysis" where "Order Dates"."Order Calendar Year" =YEAR(CURRENT_DATE)
union
SELECT  "Order Dates"."Order Calendar Year"-2 FROM "BOM-RNA Analysis" where "Order Dates"."Order Calendar Year" =YEAR(CURRENT_DATE)
In the code "Order Dates"."Order Calendar Year" is table.column name and "BOM-RNA Analysis" is Subject Area.
In the screen shot I am using server variable in "DEFAULT TO" field and respective presentation variable.




 OUTPUT : See the screen shot below. Now I am only seeing 2012, 2011, 2010













Thanks
Venkat