Restriction of Overlapping of the periods in Planning Book

Question

Hi Experts
Currently we are using monthly planning for future horizon of 12 months,We want to replace monthly level planning to the weekly level.
I am worried about the time buckets in the planning book, we cannot determine the exact forecast quantity  of the particular month when week is shared between the two months since overlapping of the time period happens.
When i use Weekly Time buckets:
Planning book appears like: wk1.2011-wk2.2011-wk3.2011-wk4.2011-wk5.2011-wk6.2011-wk7.2011-wk8.2011-w9.2011-wk10.2011
T
In the above time buckets represents the following from date to to date:
wk1.2011 = 03.01.2011-09.01.2011
wk2.2011 = 10.01.2011-16.01.2011
wk3.2011 = 17.01.2011-23.01.2011
wk4.2011 = 24.01.2011-30.01.2011
wk5.2011 = 31.01.2011-06.02.2011
wk6.2011 = 07.02.2011-13.02.2011
wk7.2011 = 14.02.2011-20.02.2011
wk8.2011 = 21.02.2011-27.02.2011
wk9.2011 = 28.02.2011-06.03.2011
wk10.2011 = 07.03.2011-13.03.2011
WK5.2011 is sharing between the Jan 2011 and Feb 2011
WK9.2011 is sharing between the Feb 2011 and Mar 2011
But my customer requirment is as follows:
03.01.2011-09.01.2011/10.01.2011-16.01.2011/17.01.2011-23.01.2011/24.01.2011-30.01.2011/31.01.2011-31.01.2011/01.02.2011-06.02.2011/07.02.2011-13.02.2011/14.02.2011-20.02.2011/21.02.2011-27.02.2011/28.02.2011-28.02.2011/01.03.2011-06.03.2011/07.03.2011-13.03.2011
If the week is sharing between the two months, there should be two columns to separate the week by month days.
How to achieve this ?
Thanks
Kanth

Answer 1

Thomas
Respectfully disagree that Days is necessarily required in the storage bucket profile. Even without Days, as long as both Week and Month are selected, the system will automatically split quantities into technical periods and allow planning books to display data by week or month (But not day).
From SAP Help :
You select the periodicities month and week in the storage buckets profile.Data for the months of June and July 2001 is stored in the following buckets, also known as technical periods.
June 1-3               3 days
June 4-10             7 days
June 11-17           7 days
June 18-24           7 days
June 25-30           6 days
July 1                   1 day
July 2-8                7 days
July 9-15             7 days
July 16-22            7 days
July 23-29            7 days
July 30-31            2 days
Of course, it would work if days is included as well, but it would unneccarily increase Livecache Sizing requirements. Again from SAP Help:
Include in the storage buckets profile only the periodicities you need because the technical periods take up storage space. On the other hand, you must include all the periodicities in which you intend to plan.
Rishi Menon