BPC 10.1 - no sum on time dimension

Hi,
we've a BPC 10.1 sandbox and we're facing several problems
#3 no sum on time Dimension
If you check the attached file you will see that there is no summing up on the time Dimension. I've checked that on BPC 7.5 and 10.0 and it should work on 10.1 as well but it doesn't ... e.g. Account Dimension works fine
Any idea or hint?
Thx

Yes
We used the "BPC_HANA_MIGRATE_FROM_10" as well

Similar Messages

BPC Time Dimension - 13 periods NOT Calendar

My client reports 13 periods in a year (4 weekly).
Quarter two contains 4 periods (periods 4, 5, 6, 7).
I was reading a post about how to set this up properly using the UserTimeId property. They had a situation where they needed to put their 13th period in Qtr 4, and they discussed using this property, but the answer didn't go into exactly what settings to put in the UserTimeid property.
Could someone explain how to set this up in BPC so that it calculates properly - my system is a YearToDate system (not periodic),
regards
scott Farrington

Hi Scott,
Have you tried just putting these 4 periods in Quarter 2 on your time dimension hierarchy? I believe the hierarchy (not the properties) is what drives QTD reporting, so theoretically that should work. I have not tried your specific scenario however as it is a fairly uncommon setup.
If that doesn't work and you can explain exactly what kind of issues you are seeing, then it might be easier for others to come up with helpful solutions.
Thanks,
Ethan

Bpc on Hana Time dimension

Dear Experts,
I have some problems with the creation of dummy members in time dimension.
For examples I have created this member:
2012.TOT
2012 Total Year
013
MONTH
13
TOTAL
2012
Bpc permit to save data on this item, but in the Excel report I can't see it.
The data are in the Bw cube.
I work with SAP BPC NW powered by HANA 10.0 SP13
Any idea?
Thanks in advance
Vale

Have you tested with 3 level dummy members? Please read also this discussion:
Re: Time and Measure Dimension Conflict
Vadim

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

Time Dimension 2 PARENTH2 and PRIOR,NEXT

Hi all,
We have standart TIME hierarchy from AppShell (MONTH, QUARTER, YEAR). But in some cases users want insert data in detalization by week. We decide add additional ID's with detalizations to weeks and add they in second hierarchy. Everything is ok in system.
But than we try write scrip logic with PRIOR or NEXT which use data from previous year it doesn't work. But than we use PRIOR or NEXT with current year months everything ok.
Example of logic.
*XDIM_MEMBERSET TIME = PRIOR, %TIME_SET%, %YEAR%.DEC
*CALC_EACH_PERIOD
*WHEN P_ACCT
*IS A01
*REC(EXPRESSION=%VALUE% - GET(P_ACCT="A02",TIME=PRIOR), P_ACCT = A03)
*ENDWHEN
*ENDWHEN
Then we save data on January it doesn't work. BUt on December prev year A02 and January A01 we have data.
Maybe you have some advises according second TIME dimension hierarchy. I think problem on it.
Best regards,
iaroslav

