Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
integration:elmis_interface [2019/10/28 20:09] – [Error file format] Emily Porrello | integration:elmis_interface [2022/03/15 10:26] (current) – Gary Willetts | ||
---|---|---|---|
Line 1: | Line 1: | ||
{{indexmenu_n> | {{indexmenu_n> | ||
- | ====== | + | ====== |
- | + | eLMIS stands for **E**lectronic **L**ogistics **M**anagement | |
- | + | ||
- | This is a work in progress - will be completed soon! | + | |
- | + | ||
- | eLMIS stands for **E**lectronic **L**ogistics **M**anagement **S**ystem and is a piece of software | + | |
===== Setup ===== | ===== Setup ===== | ||
Line 20: | Line 16: | ||
==== 2. Enter the setup information into mSupply ==== | ==== 2. Enter the setup information into mSupply ==== | ||
- | Go to the eLMIS tab of // | + | Go to the mSupply Special |
+ | |||
+ | ==== 3. Setup the customer budgets in mSupply ==== | ||
+ | The interface | ||
- | ==== 3. Setup eLMIS ==== | + | ==== 4. Setup eLMIS ==== |
- Set eLMIS to export its order files to the //main folder/// | - Set eLMIS to export its order files to the //main folder/// | ||
- Set eLMIS to look for incoming shipment files in the //main folder/// | - Set eLMIS to look for incoming shipment files in the //main folder/// | ||
Line 44: | Line 43: | ||
If the order is successfully converted into a customer invoice the eLMIS order file is moved from //main folder/// | If the order is successfully converted into a customer invoice the eLMIS order file is moved from //main folder/// | ||
- | If there is a problem and the order file is not converted into a customer invoice then the order file is moved to //main folder/// | + | If there is a problem and the order file is not converted into a customer invoice then the order file is moved to //main folder/// |
==== 2. Creates eLMIS shipment files for confirmed customer invoices ==== | ==== 2. Creates eLMIS shipment files for confirmed customer invoices ==== | ||
Line 57: | Line 56: | ||
Well, the good news is that day-to-day you don't have to do anything. The interface will continue running quietly in the background processing order files and creating shipment files as the customer invoices are confirmed. | Well, the good news is that day-to-day you don't have to do anything. The interface will continue running quietly in the background processing order files and creating shipment files as the customer invoices are confirmed. | ||
- | Periodically you should check the error email address set in the [[preferences: | + | Periodically you should check the error email address set in the [[preferences: |
The only other time you will hear anything from the interface is if mSupply detects an item on a customer invoice that wasn't in the original eLMIS order. This will happen if one of the item placeholder lines was replaced with a different item (e.g. because of low stock or a preferred item is to be used). In this case, mSupply will show a window and ask you to tell it which item on the original order you replaced with the item in question. Once you have selected the item that has been replaced mSupply will continue creating the shipment file. | The only other time you will hear anything from the interface is if mSupply detects an item on a customer invoice that wasn't in the original eLMIS order. This will happen if one of the item placeholder lines was replaced with a different item (e.g. because of low stock or a preferred item is to be used). In this case, mSupply will show a window and ask you to tell it which item on the original order you replaced with the item in question. Once you have selected the item that has been replaced mSupply will continue creating the shipment file. | ||
Line 88: | Line 87: | ||
\\ | \\ | ||
\\ | \\ | ||
- | | // Previous: | + | | // Previous: |
---- struct data ---- | ---- struct data ---- | ||
+ | pagestatus.status | ||
---- | ---- | ||