Goals/Scope
R&R approval workflow needs to support some additional scenarios
Status in eLMIS: Implemented.
Status in OpenLMIS: ?
Priority: High priority for Tanzania
Background
Over the past few years, the supply chain system in Tanzania was operating on a quarterly reporting and quarterly fulfillment schedule. ELMIS was also configured to do the same. Recently, a need has been expressed to report on a monthly basis but to still fulfill on a quarterly basis.
To accommodate this need, ELMIS was updated to allow administrators to select which periods result in requisition being converted to order and which periods will not result in requisition not being converted.
In the current implementation, this rule applies to only regular requisitions.
There is no change in the formula of calculated order quantity In the current implementation of this requirement.
Note: This feature is not in production. It is only in test. Feedback is still expected.
Assumptions
The current implementation of the average monthly consumption based order quantity works for this scenario and that this requirement does not add more formula
- Removing requested quantity so the user cannot requisition
- Updating the requisition status to released without order
User Stories
| # | Title | User Story | Label | Importance | Notes | JIRA Tickets |
|---|
| 1 | Schedule Management Page | As an administrator, I would like to mark which period would be converted to order and which period does not result in an order being generated.
 | Administration | Must have | - What other components use processing periods, and would be impacted by this change?
- How does using processing periods to flag enabling orders impact distributions?
- Likely would be a per-program property, so would not impact other parts that use period
- Can this setting be turned on or off for a requisition that is in a further state (initiated or other)?
- NO, the setting must be snapshotted in case the setting is changed while a requisition is in process.
- How configurable should this setting be?
- The setting would probably need to be configured by program and processing period, to support multiple programs.
- There would either need to be a report-only requisition template, or when a requisition is initiated, it would exclude order-related columns from requisition data
- If requested quantity column is removed, what other additional columns must be removed from the template? Calc Order qty, approved qty, totals?
- What are the scenarios for supporting offline?
|  |
| 2 | R&R Approval | a requisition that is for a period that should not generate an order, I would like to see that it does not go to the convert to order screen.
| R&R Approval | Must have |
|  |
| 3 | R&R Create/Approve | As a user/supervisor, I would like to see an indication when the requisition that I am creating or approving will not result in an order. (Please see the screen cast below) | R&R Create and Approval | Must have |
|  |
- Does this impact calculations? Elias: No, we did not have to change calculations.
Gap Estimation Notes 4/12/2018
- Attendees: Mary Jo, Matt, Josh, Muhammad, Ashraf, Peter, Craig, Brandon, Elias
- Concern: This feature is still changing, and we expect new requests as this is rolled out.
- We may have this request from Zambia as well.
- It is a permanent plan to do quarterly orders/shipments but monthly reports. (This is not a temporary/bridge solution.)
- Mary Jo: I expect them to request changes to approvals as well.
- Josh: Consider meeting this need using Stock Management > Physical Inventory during the reporting-only months.
- Ashraf: However, that does not capture Stockout Days, and it does not make the UI as easy for users to enter Receipts.
- Mary Jo: I am concerned if they had 100 count, and now have 101 count, they will just give the reasons for the +1, they will not give the full month's consumption and receipts.
- OpenLMIS v3 already handles different schedules, so the work needed here is to add the checkbox (User Story #1), and add the business logic for User Story #2 and #3.
- Craig: I suggest adding a new status to mean "this reporting is captured but not converting to order". Call this new status "Released Without Order". That is covered by another epic we already estimated (Requisition - Convert requisition to order).