Hi,
Here is fragment of debuglogic.
Start time --->7:29:17 PM - Date:9/28/2011 (build code:7.5.107)
User:T2RU\bpc.sysadmin
Appset:DEVTELE2
App:BUDGETS
Logic mode:0
Logic by:
Scope by:CATEGORY,INPUTCURRENCY,P_BF,P_BUDDIM,P_BUDDIM2,P_BUSTYPE,P_CC,P_CITY,P_DATASRC,P_PROJECT,TIME
Data File:
Debug File:D:\PC_MS\DATA\WebFolders\DEVTELE2\BUDGETS\PrivatePublications\bpc.sysadmin\TempFiles\DebugLogic.log
Logic File:
Selection:DIMENSION:CATEGORY|BU|DIMENSION:INPUTCURRENCY|RUR|DIMENSION:P_BF|IBF19|DIMENSION:P_BUDDIM|NO_BUDDIM|DIMENSION:P_BUDDIM2|NO_BUDDIM2|DIMENSION:P_BUSTYPE|NO_PRODUCT|DIMENSION:P_CC|3_KEM_FF_FA|DIMENSION:P_CITY|KEM|DIMENSION:P_DATASRC|CCDATA|DIMENSION:P_PROJECT|PR_PL|DIMENSION:TIME|2012.JAN|
Run mode:1
Query size:0
Delim:,
Query type:0
Simulation:0
Calc diff.:1
Formula script:
Max Members:
Test mode:0
Is Modelling:1
Query Type:0
Max members:
Region:
DIMENSION:CATEGORY
BU
DIMENSION:INPUTCURRENCY
RUR
DIMENSION:P_ACCT
----- There a lot of accounts <All> accounts and I dont show it all
DIMENSION:P_BF
IBF19
DIMENSION:P_BUDDIM
NO_BUDDIM
DIMENSION:P_BUDDIM2
NO_BUDDIM2
DIMENSION:P_BUSTYPE
NO_PRODUCT
DIMENSION:P_CC
3_KEM_FF_FA
DIMENSION:P_CITY
KEM
DIMENSION:P_DATASRC
CCDATA
DIMENSION:P_PROJECT
PR_PL
DIMENSION:TIME
2012.JAN
DIMENSION:P_CC
3_KIR_FF_FA
DIMENSION:CATEGORY
BU
DIMENSION:P_DATASRC
CCDATA
DIMENSION:INPUTCURRENCY
RUR
DIMENSION:P_BF
IBF19, IBF15
DIMENSION:P_BUDDIM
NO_BUDDIM
DIMENSION:P_BUSTYPE
NO_PRODUCT
DIMENSION:P_BUDDIM2
NO_BUDDIM2
DIMENSION:TIME
PRIOR, %YEAR%.JAN, %YEAR%.FEB, %YEAR%.MAR, %YEAR%.APR, %YEAR%.MAY, %YEAR%.JUN, %YEAR%.JUL, %YEAR%.AUG, %YEAR%.SEP, %YEAR%.OCT, %YEAR%.NOV, %YEAR%.DEC
DIMENSION:P_ACCT
<ALL>
Loading TIME.TIMEID
Time to load properties:0.0 sec.
select P_ACCT,P_BF,TIMEID,SIGNEDDATA
into #tblTempLogic_266166
from tblFactBUDGETS
WHERE CATEGORY=N'BU' AND INPUTCURRENCY=N'RUR' AND P_BF in (N'IBF19',N'IBF15') AND P_BUDDIM=N'NO_BUDDIM' AND P_BUDDIM2=N'NO_BUDDIM2' AND P_BUSTYPE=N'NO_PRODUCT' AND P_CC=N'3_KIR_FF_FA' AND P_CITY=N'KIR' AND P_DATASRC=N'CCDATA' AND P_PROJECT=N'PR_PL' AND TIMEID in (N'20120400',N'20120800',N'20121200',N'10000425',N'20120200',N'20120100',N'20120700',N'20120600',N'20120300',N'20120500',N'20121100',N'20121000',N'20120900')
insert into #tblTempLogic_266166 (P_ACCT,P_BF,TIMEID,SIGNEDDATA)
select P_ACCT,P_BF,TIMEID,SIGNEDDATA
from tblFactWBBUDGETS
WHERE CATEGORY=N'BU' AND INPUTCURRENCY=N'RUR' AND P_BF in (N'IBF19',N'IBF15') AND P_BUDDIM=N'NO_BUDDIM' AND P_BUDDIM2=N'NO_BUDDIM2' AND P_BUSTYPE=N'NO_PRODUCT' AND P_CC=N'3_KIR_FF_FA' AND P_CITY=N'KIR' AND P_DATASRC=N'CCDATA' AND P_PROJECT=N'PR_PL' AND TIMEID in (N'20120400',N'20120800',N'20121200',N'10000425',N'20120200',N'20120100',N'20120700',N'20120600',N'20120300',N'20120500',N'20121100',N'20121000',N'20120900')
and SOURCE = 0
insert into #tblTempLogic_266166 (P_ACCT,P_BF,TIMEID,SIGNEDDATA)
select P_ACCT,P_BF,TIMEID,SIGNEDDATA
from tblFAC2BUDGETS
WHERE CATEGORY=N'BU' AND INPUTCURRENCY=N'RUR' AND P_BF in (N'IBF19',N'IBF15') AND P_BUDDIM=N'NO_BUDDIM' AND P_BUDDIM2=N'NO_BUDDIM2' AND P_BUSTYPE=N'NO_PRODUCT' AND P_CC=N'3_KIR_FF_FA' AND P_CITY=N'KIR' AND P_DATASRC=N'CCDATA' AND P_PROJECT=N'PR_PL' AND TIMEID in (N'20120400',N'20120800',N'20121200',N'10000425',N'20120200',N'20120100',N'20120700',N'20120600',N'20120300',N'20120500',N'20121100',N'20121000',N'20120900')
select tmpTable.P_ACCT,tmpTable.P_BF,tmpTable.TIMEID,sum(SIGNEDDATA) as SIGNEDDATA
from #tblTempLogic_266166 as tmpTable
group by tmpTable.P_ACCT,tmpTable.P_BF,tmpTable.TIMEID
drop table #tblTempLogic_266166
I saw that TIMEID 10000425 is incorrect -its 2012.DEC.WEEK3 from second hierarchy
Thanks,
Bets regards
Iaroslav

