Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
import_and_export:importing_locations [2018/07/31 04:34] – [Importing locations] Ujwal Khatryimport_and_export:importing_locations [2025/08/09 11:15] (current) – [17.07. Importing locations] Mark Glover
Line 1: Line 1:
 {{indexmenu_n>70}} {{indexmenu_n>70}}
-====== Importing locations ======+====== 17.07. Importing locations ====== 
 +Locations are the labelled places in your warehouse where you store stock. Locations can be created individually (see [[items:item_locations|here]]) or can be created automatically when you import stock (see [[import_and_export:import_items_and_stock|here]]). The functionality to import locations described here will save you a lot of time if you need to put a lot of locations into mSupply separately from importing stock.
  
 +This import uses a <wrap em>tab delimited text file</wrap> (easily produced by exporting a spreadsheet from Excel or other spreadsheet programme). The columns that must be present in the file and their contents are as follows:
  
-Locations are the labelled places in your warehouse where you store stock. Locations can be created individually (see [[items:item_locations|here]]) or can be created automatically when you import stock (see [[import_and_export:import_items_and_stock|here]]). The functionality to import locations described here will save you a lot of time if you need to put a lot of locations into mSupply separately from importing stock.+<WRAP  center round important 60%>All columns must be present in the import file but only the first 2 (Location code and Store code or nameare mandatoryIf either of these fields do not have values entered then the line will be ignored.</WRAP>
  
-As with the other import features of mSupply, this import uses a tab delimited text file (easily produced by exporting a spreadsheet from Excel or other spreadsheet programme). The columns that must be present in the file and their contents are as follows:+<WRAP center round alert 60%> 
 +The import must take place when the user is logged in to the store on the site where the store is Active 
 +</WRAP>
  
-<WRAP  center round important 60%>All columns must be present in the import file but only the first 2 (Location code and Store code or name) are mandatory. If either of these fields do not have values entered then the location will be ignored.</WRAP> 
  
-^ Column number  ^ Column letter  ^ Field  ^ Description ^ +^ Column ^ Field  ^ Description ^ 
-| 1 | A | Location code        | The code of the location. This is used to identify and select the location throughout mSupply and is the label you apply to the location in your warehouse e.g. "A01or "A01.03.C". | +| A | Location code        | The code of the location. This is used to identify and select the location throughout mSupply and is the label you apply to the location in your warehouse e.g. ''A01'' or ''A01.03.C''. | 
-| 2 | B | Store code or name   | The code or name of the store the location is to be created in. You can see the list of store names and their codes currently in your copy of mSupply by going to //Special > Show stores...// | +| B | Store code or name   | The code or name of the store the location is to be created in. You can see the list of store names and their codes currently in your copy of mSupply by going to //Special > Show stores...// | 
-| 3 | C | Location description | For your reference only, a longer description of the location e.g. "Aisle A, shelf 1, position C". | +| C | Location description | For your reference only, a longer description of the location e.g. ''Aisle A, shelf 1, position C''. | 
-| 4 | D | Volume               | The total storage volume of the location in m<sup>3</sup> (cubic metres). | +| D | Volume               | The total storage volume of the location in m<sup>3</sup> (cubic metres). | 
-| 5 | E | Priority             | A whole number from 0 upwards. This is used when printing a picking slip. Setting a priority for a location will override the default //alphabetical// ordering of shelf locations in a picking list. A location with a lower priority number will be printed before a location with a higher priority number. All locations with 0 priority are counted as having no priority and will be printed, in alphabetical order, //after// all locations with a priority. | +| E | Priority             | A whole number from 0 upwards. This is used when printing a picking slip. Setting a priority for a location will override the default //alphabetical// ordering of shelf locations in a picking list. A location with a lower priority number will be printed before a location with a higher priority number. All locations with 0 priority are counted as having no priority and will be printed, in alphabetical order, //after// all locations with a priority. | 
-| 6 | F | Is summary location  | Whether the location is a summary location that cannot hold stock. ''y'', ''yes'', ''t'' or ''true'' is interpreted as true, anything else (including nothing) is interpreted as false. | +| F | Is summary location  | Whether the location is a summary location that cannot hold stock. ''y'', ''yes'', ''t'' or ''true'' is interpreted as true, anything else (including nothing) is interpreted as false.  <WRAP center round important 60%> 
-| G | Location type        | The name of the location type for this location (must be an exact match and the location type must already exist in mSupply, otherwise the location will be created with no location type)| +As of August 2025, the summary location field exists in mSupply, but it has no functionality. 
-| H | Parent location code or description | The code or description of the location which is a parent to this one. If the parent does not already exist in mSupply the location will be imported without the parent. Please make sure that the parent location are imported first. |+</WRAP>  | 
 +| G | Location type        | The location type for this location.  <WRAP center round important 60%> 
 +This text must be an exact match for an existing location type in mSupply, otherwise the location will be created with no location type. 
 +</WRAP>  
 +| H | Parent location code or description | The code or description of the location which is a parent to this one. If the parent does not already exist in mSupply the location will be imported without the parent.  Make sure that the parent location is imported first! <WRAP center round important 60%> 
 +As of August 2025, the parent / child location feature does not function. 
 +</WRAP> |
  
 An empty Excel spreadsheet containing these columns for you to use as a template is here: {{:import_and_export:location_import_template.xlsx|}} An empty Excel spreadsheet containing these columns for you to use as a template is here: {{:import_and_export:location_import_template.xlsx|}}
Line 37: Line 46:
 When you're ready to carry out the import, click on the //OK// button. mSupply will carry out the import and tell you how many locations were imported, how many already in mSupply were modified and if there were any errors. You can see more details by viewing the log (see [[admin:the_log|The log]]). When you're ready to carry out the import, click on the //OK// button. mSupply will carry out the import and tell you how many locations were imported, how many already in mSupply were modified and if there were any errors. You can see more details by viewing the log (see [[admin:the_log|The log]]).
  
 +<WRAP info center round 60%>
 +If there are non-printable characters before or after the location description or code they will be removed. Any non-printable characters in the description or code will be replaced with an underscore (<wrap em>_</wrap>).
 +</WRAP>
  
-// Previous: [[import_and_export:importing_customer_budgets|Importing customer budgets]]     Next: [[import_and_export:export_invoice|Exporting invoices]]//+\\ 
 +\\ 
 +|  //  Previous:  **[[import_and_export:importing_customer_budgets]]** | | Next: **[[import_and_export:importing_a_supplier_invoice]]** //  |
 ---- struct data ---- ---- struct data ----
 +pagestatus.status    : 
 ---- ----
  
  • Last modified: 2018/07/31 04:34
  • by Ujwal Khatry