04-22-2016 08:46 AM
04-22-2016 10:36 AM
I used this formula for my rule. Source.Cost<>0
The only caveat here is that this particular rule will also make assignment to accounts in the same module where there is no source cost. You would have to clean those assignments up if you have accounts with that state. If you would like me to dig deeper, please let me know. You can reach me at firstname.lastname@example.org
04-25-2016 08:58 AM
One of my colleagues had this in response to your question. And remember source.cost<>0 would be the module the account making the assignment in. Here is what my colleague said.
Whether this works or not will depend on whether he is using sequenced drivers. To work this driver would have to be at least sequence 2 as there will be no cost for sequence 1 until after a calc. If the rule is being used in the Resource module then you may be able to use EnteredCost instead but expect you will get the same result.
To designate the rule as only applying to this module you could use SOURCE.Module.DimMemberRef = destination.Module.dimmemberref (or of course not equal if it mustn’t go the same module).
04-27-2016 07:29 AM
On a difference subjuct, I have just posted the query below. Are you in a position to assist or would it go to another grouop? Thanks again for your assistance so far.
Long Calculation / Cube times
Recently calculation / cube processing times have increased 10 fold and I am trying to work towards a solution. I have sought out reported / unreported errors (e.g. circular account assignments , percentages exceeding / not equating to 100, invalid driver rules disabled / corrected / removed, OutputQtyUE not equal to 0, etc. I have also made reference values as short as possible to ensure intersections are as short as they can be. Can anyone suggest other actions that could be taken?
Need further help from the community? Please ask a new question.