PeriodsToDate and single Time dimension Attributes

Hi folks,
I just want to kindly confirm with you, if the PeriodsToDate function works only with user hierarchy?
That is because I am building some YTD calculation and I have two user hierarchies in the Time dimension, let´s say Markenting Calendar and Fiscal Calendar, but also I have single attributes that do not belong to any of these hierarchies like RetailDay.
Could I build a PeriodsToDate for these attributes?
I think the answer is no, because if a year is not related through the user hierarchy, how could the siblings be found.
Any comment will be appreciated.

Hello,
Basicly,PeriodsToDate function expects level expression for the first argument,i think it should be hierarcy level,since it should be hierarchy level,second argument should be hierarchy member as well,otherwise it throws an error.This is what i know.Hope
this helps.
Thanks,

Similar Messages

Time Dimension, i don´t bind the fact dimension and the time dimension

Well i don´t know why my fact table don´t bind with the time dimension, i create a time table in the data base and change the key to int32 for example year(date)*10000+month(date)*100+day(date), and create to similar in the fact table, and
this attributes binding, when i process the dimension all result without problems, after i process the cube and all result without problems, but when i try to deployment the browser, the measures in all years are equals, please help me

Hi franciscofelipe,
According to your description, you find the measures shows all same value for all years of time dimension. Right?
In this scenario, since your change the key of your time table into an integer, when pulling this dimension out in Browser, the measure will only regards those members as numeric value instead of date so that is will show an aggregate value. Even
all the members are displayed properly in your dimension. So please change the attribute type into appropriate date type.
If you have any question, please feel free to ask.
Regards,
Simon Hou
TechNet Community Support

How to Link two Facts with Different Time Granularity (Year, Quarter) to a Single Time Dimension

Hello All,
I have the below scenario where i have Two Facts Fact Quarterly and Fact Yearly but one Time Dimension which has Quarter grain.
So my question is how do i Establish relationship from Fact Yearly to Time Dimension??
Ex:

Hi naveej,
According to your description, you want to know how to build the relationship with time dimension and fact tables. Right?
Based on your screenshot, it's better to have only one fact table for sales and build the relationship with time dimension. To determine quarterly or yearly data only depends on how you slice the time dimension. However, I notice that the Revenue for year
is different from the aggregated Profit for quarters. If the Revenue and Profit are different measure, you need to have two fact tables. And you should build the relationship (Regular) between TimeDim and FactYearly on YYYY attribute.
Reference:
Defining a Fact Relationship
Best Regards,
Simon Hou
TechNet Community Support

OracleBI Spreadsheet Add-in Not Working With ROLAP TIME Dimension

Hello,
I've been trying to figure this bizarre behavior for a while now.
I have created a TIME dimension (based on a relational table) using OEM and defined the metadata etc. My hierarchy has 4 levels: day->month->quarter->year. I have end_date and time_span attributes defined for each level. I have defined a simple cube dimensioned by TIME and having only 1 numeric measure.
When I open BI Spreadsheet Add-in, I can see my cube measure and the dimension in the list of available entities. I add them to the list of selected entities and hit 'next'. On the next screen I arrange them to my liking and hit 'next' again. This is where the problem occurs. Or rather where nothing occurs. The add-in just gets stuck at this point and no matter what I do or click, it won't advance to the next step.
If I change the dimension type from time to normal, then everything works as expected (although, I cannot do time-series analysis).
If I create and enable an analytic workspace and use it in the add-in, then everything works as expected as well.
Any ideas what's wrong here? I kind of suspect the end_date and time_span attributes are involved somehow...
Thanks!
Dobo

