BW Hierarchies in OLAP?

This is from another post regarding hierarchies in OLAP. Currently in our system we have many many hierarchies that have been setup in BW, these range from Regions to Time based. In this example I'm looking to utilize the Time based hierarchies in OLAP that are setup in BW. Yet I see no way to do this, is it possible? We have Analysis for Office as well (limited license usage) and I couldn't see how to do it their either. Really we need it in OLAP though since that's where our users (thousands) will be running these reports. Currently they are using BEx and we'd like to transition to BOBJ, but losing basic functionality like this would be a deal-breaker. See below for screenshots on how it's done in BEx. Any help anyone can give would be most appreciated, thanks!
OLAP Right-Click (FAR less options, and no mention of Hierarchy)

If you create your Analysis on top of a BEx query, and then drag in the hierarchy object from the dimension folder, then you can get hierarchy related navigation. We are on BI 4.0 SP6.

Similar Messages

OBIEE and Oracle OLAP Value Based Hierarchies

Hi there...
I have a value based dimension built on Oracle OLAP and want to map it on OBIEE Administration tool.
I've been using the above link as reference:
http://www.oracle.com/technology/obe/olap_biee/CreateBIEEMetadata.htm
There's no option to import from Oracle Multi-dimensional Database. Either to import/configure the view created by OLAP as an Unballanced or Ragged Dimension.
I also checked this example, but it uses ESSBASE as the multi-dimensional source....
http://www.rittmanmead.com/2008/08/27/ragged-hierarchy-handling-in-obiee/
How to map this Ragged Dimension created in OLAP workspace in OBIEE? Any suggestions or directions will be highly appreciated...
Thanks in advance
Marcos

Mark and others,
You can create OLAP_TABLE views with level columns on top of value-based hierarchies. BI Beans used to do that too behind the scenes in Discoverer Plus OLAP. If you trace the Discoverer session, where you are querying data from Value-based hierarchies, you will see that it also generates OLAP_TABLE views with level columns in it.
So the question is how to do it. Internally, even for Value-based hierarchies Oracle OLAP keeps track of the "depth" of each value by using a structure called GID_DIMENSION (i.e., Grouping Dimension). Here is an example of a view on top of a value-based hierarchy (CFC_ACCT_GAPP) for RPT_ACCOUNT dimension. You have to know how "deep" your value-based hierarchy is.
Similar kind of a thing is done by OLAP View Generator application, which I never use - since I always prefer to define my own OLAP_TABLE views.
This kind of a view can then be used in the RPD of OBIEE.
select *
FROM table(OLAP_TABLE ('AW duration session',
*'DIMENSION RPT_ACCT_ID FROM RPT_ACCOUNT WITH*
HIERARCHY RPT_ACCOUNT_GAAP_PARENT   FROM RPT_ACCOUNT_PARENTREL(RPT_ACCOUNT_HIERLIST ''CFC_ACCT_GAAP'') INHIERARCHY RPT_ACCOUNT_INHIER
HATTRIBUTE RPT_ACCOUNT_GAAP_LVL_NUM FROM RPT_ACCOUNT_DEPTHVAL
FAMILYREL RPT_ACCOUNT_GAAP_LVL1,
RPT_ACCOUNT_GAAP_LVL2,
RPT_ACCOUNT_GAAP_LVL3,
RPT_ACCOUNT_GAAP_LVL4,
RPT_ACCOUNT_GAAP_LVL5,
RPT_ACCOUNT_GAAP_LVL6,
RPT_ACCOUNT_GAAP_LVL7,
RPT_ACCOUNT_GAAP_LVL8
FROM RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 127),
RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 63),
RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 31),
RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 15),
RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 7),
RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 3),
RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 1),
RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 0)
FAMILYREL RPT_ACCOUNT_GAAP_LVL1_DSC,
RPT_ACCOUNT_GAAP_LVL2_DSC,
RPT_ACCOUNT_GAAP_LVL3_DSC,
RPT_ACCOUNT_GAAP_LVL4_DSC,
RPT_ACCOUNT_GAAP_LVL5_DSC,
RPT_ACCOUNT_GAAP_LVL6_DSC,
RPT_ACCOUNT_GAAP_LVL7_DSC,
RPT_ACCOUNT_GAAP_LVL8_DSC
FROM RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 127),
RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 63),
RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 31),
RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 15),
RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 7),
RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 3),
RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 1),
RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 0)
LABEL RPT_ACCOUNT_LONG_DESCRIPTION
ATTRIBUTE ACCOUNT_LDSC    FROM RPT_ACCOUNT_LONG_DESCRIPTION
ATTRIBUTE ACCOUNT_SDSC    FROM RPT_ACCOUNT_SHORT_DESCRIPTION
ATTRIBUTE ACCOUNT_TYPE    FROM RPT_ACCOUNT_TYPE
ATTRIBUTE SOURCE_LEVEL    FROM RPT_ACCOUNT_LEVEL
ATTRIBUTE CALCULATION     FROM RPT_ACCOUNT_CALCULATION
ATTRIBUTE CALC_DATA       FROM RPT_ACCOUNT_CALC_DATA
ATTRIBUTE GAAP_SORT_ORDER FROM RPT_ACCOUNT_GAAP_SORT_ORDER
ATTRIBUTE RATIO           FROM RPT_ACCOUNT_RATIO
ATTRIBUTE ACCOUNT_LEVEL   FROM RPT_ACCOUNT_LEVELREL'))

