Oracle® Retail Advanced Inventory Planning Store and Warehouse Replenishment Planning User Guide for the RPAS Fusion Client Release 14.1 |
|
![]() Previous |
![]() Next |
This chapter describes the System Setup activity. These workbooks are used to manage thresholds for generating alerts for stores and warehouses.
The System Setup activity contains these tasks:
This task is used to set up the global (Sub-class/Company), default (SKU/Company), and exception (SKU/Store) values that are used to populate alert measures. Global measures are used when no default or exception value exits. The values set here define the thresholds and horizons used to generate alerts.
Use the SRP Alert Maintenance workbook to perform the steps for this task. To build this workbook, see "SRP Alert Maintenance Workbook".
These steps help you achieve this task:
This step contains a view that allow you to examine the global department level default values for parameters for store replenishment plans.
The available views are:
This view contains the global department level default values for parameters that are used in generating and processing store replenishment plans.
Table 10-1 lists the measures in this view.
Table 10-1 Measures: SRP Alert Default (SKU/Company) View
Measure Label | Description |
---|---|
Day on Day OOS Alerting Stores Ratio |
The Day on Day Alerting Stores Ratio defines the threshold for the ratio of ranged stores Out of Stock (OOS) on the same day in consecutive weeks to the total number of ranged stores. This parameter represents the percentage threshold that must be exceeded when considering the generation of a Day on Day Repeat Out of Stocks alert. Valid values are zero (0) through one (1). Example: To generate an alert when more than half of the ranged stores are out of stock on the same day in consecutive weeks; then in the Day on Day OOS Alerting Stores Ratio, enter: 0.5. |
Day on Day OOS Corp. Lost Sales Volume |
The Day on Day OOS Corp. Lost Sales Volume defines the threshold for the sum of lost sales for this SKU across ranged stores. This parameter represents the lost sales volume in units that must be exceeded when considering the generation of a Day on Day Repeat Out of Stocks alert. Any positive number, including zero, is valid. |
Day on Day OOS Day on Day Count Threshold |
The Day on Day OOS Day on Day Count Threshold defines the threshold for the number of days a product is out of stock at a store for that SKU/Store to be considered as an exception. This parameter represents the number of days a store must be out of stock on the same day in consecutive weeks that must be exceeded before the Day on Day Repeat Out of Stocks alert is triggered. Any positive integer, including zero, is valid. Example: To generate an alert when a SKU/Store is out of stock on the same day for the past three weeks; then in the Day on Day OOS Day on Day Count Threshold, enter: 3. |
High Proj Low Stock Alerting Stores Ratio |
The High Proj Low Stock Alerting Stores Ratio defines the threshold for the ratio of ranged stores with projected low stock to the total number of ranged stores. This parameter represents the percentage threshold that must be exceeded when considering the generation of High Projected Low Stocks alert. Valid values are zero (0) through one (1). Example: To generate an alert when more than half of the ranged stores have projected low stock, then in the High Proj Low Stock Alerting Stores Ratio, enter: 0.5. |
High Dissipation Yesterday % of Sales |
The High Dissipation Yesterday % of Sales defines the threshold used in the High Dissipation Yesterday alert calculation; it represents a percentage of dissipation compared to sales. Zero is not a valid value. Valid percentages are greater than zero (0). |
High Dissipation Yesterday Alerting Stores Ratio |
The High Dissipation Yesterday Alerting Stores Ratio defines the threshold used in the High Dissipation Yesterday alert calculation; it represents a percentage of High Dissipation stores (that are not High Repeat Dissipation Stores) that exceeded the High Dissipation % of sales ratio. Zero is not a valid value. Valid percentages are greater than zero (0). |
High Dissipation Yesterday Total % of Sales |
The High Dissipation Yesterday Total % of Sales defines the threshold used in the High Dissipation Yesterday alert calculation; it represents a percentage of total dissipation yesterday compared to total sales yesterday. Valid percentages are greater than zero (0). |
High Planned Orders Packs Threshold |
Threshold for High Planned Orders. It is the number of packs that a planned order quantity must not exceed. |
High Planned Orders Horizon |
The maximum number of days that are reviewed when scanning for order quantities that exceed the alerting threshold. |
High Proj OOS Alerting Stores Ratio |
The High Proj OOS Alerting Stores Ratio defines the threshold for the ratio of ranged stores with projected out of stocks to the total number of ranged stores. This parameter represents the percentage threshold that must be exceeded when considering the generation of High Projected Out of Stock alert. Valid values are zero (0) through one (1). Example: To generate an alert when more than half of the ranged stores have projected out of stocks; then in the High Proj OOS Alerting Stores Ratio, enter: 0.5. |
High Proj OOS Corp. Lost Sales % Forecast |
The High Proj OOS Corp. Lost Sales % Forecast defines the threshold for the ratio of projected lost sales for all stores over the horizon to demand forecast for all stores over the horizon. This parameter represents the percentage threshold that must be exceeded when considering the generation of High Projected Out of Stock alert. Valid values are zero (0) through one (1). Example: To generate an alert when the projected lost sales over the alert horizon are greater than 25% of the forecasted demand; then in The High Proj OOS Corp. Lost Sales % Forecast, enter: 0.25. |
High Proj OOS Corp. Lost Sales Volume over horizon |
The High Proj OOS Corp. Lost Sales parameter defines the threshold for the sum of projected lost sales across for this SKU across ranged stores. This parameter represents the corporate lost sales volume threshold in units that must be exceeded when considering the generation of High Projected Out of Stock alert. Any positive integer, including zero, is valid. |
Large Cons. OOS Alerting Stores Ratio |
The Large Cons. OOS Alerting Stores Ratio defines the threshold for the ratio of ranged stores OOS on consecutive days to the total number of ranged stores. This parameter represents the percentage threshold that must be exceeded when considering the generation of the Large Consecutive Out of Stocks alert. Valid values are zero (0) through one (1). Example: To generate an alert when more than 20% of the ranged stores were out of stock over; then in the Large Cons. OOS Alerting Stores Ratio defined number of consecutive days, enter: 0.2. |
Large Cons. OOS Corp. Lost Sales Volume over horizon |
The Large Cons. OOS Corp. Lost Sales Volume over horizon defines the threshold for the sum of lost sales for this SKU across ranged stores. This parameter represents the lost sales volume in units that must be exceeded when considering the generation of a Large Consecutive Out of Stocks alert.Any positive number, including zero, is valid. |
Large Non-Cons. OOS Alerting Stores Ratio |
The Large Non-Cons. OOS Alerting Stores Ratio defines the threshold for the ratio of ranged stores OOS on non-consecutive days to the total number of ranged stores. This parameter represents the percentage threshold that must be exceeded when considering the generation of the Large Non-Consecutive Out of Stocks alert. Valid values are zero (0) through one (1). Example: To generate an alert when more than 30% of the ranged stores were out of stock over the defined number of non-consecutive days; then in the Large Non-Cons. OOS Alerting Stores Ratio, enter: 0.3. |
High Repeated Dissipation % of Sales |
The High Repeated Dissipation % of Sales defines the threshold used in the High Repeated Dissipation alert calculation; it represents a percentage of dissipation compared to sales. Zero is not a valid value. Valid percentages are greater than zero (0). |
High Repeated Dissipation Alerting Stores Ratio |
The High Repeated Dissipation Alerting Stores Ratio defines the threshold used in the High Repeated Dissipation alert calculation; it represents a percent of stores with high dissipation over a significant number of days. Valid percentages are greater than zero (0). |
High Repeated Dissipation Days |
The High Repeated Dissipation Days defines the threshold used in the High Repeated Dissipation alert calculation; it represents the number of days that must exceed the Dissipation % of Sales threshold. Zero is not a valid value. Valid values are greater than zero (0). |
High Repeated Dissipation Horizon |
The High Repeated Dissipation Horizon defines the threshold used in the High Repeated Dissipation alert calculation; it represents the number of days to which the alert calculation is limited. The Dissipation Days threshold must be exceeded within this horizon. Zero is not a valid value. Valid values are greater than zero (0). |
Large Non-Cons. OOS Corp. Lost Sales Volume over horizon |
The Large Non-Cons. OOS Corp. Lost Sales Volume over horizon defines the threshold for the sum of lost sales for this SKU across ranged stores. This parameter represents the lost sales volume in units that must be exceeded when considering the generation of a Large Non-Consecutive Out of Stocks alert.Any positive number, including zero, is valid. |
Large OOS Last Night Alerting Stores Ratio |
The Large OOS Last Night Alerting Stores Ratio defines the threshold for the ratio of ranged stores OOS last night to the total number of ranged stores. This parameter represents the percentage threshold that must be exceeded when considering the generation of the Large Out of Stocks Last Night alert. Valid values are zero (0) through one (1). Example: To generate an alert when more than 40% of the ranged stores were out of stock last night; then in the Large OOS Last Night Alerting Stores Ratio, enter: 0.4. |
Large OOS Last Night Corp. Lost Sales % Possible Sales |
The Large OOS Last Night Corp. Lost Sales % Possible Sales parameter defines the threshold for the ratio of lost sales last night to demand last night. Note this ratio compares all stores for a SKU, not just those that were out of stock last night. This parameter represents the percentage threshold that must be exceeded when considering the generation of the Large Out of Stocks Last Night alert. Valid values are zero (0) through one (1). Example: To generate an alert when lost sales last night compared to possible sales last night (demand) were more than 20 %; then in the Large OOS Last Night Corp. Lost Sales % Possible Sales, enter: 0.2. |
Large OOS Last Night Corp. Lost Sales Volume |
The Large OOS Last Night Corp. Lost Sales Volume defines the threshold for the sum of lost sales last night for this SKU across ranged stores. This parameter represents the lost sales volume in units that must be exceeded when considering the generation of a Large Out of Stocks Last Night alert.Any positive number, including zero, is valid. |
This view contains the global Sub-class/Company level default values for parameters that are used in generating alerts.
Table 10-2 lists the measures in this view.
Table 10-2 Measures: SRP Alert Global Default (Sub-class/Company) View
Measure Label | Description |
---|---|
Day on Day OOS Def Alerting Stores Ratio |
The Day on Day Alerting Stores Ratio defines the threshold for the ratio of ranged stores Out of Stock (OOS) on the same day in consecutive weeks to the total number of ranged stores. This parameter represents the percentage threshold that must be exceeded when considering the generation of a Day on Day Repeat Out of Stocks alert. Valid values are zero (0) through one (1). Example: To generate an alert when more than half of the ranged stores are out of stock on the same day in consecutive weeks, then in the Day on Day OOS Alerting Stores Ratio, enter: 0.5. |
Day on Day OOS Def Corp. Lost Sales Volume |
The Day on Day OOS Corp. Lost Sales Volume defines the threshold for the sum of lost sales for this SKU across ranged stores. This parameter represents the lost sales volume in units that must be exceeded when considering the generation of a Day on Day Repeat Out of Stocks alert. Any positive number, including zero, is valid. |
Day on Day OOS Def Count Threshold |
The Day on Day OOS Count Threshold defines the threshold for the number of days a product is out of stock at a store for that SKU/Store to be considered as an exception. This parameter represents the number of days a store must be out of stock on the same day in consecutive weeks that must be exceeded before the Day on Day Repeat Out of Stocks alert is triggered. Any positive integer, including zero, is valid. Example: To generate an alert when a SKU/Store is out of stock on the same day for the past three weeks (21 days), then in Day on Day OOS Count Threshold, enter: 21. |
Day on Day OOS Def Horizon |
Day on Day OOS Horizon defines the number of days in history that are reviewed when considering the generation of a Day on Day Repeat Out of Stocks alert. Any positive integer, including zero, is valid. Example: To review three weeks (21 days) of history; then in Day on Day OOS Horizon, enter: 21. |
Def Stock Cover Days Threshold |
The Stock Cover Days Threshold defines the threshold in number of days of supply that must be exceeded when considering the generation of an Overstock alert. Any positive integer, including zero, is valid. Example: To generate an alert only when the existing inventory covers demand for two weeks (14 days) or more, then in the Stock Cover Days Threshold, enter: 14. |
High Dissipation Yesterday Def % of Sales |
The High Dissipation Yesterday Def % of Sales defines the default threshold used in the High Dissipation Yesterday alert calculation; it represents a percentage of dissipation compared to sales. Zero is not a valid value. Valid percentages are greater than zero (0). |
High Dissipation Yesterday Def Alerting Stores Ratio |
The High Dissipation Yesterday Def Alerting Stores Ratio defines the default threshold used in the High Dissipation Yesterday alert calculation; it represents a percentage of High Dissipation stores (that are not High Repeat Dissipation Stores) that exceed the High Dissipation % of sales ratio. Zero is not a valid value. Valid percentages are greater than zero (0). |
High Dissipation Yesterday Def Total % of Sales |
The High Dissipation Yesterday Def Total % of Sales defines the default threshold used in the High Dissipation Yesterday alert calculation; it represents a percentage of total dissipation yesterday compared to total sales yesterday.Valid percentages are greater than zero (0). |
High Planned Orders Def Packs Threshold |
Threshold for High Planned Orders. It is the number of packs that a planned order quantity must not exceed. |
High Planned Orders Def Horizon |
The maximum number of days that are reviewed when scanning for order quantities that exceed the alerting threshold. |
High Proj Low Stock Def Alerting Stores Ratio |
The High Proj Low Stock Alerting Stores Ratio defines the threshold for the ratio of ranged stores with projected low stock to the total number of ranged stores. This parameter represents the percentage threshold that must be exceeded when considering the generation of High Projected Low Stocks alert. Valid values are zero (0) through one (1). Example: To generate an alert when more than half of the ranged stores have projected low stock; then in the High Proj Low Stock Alerting Stores Ratio enter: 0.5. |
High Proj Low Stock Def Low Level Percentage |
The High Proj Low Stock Low Level Percentage defines the percentage below the RUTL that Projected Inventory must be when considering the generation of High Projected Low Stocks alert. Valid values are zero (0) through one (1). Example: To generate an alert if the Projected Inventory falls below 75% of the RUTL; then in the High Proj Low Stock Low Level Percentage, enter 0.75. |
High Proj Low Stock Def Number of Low Stock Days |
High Proj Low Stock Number of Low Stock Days defines the threshold for the number of days a product is projected low stock that must be exceeded before the High Projected Low Stocks alert is triggered. Any positive integer, including zero, is valid. Example: To generate an alert when a SKU/Store is projected low stock for 5 days; then in the High Proj Low Stock Number of Low Stock Days Threshold, enter: 5. |
High Proj OOS / Low Stock Def Horizon |
The High Proj OOS / Low Stock Horizon parameter defines the number of future days that are reviewed when considering the generation of a High Projected Low Stocks alert or a High Projected Out of Stock alert. Any positive integer, including zero, is valid. Example: To review two weeks (14 days) in the future; then in the High Proj OOS / Low Stock Horizon, enter: 14. |
High Proj OOS Def Alerting Stores Ratio |
The High Proj OOS Alerting Stores Ratio defines the threshold for the ratio of ranged stores with projected out of stocks to the total number of ranged stores. This parameter represents the percentage threshold that must be exceeded when considering the generation of High Projected Out of Stock alert. Valid values are zero (0) through one (1). Example: To generate an alert when more than half of the ranged stores have projected out of stocks; then in the High Proj OOS Alerting Stores Ratio, enter: 0.5. |
High Proj OOS Def Corp. Lost Sales % Forecast |
The High Proj OOS Corp. Lost Sales % Forecast defines the threshold for the ratio of projected lost sales for all stores over the horizon to demand forecast for all stores over the horizon. This parameter represents the percentage threshold that must be exceeded when considering the generation of High Projected Out of Stock alert. Valid values are zero (0) through one (1). Example: To generate an alert when the projected lost sales over the alert horizon are greater than 25% of the forecasted demand; then in The High Proj OOS Corp. Lost Sales % Forecast, enter: 0.25. |
High Proj OOS Def Corp. Lost Sales Volume over horizon |
The High Proj OOS Corp. Lost Sales parameter defines the threshold for the sum of projected lost sales across for this SKU across ranged stores. This parameter represents the corporate lost sales volume threshold in units that must be exceeded when considering the generation of High Projected Out of Stock alert. Any positive integer, including zero, is valid. |
High Proj OOS Def Number of Projected Days OOS |
The High Proj OOS Number of Projected Days OOS parameter defines the threshold for the number of days this product is projected out of stock that must be exceeded before the High Projected Out of Stock alert is triggered. Any positive integer, including zero, is valid. Example: To generate an alert when a SKU/Store is projected out of stock for 3 days; in the High Proj OOS Number of Projected Days OOS Threshold, enter 3. |
High Repeated Dissipation Def % of Sales |
The High Repeated Dissipation Def % of Sales defines the default threshold used in the High Repeated Dissipation alert calculation; it represents a percentage of dissipation compared to sales. Zero is not a valid value. Valid percentages are greater than zero (0). |
High Repeated Dissipation Def Alerting Store Ratio |
The High Repeated Dissipation Def Alerting Store Ratio defines the default threshold used in the High Repeated Dissipation alert calculation; it represents a percent of stores with high dissipation over a significant number of days. Valid percentages are greater than zero (0). |
High Repeated Dissipation Def Days |
The High Repeated Dissipation Def Days defines the default threshold used in the High Repeated Dissipation alert calculation; it represents the number of days that must exceed the Dissipation % of Sales threshold. Zero is not a valid value. Valid values are greater than zero (0). |
High Repeated Dissipation Def Horizon |
The High Repeated Dissipation Def Horizon defines the default Threshold used in the High Repeated Dissipation alert calculation; it represents the number of days to which the alert calculation are limited. The Dissipation Days threshold must be exceeded within this horizon. Zero is not a valid value. Valid values are greater than zero (0). |
Large Cons. OOS Def Alerting Stores Ratio |
The Large Cons. OOS Alerting Stores Ratio defines the threshold for the ratio of ranged stores OOS on consecutive days to the total number of ranged stores. This parameter represents the percentage threshold that must be exceeded when considering the generation of the Large Consecutive Out of Stocks alert. Valid values are zero (0) through one (1). Example: To generate an alert when more than 20% of the ranged stores were out of stock over the defined number of consecutive days; then in Large Cons. OOS Alerting Stores Ratio, enter: 0.2. |
Large Cons. OOS Def Corp. Lost Sales Volume over horizon |
The Large Cons. OOS Corp. Lost Sales Volume over horizon defines the threshold for the sum of lost sales for this SKU across ranged stores. This parameter represents the lost sales volume in units that must be exceeded when considering the generation of a Large Consecutive Out of Stocks alert.Any positive number, including zero, is valid. |
Large Cons. OOS Def Number of Consecutive Days OOS |
The Large Cons. OOS Number of Consecutive Days OOS defines the threshold for the number of consecutive days a product is out of stock that must be exceeded before the Large Consecutive Out of Stocks alert is triggered. Any positive integer, including zero, is valid. Example: To generate an alert when a SKU/Store is out of stock for 4 consecutive days; then in the Large Cons. OOS Number of Consecutive Days OOS, enter: 4. |
Large Non-Cons. OOS Def Alerting Stores Ratio |
The Large Non-Cons. OOS Alerting Stores Ratio defines the threshold for the ratio of ranged stores OOS on non-consecutive days to the total number of ranged stores. This parameter represents the percentage threshold that must be exceeded when considering the generation of the Large Non-Consecutive Out of Stocks alert. Valid values are zero (0) through one (1). Example: To generate an alert when more than 30% of the ranged stores were out of stock over the defined number of non-consecutive days; then in the Large Non-Cons. OOS Alerting Stores Ratio, enter: 0.3. |
Large Non-Cons. OOS Def Corp. Lost Sales Volume over horizon |
The Large Non-Cons. OOS Corp. Lost Sales Volume over horizon defines the threshold for the sum of lost sales for this SKU across ranged stores. This parameter represents the lost sales volume in units that must be exceeded when considering the generation of a Large Non-Consecutive Out of Stocks alert. Any positive number, including zero, is valid. |
Large Non-Cons. OOS Def Number of Days OOS |
The Large Non-Cons. OOS Number Days OOS defines the threshold for the number of non-consecutive days a product is out of stock that must be exceeded before the Large Non-Consecutive Out of Stocks alert is triggered. Any positive integer, including zero, is valid. Example: To generate an alert when a SKU/Store is out of stock for 5 non-consecutive days; then in the Large Non-Cons. OOS Number Days OOS, enter: 5. |
Large OOS Def Horizon |
The Large OOS Horizon parameter defines the number of days in history that are reviewed when considering the generation of a Large Consecutive Out of Stocks alert or a Large Non-Consecutive Out of Stocks alert. Any positive integer, including zero, is valid. Example: To review two weeks (14 days) of history; then in the Large OOS Horizon, enter: 14. |
Large OOS Last Night Def Alerting Stores Ratio |
The Large OOS Last Night Alerting Stores Ratio defines the threshold for the ratio of ranged stores OOS last night to the total number of ranged stores. This parameter represents the percentage threshold that must be exceeded when considering the generation of the Large Out of Stocks Last Night alert. Valid values are zero (0) through one (1). Example: To generate an alert when more than 40% of the ranged stores were out of stock last night; then in the Large OOS Last Night Alerting Stores Ratio, enter: 0.4. |
Large OOS Last Night Def Corp. Lost Sales % Possible Sales |
The Large OOS Last Night Corp. Lost Sales % Possible Sales parameter defines the threshold for the ratio of lost sales last night to demand last night. Note this ratio compares all stores for a SKU, not just those that were out of stock last night. This parameter represents the percentage threshold that must be exceeded when considering the generation of the Large Out of Stocks Last Night alert. Valid values are zero (0) through one (1). Example: To generate an alert when lost sales last night compared to possible sales last night (demand) were more than 20 %; then in the Large OOS Last Night Corp. Lost Sales % Possible Sales, enter: 0.2. |
Large OOS Last Night Def Corp. Lost Sales Volume |
The Large OOS Last Night Corp. Lost Sales Volume defines the threshold for the sum of lost sales last night for this SKU across ranged stores. This parameter represents the lost sales volume in units that must be exceeded when considering the generation of a Large Out of Stocks Last Night alert.Any positive number, including zero, is valid. |
Overstock Def Units Threshold |
The Overstock Units Threshold parameter defines the threshold in number of units which must be exceeded to trigger an Overstock Alert. Any positive integer, including zero, is valid. |
Single Store Def Corp. Lost Sales Volume over Horizon |
The Single Store Corp. Lost Sales Volume over Horizon defines the threshold for the sum of lost sales for this SKU at a single store. This parameter represents the lost sales volume in units that must be exceeded when considering the generation of a Single Store Availability Problems alert. Any positive number, including zero, is valid. |
Single Store Def Horizon |
The Single Store Horizon parameter defines the number of days in history that are reviewed when considering the generation of a Single Store Availability Problems. Any positive integer, including zero, is valid. Example: To review two weeks (14 days) of history; then in the Single Store Horizon, enter: 14. |
Single Store Def Number of Days OOS |
The Single Store Number of Days OOS defines the threshold for the number of days this product is out of stock for a store that must be exceeded to trigger a Single Store Availability Problems alert. Any positive integer, including zero, is valid. Example: To generate an alert when a product at a single store is out of stock for at least 4 days; then in the Single Store Number of Days OOS, enter: 4. |
This step contains the SKU/Store exception level values for parameters that are used in generating alerts.
The available view is:
This view contains the SKU/Store exception level values for parameters that are used in generating alerts.
Table 10-3 lists the measures in this view.
Table 10-3 Measures: SRP Alert Exception (SKU/Store) View
Measure Label | Description |
---|---|
Day on Day OOS Count Threshold |
The Day on Day OOS Count Threshold defines the threshold for the number of days a product is out of stock at a store for that SKU/Store to be considered as an exception. This parameter represents the number of days a store must be out of stock on the same day in consecutive weeks that must be exceeded before the Day on Day Repeat Out of Stocks alert is triggered. Any positive integer, including zero, is valid. Example: To generate an alert when a SKU/Store is out of stock on the same day for the past three weeks (21 days), then in the Day on Day OOS Count Threshold, enter: 21. |
Day on Day OOS Horizon |
Day on Day OOS Horizon defines the number of days in history that are reviewed when considering the generation of a Day on Day Repeat Out of Stocks alert. Any positive integer, including zero, is valid. Example: To review three weeks (21 days) of history; then in the Day on Day OOS Horizon, enter: 21. |
High Proj Low Stock Number of Low Stock Days |
High Proj Low Stock Number of Low Stock Days defines the threshold for the number of days a product is projected low stock that must be exceeded before the High Projected Low Stocks alert is triggered. Any positive integer, including zero, is valid. Example: To generate an alert when a SKU/Store is projected low stock for five days; then in the High Proj Low Stock Number of Low Stock Days Threshold, enter: 5. |
High Proj OOS / Low Stock Horizon |
The High Proj OOS / Low Stock Horizon parameter defines the number of future days that are reviewed when considering the generation of a High Projected Low Stocks alert or a High Projected Out of Stock alert. Any positive integer, including zero, is valid. Example: To review two weeks (14 days) in the future; then in the High Proj OOS / Low Stock Horizon, enter: 14. |
High Proj Number of Projected Days OOS |
The High Proj OOS Number of Projected Days OOS parameter defines the threshold for the number of days this product is projected out of stock that must be exceeded before the High Projected Out of Stock alert is triggered. Any positive integer, including zero, is valid. Example: To generate an alert if a SKU/Store is projected out of stock for three days; then in the High Proj OOS Number of Projected Days OOS Threshold, enter: 3. |
Large Cons. OOS Number of Consecutive Days OOS |
The Large Cons. OOS Number of Consecutive Days OOS defines the threshold for the number of consecutive days a product is out of stock that must be exceeded before the Large Consecutive Out of Stocks alert is triggered. Any positive integer, including zero, is valid. Example: To generate an alert when a SKU/Store is out of stock for four consecutive days; then in the Large Cons. OOS Number of Consecutive Days OOS, enter: 4. |
Large Non-Cons. OOS Number of Days OOS |
The Large Non-Cons. OOS Number Days OOS defines the threshold for the number of non-consecutive days a product is out of stock that must be exceeded before the Large Non-Consecutive Out of Stocks alert is triggered. Any positive integer, including zero, is valid. Example: To generate an alert when a SKU/Store is out of stock for five non-consecutive days; then in the Large Non-Cons. OOS Number Days OOS, enter: 5. |
Large OOS Horizon |
The Large OOS Horizon parameter defines the number of days in history that are reviewed when considering the generation of a Large Consecutive Out of Stocks alert or a Large Non-Consecutive Out of Stocks alert. Any positive integer, including zero, is valid. Example: To review two weeks (14 days) of history; then in the Large OOS Horizon, enter: 14. |
Overstock Units Threshold |
The Overstock Units Threshold parameter defines the threshold in number of units which must be exceeded to trigger an Overstock Alert.Any positive integer, including zero, is valid. |
Single Store Corp. Lost Sales Volume over Horizon |
The Single Store Corp. Lost Sales Volume over Horizon defines the threshold for the sum of lost sales for this SKU at a single store. This parameter represents the lost sales volume in units that must be exceeded when considering the generation of a Single Store Availability Problems alert.Any positive number, including zero, is valid. |
Single Store Horizon |
The Single Store Horizon parameter defines the number of days in history that are reviewed when considering the generation of a Single Store Availability Problems. Any positive integer, including zero, is valid. Example: To review two weeks (14 days) of history; then in the Single Store Horizon, enter: 14. |
Single Store Number of Days OOS |
The Single Store Number of Days OOS defines the threshold for the number of days this product is out of stock for a store that must be exceeded to trigger a Single Store Availability Problems alert. Any positive integer, including zero, is valid. Example: To generate an alert when a product at a single store is out of stock for at least four days; then in the Single Store Number of Days OOS, enter: 4. |
Stock Cover Days Threshold |
The Stock Cover Days Threshold defines the threshold in number days of supply that must be exceeded when considering the generation of an Overstock alert. Any positive integer, including zero, is valid. Example: To generate an alert only when the existing inventory covers demand for two weeks (14 days) or more; then in the Stock Cover Days Threshold, enter: 14. |
This step contains the default values at SKU/ Company for parameters that are used in generating alerts.
The available view is:
This view contains the global department level default values for parameters that are used in generating and processing store replenishment plans.
Table 10-4 lists the measures in this view.
Table 10-4 Measures: SRP Alert Default (SKU/Company) View
Measure Label | Description |
---|---|
Day on Day OOS Alerting Stores Ratio |
The Day on Day Alerting Stores Ratio defines the threshold for the ratio of ranged stores Out of Stock (OOS) on the same day in consecutive weeks to the total number of ranged stores. This parameter represents the percentage threshold that must be exceeded when considering the generation of a Day on Day Repeat Out of Stocks alert. Valid values are zero (0) through one (1). Example: To generate an alert when more than half of the ranged stores are out of stock on the same day in consecutive weeks; then in the Day on Day OOS Alerting Stores Ratio, enter: 0.5. |
Day on Day OOS Corp. Lost Sales Volume |
The Day on Day OOS Corp. Lost Sales Volume defines the threshold for the sum of lost sales for this SKU across ranged stores. This parameter represents the lost sales volume in units that must be exceeded when considering the generation of a Day on Day Repeat Out of Stocks alert. Any positive number, including zero, is valid. |
Day on Day OOS Day on Day Count Threshold |
The Day on Day OOS Day on Day Count Threshold defines the threshold for the number of days a product is out of stock at a store for that SKU/Store to be considered as an exception. This parameter represents the number of days a store must be out of stock on the same day in consecutive weeks that must be exceeded before the Day on Day Repeat Out of Stocks alert is triggered. Any positive integer, including zero, is valid. Example: To generate an alert when a SKU/Store is out of stock on the same day for the past three weeks; then in the Day on Day OOS Day on Day Count Threshold, enter: 3. |
High Proj Low Stock Alerting Stores Ratio |
The High Proj Low Stock Alerting Stores Ratio defines the threshold for the ratio of ranged stores with projected low stock to the total number of ranged stores. This parameter represents the percentage threshold that must be exceeded when considering the generation of High Projected Low Stocks alert. Valid values are zero (0) through one (1). Example: To generate an alert when more than half of the ranged stores have projected low stock, then in the High Proj Low Stock Alerting Stores Ratio, enter: 0.5. |
High Dissipation Yesterday % of Sales |
The High Dissipation Yesterday % of Sales defines the threshold used in the High Dissipation Yesterday alert calculation; it represents a percentage of dissipation compared to sales. Zero is not a valid value. Valid percentages are greater than zero (0). |
High Dissipation Yesterday Alerting Stores Ratio |
The High Dissipation Yesterday Alerting Stores Ratio defines the threshold used in the High Dissipation Yesterday alert calculation; it represents a percentage of High Dissipation stores (that are not High Repeat Dissipation Stores) that exceeded the High Dissipation % of sales ratio. Zero is not a valid value. Valid percentages are greater than zero (0). |
High Dissipation Yesterday Total % of Sales |
The High Dissipation Yesterday Total % of Sales defines the threshold used in the High Dissipation Yesterday alert calculation; it represents a percentage of total dissipation yesterday compared to total sales yesterday. Valid percentages are greater than zero (0). |
High Planned Orders Packs Threshold |
Threshold for High Planned Orders. It is the number of packs that a planned order quantity must not exceed. |
High Planned Orders Horizon |
The maximum number of days that are reviewed when scanning for order quantities that exceed the alerting threshold. |
High Proj OOS Alerting Stores Ratio |
The High Proj OOS Alerting Stores Ratio defines the threshold for the ratio of ranged stores with projected out of stocks to the total number of ranged stores. This parameter represents the percentage threshold that must be exceeded when considering the generation of High Projected Out of Stock alert. Valid values are zero (0) through one (1). Example: To generate an alert when more than half of the ranged stores have projected out of stocks; then in the High Proj OOS Alerting Stores Ratio, enter: 0.5. |
High Proj OOS Corp. Lost Sales % Forecast |
The High Proj OOS Corp. Lost Sales % Forecast defines the threshold for the ratio of projected lost sales for all stores over the horizon to demand forecast for all stores over the horizon. This parameter represents the percentage threshold that must be exceeded when considering the generation of High Projected Out of Stock alert. Valid values are zero (0) through one (1). Example: To generate an alert when the projected lost sales over the alert horizon are greater than 25% of the forecasted demand; then in The High Proj OOS Corp. Lost Sales % Forecast, enter: 0.25. |
High Proj OOS Corp. Lost Sales Volume over horizon |
The High Proj OOS Corp. Lost Sales parameter defines the threshold for the sum of projected lost sales across for this SKU across ranged stores. This parameter represents the corporate lost sales volume threshold in units that must be exceeded when considering the generation of High Projected Out of Stock alert. Any positive integer, including zero, is valid. |
Large Cons. OOS Alerting Stores Ratio |
The Large Cons. OOS Alerting Stores Ratio defines the threshold for the ratio of ranged stores OOS on consecutive days to the total number of ranged stores. This parameter represents the percentage threshold that must be exceeded when considering the generation of the Large Consecutive Out of Stocks alert. Valid values are zero (0) through one (1). Example: To generate an alert when more than 20% of the ranged stores were out of stock over; then in the Large Cons. OOS Alerting Stores Ratio defined number of consecutive days, enter: 0.2. |
Large Cons. OOS Corp. Lost Sales Volume over horizon |
The Large Cons. OOS Corp. Lost Sales Volume over horizon defines the threshold for the sum of lost sales for this SKU across ranged stores. This parameter represents the lost sales volume in units that must be exceeded when considering the generation of a Large Consecutive Out of Stocks alert.Any positive number, including zero, is valid. |
Large Non-Cons. OOS Alerting Stores Ratio |
The Large Non-Cons. OOS Alerting Stores Ratio defines the threshold for the ratio of ranged stores OOS on non-consecutive days to the total number of ranged stores. This parameter represents the percentage threshold that must be exceeded when considering the generation of the Large Non-Consecutive Out of Stocks alert. Valid values are zero (0) through one (1). Example: To generate an alert when more than 30% of the ranged stores were out of stock over the defined number of non-consecutive days; then in the Large Non-Cons. OOS Alerting Stores Ratio, enter: 0.3. |
High Repeated Dissipation % of Sales |
The High Repeated Dissipation % of Sales defines the threshold used in the High Repeated Dissipation alert calculation; it represents a percentage of dissipation compared to sales. Zero is not a valid value. Valid percentages are greater than zero (0). |
High Repeated Dissipation Alerting Stores Ratio |
The High Repeated Dissipation Alerting Stores Ratio defines the threshold used in the High Repeated Dissipation alert calculation; it represents a percent of stores with high dissipation over a significant number of days. Valid percentages are greater than zero (0). |
High Repeated Dissipation Days |
The High Repeated Dissipation Days defines the threshold used in the High Repeated Dissipation alert calculation; it represents the number of days that must exceed the Dissipation % of Sales threshold. Zero is not a valid value. Valid values are greater than zero (0). |
High Repeated Dissipation Horizon |
The High Repeated Dissipation Horizon defines the threshold used in the High Repeated Dissipation alert calculation; it represents the number of days to which the alert calculation is limited. The Dissipation Days threshold must be exceeded within this horizon. Zero is not a valid value. Valid values are greater than zero (0). |
Large Non-Cons. OOS Corp. Lost Sales Volume over horizon |
The Large Non-Cons. OOS Corp. Lost Sales Volume over horizon defines the threshold for the sum of lost sales for this SKU across ranged stores. This parameter represents the lost sales volume in units that must be exceeded when considering the generation of a Large Non-Consecutive Out of Stocks alert.Any positive number, including zero, is valid. |
Large OOS Last Night Alerting Stores Ratio |
The Large OOS Last Night Alerting Stores Ratio defines the threshold for the ratio of ranged stores OOS last night to the total number of ranged stores. This parameter represents the percentage threshold that must be exceeded when considering the generation of the Large Out of Stocks Last Night alert. Valid values are zero (0) through one (1). Example: To generate an alert when more than 40% of the ranged stores were out of stock last night; then in the Large OOS Last Night Alerting Stores Ratio, enter: 0.4. |
Large OOS Last Night Corp. Lost Sales % Possible Sales |
The Large OOS Last Night Corp. Lost Sales % Possible Sales parameter defines the threshold for the ratio of lost sales last night to demand last night. Note this ratio compares all stores for a SKU, not just those that were out of stock last night. This parameter represents the percentage threshold that must be exceeded when considering the generation of the Large Out of Stocks Last Night alert. Valid values are zero (0) through one (1). Example: To generate an alert when lost sales last night compared to possible sales last night (demand) were more than 20 %; then in the Large OOS Last Night Corp. Lost Sales % Possible Sales, enter: 0.2. |
Large OOS Last Night Corp. Lost Sales Volume |
The Large OOS Last Night Corp. Lost Sales Volume defines the threshold for the sum of lost sales last night for this SKU across ranged stores. This parameter represents the lost sales volume in units that must be exceeded when considering the generation of a Large Out of Stocks Last Night alert.Any positive number, including zero, is valid. |
This step contains views that:
Display the default values at the SKU/Store/Day level for parameters that are used in generating alerts.
Allow you to examine the global department level default values for parameters for store replenishment plans.
The available views are:
This view contains masks for SRP alerts that allow you to turn off the alert, or keep SRP from generating that alert on a specific day of the week.
The Alert Day Masks view contains the following writeable measures at the Day of Week (DOW) level. The alert does not trigger for a SKU/Store if its corresponding alert mask has the day of week in which today falls on is deselected.
The following measures display automatically when using the default template.
Day on Day Repeat Out of Stock DOW Mask
High Dissipation Yesterday Alert DOW Mask
High Planned Orders DOW Mask
High Projected Low Stocks DOW Mask
High Projected Out of Stock DOW Mask
High Repeated Dissipation Alert DOW Mask
Large Consecutive Out of Stocks DOW Mask
Large Non-Consecutive Out of Stocks DOW Mask
Large Out of Stocks Last Night DOW Mask
No Like SKU Found DOW Mask
Sales Forecast Detail Alert DOW Mask
Single Store Availability Problems DOW Mask
SRP Over Stock DOW Mask
This view contains masks for SRP alerts that allow you to turn off the alert, or keep SRP from generating that alert.
The SRP Alert Masks view contains the following writeable measures at the SKU/Store/Day level. The alert does not trigger for a SKU/Store if its corresponding alert mask at SKU/Store/today is deselected.
The following measures display automatically when using the default template.
Day on Day Repeat Out of Stock Mask
High Dissipation Yesterday Mask
High Planned Orders Mask
High Projected Low Stocks Mask
High Projected Out of Stock Mask
High Repeated Dissipation Mask
Large Consecutive Out of Stocks Mask
Large Non-Consecutive Out of Stocks Mask
Large Out of Stocks Last Night Mask
No Like SKU Found Mask
Sales Forecast Detail Alert Mask
Single Store Availability Problems Mask
SRP Over Stock Mask
This task is used to manage default and exception level parameters relating to warehouse alerts.
Use the WRP Alert Maintenance workbook to perform the steps for this task. See To build this workbook, see "WRP Alert Maintenance Workbook".
These steps help you achieve this task:
This step contains a view that allow you to examine the global department level default values for parameters for warehouse replenishment plans.
The available views are:
This view permits maintenance of alert-related defaults at the Sub-class level.
Table 10-5 lists the measures in this view.
Table 10-5 Measures: WRP Alert Default (Sub-class) View
Measure Label | Description |
---|---|
Demand Credit Case Threshold For Stocked Commodity Default |
Threshold in cases for alerting Demand Credits for stocked commodity. This quantity must be exceeded, as must the percentage demand credit threshold for a demand credit alert to be raised. Any positive value, including zero, is valid. Example: To generate alerts for more than a threshold of ten cases, enter: 10 |
Demand Credit Days Threshold For Stocked Commodity Default |
Threshold in days for alerting Demand Credits for a stocked commodity based on a number of consecutive days of demand credits. Any positive value, including zero, is valid. Example: To generate alerts for when there are more than three days of demand credits, enter: 3. |
Demand Credit Percentage Threshold For Stocked Commodity Default |
Threshold as a percentage of demand for alerting Demand Credits for a stocked commodity. This percentage must be exceeded, as must the demand credit case threshold for a demand credit alert to be raised. Any value between zero and one is valid. Example: To generate alerts for all Demand Credits representing more than 60% of demand, enter: 0.6. |
Demand Credit Unit Threshold For Stocked Commodity Default |
Threshold in units for alerting Demand Credits for a stocked commodity. This quantity must be exceeded for a demand credit alert to be raised. Any positive value, including zero, is valid. Example: To generate alerts for more than a threshold of ten units, enter: 10. |
Overstock Threshold Default |
Threshold in Units for generating overstock alert. This quantity must be exceeded for an overstock alert to be raised. Any positive value, including zero, is valid. Example: To generate overstock alerts for more than a threshold of 100 units, enter: 100. |
Projected Stock Cover Days Threshold Default |
Threshold in number of days cover for generating overstock alert. An overstock alert occurs when the number of days stock cover exceeds the stock cover days threshold. Any positive value, including zero, is valid. Example: To generate overstock alerts for when there are more than ten days of stock in the warehouse, enter: 10. |
Sales Credit Case Threshold For Stocked Commodity Default |
Threshold in cases for alerting Sales Credits for a stocked commodity. This quantity must be exceeded, as must the percentage sales credit for a sales credit alert to be raised. Any positive value, including zero, is valid. Example: To generate alerts for more than a threshold of ten cases, enter: 10. |
Sales Credit Case Threshold For Stockless Commodity Default |
Threshold in cases for alerting Sales Credits for a stockless commodity. This quantity must be exceeded, as must the percentage sales credit for a sales credit alert to be raised. Any positive value, including zero, is valid. Example: To generate alerts for more than a threshold of ten cases, enter: 10. |
Sales Credit Days Threshold For Stocked Commodity Default |
Threshold in days for alerting Sales Credits for a stocked commodity based on a number of consecutive days of sales credits. Any positive value, including zero, is valid. Example: To set alerts when there are more than three days of sales credits, enter: 3. |
Sales Credit Days Threshold For Stockless Commodity Default |
Threshold in days for alerting Sales Credits for a stockless commodity based on a number of consecutive days of sales credits. Any positive value, including zero, is valid. Example: To set alerts when there are more than three days of sales credits, enter: 3. |
Sales Credit Percentage Shortage For Stocked Commodity Default |
Threshold as a percentage of Sales for alerting Sales Credits for a stocked commodity. This percentage must be exceeded, as must the Sales credit case threshold for a sales credit alert to be raised. Any value between zero and one is valid. Example: To set alerts for all Sales Credits representing more than 60% of Sales, enter: 0.6. |
Sales Credit Percentage Shortage For Stockless Commodity Default |
Threshold as a percentage of Sales for alerting Sales Credits for a stockless commodity. This percentage must be exceeded, as must the Sales credit case threshold for a sales credit alert to be raised. Any value between zero and one is valid. Example: To set alerts for all Sales Credits representing more than 60% of Sales, enter: 0.6. |
Sales Credit Unit Threshold For Stocked Commodity Default |
Threshold in units for alerting Sales Credits for a stocked commodity. This quantity must be exceeded, as must the percentage sales credit for a sales credit alert to be raised. Any positive value, including zero, is valid. Example: To generate alerts for more than a threshold of ten units, enter: 10. |
Sales Credit Unit Threshold For Stockless Commodity Default |
Threshold in units for alerting Sales Credits for a stockless commodity. This quantity must be exceeded, as must the percentage sales credit for a sales credit alert to be raised. Any positive value, including zero, is valid. Example: To generate alerts for more than a threshold of ten units, enter: 10. |
Stockless Surplus Days of Demand Threshold Default |
This measure represents a number of days of demand to be summed and is used as part of the criteria for raising a stockless surplus alert. A stockless surplus alert notifies you that excessive orders exist at this warehouse based on warehouse demand. If the sum of demand over the Stockless Surplus Days of Demand Threshold is less than or equal to the demand credit surplus, one of the criteria to raise a stockless surplus has been met. The Stockless Surplus Days of Demand Threshold is used in both the Stockless Surplus Alert for a Single Day and the Stockless Surplus Alert for Multiple Days. Any positive value, including zero, is valid. Example: To sum the demand for five days, enter: 5. |
Stockless Surplus MultiDay Threshold Default |
This measure represents a threshold in days for triggering a Stockless Surplus Alert for Multiple Days. This number of days that meet the criteria for a stockless surplus alert must exceed Stockless Surplus Multi Day Threshold as one of the criteria to raise the Stockless Surplus Alert for Multiple Days. A stockless surplus alert notifies you that excessive orders exist at this warehouse based on warehouse demand. Any positive value, including zero, is valid. Example: To raise a Stockless Surplus Alert for Multiple Days when there are more than three days of stockless surplus alerts, enter: 3. |
Stockless Surplus Threshold Default |
This threshold represents the number of units a demand credit must exceed as part of the criteria for raising a stockless surplus alert. A stockless surplus alert notifies you that excessive orders exist at this warehouse based on warehouse demand. The Stockless Surplus Threshold is used in both the Stockless Surplus Alert for a Single Day and the Stockless Surplus Alert for Multiple Days. Any positive value, including zero, is valid. Example: To raise a Stockless Surplus Alert when the demand credit is greater than 100 units, enter: 100. |
This view permits maintenance of alert-related global default parameters at the Department level.
Table 10-6 lists the measures in this view.
Table 10-6 Measures: WRP Alert Global Default (Department) View
Measure Label | Description |
---|---|
Demand Credit Case Threshold For Stocked Commodity Global Default |
Threshold in cases for alerting Demand Credits for stocked commodity. This quantity must be exceeded, as must the percentage demand credit threshold for a demand credit alert to be raised. Any positive value, including zero, is valid. Example: To generate alerts for more than a threshold of ten cases, enter: 10. |
Demand Credit Days Threshold For Stocked Commodity Global Default |
Threshold in days for alerting Demand Credits for a stocked commodity based on a number of consecutive days of demand credits. Any positive value, including zero, is valid. Example: To generate alerts for when there are more than three days of demand credits, enter: 3. |
Demand Credit Percentage Threshold For Stocked Commodity Global Default |
Threshold as a percentage of demand for alerting Demand Credits for a stocked commodity. This percentage must be exceeded, as must the demand credit case threshold for a demand credit alert to be raised. Any value between zero and one is valid. Example: To generate alerts for all Demand Credits representing more than 60% of demand, enter: 0.6. |
Demand Credit Unit Threshold For Stocked Commodity Global Default |
Threshold in units for alerting Demand Credits for a stocked commodity. This quantity must be exceeded for a demand credit alert to be raised. Any positive value, including zero, is valid. Example: To generate alerts for more than a threshold of ten units, enter: 10. |
Overstock Threshold Global Default |
Threshold in Units for generating overstock alert. This quantity must be exceeded for an overstock alert to be raised. Any positive value, including zero, is valid. Example: To generate alerts for more than a threshold of 100 units, enter: 100. |
Projected Stock Cover Days Threshold Global Default |
Threshold in number of days cover for generating overstock alert. An overstock alert occurs when the number of days stock cover exceeds the stock cover days threshold. Any positive value, including zero, is valid. Example: To set an overstock alert for when there is more than ten days stock in the warehouse, enter: 10. |
Sales Credit Case Threshold For Stocked Commodity Global Default |
Threshold in cases for alerting Sales Credits for a stocked commodity. This quantity must be exceeded, as must the percentage sales credit for a sales credit alert to be raised. Any positive value, including zero, is valid. Example: To generate alerts for more than a threshold of ten cases, enter: 10. |
Sales Credit Case Threshold For Stockless Commodity Global Default |
Threshold in cases for alerting Sales Credits for a stockless commodity. This quantity must be exceeded, as must the percentage sales credit for a sales credit alert to be raised. Any positive value, including zero, is valid. Example: To generate alerts for more than a threshold of ten cases, enter: 10. |
Sales Credit Days Threshold For Stocked Commodity Global Default |
Threshold in days for alerting Sales Credits for a stocked commodity based on a number of consecutive days of sales credits. Any positive value, including zero, is valid. Example: To raise alerts when there are more than three days of sales credits, enter: 3. |
Sales Credit Days Threshold For Stockless Commodity Global Default |
Threshold in days for alerting Sales Credits for a stockless commodity based on a number of consecutive days of sales credits. Any positive value, including zero, is valid. Example: To raise alerts when there are more than three days of sales credits, enter: 3. |
Sales Credit Percentage Shortage For Stocked Commodity Global Default |
Threshold as a percentage of Sales for alerting Sales Credits for a stocked commodity. This percentage must be exceeded, as must the Sales credit case threshold for a sales credit alert to be raised. Any value between zero and one is valid. Example: To set alerts for all Sales Credits representing more than 60% of Sales, enter: 0.6. |
Sales Credit Percentage Shortage For Stockless Commodity Global Default |
Threshold as a percentage of Sales for alerting Sales Credits for a stockless commodity. This percentage must be exceeded, as must the Sales credit case threshold for a sales credit alert to be raised. Any value between zero and one is valid. Example: To set alerts for all Sales Credits representing more than 60% of Sales, enter: 0.6. |
Sales Credit Unit Threshold For Stocked Commodity Global Default |
Threshold in units for alerting Sales Credits for a stocked commodity. This quantity must be exceeded, as must the percentage sales credit for a sales credit alert to be raised. Any positive value, including zero, is valid. Example: To set a threshold of ten units, above which alerts are generated, enter: 10. |
Sales Credit Unit Threshold For Stockless Commodity Global Default |
Threshold in units for alerting Sales Credits for a stockless commodity. This quantity must be exceeded, as must the percentage sales credit for a sales credit alert to be raised. Any positive value, including zero, is valid. Example: To set a threshold of ten units, above which alerts are generated, enter: 10. |
Stockless Surplus Days of Demand Threshold Global Default |
This measure represents a number of days of demand to be summed and is used as part of the criteria for raising a stockless surplus alert. A stockless surplus alert notifies you that excessive orders exist at this warehouse based on warehouse demand. If the sum of demand over the Stockless Surplus Days of Demand Threshold is less than or equal to the demand credit surplus, one of the criteria to raise a stockless surplus has been met. The Stockless Surplus Days of Demand Threshold is used in both the Stockless Surplus Alert for a Single Day and the Stockless Surplus Alert for Multiple Days. Any positive value, including zero, is valid. Example: To sum the demand for five days, enter: 5. |
Stockless Surplus MultiDay Threshold Global Default |
This measure represents a threshold in days for triggering a Stockless Surplus Alert for Multiple Days. This number of days that meet the criteria for a stockless surplus alert must exceed Stockless Surplus Multi Day Threshold as one of the criteria to raise the Stockless Surplus Alert for Multiple Days. A stockless surplus alert notifies you that excessive orders exist at this warehouse based on warehouse demand. Any positive value, including zero, is valid. Example: To raise a Stockless Surplus Alert for Multiple Days when there are more than three days stockless surplus alerts, enter: 3. |
Stockless Surplus Threshold Global Default |
This threshold represents the number of units a demand credit must exceed as part of the criteria for raising a stockless surplus alert. A stockless surplus alert notifies you that excessive orders exist at this warehouse based on warehouse demand. The Stockless Surplus Threshold is used in both the Stockless Surplus Alert for a Single Day and the Stockless Surplus Alert for Multiple Days. Any positive value, including zero, is valid. Example: To raise a Stockless Surplus Alert when the demand credit is greater than 100 units; then enter: 5. |
This step contains the SKU/Store exception level values for parameters that are used in generating alerts.
The available view is:
This view permits maintenance of Alert Exception parameters at the SKU/Destination level.
Table 10-7 lists the measures in this view.
Table 10-7 Measures: WRP Alert Exception (SKU/Destination) View
Measure Label | Description |
---|---|
Demand Credit Case Threshold For Stocked Commodity |
Threshold in cases for alerting Demand Credits for stocked commodity. This quantity must be exceeded, as must the percentage demand credit threshold for a demand credit alert to be raised. Any positive value, including zero, is valid. Example: To generate alerts for more than a threshold of ten cases, enter: 10. |
Demand Credit Days Threshold For Stocked Commodity |
Threshold in days for alerting Demand Credits for a stocked commodity based on a number of consecutive days of demand credits. Any positive value, including zero, is valid. Example: To generate alerts when there are more than three days of demand credits, enter: 3. |
Demand Credit Percentage Threshold For Stocked Commodity |
Threshold as a percentage of demand for alerting Demand Credits for a stocked commodity. This percentage must be exceeded, as must the demand credit case threshold for a demand credit alert to be raised. Any value between zero and one is valid. Example: To generate alerts for all Demand Credits representing more than 60% of demand, enter: 0.6. |
Demand Credit Unit Threshold For Stocked Commodity |
Threshold in units for alerting Demand Credits for a stocked commodity. This quantity must be exceeded for a demand credit alert to be raised. Any positive value, including zero, is valid. Example: To generate alerts for more than a threshold of ten units, enter: 10. |
Overstock Threshold Exception |
Threshold in Units for generating overstock alert. This quantity must be exceeded for an overstock alert to be raised. Any positive value, including zero, is valid. Example: To generate overstock alerts for more than a threshold of 100 units, enter: 100. |
Projected Stock Cover Days Threshold Exception |
Threshold in number of days cover for generating overstock alert. An overstock alert occurs when the number of days stock cover exceeds the stock cover days threshold. Any positive value, including zero, is valid. Example: To generate overstock alerts for when there are more than ten days of stock in the warehouse, enter: 10. |
Sales Credit Case Threshold For Stocked Commodity |
Threshold in cases for alerting Sales Credits for a stocked commodity. This quantity must be exceeded, as must the percentage sales credit for a sales credit alert to be raised. Any positive value, including zero, is valid. Example: To generate alerts for more than a threshold of ten cases, enter: 10. |
Sales Credit Case Threshold For Stockless Commodity |
Threshold in cases for alerting Sales Credits for a stockless commodity. This quantity must be exceeded, as must the percentage sales credit for a sales credit alert to be raised. Any positive value, including zero, is valid. Example: To generate alerts for more than a threshold of ten cases, enter: 10. |
Sales Credit Days Threshold For Stocked Commodity |
Threshold in days for alerting Sales Credits for a stocked commodity based on a number of consecutive days of sales credits. Any positive value, including zero, is valid. Example: To generate alerts when there are more than three days of sales credits, enter: 3. |
Sales Credit Days Threshold For Stockless Commodity |
Threshold in days for alerting Sales Credits for a stockless commodity based on a number of consecutive days of sales credits. Any positive value, including zero, is valid. Example: To generate alerts when there are more than three days of sales credits, enter: 3. |
Sales Credit Percentage Shortage For Stocked Commodity |
Threshold as a percentage of Sales for alerting Sales Credits for a stocked commodity. This percentage must be exceeded, as must the Sales credit case threshold for a sales credit alert to be raised. Any value between zero and one is valid. Example: To generate alerts for all Sales Credits representing more than 60% of sales, enter: 0.6. |
Sales Credit Percentage Shortage For Stockless Commodity |
Threshold as a percentage of Sales for alerting Sales Credits for a stockless commodity. This percentage must be exceeded, as must the Sales credit case threshold for a sales credit alert to be raised. Any value between zero and one is valid. Example: To generate alerts for all Sales Credits representing more than 60% of sales, enter: 0.6. |
Sales Credit Unit Threshold For Stocked Commodity |
Threshold in units for alerting Sales Credits for a stocked commodity. This quantity must be exceeded, as must the percentage sales credit for a sales credit alert to be raised. Any positive value, including zero, is valid. Example: To generate alerts for more than a threshold of ten units, enter: 10. |
Sales Credit Unit Threshold For Stockless Commodity |
Threshold in units for alerting Sales Credits for a stockless commodity. This quantity must be exceeded, as must the percentage sales credit for a sales credit alert to be raised. Any positive value, including zero, is valid. Example: To generate alerts for more than a threshold of ten units, enter: 10. |
Stockless Surplus Days of Demand Threshold |
This measure represents a number of days of demand to be summed and is used as part of the criteria for raising a stockless surplus alert. A stockless surplus alert notifies you that excessive orders exist at this warehouse based on warehouse demand. If the sum of demand over the Stockless Surplus Days of Demand Threshold is less than or equal to the demand credit surplus, one of the criteria to raise a stockless surplus has been met. The Stockless Surplus Days of Demand Threshold is used in both the Stockless Surplus Alert for a Single Day and the Stockless Surplus Alert for Multiple Days. Any positive value, including zero, is valid. Example: To sum the demand for five days, enter: 5. |
Stockless Surplus Multi Day Threshold |
This measure represents a threshold in days for triggering a Stockless Surplus Alert for Multiple Days. This number of days that meet the criteria for a stockless surplus alert must exceed Stockless Surplus Multi Day Threshold as one of the criteria to raise the Stockless Surplus Alert for Multiple Days. A stockless surplus alert notifies you that excessive orders exist at this warehouse based on warehouse demand. Any positive value, including zero, is valid. Example: To raise a Stockless Surplus Alert for Multiple Days when there are more than three days of stockless surplus alerts, enter: 3. |
Stockless Surplus Threshold |
This threshold represents the number of units a demand credit must exceed as part of the criteria for raising a stockless surplus alert. A stockless surplus alert notifies you that excessive orders exist at this warehouse based on warehouse demand. The Stockless Surplus Threshold is used in both the Stockless Surplus Alert for a Single Day and the Stockless Surplus Alert for Multiple Days. Any positive value, including zero, is valid. Example: To raise a Stockless Surplus Alert when the demand credit is greater than 100 units; then enter: 100. |
This step contains the views that show:
Allow you to examine the global department level default values for parameters for warehouse replenishment plans.
Show default values at SKU Group/Destination/Day for parameters that are used in generating alerts.
The available views are:
This view permits maintenance of alert masks by Day of Week. By deselecting a day of week for a given alert mask, you prevent the generation of that alert for that day of week for a SKU/Destination. The Alert Day-of-Week Mask together with the Alert Mask determines whether an alert can be triggered.
The following alert masks display automatically when using the default template.
Demand Credit Alert Day Mask
Overstock Alert Day Mask
Sales Forecast Alert Day Mask
Sales Credit Alert Day Mask
This view contains masks for WRP alerts that allows you to turn off the alert, or keep WRP from generating that alert.
The WRP Alert Masks view contains the following writeable measures at the SKU Group/Destination/Day level. You can deselect a box to stop that alert from being run. The Alert Mask together with the Alert Day-of-Week Mask determines whether an alert can be triggered.
The following measures display automatically when using the default template.
Demand Credit Alert Mask
Overstock Alert Mask
Sales Credit Alert Mask
This view contains masks for WRP alerts that allows you to turn off the alert, or keep WRP from generating that alert.
The WRP Alert Masks view contains the following writeable measure at the SKU Group/Destination level. The WRP user can deselect a box to stop that alert from being run.
The following measure is displayed automatically when using the default template:
Sales Forecast Alert Mask
This task enables you to manage Network Level Thresholds and Capacity Levels for warehouses.
Use the WRP Network Threshold Maintenance workbook to perform the step for this task. See To build this workbook, see "WRP Network Threshold Maintenance Workbook".
These steps help you achieve this task:
This step enables you to manage Network Level Thresholds and Capacity Levels for warehouses.
The available views are:
This view displays parameters at the global level.
Table 10-8 lists the measures in this view.
Table 10-8 Measures: WRP Excessive Stock Cover Threshold View
Measure Label | Explanation |
---|---|
Excessive Stock Cover Global Threshold. |
A value that must be exceeded for excessive stock cover alert to be triggered. Stock cover is based on current inventory and forecasted demand. Any positive value is valid. |
This view permits maintenance of the warehouse capacity at the Network Group/Destination level.
Table 10-9 lists the measures in this view.
This view displays measures at the Network Group/Destination/Day level.
Table 10-10 lists the measures in this view.
Table 10-10 Measures: WRP Target Stock Cover Screen View
Measure Label | Explanation |
---|---|
Outbound Distribution Capacity Cases |
A measure indicating the outbound distribution capacity in cases for a network group at a warehouse. Any positive value is valid. |
Target Stock Cover |
Stock cover target in terms of weeks cover for a network group and warehouse. Any positive value is valid. |
This view enables you to maintain day on day change thresholds at the Network Group/Destination/Day level.
Table 10-11 lists the measures in this view.
Table 10-11 Measures: WRP Day on Day Change Threshold View
Measure Label | Explanation |
---|---|
Inbound Day-on-Day Change Threshold |
When the percentage change between yesterday's remaining week actual inbound plan and today's remaining week actual inbound plan exceeds this threshold, an alert is raised. |
Outbound Day-on-Day Change Threshold |
When the percentage change between yesterday's remaining week actual outbound plan and today's remaining week actual outbound plan exceeds this threshold, an alert is raised. |
Stock Cover Day-on-Day Change Threshold |
When the percent change between yesterday's stock cover in cases and today's stock cover in cases exceeds this threshold, an alert is raised. |
This step contains a view that allow you to examine the global department level default values for parameters for store replenishment plans.
The available view is:
This view allows you to maintain alert masks at the Day of Week level.
Table 10-12 lists the measures in this view.
Table 10-12 Measures: WRP Network Alert Run Days View
Measure Label | Explanation |
---|---|
Inbound Day-on-Day Change Alert Day Mask |
A mask that determines if the Inbound Day on Day Change Alert should run. Checking the box indicates the alert should run on that day of the week. |
Outbound Day-on-Day Change Alert Day Mask |
A mask that determines if the Outbound Day on Day Change Alert should run. Checking a box indicates the alert should run on that day of the week. |
Outbound Distribution Capacity Alert Day Mask |
A mask that determines if the Outbound Distribution Capacity Alert should run. Checking the box indicates the alert should run on that day of the week. |
Stock Cover Alert Day Mask |
A mask that determines if the Stock Cover Alert should run. Checking the box indicates the alert should run on that day of the week. |
Stock Cover Day-on-Day Change Alert Day Mask |
A mask that determines if the Stock Cover Day on Day Change Alert should run. Checking the box indicates the alert should run on that day of the week. |
Warehouse Holding Capacity Alert Day Mask |
A mask that determines if the Warehouse Holding Capacity Alert should run. Checking the box indicates the alert should run on that day of the week. |
This task is required to maintain SRP implementation parameter settings that are used by the entire package (scalar level).
Use the SRP Inventory Capping Parameter workbook to perform the step for this task. See To build this workbook, see "SRP Inventory Capping Parameters Workbook".
Note: Because values in this workbook are used by the entire SRP system, it is recommended that security is set to allow a single or limited number of super users access to this workbook. |
This step helps you achieve this task:
This step is required to maintain SRP implementation parameter settings that are used by the entire package (scalar level).
The available views are:
The Implementation Parameters view contains SRP Implementation Parameter settings that impact the functionality of the system. These settings are managed by a small group of business administrators or a system administrator.
Table 10-13 lists the measures in this view.
Table 10-13 Measures: Implementation Parameters (Scalar) View
Measure Label | Description |
---|---|
Workbook Selection Limit - Store Planning |
Maximum number of combinations of products, stores and days. |
Prioritize Warehouse External Demand |
When performing Day-on-day reconciliation a True value indicates that inventory must be allotted to warehouse External Demand first. When the value is False, inventory must be allotted to all location demand before External Demand. |
Store Cases Per Pallet Override Indicator |
Indicates when cases per pallet is user entered for warehouse sources. The default is False which indicates Cases Per Pallet should be calculated from the warehouse pallet multiple. If the value is True, you must specify the value in order to round store orders to pallets. |
Calculated Store Presentation Stock Indicator |
Boolean indicator to denote when the calculated store presentation stock should be factored into the calculation of Store Presentation Stock. |
Daily Forecast Length |
Note: Forecasts are loaded to SRP from an external system as daily forecasts, weekly forecasts, or a combination of daily and weekly forecasts. The Daily Forecast Length is used to specify the number of days of daily forecasts to use when loading forecasts. Valid values are negative one (-1), zero (0), and n, where n is any positive number. -1 = Load all daily forecasts 0 = Load all weekly forecasts n = Load daily forecasts for the first n days Example: To load daily forecasts for the first two weeks (14 days); then in the Daily Forecast Length, enter: 14. |
Days Beyond Planning Horizon |
The Days Beyond Planning Horizon Parameter represents the number of days SRP looks forward to find the next ATP day after the end of the planning horizon. SRP uses the data between the end of the planning horizon and the next ATP day to calculate the receipt plan for the last ATP day. No plan is calculated on the ATP day beyond the planning horizon. If SRP does not find an ATP day in the period from the end of the planning horizon through the days beyond the planning horizon, the receipt plan calculations uses data through the days beyond planning horizon to plan the last receipt. Any positive number, including zero, is valid. Example: If the majority of items are available to plan to weeks or less; then in the Days Beyond Planning Horizon, enter: 14. This allows the system to find the next ATP day in most cases and have the required data to calculate an accurate receipt plan on the last ATP day within the horizon. |
Days of Ignored Availability |
The Days of Ignored Availability indicates how many days of availability should be ignored when determining the end of the first Reconciliation Period. This parameter should never be set to less than one day.(Read Only) |
Expected Spoilage Calculation Indicator |
The Expected Spoilage Calculation Indicator indicates when Expected Spoilage (ES) calculations should be performed. The default is True, which indicates that ES calculations should be performed where product life is deemed relevant for a particular SKU. If value set to False, ES is considered to be zero in projected and net inventory calculations. |
Inventory Capping Forecast Days |
Inventory Capping Forecast Days is an implementation parameter representing the number of days over which forecasts are summed when determining the Inventory Cap Forecast for a SKU. The Inventory Cap Forecast is used to recommend SKU Caps proportionally for a department. The Inventory Capping Forecast Days should be set to value that would represent a fair split of the stores forecast. Inventory Capping Forecast Days must be a positive integer; the default value is seven days. |
Inventory Tracking Level |
Inventory Tracking Level determines the level at which planning occurs. The available options are packs or eaches. Example: Selecting Packs causes AIP to plan in pack-sizes. Selecting Eaches causes AIP to plan in eaches, where all inventory and supply is considered available in singles, and orders are generated using the order multiple and pack-sizes as the appropriate rounding multiples. Note: A change to the Inventory Tracking Level parameter after implementation is not supported. If business requirements require a change to tracking level, analysis of the impact and other changes which may be required can be provided by Services. |
Prioritize External Demand |
When performing day-on-day reconciliation a True value indicates that inventory must be allotted to warehouse External Demand first. When the value is False inventory must be allotted to all location demand before External Demand. |
Round to Meet Store MSS |
When performing Order Multiple rounding on the store's ideal receipt quantity, the rounded quantity plus NI must be at least as great as the Minimum Sales Stock boundary. The default value is False. |
Secondary Delivery Window |
The Secondary Delivery Window indicates how many days earlier than the day of a shortage a delivery can be received from a Secondary Source to meet that shortage.(Read only) |
SPQ Date Type |
The SPQ Date Type determines whether SPQ constraint is applied against the ship date or receipt date. You select the SPQ Date Type from the following options:
|
Spread Inventory Flag |
The Spread Inventory Flag specifies if it is desirable to spread inventory across multiple delivery opportunities of a single destination during Primary Reconciliation.(Read Only) |
Store Forecast Demand Index Calculation Indicator |
A boolean parameter that indicates when a Store Forecast Demand Index (FDI) calculation should be performed. The default is False and this indicates that an FDI calculation should not be performed when calculation Store Forecast Standard Deviation. |
Store Inventory Aging Limit |
The Store Inventory Aging Limit defines the upper threshold in days which product life. When the product life is less than the aging limit, inventory aging processing occurs. Any positive number, including zero, is valid. Example: To use inventory aging only on items with a product life of one week or less; then in the Store Inventory Aging Limit, enter: 7. This ensures that any item with a product life greater than seven days is not considered in the inventory aging calculation. |
The Implementation Parameters view contains SRP Implementation Parameter settings that impact the functionality of the system at the Department level. These settings are managed by a small group of business administrators or a system administrator.
Table 10-14 lists the measures in this view.
Table 10-14 Measures: Implementation Parameters (Department) View
Measure Label | Description |
---|---|
Aggregated Forecast Sales Period. |
Indicates the number of days over which store sales are aggregated to determine the Aggregated Forecast Period Sales measure. Acceptable values are integers from 1 to 42 inclusive. |