How to separate usually in stock items?

One way to separate inventory parts that should normally be kept in stock from parts that should only be purchased when requested is to look at the Safety Stock and Warehouse/Location information.

• If a part has a Safety Stock quantity greater than zero, this is a strong indication that the part is expected to be kept in stock.

• If the part is physically stored in a specific Warehouse or Location, this can also indicate that the part is normally kept in inventory.

• On the other hand, if the part has no Safety Stock, no regular inventory quantity, and is only purchased when there is a specific demand, it can be considered a request-based / order-on-demand part.

However, Safety Stock alone should not be considered as the only criterion. A part may still be kept in stock using other planning parameters such as Minimum/Maximum Stock, Reorder Point, or MRP settings.

Therefore, Safety Stock can be used as the main indicator, while Warehouse/Location and other planning parameters can be used as supporting criteria.

Hi ​@ModinA 

In IFS Cloud this is controlled by how the part is planned and how demand is sourced, not by the stock level itself.

• Stocked parts (MTS): Set a replenishment-driven planning method on the Inventory Part Planning Data (e.g. Order Point, Order Up to, or an MRP method) and maintain Safety Stock, Order Point Qty and lot sizes. Demand is normally supplied from inventory (supply code Invent Order).
• Order-on-request parts (MTO): Don't rely on replenishment for these. Set the sales part's sourcing (sourcing option or sourcing rule) so the customer order line gets an order-driven supply code such as Shop Order for manufactured parts, Purch Order Direct/Transfer for purchased ones, or DOP Order for multi-level structures. Supply is then created against the specific demand.

Baran's indicators (safety stock > 0, defined location) are a good sanity check for the stocked group. For reporting, a part group or classification code lets you filter the two groups easily.