| Page Properties | ||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
- A Stock Based requisition is defined as:
- A requisition using pre-populated stocking information that cannot be changed.
- The following rules also apply:
- The only field a user can edit is requested quantities and an explanation.
- Administrators can turn off the authorize step.
- Follows existing processing periods.
- Can include new ISA column to assist in amount to request (assuming ISA quantities are configured).
- Utilizes existing approval hierarchy from Requisitions within OpenLMIS
- For an ideal state, a user should be requesting commodity types for any requisition (same set of products as defined in FTAP)
- An administrator can configure multiple templates per program
Background
These are the differences between regular requisitions and stock based requisitions:
...
- Stock on Hand level is only incremented/decremented in the Proof of Delivery process. This needs to be defined when the Proof of Delivery feature requirements are documented.
- Stock Card is the Stock on Hand at that time - this is not historical stock or available stock
We want to use the existing requisition endpoints as much as possible
- New System generated triggers to prompt a user to create a stock based requisition (alerts and notifications for stock outs or potential stockouts) are out of scope for this release
- Additional consideration to support the Product Model must be included in these requirements to request commodity types and trade items for requisitions, orders, and fulfillment, but is still being designed (as of 1/5/18).
- Stock Management records stock on hand as dispensing units
- Requisitions records stock on hand and requested quantities as dispensing units
- View Orders reports Order quantities as dispensing units
User Stories
Using known stock data, Spock needs to request new stock (stock-based requisition) so that an order can be created to fulfill.
...
| # | Title | User Story | Label | Importance | Jira tickets | ||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Configurability for Authorize | As an administrator I need to configure the authorize step in Requisitions so that it is not required in the resupply process. |
| ||||||||||||||||||||||||||||||||||||||||||
| 2 | Create a Stock Based requisition | As a DIVO I need to requisition stock when I have completed my physical inventory and determine that additional stock is needed. Acceptance Criteria:
Questions:
Assumptions:
| Tickets to be deaded:
| ||||||||||||||||||||||||||||||||||||||||||
| 3 | Configure Stock based requisition template | As an admin I need to configure stock based requisition templates so that they display required fields. Acceptance Criteria:
Questions:
|
Ticket to be deaded:
| ||||||||||||||||||||||||||||||||||||||||||
| 4 |
|
| |||||||||||||||||||||||||||||||||||||||||||
| 5 | Replace Convert to Order Process | Modify the current 'convert to order' process so that requisition can be fulfilled with OpenLMIS (need ability for the user to view orders for other facilities, and select a facility that is not a warehouse to fulfill when the order is created) |
|
Diagrams
Process Workflows:
- Intentional Request: Spock knows he needs to request more stock before he even logs into OpenLMIS (based on external data maybe)
- Spock can create a stock based requisition for a facility/program *at any time*
- Spock knows of an external (undocumented maybe) need for stock, and sees his stock will be low
- Unintentional Request: Spock is completing stock management activities in OpenLMIS and is notified or looks at stock data and determines that he needs to request stock. (This is otherwise known as system alerts or notifications.)
- Spock completed his physical inventory and sees that his ISA is higher than the SOH, next order won't be for some time
- Spock has loss/wastage that he reported in his physical inventory, and now needs new stock
- Spock received notification (email or phone call) that his stock is low
- Min/max stock levels compared to physical inventory, Min stock level notification
- Emergency order point notification
- When Spock creates an issue, he is prompted to create a stock based requisition
Dependencies
| Description | Link |
|---|---|
| Connecting Stock Management to Requisitions (Brandon Bowersox-Johnson are there dependencies?) | |
| In Local Fulfillment, when a DIVO is deciding how much to fulfill at each facility, they can manually update the SOH. When we are completing stock based requisitions this field in fulfillment should be populated by the stock cards, so that the SOH in fulfillment matches the SOH in the stock based requisition, and this field should not be editable if it is auto populated. |
Open Questions
Below is a list of questions to be addressed as a result of this requirements document:
| # | Question | Outcome | Status |
|---|---|---|---|
| 1 | Will stock based requisitions use different consumption calculations? For example if more than one stock based requisitions are created within a regular requisition processing period? | ||
| 2 | Is there a difference between stock based requisitions and emergency requisitions? Should they be the same? (Reuse or modify emergency requisitions to support additional requirements (if any) for stock based reqs.) | ||
| 3 | If I have created a SB requisition, and that is pending approval, should I be able to create another simple requisition before the first is approved? | ||
| 4 | If I have submitted my physical inventory on previous date, and now want to create a SB requisition, how will I get to that screen? This workflow would require the user to submit another physical inventory, and then they will see the prompt to create a requisition. Should there be another way? A button on the stock mgmt screen? | ||
| 5 | What are the triggers for creating the SB requisition? Should there be a prompt every time a physical inventory is submitted? Or are there automated calculations that trigger a user to create the SB requisition? (triggered by stockouts?) | ||
| 6 | How are reporting and existing requisitions impacted? | ||
| 7 | What products are on a stock-based requisition? Does it start empty and you pick and add products one-by-one? | For 3.3 we will use FTAPs and address the one by one in later releases. | Closed |
| 8 | What columns are on a stock-based requisition? | ||
| 9 | Product must have a stock card? If there is a product that doesn't have a stock card, should Spock still be able to request it? |