Alternative tree issues for Time dimension

Hi, there. I am developing a purchase system. We have two types of date one for goods receing and one for settlement date.
I plan to create two alternative trees in Time dimension one for receving date and the other for settlement date.
For each alternative tree, there would be four levels (Year->Quarter->Month->Date). Does Essbase support this kind of design?
I would like leaf note be date format therefore I could use pre-defined Time function such as YTD, MTD etc.

I'm just kibbitzing on this one -- I like Glenn's suggestion the best because of its simplicity (elegance?).
One dimension to maintain versus two has to be the better approach. With that View or Type or whatever dimension you don't (I think) lose any analytic capability unless you specifically need to crossdim the two calendars, but that would be an almost herculean task for a given intersection given all of the potential nonintersections. And that requirement isn't in your post, so his suggestion would work.
Regards,
Cameron Lackpour

Similar Messages

Creating time source table for time dimension?

hi exports
can any one helps to create time source table or view_ for time dimension for awm_ mapping ?
thanks
Edited by: 1008794 on May 30, 2013 12:21 AM

No. Thank you very much for reply.I have solved my problem
Edited by: 1008794 on Jun 3, 2013 6:30 AM

Primary Key and Chronological Key for Time Dimension

Could someone please shed light whether it's better to use normal PK or Calendar Date (which is a chronological key on the most detailed level). I tried both and haven't noticed any difference. But my understanding is that I still need to have the PK key on the most detailed level in time hierarchy.
Thanks

Matt,
the PK of the Time Dimension is a regular sequence numeric key. I have it defined as a logical PK for the dimension. However, I guess I was talking about hierarchy key. I tested it either way and the query time is the same. So I guess it doesn't really matter.
--------Year
Year (chronological key and primary key)
------------------Quarter
Quarter (key)
Quarter+Year (primary key, chronological key)
---------------------------------Day Detail
PK (key)
Date (primary key , chronological key)
I hope it makes sense.

Best Practice for Time Dimension

I am designing a new outline. I need to set up a time dimension for every day, perpetually. In the past I would set up one member for years i.e. 2010, 2011, 2012... and a second dimension with the days i.e. Jan 01, Jan 02.
Is there a better way than this? I would like to do it in one dimension if possible.

If you create a new ASO (remember, this does not work in BSO) database, right click in the outline (okay, the completely blank outline).
You should see a pop up menu with "Create date-time dimension..."
I should also note that you have to click on the word "Outline: dbname" to do this.
I wonder if you are trying to do this in a BSO app as that will make the menu item show up unselected.
Regards,
Cameron Lackpour

Updating master data for time dimensions from front end

Hi Experts,
I am sure this must be handled in a very straight forward way. Just want to know the best practice here. We are working on a copy of appset and want to completely revamp the time dimension papers as per client's fiscal year which is april to march every year.
When we have deleted all the existing memebers from the time dimension master data from BPC front end and replaced with new memebers, the task is getting completed successfully.
But when I check back in BI for the master data, it has not replaced all the existing members. How best to handle this?
The transaction data is deleted from all the application cubes. Are there any checks to be performed?
Thanks,
Santosh

Closing the thread as I could not replicate the problem. The problem is resolved.
Thanks,
Santosh

Validity period merging issue for time dependent master data

Hello All,
I am trying to load the data from DSO ZDSO1 to Master data object ZCASE1. Attribute "ZATR1" of ZCASE1 is the time dependent attribute of ZCASE1.
ZDSO1 contains "Changed On" field which defines the "Valid From" period for attribute "ZATR1" of case ZCASE1.
For eg.
ZDSO1 contains below records for Case 'C1':
Case ID     Changed On ZATR1
C1              01.01.2014     01
C1              02.01.2014     01
C1              02.15.2014     07
C1              02.17.2014     07
My transformation from ZDSO1 to infoobject ZCASE1 contains below mapping:
Case ID - Direct Mapping - ZCASE1 object
Constant value '12/31/'9999' - VALID TO field
Changed on - Direct Mapping - DATE FROM field
ZATR1 - Direct Mappint - ZATR1 object
After loading the data from ZDSO1 to ZCASE1 below results are obtained:
Case ID     VALID FROM VALID TO   ZATR1
C1             01.01.1000    12.31.2013 BLANK
C1             01.01.2014    01.31.2014 01
C1             02.01.2014    02.14.2014 01
C1             02.15.2014    12.31.9999 07
Time-Dependency is define correctly however my concern is why second and third records were not merged together. Instead of having four records, I should have ideally received THREE records. As shown above, third and fourth record (value 07) from ZDSO1 are merged into SINGLE record in infoobject ZCASE1.
For the subsequent data, it again does the same thing.
For eg. If I receive below Delta record from ZDSO1:
C1   03.01.2014 07
I get FIVE records in infoobject ZATR1 as shown below:
Case ID     VALID FROM VALID TO   ZATR1
C1             01.01.1000    12.31.2013 BLANK
C1             01.01.2014    01.31.2014 01
C1             02.01.2014    02.14.2014 01
C1             02.15.2014    02.28.2014 07
C1             03.01.2014    12.31.9999 07
In my understanding, BW system should have merged this Delta record with the last record present in infoobject because both the records have same ZATR1 value.
I would really appreciate your help/suggestions to understand/resolve this issue.
Thank You,
Nilima

