Consumption Report

Added a block from epic OLMIS-4131, however it's understood that a simpler approach to tagging, i.e. hard-coding which reasons are which, is possible though less flexible for implementers in production.

To add onto this and for reference @Clay Crosby the idea I floated with you earlier about identifying Stock Adjustment Reasons using a tagging concept (e.g. to find what consumption is a tag would be defined which could be associated to one to many stock adjustment reasons) has moved forward a bit as we have it as a dependency in stock based requisition workflows. first and foremost in this ticket: OLMIS-4034. To go this route we're waiting on LOE and scoping to make the final call for v3.3, however I wanted you to be aware that this is out there.

@Clay Crosby, Consumption is "issued". When stock leaves the inventory for the "correct/desired" intent of being shipped to the next facility or to a location for dispensing to a client. However, it is a little tricky since during a physical inventory you can give a reason for the negative adjustment for 'transferred out'... So all this is to say we run into the same concern as we did with Closed Vial Wastage. We need a way to 'tag' within OpenLMIS so that reporting (and other things) know which reasons feed what...

Regarding the questions on schedules and periods, this relates to https://openlmis.atlassian.net/wiki/spaces/OP/pages/112138794/Implementer+Administrator#Implementer/Administrator-SetupPrograms,ProcessingSchedules,andPeriods

In terms of packs, this concept is important to understand and can be confusing. You will always want to understand if a quantity is expressed in dispensing units or "packs". Take a look at https://openlmis.atlassian.net/wiki/spaces/OP/pages/112138794/Implementer+Administrator#Implementer/Administrator-SetupOrderables,TradeItems,CommodityTypes and scroll towards the bottom of the section for a description about packs and rounding thresholds.

Adjusted Consumption is defined here: https://openlmis.atlassian.net/wiki/spaces/OP/pages/112138794/Implementer+Administrator#Implementer/Administrator-SetupRequisition&ReportTemplatebyprogram

I think we will need to talk through these items since some of them are 'blocked' in the sense that we don't have a tagging system implemented for adjustment reasons in stock management.
HTH