Security on Time Dimension?

A while back when we built out our BPC environment it was recommended that the Time Dimension not be part of security. What are you thoughts on applying secuirty on the time dimension?
Th reason I ask is because the getonly range on templates is fragile. Securing time would help us protect our actuals.
Thanks for any insight
Cheers,
Mark

Hi
Please try the following :
This is to fix Secure Time Dimension for DM in BPC 5.1SP01
Install this patch to receive an updated OSoftDMTaskMain.dll file. To install the patch, perform the following steps:
1. Uncompress the file CPMBPC01P_2.zip.
2. Locate the BPC Setup folder that contains the executable program file "[Server] AutoUpdate For BPC 5.1 (5.0.496.01).exe".
3. Run this executable file on the Application Server, choosing Install when prompted.
4. A "Successfully updated" message appears when the installation completes successfully.
Raghu B.S.

How can I modify Time dimension to create a Top member above year members ?

Hi experts,
I would like to modify Time dimension to add a Top member above year members.
I already did a test:
I added a member in Time dimension which is the parent of all year members. I granted it these property values:
- ID = TOTAL
- EVDESCRIPTION = Total
- LEVEL = TOTAL
- HLEVEL = 1 (and I added 1 to all the other members)
- TIMEID = 10000001
All other properties were left blank for this member.
I processed the dimension. It went well. But when I tried an evdre in BPC excel it failed.
Any idea of something missing ?
I am working on SAP BPC MS 7 SP4
Thanks for your help
Ludovic

Hi Petar,
Thanks for your answer. No doubt that we could solve the issue using on of the way you suggested.
However, even though I had the evdre issue right after applying time dimension modifications, it occurs that the evdre issue was not due to time dimension modifications. I tested it better and I can tell that using "total" as a level works.
Best regards,
Ludovic

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

Updating master data for time dimensions from front end

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

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

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

Display all dates between date range (Time Dimension left outer join Fact)

All,
I have done some searching around this issue but within all the posts regarding date variables, date prompts and date filtering I haven't seen one exactly answering my issue (maybe they are and I just dont have my head around it correctly yet).
My report requirement is to allow a user to select a start day and an end day. The report should show all activity between those two days - AND display 0/null on days where there is no activity. That second part is where I am getting hung up.
The tables in question are:
TimeDim
EventFact
CustomerDim
My BMM is setup as follows:
TimeDim left outer join EventFact
CustomerDim inner join EventFact
If I run a report selecting DAY from TimeDim and a measure1 from EventFact with day range 1/1/2010 - 12/31/2010 .. I get a record for every day and it looks perfect because of the left outer join between TimeDim and CustomerDim.
But .. if I add in a field from CustomerDim, select TimeDim.DAY, CustomerDim.CUSTNAME, EventFact.MEASURE1, OBIEE only returns records for the days that have EventFact records.
This is due to the fact that the TimeDim is still outer joined into EventFact but adding in CustomerDim makes OBIEE setup an inner join between those tables which then causes only data to be returned where EventFact data exists.
There is a way around this in this simple case and that is to define the relationship between CustomerDim and EventFact as an outer join as well. This will give the desired effect (but an outer join between these two tables is not the true relationship) and as I add additional dimensions and add additional logical sources to a single dimension in the BMM it gets complicated and messy.
Ive also messed with setting the driving table in the relationship, etc.. but it has not given the desired effect.
Has anyone ever encountered the need to force display all dates within a specfied range with a fact table that may not have an entry for every date?
Thanks in advance.
K
Edited by: user_K on Apr 27, 2010 11:32 AM