The expected format for a relational time table would be something like the following:
CREATE TABLE "BIBDEMO"."BIBDEMO_TIME"
("TIME_STD_MONTH" VARCHAR2(30),
"TIME_STD_MONTH_LLABEL" VARCHAR2(60),
"TIME_STD_MONTH_SLABEL" VARCHAR2(30),
"TIME_STD_QUARTER" VARCHAR2(30),
"TIME_STD_QUARTER_LLABEL" VARCHAR2(60),
"TIME_STD_QUARTER_SLABEL" VARCHAR2(30),
"TIME_STD_YEAR" VARCHAR2(30),
"TIME_STD_YEAR_LLABEL" VARCHAR2(60),
"TIME_STD_YEAR_SLABEL" VARCHAR2(30),
"TIME_YTD_YEAR" VARCHAR2(30),
"TIME_YTD_YEAR_LLABEL" VARCHAR2(60),
"TIME_YTD_YEAR_SLABEL" VARCHAR2(30),
CONSTRAINT BIBDEMO_TIME_PK PRIMARY KEY("TIME_STD_MONTH")
ALTER TABLE "BIBDEMO"."BIBDEMO_TIME"
ADD ("TIME_STD_MONTH_END_DATE" DATE,
"TIME_STD_QUARTER_END_DATE" DATE,
"TIME_STD_YEAR_END_DATE" DATE,
"TIME_YTD_YEAR_END_DATE" DATE) ;
ALTER TABLE "BIBDEMO"."BIBDEMO_TIME"
ADD ("TIME_STD_MONTH_TIMESPAN" NUMBER,
"TIME_STD_QUARTER_TIMESPAN" NUMBER,
"TIME_STD_YEAR_TIMESPAN" NUMBER,
"TIME_YTD_YEAR_TIMESPAN" NUMBER) ;
and the metadata registration script should look something like this:
-- This script modifies the bibdemo_time lookup table and bibdemo TIME dimension. It adds a period end date attribute.
ALTER TABLE "BIBDEMO"."BIBDEMO_TIME"
ADD ("TIME_STD_MONTH_END_DATE" DATE,
"TIME_STD_QUARTER_END_DATE" DATE,
"TIME_STD_YEAR_END_DATE" DATE,
"TIME_YTD_YEAR_END_DATE" DATE) ;
ALTER TABLE "BIBDEMO"."BIBDEMO_TIME"
ADD ("TIME_STD_MONTH_TIMESPAN" NUMBER,
"TIME_STD_QUARTER_TIMESPAN" NUMBER,
"TIME_STD_YEAR_TIMESPAN" NUMBER,
"TIME_YTD_YEAR_TIMESPAN" NUMBER) ;
begin
dbms_output.put_line('Drop level attributes of TIME prior to recreation.');
cwm_olap_dim_attribute.remove_level_attribute('BIBDEMO', 'TIME', 'Long Description', 'L1', 'TIME_STD_YEAR_LLABEL');
cwm_olap_dim_attribute.remove_level_attribute('BIBDEMO', 'TIME', 'Short Description', 'L1', 'TIME_STD_YEAR_SLABEL');
cwm_olap_dim_attribute.remove_level_attribute('BIBDEMO', 'TIME', 'Long Description', 'L2', 'TIME_STD_QUARTER_LLABEL');
cwm_olap_dim_attribute.remove_level_attribute('BIBDEMO', 'TIME', 'Short Description', 'L2', 'TIME_STD_QUARTER_SLABEL');
cwm_olap_dim_attribute.remove_level_attribute('BIBDEMO', 'TIME', 'Long Description', 'L3', 'TIME_STD_MONTH_LLABEL');
cwm_olap_dim_attribute.remove_level_attribute('BIBDEMO', 'TIME', 'Short Description', 'L3', 'TIME_STD_MONTH_SLABEL');
cwm_olap_dim_attribute.remove_level_attribute('BIBDEMO', 'TIME', 'Long Description', 'L4', 'TIME_YTD_YEAR_LLABEL');
cwm_olap_dim_attribute.remove_level_attribute('BIBDEMO', 'TIME', 'Short Description', 'L4', 'TIME_YTD_YEAR_SLABEL');
commit;
exception
when others then
dbms_output.put_line('ERROR: unexpected exception during seeding');
cwm_utility.dump_error;
rollback;
raise;
end;
ALTER DIMENSION BIBDEMO.TIME
DROP ATTRIBUTE L1
DROP ATTRIBUTE L2
DROP ATTRIBUTE L3
DROP ATTRIBUTE L4;
ALTER DIMENSION BIBDEMO.TIME
ADD ATTRIBUTE L1 DETERMINES
(BIBDEMO_TIME.TIME_STD_YEAR_LLABEL,
BIBDEMO_TIME.TIME_STD_YEAR_SLABEL,
BIBDEMO_TIME.TIME_STD_YEAR_END_DATE,
BIBDEMO_TIME.TIME_STD_YEAR_TIMESPAN)
ADD ATTRIBUTE L2 DETERMINES
(BIBDEMO_TIME.TIME_STD_QUARTER_LLABEL,
BIBDEMO_TIME.TIME_STD_QUARTER_SLABEL,
BIBDEMO_TIME.TIME_STD_QUARTER_END_DATE,
BIBDEMO_TIME.TIME_STD_QUARTER_TIMESPAN)
ADD ATTRIBUTE L3 DETERMINES
(BIBDEMO_TIME.TIME_STD_MONTH_LLABEL,
BIBDEMO_TIME.TIME_STD_MONTH_SLABEL,
BIBDEMO_TIME.TIME_STD_MONTH_END_DATE,
BIBDEMO_TIME.TIME_STD_MONTH_TIMESPAN)
ADD ATTRIBUTE L4 DETERMINES
(BIBDEMO_TIME.TIME_YTD_YEAR_LLABEL,
BIBDEMO_TIME.TIME_YTD_YEAR_SLABEL,
BIBDEMO_TIME.TIME_YTD_YEAR_END_DATE,
BIBDEMO_TIME.TIME_YTD_YEAR_TIMESPAN);
declare
timespan_desc_id number;
enddate_desc_id number;
TIME_DIM_ATTRIB_TYPE constant varchar2(30) := 'DIMENSION ATTRIBUTE';
TIME_ATTRIBUTE_TYPE constant varchar2(30) := 'LEVEL ATTRIBUTE';
begin
dbms_output.put_line('Create end_date and timespan attributes of TIME for BIBDEMO schema');
begin
cwm_olap_level_attribute.set_name('BIBDEMO', 'TIME', 'L1', 'TIME_STD_YEAR_END_DATE', 'TIME_STD_YEAR_END_DATE');
cwm_olap_level_attribute.set_name('BIBDEMO', 'TIME', 'L2', 'TIME_STD_QUARTER_END_DATE', 'TIME_STD_QUARTER_END_DATE');
cwm_olap_level_attribute.set_name('BIBDEMO', 'TIME', 'L3', 'TIME_STD_MONTH_END_DATE', 'TIME_STD_MONTH_END_DATE');
cwm_olap_level_attribute.set_name('BIBDEMO', 'TIME', 'L4', 'TIME_YTD_YEAR_END_DATE', 'TIME_YTD_YEAR_END_DATE');
cwm_olap_level_attribute.set_name('BIBDEMO', 'TIME', 'L1', 'TIME_STD_YEAR_TIMESPAN', 'TIME_STD_YEAR_TIMESPAN');
cwm_olap_level_attribute.set_name('BIBDEMO', 'TIME', 'L2', 'TIME_STD_QUARTER_TIMESPAN', 'TIME_STD_QUARTER_TIMESPAN');
cwm_olap_level_attribute.set_name('BIBDEMO', 'TIME', 'L3', 'TIME_STD_MONTH_TIMESPAN', 'TIME_STD_MONTH_TIMESPAN');
cwm_olap_level_attribute.set_name('BIBDEMO', 'TIME', 'L4', 'TIME_YTD_YEAR_TIMESPAN', 'TIME_YTD_YEAR_TIMESPAN');
cwm_olap_dim_attribute.create_dimension_attribute('BIBDEMO', 'TIME', 'End_Date', 'End_Date', 'End Date of time period');
cwm_olap_dim_attribute.create_dimension_attribute('BIBDEMO', 'TIME', 'Time_Span', 'Time_Span', 'Number of days in time period');
cwm_olap_dim_attribute.add_level_attribute('BIBDEMO', 'TIME', 'Long Description', 'L1', 'TIME_STD_YEAR_LLABEL');
cwm_olap_dim_attribute.add_level_attribute('BIBDEMO', 'TIME', 'Short Description', 'L1', 'TIME_STD_YEAR_SLABEL');
cwm_olap_dim_attribute.add_level_attribute('BIBDEMO', 'TIME', 'End_Date', 'L1', 'TIME_STD_YEAR_END_DATE');
cwm_olap_dim_attribute.add_level_attribute('BIBDEMO', 'TIME', 'Time_Span', 'L1', 'TIME_STD_YEAR_TIMESPAN');
cwm_olap_dim_attribute.add_level_attribute('BIBDEMO', 'TIME', 'Long Description', 'L2', 'TIME_STD_QUARTER_LLABEL');
cwm_olap_dim_attribute.add_level_attribute('BIBDEMO', 'TIME', 'Short Description', 'L2', 'TIME_STD_QUARTER_SLABEL');
cwm_olap_dim_attribute.add_level_attribute('BIBDEMO', 'TIME', 'End_Date', 'L2', 'TIME_STD_QUARTER_END_DATE');
cwm_olap_dim_attribute.add_level_attribute('BIBDEMO', 'TIME', 'Time_Span', 'L2', 'TIME_STD_QUARTER_TIMESPAN');
cwm_olap_dim_attribute.add_level_attribute('BIBDEMO', 'TIME', 'Long Description', 'L3', 'TIME_STD_MONTH_LLABEL');
cwm_olap_dim_attribute.add_level_attribute('BIBDEMO', 'TIME', 'Short Description', 'L3', 'TIME_STD_MONTH_SLABEL');
cwm_olap_dim_attribute.add_level_attribute('BIBDEMO', 'TIME', 'End_Date', 'L3', 'TIME_STD_MONTH_END_DATE');
cwm_olap_dim_attribute.add_level_attribute('BIBDEMO', 'TIME', 'Time_Span', 'L3', 'TIME_STD_MONTH_TIMESPAN');
cwm_olap_dim_attribute.add_level_attribute('BIBDEMO', 'TIME', 'Long Description', 'L4', 'TIME_YTD_YEAR_LLABEL');
cwm_olap_dim_attribute.add_level_attribute('BIBDEMO', 'TIME', 'Short Description', 'L4', 'TIME_YTD_YEAR_SLABEL');
cwm_olap_dim_attribute.add_level_attribute('BIBDEMO', 'TIME', 'End_Date', 'L4', 'TIME_YTD_YEAR_END_DATE');
cwm_olap_dim_attribute.add_level_attribute('BIBDEMO', 'TIME', 'Time_Span', 'L4', 'TIME_YTD_YEAR_TIMESPAN');
begin
SELECT descriptor_id INTO enddate_desc_id
FROM all_olap_descriptors
WHERE descriptor_value = 'End Date'
AND descriptor_type = 'Time Dimension Attribute Type';
begin
dbms_output.put_line('Classify entity descriptor use end date for TIME');
begin
cwm_classify.add_entity_descriptor_use(enddate_desc_id, TIME_DIM_ATTRIB_TYPE, 'BIBDEMO', 'TIME', 'End_Date');
exception
when cwm_exceptions.element_already_exists
then null;
end;
begin
cwm_classify.add_entity_descriptor_use(enddate_desc_id, TIME_ATTRIBUTE_TYPE, 'BIBDEMO', 'TIME', 'L3', 'TIME_STD_MONTH_END_DATE');
exception
when cwm_exceptions.element_already_exists
then null;
end;
begin
cwm_classify.add_entity_descriptor_use(enddate_desc_id, TIME_ATTRIBUTE_TYPE, 'BIBDEMO', 'TIME', 'L2', 'TIME_STD_QUARTER_END_DATE');
exception
when cwm_exceptions.element_already_exists
then null;
end;
begin
cwm_classify.add_entity_descriptor_use(enddate_desc_id, TIME_ATTRIBUTE_TYPE, 'BIBDEMO', 'TIME', 'L1', 'TIME_STD_YEAR_END_DATE');
exception
when cwm_exceptions.element_already_exists
then null;
end;
begin
cwm_classify.add_entity_descriptor_use(enddate_desc_id, TIME_ATTRIBUTE_TYPE, 'BIBDEMO', 'TIME', 'L4', 'TIME_YTD_YEAR_END_DATE');
exception
when cwm_exceptions.element_already_exists
then null;
end;
end;
end;
begin
SELECT descriptor_id INTO timespan_desc_id
FROM all_olap_descriptors
WHERE descriptor_value = 'Time Span'
AND descriptor_type = 'Time Dimension Attribute Type';
begin
dbms_output.put_line('Classify entity descriptor use time span for TIME');
begin
cwm_classify.add_entity_descriptor_use(timespan_desc_id, TIME_DIM_ATTRIB_TYPE, 'BIBDEMO', 'TIME', 'Time_Span');
exception
when cwm_exceptions.element_already_exists
then null;
end;
begin
cwm_classify.add_entity_descriptor_use(timespan_desc_id, TIME_ATTRIBUTE_TYPE, 'BIBDEMO', 'TIME', 'L3', 'TIME_STD_MONTH_TIMESPAN');
exception
when cwm_exceptions.element_already_exists
then null;
end;
begin
cwm_classify.add_entity_descriptor_use(timespan_desc_id, TIME_ATTRIBUTE_TYPE, 'BIBDEMO', 'TIME', 'L2', 'TIME_STD_QUARTER_TIMESPAN');
exception
when cwm_exceptions.element_already_exists
then null;
end;
begin
cwm_classify.add_entity_descriptor_use(timespan_desc_id, TIME_ATTRIBUTE_TYPE, 'BIBDEMO', 'TIME', 'L1', 'TIME_STD_YEAR_TIMESPAN');
exception
when cwm_exceptions.element_already_exists
then null;
end;
begin
cwm_classify.add_entity_descriptor_use(timespan_desc_id, TIME_ATTRIBUTE_TYPE, 'BIBDEMO', 'TIME', 'L4', 'TIME_YTD_YEAR_TIMESPAN');
exception
when cwm_exceptions.element_already_exists
then null;
end;
end;
end;
end;
commit;
exception
when others then
dbms_output.put_line('ERROR: unexpected exception during seeding');
cwm_utility.dump_error;
rollback;
raise;
end;
--UPDATE "BIBDEMO"."BIBDEMO_TIME" SET TIME_STD_MONTH_END_DATE = LAST_DAY(TO_DATE( time_std_month , 'monyy'));
--UPDATE "BIBDEMO"."BIBDEMO_TIME" t SET TIME_STD_QUARTER_END_DATE = (select max(t1.time_std_month_end_date) from bibdemo_time t1 where t1.time_std_quarter = t.time_std_quarter group by t1.time_std_quarter) ;
--UPDATE "BIBDEMO"."BIBDEMO_TIME" t SET TIME_STD_YEAR_END_DATE = (select max(t1.time_std_month_end_date) from bibdemo_time t1 where t1.time_std_year = t.time_std_year group by t1.time_std_year) ;
update bibdemo_time set time_std_month_end_date = to_date('31-JAN-2000', 'dd-mon-yyyy') where time_std_month = 'JAN00';
update bibdemo_time set time_std_month_end_date = to_date('29-FEB-2000', 'dd-mon-yyyy') where time_std_month = 'FEB00';
update bibdemo_time set time_std_month_end_date = to_date('31-MAR-2000', 'dd-mon-yyyy') where time_std_month = 'MAR00';
update bibdemo_time set time_std_month_end_date = to_date('30-APR-2000', 'dd-mon-yyyy') where time_std_month = 'APR00';
update bibdemo_time set time_std_month_end_date = to_date('31-MAY-2000', 'dd-mon-yyyy') where time_std_month = 'MAY00';
update bibdemo_time set time_std_month_end_date = to_date('30-JUN-2000', 'dd-mon-yyyy') where time_std_month = 'JUN00';
update bibdemo_time set time_std_month_end_date = to_date('31-JUL-2000', 'dd-mon-yyyy') where time_std_month = 'JUL00';
update bibdemo_time set time_std_month_end_date = to_date('31-AUG-2000', 'dd-mon-yyyy') where time_std_month = 'AUG00';
update bibdemo_time set time_std_month_end_date = to_date('30-SEP-2000', 'dd-mon-yyyy') where time_std_month = 'SEP00';
update bibdemo_time set time_std_month_end_date = to_date('31-OCT-2000', 'dd-mon-yyyy') where time_std_month = 'OCT00';
update bibdemo_time set time_std_month_end_date = to_date('30-NOV-2000', 'dd-mon-yyyy') where time_std_month = 'NOV00';
update bibdemo_time set time_std_month_end_date = to_date('31-DEC-2000', 'dd-mon-yyyy') where time_std_month = 'DEC00';
update bibdemo_time set time_std_month_end_date = to_date('31-JAN-2001', 'dd-mon-yyyy') where time_std_month = 'JAN01';
update bibdemo_time set time_std_month_end_date = to_date('28-FEB-2001', 'dd-mon-yyyy') where time_std_month = 'FEB01';
update bibdemo_time set time_std_month_end_date = to_date('31-MAR-2001', 'dd-mon-yyyy') where time_std_month = 'MAR01';
update bibdemo_time set time_std_month_end_date = to_date('30-APR-2001', 'dd-mon-yyyy') where time_std_month = 'APR01';
update bibdemo_time set time_std_month_end_date = to_date('31-MAY-2001', 'dd-mon-yyyy') where time_std_month = 'MAY01';
update bibdemo_time set time_std_quarter_end_date = to_date('30-JUN-2000', 'dd-mon-yyyy') where time_std_quarter = 'Q2.00';
update bibdemo_time set time_std_quarter_end_date = to_date('30-SEP-2000', 'dd-mon-yyyy') where time_std_quarter = 'Q3.00';
update bibdemo_time set time_std_quarter_end_date = to_date('31-DEC-2000', 'dd-mon-yyyy') where time_std_quarter = 'Q4.00';
update bibdemo_time set time_std_quarter_end_date = to_date('31-MAR-2000', 'dd-mon-yyyy') where time_std_quarter = 'Q1.00';
update bibdemo_time set time_std_quarter_end_date = to_date('31-MAR-2001', 'dd-mon-yyyy') where time_std_quarter = 'Q1.01';
update bibdemo_time set time_std_quarter_end_date = to_date('31-MAY-2001', 'dd-mon-yyyy') where time_std_quarter = 'Q2.01';
update bibdemo_time set time_std_year_end_date = to_date('31-DEC-2000', 'dd-mon-yyyy') where time_std_year = '2000';
update bibdemo_time set time_std_year_end_date = to_date('31-MAY-2001', 'dd-mon-yyyy') where time_std_year = '2001';
update bibdemo_time set time_ytd_year_end_date = to_date('31-DEC-2000', 'dd-mon-yyyy') where time_ytd_year = '2000';
update bibdemo_time set time_ytd_year_end_date = to_date('31-MAY-2001', 'dd-mon-yyyy') where time_ytd_year = '2001';
update "BIBDEMO"."BIBDEMO_TIME" set "TIME_STD_MONTH_TIMESPAN" = 31 where "TIME_STD_MONTH" = 'JAN00';
update "BIBDEMO"."BIBDEMO_TIME" set "TIME_STD_MONTH_TIMESPAN" = 29 where "TIME_STD_MONTH" = 'FEB00';
update "BIBDEMO"."BIBDEMO_TIME" set "TIME_STD_MONTH_TIMESPAN" = 31 where "TIME_STD_MONTH" = 'MAR00';
update "BIBDEMO"."BIBDEMO_TIME" set "TIME_STD_MONTH_TIMESPAN" = 30 where "TIME_STD_MONTH" = 'APR00';
update "BIBDEMO"."BIBDEMO_TIME" set "TIME_STD_MONTH_TIMESPAN" = 31 where "TIME_STD_MONTH" = 'MAY00';
update "BIBDEMO"."BIBDEMO_TIME" set "TIME_STD_MONTH_TIMESPAN" = 30 where "TIME_STD_MONTH" = 'JUN00';
update "BIBDEMO"."BIBDEMO_TIME" set "TIME_STD_MONTH_TIMESPAN" = 31 where "TIME_STD_MONTH" = 'JUL00';
update "BIBDEMO"."BIBDEMO_TIME" set "TIME_STD_MONTH_TIMESPAN" = 31 where "TIME_STD_MONTH" = 'AUG00';
update "BIBDEMO"."BIBDEMO_TIME" set "TIME_STD_MONTH_TIMESPAN" = 30 where "TIME_STD_MONTH" = 'SEP00';
update "BIBDEMO"."BIBDEMO_TIME" set "TIME_STD_MONTH_TIMESPAN" = 31 where "TIME_STD_MONTH" = 'OCT00';
update "BIBDEMO"."BIBDEMO_TIME" set "TIME_STD_MONTH_TIMESPAN" = 30 where "TIME_STD_MONTH" = 'NOV00';
update "BIBDEMO"."BIBDEMO_TIME" set "TIME_STD_MONTH_TIMESPAN" = 31 where "TIME_STD_MONTH" = 'DEC00';
update "BIBDEMO"."BIBDEMO_TIME" set "TIME_STD_MONTH_TIMESPAN" = 31 where "TIME_STD_MONTH" = 'JAN01';
update "BIBDEMO"."BIBDEMO_TIME" set "TIME_STD_MONTH_TIMESPAN" = 28 where "TIME_STD_MONTH" = 'FEB01';
update "BIBDEMO"."BIBDEMO_TIME" set "TIME_STD_MONTH_TIMESPAN" = 31 where "TIME_STD_MONTH" = 'MAR01';
update "BIBDEMO"."BIBDEMO_TIME" set "TIME_STD_MONTH_TIMESPAN" = 30 where "TIME_STD_MONTH" = 'APR01';
update "BIBDEMO"."BIBDEMO_TIME" set "TIME_STD_MONTH_TIMESPAN" = 31 where "TIME_STD_MONTH" = 'MAY01';
update "BIBDEMO"."BIBDEMO_TIME" t
set "TIME_STD_QUARTER_TIMESPAN" = (
select sum(t1.time_std_month_timespan)
from bibdemo_time t1
where t."TIME_STD_QUARTER" = t1.time_std_quarter
group by t1.time_std_quarter
update "BIBDEMO"."BIBDEMO_TIME" t
set "TIME_STD_YEAR_TIMESPAN" = (
select sum(t1.time_std_month_timespan)
from bibdemo_time t1
where t."TIME_STD_YEAR" = t1.time_std_year
group by t1.time_std_year
update "BIBDEMO"."BIBDEMO_TIME" t
set "TIME_YTD_YEAR_TIMESPAN" = (
select sum(t1.time_std_month_timespan)
from bibdemo_time t1
where t."TIME_YTD_YEAR" = t1.time_ytd_year
group by t1.time_ytd_year
commit;
quit;
Hope this helps
Business Intelligence Beans Product Management Team
Oracle Corporation

Date time dimension solution

I'd like to have a date and time dimension where i can drill down to hours and quarters. What i don't want is one large dimension ( too many rows :-). Getting a date and a time dimension linked from the fact table is another solution, but i don't know if i can drill down with this solution.
My solution is creating a datetime dimension that is clustered with a date dimension and a time key and time table. What are the downgrades when i implement this? Probably creating a view wherein i join the cluster? And can i drill and create a single dimension using this implementation?

I suspect that your chief problem is a forum mismatch
?

Distinct count of role-played dimension attribute

Needed distinct count of AccountGroup attribute of AccountB dimension which is a role played dimension of Account.
Added measure distinct count of the dimension attribute (AccountGroup). In dimension usage added the main fact table as intermediate for other dimensions with many2many relationships.
The two role played Account dimensions must be related to the new AccountFact table with fact relationship.
But then how will I be able to count distinct attribute of
certain Account dimension (out of the two role played dimensions)???
Namnami

Thanks for the links, they are useful. But still they do not explain how to manage a distinct count of
certain role played dimension attribute.
I gave up on this and added that dimension attribute to the fact table so now I do a regular distinct count on a cube fact measure.
Thanks
Namnami

Macro help on selectin crieteria with time dimension to the user

Hi Experts,
I have some Macro requirement in my input schedule.
We are preparing Head Count Planning report and the time dimension is selected for next five years and category is Budget.
Now user wants to select only on year wise and then the report needs to be refreshed with the selected year (Example selected budget year is 2015).
I have heard that it can be achieved through Macro. Can some one please provide a piece of Macro sample so that I can make the changes according to my requirement.
Please see the below report format (Time Dimension details).

Hi Satish,
What macro are you talking about?
If it's symmetric report then you use context to select YYYY.TOTAL and expand to base members.
If it's asymmetric report then use: Static report in BPC NW 10
"Now user wants to select only on year wise and then the report needs to be refreshed with the selected year (Example selected budget year is 2015)."
If you want to have report for 5 years and the user select first year with context - then Static report in BPC NW 10
You have to generate TIME members by Excel formula:
Example:
in A10 you have formula =EPMContextMember("ConnName";"TIME"), resulting in 2015.01
Then in column axis you can use LEFT($A$10,4)&".02", LEFT($A$10,4)&".03" etc. for the first year
LEFT($A$10,4)+1&".02",... for the second year
Vadim

Time dimension population

Hi
I am taking "clndr" as source and populate time dimension table.Time dimension table ( granularity is an hourly basis) will be populated with date with 24 intervals and based on the cln_dt whether it falls in weekened or holiday ,If falls in weekened or holiday , populate 'Y' Else 'N' .Please see the below example
clndr(source table)
cln_dt cldr_day busday cldr_yr
1/05/2006 monday y 2005
2/5/2006 Tuesday y 2005
Expected data
==========
Time_dim(Target table)
Time_dt interval holidy ind
1/05/2006 0 N
1/05/2006 1 N
1/05/2006 2 N
1/05/2006 3 N
1/05/2006 23 N
2/5/2006 0 N
2/5/2006 1 N
2/5/2006 23 N
Thanksinadvance
MR

Try this, Modified Dnikiforov's solution:
SQL> ed
Wrote file afiedt.buf
1 select date#, hour, decode(busday,'Fri','Y','Sat','Y','Sun','Y','N') flag
2 from ( select to_date('06-MAY-06') date#, to_char(to_date(
3 '06-MAY-06'),'Dy') busday from dual
4 union all
5 select to_date('07-MAY-06') date#, to_char(to_date(
6 '07-MAY-06'),'Dy') from dual
7 union all
8 select to_date('08-MAY-06') date#, to_char(to_date(
9 '08-MAY-06'),'Dy') from dual ) calendar,
10 (select rownum-1 hour from dict where rownum <=24) hours
11* order by 1,2
SQL> /
DATE#        HOUR F
06-MAY-06       0 Y
06-MAY-06       1 Y
06-MAY-06       2 Y
06-MAY-06       3 Y
06-MAY-06       4 Y
06-MAY-06       5 Y
06-MAY-06       6 Y
06-MAY-06       7 Y
06-MAY-06       8 Y
06-MAY-06       9 Y
06-MAY-06      10 Y
06-MAY-06      11 Y
06-MAY-06      12 Y
06-MAY-06      13 Y
06-MAY-06      14 Y
06-MAY-06      15 Y
06-MAY-06      16 Y
06-MAY-06      17 Y
06-MAY-06      18 Y
06-MAY-06      19 Y
06-MAY-06      20 Y
06-MAY-06      21 Y
06-MAY-06      22 Y
06-MAY-06      23 Y
07-MAY-06       0 Y
07-MAY-06       1 Y
07-MAY-06       2 Y
07-MAY-06       3 Y
07-MAY-06       4 Y
07-MAY-06       5 Y
07-MAY-06       6 Y
07-MAY-06       7 Y
07-MAY-06       8 Y
07-MAY-06       9 Y
07-MAY-06      10 Y
07-MAY-06      11 Y
07-MAY-06      12 Y
07-MAY-06      13 Y
07-MAY-06      14 Y
07-MAY-06      15 Y
07-MAY-06      16 Y
07-MAY-06      17 Y
07-MAY-06      18 Y
07-MAY-06      19 Y
07-MAY-06      20 Y
07-MAY-06      21 Y
07-MAY-06      22 Y
07-MAY-06      23 Y
08-MAY-06       0 N
08-MAY-06       1 N
08-MAY-06       2 N
08-MAY-06       3 N
08-MAY-06       4 N
08-MAY-06       5 N
08-MAY-06       6 N
08-MAY-06       7 N
08-MAY-06       8 N
08-MAY-06       9 N
08-MAY-06      10 N
08-MAY-06      11 N
08-MAY-06      12 N
08-MAY-06      13 N
08-MAY-06      14 N
08-MAY-06      15 N
08-MAY-06      16 N
08-MAY-06      17 N
08-MAY-06      18 N
08-MAY-06      19 N
08-MAY-06      20 N
08-MAY-06      21 N
08-MAY-06      22 N
08-MAY-06      23 N
72 rows selected.

