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

Similar Messages

BO 4.0 Advanced Analysis for OLAP - The MDAS service encountered an error.

Hi guru's,
We are running BO 4.0 SP02 Patch 11 with SAP BW 7 and experiencing the following error with Advanced Analysis for OLAP:
"Analysis edition for OLAP
The MDAS service encountered an error."
After you click show details:
"com.crystaldecisions.thirdparty.org.omg.CORBA.MARSHAL minor code: 0x0 completed: No"
I have researched into this and found forums such as:
http://forums.sdn.sap.com/thread.jspa?threadID=2053481
SAP KB 1560100 - BI4.0 Advanced Analysis Web problem: The MDAS Service encountered an error
SAP KB 1661163 - An error is generated when selecting a query or cube in Analysis for OLAP: Error 15
However, none of these have helped our situation too much.
We have rebuilt the windows server 2008 R2 recently, hence the process we followed was a fresh install of BO 4.0 SP02 platform & tools, and then patch 11 on top of these.
Crystal, WEBI's (using the same BICS connections as the AA's) and Dashboards are all working as per expected.
The errors are for every AA including ones with only 2 variable selections (light queries) to ones with many more. Hence it is platform wide for Advanced Analysis.
I have also tried creating new AA using existing BICS, new BICS existing AA, new BICS new AA all with no luck.
We have also created new Adaptive Processing Servers with only the MDAS as a common service, turned on tracing etc but nothing springs to us as to what is going wrong.
Any ideas would be greatly appreciated?
Thanks all,

Hi All,
After conversing with SAP support technicians we have found what is causing this issue.
On the windows servers we have the following installed locally:
- BO platform 4.0 SP02
- BO platform 4.0 SP02 patch 11
- BO client tools 4.0 SP02
- BO client tools 4.0 SP02 patch 11
- Crystal reports 2011 SP02
- Crystal reports 2011 SP02 patch 11
- Crystal reports for Ent SP02
- Crystal reports for Ent SP02 patch 11
It seems that the crystal reports 2011 or cr for Ent was causing an issue in the .WAR files that BOE uses to run Advanced Analysis for OLAP.
After uninstalling the two crystal products and removing any left over cr files in program files on the server, AA for OLAP works successfully in our environment.
The other point after this was i stopped the tomcat and SIA, i renamed the BOE folder under <install dir>\SAP BO4.0\Tomcat6\webapps and restarted the tomcat and then the SIA. In 4.0 when the tomcat is started again it will go and recreate the BOE folder from the BO directories effectively recreating the apps .WAR files under the webapps\BOE folder.
SAP will hopefully document this issue for other clients.
Cheers,

Two time-dependant entire hierarchies problem

I has one infoobject which is assigned two time-dependant entire hierarchies. The two hierarchies have two different time ranges. But when I ran a query which set a key date and choosed one of two hierarchies. The error happened. Error message "abort Hierarchy has been adjusted. start the query again". I tried again, the problem was still there.
Who can tell me what's the problem?

Hi Robert,
in OSS i found Note 659283 that seems to be suitable: are you runnig with SP lower than 16 on 3.0B or 10 on 3.1C? The message shuod have the Code BRAIN 074 ...
Hope it helps
GFV

BEx formula change not working in existing Analysis for Olap/Analysis for Excel reports

Hello all,
I posted this in Analysis for OLAP, but there has been no response so I'm hoping perhaps you BEx experts can help me.
I had to modify a formula in a Bex query to have it calculate the results of the formula by summation.
I checked the query using BEx Analyzer and it summed correctly. If I create a new analysis for olap report, it sums correctly.
If I modify an existing report, it does not pick up the change. Existing Analysis for Excel reports also do not pick up the new summary calculation.
Using the CMC, I edited the connection and reselected the Bex query, but that did not work either.
Here it is working in the query:
Line Discount is a formula with logic checking to see if "product list price total amount" is 0, set the line discount to 0; otherwise calculate it as "product list price total amount" - Net Sale. So the total needs to sum of the line discounts (0+2820+2820 = 5640) and not be the Overall result "product list price total amount" - Overall Result "net sale" (13960-96720= -82760).
Here it is in an existing Webi report - working:
Here is what is happening in an existing Analysis for OLAP report - not working:
I also tried to unselect Line Discount as a key figure from the existing report and reselect it, but that did not work.
I'd like to find a solution so that all the reports that use this query won't have to be rewritten.
I'm on BW 7.0 EP 1 SP 10 and BI 4.0 SP7 Patch 5.
Thank you for your help,
Susan

