Time Dimension: Naming requirement?

I am trying to create a YTD calculation in a cube using BI beans/Jdeveloper. This used to work fine in a previous version of the cube. In the new cube, the 'next' button remains grayed out if I select the 'YTD calculation (or any other time related calculation)
One of the changes between the cubes seems to be that we renamed the time dimension to t_time_month. I am wondering if BI beans has a requirement that the time dimension ends in 'Time', similar to the requirement that the dimension name needs to end with 'Name'. I can't find a way to tell BI beans which is the time dimension, so maybe the name is the only way it could know?
Is there a document that describes this type of requirements for BI Beans?
Thank you in advance for your help.
Cor Wooning

Hi,
There are certain requirements for a dimension to be of type time. Each level in the dimension must have two attributes: End Date and Timespan.
If your DW environment is purely relational you can use OEM to check the status of your time dimension. There is a radio button to indicate if the dimension is of type time. You can try setting this, when you apply the change OEM will validate the dimension to see if it complies with the requirements for a time dimension.
If you are using Oracle Warehouse Builder to construct your DW environment, it provides a default mapping and dimension within a best practice MDL file. (it is located in the OWB_HOME/owb/misc/time directory).
There should me information in the OLAP Developer and user manuals relating Analytic Workspace dimensions
Hope this helps,

Similar Messages

'Time' dimension hierarchy Required

Dear all,
We came across one requirement where 'Time' dimension having 365 days along with month, quarter, halfyear and yeartot as their ancestor.
"Time" Dimension hierarchy:
Time
- Yeartot
- Half year
- Quarters
- Months
- Days
Also we need alternate hierarchy in time dimension:
Time
- Yeartot
- Weeks
- Week1
- 1 Apr
- 2 Apr
- Week2
Weeks are Monday to sunday.
We are using 11.1.1.2 version.
Can anyone suggest me how to achieve this in Planning?
Thanks in Adv,
Bunny

I believe the limit for Planning's Period dimension is 400 members.
That's going to get you the first bit, but not the alternate hierarchy.
Does this alternate hierarchy have to be in Planning, or could it be in Essbase only?
This isn't exactly a recommended strategy, but I think you can still use the HSP_UDF UDA in Essbase to basically make your alternate hierarchy happen only in Essbase. It won't show up on forms, but will be available from a reporting tool.
I have not tried HSP_UDF (it was used all the time on pre System 9 (maybe Planning 4) Planning apps to get in member formulas) in 11, so it may be worth trying a small alternate hierarchy with that UDF and then forcing a refresh to see if it still sticks about.
Regards,
Cameron Lackpour

Valid time dimensions

Hi,
When reverse engineering an Oracle 12c database (using Data Modeler stand alone, 4.1 EA2 using a thin jdbc connection) on some tables valid time dimensions are detected in the database.
This suggests the existence of a period for clause on the table in the database. This is not present, however.
These valid time dimensions are reversed engineered to the model.
Where can these valid time dimensions (named, for example "SYS_STSSAKFUXTO4R$45K8IN#E2LV5") be found in the database ?
And why is it not possible to exclude the valid time dimensions in comparing the model with the database ?
Richard.

Hi,
Thnaks for sorting this out. Please note that this also causes a lot of differences being reported when synchronizing the model with the database (or vice versa).
I assume this behaviour will disappear once the bug is fixed and the "valid time constraints" have been erased form the model.
Is this correct ?
Richard.

Time Dimension Consistency Error in RSRV - Need Help