Dimension Attribute Write Back

Is it possible to write-back and update a dimension attribute. If so, could someone please post an example doing this.
Thanks!

I assume that your question is about Oracle-OLAP dimension attribute (and not Essbase).
You will have to come up with a custom front-end (web or windows) where you will enter (or change) the attribute value. Then behind the scenes, you will call DBMS_CUBE.BUILD procedure to update the attribute value for that dimension member.
Here is an example:
Dimension = 'ACC', Hierarchy = 'ACCHIER', Dimension Member = 'CM1' and we want to update an attribute value called "LONG_DESCRIPTION" for this member 'CM1'.
begin
dbms_cube.build(q'! "ACC" USING (
SET "ACC"."LONG_DESCRIPTION"["ACC" = 'CM1'] = CAST('Custom Member 1' AS VARCHAR2),
MERGE INTO HIERARCHIES ("ACC"."ACCHIER") VALUES ('CM1', 'ALL_ACC', NULL),
COMPILE)!');
end;

I created a form with Single Choice fields, 4 days with times listed. But, I want the user to only be able to choose one time, and the time chosen to be unavailable for other users. How do I do this?

I created a form with Single Choice fields, 4 days with times listed. But, I want the user to only be able to choose one time, and the time chosen to be unavailable for other users. How do I do this? I have 4 blocks of Single Choice fields in order for the summary page to give me each day in the final report. But, I need the user to be able to make a selection of any day and time and that apointment to no longer be available to future users when they log in. Plus, when the user clicks on the time, they are unable to change their mind and choose another time. Here's the link if you want to see what I'm talking about: 2015-2016 Workload Apportionment Review