Type 2 SCD dimension on multipe levels turns into type 1 !!!

Hello
Im having difficulties implementing a type 2 dimension where the history trigger is put on multiple levels. If I only have history on the lowest level of the dimension everything works fine. But as soon as I try to capture the changes in de higher levels as well the trouble starts.
Image the following dimension:
PClass_Code PClass_Desc PGroup_Code PGroep_Desc PCode PName Eff_Dt End_Dt
A Play 120 Boardgames 4209420X Chess 19000101 20010101
A Play 120 Boardgames 4209420X Chessboard 20010102 NULL
So somewhere in time the productname has been changed, resulting in a type 2 record.
If I chose to change the productclass description in 'Toys' I expect the following to happen:
PClass_Code PClass_Desc PGroup_Code PGroup_Desc PCode PName Eff_Dt End_Dt
A Play 120 Boardgames 4209420X Chess 19000101 20010101
A Play 120 Boardgames 4209420X Chessboard 20010102 20060730
A Toys 120 Boardgames 4209420X Chessboard 20060731 NULL
A new type 2 record in my dimension.
In OWB I have set a history trigger with effective and expiration dates on the highest (productclass) and lowest (product) level to capture the changes in the history. The generation of sparse data works fine, i.e. I also get a unique record for each productclass record without any products. All the links between levels are correctly defined.
But this is what happens:
PClass_Code PClass_Desc PGroup_Code PGroup_Desc PCode PName Eff_Dt End_Dt
A Toys 120 Boardgames 4209420X Chess 19000101 20010101
A Toys 120 Boardgames 4209420X Chessboard 20010102 NULL
A type 1 change in my highest level!
Can anyone help me to achieve the 2nd scenarion, the one I expected?
Thanks much,
Roelant

Hello Rajesh,
I agree, the thing is that this is all standard OWB R2 functionality. Up untill now I always programmed SCD's manually but with this new release I try to use the built in functions. I have to say that it works fine when the changes occur on the lowest level. But with changes on higher levels... see my example :-). I am still looking for ways to get a full type 2 dimension with using the standard dimension properties.
Another possible solution is to skip all the levels and create 1 big level which contains all the attributes (including 'higher levels'). You have then got to recreate the levels and hierarchies in OLAP, which is a shame...
Hope you (or anyone) can take a look at this.
Regards,
Roelant

Reference same dimension multiple times in a cube

Hi,
I'm creating a cube with Analytic Workspace Manager. The cube needs to reference same dimension more than once. For example, in a movie ticket booking cube, there's a booking date and a show date , both should reference same pre-created TIME dimension. Because one dimension can be added to a cube only once, now my solution is to define 2 dimensions, i.e. BOOKING_TIME and SHOW_TIME, both are based on same underlying table and have exactly same levels/hierarchies/mapping, and then add them to the cube. I believe there must be smarter approaches out there, please advise.
Thanks!
Jim
Edited by: user11955172 on 2012-12-10 上午2:36

