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

Similar Messages

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

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 7.5 Input Schedule in Excel 2010 - Expand time dimension dynamically

Hi BPC experts,
My project dimension has two properties, one for startdate and one for enddate of the underlying project. Example: Project XYZ, startdate: 2010.APR, enddate: 2011.JUN
In my input schedule I need the timespan to expand on month level from 2010.APR up until 2011.JUN. In this case it needs to expand 15 months where each month is displayed per column.
The issue is that all projects have different start and end dates and the expansion on month level needs to adjust accordingly. There is no maximum project time frame but if it helps I can live with a maximum expansion of for instance max 100 months.
I have another dimension for time with a hierarchy year - quarter - month (month being the basemember).
Every tipp highly appreciate!
Regards
Sven

Hi,
1) i use EvMBR for list values the CEBE necesaries.
2) Define ListBox by source list the EvMBR
Is necesary use Index() for get value the indice returned by Listbox when is selected the value.
3) Use EvGTS() linked to value getting by Index()
4) This is code in EvGTS:
=SI(EVGTS($N$11;1;"CEBE:CI1CA001";$N$14;"CUENTA:ZACB0001";$N$16;I28;"MONEDA_PPTO:USD";"PARAMETRO:NA";$N$20;$N$21;"SUCURSALES:NA";$M$27;$N$24)="#NODATA";"";EVGTS($N$11;1;"CEBE:CI1CA001";$N$14;"CUENTA:ZACB0001";$N$16;I28;"MONEDA_PPTO:USD";"PARAMETRO:NA";$N$20;$N$21;"SUCURSALES:NA";$M$27;$N$24))

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

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

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

BPC Script Logic Multi-dimension REC Statement

Hi All BPC Experts,
The way that our data in the dimensions is setup, members in one dimension have properties that "point" to members in other dimensions.
In this case when I write the REC statement, whilst I'm just doing arithmetic on P_ACCT, when I write the final value, I also need to specifiy the members for the dimensions CUSTOMER, ENTITY, MINE, DESTINATION.
In the example below I hve hardcoded the CONTRACT and TIME dimension members, but going forward, this logic will be appllied to a number of CONTRACTS and TIMES so the members of the other dimensions need to be retrieved dynamically.
*XDIM_MEMBERSET P_ACCT = CAPACITY_REV,CAPACITY_RATE,FINAL_VOLUME
*XDIM_MEMBERSET CATEGORY=FORECAST
*XDIM_MEMBERSET P_DATASRC=Input
*XDIM_MEMBERSET CONTRACT=0005000001_10
*XDIM_MEMBERSET TIME=2009.JUL
*WHEN P_ACCT
      *IS CAPACITY_RATE
         *BEGIN
            REC(EXPRESSION=(%VALUE%[P_ACCT].[FINAL_VOLUME]),
                     CUSTOMER = CONTRACT.CUSTOMER,
                     DESTINATION = CONTRACT.DESTINATION_ID,
                     ENTITY = CONTRACT.HAUL_PC,
                     MINE = CONTRACT.MINE_ID,
                     P_ACCT = "CAPACITY_REV")
         *END
*ENDWHEN
*COMMIT
My Question is twofold:
- Can anyone see any problems with the above code, ie is this a valid way of writing the REC statement?
- Can anyone suggest another way of writing this code?
Best regards
Mark Rodrigues

Just repostoing the logic as "Code"
*XDIM_MEMBERSET P_ACCT = CAPACITY_REV,CAPACITY_RATE,FINAL_VOLUME
*XDIM_MEMBERSET CATEGORY=FORECAST
*XDIM_MEMBERSET P_DATASRC=Input
*XDIM_MEMBERSET CONTRACT=0005000001_10
*XDIM_MEMBERSET TIME=2009.JUL
*WHEN P_ACCT
*IS CAPACITY_RATE
    *BEGIN
        REC(EXPRESSION=(%VALUE%P_ACCT.FINAL_VOLUME),
                                        CUSTOMER = CONTRACT.CUSTOMER,
                                        DESTINATION = CONTRACT.DESTINATION_ID,
                                        ENTITY = CONTRACT.HAUL_PC,
                                        MINE = CONTRACT.MINE_ID,
                                        P_ACCT = "CAPACITY_REV")
    *END
*ENDWHEN
*COMMIT

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

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

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

Disaggregate Periodic Data to Weekly Data (Modeling Time Dimension)

Hi,
We are using BPC MS Version 7.0. Our users plan at period level and I need to disaggregate periodic data to weekly data by looking up weeks from Time Dimension.
Suppose if 2009.Jan has 4 weeks I need the following result
Periodic Data
2009.Jan Acct1 1000$
Weekly Data
2009.Jan Wk1 Acct1 250$
2009.Jan Wk2 Acct1 250$
2009.Jan Wk3 Acct1 250$
2009.Jan Wk4 Acct1 250$
Can we model Time Dimension with two hiearchies to achieves this?
Which is best way to dissaggrate? (Stored Proc or SSIS Pacakge or Script Logic) ?
Thanks
Raj

An easy way to achieve this feature is to have the time dimension be weekly and do the spread on the input schedules before sending.
There would be two EVDREs (one refresh only of monthly data and the other send only of weekly data). The data range of the monthly EVDRE would be input and where the user enters data. The data range of the weekly EVDRE would be formulas (pointing to the monthly data and doing the correct division based on number of weeks in a month). The user is inputting monthly data, but the schedule is sending the weekly values.
The allocation will work as well, but I would suggest to create a weekly input node under each month to capture the monthly value and then spread to the weekly members.
JAN
|---WK Input
|--- WK1
|--- WK2
|--- WK3
|--- WK4

Bpc on Hana Time dimension

Similar Messages

Maybe you are looking for