...
# | Title | User Story | Label | Importance | Notes | JIRA Tickets |
---|---|---|---|---|---|---|
1 | Product list update from ERP | As an administrator I want product lists in OpenLMIS updated in line with updates to product lists in the MSD E9 ERP so that I don't have errors with other OpenLMIS-MSD E9 ERP data exchanges. | Tanzania MSD Epicor 9 ERP | Must haveProduct list update from ERP | ||
2 | Product list update review | As an administrator I want to be able to manually review product list changes and add additional information or configurations which are not available in the MSD E9 ERP. | Tanzania MSD Epicor 9 ERP | Must have | ||
3 | Price list update from ERP | As an administrator I want prices in OpenLMIS updated in line with updates to prices lists in the MSD E9 ERP so that R&R submitters and approvers have accurate cost information. | Tanzania MSD Epicor 9 ERP | Must have |
Diagrams
Dependencies
...
Below is a list of questions to be addressed as a result of this requirements document:
# | Question | Outcome | Status |
---|---|---|---|
1 | Will product list updates always go through a manual validation and update process? | ||
2 | Was this background detail confirmed as not a gap in OpenLMIS: "Prices are normally changed once per year, at the start of the financial year (i.e., 1 July). The system stores old prices as well as new prices and uses the appropriate prices for any particular time period"? | ||
3 | Need for adding in "System requirements specifications for eLMIS interface with mSupply" on import of product lists. | ||
4 | Is there a desire to have this done automatically? |