week 53 issue in 0calweek

 It wont as the occurence of a 53rd week is internationally standardized. The check in BW follows these international conventions which count the week depending on the majority of days:
- if the week has 4 days of the old year it counts as CW53;
- if it has 4 days of the new year it is CW1.

That is to say, the number of ISO weeks belonging to a year number is equal to the number of Thursdays in the correspondingly-numbered calendar year, and is equal to the week number of December 31st; and a year has 53 weeks if, and only if, the following day is in its Week 53.

The 53-week years in the range 2000-2027 are: 2004, 2009, 2015, 2020, 2026.
That pattern repeats every 28 years before 2100.

For 0CALWEEK, it will calculate the week based on the calendar you specified in tcode RSRHIERARCHYVIRT. Please note that RSRHIERARCHYVIRT is a BW global setting, i.e. that means the system will use this calendar for all data targets.
If you have some special business impact to include a 201153, please check the following:
1. write a routine in the transfer rules for 0CALWEEK that modifies into the week 201201.
2. manually correct the data in the PSA and load from PSA into the target cube.

Try the steps below, as the logic is:

=> weeks start on a Monday
=> create as week 53 if it starts on or before 27th Dec (ie. there are >= 4 days of that year in it) otherwise it becomes week 1 of the next year ie. week 1 can start in the “previous” year
=> Try to play with function module DATE_GET_WEEK