Freezing of a Scenario in Costing Essentials

Hi

Thanks for the answer. I'll give some comments to the different perspectives and where I could see some challenges:

1. This could be possible, but I think the reporting will be very difficult to configure then. You want to have a freezed budget, but you want to be able to compare that to the actuals. If it is a snapshot in an entirely different environment, the reporting between budget and actuals would be quite difficult.

2. I think this perspective is quite good and would make sense. What is important to be aware of, is that it is not only the allocations that should be locked, but somewhat also some of the master data. 
Lets say you have a service that you are allocating based on headcount to the organizations. In the budget, you expected that there would be 200 employees. During the FY, the amount of employees increase to 300, but it is important that the budget still allocates, as if there is only 200 employees in the organization.

3. I think i need to understand this functionality a bit better. Would you then copy all tables with allocations related to the budget, and have that as a flat table, to show budget numbers across spend drivers, solutions and the consumers? This could probably also work as an easy fix, but I am afraid that the reporting between the "copied tables" and non-copied tables could cause some issues (there would no longer be a connection between the different models. As an example, how would the reporting show the solutions cost from different vendors, if it a copied table? I think it is important that this is still possible.

Let me know if we should take a call regarding this.

There are a few different ways we can accomplish your request. I'd like to better understand the desired process workflow.

1. Create a "Snapshot" Branch which will duplicate the project at that point in time and will not allow any changes to the project (no table uploads, no configuration changes). This would be a snapshot of the entire environment including Actuals and Budget.

2. Allow the project to continue to be updated from an Actuals perspective. This would include data as well as configuration changes. However, lock the Budget from ever changing. This may require the following: a) lock the Budget source data pipeline so a new version cannot be uploaded during the current fiscal year (new platform feature if done systematically); b) separate any budget-based model allocations so that changes can made in the Cost model allocations are independent of the budget allocations (this could be done with configuration changes to the model allocations where we may use the same in the current OOTB config). There is no way to "systematically" lock any changes being made to the Budget modeled metric.

3. Use CopyTable() to copy the modeled and calculated metrics for the Budget and saves it to a "flat file". This is what is commonly done for Chargeback to see a permanent view for each month.

Please let me know what specific option is more aligned with your expectations.

Thanks,

Ed

This is a feature that would need to be part of TBM Studio as opposed to a specific solution area.