About rob_marshall

@praba71 ,   Why are you daisy-chaining the calculation, just use comp_reservation_details.Organaization Code as the second parameter.     ... View more

@MarkTurkenburg  in that module, go to the blueprint, click on the Edit menu (I think), go down the Version Formula.  In that module, you have a formula just for version Forecast.   Rob ... View more

@Misbah ,   It can be done with filters, but you are also correct it can be done using effective dating, it depends on the use can and what is moving as in what level.  If you want to use filters it can be done in the below manner:   I have a hierarchy that is theoretically 9 levels deep, L1->L9, but in this case, I want my hierarchy to stop at L8 and then by "L9" is actually all detailed members in a flat list.       Create a module (Assigning Parent) that is dimensionalized by L9 Flat and Time as this will show the "movement" of the L9 member.  In this module, I have two input line items, Parent and Data.     In a 2nd module, I have what could be a fairly large module which is dimensionalized by L8, L9 Flat, and Time with the following line items: Data: Assigning Parent.Data Filter?: CODE(ITEM('CC L8')) = Assigning Parent.Parent Code   Note, if this was done according to best practice, I would have created the code in a SYS L8 Properties module instead of doing the code here and just referenced that line item.  Reason being, "figuring" out the code of L8 as I have it is actually over dimensionalized as the code of L8 will not change over time nor CC L9 Flat.       Create a 3rd module named Time Dependent - Summary dimensionalized by CC L8 and Time with one line item Data. Data= Assigning Parent.Data[SUM: Assigning Parent.Parent]     Now on the old UI, you can publish the all three   On the Time Dependent Data module, create a view based on Filter?     So now, the only data that will be shown and calculated will be based on the "input" of the parent information entered in the Assigning Parent module.   So, what is so slick about this, there are no actions created at all, just filtering on data that has been entered as the "parent".  This won't work for every instance of effective dating, but it will work on most.   You can then get "fancy" and create an action at the beginning of the month to copy the previous months assignments to the new month, and then if there are changes, you just modify the changes.     So after I run it:   Hope this helps,   Rob ... View more

@debbie5154 ,   I think I get it.  First, I would not add a SKU line item in the source with Time as SKU will not be changing over time, so it is wasting space.  So, in the source, say your code or unique list is 100_200_300_400 where one of those is SKU.  Dimensionalize this by time, at the week level which is what i think you have.   Then, create a module by SKU and time, still at the week level and this is where you do the sum (data[sum:target module.SKU]).  Now, for the target, you can create a module dimensionalized by SKU at the day level, and you can do a lookup using a SYS Time Filter module dimensionalized by Day with a line item showing the week (SKU.Data[lookup:SYS Time Filter Day.Current Week]) where current week is the line item in the SYS Time module.   Hopefully that makes since, if not I can put some pictures together to help here.   Rob ... View more

@MarkTurkenburg ,   Hopefully the below helps...Essentially, it is using the summary method of Ratio (instead of Sum, Max, etc.)   ... View more