It worked!!!* Even my time drill downs and date based filtering still work!
That is awesome. Never would have thought of that intuitively.
Now, just need a little help understanding how it works. When I run my report and check the logs I can see that two queries are issued:
Query 1: Joins the fact table to all the associated dimensions. I even changed all the relationships to inner joins (which is what they truly are). And calculates the original measure. If I copy and paste this query into sql developer it runs fine but only returns those rows that joined to the time dimension - which is what was happening before. It is correct but I wanted a record for every time dimension record.
Query 2: Looks like the following:
select sum(0)
from timedim
where date between <dateprompt1> and <dateprompt2>
group by month *<--* this is the time dimension level specified in Query 1, so it knows to aggregate to the month level as was done in query 1
Final Question: So what is OBIEE doing ultimately, does it issue these two requests and then perform a full outer join or something to bring them together? I couldn't see anywhere in the log a complete query that I could just run to see a similar result that I was getting in Answers.
Thanks for all the help .. Id give more points if I could.
K

Creating P&L report with Time dimension view ( Period , HTD, YTD )

Hi
I have a requirement to create P&L report that will Time dimension view ( Period , HTD, YTD ). I guess the original report was created with hyperion tool now they want the same in BO report.
Is this technically possible with BEX since there is no standard time object for YTD and HTD. I know in BPC there are ready made objects.
does any one know how I can create this solution with BEX.
thanks
Bhat

Hi,
It is possible in BEx. You would need to create variables of type customer exit and write code to realize YTD, etc. Check the forums for documents and sample code.

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

Locking Periods using the Second Hierarchy in the Time Dimension

Hi,
They are not usiing work status for this...
I am at a client, and they used the second hierarchy in the time dimension to lock periods. If they left the second hierarchy blank, no data can be written to it. To open the open the period, they code the Second Heirarchy with CONS_OPEN. Just wondering if anyone has information on this?
It was working fine, then we needed to run a transport to move BPC to a new machine, and it stopped working. Not sure if anyone has done it this way before?
Thanks,
Chandra

Dear Kacper,
the way I understood, there are two separate questions in this post, namely:
I'm using a shared resource in multiple actors, and the code accessing the resource can take quite some time to execute. How can can I ensure this does not mess up the timing of one or all accessors?
I'm using a shared resource in multiple actors, and the code accessing the resource can generate errors if I try to access it from multiple places. How can I ensure synchronization between all accessors?
As for the first question, the optimal solution to separate the resource prone to timing issues in a different thread/actor. Put anything that is not strictly timed (file access, network comunication) in a separate loop. For each actor, you will get queue references to communicate with, so instead of logging the measurements in the actors where they are made, just queue them up for a different loop to process.
For the second part, the same logic still applies. Ideally, every singular resource should be handled by its own thread and nowhere else, so if anything else needs data from/to said resource, it can send a request to the dedicated thread or actor.
If, for some reason, this is not sufficient, you have to handle synchronization in some other way. There are a lot of techniques here, for example:
Create a named semaphore or lock as a part of the class. Have class functions use the semaphore before accessing the resource.
Use actor messages. Have a "resource in use" or "resource released" messages sent to all users whenever obtaining or releasing said resource.
Have a separate actor handle all resources, awarding them to threads needing them. This method also allows setting priorities between requests.
These are just a few examples, there are many other options.
Please let me know if this was helpful.
Kind regards:
Andrew Valko
National Instruments Hungary

Aggregation mode along one dimension (product) different than along the time dimension

Dear All,
In IBP S&OP, Is it possible that the aggregation mode along one dimension (product) could be different than along the time dimension?
For a demo, a customer has an input at the product family level (vehicle production) which we just “copy” for disaggregation purposes, to the product level (parts), see attached. So for aggregation we used average.
However, time-wise, we need to sum it up.
Thanks for your insight and help.
Kind Regards,
Omar

Hi Omar,
Yes it is possible.
1. Create a new planning level (say PERPRODCUST1) which will be a copy of PERPRODCUST (you base planning level).
2. In the PER section of PERPRODCUST1, do NOT mark any period attribute as root. In other words, the roots for this PL will only be PRDID and CUSTID.
3. Now your KF calculations will be:
VEHICLEPRODUCTION@PERPRODCUST1 = SUM(VEHICLEPRODUCTION@PERPRODCUST)
VEHICLEPRODUCTION@REQUEST = AVG(VEHICLEPRODUCTION@PERPRODCUST1)
Since your KF is editable, it is worth mentioning that, following the above steps has trade-offs. Since your KF is editable, you will have issues with disaggregation when you enter the values at an aggregated level of both time and other attributes. My recommendation (for your configuration) is that this will work fine as long you enter the values at the root level of you time attribute.
Hope this helps,
Chendur

BPC 10.1 - no sum on time dimension

Similar Messages

Maybe you are looking for