Inconsistent data in Year Ago Column

645922

Hi All,

Thanks in Advance

I have developed a OBIEE report with year ago column, however data in year ago column is not consistent.

Report output is as follows

Year -- Booked Amt -- Year Ago Booked Amt
2004 -- 0 -- 0
2008 -- 0 --
2009 -- 3496 -- 0
2010 -- 0 -- 0


Please let me know what went wrong!

Regards,
Arjun SM

user12116294

Hi,

follow the below link it might be helpful
http://gerardnico.com/wiki/dat/obiee/bi_server/design/dimension/obiee_time_series_functions

let us know if you still have some issue

user12116294

Plesae check the below link also

http://gerardnico.com/wiki/dat/obiee/bi_server/design/dimension/time_dimension_parameters_for_ago_and_td_functions

645922

Thanks for you reply

I followed the same process, data is not consistent in only few rows in other rows data is displayed properly only

For year 2008 and 2010 data for year ago column is not correct, however for remaining rows data is displayed correctly.


Thanks,
Arjun SM

645922

Thank in advance

did anyone face this type of problem!


Thanks,
Arjun SM

Edited by: SMA on Oct 29, 2009 4:28 PM

645922

Please help

gerardnico

Check and recheck your chronological key :
http://gerardnico.com/wiki/dat/obiee/bi_server/design/dimension/time_dimension_parameters_for_ago_and_td_functions#chronological_key_configuration

It must be a real real chronological key which give a good chronological order.
Otherwise, you can have inconsistency in your result.

Just set only the lowest level of your time dimension. Ex date with a date value in a date datatype.

What is your lowest level ?
Which chronological key have you defined ?

Cheers
Nico

575282

just to back Nico's response above, I have only seen this behaviour when my chronological key was based on an incorrect value in my time dimension. First make sure its set, second check your time dimension and ensure the dimension PK's and chronological keys order correctly.

645922

Thank you all for you suggestions, my question has been answered

Time dimension PK's order is incorrect, more then one PK is assigned to the same chronological key.


Thanks,
Arjun SM

gerardnico

Good to hear so good news to begin a new day.

Good day everybody
Nico

575282

Good morning lol