Week numbers are often used in calendars, although not as commonly in some countries as in others. In northern Europe, it is very common to refer to a week by its number, but in many other countries it is not used at all. Just as with the week start, week numbers are defined differently depending on country, so you may need to add code in QlikView to generate your own week numbers.
So, how do you count the weeks? Is Jan 1st always part of week one? Not necessarily.
If week 53 starts as late as Dec 28th, does Jan 1st also belong to week 53? Sometimes, yes.
There is a definition made by the International Organization for Standardization (ISO 8601) that QlikView uses to calculate week numbers. It states that
The week starts on a Monday.
A week is always unbroken. I.e. some years week 1 starts already in December, and in other years week 52 or 53 continues into January.
Week 1 always contains Jan 4th. Or, differently put: Week 1 always has at least 4 days in January. A third way to say the same thing is: The first Thursday of the year always lies in week 1.
These three bullets define the three parameters you need to define general week numbers:
SetvCal_FD = 0; // First Day of the week {0=Mon, 1=Tue, ... , 6=Sun} SetvCal_BW = 0; // Broken Weeks allowed {0=No, 1=Yes} SetvCal_RD = 4; // Reference day = This day in Jan defines week one {1..7}
How the week start - the first parameter - influences the week number can be seen in the following table. It shows how the week number would change for the days around New Year 2013 if different week starts are used. The other parameters are kept constant.
The second parameter concerns whether or not broken weeks should be used. If they are, a new week number will always be used on Jan 1st, and as a consequence the first and last weeks of the year can have less than 7 days.
And finally, the third parameter, the reference day. It defines which day that always belongs to week 1. In the table below, the reference day is 4; hence Jan 4th always belongs to week 1, which can be clearly seen. This number also defines the minimal number of days of week 1 that fall in the new year.
The ISO standard is thus a 0/0/4 week numbering. In countries where Sunday is used as first day of the week, I have seen several different variants: 6/1/1, 6/0/3 and 6/0/4.
If you copy the above parameters to your QlikView script and the following lines to your Master Calendar definition, you can redefine the week numbers any way you want:
The fields WeekYearRefDate (Jan 4th in the ISO definition) and WeekRefDate (the Thursday of the week in the ISO definition) are really not necessary, but the expressions become somewhat simpler if these are used.
Until we get a general week numbering functionality built into the QlikView standard functions (and, yes, we are looking into this) you will have to redefine the week numbers using the above script. Good luck!
And what about if my company needs week 1 to start on Thu. 01/01/2015, week 2 to to start on Mo. 12/01/2015, week 3 on Mo. 19/01 and so on — i.e. week 1 lasts 11 days?
Is it something I can get tweaking these parameters?
The default behaviour is to have Monday as the first day of the week. Further, week one is by default defined as the week that contains Jan 4th. So your case should work straight off.
However, this definition means that week one some years starts already in December. If you don't want this behaviour you need to ask yourself what you want instead. One possibility is that week one should start the first Monday of the year. In other words: Week one always contains Jan 7th. Then you should use
SetvCal_FD = 0; // First Day of the week {0=Mon, 1=Tue, ... , 6=Sun}
I've used your calendar script and its working fine for 2016 & 2017 but 2018 week1 not working as expected out (iso week1: 1st jan'18 to 6th jan 18 instead of 1-jan-18 to 7-jan-18 ).
here below is the ISO week format expected week 2018 (week 1 starts from 1-jan-18 to 7-jan-18)