Does anyone know if it's possible to version the allocation strategies in Cost Transparency?

Unrealistic but illustrative example: 2018 I have a strategy that says Drive cost from Cost Source to Fixed Assets where Is Depreciation = Yes.

Can I change that in 2019 to be Drive cost from Cost Source to Fixed Assets where Is Depreciation = No without altering 2018 which has been locked?

I wonder if you can add a row filter in the "To Fixed Asset Ledger" section of the Cost Source allocation. One that puts a date condition on the allocation.  You might need to separate allocation going to the fixed asset ledger. One that drives the 2018 cost with a date filter and one that drives the 2019 cost with a date filter. Does that make sense?

I agree with what @Jason Tuckeris suggesting here.

The way I would tackle this is by adding some helper columns to the Cost Source Master Data including:

• Current Year = CurrentYear()
• Allocate to Fixed Asset Ledger = if(Depreciation=No AND Current Year>2018,"Yes","No")

You can then configure your allocation rules to evaluate the "Allocate to Fixed Asset Ledger" column to route your costs to Fixed Asset Ledger if it meets the criteria.

(For R12) In the top banner, you can click "Create version" while you are on the cost source object. Once you have done that, you can change any allocation strategy you want and only months going forward will be impacted, not months behind (if you want it to be all of 2019, make sure to create version in Jan 2019).

For R11, it has been awhile since i used it but i believe you must version the entire model, not just the object.

@Travis Cole if I 'create version' does that have any impact on reporting functionality? (e.g. KPIs ability to reference previous period, previous YTD, etc.)

I have created multiple versions, the only impact i have noticed is if you want to go back and change how that object behaved since the beginning of time, you would have to make the change after each version (multiple times), so there should be no impact.

I would recommend trying the formula for this particular exercise like @Kyle Castro mentioned above before using versioning, as it may end up being a cleaner implementation of this.