I'm afraid not. It's not rocket science but you need to do some coding.
You'll need to find a script (php) and save it to your local site folder. Then reference the script in your form's action attribute like so.
<form action="path/form-to-email-script.php" >
The input fields in your HTML form need to exactly match the script variables.
I'm assuming you're hosted on a Linux server which uses PHP code. Linux servers are also case sensitive, so upper case names are not the same as lower case names. It's usually best to use all lower case names in your form and script to avoid confusion.
Related Links:
Formm@ailer PHP from DB Masters
http://dbmasters.net/index.php?id=4
Tectite
http://www.tectite.com/formmailpage.php
If this is all a bit beyond your skill set, look at:
Wufoo.com (on-line form service)
http://wufoo.com/
Nancy O.

TIME dimension processing fails saying "..attribute key cannot be found.." in EPM 10

After upgrading from version 7.5 to EPM 10, when we ran a ‘Full Process’ on the TIME dimension, it ran into an error saying “Errors in the OLAP storage engine: The attribute key cannot be found when processing: Table: 'dbo_tblFactCapEx', Column: 'TIMEID', Value: '20090013'. The attribute is 'Time_TIMEID'. (1/13/2015 2:41:02 PM)”.
Full error message is attached herewith – ‘Time Dimension Error.txt’
After researching, we did discover that MONTHNUM needed to be converted to BASE_PERIOD. Re-processed which produced the same error.
Prior to migration to version 7.5, we ran a full process on TIME dimension there. It completed successfully, confirming the issue is only with version 10.
Confirmed we could see the TIMEID value of 20090013 in the following places:
Time Dimension in the appropriate TIMEID attribute column.
Confirmed mbrTIME table had base member ID with TIMEID attribute filled out correctly.
Data in tblFactFINANCE could be pulled using that TIMEID
We truncated all the records in all the fact tables associated to this TIME dimension.
Eventually, when none of the tables had any records, the TIME dimension then processed successfully.
We this began to suspect the issue may not really be related to bad records.
We conducted one more test to confirm this.
Using an input form in EPM 10, we manually entered data in one of the models (at this point none of the fact tables have any records)
Ran Full Optimize on that model with Compress Database and Index Defragmentation checked – This step failed with the error attached in ‘MatrixRateFullOptimize.txt’
Ran Full process on Time Dimension – Failed indicating issue with TimeID 2012001 (that’s my manual entry). Attached error report ‘TimeDim Error MatrixRate.txt’
At this point, the table only contains the manually entered records (no suspected bad records)
We then suspected there could have been an issue with the upgrade process.
So we reprocessed all the dimension and optimized all the models in version 7.5, made a new backup and restored it to version 10.
The issue still persisted!
At this point, we have tried all the possibilities we could think of. Each time the fact table is populated with records, the TIME dimension process fails indicating ‘the attribute key’ cannot be found.
There is probably something in the OLAP partition that is not able to link the dimension attributes to the cubes.
Additional Information:
Please find attached the existing Time Dimension – TimeDimensionMembers.xlxs
Version of Excel used: Excel 2007, SP3 MSO (12.0.6683.5000)
System Specs: Please see screenshot below.

