Best Of

Try this:

MONTH(ITEM(Time)) = 1

@Mahdiyar

Something like this?

First, setup a SYS Time Year module dimensionalized by Time at the Year level. Create a line item called Multiplier where your first year is 1 and your second year is -1.

Here is the blueprint for the main module:

Formulas:

Desired Value: IF Value = 0 THEN 0 ELSE IF Value < OFFSET(Value, 12 * Multiplier, Value) THEN Value ELSE OFFSET(Value, 12 * Multiplier, Value)

Desired Text: IF Value <> 0 THEN "This is min value for " & Month Text ELSE BLANK

Month: NAME(ITEM(Time))…..Notice this is not dimensionalized by Products i the Applies To. In fact, you should really get this from a SYS Time Month module and can do away with this line item as long as you substitute SYS Time Month.Month where I referenced Month.

Month Text: IF Value < MOVINGSUM(Value, 12 * Multiplier, 12 * Multiplier) OR Value = Desired Value THEN Month ELSE MOVINGSUM(Month, 12 * Multiplier, 12 * Multiplier)

Multiplier: YEARVALUE(SYS Time Year.Mulltiplier)….Again, not dimenisionalized by Project, only Time.

Let me know how it goes,

Rob

@TristanS

At my finance company we do something similar. We have a bunch of contracts that we must put into different funding vehicles. Each vehicle has a lot of different constraints such as 25% of contracts can't be in Florida or no more than 10% of contracts can be longer than 12 months. We use anaplan for this. I will have to get back to you on specifics. We can't possibly run all the possibilities (we have 1,000s of contracts everyday). So what we do is we have the model spit out 3 different scenarios and we pick the one we like best. Hope that helps

Depends how you use them…
RANK and RANKCUMULATE are generally worse-performing because they have to be performed on a single CPU thread where other functions can benefit from parallel CPU execution.