Guidelines for Working with Plan Messages for Replenishment Plans
This topic explains what the plan messages for replenishment plans mean and how you should work with them.
In the Replenishment Planning work area, you can view plan messages after a replenishment plan runs. By understanding the root causes why policies and replenishments weren't calculated within the replenishment plan for item-location combinations, you can take corrective actions.
Plan messages deal with these issues:
-
The size and run of the replenishment plan
-
The calculation of safety stock
-
The calculation of average daily demand
-
Other issues, such as the calculation of the economic order quantity (EOQ)
Messages Dealing with the Size and Run of the Replenishment Plan
This table lists plan messages that deal with the size and run of the replenishment plan:
Message |
Meaning |
Corrective Action |
---|---|---|
The following number of item and organization combinations were included in the replenishment plan: {COUNT}. |
Indicates the number of item-location combinations covered in the replenishment plan and for which replenishment planning is done. The item-location combinations are in the selected segments and level members on the Scope tab on the Plan Options page for the replenishment plan. Moreover, in Oracle Fusion Cloud Product Lifecycle Management, for MPS MRP planning, the planning method attribute is set to Replenishment Planning for these items. |
- |
The plan was run in the Refresh with Current Data mode because targeted collection was run. |
Indicates that the replenishment plan is run with current data even though the Enable for incremental planning check box is selected on the Plan Options page and the Refresh with net-changed data option is selected under the Details region on the Parameters tab in the Run Plan dialog box. Current data is used because the type of the previous collection was targeted. |
- |
Messages Dealing with the Calculation of Safety Stock
This table lists plan messages that deal with the safety stock for item-location combinations:
Message |
Meaning |
Corrective Action |
---|---|---|
Safety stock wasn't calculated for item {ITEM} in organization {ORG} because the MAPE wasn't available. |
Indicates that the safety stock isn't calculated for the item-location combination. This plan message is displayed because of these reasons:
|
Perform these steps:
|
Safety stock wasn't calculated for item {ITEM} in organization {ORG} because the total lead time was zero. |
Indicates that the safety stock isn't calculated for the item-location combination. This plan message is displayed because of these reasons:
|
Perform these steps:
|
Safety stock wasn't calculated for item {ITEM} in organization {ORG} because average interarrival time wasn't available. |
Indicates that the safety stock isn't calculated for the item-location combination. This plan message is displayed because of these reasons:
|
Perform these steps:
|
The intermittent demand indicator for item {ITEM} in organization {ORG} was invalid. Safety stock was set equal to average daily demand. |
Indicates that the safety stock isn't calculated for the item-location combination. This plan message is displayed because of these reasons:
|
Perform these steps:
|
The uploaded safety stock quantity wasn't considered for item-location combinations in segment {SEG_NAME}. Instead of the uploaded quantity, the safety stock defined or calculated for the segment was used because the policy UOM for the segment is Days and not Units. |
Indicates that the uploaded safety stock quantity isn't considered for the item-location combinations in the specified segment. Instead, the safety stock override or calculated safety stock for the segment is used. This plan message is displayed because the safety stock quantity was uploaded through the file-based data import (FBDI) template for Supply Chain Planning safety stock levels (ScpSafetyStockLevelImportTemplate.xlsm). The uploaded safety stock quantity is always in units and takes precedence over the calculated or override value for safety stock. However, the unit of measure (UOM) for the segment is days instead of units. |
Perform these steps:
|
Messages Dealing with the Calculation of Average Daily Demand
This table lists plan messages that deal with the demand for item-location combinations:
Message |
Meaning |
Corrective Action |
---|---|---|
Average daily demand wasn't calculated for item {ITEM} in organization {ORG}. Policies weren't calculated. |
Indicates that the average daily demand isn't calculated for the item-location combination. This plan message is logged because the demand history isn't present or the forecast isn't generated for the item location combination. Also, the default daily demand isn't specified for the segment to which the item-location combination belongs. |
Perform these steps:
|
For segment {SEG}, the plan horizon days was used for the horizon for average daily demand because it's less than the horizon for average daily demand. |
Indicates that the number of days in the planning horizon is taken for calculation of the average daily demand for item-location combinations in the segment. This plan message is displayed because the planning horizon is less than the value supplied in the Horizon for Average Daily Demand field on the Policy Parameters subtab on the Segment-Level Policy Parameters Assignment tab of the policy assignment set that's attached to the replenishment plan. |
If you want the specified horizon for average daily demand to be considered, perform these steps:
|
Messages Dealing with Other Issues
This table lists plan messages that deal with other issues:
Message |
Meaning |
Corrective Action |
---|---|---|
The following number of items in ORG {ORG} were discarded because their planning method isn't set to Replenishment Planning: {COUNT}. |
Indicates the number of items in the location for which replenishment planning isn't done. The items are ignored because their MPS and MRP Planning Method attribute isn't set to Replenishment planning in Oracle Product Lifecycle Management. |
Perform these steps:
|
The plan created 10 supplies on a single day for item {ITEM} in organization {ORG}. Check the order modifiers. |
Indicates that 10 replenishment orders are created for the item-location combination on a day. This plan message is displayed because of these reasons:
|
Perform these steps:
|
Policy parameters weren't found for segment {SEGMENT}. Policies weren't calculated for the item and location combinations that were part of this segment. |
Indicates that replenishment policies aren't calculated for the item-location combinations in the segment. In the policy assignment set that's attached to the replenishment plan, policy parameters aren't specified for the segment. Therefore, no policies are calculated for the item-location combinations in the segment. |
Perform these steps:
|
EOQ wasn't calculated for item {ITEM} in organization {ORG}. Check Item cost components. |
Indicates that the EOQ isn't calculated for the item-location combination. This plan message is displayed because of these reasons:
|
Perform these steps:
|
Forecast and policy values haven't been calculated for items in organization {ORG}. Valid manufacturing calendar data isn't available for the organization. To get the forecast and policy values, collect the calendar data, and rerun the replenishment plan. |
Indicates that the forecast and policy values aren't calculated for the items in the specified location. This plan message is displayed because the manufacturing calendar isn't available for the location. |
Perform these steps:
|