...
Time | Item | Who | Notes | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| ||||||||||||
| Shiyu Jin (Deactivated) has questions about when the system would record the lineItem. | ||||||||||||
What is the definition of an event? What is the relationship between stock card line item and event? Josh will respond.
Do we need a line item when the physical inventory count matches the stock on hand? Yes From an end user perspective, we want there to be a way to see that a physical inventory was done. How it is recorded on the backend is another story... See the ticket for Mary Jo Kochendorfer (Deactivated) response.
Does the system allow the reference data to be deleted/deactivated? If it is yes, how would the system handle the historical data conflict? Deactivation takes place centrally. We have an open question about users being able to favorite and archive products within their own storerooms. See ticket for responses from Brandon Bowersox-Johnson.
Since we do not have the lot function yet, anything depends on lot function is out of scope. We would have another ticket to update this view story after we have the lot function. Do we need a specific print format? If yes, that print function should be an separate ticket. yes, let's call this out in the lot management tickets. Yes, let's create a new print ticket.
I assume the stock on hand for a district/Province level is not the aggregate amount of those facilities below them in the supervisory hierarchy? Each district/province store room has its own stock on hand amount which is independent from its supervisory facilities. Correct. However we will want to have a report or a way to view SOH at various locations. However this ticket is about a specific facility. |
Action items
- Shiyu Jin (Deactivated) Update the existing business process
- Shiyu Jin (Deactivated) Create a ticket to track how the system will handle the deactivation of products (done centrally) system
Jira Legacy server JIRA (openlmis.atlassian.net) columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-1832 - Shiyu Jin (Deactivated) create a print ticket and pull out from 625
Jira Legacy server JIRA (openlmis.atlassian.net) columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-1833 - Shiyu Jin (Deactivated) move AC from 625 to lot management stories
Jira Legacy server JIRA (openlmis.atlassian.net) columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 448ba138-230b-3f91-a83e-16e7db1deed1 key OLMIS-1834
...