import_and_export:importing_requisitions

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_requisitions [2021/08/11 11:49] – [Import spreadsheet format] Gary Willettsimport_and_export:importing_requisitions [2021/10/08 09:32] (current) – Gary Willetts
Line 1: Line 1:
 {{indexmenu_n>96}} {{indexmenu_n>96}}
  
-====== 16.11. Importing requisitions ======+====== 17.11. Importing requisitions ======
 This is a way to import standard customer requisitions (response). Requisitions created by this import are not connected to any internal order. You cannot import internal orders (request requisitions), customer stock history requisitions or imprest requisitions. This is a way to import standard customer requisitions (response). Requisitions created by this import are not connected to any internal order. You cannot import internal orders (request requisitions), customer stock history requisitions or imprest requisitions.
  
Line 17: Line 17:
 | 5              | E              | Customer current stock on hand  | Optional. Integer. The number of units of the item (not packs) the customer currently has in stock. If there is no value in this column, it is assumed to be 0. | | 5              | E              | Customer current stock on hand  | Optional. Integer. The number of units of the item (not packs) the customer currently has in stock. If there is no value in this column, it is assumed to be 0. |
 | 6              | F              | Quantity requested              | **Mandatory**. Integer. The number of units (not packs) of the item that the customer is requesting. | | 6              | F              | Quantity requested              | **Mandatory**. Integer. The number of units (not packs) of the item that the customer is requesting. |
 +
 +Rows belonging to the same requisition must all be grouped together in the spreadsheet; mSupply will interpret a change in customer code to mean that this row is for a new requisition. 
  
 Here is an example spreadsheet you can use (contains no property columns, only the standard mSupply columns): {{ :import_and_export:requisition_import_blank_template.xlsx |}} Here is an example spreadsheet you can use (contains no property columns, only the standard mSupply columns): {{ :import_and_export:requisition_import_blank_template.xlsx |}}
Line 24: Line 26:
 Choose //File > Import > Import requisitions// from the menus and you will be asked to select the import file from a file window. After you have selected the file (if it is valid) you will be shown this window: Choose //File > Import > Import requisitions// from the menus and you will be asked to select the import file from a file window. After you have selected the file (if it is valid) you will be shown this window:
  
-{{ :import_and_export:screenshot_2021-04-19_at_15.35.02.png?600 |}}+{{ :import_and_export:screenshot_2021-08-11_at_15.42.11.png?400 |}}
  
-mSupply uses the **code** field to determine whether the asset being imported is a duplicate; an asset with the same code as one already in the database is determined to be a duplicate. Any assets with no code are ignored during duplicate checking i.e. an asset with no code can //never// be a duplicate and will always be imported as a new asset. In the //If duplicate codes are detected// section you tell mSupply what to do if it encounters a duplicate asset during the import: +The //Value// column shows the values mSupply has found in the cells for that row of the spreadsheet. You can move through the rows of the spreadsheet using the **Previous** and **Next** buttons. If you try to go beyond the first or last row of the spreadsheet mSupply will let you know.
-  * **Import as new asset:** this option will import the duplicate as a new asset +
-  * **Skip the duplicate without asking:** the duplicate will not be imported and that row of the spreadsheet will be ignored +
-  * **Stop the import:** as soon as a duplicate is encountered, the import will stop and all assets imported so far will be removed so that nothing is imported. +
-  * **Update the existing asset:** the asset that already exists with the code in the database will be updated with the information contained in the spreadsheet row. A new asset will not be created. BE CAREFUL WITH THIS OPTION: if a cell is blank in the spreadsheet then the corresponding value is removed from the asset (if it had a value set for it), not left as it is. +
- +
-The //Field// column of the table shows you all the columns that mSupply has detected in your import file, the //Value// column shows the values it has found in the cells for that row of the spreadsheet. You can move through the rows of the spreadsheet using the **Previous** and **Next** buttons. If you try to go beyond the first or last row of the spreadsheet mSupply will let you know.+
  
 You can carry out the import by clicking on the **Import now** button or cancel it by clicking on the **Cancel** button. You can carry out the import by clicking on the **Import now** button or cancel it by clicking on the **Cancel** button.
  
-When the import has finished you will be shown a message telling you how many assets were imported and how many rows of the spreadsheet were skipped, ignored or failed. +When the import has finished you will be shown a message telling you how many requisitions were imported. If there is an error (a customer code or item code doesn't exist or a mandatory column value is not present) you will be told what the error is and the import will be cancelled (nothing will be imported). In this case, correct the error in the spreradsheet and try the import again.
- +
-<WRAP info center round 90%> +
-All the assets created by the import will have the text "Created by import on //xx/xx/xxxx//" (where //xx/xx/xxxx// is the date of the import) appended to the end of their //Notes// field. +
-</WRAP>+
  
 \\ \\
  • Last modified: 2021/08/11 11:49
  • by Gary Willetts