...
Field Name in API | Column Name | eLMIS Report(s) | Superset Dashboard(s) | Calculation(s) or Column(s) in eLMIS Report(s) | Comment |
---|---|---|---|---|---|
requisitionLineItems.id | requisition_line_item_id | ||||
id | requisition_id | ||||
orderable.id | orderable_id | ||||
orderable.productCode | product_code | ||||
orderable.fullProductName | full_product_name | Orderable name | |||
orderable.commodityTypeIdentifier | commodity_type_id | ||||
orderable.identifiers.tradeItem | trade_item_id | Used to join to Reference Data to find trade item name, etc. | |||
beginningBalance | beginning_balance | Stock Status Summary Report Logistics Summary Report | Consumption dashboard | Counts as a stockout if = 0 Opening Balance | |
totalConsumedQuantity | total_consumed_quantity | Consumption dashboard | Reported Consumption Consumption | ||
averageConsumption | average_consumption | Not included but could be easily added (it is in the data model) | Stock level / stock status calculation in popup Stock Status & AMC | ||
adjustedConsumption | adjusted_consumption | Consumption Report | Consumption dashboard | Adjusted Consumption | |
totalLossesAndAdjustments | total_losses_and_adjustments | Adjustments dashboard Consumption dashboard | We need to use the quantities on the adjustment reason lines for the line-level detail in the Adjustment Summary Report. Including this in case necessary for totals in the future. | ||
stockOnHand | stock_on_hand | Consumption dashboard | Count as stockout if = 0 Closing Balance Closing Balance | Could be easily added to Stock Status dashboard in Superset, although it was omitted due to feedback that Periods of Stock was more pertinent as stock on hand is relative to the expected stock level for that product, facility, and program | |
totalStockoutDays | total_stockout_days | Stock Status Summary Report | Stockouts dashboard | Count as stockout if > 0 | |
maxPeriodsOfStock | max_periods_of_stock | Stock Status dashboard | Count as stockout if = 0 MOS | ||
calculatedOrderQuantity | calculated_order_quantity | System determined amount to reorder based on consumption and current stock level. Not necessary for eLMIS reports, but could be useful. Omitted from Superset reports in favor of the actual order quantity (requested_quantity) | |||
requestedQuantity | requested_quantity | Logistics Summary Report | Orders dashboard Consumption dashboard | Reorder Amount | |
approvedQuantity | approved_quantity | Order Quantity Quantity Ordered | Excluded from Superset, but could be easily added as it is in the data model. For Order Item & Fill Rate report, we used requested_quantity and total_received_quantity | ||
packsToShip | packs_to_ship | Used in Order Summary Report but this report is not coming from the reporting stack. Including for potential future need. | |||
pricePerPack | price_per_pack | Used in Order Summary Report but this report is not coming from the reporting stack. Including for potential future need. | |||
totalCost | total_cost | Total Cost of Orders | Orders dashboard | Approved Total Cost | |
totalReceivedQuantity | total_received_quantity | Order & Item Fill Rate Report | Orders dashboard | Quantity Received |
requisition_status_history
...