feeding all elements from a single source.

[karan2345]

Hi Guys,

I have a Sales cube having the following dimensions
1.Sales Facility
2.Year
3.Month
4.Market Segment
5.Product line
6.Market
7.Item Sales Group
8.Scenario
9.Sales Measures

I am allowing the user to enter values on certain intersection , and then I am using these values to calculate the entire cube.

Code: Select all

['No Cust Class','No Product Line','None Market','No Item Sales Group','Budgeted','Amount']=STET;	

The user enters a total amount at the above specified cells and this value is used across all the elements.

Code: Select all

['Budgeted','Amount']=N:['No Cust Class','No Product Line','None Market','No Item Sales Group','Budgeted','Amount'];

My problem is writing feeders for the above rule

Code: Select all

FEEDERS;
['No Cust Class','No Product Line','None Market','No Item Sales Group','Budgeted','Amount']=>
DB('Sales Budgeting',!Sales Facility,!Year,!Months,!Market Segment,!Product Line,!Market,!Item Sales Group,!'Budgeted','Amount');

Is this the right way to deal with the above rules in writing feeders, Request some one to please help me on this.

[qml]

Try something like this:

Code: Select all

FEEDERS;
['No Cust Class','No Product Line','None Market','No Item Sales Group','Budgeted','Amount'] =>
DB('Sales Budgeting','Total Sales Facility','Total Year','Total Months','Total Market Segment','Total Product Line','Total Market','Total Item Sales Group','Budgeted','Amount');

Of course you will need the 'Total' elements in your dimensions.

And a warning - this cube looks like it will be big and slow if you do it that way. Skipcheck and feeders are only needed in case of any sparsity in the cube. Since it looks like you will be populating the whole cube using rules, you might as well get rid of skipcheck and feeders, keeping the same level of performance (which won't be great). And I don't really see why you would want to have that rule there in the first place. It doesn't look like a well thought through design to me, but then again, I haven't seen your requirements.

[karan2345]

Hi qml,

Thanks a lot for the reply, I have tried the feeder as suggested by you, however it takes hell lot of time to save the rule at the end I have to force shut the window.

Is there any other way that I can deal with.

Additionally If I dont use skipcheck and feeders the cube is running very slow.

Thanks once again.

[karan2345]

It doesn't look like a well thought through design to me, but then again, I haven't seen your requirements.

['No Cust Class','No Product Line','None Market','No Item Sales Group','Budgeted','Amount']
At this intersection the customer would be entering Budgeted amount at the overall level, basically here he is doing sales by month.
he wants the amount entered to be split across everything using the % of actuals.

[qml]

I have tried the feeder as suggested by you, however it takes hell lot of time to save the rule at the end I have to force shut the window.

Hopefully this will make you realise what you are trying to do. Yes, it takes a long time, because you're feeding a gazillion cells. But this is what you wanted, isn't it?

Is there any other way that I can deal with.

There are probably quite a few things you can do. But, of course, it all depends on the detailed requirements you have. For starters, I would consider keeping the budgeted amounts in a separate cube if they are meant to be the same for every product class, sales group, market etc. Then you could use references to this cube for any other measures you want to calculate on the basis of budgeted amount. But they could hopefully be fed from the Sales Budgeting cube.

Additionally If I dont use skipcheck and feeders the cube is running very slow.

Well, don't expect it to be any faster with skipcheck if all the cells are fed anyway.

[karan2345]

Hi qml,

Thanks for the suggestion, I would certainly try doing that way.

But they could hopefully be fed from the Sales Budgeting cube.

I am sorry I dint get what are you trying to say here.

Thanks once again.

[qml]

But they could hopefully be fed from the Sales Budgeting cube.

I am sorry I dint get what are you trying to say here.

I meant that even with a 2-cube design you could try and avoid intercube feeders and feed within the same cube. Not that it is the key issue, but it always makes life slightly easier.

[tomok]

The problem I see here, other than it's bad practice to just blindly spread budgeted input amounts along actuals, is that what you are saying and what your examples show are two different things.

The user enters a total amount at the above specified cells and this value is used across all the elements.

Code: Select all

['Budgeted','Amount']=N:['No Cust Class','No Product Line','None Market','No Item Sales Group','Budgeted','Amount'];

Where exactly is this value spread across all elements based on actual? All you are doing here is make every single Market Segment, Product Line, Market, and Item Sales Group equal to the amount entered in the
No Cust Class, No Product Line, None Market, No Item Sales Group elements. This is just making your total budget numbers invalid.

Assuming you wanted such a rule, it would look like this:

Code: Select all

['Budgeted','Amount']=N:
DB('Sales Budgeting',!Sales Facility,!Year,!Months,'No Cust Class','No Product Line','None Market','No Item Sales Group',!'Budgeted','Amount')*
DB('Sales Budgeting',!Sales Facility,!Year,!Months,!Market Segment,!Product Line,!Market,!Item Sales Group,'Actual','Amount')\
DB('Sales Budgeting',!Sales Facility,!Year,!Months,'Total Market Segment','Total Product Line','Total Market','Total Item Sales Group','Actual','Amount');

Other than just needlessly blowing out data for no good reason, you also have to realize that by doing this you can't budget in an account that doesn't have actuals because then the breakdown along actuals would not work. If that's OK then you can just use Actual to feed budget and forget about all our worries:

Code: Select all

FEEDERS;
['Actual']=>['Budget'];