Hey Arun,
While there wasn't any other time-dependent attribute apart from ZATR1, there is another time-independent attribute ZATR2 of ZCASE1 whose value was changed and hence somehow system was not able to merge the validity range.
Thank You.
Nilima

How to build dynamic time series for the time dimension

I am planning to build dynamic time series using rule file instead of manually.Please let me know if there is any property need to assign to enable DTS property for TIME dimension.
Edited by: 844104 on Mar 14, 2011 3:37 AM

In the load rule in the dimension build settings you would need to go to the tab dimension definition, choose the time dimension and right click on it. Select Edit properties. If you have not done so, set the dimension to be the time dimension. Then go to the generations/levels tab and set the generation names you need. For example if you want YTD, you would set the generation name to Year, if you want QTD set it to Quarter. You would set the number to the generation number that coorisponds to the generation. The DBAG has the list of names for all of the DTS members.

EXPAND INTERMEDIATE NODE OF TIME DIMENSION

Hello!
Can anybody help me? we created members for time dimension like this:
2010.TOTAL
___2010.JAN
______2010.JAN.Q1
______2010.JAN.Q2
If we try to expand, like a column, this dimension in a Report, adding the ID in the "MemberSet", it's only possible for the TOTAL and the Q1 or Q2. But It's not possible for de month directly. In that case we have an EVDRE error "invalid member in <memberset>"
Anybody know what can I do to expand the intermediate node of the tree?
Thank you very much!!
Elena

Hi Elena,
In one of the empty cells, type the below formula
=EVPRO($B$3,$B$23,"YEAR")&".JAN.F1,"&EVPRO($B$3,$B$23,"YEAR")&".JAN.F2,"&EVPRO($B$3,$B$23,"YEAR")&".FEB.F1,"&EVPRO($B$3,$B$23,"YEAR")&".FEB.F2,"&EVPRO($B$3,$B$23,"YEAR")&".MAR,"&EVPRO($B$3,$B$23,"YEAR")&".APR,"&EVPRO($B$3,$B$23,"YEAR")&".MAY,"&EVPRO($B$3,$B$23,"YEAR")&".JUN"
Where B3 is the cell with the application name
B23 is the cell with the time member
EVPRO($B$3,$B$23,"YEAR") is going to fetch the year from the member in the cell B23
Once you have entered the above formula in an empty cell, and if you have 2010.JAN in the cell B23, then your cell should display the value as
2010.JAN.F1,2010.JAN.F2,2010.FEB.F1,2010.FEB.F2,2010.MAR,2010.APR,2010.MAY,2010.JUN
In the memberset of the time dimension, refer to the cell in which you have entered the above formula.
Hope this helps.

Time Dimension Type allows different values in attributes - Bug or Feature?

Not sure if this is a bug or a feature.
But if one has multiple hierarchies on a Time dimension. You have the ability to specify different values for member attributes in different hierarchies.
Example.
Hierarchy A has MIN_ID for it's Member and uses MIN_END_DATE for it's END_DATE
Hierarchy B has MIN_ID for it's Member and uses SESS_END_DATE for it's END_DATE
As per this post and David Greenfield's comment:
Dimension Sort issue when multiple mappings for different hierarchies
"Are you attempting to map the same attribute, SORT, to different columns in the two hierarchies? Put another way, do you expect the same member to have different values for the attribute in the two different hierarchies? If so, then this is a problem since a member must have the same value for the attribute regardless of the hierarchy."
Unlike a user dimension, a time dimension appears to allow this and it appears to work as intended. Is the behavior in this case intended to be different between a user and time dimension?

