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: In the policy assignment set that's attached to the replenishment plan, for the segment to which the item-location combination belongs, on the Policy Parameters subtab on the Segment-Level Policy Parameters Assignment tab, you selected Service level-based in Safety Stock Calculation. The demand isn't intermittent. The mean average percentage error (MAPE) isn't available for the item-location combination in the demand plan, replenishment plan, or external demand schedule that's used as the demand schedule for the replenishment plan.	Perform these steps: Ensure that the MAPE is available for the item-location combination in the demand plan, replenishment plan, or external demand schedule. Run the replenishment plan: Under the Details region on the Parameters tab in the Run Plan dialog box, select Refresh with current data. Select the Calculate policy parameters check box.
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: In the policy assignment set that's attached to the replenishment plan, for the segment to which the item-location combination belongs, on the Policy Parameters subtab on the Segment-Level Policy Parameters Assignment tab, you selected Service level-based in Safety Stock Calculation. The demand isn't intermittent. The replenishment lead time, which is the sum of the preprocessing, processing, and postprocessing lead times and transit time for a buy order or preprocessing and postprocessing lead times and transit time for a transfer order, is zero for the item-location combination.	Perform these steps: Set the preprocessing, processing, and postprocessing lead times for the item-location combination in Oracle Product Lifecycle Management. Set the transit time in the sourcing rule or bill of distribution. Run the collections process. Run the replenishment plan: Under the Details region on the Parameters tab in the Run Plan dialog box, select Refresh with current data. Select the Calculate policy parameters check box.
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: In the policy assignment set that's attached to the replenishment plan, for the segment to which the item-location combination belongs, on the Policy Parameters subtab on the Segment-Level Policy Parameters Assignment tab, you selected Service level-based in Safety Stock Calculation. The demand is intermittent. The average interarrival time isn't available for the item-location combination in the Items table.	Perform these steps: Ensure that the average interarrival time is available for the item-location combination in the Items table. Run the replenishment plan: Under the Details region on the Parameters tab in the Run Plan dialog box, select Refresh with current data. Select the Calculate policy parameters check box.
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: In the policy assignment set that's attached to the replenishment plan, for the segment to which the item-location combination belongs, on the Policy Parameters subtab on the Segment-Level Policy Parameters Assignment tab, you selected Service level-based in Safety Stock Calculation. The value in the Intermittent Demand or Intermittent Demand Override column of the Items table for the item-location combination is invalid. Consequently, the safety stock has been set to the average daily demand for the item-location combination.	Perform these steps: Ensure that valid values are there in the Intermittent Demand and Intermittent Demand Override columns for the item-location combination in the Items table. Run the replenishment plan: Under the Details region on the Parameters tab in the Run Plan dialog box, select Refresh with current data. Select the Calculate policy parameters check box.
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: In the policy assignment set that's attached to the replenishment plan, for the segment, on the Policy Parameters subtab on the Segment-Level Policy Parameters Assignment tab, select Units in Policy UOM. Run the replenishment plan: Under the Details region on the Parameters tab in the Run Plan dialog box, select Refresh with current data. Select the Calculate policy parameters check box.

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: In the policy assignment set that's attached to the replenishment plan, for the segment to which the item-location combination belongs, on the Policy Parameters subtab on the Segment-Level Policy Parameters Assignment tab, if History is selected in Days of Cover Basis, ensure that the demand history is collected or uploaded. If Forecast is selected in Days of Cover Basis, ensure that the demand forecast is there in the demand plan, replenishment plan, or external demand schedule that's used as the demand forecast. Otherwise, specify a default daily demand for the segment. Run the replenishment plan: Under the Details region on the Parameters tab in the Run Plan dialog box, select Refresh with current data. Select the Generate forecast and Calculate policy parameters check boxes.
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: Decrease the horizon for the average daily demand in the policy assignment set, or increase the days in the planning horizon by increasing the number of buckets on the Scope tab on the Plan Options page for the replenishment plan. Run the replenishment plan: Under the Details region on the Parameters tab in the Run Plan dialog box, select Refresh with current data. Select the Generate forecast and Calculate policy parameters check boxes.

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: Set the attribute for the items in Oracle Product Lifecycle Management. Run the collections process. Run the replenishment plan: Under the Details region on the Parameters tab in the Run Plan dialog box, select Refresh with current data. Select the Generate forecast, Calculate policy parameters, and Calculate replenishments check boxes.
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: The fixed order quantity order modifier or EOQ is used with a very small value, and many planned orders with small quantities are generated. For reducing the number of planned orders and improving the replenishment plan performance, the first nine planned orders are generated according to the order modifiers, and the remaining planned orders are grouped into the 10th planned order. The 10th planned order might violate the order modifiers and therefore won't be released.	Perform these steps: Review and modify the value in the Fixed Order Quantity column of the Items table for the item-location combination. Otherwise, review and modify the inputs for calculating the EOQ or default EOQ for the item-location combination. Run the replenishment plan: Under the Details region on the Parameters tab in the Run Plan dialog box, select Refresh with current data. Select the Calculate replenishments check box.
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: In the policy assignment set, specify policy parameters for the segment. Run the replenishment plan: Under the Details region on the Parameters tab in the Run Plan dialog box, select Refresh with current data. Select the Calculate policy parameters check box.
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: In the policy assignment set that's attached to the replenishment plan, for the segment to which the item-location combination belongs, the policy type is one of the following: Reorder point (ROP) and EOQ Min-max planning or fixed order cycle, and the maximum quantity calculation method is minimum plus EOQ. For the segment to which the item-location combination belongs, the default EOQ isn't specified on the Default Policy Parameters subtab on the Segment-Level Policy Parameters Assignment tab in the policy assignment set. The fixed cost per order isn't available for the item-location combination in the Order Cost column of the Items table. The annual carrying cost isn't available for the item-location combination in the Annual Carrying Cost Percentage column of the Items table. The standard cost isn't available for the item-location combination in the Standard Cost column of the Item table, or the default standard cost isn't specified for the segment on the Default Policy Parameters subtab.	Perform these steps: Check that values are present for the item-location combination in the Items table for the various components of the formula for EOQ calculation. If any values are missing in the Items table, do one of these steps: Provide the values in the Items table. In the policy assignment set, enter the required defaults for the EOQ formula or the default EOQ for the segment to which the item-location combination belongs. Run the replenishment plan: Under the Details region on the Parameters tab in the Run Plan dialog box, select Refresh with current data. Select the Calculate policy parameters check box.
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: Ensure that the manufacturing calendar is available for the location. Run the collections process. Run the replenishment plan: Under the Details region on the Parameters tab in the Run Plan dialog box, select Refresh with current data. Select the Generate forecast, Calculate policy parameters, and Calculate replenishments check boxes.