Create a simple requisition with additional stock information

Description

As a storeroom manager, I want to quickly create a requisition with simple stock level information based on my role so that I can report on stock information and make a requisition at the same time.

From OLMIS-760, this story adds a Type (regular or emergency) of requisition, 5 configured column headers/fields for user input, and user data defaults based on roles (if a user is assigned to one program, no selection is made since no option is available).

Review and Reference

User Tasks

  1. User provides "program" if assigned to more than one

  2. User provides facility if assigned to more than one

  3. User indicates if the requisition is an 'emergency' requisition OR a regular requisition

  4. User inputs the following information (when not calculated) to complete the simple requisition form

Basic inventory fields
In the final product, the following should be defined during the setup and implementation period.
A. Beginning Balance (user input)
B. Total Received Quantity (user input)
D. Total Losses / Adjustments (user input)
C. Total Consumed Quantity (user input) I missed this one earlier! I hope we can sneak it in
E. Stock on Hand (calculated A + B (+/-) D - C) - reference the "Configuration Requisition Template" excel doc for list of attributes.
J. Requested Quantity (user input)
W. Requested Quantity Explanation (user input)

Acceptance Criteria:
Verify that:

  • the basic inventory fields (above) are available for each product (assigned to the facility/program)

  • system references facility and program data assigned to the user profile (dependency)

  • user can select 'my facility' or a facility from my supervised facilities (depending on user profile)

  • If user is only associated with 1 facility, this selection should be pre-populated/selected

  • user can select which program (from all programs my facility or supervised facilities serves) to requisition for

  • if a user is only associated with 1 program, program selection to be automatically made

  • "type" is defacto as "regular" for that scheduling period and "emergency" otherwise

  • facility, program and type are required before proceeding

  • the user cannot change his/her assigned facility (if only assigned one)

  • there is a mechanism to 'submit' the requisition

  • there is a mechanism to save the requisition**

  • a requisition can be saved and returned to**

  • upon submission the requisition status changes to "submitted"

  • the selections are easy to make in low-bandwidth environments

  • Stock on hand is calculated during data entry (see formula above)

  • the user can input the quantity for the Beginning Balance (integer)

  • the user can input the quantity for the Total Received Quantity (integer)

  • the user can input the quantity for the Total Losses / Adjustments (+/- integer)

  • the user can input the quantity for the Requested Quantity (integer)

  • the user can input the quantity for the Total Consumed Quantity (integer)

Please test that alpha characters and symbols are not accepted for integer inputs
**saving behavior may need to be pulled out to be its own story.

Activity

Show:
Pengfei Cui
October 17, 2016, 2:31 PM

SUCCESS: Integrated in

OpenLMIS-requisition-service #621
Fixing mess with labels, moving booleans to column definition (jkondrat: f802ae90471c00426a510de3df394541de811563)

Pengfei Cui
October 17, 2016, 2:40 PM

SUCCESS: Integrated in

OpenLMIS-requisition-service-Sonar #374
Fixing mess with labels, moving booleans to column definition (jkondrat: f802ae90471c00426a510de3df394541de811563)

Pengfei Cui
October 18, 2016, 12:22 PM

SUCCESS: Integrated in

OpenLMIS-requisition-service #626
OLMIS-741: Additional template columns (pgesek: feaeed55e17b9516e74c9fc35a5295780e8854e0)

Pengfei Cui
October 18, 2016, 12:31 PM

SUCCESS: Integrated in

OpenLMIS-requisition-service-Sonar #380
OLMIS-741: Additional template columns (pgesek: feaeed55e17b9516e74c9fc35a5295780e8854e0)

Brandon Bowersox-Johnson
October 19, 2016, 1:32 PM

Pawel and I agreed to close this ticket. Every single piece of this ticket is covered by other, more specific tickets that are being QA'd right now. It is just confusing and not helpful to have this over-arching ticket also moving around the JIRA board.

Assignee

Paweł Gesek

Reporter

Mary Jo Kochendorfer

Story Points

5

Time tracking

0m

Time remaining

0m

Epic Link

Sprint

None

Fix versions

Priority

Critical
Configure