I think that this is not a bug. There is an incompatibility in design which prevents you from using the same attribute differently for both hierarchies.
NOTE: Unlike parent relationship which depends on <dimension, dimension hierarchy>, Dimension Attribute is dependent on <dimension> alone, not dependent on <dimension, dimension hierarchy> combination. Hence it can only take on 1 value for 1 dimension member.
I think that the time dimension only appears to allow this. The key thing to check is for Time Dimension members which are common to both the hierarchies. Only one of the mappings will take effect (usually the hierarchy which is loaded last will remain in the aw/usable for queries, reports.. it would have over-written the earlier attribute value loaded as per the earlier hierarchy load).
Visualize a dimension as a long list of members which are built up contiguously on a per hierarchy, per level process using the mapping information saved. Once a member is defined (created) via Hierarchy A, it wont be created once again while loading Hierarchy B but is instead updated or redefined based on Hierarchy B's mapping info.
Assuming the dimension load attempts to load Hierarchy A first and then Hierarchy B,
* Dimension load for Hierarchy A will define the various members using MIN_ID and set the END_DATE attribute to value=MIN_END_DATE
* Dimension load for Hierarchy B will re-define the various members using MIN_ID and re-set or over-write the END_DATE attribute to value=SESS_END_DATE
* In this case, it looks like all members are common for both hierarchies (as both members are mapped to same column MIN_ID) and you would end up with END_DATE=SESS_END_DATE.
Actually whether all members are common to both hierarchies or not depends on the quality of data in your snowflake/star table: if parent level for Hierarchy A as well as Hierarchy B is setup fine then the members will be same set (overlapping in whole). If some rows for MIN_ID have parent column for Hierarchy A setup correctly but parent column for Hierarchy B =null or invalid value then that member will exist in Hierarchy A alone and would contain END_DATE=MIN_END_DATE as the corresponding update along Hierarchy B would fail due to hierarchy data quality issues (join from current level to parent level).
As regards a solution to your problem, you should not use the same attribute "SORT" for dual purpose (both hierarchies). Instead define attributes SORT_A and SORT_B and make them enabled for Hierarchy A, Hierarchy B respectively and map/use them appropriately in your reports.
HTH
Shankar

Time dimension BPC10

Tried to use Time dimension in one of the reports in BPC10NW. The expansion of Time dimension is following the alphabetical order. Example: If Q1 of a year is expanded, its showing up Feb, Jan, Mar. Same is the case with other Quarters(Q2/Q3/Q4). All the Id's in the Excel membersheet for Time dimension is also being automatically sorted alphabhetically. Anyway to fix this to show up in a regular way(Jan, Feb, Mar)...?
Thanks
KV

Found an SAP Note #1643521related to this issue.

Time Dimension Consistency Check Failed

Dear all,
Got a issue..
A cube which is found to be active in RSA1, but when we do the consistency check for time dimension in the transaction RSRV, we get the following error.
Unknown, profound errors with instance creation in test "CL_RSRV_CHK_TIM_DIM"
Pl help to resolve this issue.
Thanks,
Ramya

Hi Ramya,
Welcome to SDN...!!
Check with the Correct Error option in RSRV after selecting testing ur cube.
Best Regards,
SG

Time Dimension and database 8.1.7.3

Hi,
I imported owb_bp project that is located in: <OWB install directory>\owb\misc\time directory into my OWB. Then i copied the standard time dimension and mapping from that project to my project. I changed the necesary things(removed day level, did reconcile inbound on a dimension in a mapping with "match by bound name" strategy) in the dimension and mapping and when i tried to deploy the mapping i got an error:
VLD-3268: A mapping can be deployed only if the database version is Oracle 9.2 or higher.
Is it true that you need Oracle 9.2 or higher for deploying this kind of time dimension. If that is so, how can i create a time dimension that is going to work with Oracle 8.1.7.3
Thx

Thanks for your answer Igor.
The problem is that we cant upgrade our database to 9.2, becouse our customers dont use it, so we are stuck with 8.1.7.3, which by the looks of things doesnt support a lot of things in OWB 9.04.
So I would really appreciate it if someone could give me some pointers as to how to generate data for time dimension, thats going to work on database 8.1.7.3.
Thanks you all for your time.

Setting up a TIME dimension in OBIEE

