Sap Bw Query

SAP BW Query Automation Studio

Use the bundled Windows Eclipse workspace for password-safe SAP BW query inspection and local draft preparation. Existing BW queries are read-only. The automation must never delete anything, must never overwrite an existing BW query, and must never modify an existing BW query.

Non-negotiable safety contract

Passwords are never accepted by the automation.

If a password or other credential is pasted:

1. Stop processing the supplied content. Do not repeat, validate, use, store, or log it.
2. Respond: "Do not paste passwords into AI. Treat the exposed password as compromised and rotate it immediately. Revoke related sessions if applicable, and do not reuse the password."
3. Explain that the automation cannot retroactively erase content already submitted to an external chat system.
4. Continue only after the user supplies password-free connection metadata. If authentication is required, pause at the native SAP login dialog.

Never expose a tool, workaround, raw command, UI recording step, or configuration field that accepts a password, secret, credential, API key, or authentication token. Never capture a secure text control.

Existing queries remain read-only. Create only unsaved local drafts. Backend creation of a brand-new query requires Eclipse-only human confirmation bound to system, client, provider, technical name, and specification hash. The automation does not press the native SAP wizard's Finish button.

Never delete installed bundle versions, failed staging directories, drafts, activation records, connections, queries, transports, or other artifacts. Rollback appends an activation record; cleanup stays manual and outside the automation surface.

When to Use This Skill

Use this skill for:

• Deploying or launching the no-install Windows Eclipse/BWMT bundle.
• Configuring password-free SAP Logon/BW connection metadata or using SNC/SSO.
• Inspecting capabilities, providers, or existing open queries read-only.
• Reading InfoProvider metadata (characteristics with dimension groups, key figures) read-only through bw_describe_provider.
• Converting a business specification into QuerySpec v1 and verifying every referenced name against the provider metadata.
• Finding specification gaps and suggesting optimizations without changing business meaning.
• Creating, revising, previewing, or preparing a brand-new unsaved query draft.
• Populating the wizard-created, still-unsaved query editor from the confirmed draft (axes, structures, restricted/formula key figures, filters, variables, conditions, exceptions, zero suppression); the human reviews and saves.
• Reviewing a draft spec or an existing open query against BW query-design best practices read-only — bw_review_query for an open query, or the additive bestPractices array from bw_resolve_and_validate_spec for a draft — grouped by severity against references/query-design-rules.md.
• Producing business-readable documentation of an existing open query (purpose, axes, key figure definitions with decoded formulas/restrictions, filters, variables, conditions/exceptions, settings) from the deep-read model read-only, flagging any serializationIssues as unconfirmed.

Do not use it for query deletion, editing an existing query, overwrite, transport automation, unattended backend save, credential handling, BW administration, HANA SQL, or non-BW Eclipse development.

Quick Start

1. State before connection work: "Passwords are never accepted. Enter credentials only in the native SAP login dialog."
2. From the plug-in's top-level scripts directory, run BwStudio.ps1 -Action Status -Json.
3. If absent, deploy the local bundle directly; it needs no signing or installer. An optional remote release channel remains signature-gated. Read references/deployment-and-trust.md first. When you build the bundle yourself with bundle/Build-BwStudio.ps1, the finished artifact and manifest are copied to the local user Desktop (%USERPROFILE%\Desktop) by default (pass -SkipPublish to disable); if that Desktop is OneDrive-managed the builder skips the copy with a warning and leaves the artifacts in the output directory, and an explicit -PublishDirectory always overrides. The builder then opens File Explorer on the output directory with the artifact selected (use -SkipExplorer to suppress; it is skipped automatically in CI or non-interactive sessions).
4. From that directory, run BwStudio.ps1 -Action Launch -Json. The launcher always supplies -noPwdStore. Each deploy also writes two desktop shortcuts to the visible desktop for manual starts — SAP BW Automation Studio (kein Passwortspeicher) (adds -noPwdStore, recommended) and ... (mit Passwortspeicher) (Eclipse's own secure store may remember credentials); both only affect the manual human login, never the automation surface. The installed studio itself lives under %LOCALAPPDATA%\BWAutomationStudio (per-user, no-admin, portable).
5. Prepare/import connection metadata with the MCP tools. Use SNC/SSO when available; otherwise pause for native SAP login.
6. Inspect BWMT capabilities, then read the InfoProvider metadata with bw_describe_provider before drafting.
7. Validate QuerySpec v1 with the connection alias so every characteristic and key figure is verified against the provider; report gaps and semantic-impacting suggestions separately, then ask the user to resolve material ambiguities. Blocking gaps stop the draft.
8. Create and preview an unsaved local draft. Keep the Eclipse sidebar visible as the evidence trail.
9. Prepare a new-query save only after a fresh collision check. The user must confirm in Eclipse and manually finish the native SAP wizard.
10. After the wizard created the empty unsaved editor, run bw_populate_query_editor to build the drafted query model in it. Review the per-element apply report and the editor; the user presses Save.

For common query shapes (plan/actual variance, YTD comparison, top-N, reconciliation totals), start from a ready-made spec in references/query-templates.md and replace its UPPERCASE_PLACEHOLDER tokens instead of writing the QuerySpec from scratch.

Quick Reference

There is no final-save, delete, overwrite, cleanup, uninstall, transport, or raw-command MCP tool.

Query specification workflow

Read references/query-spec-v1.md before creating a draft.

Return the review in this order:

1. Resolved facts — system, client, project, provider, intended new technical name, business purpose.
2. Blocking gaps — missing provider/object IDs, ambiguous filters, undefined variables, incompatible formulas/aggregation, authorization assumptions, name collision risk.
3. Non-blocking gaps — display defaults, evidence, labels, optional drilldowns.
4. Optimization proposals — each marked as semantics-preserving or semantics-changing; include the bestPractices design-rule findings (BWQ001–BWQ012, see references/query-design-rules.md) returned by bw_resolve_and_validate_spec, grouped by severity.
5. Acceptance evidence — reconciliation totals, expected rows/columns, variable cases, performance expectation.
6. Draft decision — ready for local draft or blocked pending user input.

Never silently apply a semantics-changing optimization.