S_00009 — Management views over the live operating record

This solution addresses P_00010; the problem owns the forward reference in its ordered solutionsIds array.

The closest existing record was S_00002. Its mechanism consolidates operating and ledger records to calculate margin, while this mechanism changes the reporting path for broader management questions without requiring that consolidation. The duplicate review therefore found only partial overlap and approved a materially distinct record.

kind: solution_catalog
schema_version: 1
solutions:
  - id: S_00009
    proofIds: []
    priority: 50
    name: 'Management views over the live operating record'
    status: approved
    mechanism: >-
      Implement recurring management questions as in-system transaction-table
      queries, pivots, aggregations, and dashboard widgets over the sales,
      purchasing, inventory, manufacturing, and finance records that own the
      activity. Configure each view's fields, filters, groupings, calculations,
      ranking, and time basis once, then rerun it against current records rather
      than exporting the records and reconstructing the answer in a spreadsheet.
    capabilities:
      - name: 'Filter, sort, group, aggregate, and pivot supported transaction tables'
        classification: native
        conditions:
          - >-
            The source table must be connected to the implemented
            search-and-aggregate-with-pivoting path.
          - 'The required fields must exist and support the requested operation.'
          - 'Nested fields and relationships may require explicit query configuration.'
          - "Results remain subject to the user's record-access permissions."
        evidence_ids: []
      - name: 'View configured dashboard charts with date ranges, zoom, and download'
        classification: native
        conditions:
          - 'The dashboard and its referenced chart definitions must already exist.'
          - 'The requested metric must be available through the configured chart data source.'
          - 'Dashboard visibility remains subject to configured access.'
        evidence_ids: []
      - name: 'Configure recurring management views and dashboard widgets for account-specific questions'
        classification: configured
        conditions:
          - >-
            The customer must supply representative reports and define each
            metric, grouping, ranking, filter, and reporting period.
          - >-
            Cross-document views require verified relationships and consistent
            treatment of units, currencies, statuses, and dates.
          - 'Each configured result must be reconciled to representative source transactions.'
          - >-
            Configuration and testing effort cannot be sized before the reports,
            source fields, and relationships are inspected.
          - >-
            A ranked top-selling-product or vendor analysis remains unverified
            until its exact field mapping and calculation are tested.
        evidence_ids: []
    expected_outcome_hypotheses:
      - >-
        A recurring management report can be rerun against current operating
        records without rebuilding it from a new spreadsheet export.
      - >-
        Repeated questions can use the same approved filters, groupings,
        rankings, and calculations.
      - >-
        Supported management views can present both underlying transaction rows
        and grouped or aggregated results inside the operating environment.
      - >-
        Changes to the source records can be reflected when the configured view
        or dashboard is executed again.
    limitations:
      - >-
        The implementation does not establish that every requested management
        report exists out of the box; account-specific reports require
        configuration and testing.
      - >-
        Native report/export settings are not uniformly enabled across every
        source document, so the same reporting path cannot be assumed for all
        record types.
      - >-
        Cross-document calculations remain dependent on correct joins, field
        mappings, units, currencies, statuses, and reporting-period definitions.
      - >-
        Missing, incomplete, or inconsistently recorded transactions produce
        incomplete or misleading views.
      - >-
        A general end-user self-service dashboard builder was not verified in
        MCP server d8189168.
      - >-
        One-off scenario modelling or analysis that is not represented in the
        configured data model may still require an external analytical tool.
    prohibited_claims:
      - 'That the mechanism eliminates Excel or all manual analysis.'
      - 'That every management-reporting modality is available out of the box.'
      - >-
        That a top-selling-product, vendor, purchasing, inventory,
        manufacturing, or accounting report is correct before reconciliation
        with representative source transactions.
      - 'That all transaction tables support identical fields, pivots, or aggregations.'
      - 'That dashboards are universally self-service for end users.'
      - 'That queried results update continuously without rerunning the view.'
      - 'Any quantified delay, labor, accuracy, or error-rate improvement.'

Outstanding

1. proofIds is empty. Run W7 after at least one eligible evidence record exists.
2. Every capability has evidence_ids: []. The implementation checks from MCP server d8189168 are deployment-specific observations, not canonical evidence records. Route formal product evidence through W9.
3. Exact report definitions are missing. Obtain representative reports, source-field mappings, and reconciliation criteria before configuring or recommending a specific management view.
4. Configured effort is unknown. Inspect the required reports, source fields, relationships, units, currencies, statuses, and reporting periods before estimating implementation work.