sap-bw-query

Inspect SAP BW queries and populate unsaved query drafts through Eclipse BW Modeling Tools.

Updated May 18, 2026
One-click install
npx skills add https://github.com/Melik1986/axon-erp-api --skill sap-bw-query-melik1986
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sap-bw-query
Source: https://github.com/Melik1986/axon-erp-api/tree/main/cursor/skills/sap-bw-query
Command: npx skills add https://github.com/Melik1986/axon-erp-api --skill sap-bw-query-melik1986

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Building SAP BW queries requires tedious manual metadata lookups and click-through work in BW Query Designer, while giving an AI assistant direct access risks credential exposure, accidental overwrites, and unauthorized saves. This Skill lets an AI inspect InfoProvider metadata and draft queries while keeping passwords, existing queries, and the final Save strictly under human control. ## Core Features & Use Cases - Read-only BW inspection: List open queries, read InfoProvider characteristics and key figures, and deep-read an open query's full EMF model through 22 closed-schema MCP tools. - Metadata-verified spec review: Convert a business specification into QuerySpec v1, verify every referenced characteristic and key figure against the live provider, and get gap analysis plus BWQ001–BWQ012 best-practices findings. - Human-gated draft population: Create unsaved local drafts, require an Eclipse confirmation bound to the spec hash, populate only the wizard-created unsaved editor, and leave the final Save to the user. - Use Case: A BW developer describes a plan/actual variance report; the assistant reads the provider metadata, validates a QuerySpec from a ready-made template, drafts it locally, and fills the new query editor after the developer confirms and finishes the native SAP wizard. ## Quick Start Ask the assistant to check the studio status with BwStudio.ps1, connect to your BW system using password-free metadata, and describe the target InfoProvider before drafting a new query.

Frequently Asked Questions about sap-bw-query

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate SAP BW query creation with an AI assistant?▼

Deploy the local Eclipse/BWMT bundle, connect with password-free metadata or SNC/SSO, then validate a QuerySpec against the provider metadata. After you confirm in Eclipse and finish the native New Query wizard, the automation populates the unsaved editor and you press Save manually.

What MCP tools are available for SAP BW query inspection?▼

The gateway exposes 22 closed-schema tools including bw_describe_provider for InfoProvider metadata, bw_read_query_model for deep query reads, bw_review_query for best-practices findings, and bw_populate_query_editor for filling unsaved editors. No save, delete, overwrite, or transport tools exist.

Can the automation save or overwrite an existing BW query?▼

No. Existing queries are strictly read-only, duplicate technical names are rejected, and editor population refuses any editor that already has content. The automation never presses Save; the human always completes SAP's own validation and Save action.

Does SAP BW query automation handle passwords or credentials?▼

No. Passwords, tokens, and secrets are never accepted, and all schemas reject credential-like keys. Authentication pauses at the native SAP login dialog, and the launcher always runs Eclipse with -noPwdStore.

What platforms and versions does the BW query studio require?▼

The runtime requires Windows with the bundled Eclipse 4.40, BW Modeling Tools 1.27.36, Java 21, and Node 24, installed per-user under %LOCALAPPDATA% without admin rights. Live BW system validation is still pending per the project runbook.

Why does BW query validation report blocking gaps?▼

Blocking gaps such as UNKNOWN_CHARACTERISTIC or UNKNOWN_KEY_FIGURE occur when spec names do not match the provider metadata. Rerun validation with a connection alias so every referenced name is verified against the live InfoProvider before drafting.