How do you analyze SAP ERP data in Metabase?

{
  "mcpServers": {
    "sap": {
      "type": "http",
      "url": "https://<your-btp-app-route>/mcp"
    }
  }
}

# Install the Metabase CLI
npm install -g @metabase/cli

# Log in (opens your browser; requires Metabase v62+)
mb auth login --url https://your-metabase.example.com

# Load a scoped SAP export - creates a table and a model
mb upload csv --file sap-export.csv --collection "Finance & Accounting"

# Refresh the same table later
mb upload replace <table-id> --file sap-export.csv

Create a polished Metabase dashboard for SAP finance analytics.
Work end to end: find existing modeled data first; if none exists, load a minimal
read-only snapshot or describe the warehouse sync required.

Goal: Connect SAP S/4HANA or SAP BTP data to Metabase for general-ledger, working-capital, spend, cash, budget, and operational finance dashboards.

Inspect before querying:
- Inspect actual tables, column names, currencies, status values, and timestamps.
- Do not assume the source schema matches this guide exactly.
- Reconcile source totals before publishing any finance KPI.

Important:
- Do not claim Metabase connects natively to SAP; it reads a
  supported database or CLI-uploaded tables.
- Keep native amount, native currency, and reporting-currency amount separate.
- Distinguish authorization, posting, payment, settlement, and reconciliation
  states where the source exposes them.
- Use stable business keys and apply updates/deletes during incremental syncs.
- Exclude account numbers, personal data, and secrets from broad dashboards.
- Only build cards whose required fields and history are actually present.

Dashboard sections:
1. Finance overview: Cash and liquidity; Revenue, margin, and operating expense; AR and AP aging; Plan vs. actual.
2. Operations: Blocked invoices; Overdue receivables; Purchase-order commitments; Close task and posting status.
3. Controls and reconciliation: Unbalanced or reversed documents; Intercompany exceptions; Three-way match exceptions; Reconciliation status.
4. Planning and trends: Cost-center variance; Working-capital trend; Liquidity forecast; Margin by product or segment.

Suggested models: modeled_sap_gl, modeled_sap_open_items, modeled_sap_vendor_spend, modeled_sap_plan_actuals.

Output: Build the dashboard if you have permission; otherwise provide the exact
questions, SQL, model definitions, and layout. State refresh time, reporting
currency, accounting basis, and any reconciliation caveats.

SELECT
  fiscal_year,
  fiscal_period,
  cost_center,
  SUM(company_code_currency_amount) AS operating_expense
FROM modeled_sap_gl
WHERE account_type = 'EXPENSE'
  AND ledger = '0L'
GROUP BY 1, 2, 3
ORDER BY 1, 2, 4 DESC;

Keep company code and document currency explicit before consolidation.

SELECT
  company_code,
  document_currency,
  CASE
    WHEN CURRENT_DATE <= due_date THEN 'Current'
    WHEN CURRENT_DATE - due_date <= 30 THEN '1-30 days'
    WHEN CURRENT_DATE - due_date <= 60 THEN '31-60 days'
    ELSE '61+ days'
  END AS aging_bucket,
  SUM(open_amount) AS open_amount
FROM modeled_sap_open_ar
WHERE clearing_document IS NULL
GROUP BY 1, 2, 3
ORDER BY 1, 2, 3;