CAPEX

[Former Member]

Hi,

For Fixed Asset Planning, how do we design the rate to maintain the asset price? do we maintain it as properties in asset or create another model to store the asset price?

Thanks in advance.

[former_member623827 · Accepted solution]

Hi,

Usually we maintain the rate in same model where capex planning is done.

You can use the new dimension called Key figure with which you can bifurcate values amongst Qty and rate of Assets.Further you can use the required values for directly for reporting  purpose or calculation.

As per my understanding separate model is notadvisable for this requirement.

Regards

Harpreetsingh Wasu

[Former Member · Accepted solution]

Hi Wasu,

If we maintain the rate in the same model using a Key Figure Dimension, then we need to have Logic script to duplicate the rate into different month and different entity ,rite?

Thank you

[Shrikant_Jadhav · Accepted solution]

Hi,

The idea of having key figure dimension is major call regarding requirement and design.

To simplify work and design , maintain rates in single model without key figure dimension.

Create one statistical account and maintain rates of assets. To perform calculation refer that rate.

Can you explain your requirement in detail ?

Shrikant 

[Former Member · Accepted solution]

Hi Shrikant,

Thank you for your reply.

The requirement will be to have GL account (which some of them will represent Asset type) and then the detail by Asset Number.

So in the data input template to maintain the Asset Rate will be:

Row Axis : GL account and Asset Number

Column Axis : Rate.

If the rate is maintained as statistical account, is the above scenario possible? Can we put GL account in Row Axis and Column Axis at the same time?

Thanks

[Shrikant_Jadhav · Accepted solution]

Hi,

Are the "Asset type " GL accounts are base level ?

We have gone through the same situation, In our case asset type was parent node, we have created dummy inputable accounts and in Audit trail dimension, we have created new member as "ASSET_RATE"

Then in combination of account and audit trail we have managed it.

But it's totally depends on overall requirement and solution.

Shrikant 

[Former Member · Accepted solution]

Hi Shrikant,

Thank you so much for the sharing.

In my case, the asset type is GL accounts base level.

Is there any significant differences if we create the Asset_Rate member in Audit Trail dimension compared to create it in new dimension (for example Key Figure dimension)?

Furthermore, how do you define the quantity? (in my case, the asset quantity need to be multiplied with the asset rate). Do you define it as member in the audit trail dimension too?

[Former Member · Accepted solution]

Are you the solution architect for the project?

There are many ways to do the rate and there are so many factors to consider.

how it is loaded or maintained, which level do you want to capture rate. and now you talking about asset quantity.

you can consider comments, extra dimension or new member in the existing dimension.

It all depends where do you want to use the rate, and how to use it.

Andy

[Shrikant_Jadhav · Accepted solution]

Hi ,

Already suggested in previous comments it's totally depends on requirement, it's not simple question answer , like whether we add new dimension or leverage existing one. Definitely adding dimension is big discussion and impact on system performance , maintenance but if it is required then no other option.

Shrikant    

[Shrikant_Jadhav]

This message was moderated.

[Former Member]

Hi,

it depends on your overall solution, you can create global members in the same model to store those rates, or you can create a special rate model to store them, or use properties.

It all depends how and where you want to use those rates, same may be easier to access, and some may not.

Andy