Can't find Week 53 FY20 in Time Settings.

Hello All,

When Setting Calendar type as Weeks: 4-4-5 and setting for Current Period FY 2020( viz. a leap year). There is no option available for week 53 FY20.

Whereas the same is available for FY16 and FY22(which is not a leap year).

Week 53 missing in FY20

Week 53 in FY16

Week 53 in FY22

Am I missing something in the settings or is it a bug ?

Regards ,

Jitendra

Accepted answers

Misbah

@Jitendra.Vishnolia

Two things

1 Functionally Its not a disadvantage. There are pros and cons to each method. Companies do plan at a weekly level and their 364 days Year keeps on changing the start date and end date on a yearly basis. In today's world where strategic or operational decisions keep on changing based on the macro economic or micro economic factors you have to adapt to such conditions quickly. If you ask me I would say Planning at the month level is easy, less complicated but at the same time you lose the visibility on your numbers on a weekly basis, react to the market conditions fast (but not faster)and you plan at higher level whereas weekly is a little bit complicated but allows you to plan at more granular level and you react to market conditions faster.

2. Technically too it is not a disadvantage - You won't have to add it manually, Anaplan will figure it out on its own based on the settings that you have on Time Page. Left over day of Year 1 will be planned for in Next Year Week 1 , so everyday is getting included in the plan its just a matter of classification.

All comments

Misbah

@Jitendra.Vishnolia

First of all, 53rd week doesn't necessarily have to fall on Leap Years. It depends on company to company

In your case you have kept the setting in such a way that you are planning for 53rd Week in FY16 and from FY17 Onwards you will keep planning for 52 weeks until you cumulate another 7 days which will happen in FY22 and not FY21. Illustration as below

FY17 - 52 weeks =364 days, 1 day goes unplanned

FY18 - 52 weeks =364 days, 1 day goes unplanned

FY19 - 52 weeks =364 days, 1 day goes unplanned

FY20 - 52 weeks =364 days, 2 days go unplanned

FY21 - 52 weeks =364 days, 1 day goes unplanned

FY22 - 52 weeks =364 days, 1 day goes unplanned

So in FY22 you will have 53 weeks to plan for

Hope that makes sense

Misbah

Jitendra.Vishnolia

@Misbah :

In that case, don't you think it's a disadvantage of the 4–4–5 calendar is that it has only 364 days (7 days x 52 weeks), meaning a 53rd week will need to be added every five or six years(not necessarily a leap year as in my case here.).

Misbah

@Jitendra.Vishnolia

Two things

Jitendra.Vishnolia

Got it. Thanks for the detailed clarification @Misbah .

Quick Links

Can you help?

Unanswered questions

Introducing Anaplan API Python SDK
Hey everyone, I wanted to share the Anaplan Python SDK with you. It's a Python Library that wraps all Anaplan APIs and makes it easier to interact with Anaplan programmatically. It is mostly designed with Data Integration Scenarios in mind, but it does support all APIs including ALM, SCIM, Audit, and Cloud Works. Please…
Batch Script
Hello team, I am logging into Anaplan through SSO. I would like to create a batch script to import a file into Anaplan. For the Spoke model, I would like to run an process via a batch script to import data from the Data Hub. Can anyone provide me script for both the condition.
Cloudworks Big Query Integration Fail
Hello, I am receiving an 'Anaplan Upload Failed' Status Description when testing my integration with a Big Query dataset. The integration imports data from BQ to our Anaplan model. No other details given in the error log. I suspect that Cloudworks is not even picking up the file but am not sure what we did wrong on the set…