Skip to main content
Hi Tarjei,
What is the purpose of the module? Is it an output Module that is based on a secondary time series that rolling up data ie. Monthly to Quarterly/Semi-Annual/Annual. Are you preparing a separately module on a wholly separate primary periodicity?
If it is the latter, in my experience, it is often easier (and cleaner) to start from scratch given two differing time series will likely have separate logic behind it.
Hope that helps.
Cheers,
Hi Tarjei/Jun,
In many cases I agree with Jun - i.e. the logic can be so different that it can sometimes be dangerous to try to convert a module from one time series to another. An example of this is GST, where annual GST cash payment timing is relatively simple compared with monthly, which can get extremely complicated due to different payment options, etc.
Having said that, there are cases in which the content within a module is very similar across different time series periodicities and time frames. Obvious examples include financial statements (e.g. income statement, balance sheet, cash flow statement, etc.) and basic operational modules such as Revenue (Amounts) and Cost of Goods Sold (Margins). In these cases I've often used a simply trick to do this, which can be demonstrated by the following steps used to convert an annual Revenue (Amounts) module to a monthly Revenue (Amounts) module:
This approach has the benefit of capturing all Excel-based data within the original module, such as module links, row grouping, etc. The downside of it is that it's a bit messy and you will need to re-enter all the properties of the new monthly module from scratch. In the case of modules with only one module component - such as an income statement - it's usually the best approach because it's a single entire row copy and paste without any hyperlinks or inter-component formulas to break.
The other common approach is to edit the time series module of the existing annual module so that it becomes monthly, which can be done with the assistance of the Time Series Module Conflicts Identifier tool. It's often a line call as to which approach is the best, something which I decide on a module-by-module basis.
Hope this helps!
Hi Michael,
Very useful approach, will be sure to try it shortly!
Cheers,
Thank Michael - That is a really neat trick!