Profitability and Cost Management

Get Involved. Join the Conversation.

Topic

    Ayeshan Peiris
    Allocation target members
    Topic posted August 19, 2018 by Ayeshan PeirisSilver Medal: 2,000+ Points, tagged Allocations 
    140 Views, 10 Comments
    Title:
    Allocation target members
    Content:

    Hi All,

    I have defined two dimensions within PCM, Account and Entity (Cost Center). When defining allocation rules, in the target, I decided not to select the option "Same as Source for Entity member and I gave different destination cost center instead. I did this because merely for ease of my reporting purpose. To me, It seems funds flow is interrupted here.(Allocation out is from one cost center and Allocation in is for Another cost center, but account member it is same.)what are the implications of doing that. is this a best practice?

    Thanks

    Comment

     

    • Erik De Rouck

      There are a couple of things that impact the design setup of your allocations. First and most important is the output: you should obtain what you need for your reporting. Or in case the data analysis is also done in another system, you should have enough data detail available to successfully load the data in that other system. Secondly keep an eye on your volumes of data. PCM is a layered allocation system, so an additional allocation could use all prior allocated data. Meaning that design decisions could have a exponential impact on data. Otherwise said, if you will never do an analysis on detailed GL accounts, then you could build an allocation that distributes your cost accounts in the necessary cost account "buckets" (or even more simple, do this during the import upfront). From the calculation speed point of view, putting the "Same as source" option is faster (but potentially creates more data).

      Hope this helps

      Erik

       

      • Ayeshan Peiris

        Hi Erick,

        Thanks for the detailed explanation. Suppose I need to classify some accounts and cost centers and get a specific amount of source value (from both cost center and account POV ) and distribute that value across some routes (Airline related).In that case it seems to me I have two options.

        1.Structure the account and entity dimension according to my classification and produce the source value and then allocate using a allocation rule.

        2.I'm not going to structure any dimension, I'm going to create a custom calculation rule to produce the source value and then build a allocation rule to allocate values. (In this case 2 Rules)

        Which is the best method, you recommends.Please explain.

        Thank You.

         

        • Ayeshan Peiris

          Hi Erick,

          Thanks for the detailed explanation. Suppose I need to classify some accounts and cost centers and get a specific amount of source value (from both cost center and account POV ) and distribute that value across some routes (Airline related).In that case it seems to me I have two options.

          1.Structure the account and entity dimension according to my classification and produce the source value and then allocate using a allocation rule.

          2.I'm not going to structure any dimension, I'm going to create a custom calculation rule to produce the source value and then build a allocation rule to allocate values. (In this case 2 Rules)

          Which is the best method, you recommends.Please explain.

          Thank You.

    • Erik De Rouck

      It's difficult to give a fits-all answer. It looks like you first need to assemble up the context on the source side to have the right value ready for allocation. Investigate first the possibility of using UDA's (flags on members that can be used to filter) and standard allocations to build up the right costpools. In the interest of the client, try to avoid custom allocations as long as possible. 

      Succes

      Erik

       

      • Ayeshan Peiris

        Hi Erik,

        Yes.I was trying to have the right value ready for allocation. As you mentioned I have used UDA's for reporting purpose. But It seems there is no way to bring UDA Flagged member into a allocation rule or custom calc rule.is there anyway to do that? (Is it possible with filter functionality in rules?)

        Thank You

    • Erik De Rouck

      Yes, it's possible to use UDA's in PCM. Check the screenshot from on-premise version 11.1.2.4. Check the allocation setup, at the bottom of the source definition you will a filter option.

      Rgds

      Erik

       

    • Don Bean

      Ayeshan;

      Make sure you have defined some UDAs on the members in the dimension you are trying to filter.  The UI will not show UDA or Attribute as a filtering option if there are no UDAs or Attributes defined for the dimension.