For hand written/custom sql going against the Cube:
You're right that you can use one of the 3 time dimension based views (duplicated 4 times for time1/2/3/4 dimensions).
If you need to use 2 out of 4 time dimensions in your query (by applying an application based filter/restriction) then you would need to alias the relevant view(s) 2 times and get your result.
If you needed to use all 4 time attribute dimensions, then you need to alias the time dimension view 4 times.
12 views represent the full spectrum of possible report/query usage scenarios available to users via these 4 time dimension views. A typical session with various reports/queries is unlikely to refer to all of them (possible but not likely).
In different scenarios, any one of the 3 views - dimension view, h1, h2 view - comes into play for each dimension.
In every query/report scenario, only 1 out of the 3 applicable views would be needed or suitable based on the query/report specifics.
E.g:
* If your query is at lowest level and is also referencing attributes/descriptions which pertain to >1 hierarchies, then the view v_time<N>d is the appropriate view to use. Neither vtime<N>h1 or vtime<N>_h2 will be able to give you the results you require if you have attributes defined exclusively in either hierarchy h1 or h2.
* Setting the default hierarchy to either h1 or h2 determines which hierarchy view is expected to be used/preferred in cases where dimension is not referenced or where Top level of dimension is desired in query/report. E.g: Top level is same for both hierarchies h1 and h2 but read the Top Level values from h1 view as h1 is marked as the default hierarchy for dimension.
* The level of the query is generally determined by the lowest level of the attributes/fields in your query. If you have attributes like Long_Desc, Short_Desc (available at all levels/all hiers) and you have 2 attributes from Hierarchy H1 and from levels L1 (one level above leaf) and L3 (higher than L1 by 2 levels)... then the query uses v_time<N>h1 and will apply a filter to choose/constraint levelname field = 'L1'.
* Reporting tools like OBIEE etc. have security filters defined to ensure that the joins to missing dimensions and the appropriate dimension level filters appended to the query in a transparent "behind the scenes" manner.
NOTE: By modeling the time based fields as different dimensions, you get the benefit of time series analysis along any of the 4 dimensions. You can create a Month-to-Date Revenue measure along "Show Biz Time" dimension and also create a Year-to-Date Revenue Measure based on "Booking Time" dimension. Also compare % variance of "MTD - Revenue - Show Biz Time" with corresponding value for Last year "MTD LY - Revenue - Show Biz Time". This is the benefit you get by breaking out the 4 columns in relational fact and modeling them as explicit time dimensions. You pay a small price in terms of cube space expansion, time dimension load increase but as acknowledged earlier, this dimension can be loaded incrementally, the full load process is done only initially. It is an offline process (batch) and does not hamper query performance.
Regd
3) In the underlying star schema, we have only one time dimension table, in the ticket booking fact table, we have 4 dimension columns referencing the same time dimension table. So it's intuitive to expect similar design in the cube. Current approach seems like replicating the dimension table for each dimension column.Do you have parentage along h1/h2 laid out in terms of different parent columns ... 06:30am should have parent D1 in h1 hierarchy (regular day) and parent=D1-1 in h2 hierarchy (business day)?
h1=regular day hierarchy
h2=biz day hierarchy
In that case, perhaps you want "Booking Time" (Time1) to use view: v_time1_h1 by default and "Booking Biz Time" (Time3) to use v_time3_h2 by default.
Using h2 hierarchy for Time1 or h1 hierarchy for Time3 would be illogical/invalid. Maybe you can simplify things by removing the hierarchies from olap model which dont apply to the dimension.
HTH
Shankar

Rejcted records cube build log.

I am on 11.1.0.7 db with 11.1.0.7B AWM and loading the dimensions and cube. The olapsys.xml_load_log table is not populated with the build log. I can query cube_build_log but xml_load_log give me better information(rejected/processed records). I know there is a bug for this issue on 11.1.
Can I somehow know the rejected records information other than doing a minus between fact and dimensions? Any workaroud for this?
Thanks,

