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 [2023/09/18 22:40] – [Store credentials] Adam Dewey | other_stuff:virtual_stores [2025/07/01 09:35] (current) – [Turn an existing customer into a store] Mark Glover | ||
---|---|---|---|
Line 38: | Line 38: | ||
{{ : | {{ : | ||
+ | You can customise the columns that show on this window. Click on the **Customise** button and this window will show: | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | The columns in the //Chosen// list are displayed in the table, the columns in the // | ||
==== Editing a store ==== | ==== Editing a store ==== | ||
+ | |||
Double-click on any store in the list in the View stores window described [[other_stuff: | Double-click on any store in the list in the View stores window described [[other_stuff: | ||
+ | |||
+ | <WRAP center round important 60%> | ||
+ | If you're working within a [[synchronisation: | ||
+ | </ | ||
+ | |||
==== 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. | ||
+ | |||
+ | As noted above, in a syncing system you must be logged into the central server to create a new store - it will be synced to any site where it is visible to any stores active on that site (which will also include the supplying store). When a store is created, it is made active on the central server by default - see [[synchronisation: | ||
+ | </ | ||
+ | |||
+ | <WRAP center round alert 90%> | ||
+ | <wrap em>After creating the new store, you will not be able to immediately log in to it.</ | ||
+ | </ | ||
+ | |||
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 68: | Line 90: | ||
=== Address details === | === Address details === | ||
- | + | Enter the address and contact details for the store in here if there are any. These details can be used in reports. Note that these fields will be copied to the **Main/ | |
- | Enter the address and contact details for the store in here if there are any. These details can be used in reports | + | |
+ | === Turn an existing customer into a store === | ||
+ | Only visible if you are creating a new store, not if you are editing an existing one. If this is checked then the **Name** field becomes a search field for the customer: enter the first few characters of the customer' | ||
+ | === Down arrow button === | ||
+ | Only visible if editing an existing store, not when creating a new one. Clicking this button will open the store' | ||
=== Disable this store === | === Disable this store === | ||
Line 93: | Line 119: | ||
Tags are used in several ways: | Tags are used in several ways: | ||
* for determining which programs a store can use. | * for determining which programs a store can use. | ||
- | * for contronlling | + | * for controlling |
* for reporting to group stores together. | * for reporting to group stores together. | ||
* | * | ||
Line 108: | Line 134: | ||
* Set the [[other_stuff: | * Set the [[other_stuff: | ||
* Set the store' | * Set the store' | ||
- | * Set the [[other_stuff: | + | * Set the [[other_stuff: |
- | * Setup Synchronisation if you are going to use a synced system. See [[other_stuff: | + | |
* Setup any [[other_stuff: | * Setup any [[other_stuff: | ||
* Set the master lists used by the store (a convenient method for controlling item visibility). | * Set the master lists used by the store (a convenient method for controlling item visibility). | ||
- | <WRAP center round alert 90%> | ||
- | If this newly created store will be ' | ||
- | </ | ||
==== Preferences tab ==== | ==== Preferences tab ==== | ||
+ | |||
<WRAP center round important 90%> | <WRAP center round important 90%> | ||
- | * The preferences tab is only visible if you are looking at the details of the store you are logged into. | ||
* The preferences described here are set 'per store' and can be different for each store in an mSupply datafile. | * The preferences described here are set 'per store' and can be different for each store in an mSupply datafile. | ||
- | * In a **synced system** | + | * In a **synced system** |
* Other preferences (accessed through **File > Preferences...**) apply to //all// stores in an mSupply datafile. | * Other preferences (accessed through **File > Preferences...**) apply to //all// stores in an mSupply datafile. | ||
* If you have to set the same preferences for lots of stores you might like to try the [[other_stuff: | * If you have to set the same preferences for lots of stores you might like to try the [[other_stuff: | ||
Line 151: | Line 173: | ||
^ Confirm customer invoices automatically| Set a New Customer Invoice status to confirmed when the OK button is clicked. This means that it is not possible to print a picking slip for the issued goods.| | ^ Confirm customer invoices automatically| Set a New Customer Invoice status to confirmed when the OK button is clicked. This means that it is not possible to print a picking slip for the issued goods.| | ||
^ Supplier invoices must be authorised| Turns on supplier invoice authorisation (i.e. goods can only be brought into stock when the action has been authorised). See [[other_stuff: | ^ Supplier invoices must be authorised| Turns on supplier invoice authorisation (i.e. goods can only be brought into stock when the action has been authorised). See [[other_stuff: | ||
- | ^ Confirm supplier invoices without asking | Set a New Supplier Invoice status to confirmed when the OK button is clicked. The goods are made available in stock without informing the user.| | + | ^ Confirm supplier invoices without asking | Sets a new Supplier Invoice status to confirmed |
+ | ^ Disallow adding expired stock to supplier invoices | If checked then a user will not be allowed to add stock which is already expired to a supplier invoice. If a user does this, they will be shown an alert message saying that the line is expired and they will not be allowed to save it. The same check is also performed when adding lines to a goods received note, an inventory adjustment - add or a customer credit. | | ||
^ Goods received lines must be authorised: | ^ Goods received lines must be authorised: | ||
^ Locations must be entered for goods received | A shelf location must be entered on the goods receipt item line form when receiving goods into stock. | | ^ Locations must be entered for goods received | A shelf location must be entered on the goods receipt item line form when receiving goods into stock. | | ||
Line 163: | Line 186: | ||
^ 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). | | + | ^ Keep requisition lines with zero requested quantity on finalise | If this is checked, 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 170: | Line 193: | ||
^ Allow users to choose diagnosis on prescriptions | When checked an additional **Diagnosis** drop down list is available on a prescription. See [[dispensing: | ^ Allow users to choose diagnosis on prescriptions | When checked an additional **Diagnosis** drop down list is available on a prescription. See [[dispensing: | ||
^ Use consumption and stock from customers for internal orders | If checked, when calculating the current stock and consumption figures (to calculate the suggested order quantity), the stock issued to all customers and the total stock of all customers will be used instead of the current stock and consumption of the current store. Note that customer stores are all those stores that have this store set as their supplying store. See the [[purchasing: | ^ Use consumption and stock from customers for internal orders | If checked, when calculating the current stock and consumption figures (to calculate the suggested order quantity), the stock issued to all customers and the total stock of all customers will be used instead of the current stock and consumption of the current store. Note that customer stores are all those stores that have this store set as their supplying store. See the [[purchasing: | ||
+ | ^ Items received on a purchase order must be within a minimum expiry date | When turned on, stock cannot be received if it has an expiry date that is before a date set on a purchase order. See [[https:// | ||
+ | ^ Store credentials are controlled on the central server | In a [[synchronisation: | ||
^ mobile: Alert if a patient is dispensed the same vaccine multiple times in a week | This preference only has an effect if this is an mSupply mobile store. See [[https:// | ^ mobile: Alert if a patient is dispensed the same vaccine multiple times in a week | This preference only has an effect if this is an mSupply mobile store. See [[https:// | ||
^ mobile: Enforce lookback period | This preference only has an effect if this is an mSupply mobile store. See [[https:// | ^ mobile: Enforce lookback period | This preference only has an effect if this is an mSupply mobile store. See [[https:// | ||
Line 232: | Line 257: | ||
* 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 258: | Line 305: | ||
==== Master lists tab and Visibility tab (controlling item visibility) ==== | ==== Master lists tab and Visibility tab (controlling item visibility) ==== | ||
- | Controlling the visibility of items in different stores is important because you can only order, distribute, receive goods for and report on items that are visible in your store. It's also important that stores don't have items visible that they don't use so that they don't accidentally order them etc. | + | |
+ | Controlling the visibility of items in different stores is important because you can only order, distribute, receive goods for, and report on items that are visible in your store. It's also important that stores don't have items visible that they don't use so that they don't accidentally order them etc. | ||
+ | |||
+ | <WRAP center round important 60%> | ||
+ | In a syncing system, item visibility and master lists can only be edited on the primary server => if it's a mirror sync system, then you'll need to create the store first on the central server and wait for it to sync to the primary. | ||
+ | </ | ||
If you have lots of stores in your data file, managing item visibility can turn into a difficult task. Thankfully, mSupply has some helpful tools to make it simple! There are 2 ways to manage item visibility and you use one or the other, not both: | If you have lots of stores in your data file, managing item visibility can turn into a difficult task. Thankfully, mSupply has some helpful tools to make it simple! There are 2 ways to manage item visibility and you use one or the other, not both: | ||
- automatically using the Master lists tab or | - automatically using the Master lists tab or | ||
- manually using the Visibility tab | - manually using the Visibility tab | ||
+ | |||
Each are useful in different situations and are described below. | Each are useful in different situations and are described below. | ||
=== Master lists tab === | === Master lists tab === | ||
- | If you have a lot of stores in mSupply, we recommend that you use master lists to control item visibility. Especially in a [[other_stuff: | + | |
+ | If you have a lot of stores in mSupply, and especially in a syncing system, we recommend that you use master lists to control item visibility, because it means that the visibility of newly created items will be automatically handled correctly. The visibility of items in a store whose visibility is controlled by master lists is immediately updated if any changes are made to any of the master lists. For instance, if a new item is added to a master list controlling visibility then that new item is made visible in all stores that use the master list. And any items deleted from the master list are made invisible in any store using that list. | ||
The first thing to do is to turn on the preference to make master lists control item visibility in stores. Do that in **File > Preferences...** on the //Item// tab - see [[preferences: | The first thing to do is to turn on the preference to make master lists control item visibility in stores. Do that in **File > Preferences...** on the //Item// tab - see [[preferences: | ||
Line 275: | Line 329: | ||
- Click on **Special > Show stores...** (or click on the //Stores// icon on the //Special// tab of the navigator) | - Click on **Special > Show stores...** (or click on the //Stores// icon on the //Special// tab of the navigator) | ||
- Double-click the store who's visibility you would like to manage:{{ : | - Double-click the store who's visibility you would like to manage:{{ : | ||
- | - Click on the //Master lists// tab: {{ : | + | - Click on the //Master lists// tab: |
- Select which master list(s) you would like to control the visibility of items in your chosen store by checking their checkbox in the //Use master list// column: {{ : | - Select which master list(s) you would like to control the visibility of items in your chosen store by checking their checkbox in the //Use master list// column: {{ : | ||
- Click the **OK** button to finish. As soon as you do that the items on the selected master list(s) are made visible in the store and any items **not** on the selected master list(s) are made **invisible**. Any new items added to the selected master list(s) will be made visible in the store and any items removed form the master list(s) will be made invisible in the store. | - Click the **OK** button to finish. As soon as you do that the items on the selected master list(s) are made visible in the store and any items **not** on the selected master list(s) are made **invisible**. Any new items added to the selected master list(s) will be made visible in the store and any items removed form the master list(s) will be made invisible in the store. | ||
+ | |||
+ | **NOTE:** Assigning master lists to stores can also be done on a master list's details window. See the [[items: | ||
=== Visibility tab === | === Visibility tab === | ||
+ | |||
<WRAP center round important 90%> | <WRAP center round important 90%> | ||
- | If your system is a Sync system | + | In a syncing |
</ | </ | ||
<WRAP center round tip 90%> | <WRAP center round tip 90%> | ||
- | You will also // | + | You will // |
</ | </ | ||
Line 295: | Line 352: | ||
If you have turned on the [[preferences: | If you have turned on the [[preferences: | ||
</ | </ | ||
- | |||
Here's what the tab looks like: | Here's what the tab looks like: | ||
Line 334: | Line 390: | ||
==== Names tab ==== | ==== Names tab ==== | ||
- | This tab shows a list of all the names (customers, suppliers, stores, donors, manufacturers etc.) in the datafile and which are visible in this store. You are also able to edit the visibility of names: | ||
- | {{ : | + | This tab shows a list of all the customers, suppliers and stores (collectively called " |
+ | |||
+ | {{ : | ||
The table shows whether the name is a customer or supplier (or both). The checkboxes in the **Visible in this store** column are editable. If checked then the name is visible in this store, if unchecked then the name is not visible in this store. Click on one of the checkboxes to change its state. | The table shows whether the name is a customer or supplier (or both). The checkboxes in the **Visible in this store** column are editable. If checked then the name is visible in this store, if unchecked then the name is not visible in this store. Click on one of the checkboxes to change its state. | ||
- | * **Store checkbox:** If checked then names thast are stores are shown in the table | + | * **Store checkbox:** If checked then names that are stores are shown in the table |
- | * **Facility | + | * **Customer |
- | * **Search names field:** If you type in here then only names that contain what you type will be displayed in the list. Useful if you want to find a particular name or group of names in a long list. | + | * **Supplier checkbox:** If checked then names that are suppliers |
+ | * **//Search names// field:** If you type in here then only names that contain what you type will be displayed in the list. Useful if you want to find a particular name or group of names in a long list. | ||
* **All off button:** Clicking this will uncheck all the checkboxes in the **Visible in this store** column (so making all names invisible in this store) and the button will change to **All on**. Clicking it then will check all the checkboxes in the column (and therefore make all names visible in this store). | * **All off button:** Clicking this will uncheck all the checkboxes in the **Visible in this store** column (so making all names invisible in this store) and the button will change to **All on**. Clicking it then will check all the checkboxes in the column (and therefore make all names visible in this store). | ||
* **Copy button:** Copies the current state of all the checkboxes in the **Visible in this store** column. | * **Copy button:** Copies the current state of all the checkboxes in the **Visible in this store** column. | ||
Line 349: | Line 407: | ||
Clicking on the **OK**, **OK & Next** or **OK & Previous** buttons will save any changes you make on this tab. | Clicking on the **OK**, **OK & Next** or **OK & Previous** buttons will save any changes you make on this tab. | ||
==== Deleting a store ==== | ==== Deleting a store ==== | ||
- | To delete a store, click on the //Delete// button in the View stores window. **Note:** deletion of a store is a serious thing to do and is only possible when that store contains zero stock and there have been no transactions recorded. mSupply will check and tell you that deletion is not possible if these criteria are not met. If you can't meet these criteria and you still want to stop people using the store then you can [[other_stuff: | + | |
+ | To delete a store, click on the //Delete// button in the View stores window. **Note:** deletion of a store is a serious thing to do and is only possible when that store contains zero stock and there have been no transactions recorded. mSupply will check and tell you that deletion is not possible if these criteria are not met. If you can't meet these criteria and you still want to stop people using the store then you can [[other_stuff: | ||
<WRAP center round alert 60%> | <WRAP center round alert 60%> | ||
- | If the store is **Active** on a sync satellite | + | If the store is **Active** on another |
</ | </ | ||
Line 378: | Line 437: | ||
* mSupply may prevent the merge due to unfinalised CIs from other stores in the system. | * mSupply may prevent the merge due to unfinalised CIs from other stores in the system. | ||
* These can be hard to find on a multi-store system where the transactions could have come from a number of places. | * These can be hard to find on a multi-store system where the transactions could have come from a number of places. | ||
- | * If these transactions are on a number of stores on satellite | + | * If these transactions are on a number of stores on remote |
* These inconveniences are why the [[other_stuff: | * These inconveniences are why the [[other_stuff: | ||
</ | </ | ||
Line 386: | Line 445: | ||
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 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. | ||
- | </ | ||
<WRAP center round alert 60%> | <WRAP center round alert 60%> | ||
Line 398: | Line 454: | ||
- Log into a store that will have the same or similar user and group permissions as the new store. | - Log into a store that will have the same or similar user and group permissions as the new store. | ||
- **Customer > Show customers...** to find the customer that you want to convert into a store and copy the Name. This will ensure that you are converting the correct name into a store - see warning below! | - **Customer > Show customers...** to find the customer that you want to convert into a store and copy the Name. This will ensure that you are converting the correct name into a store - see warning below! | ||
- | - **Special > Show stores... > New Store** | + | - **Special > Show stores... > New Store** |
+ | User store login permissions are **NOT** copied to the new store. | ||
+ | </ | ||
- Click on the **Turn an existing customer into a store** checkbox | - Click on the **Turn an existing customer into a store** checkbox | ||
- Enter the existing customer name into the **Name** field. | - Enter the existing customer name into the **Name** field. |