Hi,
We have an Oracle OLAP Cube built using AWM v10.2.0.3A. We have also created a relational view for this cube (using the OLAP view generator) and are now using this view as a data source in OBIEE v.10.1.3.3.2.
As part of defining the Time dimension in the Business Model Layer of OBIEE repository, we have done all the relevant mappings to the TIME dimension as in the AWM Cube and have marked the dimension as type 'TIME'. Also, for the TIME logical table, we have defined each level (All Years, Year, Month, Quarter, and Day) to have its own chronological key with unique values at all levels. The primary key for our TIME table in the business layer is 'Day'. This level 'Day' is mapped to TIME_DAY_LVLDSC column of the relational view created over the AWM cube. The data type for this column is "VARCHAR". (We basically picked up all the 'Description' columns while creating the view over the cube!)
With this background of the TIME dimension structure, here is the problem scenario:
When we try to create a report with one AGO and one TODATE function defined over the "Day" level (both are defined as logical columns), then the report takes forever to run and never comes back with any data/error even for a handful of rows. We are seeking the forum's help on the following:
1. Is it necessary for the primary key 'Day' of the TIME logical table to be of type DATE? If yes, does this mean that we have to change the column data type in our cube (or select a 'date' type column to be a part of the view and then redo the mapping in the repository) or do we just make a change to the column data type in the physical layer of OBIEE repository?
2. Going by the description above, is there something missing (other than point 1. above) in the setup of the TIME dimension in OBIEE so as to make it usable for Time Series type of calculations/functions?
Any help is much appreciated.
Thanks and Regards,
Piyush

Hi Wildmight,
Thanks a lot for your kind inputs.
1. No, VARCHAR is fine. You should have also defined unique time keys in your time dimension (Quarter Year, Month Year) and check box 'time dimension' in the properties of your time dimension.
-->> The Time dimension that we have defined in the Business layer of the repository is mapped to the respective level columns in the AWM cube and has already got unique members at each level. We are using the "Description (LVLDSC)" columns for each level and have defined the "Description" column to have unique values at each level. A sample data set looks like :
Year:
2007
2008
Quarter:
QUARTER1 2007
QUARTER2 2007
QUARTER1 2008
QUARTER2 2008
Month:
JANUARY 2007
FEBRUARY 2007
JANUARY 2008
FEBRUARY 2008
Day:
Monday, January 1st 2007
Tuesday, January 2nd 2007
So in the above case, do we still need to define a unique key for each level like Quarter Year, Month Quarter, etc.? (Please note that the check box for 'TIME' dimension is checked !)
2. Is your AGO based on TODATE? or your TODATE based on AGO?
-->> I am not sure what this really means - however I can tell you that we have created two new logical columns (in the fact table in Business Layer) : one to show the measure as TODATE for Day level, and the other to show the measure as Day Ago.
So it means that we are trying to create two reports with three columns as below:
- Day Measure on Day Measure Todate (Day)
- Day Measure on Day Measure Day Ago (Day, 1)
I hope I have been able to clarify the problem scenario with this. Does this setup seem correct to you?
Many thanks for your help.
Best Regards,
Piyush

Problem with drill down in time dimension - OBIEE 11G

Hello There,
I have a problem with drill down in time dimension. The hierarchy for time dimension is " Fiscal Year---> Fiscal Quarter---> Month(Name)--->Date". When I select a Time dimension and click results its getting opened in a Pivot table view. The problem here is, when I click the "Total" its getting drilled down to Year ---> Quarter but when I click on "+ sign next to quarter" it should drill down to month for that particular quarter for that particular year but its drilling down to month for that particular quarter for all years.
Any suggestions are much appreciated.
Thanks,
Harry.

1.) Congrats for resurrecting a year-old thread.
2.) Your answer is here: "Check the level key of the quarter level...it should include both quarter and year columns. Since a specific quarter occurs every year, quarter column alone can't be used as the level key."

Time Dimension - Additional Attributes..

Hi
We are building a Financial Services BI Applications. In one of my Cube, for Time Dimension, i need to add more attributes like
for Month Level i need the following
a) End Date of the Month
b) No of Days in the Month
at Quarter Level
a) End Date of the Quarter
b) No of Days at the Quarter
and likewise.
I can do this in AWs using attributes, however in essbase since i have to tag the TIME dimension as DENSE, it is not allowing me to create any attributes. Has somebody solved this problem in the past. Please help.
Thanks
bala

Any more recommendations please..
I cannot use UDAs as it expects that the consumer of the UDA knows the value set.
i.e. in Time Dimension assume the leaf is
200701 (UDA 31)
I would want something like this
if provided 200701 then the server should return 31 as the number of days.. However if i use UDA then i can only check (if @UDA(200701) = 31) then
here it assumes that i know the attribute value before hand which i would not know..
Please help as we are reaching a critical stage in our project
Thanks
bala

Alternative tree issues for Time dimension

Similar Messages

Maybe you are looking for