Rule: transfer data from input line

[cfm04]

Hi all,
I'm trying to rework some of the existing part of my model.

One thing is I want to write a rule which transfer data from an input line to the specific dataline.
The user first sekect costcenter and some other data which will be stored in the cube as a string.
After all necessary selections are made he will input quanities. those will be stored in a dummy costcenter.

Now I want to write a rule which reads the dummy costcenter for the inputs and writes those to the previous chosen costcenters.

Code: Select all

['Quantity','1999'] = N:DB('Employee',
			!ID,
			!Month,
			!Year, 
			DB('Employee',!ID,!Month,!Year,'Cost Center Total',!CostUnit,!Version,'IN_CostCenter'),
			!CostUnit,
			'FC_M08',
			DB('Employee',!ID,!Month,!Year,'KST_BFC',!CostUnit,'FC_M08','Quantity'));

What I don't get now is. Do I need to write on the right side of the rule the specific costcenter? Using the DB funtion on the right side didn't seem to work for me.

What is the best practice for userinputs in a cube? I thought having them input all data on the dummy elements and then moving the data to the selected items would be a good idea.

Any help is appreciated.

[Duncan P]

Have a look at this thread and see if it is any help.

[Steve Rowe]

Hello cfm04

Personally for me this isn't worth the extra effort. If the user is
1. Selecting a cost centre on the input sheet
2. Storing that in a cube.
3. Then inputting a value to a cube.
4. Ruling the value input in 3 from steps to 1+2 into another cube

Given you already know the cost centre from step 1 why not write the value directly to the target cube and skip steps 2 and 4? Seems it a bit over complicated to me.

Also I can see from your rules that you are using the same cube to hold the cost centre and your input data and your ruled data, so you are not gaining any advantage from the user inputting the cost centre at the frequency which it changes (maybe, obviously I don't know anything about your requirements).

I'd also think you were bound to end up over feeding your rules with this approach.

In terms of checking what is going wrong with your rule. Standard practice for reviewing this type of issue (assuming the rule compiles).

1.Navigate to the N level on _all_ dimensions of the cube, keeping the scope narrow so you can turn zero suppression off.
2.Turn zero suppression off and find the suspect cell
3.1 If there is a value there then your rule is working but your feeder isn't so navigate to the feeder source at the N level and do a trace feeder and see what is going on.
3.2 If the value is zero (and grey) then your rule isn't working, right click and rule trace and find out what is wrong.
3.3 If the value is zero and white then your rule is against the wrong cube area or you have navigated to the wrong location.

These steps should get you a long way to resolving any rule / feeder issue
HTH
Cheers,