Diagnosing Min-Max Planning Orders That Never Appear in Oracle Fusion SCM

 

When min-max planning fails to generate replenishment orders, the silence in the supply plan is usually traced to a mismatch between the planning parameters, the item setup, and the actual on-hand position at the moment the plan executes Oracle Fusion SCM Online Training The min-max engine evaluates each item-organization combination against its defined minimum and maximum quantities, but it only acts when the projected available balance falls below the minimum and when all enabling conditions are met. A single missing condition an inactive planner code, a sourcing rule gap, or a collection scope omission can suppress the order entirely.

The planning engine does not raise an error when it skips an item; it simply produces no output for that combination. This makes the failure mode invisible until someone notices that inventory has dipped below the minimum with no purchase requisition, transfer order, or work order in the pipeline. The diagnosis starts by reconstructing the exact inputs the engine saw: the item's planning attributes, the current on-hand and projected available, the min-max values, and the sourcing configuration.

Verify the Item Planning Attributes

Open the item in the Product Information Management work area and confirm that the Planning tab has a planner assigned, a planning method that supports min-max (typically Min-Max or Min-Max with Safety Stock), and that the item is planned in the target organization. An item marked as Not Planned or assigned to a planner who is not included in the plan's planner filter will be skipped without notice.

Check the Min-Max Quantity fields: the minimum quantity triggers the order, and the maximum quantity defines the order-up-to level. If both are zero or null, the engine has no basis for calculation. Also verify the Fixed Order Quantity and Minimum Order Quantity fields if the calculated replenishment quantity falls below the minimum order quantity, the engine may suppress the order rather than generate an undersized one.

Confirm Sourcing Rules and Supply Sources

Min-max planning requires a valid sourcing rule to determine where the supply comes from. For purchased items, the sourcing rule must point to an approved supplier site with an active blanket purchase agreement or sourcing rule assignment. For transferred items, the rule must identify a source organization with an active shipping network. For manufactured items, a valid bill of material and routing must exist in the source organization.

A common failure occurs when the sourcing rule expires, the supplier site is inactivated, or the shipping network is disabled yet the item's min-max settings remain unchanged. The engine evaluates the sourcing rule at plan time; if no valid source resolves, it cannot create a requisition, transfer order, or work order. Review the Sourcing Rules work area and the Manage Sourcing Rules assignment for the item-organization combination.

Check Collection Scope and Data Freshness

The supply plan only knows what the collection process feeds it. If the collection scope excludes the inventory organization, the subinventory where stock resides, or the supplier-facing organization that receives purchase orders, the plan sees zero on-hand and zero scheduled receipts for that item. The projected available balance then reflects only demand, often triggering a min-max order that the planner cannot explain because the actual warehouse has stock.

Run the Collection Diagnostics report after the plan executes. Look for record counts in the On Hand, Purchase Order, Transfer Order, and Work Order collections. A sudden drop in collected records for a specific organization signals a scope change or an integration failure. Also verify the collection schedule: if the plan runs at 6 AM but the last collection completed at 10 PM the previous night, any receipts or issues between those times are invisible to the plan.

Evaluate Projected Available vs. Minimum

The min-max engine compares the projected available balance on-hand plus scheduled receipts minus demand against the minimum quantity. If the projected available is at or above the minimum, no order is generated. This is expected behavior, not a failure. The projected available includes firm planned orders, purchase orders, transfer orders, and work orders that are already in the pipeline.

To diagnose, open the Supply Plan workbench for the item and organization. Display the time-phased view with projected available, scheduled receipts, and the min-max minimum line. Identify the first bucket where projected available dips below the minimum. If no such bucket exists within the planning horizon, the engine correctly produces no order. If the bucket exists but no order appears, the issue lies in sourcing, planner filters, or plan options.

Review Plan Options and Planner Filters

The supply plan definition includes planner filters that restrict which planners' items are planned. If the item's planner is not in the filter, the item is excluded. Similarly, the plan's organization scope must include the target inventory organization. A plan defined for a single business unit will not plan items in organizations outside that unit.

Check the Plan Options for the specific plan: the planning horizon, the demand and supply time fences, and the setting for Generate Planned Orders. Some plans are configured to generate planned orders only for certain item categories or sourcing types. If min-max orders are expected to create purchase requisitions, verify that the plan option allows planned purchase orders and that the sourcing rule maps to a buy flow.

Inspect the Min-Max Calculation Logic

When the engine decides to order, it calculates the order quantity as: Maximum Quantity minus Projected Available Balance, rounded to the Fixed Order Quantity multiple if defined, and constrained by the Minimum Order Quantity. If the result is zero or negative, no order is created. This can happen when scheduled receipts already cover the gap between minimum and maximum, or when the maximum is set lower than the current projected available.

Also consider the planning calendar. The engine respects the organization's workday calendar for lead time offset. If the lead time pushes the order start date into a non-working period, the order may be deferred to the next working day, which can shift the projected available calculation. Verify the calendar assigned to the organization and the lead time on the sourcing rule or item. Oracle Supply Chain documentation

Conclusion

Min-max planning orders appear when every link in the chain is intact: the item is planned, the planner is in scope, the organization is collected, the sourcing rule resolves to a valid source, the projected available falls below the minimum, and the calculated order quantity is positive. In Fusion SCM Online Training, missing any one link yields silence, not an error. Walk the chain from item attributes through sourcing, collection, plan filters, and projected available arithmetic to find the broken link.

Once identified, the fix is usually a data correction adding the organization to the collection scope, reactivating a supplier site, updating the planner assignment, or adjusting the min-max values rather than a process change. The next plan run will then generate the expected replenishment orders.