All stock movements made from or to stock instances are recorded. The date, quantity and type of each movement are recorded. For the most part, these records are created and maintained automatically as you do things. The table below describes each of the movement types.
Book-in |
This represents stock being added to the instance from a works order or a purchase order. The system can show you the associated works order or purchase order and, in the case of a completed purchase, the supplier’s delivery note. |
Issue |
This represents stock being taken out of the instance and issued to a works order or a sub-contract purchase order. The system can show you the associated works order or purchase order. |
Dispatch |
This represents stock being taken out of the instance and dispatched to a customer against a sales order. The system can show you the associated sales order and, in the case of a completed dispatch, your dispatch note. |
Demand |
This represents stock being allocated from an instance against a sales contract. The system can show you the associated sales contract. |
Supplier reject |
This represents stock being taken out of the instance and sent back to the supplier. The stock will have been originally added via an earlier book-in movement on the same instance. This is usually done as a result of an inspection failure. The system can show you the original purchase order used to buy the returned stock. |
Customer return |
This represents stock being added to the instance as a result of a customer return. The stock will have been originally taken out via an earlier dispatch movement on the same instance. The system can show you the original sales order and your original dispatch note. |
Fail |
This represents stock being taken out of the instance because it has failed an inspection. You can record the location to where it was moved. |
Un-fail |
This represents stock being added to the instance as a result of re-working some previously failed stock from the same instance. |
Adjust In |
This represents stock being added to the instance to correct errors, as a result of a stock take, for example. It is treated like an ‘un-issue’. |
Adjust Out |
This represents stock being taken out of the instance to correct errors, as a result of a stock take, for example. It is treated as an anonymous ‘issue’. |
Scrap |
This represents stock being taken out of the instance because you have thrown it away. |
Defective |
This is used to record failures within the instance that where not discovered until after the stock was used. In this situation, you cannot fail the stock because it is no longer there to fail. The significance of marking part of the instance as defective is that it allows you to raise a Supplier Reject note. |
The book-in, issue, demand and dispatch movement types also have a state that is ether reserved or committed or done. The state of all the other movement types is always done.
A reserved movement is one that has been planned. It represents an intention. The associated date defines when the movement is planned for.
A committed movement on a book-in indicates the order that will create the stock has been raised, but not yet completed. It represents work in progress. The associated date defines when the order is expected to complete.
A committed movement on an issue indicates the stock is being issued to an order that has been started ‘early’. This means the kit was not available, but the order was approved anyway. The associated date defines when the issue is expected to actually happen. It will be upgraded to done when the stock being issued arrives.
A demand or dispatch movement is never given the committed state.
A done movement indicates the stock movement has actually taken place. The associated date defines when it happened.