Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
other_stuff:virtual_stores [2023/02/10 12:33] – [Preferences tab] Gary Willetts | other_stuff:virtual_stores [2023/12/12 16:53] – [Location code pattern] Gary Willetts | ||
---|---|---|---|
Line 42: | Line 42: | ||
==== Creating new stores ==== | ==== Creating new stores ==== | ||
+ | <WRAP center round important 60%> | ||
+ | This new store will inherit the same user and group permissions (but not login permissions!) as the store which you are logged in to when you execute it. It is therefore worth logging in to a store that has similar user and group permissions to those that you want to have in the new store. | ||
+ | </ | ||
To create a new store click the **New store** button in the Store list window shown [[other_stuff: | To create a new store click the **New store** button in the Store list window shown [[other_stuff: | ||
Line 87: | Line 90: | ||
* The // | * The // | ||
- | * The // | + | * The // |
If you need to view the password you have entered to check it is correct, click on the {{: | If you need to view the password you have entered to check it is correct, click on the {{: | ||
Line 137: | Line 140: | ||
|<100% 40%>| | |<100% 40%>| | ||
- | ^ Sort available batches by VVM status|If the store is only to be used for vaccines, you can sort the list of available batches by vaccine status rather than expiry date.| | + | ^ Sort available batches by VVM status |
^ Patients created in other stores not visible in this store| If this is checked, patients that are created in other stores across all sites will not be visible in this store. If it is **off**, all patients from all stores from all sites will be visible to this store. It is set to true by default when a store is created. **USE CAUTION:** Turning this **OFF** for many stores does not scale well and can overload the sync system. See the [[dispensing: | ^ Patients created in other stores not visible in this store| If this is checked, patients that are created in other stores across all sites will not be visible in this store. If it is **off**, all patients from all stores from all sites will be visible to this store. It is set to true by default when a store is created. **USE CAUTION:** Turning this **OFF** for many stores does not scale well and can overload the sync system. See the [[dispensing: | ||
^ Names created in other stores not visible in this store| If this is checked, names (customers, suppliers, manufacturers, | ^ Names created in other stores not visible in this store| If this is checked, names (customers, suppliers, manufacturers, | ||
Line 160: | Line 163: | ||
^ Use remote authorisation for response requisitions | Turns on remote authorisation for response requisitions. See [[other_stuff: | ^ Use remote authorisation for response requisitions | Turns on remote authorisation for response requisitions. See [[other_stuff: | ||
^ Include requisitions from this store in suppliers' | ^ Include requisitions from this store in suppliers' | ||
- | ^ Can manually link requisition to supplier invoice | When receiving stock, users can match the supplier invoice to the initial requisition. They can then add items from the linked requisition, | + | ^ Can manually link requisition to supplier invoice | When receiving stock, users can match the supplier invoice to the initial requisition. They can then add items from the linked requisition, |
^ Automatically populate supply quantities with requested quantities | On requisitions, | ^ Automatically populate supply quantities with requested quantities | On requisitions, | ||
^ Show extra fields on requisitions | When a line is selected on a response requisition, | ^ Show extra fields on requisitions | When a line is selected on a response requisition, | ||
+ | ^ Keep requisition lines with zero requested quantity on finalise | If this is checkled, lines on requisitions that have zero requested quantity are kept when the requisition is finalised. Otherwise they are deleted (normal behaviour). | | ||
^ Show comment field when entering supplier invoice lines | Allows users to type a comment for individual items received on a supplier invoice. | | ^ Show comment field when entering supplier invoice lines | Allows users to type a comment for individual items received on a supplier invoice. | | ||
^ Use EDD placeholder lines in supplier invoices from this store | If turned on, any placeholder lines on a customer invoice that is a stock transfer are duplicated on the supplier invoice in the receiving store when the customer invoice is finalised. The placeholder lines in the supplier invoice appear on an // | ^ Use EDD placeholder lines in supplier invoices from this store | If turned on, any placeholder lines on a customer invoice that is a stock transfer are duplicated on the supplier invoice in the receiving store when the customer invoice is finalised. The placeholder lines in the supplier invoice appear on an // | ||
Line 191: | Line 195: | ||
== Threshold for understock == | == Threshold for understock == | ||
- | The number of months of stock that an item must have less of to be considered understocked i.e. in danger of not having enough to meet demand. An alert is triggered for an item is the total quantity in stock(including all batches) divided by the average monthly consumption of the item (calculated using the last 12 months' | + | Also called <wrap em> |
- | This alert should only be triggered when your stock levels fall below your buffer stock levels. | + | This alert should only be triggered when your stock levels fall below your buffer stock levels. |
</ | </ | ||
Line 231: | Line 235: | ||
* 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. | ||
+ | |||
+ | === Location code pattern === | ||
+ | This is used with phased stocktakes (see the [[items: | ||
+ | |||
+ | An aisle is a whole row of racking like this: | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | A level is a horizontal level of the racking like this: | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | And a position is a vertical column of the racking like this: | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | Use the letters A, L and P to represent the aisle, level and position parts of the location code. | ||
+ | |||
+ | Let's use an example to show how it works. Let's say that the shelf location codes are in the format B01.C.01 where B01 represents the aisle, C represents the position and 01 represents the level. Then in the **Location code pattern** text box you would enter the text **AAA.P.LL** | ||
+ | |||
+ | It doesn' | ||
+ | |||
==== Logo tab ==== | ==== Logo tab ==== | ||
Line 385: | Line 411: | ||
Due to the limitations of the method described above, from mSupply v5.02 onwards, you can choose to convert an existing customer into a store, and thereby retain all of its properties. | Due to the limitations of the method described above, from mSupply v5.02 onwards, you can choose to convert an existing customer into a store, and thereby retain all of its properties. | ||
- | <WRAP center round important | + | |
- | This new store will inherit | + | <WRAP center round alert 60%> |
+ | If the name is not visible to the store that you are logged in to, this method will not work! First make the name visible, then start this process... | ||
</ | </ | ||
+ | |||