The basic usage of tripping is it checks whether there are systematic deviations of demand history in the forecast for the current forecast model, meaning whether the forecast values are permanently above or below the values of the demand history. If this is the case, the system initializes the base values and the mean absolute deviation (MAD) for a location product, and restricts the number of historical periods that it uses for forecast calculation. The system can thus react to systematic changes in the demand history.
In case you run a tripping service for any location product , you can check the last tripping run date being updated in forecast(/SAPAPO/SPPFCST).
The date you notice there will be set to initial date of the month/period.
Example:You run tripping on 06 Sep 2016 & if you recheck in forecast the last tripping date is set to .
This is the standard behaviour.
The date is intentionally set to the first day of the current forecast period independent of when the run actually happened within that period.
The first day of the actual period is used because tripping is required only once in a period. If model or parameters are changed the date is set blank and rerun sets the date again.
It indicates tripping is completed.
Below snaphot shows the forecast screen with last tripping run date being updated to the initial day of the forecast period.