Hello,
I am having a problem when I run RSRV on our 0ECCS_C01 cube. We have extended the time characteristics to include posting period (0FISCPER3). The only problems RSRV finds is when 0FISCPER is period 0 and 0FISCPER3 is 0. For some reason, these are being flagged as inconsistent. I think this is causing negative performance on our queries because I feel partitioning may not be getting used from some research I've done due to this inconsistency.
Here are the errors I am getting from RSRV:
1. Record with the DIMID 410 contains non-fitting time characteristics
Message no. RSCV053
Diagnosis
The data record of the time dimension table with the described DIMID contains values for time characteristics that do not fit together.
2. This DIMID is used by 9860 records of the fact tables
3. No master data found for characteristic of test described subsequently
Message no. RSCV083
Diagnosis
No master record exists for a characteristic used in the time dimension. The characteristic is one of the characteristics described in the following message with one of the SIDs named there or it is the fiscal year variant that was derived from one of the characteristics.
4. Time characteristic 0FISCPER value 132000000 does not fit with time char 0FISCPER3 val 0
Message no. RSCV054
Diagnosis
The described values of the specified time characteristics do not fit together.
How exactly can I get these time characteristics to "fit" properly? Will it require a data reload?

hi,
did u get answer to ur problem.
thanks.
Raju

OWB 10.2 - How are you handling time dimensions?

Hi all,
I am struggling with what should be a simple thing to do. I want to create a time dimension and then have many "roles" or aliases for the time dimensioin WITH UNIQUE COLUMN NAMES across all of the roles.
When the time dimensions are deployed to Discoverer, I want every one of them to have unique names and the column names within the time dimension have a unique prefix so that report users know which date column is from which table or dimension.
Here's what I've done and failed at:
1. Use the time dimension wizard - I can create any number of dimensions and corresponding tables BUT all of them have the same column names and I would have to manually change each and every one of them to get unique names (which may not even be possible with the wizard). Also, because I require ISO weeks, I can't really use the wizard at all.
2. Manually create a time dimension (that supports ISO weeks) and create multiple "roles" for it:
Thanks to a bug, I cannot exceed 4 roles without OWB crashing. Even with those 4 roles, when deployed to Discoverer, every attribute within the item folders has the same name. When I drag them to a report, there is no way to tell one from another. Is there some way I could do this without having to manually rename hundreds of columns?
3. I wrote an elaborate SQLPlus script to copy and prefix dimensions and tables from a base dimension and table. When I then import the Dimension to OWB, the metadata for business identifier and surrogate identifier is not there and any cubes using those dimensions do not work with these attributes missing. I can't find a way to cleanly reverse engineer these into OWB.
I have a cube with 12 dates - each of which should be a foreign key to a date dimension.
How can I have all of these be uniquely named with uniquely named columns?
How can I make it easy for my reporting users to select dates onto their reports?
I hope I am missing an obvious solution, because so far, I cannot see where Oracle Warehouse Builder supports such a basic data warehousing concept.

