Skip to main content

The last day of February is the 29th for year 2020.  Because of this, IFS Support normally sees several cases logged for an incorrect valid to date, in Statistical Periods. 

All too often, the customer runs statistics (a.k.a. Aggregate Inventory Transaction Per Period), for the period.  They get a background job error, indicating an incorrect valid to date is entered.  They navigate to Statistical Periods, and try to change the valid to date.  Unfortunately, at this point it is too late.  Once statistics are run for the period, the dates cannot be changed.  That is why it is so important to check your periods now (before February). 

At this point the only way to correct the date, is via a billable data repair script. To avoid this type of situation, please check your February 2020 Periods.  Make sure the end date/valid to date is set to February 29, 2020. 

 

Many thanks for this!!!

Do you have a proposed “check-list” for what to change or check in IFS?

@MattiasLindahl Just check this page in IFS:

 

Thanks Janet!

RnD Solution 192591 had the script attached to it. Also has some instructions.

(More info on solution 265461) 

Hi @AsankaGaru I’m not able to find those solutions (192591 or 265461) when I search the support center.  Any chance of getting that script here?

 

Thanks!

@ProThushA  This might help you with your other query.

To be proactive, it is better to ask your customers to key in periods for the following years well in advance in the statistics period screen. (applicable for leap year and non leap year as well)

Customers tend to forget when the year changes and that they need to update the above screen. e.g. if they have data in the above screen up to 12/31/2021 and new transactions come in on 1/1/2022 and they forget to update the above screen to include new period ranges, it could cause serious problems and could need data repair to statistic_period_tab.

Reply


Terms & ConditionsCookie settings