With 11gr2 we have the following logs which will give all the information including rejected dimensions without having to do a minus from fact table.
Maintenance Logs
The first time you load data into a cube or dimension using Analytic Workspace Manager, it creates several logs. These logs are stored in tables in the same schema as the analytic workspace:
•     Cube Build Log: Contains information about what happened during a build. Use this log to determine whether the build produced the results you were expecting, and if not, why not. The log is continually updated whenever a cube or dimension is refreshed, whether by Analytic Workspace Manager, the database materialized view refresh subsystem, or a PL/SQL procedure. You can query the log at any time to evaluate the progress of the build and to estimate the time to completion. The default table name is CUBE_BUILD_LOG.
•     Cube Dimension Compile Log: Contains errors that occur during the validation of the dimension hierarchies when OLAP is aggregating a cube. The default table name is CUBE_DIMENSION_COMPILE.
•     Cube Operations Log: Contains messages and debugging information for all OLAP engine events. The default table name is CUBE_OPERATIONS_LOG.
•     Cube Rejected Records Log: Identifies any records that were rejected because they did not meet the expected format. The default table name is CUBE_DIMENSION_COMPILE.
You can also run the $ORACLE_HOME/olap/admin/utlolaplog.sql script to create the build log with some useful views.

Time-dependent BW hierarchies in Analysis for OLAP

Hi all,
We are using time-dependent hierarchies in combination with a key date variable.
Tools used: Query designer based on SAP BW 7.4 and BO 4.0.
The following steps are executed:
Report is executed and key date is prompted
According to the key date, the correct time-dependent organisation hierarchy will be used in drill-down
Bring up variable screen again and select different key date
The drill-down changes according to the now correct time-dependent organisation hierarchy
The above scenario works for BEx Analyzer, BEx Web, Analysis for Office - but not for Analysis for OLAP.
Whenever I run through this scenario and confirm the updated key date, the following error is displayed:
cube.get.dimension.info.runtime.error : java.lang.IllegalStateException: There is no default hierarchy for dimension [ORG].
In the user guide I don't find any specifics about the hierarchies and since it works in all the other applications, I wonder where the error is coming from. I also could not find it anywhere else in the forum.
Has anyone experienced the same error or any suggestions?

Hi Peter,
This issue is captured in SAP Note 1941865. Resolved in 4.0 (8.5, 9.2 or SP10) and 4.1 (1.6 or SP03).
Symptom
In BI 4.1, Analysis for OLAP returns errors similar to:"An error occurred in the MDAS service while processing a request from Analysis, edition for OLAP. Try the operation again. If the problem persists, please contact your administrator. (AOC00041)" and/or "cube.get.dimension.info.runtime.error: java.lang.IllegalStateException: There is no default hierarchy for dimension [DIMENSIONNAME]"
The BW Query the AOLAP workspace is created against has 2 different hierarchies that have the same text description
Environment
SAP BusinessObjects Business Intelligence platform 4.0
SAP BusinessObjects Business Intelligence platform 4.1
Analysis, edition for OLAP
Reproducing the Issue
In CMC, create an OLAP BICS connection to a multi provider
Connect to BI launchpad and launch Analysis, edition for OLAP.
Use the connection to create a new workspace.
The error is observed
Cause
This issue has been logged as a defect under ADAPT01720287 for BI4.0 and ADAPT01713663 for BI4.1
Resolution
A fix for this issue is included in the following maintenance releases:
BI4.0:
Patch 8.5
Patch 9.2
Support Pack 10
BI4.1:
Patch 1.6
Support Pack 03

IDT - Hierarchical List of Values on an OLAP data model

Hey All,
I am having a problem converting a UNV universe to a UNX version which is based on a SQL SSAS 2012 data source.
In the Information Design tool when I right click and select Preview Values I see the below List of Values as a Hierarchy.
However, when I add this same object into a WebI report the List of Values does not appear anything like the above. How do I set the Business Layer to perform the same way in WebI???

Ok, I have worked out to add prompts for a hierarchical object from an OLAP unx universe the object that needs the prompt added to it must be added in the Result Objects and then using the Member Selector properties to Enable Prompt.
However, now that I do this I am getting a new problem with the following error message appearing when I Run the query...

OLAP on 11g and Materialised Views with Multiple Value-Based Hierarchies