Thank you all for responding! This issue is resolved.
Here’s what the issue was:
The time structure is TOTAL >> Years >> Quarters >> Months (e.g. T.ALL >> 2012.TOTAL >> 2012.Q1 >> 2012.P01)
As shown in the screenshot below, the LEVEL for ‘T.ALL’ member was set to YEAR, which is incorrect (we can’t have Year rolling up to a Year)
We changed the LEVEL to ‘TOTAL’ and this fixed the issue!!
If only it gave a better error message than the “..attribute key not found” message

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

TIME_DSO_1 attribute in Time Dimension

Hi,
We are using Oracle Analytic Workspace Manager version 10.2.0.3.0A for creating a cube.
We have defined a dimension as "Time" dimension and have also specified the dimension type as "Time".
This dimension has the levels: Year, Quarter, Month, Week and Day. These levels are for the one and only hierarchy of the Time dimension.
The attributes of the dimension (applicable to all the levels) are: END_DATE, LONG_DESCRIPTION, SHORT_DESCRIPTION, and TIME_SPAN.
In this structure, we are having a strange observation : During the process of defining this TIME dimension, there were some problems with the machine (it got hanged) and so we had to exit (kill) the AWM and come in again. When we logged in to AWM again, we could see a new attribute called TIME_DSO_1 defined within the Time dimension by itself.
Can anyone let us know what is this attribute all about ? And can we go ahead and just delete this from our dimension structure without creating problems for ourselves?
Many thanks in advance for the kind inputs of the forum.
Regards,
Piyush

