Floor stock is defined as items that are used in large quantities and have a low per unit cost. In many cases, we literally make sure this stock is always available on the manufacturing floor and does not have to be picked from any warehouse shelf.
The key driver in this scenario is that we want an absolute minimum of transactions for floor stock as the cost of doing transactions can easily become higher then the cost of the item itself.
What are the unique requirements for the behavior of floor stock items in Microsoft Dynamics 365 for Finance and Operations (D365FO)? (It will be the same for any ERP system.)
It turns out that the almost perfect fit for floor stock behavior is a “stocked” service item. The “stocked” checkbox in the Item model group has to be checked to allow a service item in the BOM. (NOTE: no “stocked” checkbox existed in versions before AX2012.) But it certainly does not mean we “stock’ this service item. It’s quite the opposite. The system has no idea of the on-hand of our floor stock items.
NOTE: “Non-stocked” service items are service charges like freight that can only be used in Purchase or Sales orders
Let’s review the behavior of “stocked” service items in D365FO:
So why an “almost” perfect fit? Because we can never change our mind on floor stock items that were set up as service items. Service items can never become a regular item again (for versions before AX2012 this is different. One could convert a service item to a regular item and vice versa). This may be a minor thing for most manufacturing companies. One should know rather precisely when something should be setup as a floor stock item. For example, there are nuts and bolts that can be quite expensive. These should not be set up as floor stock service items. A simple cost rule should be followed, such as “anything less than $2 USD,” to decide whether to make it a floor stock service item.
To meet the requirements of floor stock behavior using regular items, we have to take some special measures:
The difference with the first alternative is that we do not set up this item for advanced warehousing. It will transact in an advanced warehouse the traditional way, which means no picking is required. The floor stock item will be backflushed just like in the first alternative. This is a significant improvement over the first alternative solution. Yet the fact that we have to keep on-hand inventory remains a big negative. The service item approach remains the winner.
Floor stock items have a low cost, yet they can be consumed in big numbers and, in a piece of equipment, their total cost can become substantial. Cost accounting wants to see that cost. This means we have to put these items on the BOM. To minimize the setup and the transactions, the best choice is to set them up as a service item.
One word of caution regarding the flushing principle “Finish,” and the use of the menu item on the handheld terminal “Report as finished and put away.” We found that the handheld menu item is checking for inventory for a service item on the Prod-BOM if it is the only item with flushing principle “Finish.” It will generate the error “not enough inventory” and will not do the RAF transaction. If there are other, non-service items, with the “Finish” principle in the Prod-BOM, it works fine. We are investigating this as a bug. For now use “start” as your flushing principle for your service item.
Need help with your Dynamics 365 for Finance and Operations solution? Contact our team of experts today!
This publication contains general information only and Sikich is not, by means of this publication, rendering accounting, business, financial, investment, legal, tax, or any other professional advice or services. This publication is not a substitute for such professional advice or services, nor should you use it as a basis for any decision, action or omission that may affect you or your business. Before making any decision, taking any action or omitting an action that may affect you or your business, you should consult a qualified professional advisor. In addition, this publication may contain certain content generated by an artificial intelligence (AI) language model. You acknowledge that Sikich shall not be responsible for any loss sustained by you or any person who relies on this publication.