Hello OLAPians
I am trying to setup Orable BIEE to report on an OLAP cube with pre-aggregated data. As OBIEE is not able to hook into the OLAP directly i have to create an SQL cubeview.
Currently i am on a 10g OLAP environment and am using the oracle sample SQL cubeview generator to create an SQLview of my cube.
The cube itself has multiple dimensions and these dimensions have multiple VALUE-based (ragged) hierarchies and dimension members can be shared across hierarchies also.
Initially i had a problem running the view generator plugin because there is a bug within it that does not finish if there are multiple value-based hierarchies present. I was able to get around this by manually editing the limitmap for the cubeview and manually creating the SQL view.
The question that i want to ask is how robust is the 11g materialised views with multiple value-based hierarchies and the sharing of dimension members across different hierarchies?
Has anyone successfully been able to create a cubeview and import it into OBIEE without the hassle of manually editing the limitmap?
A problem arises with the value-based setup whereby if the client creates a newer depth in the ragged hierarchy, i need to manually create the limitmap and the cube-view over again, and then re-map the BI Administration mappings.

The simple answer to your question,
how robust is the 11g materialised views with multiple value-based hierarchies...?is that materialized views are not supported on top of value-based hierarchies in 11g. The reason is that it is not possible to write a reasonable SQL statement that aggregates a fact over a value-based hierarchy. Such a SQL statement is necessary if we want to create a rewritable MV on top of the cube.
But I suspect this is not what you are really asking. If you are trying to set up OBIEE on top of the cube in 10g using the view generator, then you will probably want to use the "ET VIEWS" that are generated automatically in 11g. These are generated whether or not you enable materialized views on top of your cube. I am not aware of any issues with the generated value-based hierarchy view support in 11g. Members may be shared between value hierarchies and you will not need to generate or modify limit maps.

Has anyone setup BIEE with OLAP 10g using value-based dimension hierarchies

I just wanted to know if it is possible to setup BIEE with 10g using multple dimensions containing multiple value-based hierarchies?
I know this involves using the OLAP Cube View Generator to create an sql view of the cube data.
I have been able to get this to work with nine dimensions all containing a single value-based hierarchy bar one which had four value-based hierarchies. But as soon as i have multiple hierarchies in multiple dimensions it seems to go haywire and i cannot get the sql view to return correct data.
I thought i would post on the BI side to see if anyone has been successful in creating a BIEE setup like this?

The simple answer to your question,
how robust is the 11g materialised views with multiple value-based hierarchies...?is that materialized views are not supported on top of value-based hierarchies in 11g. The reason is that it is not possible to write a reasonable SQL statement that aggregates a fact over a value-based hierarchy. Such a SQL statement is necessary if we want to create a rewritable MV on top of the cube.
But I suspect this is not what you are really asking. If you are trying to set up OBIEE on top of the cube in 10g using the view generator, then you will probably want to use the "ET VIEWS" that are generated automatically in 11g. These are generated whether or not you enable materialized views on top of your cube. I am not aware of any issues with the generated value-based hierarchy view support in 11g. Members may be shared between value hierarchies and you will not need to generate or modify limit maps.

Report performance with Hierarchies

Hi
How to improve query performance with hierarchies. We have to do lot of navigation's in the query and the volume of data size very big.
Thanks
P G

HI,
chk this:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/1955ba90-0201-0010-d3aa-8b2a4ef6bbb2
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/ce7fb368-0601-0010-64ba-fadc985a1f94
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/4c0ab590-0201-0010-bd9a-8332d8b4f09c
Query Performance Is "Aggregates" the way out for me?
/people/vikash.agrawal/blog/2006/04/17/query-performance-150-is-aggregates-the-way-out-for-me
° the OLAP cache is architected to store query result sets and to give all users access to those result sets.
If a user executes a query, the result set for that querys request can be stored in the OLAP cache; if that same query (or a derivative) is then executed by another user, the subsequent query request can be filled by accessing the result set already stored in the OLAP cache.
In this way, a query request filled from the OLAP cache is significantly faster than queries that receive their result set from database access
° The indexes that are created in the fact table for each dimension allow you to easily find and select the data
see http://help.sap.com/saphelp_nw04/helpdata/en/80/1a6473e07211d2acb80000e829fbfe/content.htm
° when you load data into the InfoCube, each request has its own request ID, which is included in the fact table in the packet dimension.
This (besides giving the possibility to manage/delete single request) increases the volume of data, and reduces performance in reporting, as the system has to aggregate with the request ID every time you execute a query. Using compressing, you can eliminate these disadvantages, and bring data from different requests together into one single request (request ID 0).
This function is critical, as the compressed data can no longer be deleted from the InfoCube using its request IDs and, logically, you must be absolutely certain that the data loaded into the InfoCube is correct.
see http://help.sap.com/saphelp_nw04/helpdata/en/ca/aa6437e7a4080ee10000009b38f842/content.htm
° by using partitioning you can split up the whole dataset for an InfoCube into several, smaller, physically independent and redundancy-free units. Thanks to this separation, performance is increased when reporting, or also when deleting data from the InfoCube.
see http://help.sap.com/saphelp_nw04/helpdata/en/33/dc2038aa3bcd23e10000009b38f8cf/content.htm
Hope it helps!
tHAK YOU,
dst

