Leap year in IBP

[former_member657638]

Dear IBP experts

Next year (2020) will be a 'leap year', so 29/02/2020 is an 'extra date' in our planning level in days. We are using attribute transformations to shift our actuals one year (+365 days). As a result of this, after 29/02/2020, the numbers are not correct anymore. It means 01/03/2019 is shifted on to 29/02/2020, 02/03/2019 into 01/03/2020 and so on. When looking at monthly buckets, as most of our planners do, this gives a wrong view.

How can we handle with this? Working with a shift on week levels is not possible as the days are always different within a weeknumber and working with month levels is also impossible because we will than loose the detail on day level (which is necessary for our planning community).

In fact we just want to ignore the 29/02/2020 date. Is that possible somehow?

[piyush_parekh · Accepted solution]

Hi Kristoff,

You need to offset time periods by 366 for the range 01/03/2019 till 29/02/2020 (also applicable for subsequent leap years) and for remaining periods by 365. For this, add an integer-type attribute (say, LEAP) in your time profile and maintain value as 1 for the above mentioned periods. In planning level of Actuals Qty and Actuals Qty offset key figures, add this attribute in time profile section. Also, you need to add this attribute in period offset definition as follows:

PERIODID0@DAYPRODLOCCUSTOFFSET = PERIODID0 + 365 + LEAP

This will offset your data by 366 days for above mentioned period and by 365 days for rest of the periods. You also need to make sure that no data will be loaded for period 29/02/2020. If it happens, sum of values in 29/02/2020 and 01/03/2020 will start reflecting in 01/03/2021. You also need to add this attribute in other planning levels containing same set of root attributes as that of DAYPRODLOCCUSTOFFSET because of new checks introduced by SAP in 1905 upgrade.

If you are in design phase, you may as well consider removing leap period ID from time profile records itself and re-design the time profile.

Hope this helps!!

Regards,

Piyush