Subversion Repositories SmartDukaan

Last modification

• Rev 37319 2026-08-14 18:17:18
• Author: amit

• Log message:

  Fix partner-performance tertiary: aggregate order items (qty*mop), not the POS-typed order header
  
  The tertiary panel summed fofo_order.total_amount - a price typed at the partner POS
  and never validated against the catalogue - and attributed each whole order to its
  first line item's brand via .get(0). One mistyped digit inflated reported sell-out
  10x, and mixed-brand orders booked 100% to the first brand, leaving the rest at zero.
  Defect dates from r32000/r32034 (May 2023); the panel was the only tertiary consumer
  diverging from the qty*mop basis.
  
  - New FofoOrder.selectMonthlyBrandTertiary: sum(quantity*mop) grouped by
  (year*100+month) and item brand - the same basis selectPartnerTertiarySales
  already uses for the DSR and the partner tier calculation
  - PerformanceController: replaces two entity-loading queries (every FofoOrder and
  FofoOrderItem for 6 months) with one aggregate; all items now count, each under
  its own brand
  - Month labels unchanged - toMonthLabel rebuilds the MMM''uu key, template untouched
  - Remove V2FofoPerformanceController, the /v2/fofo JSON copy carrying the same defect
  
  Verified against dev DB for fofo_id 175139501: Jul 2026 now 16,94,939 (panel
  previously showed 50,92,440); all six months match the qty*mop basis.