Unbalanced BW hierarchies in Webi

Hi all.
I have an issue with interpreting unbalanced hierachies from BW in WebI.
The issue occurs when importing a SAP Bex Query, containing an Infoobject
bearing a hierarchy - in this case 0ORGUNIT. The problem occurs when trying to
show 0EMPLOYEE per Organizational Unit. The employee should only be
displayed when they are directly linked to the orgunit (as known from Bex) however in WebI all employes are shown at the highest levels in the hierarch. This obviously returns a long list of employees per hierachy level.
It ought to be possible only to show 0EMPLOYEE when they are directly
related to the Organizational Unit in the hierarchy.
I tried to built a hierarchy in the Universe, where the hierarchy
dimensions are listed chronologically, and placed 0employee at the
buttom. This didn't work either as the hierarch is unbalanced and not
all branches have the same amount of nodes.
Anyone know of a fix to this. I'm aware that WebI traditionally was intended to report on non-dimensional data however I would expect that there is a workaround for this issues or do I really have to move to an OLAP based client (Pioneer or Crystal) ??.
Steps for Reconstruction
1) Create a Bex query containing an Infoobject with a hierarchy
2) Create a universe based on Bex Query
3) In the universe create a hierarchy (Tools -> Hiearchy) based on the
hierarchy level dimensions from the infoobject
4) In Webi create new web intelligence report based on the universe
5) Add a keyfigure, ex. Employee and the first level of your hierachy.
6) Run query and enable drilldown
8) How to show orgunit (and employee when the employee is directly
related to a given orgunit)?
Regards
/Frank

hi,
please can you send me the screen shot of universe how you have design and also let me know hierarchies and infocube you are you are using
regards
Pinto

BW Universe with multiple hierarchies issue

Hi,
We created an OLAP universe off a BW BEx query that has 2 hierarchies enabled. Hierarchy 1 is 12 levels deep while Hierarchy 2 is only 5 levels. Level 00 was also generated for better hierarchy reporting. In Web Intelligence reporting, Hierarchy 1 is required to report starting on Level 4 and then drill as needed so L00, L01, L02, L03, L04 was included in the report. Hierarchy 2 is for grouping and only L00, L01 was included in the report along with key figures. This Web Intelligence result set works fine [Hierarchy 1: L00, L01, L02, L03, L04] , [Hierarchy 2: L00, L01] , measures/key figures.
If additional levels of Hierarchy 1 is added, at L06 and beyond, the query suddenly returns message "No Data to Fetch". In BEx, it was confirmed the query does run with the exact same drilldowns as Web Intelligence and it works in BEx. If Hierarchy 2 is removed from Web Intelligence, the report also can successfully fetch up to the lower levels up to L09. If other flat objects are added, the Web Intelligence report still works fine, it seems to get "No Data to Fetch" when Hierarchy 2 is added. Any information would be appreciated, thank you.
Issue: Web Intelligence report with two BW hierarchies gets "No Data to fetch" if Hierarchy 1 goes lower than L06.
Observations:
1) There are some empty nodes starting in Hierarchy 1 L06, but the Hierarchy 1 works fine by itself
2) The BEx and Universe has a hierarchy node variable prompt. We filtered at lower hierarchy nodes, levels where there is data, but it still does not work with Hierarchy 2
Environment:
- BOE XI 3.1 SP2
- SAP BI 7
- BEx query (2 hierarchies), OLAP universe, Web Intelligence

Please refer to: the below document page# 43. Hope this helps!
http://help.sap.com/businessobject/product_guides/boexir31/en/xi3-1_sap_olap_universes_en.pdf

Help! Ent - 06955 "Cube name does not exist in OLAP schema"

I get this error when I try to view data from a cube or dimension.
From what I've searched, I have to deploy the objects to catalog, which I have done, but still I get the error. I'm stuck with this for 1 and half days...
Any ideas?
Regards,
M.