Well, since I'm the only one obsessed with time dimensions I guess, here is my ugly workaround:
1. I create a base time dimension in OWB which I named 'ATLAS_TIME_DIM'
2. I run the OMB script below which clones the dimension and table and renames the columns and attributes with a user supplied suffix. The end result is I get a full copy of the time dimension metadata with uniquely named columns.
You then have to deploy the objects, and with SQLPlus, ensure that the table gets its data copied from your original table. Hope it helps someone until we have better Time dimension support from OWB.
OMBCONNECT repos/password@SERVERNAME:1521:sidname
# Prompt for new Dimension name and prefix
puts -nonewline "Please enter name for new Dimension: "
gets stdin newDim
puts -nonewline "Enter Prefix for Dimension table columns: "
gets stdin dimPrefix
# Change into ATLAS_DW module in project ATLAS_DW
OMBCC 'ATLAS_DW'
OMBCC 'ATLAS_DW'
# Copy the ATLAS_TIME_DIM to this dimension
OMBCOPY DIMENSION 'ATLAS_TIME_DIM' TO '$newDim'
# Set the business name
OMBALTER DIMENSION '$newDim' \
SET PROPERTIES (BUSINESS_NAME) VALUES ('$newDim')
# Unbind the dimension from original table
OMBALTER DIMENSION '$newDim' \
DELETE BINDING
# Bind to new table
OMBALTER DIMENSION '$newDim' \
IMPLEMENTED BY SYSTEM STAR
# Add a prefix to all of the Dimension attributes
set attrList [OMBRETRIEVE DIMENSION '$newDim' GET DIMENSION_ATTRIBUTES]
foreach attrName $attrList {
OMBALTER DIMENSION '$newDim' \
MODIFY DIMENSION_ATTRIBUTE '$attrName' RENAME TO '$dimPrefix\_$attrName'
# Add a prefix to all level attributes of the Dimension
set levelList [OMBRETRIEVE DIMENSION '$newDim' GET LEVELS]
foreach levelName $levelList {
set levelAttrList [OMBRETRIEVE DIMENSION '$newDim' \
LEVEL '$levelName' GET LEVEL_ATTRIBUTES]
foreach levelAttr $levelAttrList {
OMBALTER DIMENSION '$newDim' MODIFY \
LEVEL_ATTRIBUTE '$levelAttr' OF LEVEL '$levelName' \
SET PROPERTIES (BUSINESS_NAME) VALUES ('$dimPrefix\_$levelAttr')
OMBALTER DIMENSION '$newDim' MODIFY \
LEVEL_ATTRIBUTE '$levelAttr' OF LEVEL '$levelName' \
RENAME TO '$dimPrefix\_$levelAttr'
# Add a prefix to all of the table columns except DIMENSION_KEY
set columnList [OMBRETRIEVE TABLE '$newDim' GET COLUMNS]
foreach colName $columnList {
if { $colName == "DIMENSION_KEY" } {
puts "$colName"
} else {
OMBALTER TABLE '$newDim' \
MODIFY COLUMN '$colName' SET PROPERTIES (BUSINESS_NAME) VALUES ('$dimPrefix\_$colName')
OMBALTER TABLE '$newDim' \
MODIFY COLUMN '$colName' RENAME TO '$dimPrefix\_$colName'
puts "$dimPrefix\_$colName"
OMBSAVE
OMBDISCONNECT
Message was edited by:
mike_fls

Date and Time dimensions

After reading the following article, I have decided to use SSAS dimension wizard for generating our Date dimension, which creates a DATETIME PK.
http://www.made2mentor.com/2011/05/date-vs-integer-datatypes-as-primary-key-for-date-dimensions/
I have also created a separate Time dimension as granularity of an hour is required.
The Time dimension is very simple and only contains a surrogate key (INTEGER) and actual time in hours (VARCHAR).
DimTime(TimeKey, TimeInHours)
Our Fact table will now have a link to both the Date and Time dimension using the PK's.
Our analysis is required by hour, day, week, month and year.
My query is; Will this current structure cause any problems when creating MDX scripts to analyse our data (i.e. drilldown and rollup queries) Hour - Day - Week - Month - Year

Hi Darren,
According to your description, there a day and hour granularity in your fact table, so you want to a hierarchy like Hour - Day - Week - Month - Year, right?
In your scenario, you created a time table that only contains a surrogate key (INTEGER) and actual time in hours (VARCHAR). We cannot create a Hour - Day - Week - Month - Year hierarchy without ant relationship between date table and time table. As per my understanding,
you need create a foreigner key in time table, and join those table in the data source view, then you can create such a hierarchy. Here are some links about create time dimension, please see:
http://www.ssas-info.com/analysis-services-articles/59-time-dimension/1224-date-and-time-dimensions-template
http://www.codeproject.com/Articles/25852/Creating-Time-Dimension-in-Microsoft-Analysis-Serv
Regards,
Charlie Liao
TechNet Community Support

ERROR while loading time dimension table

i need to load time dimension from csv to oracle table, while loading i got the error.
my source data type is date and target is date.
ODI-1226: Step sample day fails after 1 attempt(s).
ODI-1240: Flow sample day fails while performing a Loading operation. This flow loads target table W_SAMPLE_DATE.
ODI-1228: Task SrcSet0 (Loading) fails on the target ORACLE connection Target_Oracle.
Caused By: java.sql.SQLException: ORA-30088: datetime/interval precision is out of range
while creating c$ table
create table WORKSCHEMA.C$_0W_SAMPLE_DATE
     C3_ROW_WID     NUMBER(10) NULL,
     C1_CALENDAR_DATE     TIMESTAMP() NULL,
     C2_DAY_DT     TIMESTAMP() NULL
)

check the source data and use the correct function eg TO_DATE(SRC.DATE, 'MM?DD/YYYY') use NVL if required.

How do I include 'Time' in a time dimension?

I have a requirement where I need to classify the data in the warehouse based on date and time (example : between 10 am to 11 am, 3.00 pm to 6.00 pm like that).
The time dimension created by OWB contains only the date part and when I load the data I use the expression TO_NUMBER(TO_CHAR(input,'YYYYMMDD')) to populate the date.
But I would like to include the time also in the expression like 'YYYYMMDDHHMISS'. But unfortunately the OWB generated time dimension does not have data in this format.
How do I do that? Any pointers?
thanks in advance

You rather create 2 dimensions: Time and TimeOfDay. The first one will have all the date values with it characteristics. The second one will hold the all the possible HH24:MI:SS values with it's characteristics, for example which hour and which part of the day it is (Morning, Afternoon, Evening, Midnight or whether it's lunch time or not), depending on the requirements.
If you try to combine them both into 1 dimension you will get 86400 dimension records every day. Your dimension table will probably will become bigger than the fact tables.

Time Dimension Roll-Up Not Working

Hi Gurus,
We are on BPC NW 7.0 SP04. We are experiencing a strange problem with Time dimension. Even after defining the hierarchy correctly, the values are not being rolled up the hierarchy. Our requirement is to capture data at quarter level and year level. So we have defined the time dimension in following manner:
ID                     EVDESCRIPTION   PARENTH1     LEVEL         YEAR   PERIOD STYLE   MONTHNUM    TYPE   TIMEID           HLEVEL
2007.TOTAL     2007 TOTAL                               YEAR             2007     TOTAL   T3                12                       ACT   20070005        1
2007             2007                   2007.TOTAL   QUARTER     2007     Q1        T2                13                       ACT                        2
2007.Q1             2007 Q1                   2007.TOTAL   QUARTER     2007     Q1        T1                  3                       ACT   20070001        2
2007.Q2             2007 Q2                   2007.TOTAL   QUARTER     2007     Q2        T1                  6                       ACT   20070002        2
2007.Q3             2007 Q3                   2007.TOTAL   QUARTER     2007     Q3        T1                  9                       ACT   20070003        2
2007.Q4             2007 Q4                   2007.TOTAL   QUARTER     2007     Q4        T1                12                       ACT   20070004        2
Here TYPE is a custom dimension property . As the members depict, 2007.TOTAL value should be calculated as the sum of 2007.Q1, 2007.Q2, 2007.Q3 and 2007.Q4 (Quarters and Years are mutually exclusive in our case). But when we maintain data for Q1,Q2,Q3 and Q4, the TOTAL value is displayed as the value of Q4, and not the sum of quarters. We have tried changing MEASURES from PERIODIC to QTD and YTD, with no effect. We thought that it could be a problem with BI, and so built a simple BeX Query on top of the BPC application cube. But in the BEX query, the time dimension is properly aggregated, nd values are displayed correctly. So apparently it is not a problem with BI. In that case, we are missing something in BPC itself. Can any of you identify what it could be? Awaiting answers and Thanking in Advance.
Sincere Regards,
Amitabha

Amitabha,
It's just a problem that a lot of people run into when they are getting used to BPC. Once you see it happen to 10 or 15 people, you can start to recognize it pretty quickly
There are not a lot of examples of this in the Netweaver documentation. I think there are more in the Microsoft docs. However, there is mention of it on this page in the Netweaver documentation: [http://help.sap.com/saphelp_bpc75_nw/helpdata/en/65/84d6596224477d80cc8a4392e4c114/frameset.htm]
Ethan

Modifying Existing Time Dimension

Hi All,
Presently I have a Time Dimension and a Fact table which has a FK to this Dimension. The Time Dim has a level upto hourly values.
Now it's in production and I need to change the Time Dim to take on minutes 'cause some reports need minutes.
1. So what is the best way to go about this?
2. Is it better just to add another extra field which has the required date, in the fact table?
3. How can the existing data be easily ported to the new Time Dim(if it has a minute-level)?
Thanks,
Justin.

I am wondering how you implemented the time dimension which only has a level up to hourly values. Do you mean the time dimension only has 24+1 = 25 rows? Usually the time dimension is separate from the date dimension and its lowest level values are minutes or seconds, depending on the business requirements. Therefore the time dimension should have 24X60 + 1 or 24X60X60 +1 rows.
The solution is depended on what you want.
My suggestion is as the follows:
1.     Create a new time dimension with the desired lowest level values (minutes or seconds).
2.     Create or modify the foreign key of the fact table to point the new created time dimension.
3.     Modify the ETL mappings.
4.     Option 1: If you want the new functionality available for the existing rows in the fact, you have to reload the fact no matter which approach you use.
Option 2: If you only want the new functionality available for the subsequent refresh load, you can modify the foreign-key values pointing to the old time dimension to the new time dimension, using the rule XX --> XX:00 or XX --> XX:00:00 (where XX is the hour number in the old dimension). In the subsequent refresh load, map the foreign-key values to the actual time.
Maybe other else can provide better solutions. IF so, please let me know.
Good luck!

Time Dimension _ Report on Current month and previous year.TOTAL

Hi,
My Time dimension is as under .
July2013, Aug2013 ,......Jan2014,,,. June2014 = 2014.TOTAL
My requirement is to report based on context view along with previous period total (.TOTAL) values.
For example : If i am using CV as : 2013.JUL my report should show 2013.JUL & 2013.TOTAL
If i am using CV as : 2014.JUN my report should show 2014.JUN & 2013.TOTAL
Can anyone provide some direction to build the above scenario
Regards
Krishna

Hi,
do you have the property YEAR in your time dimension filled out? If so, you could use EPMDIMENSIONOVERRIDE function together with an Excel cell.
Let me build an example:
Assuming your report has two columns, one for the current month and one for the total year. I would split this into two, one report per month, i.e. column. The first report will show the current period, the second the total. Somewhere in the header of your sheet use:
EPMDimensionOverride("001";"TIME";EPMMemberProperty(;EPMContextMember(;"TIME");"YEAR")&".TOTAL")
001 is the default ID of the second report.
BR,
Arnold

Composite key in Time dimension

Hi All,
I would like to know Time dimension with Composite key. I have a requirement where I want to store 2 Calendars in Time dimension table. for e.g :
for one calendar Weekstarts from SUN-SAT and for another it is from MON-TUE
DateKey Type WeekStart WeekEnd
20140101 1 Sun Sat
20140101 2 Mon Tue
..................etc
I have a measure group which is related to Time dimension (DateKey and Type used a Composite key). This implementation has no issues for additive measures but there are few issues with semi-additive measures (last non-empty,...).
Will composite Key have any effect on semi-additive measures ?
what if i use surrogate key instead of composite key.
Please suggest if the approach has any issue with Time intelligence. Advise if there is any better approach for the same.
Ram MSBI Developer

Hey.. Thanks!
I am clear about the concept about defining annotation based composite key. Also, I read in the documentation that I'll be needing to define as direct, aggregate or one-to-one. But, I am not able to define and run the same in the project mapping xml of toplink.
It would be great if you can share some sample code for defining the same. For e.g. in my mentioned example, there is TestEntity POJO having 'id' as the attribute which gets populated with the testEntityCode of the TestEntityKey POJO. Please suggest the same for the same:
<opm:primary-key>
<opm:attribute-name>id</opm:attribute-name>
<opm:field table="TEST_ENTITY_B" name="TEST_ENT_CODE" xsi:type="opm:column"/>
</opm:primary-key>
Thanks!

Seeking advice regarding Time Dimension - Correction and Customization

Dear all:
Situation
1. We have a measure called HTD, Half Year to Date, which aggregates 6 months worth of data. However, I just realized that the previous consultants set HTD at LEVEL = "Week". It works fine but I feel that this naming convention is confusing, and would like to rename HTD's LEVEL.
2. We have 4 more additional periods after period 12 for adjustment purpose. What is the good practice to have a year with 16 periods?
Data
Current LEVEL for Half Year to Date is named "Week". I would like to rename this to something like "HalfYr"
200x.01 - 12 are regular periods
200x.13 - 16 are additional periods
Question
1. If I go to SQL's back end and rename my LEVEL, and then update my Time dimension, is this going to pose a problem to my historical data?
2. I would like to include additional 4 more periods to sync with BW, but at the same time not confuse my BPC users in running reports at month of December. In other words, how do I integrate the 16 period time dimension design into the concept of "1 yr = 12 months (periods)"?

Tim:
Sorry for the late reply.
We are running BPC 5.1 SP3 and SQL 2003
Yes, MONTH, QUARTER, YEAR are used for LEVEL property, and the only irrelevance is HALF YEAR which has WEEK in LEVEL property.
I think perhaps a separate data source makes sense... Have you handled any case like this before and how did you manage the "additional" periods?
Thank you! Have a great day!
Sincerely,
Brian

Performance Point Filter Scorecard by Time Dimension (without Time Intelligence)

Hello,
I use Performance Point 2010 and want to build a Performance Point Dashboard with Scorecard. My requirement is to provide a List of Years as a Filter for a Scorecard.
In the Scorecard I have a KPI which I want filter by Time Dimension. I can do this when I use "Time Intelligence" and "Time Intelligence Connection". But I want to use the "Member Selection Filter" to filter the Scorecard
KPIs by Years (Selected from a List).
I created a "Member Selection Filter" with certain Time Dimension and put Filter to a Dashboard. In my KPI Mapping Source I added a "new Dimension Filter" and choosed the same Time Dimension as
in the "Member Selection Filter".
When I try to connect the "Member Selection Filter" to my Scorecard, I can only choose the "Curent Date Time". As I know "Current Date Time" have to be used when Time Intelligence Filter is in use.
How I have to connect the Scorecard with the "Member Selection Filter"?
Thank you very much

Hi ShebUK,
I don't think we can achieve this requirement on the front end, but you can discuss this issue at the following forum:
http://social.technet.microsoft.com/Forums/en-US/home?category=performancepointserver
I'm not familiar with PerformancePoint Services and not sure that we can implement linked dimension to achieve this. A linked dimension is one that exists in one Analysis Services database, but reused in another Analysis Services database of the same version
and compatibility level. For more information, please see:
Define Linked Dimensions: http://msdn.microsoft.com/en-us/library/ms175648.aspx
Hope this helps.
Regards,
Elvis Long
TechNet Community Support

Time dimensions

Hi OBIEE Guru's,
Could any one can explain the time dimension.
My requirement is :I have one DB table which contain the year column it is dimension table and another fact table contain the amount respective years,So I need to display records in a single row with current year ,year ago and 2-years ago.
Appreciate if any one can explain this with examples.
Thanks
B.kumar

Hi Man,
Take Year as prompt and assign presentation variable for that.
Now drag Amount Column and Create a column in the rpd with ago function which gives u one year previous data
then timestampadd(SQL_TSI_DAY,-2,current_date) use this for 2 years data
You will get it
Thanks
Subhash

Time Dimension: Naming requirement?

Similar Messages

Maybe you are looking for