Hello all,
In the previous article on history cleansing in SAP IBP Demand Planning, we have seen how we do use Substitute Missing Value Algorithm in detail. Well, there are two other algorithms that are also used often, i.e. Outlier Correction Algorithm and Promotion Sales Lift Elimination Algorithm. In this article, we are going to see how do these algorithms function.
We have already seen how we do create a forecast model in SAP IBP Fiori Launchpad using the Manage Forecast Model app/tile. So in this article, we will directly start by choosing an outlier correction algorithm and see what are the details we use and why we do use them. Here in the given image, we have selected outlier correction as our algorithm.
After selecting the outlier correction algorithm, we get the following tab where there are various fields that we are required to fill according to our business requirement. We will see these fields one by one.
There are two methods SAP has provided to find whether the given value is an outlier or not. These two methods are as follow.
An interquartile range test system checks whether the time series values are within the interquartile range, which is the difference between the third quartile and the first quartile of the data. The values that are not within this range are identified as outliers.
In statistics, the quartiles are the three values that divide the data into four equal groups, each group comprising 25% of observations from the data. The quartiles are determined as follows:
A multiplier is a decimal number by which the system multiplies the range of accepted values i.e. (Interquartile range in case of the interquartile range test method and standard deviation in case of variance test), thus including additional values in the range or excluding a set of values from it. The most commonly used multipliers are 1.5 and 3.
When we use 1.5 as a multiplier in our model then it forms an inner fence i.e. shorter tolerance lane and more outliers are detected which brings false results. To exclude the false outliers, we need to manually review the detections and for doing so there should not be any forecasting steps or post-processing steps involved in the model. Therefore, it is recommended that we should use 3 as a multiplier. By using 3 as a multiplier we get the outer fence i.e. wider tolerance lane. So only strong outliers are detected which are mostly correct so we don’t need to review them manually
Amol Khomne
SAP IBP Consultant, Baranwal Consultancy and Services (BCS), Pune, Maharashtra, India