Time series inconsistency due to change in Fiscal variant/Storage bucket

[Former Member]

Hi All,

We got into the situation where running time series consistency check on a DP planning area fails with the message pointing to, 'changes to Fiscal variant'. We are unable to track any changes to the fiscal variant though there is a possibility that storage bucket horizon could have been changed. Is there a way to correct/synch this by running a report?

We are trying to avoid re-initialization here, though this is an option, for the obvious reasons to backup the data in production. Is there an alternative solution to fix this inconsistency?

Cheers!

[Former Member]

Can you try running /SAPAPO/TS_LCM_CONS_CHECK with the repair option?

This will automtically correct the inconsistencies in the planning area.

Another option is to run /SAPAPO/TS_LCM_PLOB_DELTA_SYNC.

Please let us know if you still face issues so that we can help you more on this.

[Former Member]

Hi,

Thanks for your response and appreciate your time. We have already tried these options with no success. Looks like this kind of inconsistency with the storage bucket can not be repaired by the time series and PLOB consistency check reports.

There are some reports to synch the difference in planning bucket profile but I don't see a similar one for the storage bucket.

Regards

[former_member22474]

Dear Ashok,

You should never change a FYV when this FYV is used in a storage

bucket profile which is used in a planning area and if time series

objects are already created. It is no problem to maintain the FYV for

an additional time range, but changes and deletion of periods should

never be made if the FYV is actively used. You should not

change existing periods. If you want to make any changes to buckets

in your FYV or delete buckets, you should always make a COMPLETE

backup of ALL your data from the planning area into an InfoCube,

then delete the time series objects for the planning area (and with

this all the data in liveCache) and then change the FYV. After that,

you can create time series objects again and reload the data from the

Backup-InfoCube into the planning area. If you do these steps, you

will not risk to loose any data. The data in the InfoCube will be

the backup you can reload.

As some processes check the FYV some time before and after it is used,

it is very recommendable to maintain the FYV at least 2 - 3 years in

the past and in the future. E.g. if you create time series objects up

from 2001 you should maintain your FYV at least back to 1999 and if you

create time series objects until 2006, you should maintain your FYV

at least until 2008. It might be that you never experience problems if

you do not maintain the FYV in this time range, but some processes do

additional checks and then it can come to problems

Regards,

Rakesh