TIME Dimension - TIME_SPAN parameter value (constant or decrementing?)

Hi all
For the the 'TIME_SPAN' parameter value in dimension of type 'TIME', should the value be constant for all members in a particular level or should the value decrement over time as the period progresses.
For example, for a TIME dimension having levels DAY > MONTH should the values for TIME_SPAN be:
DAY, DAY_END_DATE, DAY_TIME_SPAN, MONTH, MONTH_END_DATE, MONTH_TIME_SPAN
D01JAN2010, 01-01-2010, 1, M01_Y2010, 31-01-2010, 31
D02JAN2010, 02-01-2010, 1, M02_Y2010, 31-01-2010, 31
D03JAN2010, 03-01-2010, 1, M03_Y2010, 31-01-2010, 31
and so on...
or like below:
D01JAN2010, 01-01-2010, 1, M01_Y2010, 31-01-2010, 31
D02JAN2010, 02-01-2010, 1, M02_Y2010, 31-01-2010, 30
D03JAN2010, 03-01-2010, 1, M03_Y2010, 31-01-2010, 29
and so on...
Any assistance will be appreciated.
Cheers.

Here's a script that might be helpful to you. It fills in aggregate values for date and times span when you have existing days with date data type. If you have time periods shorter than a day, you might check out this post.
http://oracleolap.blogspot.com/2010/05/time-dimensions-with-hourly-time.html
CREATE TABLE time_dim
DAY_KEY DATE,
DAY_TIME_SPAN NUMBER,
MONTH_ID VARCHAR2(30),
MONTH_END_DATE DATE,
MONTH_TIME_SPAN NUMBER,
QUARTER_ID VARCHAR2(30),
QUARTER_END_DATE DATE,
QUARTER_TIME_SPAN NUMBER,
CALENDAR_YEAR_ID VARCHAR2(30),
YEAR_END_DATE DATE,
YEAR_TIME_SPAN NUMBER
-- Add rows for days. E.g.,
-- insert into time_dim (select distinct day_key from fact_view);
--UPDATE time_dim
--SET hour_time_span = round(1/24,5);
-- Add month members.
UPDATE time_dim SET month_id = TO_CHAR(day_key 'MON-YYYY');
UPDATE time_dim a
SET month_time_span =
(SELECT ts
FROM
(SELECT DISTINCT month_id,
SUM(day_time_span) AS ts
FROM time_dim
GROUP BY month_id
) b
WHERE a.month_id = b.month_id
UPDATE time_dim a
SET month_end_date =
(SELECT ed
FROM
(SELECT DISTINCT month_id,
MAX(day_key) AS ed
FROM time_dim
GROUP BY month_id
) b
WHERE a.month_id = b.month_id
-- Add Quarter members.
UPDATE time_dim SET quarter_id = TO_CHAR(day_key 'Q-YYYY');
UPDATE time_dim a
SET quarter_time_span =
(SELECT ts
FROM
(SELECT DISTINCT quarter_id,
SUM(day_time_span) AS ts
FROM time_dim
GROUP BY quarter_id
) b
WHERE a.quarter_id = b.quarter_id
UPDATE time_dim a
SET quarter_end_date =
(SELECT ed
FROM
(SELECT DISTINCT quarter_id,
MAX(day_key) AS ed
FROM time_dim
GROUP BY quarter_id
) b
WHERE a.quarter_id = b.quarter_id
-- Add Year members.
UPDATE time_dim SET month_id = TO_CHAR(day_key 'YYYY');
UPDATE time_dim a
SET year_time_span =
(SELECT ts
FROM
(SELECT DISTINCT year_id,
SUM(day_time_span) AS ts
FROM time_dim
GROUP BY year_id
) b
WHERE a.year_id = b.year_id
UPDATE time_dim a
SET year_end_date =
(SELECT ed
FROM
(SELECT DISTINCT year_id,
MAX(day_key) AS ed
FROM time_dim
GROUP BY year_id
) b
WHERE a.year_id = b.year_id
;

Similar Messages

  • Parameter  value "Half year " is not accepting by while updating time dimen

    Hi,
    while i am updating "Time" dimention i am getting an error as parameter value "Halfyear" is not valid value. But system is  accepting Daily, Monthly, Quarterly and yearly under Level parameter.
    So please advise me how to proceed on this.
    Regards,
    M.Chandra Sekhar Chowdary

    Hi,
    This is definitely not the answer you might be expecting. We have it as 'DAY' for the level property values for H1 and H2(completely not reasonable). But you can process the TIME dimension with this 'value' for half year provided you dont have dates as your time members (which may be the case).
    Try using 'DAY' and process the dimension as a work around. We could wait if there is any other valid reason behind this (not taking 'halfyear').
    Thanks

  • Time dimension (Using Wizard)

    Hi
    i want to create Time dimension using simple wizard(not through time wizard)
    i have following attributes in it
    Year( year ID,year Discription)
    Quarter(Quarter ID,Quarter Discription)
    Month ( Month ID,Month Discription)
    Week ( week ID,week Discription)
    DAY ( Day ID,Day Discription)
    Hours ( hours ID,hours Discription)
    i complete time dimension with simple wizard but it create sequence and table
    so what is mapping for it kindly give me guide in detail
    thnx in advance

    Hi,
    you may create your custom time dimension using the simple wizard.
    To fill it with values, create another time dimension with the time dimension wizard. Fill it using the generated mapping.
    Then write your own mapping to fill your time dimensions with the values from the generated one.
    This way is easier than to write some custom logic to fill your custom time dimension.
    Regards,
    Carsten.

  • French characters in run time parameter values doesn't show up in emails

    We have a custom workflow with configurations to send email when a request is assigned to a person and also to send email on request rejections.
    We are encountering following issues with respect to French characters that are available in the message body and message subject.
    Issue 1:Notifications are configured in Human Task (ApprovalTask.task) when a task is assigned. Since the message body contains French characters we have used ISO-8859-1 encodings to render the message properly to the user. The message body also has some run time content from the task payload.
    For e.g. À titre de responsable fonctionnel, une demande d''approbation pour un accès informatique vous est assignée.
    Acc&#232;s informatique demand&#233; : <%/task:task/task:payload/ns1:ObjectDetails/ns1:name%>
    In this case all static text values are rendered properly to the end user in his email. However the French characters in run time parameter values doesn't show up properly and has some weird characters.
    Issue 2: Unable to change the default subject shown in the approval task emails i.e. Notifications are configured in Human Task (ApprovalTask.task) when a task is assigned. By default it shows Action Required: Approval. How can this default value be changed?
    Issue 3: We have an Email Activity in Bpel process that follows a task rejection. The emailpayload is ISO-8859-1 encoded and works for the message body. However the email subject shows up with ISO-8859-1 encodings itself and doesn't convert to proper string in the end user's email. Is there any specific setting required for french characters in subject?

    Hi Kulwinder,
    Thanks for your reply.
    In fact I do, I've follewed the "Using SAP HANA Variables with SAP BusinessObjects BI4.0" guide.
    Please note, when I use a fix value to parameter is working fine, for example:
    SELECT *
    FROM "_SYS_BIC"."prueba-concepto/CV_TEST_VAR_II" ('PLACEHOLDER' = ('$$FECHA$$','20130530'))
    But when I set prompt of the DataFoundation parameter I get and error, this is my sentence:
    SELECT *
    FROM "_SYS_BIC"."prueba-concepto/CV_TEST_VAR_II" ('PLACEHOLDER' = ('$$FECHA$$',@Prompt(FECHA)))
    To me is very curious that I can't enter a value in the DataPreview in Hana Studio, because is not requested, even when the input parameter have been set as mandatory
    Have you idea of what could be happening?

  • 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

  • Dimension Time - Level property SEMESTER value?

    Hello all,
    I'm triying to organize a time dimension this way:
    -YEAR
      -SEMESTER
        -QUARTER
          -MONTH
    I've an issue, and it's when I'm setting the LEVEL property to the corresponding semester in the hierarchy. If I set it to SEMESTER, the dimension won't process. What is the correct value for a semester? In the meantime I left the property set to QUARTER, is there any problem with this?
    Thanks in advance!
    Best regards

    Hi Giovanni,
    As you can see in the documentation here ([http://help.sap.com/saphelp_bpc75_nw/helpdata/en/4a/88580e1e01465f9ae876ffc46becd2/frameset.htm]), SEMESTER and HALFYEAR are not valid options for the LEVEL property in BPC NW. You could set these members as QUARTER and then set the actual quarters as MONTH and so on, but this will mess up your QTD and PERIODIC calculations, so it is not a good option.
    I recommend that you maintain a PARENTH1 hierarchy on your time dimension that has conventional years, quarters, and months. Then maintain a secondary PARENTH2 hierarchy that contains only semesters/half-years (with the LEVEL set to YEAR or QUARTER) and months. In this way you can provide an aggregation on semester for your users.
    If that is not what you are trying to accomplish, can you tell us a little bit more about what it is you want to do with these semesters?
    Cheers,
    Ethan

  • URL Reporting Time parameter value.

    We have installed Business objects XIR2 and one of our application uses URL reporting to call a crystal report. Parameter values are retrieved from the database and used in the url.  Reports that do not have a time parameter works fine.  Even though I pass the time parameter value Im still prompted for the value.  The format of the url I use is http://hostname/businessobjects/viewrpt.cwr?init=dhtml&apstoken=<token>&prompt0=02:02:20&prompt1=LOCCODE
    where prompt0 is of type par_time.  Could someone please help me with the correct format to use for parameter type time?

    Ted, I checked the prompt order and the prompt type and they are correct.  These reports are working fine on Crystal 9.  Also reports that do not have a time parameter works fine in Crystal 11. Its only when reports with time parameter are called Im prompted for a value to be entered in hh:mm:ss format although I tried passing the value in hh:mm:ss format and Time(hh, mm, ss) format in the url.  The report comes up fine after entering the value in hh:mm:ss value in the prompt.  I tried encoding the url but it didnt work.  If I encode the entire url Crystal prompts me to enter values for all parameters.

  • Setting date ranges when Time dimension includes Period instead of Month

    I hope I am missing something simple here - we are on OBIEE 10g, and I have a Time dimension defined as follows:
    Year > Quarter > Period > Week > Day
    A "period" is not equivalent to a calendar month - a period can include either 4 or 5 weeks, and always starts on a Sunday. Fiscal years start on the first Sunday in July.
    I need to create a graph that shows Total Sales for the previous 13 periods (not including the current period). This needs to be a rolling 13 periods based on the current period.
    Since this is Period and not Month, I am unable to use the Month(CURRENT_DATE) functionality. Do I need to have repository variables defined for the current period? Is there another way to calculate what the current Period in my Time dimension is in a filter SQL?
    So I want to do something like "Where period between [current_period - 14] and [current_period -1] as the filter for Period.
    Thanks in advance for any assistance.
    Rhonda

    Sorry about that...
    Periods are 1-12 (numeric).
    Period 4 of FY 2012 for example has a begin date of 10/02/2011 and end date of 11/05/2011.
    Right now we do not have unique combos created (like 4/2012, 5/2012, etc) so to get a unique value I have to specify both a year and period.
    So on my dashboard today I will need to create a graph that covers FY2011 periods 6-12 and FY2012 periods 1-6 (translates to 12/5/2010 - 12/31/2011).
    I haven't created repository variables before, but as the Period parameter will be used often I guess I will find out how.
    Thanks in advance for the help.
    Rhonda

  • 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

  • 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

  • Time dimension with Hourly base time periods

    Hi all
    I need to analyze data at Hour, Day, Month, and Year levels. The data in the fact and dimension tables are at the 'Hour' level with DATE datatype, such as:
    02-SEP-10 10:00:00 AM
    02-SEP-10 11:00:00 AM
    To use Time-Series type calculations, I understand that I have to create an OLAP dimension of type 'TIME' (and not 'USER') and map it to the populated relational time dimension table.
    1) Can I have the primary key for 'Hour' level as the actual base level value of datatype DATE (eg. 02-SEP-10 10:00:00 AM) ?
    2) For the END_DATE and TIME_SPAN attributes at the 'Hour' level, what should I use?
    The documentation is only available for minimum 'Day' level hierarchies, which allows setting END_DATE and TIME_SPAN to the actual 'Day' value and 1, respectively.
    3) For the END_DATE and TIME_SPAN attributes at the 'Month' level, do I need to supply the last-date-of-each-month and number-of-days-in-that-month, respectively?
    Please bear in mind that I am relatively new to Oracle OLAP. Any assistance will be appreciated.
    Cheers.

    Thank you Szilard and Adnan for the very prompt and informative responses.
    I managed to follow the advice on the oracleolap.blogspot link and created a time dimension with members at Hour level loaded into the dimension in character format: TO_CHAR(hour_id, 'DD-MON-YYYY HH24')
    The problem now is the maintenance (loading) of the dimension is taking an abnormally large amount of time (over 1 hour) as opposed to when the members were being loaded in DATE format (5 minutes). The mapping table only as 10,000 entries.
    Why is these such a big difference? Is it normal? Is there a way to speed up the maintenance time?
    FYI, I have not created any indexes on any of the attributes.
    My platform is:
    11.1.0.7.0 DB
    11.1.0.7.0B Client

  • Time Dimension with Hourly base level

    Hi all
    I need to analyze data at Hour, Day, Month, and Year levels. The data in the fact and dimension tables are at the 'Hour' level with DATE datatype, such as:
    02-SEP-10 10:00:00 AM
    02-SEP-10 11:00:00 AM
    To use Time-Series type calculations, I understand that I have to create an OLAP dimension of type 'TIME' (and not 'USER') and map it to the populated relational time dimension table. My questions are:
    1) Can I have the primary key for 'Hour' level as the actual base level value of datatype DATE (eg. 02-SEP-10 10:00:00 AM) ?
    2) For the END_DATE and TIME_SPAN attributes at the 'Hour' level, what should I use?
    The documentation is only available for minimum 'Day' level hierarchies, which allows setting END_DATE and TIME_SPAN to the actual 'Day' value and 1, respectively.
    3) For the END_DATE and TIME_SPAN attributes at the 'Month' level, do I need to supply the last-date-of-each-month and number-of-days-in-that-month, respectively?
    Please bear in mind that I am relatively new to Oracle OLAP. Any assistance will be appreciated.
    Cheers.

    Thank you Szilard and Adnan for the very prompt and informative responses.
    I managed to follow the advice on the oracleolap.blogspot link and created a time dimension with members at Hour level loaded into the dimension in character format: TO_CHAR(hour_id, 'DD-MON-YYYY HH24')
    The problem now is the maintenance (loading) of the dimension is taking an abnormally large amount of time (over 1 hour) as opposed to when the members were being loaded in DATE format (5 minutes). The mapping table only as 10,000 entries.
    Why is these such a big difference? Is it normal? Is there a way to speed up the maintenance time?
    FYI, I have not created any indexes on any of the attributes.
    My platform is:
    11.1.0.7.0 DB
    11.1.0.7.0B Client

  • "Missing parameter values."  --  Export and Print only...

    I have a web application and I am using CrystalReportViewer.  I am passing several parameters to Crystal using: 
    report.SetParameterValue(field.Name, Session[field.Name]);
    I have session variables which will hold parameters needed to pass into the report.  The session variables are populated from controls on my webpage after an onclick event.  This even not only populates session, but also passes parameters to the report with the following code: 
    ReportDocument report = new ReportDocument();
    Session["MapPathName"] = "./Reporting/CaseStudy.rpt";
    report.FileName = Server.MapPath(Session["MapPathName"].ToString());
    ParameterFields fields = new CrystalDecisions.Shared.ParameterFields();
    fields = report.ParameterFields;
    foreach (ParameterField field in fields)
          report.SetParameterValue(field.Name, Session[field.Name]);
    CrystalReportViewer1.ReportSource = report;
    This works great for reporting and is very extensible.  However, when clicking on the "Print" or "Export" buttons on the toolbar I get "Missing parameter values."  I attempted to export manually in code using the .ExportToStream function but I still get the error, "Missing parameter values." 
    I received this error also in Refresh, Search, and Navigate functions.  This was corrected by calling a function that supplies the above code block to these functions.  However, I do not see any events for controlling the Print nor the Export events. 
    QUESTION: How can I print or export a report when passing parameters using CrystalReportViewer?  Thanks in advance!
    P.S. - Crystal Reports XI Release 2
    Edited by: KyleSavant on Jun 18, 2009 5:42 PM

    There are no Export or Print events accessible for the viewer
    Since it sounds like you are creating the reportdocument object in your click event, the settings on this object become out of scope on successive postbacks executed by other events.
    to get around this without major changes, you can place your "report" object in session in this event and retrieve it from session on successive postbacks.  This should solve your problems around navigation, printing and exporting.  What you will need to do is check if the session object exists (usually in page_load or page_initialze) and if so, retrieve it from session and bind it to the viewer's reportsource.  If the session object does not exist, then do nothing (ie you have not clicked your button yet that retrieves the parameter values from session and loads the report).  Also, in your click event you can check if the report session object exists and if so, remove it so that it can be re-created with your new parameter values (ie i'm assuming the only time you want to set parameter values is in this event).
    Dan

  • How to suppress "enter parameter values" screen in crystal reports for Visu

    Hi,
        I am passing parameters to the report through program.  But still the "Enter Parameter Values" Dialog is shown every time I run the application.  Code used to pass parameters is given below:
                    rptCBBookRpt objRptCBBook = new rptCBBookRpt();
                    objRptCBBook.SetParameterValue("@Branch", strBranch);
                    objRptCBBook.SetParameterValue("@CoName", mdlFinIF.objCommon.CoName);
                    objRptCBBook.SetParameterValue("@Heading", strHeading);
                    objRptCBBook.SetParameterValue("@UserInfo", mdlFinIF.objCommon.ReportInfo());
    How can I suppress the "Enter Parameter Values" dialog.  Please help.
    Cris Evan

    Well, no. But this being a community, not technical support, you may get a response, perhaps even an actual answer, or you may not...
    If you are not getting a response or an answer, you may want to consider obtaining a dedicated support here:
    http://store.businessobjects.com/store/bobjamer/en_US/pd/productID.98078100?resid=S6I@hgoHAkEAAGsiyVkAAAAR&rests=1282226845369
    Look at samples here:
    https://wiki.sdn.sap.com/wiki/display/BOBJ/CrystalReportsfor.NETSDK+Samples
    Check out the [Crystal Reports for Visual Studio 2005 Walkthroughs|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/2081b4d9-6864-2b10-f49d-918baefc7a23] - it will apply to your version of CR...
    And of course, developer help files.
    - Ludek

  • Slicer Time Dimension Issue with Cube Functions

    Hi,
    Hoping someone can help me figure out right approach here.
    Summary:
    Using Excel 2013 connected to a SSAS cube as data source, and cube functions with slicers to create a dashboard.
    Have following time dimension slicers; Fiscal Year, Fiscal Quarter, Fiscal Month, Fiscal Week & Date, that are used to slice data based on user selection, along
    with a sales measure.
    Below is example of Slicer name and CubeMember function for each:
    Slicer_Fiscal_Year: 
    =CUBEMEMBER("Cube","[Date].[Fiscal Year].&[2015]")
    Slicer_Fiscal_Quarter: 
    =CUBEMEMBER("Cube","[Date].[Fiscal Quarter].[All]")
    Slicer_Fiscal_Month: 
    =CUBEMEMBER("Cube","[Date].[Fiscal Month].&[201408]")
    Slicer_Fiscal_Week: 
    =CUBEMEMBER("Cube","[Date].[Fiscal Week].&[201509]")
    Slicer_Date: 
    =CUBEMEMBER("Cube","[Date].[Date].[All]")
    Problem:
    What I am trying to do is to build a table with cube functions that takes the lowest grain of the slicer time dimension selected, shows the current member, plus
    the prior 7 so I can have an 8 period trending view table that I will build a chart from. In the above example that would mean that it would look at Slicer_Fiscal_Week since that is lowest grain that has an attribute other than All, and then show me the prior
    7 periods. In this case 201509 means Week 9, so I would want to show in table Week 9 back to Week 2. But if Slicer_Fiscal_Week was set to All, along with Slicer_Date, then Fiscal Month would be lowest grain, so I would want to show Fiscal Months from August
    (201408) back to January 2014. I know how to use CubeRankedMember to pull the value from what is selected in the slicer, the problem is figuring out how to pass the lowest grain time dimension so that I can use lag or some other MDX function to get the previous
    periods.
    Any help on this would be greatly appreciated.
    <object height="1" id="plugin0" style=";z-index:1000;" type="application/x-dgnria" width="1"><param name="tabId" value="{28593A5C-70C0-4593-9764-80C76B51795C}"
    /></object>

    Hello,
    Thank you for your question.
    I am trying to involve someone familiar with this topic to further look at this issue.
    George Zhao
    TechNet Community Support
    It's recommended to download and install
    Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
    programs.

Maybe you are looking for