Hi,
I can't say that I really understand how your data shows up, but I do see an error in your hierarchy.
What you should do is split it up into two hierarchies.
Year-> Quarter-> Month-> Day
and
Year-> Week-> Day
And here is the reason:
A day can easily have a week as a parent and month. But week cannot. Since a month can end on any given day in a week, that means that a week can have two parents. If I take the next week as an example. Mon, tue, wed, thu and fri would belong to the august month, while the rest of the week would belong to september. But the entire week would still be week 35. And its the same issue with quarter. Months can be added into a quarter, but weeks can not.
Now, I'm not sure if this would solve all your problems, but there might be a few other things you might check out and thats what ID's you populate your member fields with.
say that you have used the month numbers (or at least the same id for every january and so on)to populate your months. If that is the case things will also behave extremely weird and slow. What you need to do is to create unique IDs for every month (and any other level) so that you are sure that january 2007 don't have any child records that really should belong to january 2006.
As a general rule, the member field needs to contain a completely unique value across on from all levels. The "generate surrogate key" functionality helps you a bit along the way as it adds the name of your level in front of the value that you load. If the values you load doesn't have unique values within the level it won't help you any.
Hope this can help you some more... ;)
regards Ragnar

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

How to create a working day/holiday attribute in Time Dimension with OWB ?

Hello everybody,
I am trying with no success to create a Time Dimension (with the wizard it would be easier...) with a working day or holiday attribute (0 or 1) to be able to calculate measures only on working time !!! I am totally sure it's possible, obviously, but I found nothing on forums... Could you help me ??
I use OWB 11g, I need all fiscal year/quarter/month/week and all calendar year/quarter/month/week attributes so without any wizard it would be quite impossible... thank you for your help !
NB: of course I know how to define if a day is a working one or not, but I currently can't add any columns in Time dim created with wizard...
Francois
Edited by: [email protected] on Jun 15, 2009 8:24 AM

Hi,
First of all, thanks everyone for your help.
I did several tests this morning.
First of all, i've tried with time_from = 000000 and time_to = 235959 (23:59:59 CET) and the activity has been created with Time From = 04:00:00 and Time To = 03:59:59
Strange no ??
I've also tried with 230000 for time from and time to but the activity has been created with Time From = 03:00:00 and Time to = 03:00:00
I cannot understand the logic behind....
Thanks,
Johnny Baillargeaux

PeriodsToDate and single Time dimension Attributes

Similar Messages

Maybe you are looking for