Hi,
I have found some interseting info for you from this forum:
This is more of an OWB question rather than OLAP specific. But there are some steps you must perform with OWB before you can view the data.
1) Design the dimension - create the levels, hierarchies and attributes
2) Storage mode - decide if you want to create a ROLAP or MOLAP dimension
3) Deploy the dimension - if you opted for a ROLAP model this will create a table and a dimension object to be used by the optimiser for query rewrite. If you opted for MOLAP this will create an analytic workspace (you should see a table called AW$xxxxxxx in your target schema) and within that AW will be your dimension.
4) Populate dimension - before you view data you must create a mapping to move data from your source table into the target dimension. Then you must deploy the mapping and finally execute the mapping to load data into the dimension.
I would check your deployment log as I suspect you have some errors during deployment and the object has not been deployed. Personally, I find the best way to deploy objects is via Control Center rather than using the right mouse click menu options in Design Center.
OLAP Blog: http://oracleOLAP.blogspot.com/
OLAP Wiki: http://wiki.oracle.com/page/Oracle+OLAP+Option
DM Blog: http://oracledmt.blogspot.com/
OWB Blog : http://blogs.oracle.com/warehousebuilder/
OWB Wiki : http://wiki.oracle.com/page/Oracle+Warehouse+Builder
DW on OTN : http://www.oracle.com/technology/products/bi/db/11g/index.html
Next question - do you have all the required patchsets in place to support OLAP? If you are using 10gR2 (which you really should be when using OLAP) you will need 10..2.0.3 + OLAP A patch or 10.2.0.4.
Hope this info. will help you.
Mandi

How to delete the Query Buffer in OLAP

Hi Guys,
I have been working with query, after some time there has some changes in cube data.
But when i execute the query it shows the previous values only.
So, i would like to delete the existed buffer in OLAP from that query.
So, please help me out regarrding this....
Its very urgent.
Points are assigned for better ones.
Thanks in advance
Peter

Cached results have a timestamp, which is compared with the timestamp of the last data load
and meta data change.
If new data is loaded before a cached query is executed again, the OLAP engine states that the
cached entry is out-of-date. It removes the old entry, loads the current query result from the
InfoProviders and writes back this new OLAP Cache entry. The OLAP Cache entry is invalidated
in the following cases:
Transaction Data Load to the underlying InfoProvider(s)
Deletion of Transaction Data from the underlying InfoProvider(s)
Master Data Load (and hierarchies) and subsequent change run of InfoObjects contained
in the query definition
Currency conversion rate change
This invalidation is also done for meta data changes, i.e. changes to the query structure, and
query generation.
Note that changes to key dates for time-dependent master data does not result in invalidation,
but in an additional cache entry.
In addition, the OLAP Cache can be invalidated and deleted completely via the OLAP Cache
monitor (transaction RSRT 􀃆 Cache Monitor or transaction RSRCACHE). One query entry in
the OLAP Cache can be invalidated by simply re-generating the query.

BOBJ - BW "Error getting hierarchies for dimension... "

Im still whitout a solution for this problem, however we have found a difference between the queries that work and the queries that dont work. The difference is in the hierarchies type but we dont know what is the problem exactly.
Does anyone know if there is an specyfic type of hierarchie that we need to use???
Regards

Hi,
I wonder why you are not using the BEx / BICS connection ? (instead of the old OLAP .unv)
the process flow for generating a universe would include the following SE37 function modules:
BAPI_MDPROVIDER_GET_CATALOGS
BAPI_MDPROVIDER_GET_CUBES
BAPI_MDPROVIDER_GET_DIMENSIONS
BAPI_MDPROVIDER_GET_HIERARCHYS
You should test these in BW .
It may actually be an authorization issue - perhaps your logon doesn't have infoobject authorizations for 0Plant?
Regards,
Henry
p.s. a quick Note search suggests : 1565615 - Error when creating a Universe from BEx: "A runtime exception has occurred. (Error getting levels for hierarchy ( dimension : Unknown error)"
--> "Business Objects Personalization objects" R21K900693 transport has not been loaded properly in the BW system, transaction STMS shows this trasport not loaded.

BW Hierarchies in OLAP?

Similar Messages

Maybe you are looking for