How to move anaplan model to the next FY and do not lose data

CommunityMember96369 · 2017-08-24T00:53:47+00:00

The Case: * Current Fiscal Year = FY17; * Some data is brought forwarded from Dec16; Option 1: Set new Current Fiscal Year + Increase Number of Past Years by 1 Option 1 results: * Original brought-forward value is still in place; * Original FY17 data is still in place; * New FY is added; * Module size is increased. Option…

CommunityMember96369

The Case:

Current Fiscal Year = FY17;
Some data is brought forwarded from Dec16;

The case.png

Option 1: Set new Current Fiscal Year + Increase Number of Past Years by 1

Option 1 results:

Original brought-forward value is still in place;
Original FY17 data is still in place;
New FY is added;
Module size is increased.

Option 1.png

Option 2: Adjust Current Fiscal Year settings

Option 2 resuls:

Original brought-forward value (Dec 16) is lost;
Original FY17 data is lost;
New FY is added;
Module size is same;
Dec17 value in line item with brought forward flag is equal to Dec17 value before time adjustment.

Option 2.png

If you have other ideas on how to move anaplan model to the next FY, please share in comments.

BR,

Igor

2017-08-23_How_to_move_to_next_FY_v1_22285.docx

Accepted answers

jdolich

Attaching a word document that shows how you might accomplish this, step by step.

I'm sure there's also a way you can make this work for version but I generally only use version for Actual/FCST and for saving off Original Plans and Last Projections (not for LY, LLY). It's too expensive on space.

ShiftingYearsInAnaplan_22294.docx

All comments

jdolich

Igor,

Could you export your plan data out of your model to Excel (or some other database), shift your years, then reimport your plan data back in to an historical module in you rmodel as LY or LLY? I'm sure you can automate this process too, possibly with actions. No loss of data that way and you would only import the line items you wanted to keep, reducing the space requirements and not requiring you to add a bunch of years in your model you don't really need.

jdolich

Attaching a word document that shows how you might accomplish this, step by step.

ShiftingYearsInAnaplan_22294.docx

CommunityMember96369

Thanks, both of your suggestions are good for moving to the next FY:

Separate line items for LY and LLY, especially useful for year-to-year variance analysis;
Action to move FY data to LY line item through 'temporary' module.

Unfortunately, this approach will not work, for example, for data to be forecasted by statistical tools. In such case it would be better to have all past period in one line item. That's why I actually wanted to show what goes on with model data after time adjustment is applied)

Quick Links

Can you help?

Unanswered questions

Request for Workflow Design: End-User Report Finalization & Stakeholder Notification with Version Co
Hi everyone, I'm looking to design a workflow and would appreciate your input or guidance on how to set this up effectively in Anaplan. So, the goal is: Once end users complete their data input, they should be able to trigger a process that: Notifies stakeholders via email with a link to a report. The report includes: A…
OAUTH 2.0 vs Google Sheets Extension
Hi, My org is looking to explore leveraging Google Apps script to extract data out of Anaplan and update already built templates in Google Sheets. We use the Anaplan Extension currently but find it crashes often with the amount of tabs, data, etc. Has anyone used both Anaplan OAUTH 2.0 API and Goolge Apps Script to write…
Exports with anaplan using informatica connector
I'm trying to execute an Action to export data with the use of a Mapping in Informatica. But it gives us null rows .If we export directly from Anaplan , the export file has all the rows filled. Both exports have same number of rows but in the informatica export the values appear as blank. This issue is with only some…