Policy overrides can be used to override an item policy, regardless of whether it was imported from the ERP system, specified in the app by a user or calculated by the app.
It is possible to specify a minimum and maximum number of safety stock days on the Policy overrides screen.
However, if the safety stock policy override does not apply to the selected items, it could be for one of these reasons:
A conflicting configuration setting exists
The Minimum safety stock days is in conflict with the Maximum safety stock days
A policy override with a higher sequence number has taken precedence
Let’s explore each of these reasons...
A conflicting configuration setting exists
Global rules can be specified on the Configuration screen.
A safety stock value of 0 will be applied to items with less sales per year than the specified value.
Changing the parameter value to 0 means every item that requires it, will have safety stock calculated, unless a policy override is in place.
The Minimum safety stock days is in conflict with the Maximum safety stock days
If the Minimum safety stock days is greater than the Maximum safety stock days, the Maximum safety stock days will take precedence, thus discarding the Minimum safety stock days constraint.
It is possible for the Minimum safety stock days to come from a different source than the Maximum safety stock days, including the configuration settings or a different policy override. It is therefore required to specify both the minimum and maximum values rather than just one of them, to reduce the chances of this conflict.
A policy override with a higher sequence number has taken precedence
Policy overrides will be applied in order from lowest sequence number, to largest. This means that if the safety stock value is specified for an item in more than one override, the override with the highest sequence number will take precedence.
NOTE: The above is applicable for all policy overrides, not just safety stock.
You might also be interested in searching the following: