Root Cause Categorization
The method of determining the conditions that resulted in a particular state of inventory. Root Cause Categorization is used by the following dashboards to determine the categories that appear in the legend of the graphs:
◦ Backorder Categorization widget
The valid categories are:
|
Category
|
Priority
|
Description
|
Conditions
|
||
|---|---|---|---|---|---|
|
Forced Non-Stock
|
1
|
A constraint or override that forces the SKU not to stock
|
Any override or constraint that forces the SKU to not stock.
For example:
Stock Maximum Fixed Override = 0
|
||
|
No Supply Source
|
2
|
No supply source is available
|
These three conditions are true:
• Procurable = N
• Replenishable = N
• Repairable = N
|
||
|
On ASL with On Order
|
3
|
Supply constraint
|
These three conditions are true:
• ASL = Y
• The supply shortage is at the parent location
• One of the following is true:
◦ For the Demand Miss Analysis dashboard:
On Order + In Repair > 0
On Order Original + In Repair Original > 0
|
||
|
Vendor Delays with On ASL with OnOrder
|
3.1
|
Supply constraint due to vendor delay impacting procuring location
|
This further categorizes On ASL with On Order (3)
Demand Miss at procurement location (ProcAllowed = ‘y’) and review reason ‘Overdue host order(s) exist’ (Review TypeID=327) occurred at this procurement location.
This condition is true for Demand Miss Analysis, SKU Supply Chain History, Performance 360- Backorder Categories and Backorder Categorization report.
For Demand Miss Analysis, SKU Supply Chain History, the Overdue host order(s) exist Review Reason (327) is looked in last ‘x’ number of days, which is defined by setting the servigistics.analytics.demandmiss.pastlookupdays WebUI property to 30
|
||
|
Vendor Delays at Procuring Location with On ASL with OnOrder
|
3.2
|
Supply constraint due to vendor delay at procuring location impacting downstream replenishment location
|
This further categorizes On ASL with On Order (3)
Demand Miss at replenishment location (ProcAllowed = ‘n’) and review reason ‘Overdue host order(s) exist’ (Review TypeID=327) occurred at its corresponding procurement location.
This condition is true for Demand Miss Analysis, SKU Supply Chain History, Performance 360- Backorder Categories and Backorder Categorization report.
For Demand Miss Analysis, SKU Supply Chain History, the Overdue host order(s) exist Review Reason (327) is looked in last ‘x’ number of days, which is defined by setting the servigistics.analytics.demandmiss.pastlookupdays WebUI property to 30
|
||
|
Under Forecast with On ASL with OnOrder
|
3.3
|
Supply constraint due to under forecast
|
This further categorizes On ASL with On Order (3)
Demand Miss exists and under forecast review reason for example. ‘Tracking Signal - Actuals Greater than Forecast’ (Review TypeID=138).
This condition is true for Demand Miss Analysis, SKU Supply Chain History, Performance 360- Backorder Categories and Backorder Categorization report.
For Demand Miss Analysis, SKU Supply Chain History, the Overdue host order(s) exist Review Reason (327) is looked in last ‘x’ number of days, which is defined by setting the servigistics.analytics.demandmiss.pastlookupdays WebUI property to 30
|
||
|
On ASL with On Order Not Categorized
|
3.4
|
Supply constraint due to other than vendor delay and under forecast
|
This further categorizes On ASL with On Order (3)
The record did not meet any of the conditions that were evaluated for On ASL with On Order.
This condition is true for Demand Miss Analysis, SKU Supply Chain History, Performance 360- Backorder Categories and Backorder Categorization report.
|
||
|
On ASL without On Order
|
4
|
No supply is available
|
These two conditions are true:
• ASL = Y
• One of the following is true:
◦ For the Demand Miss Analysis dashboard:
On Order + In Repair = 0
On Order Original + In Repair Original = 0
|
||
|
System Chose Not to Stock and Forecast Exists
|
5
|
The optimal value is to not stock with a forecast great than 0
|
These three conditions are true:
• ASL = N
• No overrides or constraints exist that force the SKU to not stock
• The Forecast is not 0
|
||
|
First Time Demand
|
6
|
First time demand
|
No Demand record existed prior to this period for Demand History.
|
||
|
System Chose Not to Stock and No Forecast Exists
|
7
|
The optimal value is to not stock with a zero forecast
|
These three conditions are true:
• ASL = N
• No overrides or constraints exist that force the SKU to not stock
• The Forecast is 0
|
||
|
Not Categorized
|
8
|
No conditions were met
|
The record did not meet any of the conditions that were evaluated
|
 |
When upgrading, existing data for the following categories are not recalculated:
• Vendor Delays With On ASL with OnOrder
• Vendor Delays at Procuring Location With On ASL with OnOrder
• Under Forecast On ASL with OnOrder
These categories are only displayed for new historicized data.
For example, if Demand Missed exists with a past date, and it was listed under the 3, On ASL with On Order, category, that will now be listed under the 3.4, On ASL with On Order Not Categorized, category. If there is demand missed on today’s date, then that will appear under one of the 3.1, 3.2, 3.3, or 3.4 categories.
|