Is there a best practice way to remap line items between modules?
What I mean by this is taking a set of line items from a module and remapping them to another set of line items in a module, as per the screenshot below?
My use case for this would be to summarise P&L lines or to reclassify line P&L lines into a different format.
For my first attempt at this - I did the following.
To me this approach is OK - but not perfect. The most significant disadvantage is the fact that I effectively have to build the source P&L module twice - using up valuable model space. Once for the original source P&L module, and once again in the COLLECT() line item in the mapping module. This is because the COLLECT() line item is dimensioned in the exact same way as the as the source module. Unfortunately, I cannot remove the dimensionality from the COLLECT() line item as it is required to pull through my organisation list, LOB list, time, and version detail to my target P&L module.
What I like about this approach is the flexibility, line items can be remapped from a quick pick list, on the fly. It is also easy to ensure that all the line items from the source P&L module are being mapped somewhere (it is for this reason that I don't want to simply link the two modules via referencing the line items themselves. It is very easy to lose track of which line items in the source module have been referenced and which ones have not).
Any other ideas or thoughts on this would be fantastic - open to any suggestions.
Solved! Go to Solution.
That is the most commonly used approach to be honest for the reasons you gave and is much better than a series of IFs that we often see.
One question worth asking - Is is not possible to use two lists instead of line items? That would reduce the size concern. If the list is a simple aggregation, then it would work just fine
Have a "data" line item with a list for the P&L
You can use a "ragged" or "unbalanced" hierarchy; We advocate using composite or balanced hierarchies, but P&Ls and Chart of Accounts is one of the exceptions
As long as the line items are all numeric and the totals are a natural aggregation, the ragged hierarchy should still work
Regarding your Org not doing a straight sum, there is trick that you can utilize (using RATIO as the summary). Take a look at the below:
Create a Signage module:
Amend the summary option for the New Way line item to Ratio
Make sure for the Ratio piece, it is Temp New Way / Ratio New Way
***obviously, you can change the line item names, but I didn't want to confuse you or others with different names vs what are in my pictures.
Hope this helps,