Can Switchover be used on a Daily basis?

neg177

Is it possible to do Switch over on a daily basis versus a monthly basis?

Accepted answers

JaredDolich

@neg177

Two approaches, both use DISCO, neither use switchover:

Use the native versions in one module (Module A). One for Actuals, one for Forecast. Add another module (Module that contains the current date. In Module A you'll add a line item that has this format: IF PERIOD(START()) >= Module B.Current Date THEN Sales[SELECT: versions.forecast] ELSE Sales[SELECT: version.actual]
Same as 1, except you'll denormalize the forecasts and actuals and create a separate line item for each instead of using the native versions. Your formula will look something like this: IF PERIOD(START()) >= Module B.Current Date THEN Sales Forecast ELSE Sales Actual

One nice thing about option 1 is that you can make the actuals read only and forecast editable using the feature to apply formula to a version.

All comments

JaredDolich

@neg177

Switchover will follow your model calendar. Lowest a model calendar can go is weeks.

To get switchover to daily, you'll most likely need to create a module to hold the current date. That can be automated, by the way using Anaplan Connect. Once you have the current date you can use formulas to determine the switchover. To be honest, this is the method I use because I don't want to have a casual Anaplan user have to become a workspace adminsitrator to change the switchover. Hope that helps!

neg177

Ok, What are other routes I can go with Forecasting? Can I have my Module with just Actuals and then a Module with just Forecast? Or would the Switchover be a better bet?

neg177

I guess the real question I'm trying to ask is what is the best technique to approach when Forecasting a Daily Model in Anaplan?

JaredDolich

@neg177

Two approaches, both use DISCO, neither use switchover:

Use the native versions in one module (Module A). One for Actuals, one for Forecast. Add another module (Module that contains the current date. In Module A you'll add a line item that has this format: IF PERIOD(START()) >= Module B.Current Date THEN Sales[SELECT: versions.forecast] ELSE Sales[SELECT: version.actual]
Same as 1, except you'll denormalize the forecasts and actuals and create a separate line item for each instead of using the native versions. Your formula will look something like this: IF PERIOD(START()) >= Module B.Current Date THEN Sales Forecast ELSE Sales Actual

One nice thing about option 1 is that you can make the actuals read only and forecast editable using the feature to apply formula to a version.

neg177

I'm going to give option 1 a try.

Thank you

JaredDolich

@neg177

Good choice! Good luck and let us know how it turns out. Anxious to hear.

neg177

In the formula IF PERIOD(START()) >= Module B.Current Date THEN Sales[SELECT: versions.forecast] ELSE Sales[SELECT: version.actual] , sales is referring to the line item I want to forecast?

JaredDolich

@neg177

Yes, that looks correct. Let me know if you need an example.

Quick Links

Can you help?

Unanswered questions

Moving Sum for Formula driven number format line items
I am trying to create a Net Debt / EBITDA formula at the bottom of one of our P&L income statements where, i have tried the MOVINGSUM function. However this does not work for summary line items which EBITDA is. What i would like is to be able to sum the previous 12 months EBITDA (Including the current period) numbers in a…
Docusign Integration
Hi I'm looking to speak to people who have used/are using the Docusign integration in their business. We are exploring the possibility, but we find the current setup quite limiting in terms of how an end user would interact with the integration, but also issues with concurrency and number field formats. Would appreciate…
A reminder of Bulk Copy - Current year to Prior year version for YoY analysis
A quick reminder of the Bulk Copy functionality. Bulk Copy allows you copy large volumes of data from one slice of a model to another in a single, optimised operation, instead of using formulas or imports. Use case: copy a version (RF1) into a prior year version (PY RF1) using a versions list to allow for year-on-year…