As an implementer, I want the option to include the "Average Consumption" (P) attribute on the requisition forms so that the user (storeroom and program manger) can see and understand what the typical or average consumption for that commodity is while he/she is making a request for more products.

Note: if the periods within a schedule are monthly, this calculation will serve as Average Monthly Consumption (AMC)

New Feature: implement the option for an implementer user to define the number of periods to average. This is a new option and part of the P attribute.

Acceptance Criteria
Verify that:

• an implementer (who is an authorized API user) can configure this field to appear in the Requisition template for their program

• an implementer (who is an authorized API user) can configure it with a field label string

• P is available to be associated with a requisition template by program

• can be assigned a display order in the requisition form

• average consumption is based on a period moving-average window of adjusted consumption (N) from most recent period(s)

  • (N _t0 + N _t-1 + N _t-2 + N _t-(n-1)) / ( n )

• user defines "n" (to indicate how many periods will be averaged)

• "n" cannot be 1 or 0, must be greater than or equal to 2

• "n" must have a value if (P) is selected to be displayed/included in the template

• n = number of periods

• t = indicates relative period (_t0 = current reporting period)

For data entry, if not enough periods exist, compute based on the following:

• if no previous periods, and there is only _t0 ; use P = N (instead of the formula above)

• if one previous period, so _t0 and _t-1 ; use P = Roundup( (N _t0 + N _t-1) / 2)

• if more than one previous period, just compute the average of what periods are available (even if less than the defined "n")