You are not logged in.

Copying dimensions values between 2 cubes

Dear visitor, welcome to Palo Community Forum. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

matze_knauer

Professional

  • "matze_knauer" started this thread

Posts: 26

Date of registration: May 26th 2010

  • Send private message

1

Thursday, July 22nd 2010, 3:43pm

Copying dimensions values between 2 cubes

Hi,

I've got a little issue getting access from two cubes.

here's the scenario:
in cube project_calculations i calculated amount x price = turnover.

in cube master i need to get access on that figure. just the entire figure, on the full year.

problem is, i filled the master cube with less dimension, due to the fact that there won't be any hard calculations, so its faster and cleaner.

is it still possible to get access while not having the same dimensions?

btw: i couldn't find any hind in the manual ...

cheers,
mathias
Cheers,
Mathias

Master Student Controlling & IT: Leuphana University Lueneburg (Germany)

holger_b

Sage

  • "holger_b" is male

Posts: 271

Date of registration: Jun 1st 2010

Location: Freiburg, Germany

Occupation: BI Consultant

  • Send private message

2

Thursday, July 22nd 2010, 4:04pm

RE: Copying dimensions values between 2 cubes

Hi Mathias,

sure you can. You will need a PALO.DATA() function to retrieve the value and for instance a PALO.SETDATA() function (or a rule) to write the value to the target cube, for example:

PALO.SETDATA(PALO.DATA(<server/database>; <source cube>; item; turnover);FALSE;<server/database>; <target cube>; item; turnover; month; version)

Now the question arises, which month and which version? This is an aspect of your data model, since the source cube contains no information about month and version, but technically no problem.


Regards
Holger

This post has been edited 2 times, last edit by "holger_b" (Jul 22nd 2010, 4:09pm)

matze_knauer

Professional

  • "matze_knauer" started this thread

Posts: 26

Date of registration: May 26th 2010

  • Send private message

3

Thursday, July 22nd 2010, 4:10pm

Thanks, that was quick! I'll try that one!
Cheers,
Mathias

Master Student Controlling & IT: Leuphana University Lueneburg (Germany)

matze_knauer

Professional

  • "matze_knauer" started this thread

Posts: 26

Date of registration: May 26th 2010

  • Send private message

4

Thursday, July 22nd 2010, 4:16pm

sorry just forgot to answer to the rest of your question :-)

all months and all the other elements as well. so, always the sum of all...

in the master cube there's still the element/dimension year.
Cheers,
Mathias

Master Student Controlling & IT: Leuphana University Lueneburg (Germany)

holger_b

Sage

  • "holger_b" is male

Posts: 271

Date of registration: Jun 1st 2010

Location: Freiburg, Germany

Occupation: BI Consultant

  • Send private message

5

Thursday, July 22nd 2010, 4:16pm

Jah, no problem. I am currently updating my SQL Server installation to a new version, that gives me lots of free time while I watch that progress bar :-)

This post has been edited 1 times, last edit by "holger_b" (Jul 22nd 2010, 4:17pm)

holger_b

Sage

  • "holger_b" is male

Posts: 271

Date of registration: Jun 1st 2010

Location: Freiburg, Germany

Occupation: BI Consultant

  • Send private message

6

Thursday, July 22nd 2010, 4:23pm

Okay. Then you will either have to splash (that is, distribute the sum in equal parts to all the underlying base elements), or you can add a dummy base element to the dimension for those cases. I got used to naming it something like "#_Year", and make it a child of the top element.

Have fun
Holger

matze_knauer

Professional

  • "matze_knauer" started this thread

Posts: 26

Date of registration: May 26th 2010

  • Send private message

7

Thursday, July 22nd 2010, 4:30pm

doesn't work that way.

Here's the rule, i just generated.
['Produktumsätze je Monat'] = Palo.SetData(PALO.DATA("DB-Name", "Plan_Kosten", !'Measures', "Produktumsätze je Monat", !'Jahr') False "DB-Name", "Plan_Kosten", !'Projekt', !'Produkte', !'Ressourcen', !'Months')

if i press "Check", it says, that there are too many arguments. even if i try Palo.SetData(Palo.Data()) he says that there are too many arguments. the rule pala.setdata is not in the list of rules...

what's wrong with my code?
Cheers,
Mathias

Master Student Controlling & IT: Leuphana University Lueneburg (Germany)

holger_b

Sage

  • "holger_b" is male

Posts: 271

Date of registration: Jun 1st 2010

Location: Freiburg, Germany

Occupation: BI Consultant

  • Send private message

8

Thursday, July 22nd 2010, 7:10pm

Yes, that won't work: Either a rule, or SETDATA(). SETDATA actually writes a value into a cell, you can use it in a spreadsheet for example. A rule however only shows a value in a cell which is not physically there. Therefore SETDATA can not be used in rules. Your rule should start with PALO.DATA(...

I guess it is a good idea to take some time and read through the manual to understand the concept of rules, things will be easier afterwards very probably.

Regards
Holger
Rate this thread