Ok, I've built it anyway to make sure everyone is helped out on this topic. Again would not say that this is best practice: First you need to create a time range just for this purpose. I've put it to 1 period (1 year) in the year 2030, any year will do. This will allow your calculation module (mentioned later) to have 365 intersects if you put it to 'days' or 12 if you put it to 'months'. If you need something in between or more then of course you can extend the period. The first module you need is one that creates all the intersects you need, in my case between product and month, I called it the hierarchy combination module: Import this filtered view into your combined hierarchy list, in my case called "Product - Month',. with Order as property. Now create your "Final Module" the one that takes user input, in my case directly, of course you can apply formulas there as well. Pay special attention to the 'Date mapping' field, that will be useful later: DATE(2030, 1, 1) + 'Product - Month'.Order - 1 . Minus 1 so that we start at the first date, 2030-1-1 was the first date of my time range. If you have set the period to months, then this field should not be date, but time period month and the formula should be PERIOD(DATE(2030, 1, 1)) + 'Product - Month'.Order - 1. In your case the formulas for Good Book and Good Book closing receivables should still be empty. The next step is to create a calculation module that uses the time range. You could for size reasons only include the first and the last item (with the last item doing all the "SUM: Final Module.Date Mapping" that happen above), but to keep it as simple as possible, I chose to create every line item seperately. Finally add the two formula's in the final module that reference to Good Book and Good Book after closing receivables with a lookup on the Date Mapping. I hope that clarifies it. KR, Bram Kurstjens
... View more
