Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| other_stuff:virtual_stores [2026/01/05 09:47] – [Preferences tab] Gary Willetts | other_stuff:virtual_stores [2026/02/16 12:57] (current) – [Visibility tab] Gary Willetts | ||
|---|---|---|---|
| Line 206: | Line 206: | ||
| ^ Pickface replenishments must be authorised | If checked, pickface replenishments in this store must be authorised by a user who has permission to authorise them before they can be finalised. See the [[items: | ^ Pickface replenishments must be authorised | If checked, pickface replenishments in this store must be authorised by a user who has permission to authorise them before they can be finalised. See the [[items: | ||
| ^ Able to specify VVM status when receiving items | If checked then a new **VVM status** field will be available on a supplier invoice for the user to select the current VVM status of the batch when it is received on a supplier invoice or inventory adjustment. See the [[receiving_goods: | ^ Able to specify VVM status when receiving items | If checked then a new **VVM status** field will be available on a supplier invoice for the user to select the current VVM status of the batch when it is received on a supplier invoice or inventory adjustment. See the [[receiving_goods: | ||
| - | ^ Finalise stock transfer supplier invoice automatically | If this is checked, supplier invoices that are created in this store as the receiving side of a stock transfer are automatically received into stock and finalised. This is set in the **receiving** store. | + | ^ Finalise stock transfer supplier invoice automatically | If this is checked, supplier invoices that are created in **this store** as the receiving side of a stock transfer are automatically received into stock and finalised. This is set in the **receiving** store. |
| === Notification preferences === | === Notification preferences === | ||
| These are used by the notification/ | These are used by the notification/ | ||
| Line 250: | Line 250: | ||
| How you set this preference is determined by how separate your goods receiving and finance sections are. If they are not in the same building, you might want to use the " | How you set this preference is determined by how separate your goods receiving and finance sections are. If they are not in the same building, you might want to use the " | ||
| - | === For stock transfers, the supplier invoice in the receiving store should be...=== | + | table at the to=== For stock transfers, the supplier invoice in the receiving store should be...=== |
| <WRAP center round important 60%> | <WRAP center round important 60%> | ||
| This option applies to all stores that this store transfers stock **to**. | This option applies to all stores that this store transfers stock **to**. | ||
| </ | </ | ||
| - | This option is used to determine whether stock transferred from one store to another is received to a destination store and automatically introduced to stock or not. The **On hold** option prevents stock from being introduced, while the **Finalised** option automatically makes the stock available for use in the destination store - //**without the receiving store having the opportunity to amend the Goods Receipt**// | + | This option is used to determine whether stock transferred from this store (the sender) |
| * Choose **Finalised** if there is no need to check / alter the quantity received compared to what was sent. | * Choose **Finalised** if there is no need to check / alter the quantity received compared to what was sent. | ||
| * Choose **On hold** if the store is being used by mSupply mobile, and the goods receipt needs to be confirmed before receiving. | * Choose **On hold** if the store is being used by mSupply mobile, and the goods receipt needs to be confirmed before receiving. | ||
| + | |||
| + | This preference is set in the **sending** store. There is another preference that can be set in the **recipient** store that will do the same thing but from the recipient' | ||
| === Location code pattern === | === Location code pattern === | ||
| Line 359: | Line 361: | ||
| The buttons provide you with different ways to hide and show items and names in the store (Note: be careful showing names in databases that have a lot of names records. For example if you have 20 virtual stores and 200,000 names in your database, showing all names in all stores will create 4 million (20x200, | The buttons provide you with different ways to hide and show items and names in the store (Note: be careful showing names in databases that have a lot of names records. For example if you have 20 virtual stores and 200,000 names in your database, showing all names in all stores will create 4 million (20x200, | ||
| * The **Show stats** button shows how many items and names are currently hidden and visible | * The **Show stats** button shows how many items and names are currently hidden and visible | ||
| - | * The **Set item visibility to match master lists for this store** button matches the item visibility to the master lists that are selected on the //Master lists// tab. (Note: this is a one-off operation, no changes will be made to item visibility if the master lists are changed after you click this button. See the section above if you want that to happen!) If there are some items that can' | + | * The **Set item visibility to match master lists for this store** button matches the item visibility to the master lists that are selected on the //Master lists// tab. (Note: this is a one-off operation, no changes will be made to item visibility if the master lists are changed after you click this button. See the section above if you want that to happen!) If using this button makes some items that have stock invisible, they will be made invisible (so that they can't be re-ordered |
| * The **Make all items in this store visible** and **Make all items in this store invisible** both do just as they say. | * The **Make all items in this store visible** and **Make all items in this store invisible** both do just as they say. | ||
| * The **Set pack to one for all visible items in this store** will check the //Allow pack to 1 conversion// | * The **Set pack to one for all visible items in this store** will check the //Allow pack to 1 conversion// | ||