As an implementer, I want the option to include and configure the "Calculated Order Quantity" (I) so that storeroom managers don't need to calculate the order quantity (reduce human arithmetic error) when filling out the requisition.

This is an API ticket to allow this field to be configured on a requisition template for a program and, when configured, that it is included on new requisitions that are initiated for that program. There is also a UI ticket for making sure this field works properly on the Requisition Form in the UI.

Definition: calculated quantity which should be reordered. Deducts stock in hand quantity and is based on defined max stock amounts. This is quantified in dispensing units.
Calculation: (H) Maximum Stock Quantity - (E) Stock on Hand
Dependencies: H and E need to be configured on the template for I to be calculated (NOT SURE ABOUT THIS) H and E doesn't need to be displayed and this should still work (verify with v2).
Review: Please review 2.0 to confirm validations and logic and https://openlmis.atlassian.net/wiki/x/UQAOBg

Looking forward: if the facility is using OpenLMIS for inventory management and have an electronic stock card, stock on hand would be generated from the stock card and not entered in by the user.

Acceptance Criteria
Verify that:

• calculated order quantity is an available field that an administrator can configure into their requisition template for a program

• appropriate requisition templates endpoints support that (no UI exists yet for configuring the requisition template—that admin UI would be a future ticket)

• to use "I", H and E must be configured for the same template (E may be dependent on A, B, C, D if there isn't an electronic stock card)

  • there should be validation that H and E are also in use if using "I"

• the field is calculated by H - E

  • (H) Maximum stock quantity is defined by the user and sits in the reference data (see the 2.0 behavior, the configuration guide and below description for more details. H is defined in https://openlmis.atlassian.net/browse/OLMIS-887#icft=OLMIS-887)

• If there is an electronic stock card for the item/product, E is populated by the electronic stock card and not by A, B, C, D

• If there isn't an electronic stock card for the item/product, E is populated by user input of A, B, C, D

• the attribute (I) is displayed in the defined order on the requisition template

• the calculated amount of "I" cannot be modified in the UI, it is generated per the definitions above

• appropriate user permissions are enforced

• data entry validations should match the current 2.0 functionality (please check)

Definitions
An implementor defines max months of stock for a product, in a program, for a facility type. It’s part of a Facility Type Approved Product aka Facility Approved Product. The idea is this: for a full-supply product at a regional hospital (facility type), you might want to approve them to be supplied with bottles of 500 pills of Ibuprofen 500mg (product’s pack) and that they can have up to 3 months of stock (using either consumption or target population as the basis for calculating per month needs). It’s per facility type as a district hospital may not be allowed to be supplied with the 500 pill bottles, but rather the 50 pill bottles, and they should only have 2 months of stock.

Additional note: please view the configuration requisition template attached to the epic to see the interconnection with other requisition attributes.

Please ask questions if there is confusion on this story. Please work with the team lead to ensure appropriate implementation.