Hi,
Apply Exception aggregation on line discount formula--Exception aggregation as Total---Reference characteristic as Promega product.
Make sure to refresh the webi report once after the changes has been done.
If this does not work then you can apply summation calculation for that column at webi level as well.
Regards,
AL

Dynamic Description in Analysis for OLAP

hi.
I am trying to create an application in Analysis for OLAP where I am trying to populate the Dynamic description based on the value entered by the user.
It works in Bex queries, however I don't see the description populated when I create a analysis for OLAP report over the same Bex query. in fact I dont see the description of any bex query. is it not possible? I am using BO 4.1
Regards,
Mahesh

Hi Kathi,
finally we solved the porblem. i guess you are working with IE 8.0?
*if so, add the BO-Server (http://server.com) to your lokal intranet sites (inside the IE 8.0).
*also check document mode in IE 8.0 is set to Quirks Mode (under ''Tool/Developer Tool'') when opening the analyis olap report
then it should work.
regards
Tom

Excel export in analysis for olap not working

Hello!
I want to export from analysis for olap 1.1 to an excel file.
First I clicked on the export button, then I chose the wanted compontents and clicked ok.
But there happens nothting, but a new browser window opens and closes itself immediately.
Neither a dialog opens and asks where I want to save this excel, nore I found a related excel-file in my system.
Any ideas on this problem?
Regards,
Kathi

Hi Kathi,
finally we solved the porblem. i guess you are working with IE 8.0?
*if so, add the BO-Server (http://server.com) to your lokal intranet sites (inside the IE 8.0).
*also check document mode in IE 8.0 is set to Quirks Mode (under ''Tool/Developer Tool'') when opening the analyis olap report
then it should work.
regards
Tom

YTD calculation from BEx is not working in Advance Analysis for OLAP/OR Office

I have AA for OLAP based on BEx. There are YTD calculation in BEx Designer: User enters Period in variable, and in user exits, the Period Range is populated as "1 ~ UserEnteredValue" in second variable. In BEx, YTD is calculated based on the Restrictive KF for the period range, calculated in User Exit. This is working fine in BEx Analyzer, however in Advance Analysis (for OLAP OR in Ofice), the YTD value is not coming up they way it is in BEx Analyzer...
Anybody has any clue, why??
Thanking all of you in advance

Hello Sharma
If something is working for BEx Analyzer but not for Analysis OLAP or Analysis Office then this typically (but not always) indicates an issue with the BICS (BI Consumer Services) component.
I would suggest you contact support about this so the appropriate logs can be captured and the issue investigated by the BICS team.
Regards
Ian

Jumplink to Analysis for OLAP

Hello All,
It is possible (I guess no) to create a jumplink to another Analysis for OLAP.
If not possible, is it a planned enhancement ?
Thanks for your help.
Kind regards,
Bertrand

Hello Bertrand
The link Tammy posted is the right direction but it is not the complete answer. To link from one AOLAP workspace to another AOLAP workspace requires the use of RRI and OpenDocument. AOLAP is an RRI sender, but not an RRI receiver.
First use RSBBS to define an RRI link on the query being used by the source AOLAP workspace. This RRI link will be to a URL sender.
The URL sender then contains the OpenDocument URL link to the destination AOLAP workspace. You find this URL in the BI Launchpad by navigating the folders to the AOLAP workspace, right-click on it and choose "Document Link". Copy the displayed URL into the definition of the RRI URL Sender.
You can also pass context from the source AOLAP workspace as a value to a prompt variable in the destination AOLAP workspace.
The two screenshots below show this.... but the second screenshot is most relevent. This shows a parameter being hard-coded but you can also pass context dynamically.
Regards

Analysis for OLAP - HANA - Performance Issue

Hi Experts,
i have a performance issue using Analysis OLAP on HANA view: when i drag a dimension in the background section, is necessary to wait a lot of time and usually BI goes in error with timeout message.
The BI release is 4.1 SP4 and HANA is in SP7.
Thanks.
Andrea

Hi Andrea,
That's a bit odd. How big is that dimension? As you know, when you add a dimension to the background it automatically opens the member selector allowing you to pick the appropriate members.
The member selector can be tuned by changing the properties of the MDAS service. If you look at section 7.7.1 in the Admin guide entitled "Maximum number of members returned when filtering", you'll see how to reduce the number of members returned. This may help with your issue.
http://help.sap.com/businessobject/product_guides/sbo41/en/sbo41sp1_aa_admin_en.pdf
Best regards,
Philip

Time dependent Hirarchy Structure

Hi,
I need to create Hirarchy, i did not create before,
Please some one explaine me how to create     Time dependent Hirarchy Structure in CostCenter InfoObject.
Please, please help me.
Thanks

HI
Find the below link
http://help.sap.com/saphelp_nw2004s/helpdata/EN/0e/fd4e3c97f6bb3ee10000000a114084/frameset.htm
Time-Dependent Hierarchies
Use
In a hierarchy that is not time dependent, the characteristic values are always the same.
If you want to create views of a hierarchy that are valid for a specific time period, you need to create the entire hierarchy as time dependent.
If you want to model relationships that change time-dependently, you need to create the hierarchy structure time-dependently.
Functions
In InfoObject maintenance, you can set whether and in which ways a hierarchy is time dependent. You can choose from the following:
·         whether the hierarchy is not time dependent (Hierarchy Not Time-Dependent). This is set by default.
·         whether the entire hierarchy is time dependent (Entire Hierarchy Time-Dependent).
·         whether individual node relationships are time dependent (Hierarchy Structure Time-Dependent)
·         whether a temporal hierarchy join is used with time-dependent hierarchy structures (Use Temporal Hierarchy Join)
Entire Hierarchy is Time-Dependent
You can either load time-dependent hierarchies (see Loading Time-Dependent Hierarchies) or create them in the BI system (see Creating a Hierarchy). When you create a time-dependent hierarchy, you have to enter a validity interval (valid to and valid from fields).
If an entire hierarchy is time dependent, the system creates hierarchy versions that are valid for separate intervals. The system automatically uses the current valid version in this case. The hierarchy valid in each case can be uniquely identified by its technical name and the From-To Date.
In the InfoObject tree of the Data Warehousing Workbench, all time-dependent hierarchies under the associated InfoObject are displayed with the corresponding To Date, for example Time-Dependent Hierarchy 05/31/2000.
In reporting, the system returns the valid hierarchy when a query is executed using the query key date.
Within a restructuring company areas, you can create time-dependent versions of a hierarchy for the Main Area InfoObject. This enables you to compare the restructuring over different time periods in a query.
Time-dependent hierarchy 01/01/1999 - 05/31/1999
Time-Dependent Hierarchy 06/01/1999 - 12/31/1999
Main Area NORTH
Main Area NORTH
Area 1
Area 2
Area 2
Main Area SOUTH
Main Area SOUTH
Area 1
Area 3
Area 3
Area 4
Area 4
In reporting, you can work in the individual columns of the report structure with fixed date values. You may want to do this to compare Main Area North in the Time-Dependent Hierarchy 05/31/2000 with Main Area North in the Time-Dependent Hierarchy 06/01/2000 (simulation).
Time-Dependent Hierarchy Structures
You can either load time-dependent hierarchies (see Loading Time-Dependent Hierarchies) or create them in the BI system (see Creating a Hierarchy).
In hierarchy maintenance, you can determine a valid time interval for each hierarchy node (Valid to and Valid from fields).
In reporting, a hierarchy with time-dependent hierarchy structures is created either for the current key date or for the key date defined for the query. In addition, you can evaluate a hierarchy historically using the temporal hierarchy join.
You can assign an employee to different cost centers at different times within the context of a restructuring.
In the context menu of a hierarchy, choose Display Hierarchy to access the hierarchy display: Each node and leaf has been given a date symbol. Hierarchy nodes that are assigned to different places in the hierarchy structure, depending on the time, are displayed more than once. By double clicking on a hierarchy node, you can display the associated validity period for the node relation.
In the following example, you can double click on the Jones leaf to see that the worker Jones was assigned to region USA between 01/01/1999 and 05/31/1999 and Puerto Rico from 06/01/1999 to 12/31/1999.
In order to use a hierarchy with a time-dependent hierarchy structure in reporting, you require the following settings in the BEx Query Designer:
                            a.      If you want to evaluate a hierarchy with a time-dependent hierarchy structure for a fixed key date, enter the key date in query definition.
                            b.      If you want to evaluate a hierarchy with a time-dependent hierarchy structure historically, for a key date that is to be derived from the data, choose the temporal hierarchy join option and specify the derivation type for the key date.
For a more detailed description of the functions and differences between the two evaluation views, see Time-Dependent Hierarchy Structures in the Query.
In maintenance of the key date derivation type (RSTHJTMAINT) determine the rule you want to use to determine the key date from the data. In this way you determine the time characteristic and way in which the key date is to be derived.
       1.      First determine the time characteristic.
If you choose a Basic Time Characteristic as a time characteristic (for example, 0CALDAY, 0CALMONTH, 0FISCPER), you can use a key date derivation type of this kind for all InfoProviders that contain exactly one time characteristic that references the selected basic time characteristic. If there are several time characteristics in an InfoProvider that reference the basic time characteristic, you have to either determine the time characteristic more specifically or select a particular time characteristic from a particular InfoSet (Time Characteristic from InfoSet).
       2.      Determine how you want the key date to be derived from the time characteristic.
The following derivation types are available:
¡        First day of the period
¡        Last day of the period
¡        Delay by number of days (you specify this in the Delay by Days field). In this case, the key date is calculated from the first day in the period plus the number of days specified minus 1. If the key date does not fall within the period, the last day of the period is used.
Key date derivation type with (basic characteristic = 0CALMONTH, derivation type = u201Cfirst day of periodu201C):
·         For January 2005 the key date is calculated as 1/1/2005.
·         For February 2005 the key date is calculated as 2/1/2005.
Key date derivation with (basic characteristic = 0FISCPER, derivation type = u201Cdelay by number of daysu201C and u201Ddelay u201C = 29):
·         For K4/01.2005 the key date is calculated as 1/29/2005.
·         For K4/02.2005 the key date is calculated as 2/28/2005.
·         For K4/03.2005 the key date is calculated as 3/29/2005.
Note that the way in which you determine the key date derivation type affects performance. The number of data records that the OLAP processor reads corresponds to the level of detail on which the time characteristic and the leaf level lie. For this reason, choose the time characteristic as approximately as possible in order to keep the hierarchy small.
A small hierarchy has 100 leaves. For a period of 12 months, the OLAP Processor reads 1200 data records at month level. At day level, it reads 36500 data records.
Regards,
kumar reddy.k
Edited by: kumar reddy on Nov 18, 2008 10:50 AM

Time dependent hierarchy structure in SEM-BPS

I want to use a time dependent hierarchy structure in sem BPS to make combination chek and proposal in a layout.
I have manage a relation of type hierarchy (based on this hierarchy) in the characteristic relationship tab page of my planning area.
I open my layout to make entries in the future (next fiscal year) but the system doesn't propose me the datas valide for the next fiscal year in my hierarchy but the datas validate today.
There is a key date in the master data tab page of the planning area but it seems to have only effects on attributes with validity dates but not with hierarchy with time dependent hierarchy structure.
Thanks for your help.

Hi,
The key data that you enter in the planning area is only for time dependent characteristics and attributes. For the hierarchies in the characteristic relationships the current data is used.
If you still want to use a time dependent hierarchy for modeling the characteristic relationships you could use a characteristic relationship type exit. In the exit you can read the hierarchy with the proper date.
Best regards,
Gerd Schoeffl
SAPNetWeaver RIG BI EMEA

Time Dependent Info Object

Hi All,
I have an extractor that extracts data with DATEFROM and DATETO fo rthe time dependent HR employee related data for managers. But when it extracts into BI and loaded to Info Object the DATEFROM is not the same as what is extracted, it is 01/01/1000 instead of record specific.
Any idea why it is showing like it is?
Thanks,
Alex.

Beekay,
You are right. But in my case I extract only 200 records with DATEFROM and DATETO as 12/10/2006 - 12/31/9999. So I should expect my extracted 200 records and the system generated 200 records. But I have only 200 records but all the DATEFROM fields are changed with 01/01/1000. My PSA and R3 extractors are having the actual real DATEFROM.
Do you see where I have this issue?
Thanks,
Alex.

Restrict 2 KF with different value of Characteristics Time dependent

Hi,
in a query I should insert 2 columns (current year and previous year) in which the KF is restrict to same values of the characteristic that it is time-dependent, but in query I can use only a value of key-date How can I do?
Thanks.
Charly

Hi Kaled,
I have not perhaps understood. I explain you with an example.
My MasterData have the caracteristic Car1 time dependent:
CUSTOMER            OBJV.       DATETO    DATEFROM CAR1
000000000000029000 A       30.06.2007 01.01.1000
000000000000029000 A       31.12.2008 01.07.2007 A10
000000000000029000 A       30.06.2009 01.01.2009 A11
000000000000029000 A       31.12.9999 01.07.2009
In my query Sales, I have to get:
Customer             Value 2008 (A10)       Value 2009 (A11)
29000                          100                    500
where the value 100 for 2008 is sales for the value A10 time dependent and the value 500 for the value A11 time dependent.
In the query how to restrict the value S1 on KF1 e the value S6 on KF2 when it are time dependent and in the query property i have the variable keydate 0DAT ?
You can make me an example of as to build the restrict KFs?
Many thanks.
Charly

Time Dependency Master Data Load

Hi:
This is my first time to work on time dependency master data. I need help!
I first deleted master data and cleaned up the PSA for material sales.
Then I have turned on the feature of time dependent on the info object for material sales. Save it and activated the object.
Then i have problems by loading the master sales attribute data in PSA. The error is: on every record of material, it has "invalid 'to' date '00/00/0000'" and "invalid 'from' data '00/00/0000'".
Is every process i did wrong? What is the process to work on time dependent master data? and loading the data?
Thank you!!

Hi,
After turning on the time dependence...you get an extra field in the key of the master data table Q table date to and a new field date from as a new field.
These two fields needs to be mapped to date to and date from R/3 source as well.
If there is no source field for these two then you need to make sure to get the values for these fields.
Just check if you are getting any field like that from R/3...right now i think you have left the mappings for these fields as blank.
Thanks
Ajeet

Measures differing if we drill down by time-dependent Attributes

Hi Everyone,
I am having 2 similar reports,one based on a Cube and other based on a Multi Provider.
The data is being fed into these two InfoProviders,from exactly same sources.
Now,if I display the measure(eg. Invoice spend),in both the reports based on the above two InfoProviders,the overall Invoice spend matches across both the reports.
But if we drill down by a characteristic(eg. BU- Low or BU-High) they differ.But by drilling down by any other characteristic they matches.
I have found out,that the nav. attributes(BU- Low and BU- High) are checked "time dependent".
While the others,for which the result is matching are not.
Can this be a possible reason for the mentioned anomaly?Or can there be some other reason to this difference?
Thanks,
Brinto.

Hi Chinnapa,
Just want one clarification here.
take one example.
if you have loaded data on 10th April, then date range is 10th april to 30th april.
then you are loading data on 11th april, at that time you want date range 11th april to 30th april.
So what will happen to 10th april data? what range? 10th to 10th?

Time-dependent BW hierarchies in Analysis for OLAP

Similar Messages

Maybe you are looking for