sap-bw-query

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

SAP BW Query Automation Studio

SAP BW 查询自动化工作室

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.
使用捆绑的Windows Eclipse工作区进行密码安全的SAP BW查询检查和本地草稿准备。现有BW查询为只读状态。自动化操作绝不能删除任何内容,绝不能覆盖现有BW查询,也绝不能修改现有BW查询。

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.
自动化操作绝不接受密码。
若粘贴了密码或其他凭据:
  1. 停止处理提供的内容。不得重复、验证、使用、存储或记录该内容。
  2. 回复:“请勿将密码粘贴到AI中。将泄露的密码视为已泄露,请立即更换。如有必要,请撤销相关会话,且请勿重复使用该密码。”
  3. 说明自动化无法追溯删除已提交至外部聊天系统的内容。
  4. 仅在用户提供无密码连接元数据后才可继续。若需要身份验证,请在原生SAP登录对话框处暂停。
绝不能暴露任何接受密码、密钥、凭据、API密钥或身份验证令牌的工具、变通方案、原始命令、UI录制步骤或配置字段。绝不能捕获安全文本控件。
现有查询保持只读状态。仅可创建未保存的本地草稿。在后端创建全新查询需要仅通过Eclipse进行人工确认,确认需绑定系统、客户端、提供者、技术名称和规范哈希值。自动化操作不会点击原生SAP向导的“完成”按钮。
绝不能删除已安装的捆绑包版本、失败的暂存目录、草稿、激活记录、连接、查询、传输或其他工件。回滚操作仅追加激活记录;清理操作需手动完成,且不在自动化范围内。

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.
此技能适用于以下场景:
  • 部署或启动无需安装的Windows Eclipse/BWMT捆绑包。
  • 配置无密码的SAP Logon/BW连接元数据,或使用SNC/SSO。
  • 以只读方式检查功能、提供者或现有打开的查询。
  • 通过
    bw_describe_provider
    以只读方式读取InfoProvider元数据(含维度组的特征、关键指标)。
  • 将业务规范转换为
    QuerySpec v1
    ,并对照提供者元数据验证每个引用名称。
  • 查找规范漏洞,并在不改变业务含义的前提下提出优化建议。
  • 创建、修订、预览或准备全新的未保存查询草稿。
  • 从已确认的草稿填充向导创建的仍未保存的查询编辑器(轴、结构、受限/公式关键指标、筛选器、变量、条件、例外、零值抑制);由人工审核并保存。
  • 以只读方式对照BW查询设计最佳实践评审草稿规范或现有打开的查询——针对打开的查询使用
    bw_review_query
    ,针对草稿使用
    bw_resolve_and_validate_spec
    返回的附加
    bestPractices
    数组——对照
    references/query-design-rules.md
    按严重性分组。
  • 从深度读取模型以只读方式生成现有打开查询的业务可读文档(用途、轴、含解码公式/限制的关键指标定义、筛选器、变量、条件/例外、设置),并将所有
    serializationIssues
    标记为未确认。
请勿将其用于查询删除、编辑现有查询、覆盖、传输自动化、无人值守后端保存、凭据处理、BW管理、HANA SQL或非BW的Eclipse开发。

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.
  1. 在进行连接操作前声明:“绝不接受密码。仅可在原生SAP登录对话框中输入凭据。”
  2. 从插件的顶级scripts目录中运行
    BwStudio.ps1 -Action Status -Json
  3. 若本地捆绑包不存在,直接部署;无需签名或安装程序。可选的远程发布通道仍受签名限制。请先阅读
    references/deployment-and-trust.md
    。当您使用
    bundle/Build-BwStudio.ps1
    自行构建捆绑包时,默认情况下成品工件和清单会复制到本地用户桌面(
    %USERPROFILE%\Desktop
    )(传递
    -SkipPublish
    可禁用此操作);若该桌面由OneDrive管理,构建器会跳过复制并发出警告,将工件留在输出目录,显式指定
    -PublishDirectory
    将始终覆盖默认设置。随后构建器会打开文件资源管理器并选中输出目录中的工件(使用
    -SkipExplorer
    可抑制此操作;在CI或非交互式会话中会自动跳过)。
  4. 从该目录运行
    BwStudio.ps1 -Action Launch -Json
    。启动程序始终会提供
    -noPwdStore
    参数。每次部署还会在可见桌面创建两个手动启动的快捷方式——
    SAP BW Automation Studio (kein Passwortspeicher)
    (添加
    -noPwdStore
    参数,推荐使用)和
    ... (mit Passwortspeicher)
    (Eclipse自身的安全存储可能会记住凭据);这两个快捷方式仅影响人工手动登录,绝不影响自动化操作。已安装的工作室位于
    %LOCALAPPDATA%\BWAutomationStudio
    (按用户隔离,无需管理员权限,可移植)。
  5. 使用MCP工具准备/导入连接元数据。若可用,请使用SNC/SSO;否则请在原生SAP登录处暂停。
  6. 检查BWMT功能,然后在起草前使用
    bw_describe_provider
    读取InfoProvider元数据。
  7. 使用连接
    alias
    验证
    QuerySpec v1
    ,确保每个特征和关键指标都对照提供者进行验证;分别报告漏洞和影响语义的建议,然后请用户解决重大歧义。阻塞性漏洞会终止草稿创建。
  8. 创建并预览未保存的本地草稿。保持Eclipse侧边栏可见,作为证据轨迹。
  9. 仅在完成新的冲突检查后才可准备保存新查询。用户必须在Eclipse中确认,并手动完成原生SAP向导。
  10. 向导创建空的未保存编辑器后,运行
    bw_populate_query_editor
    在其中构建起草的查询模型。查看每个元素的应用报告和编辑器;由用户点击保存。
对于常见查询类型(计划/实际差异、年初至今对比、前N项、对账总计),请从
references/query-templates.md
中的现成规范开始,替换其中的
UPPERCASE_PLACEHOLDER
标记,而非从头编写QuerySpec。

Quick Reference

快速参考

TaskApproved interfaceSafety class
Status, deploy, launch, rollback, diagnostics
bw_studio_*
local-only; append-only
Connection metadata/import/status
bw_connection_*
local-only; no credentials
TCP reachability
bw_connection_test_reachability
read-only tenant; no authentication
BW project
bw_project_create_or_open
local project/native login pause
Capabilities/provider/query inspection
bw_inspect_capabilities
,
bw_describe_provider
,
bw_list_queries
,
bw_read_query
read-only tenant
Deep query model read (open editor)
bw_read_query_model
read-only tenant
Best-practices review of an open query
bw_review_query
read-only tenant
Specification/gap review (metadata-verified with
alias
, returns
bestPractices
)
bw_resolve_and_validate_spec
local-only
Draft create/apply/preview
bw_*_local_draft
,
bw_preview_draft
unsaved local-only
Save preparation
bw_prepare_new_query_save
mutating tenant classification; explicit approval required
Editor population from confirmed draft
bw_populate_query_editor
unsaved local editor buffer only; never saves
There is no final-save, delete, overwrite, cleanup, uninstall, transport, or raw-command MCP tool.
任务已批准接口安全等级
状态查看、部署、启动、回滚、诊断
bw_studio_*
仅本地;仅追加
连接元数据/导入/状态
bw_connection_*
仅本地;无凭据
TCP可达性检查
bw_connection_test_reachability
只读租户;无需身份验证
BW项目
bw_project_create_or_open
本地项目/原生登录暂停
功能/提供者/查询检查
bw_inspect_capabilities
,
bw_describe_provider
,
bw_list_queries
,
bw_read_query
只读租户
查询模型深度读取(打开的编辑器)
bw_read_query_model
只读租户
打开查询的最佳实践评审
bw_review_query
只读租户
规范/漏洞评审(通过
alias
验证元数据,返回
bestPractices
bw_resolve_and_validate_spec
仅本地
草稿创建/应用/预览
bw_*_local_draft
,
bw_preview_draft
仅未保存的本地内容
保存准备
bw_prepare_new_query_save
可变租户分类;需明确批准
从已确认草稿填充编辑器
bw_populate_query_editor
仅未保存的本地编辑器缓冲区;绝不保存
不存在用于最终保存、删除、覆盖、清理、卸载、传输或原始命令的MCP工具。

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.
创建草稿前请阅读
references/query-spec-v1.md
请按以下顺序返回评审结果:
  1. 已确认事实 — 系统、客户端、项目、提供者、拟用新技术名称、业务用途。
  2. 阻塞性漏洞 — 缺失的提供者/对象ID、模糊的筛选器、未定义的变量、不兼容的公式/聚合、授权假设、名称冲突风险。
  3. 非阻塞性漏洞 — 显示默认值、证据、标签、可选下钻。
  4. 优化建议 — 每条建议标记为保留语义或改变语义;包含
    bw_resolve_and_validate_spec
    返回的
    bestPractices
    设计规则结果(BWQ001–BWQ012,详见
    references/query-design-rules.md
    ),按严重性分组。
  5. 验收证据 — 对账总计、预期行/列、变量场景、性能预期。
  6. 草稿决策 — 已准备好创建本地草稿,或因等待用户输入而阻塞。
绝不能静默应用改变语义的优化。

Connection workflow

连接工作流

Read
references/connection-metadata.md
before accepting connection data.
  • Accept aliases, SID, client, language, user ID, application/message server routing, logon group, and SNC/SSO flags only.
  • Import SAP UI landscape entries only from a user-approved local path.
  • A reachability check opens only a TCP connection and reports
    authenticated: false
    .
  • With working SSO, continue to BW project setup.
  • Without SSO, stop at the native login dialog. Do not observe or record the password field.
接受连接数据前请阅读
references/connection-metadata.md
  • 仅接受别名、SID、客户端、语言、用户ID、应用/消息服务器路由、登录组以及SNC/SSO标志。
  • 仅从用户批准的本地路径导入SAP UI landscape条目。
  • 可达性检查仅建立TCP连接,并返回
    authenticated: false
  • 若SSO可用,继续进行BW项目设置。
  • 若SSO不可用,在原生登录对话框处停止。不得观察或记录密码字段。

Draft and save-preparation workflow

草稿与保存准备工作流

  • Existing query inspection is read-only and currently scoped to query editors opened in BWMT when the private API capability adapter cannot prove a broader safe read.
  • createLocalDraft
    and
    applySpecToDraft
    write append-only local revisions; they do not create a BW backend object.
  • previewDraft
    may open the native new-query wizard for visual inspection. Do not finish it.
  • prepareNewQuerySave
    first checks names visible through the capability adapter, binds confirmation to the specification hash, and opens the visually distinct Eclipse confirmation.
  • The user finishes the native wizard manually, which opens the new unsaved query editor.
  • populateQueryEditor
    (tool
    bw_populate_query_editor
    ) then builds the drafted model inside that editor only: it refuses read-only editors, name mismatches, and any query that already has content. Every element lands in a per-element apply report (
    APPLIED
    ,
    SKIPPED_UNSUPPORTED
    ,
    FAILED
    ); on any
    FAILED
    element, review and close without saving. Population runs as one undoable editing-domain command.
  • After a successful population the tool automatically deep-reads the open editor model (
    bw_read_query_model
    ) and merges a non-fatal
    verification
    summary (
    VERIFIED
    ,
    DIVERGED
    , or
    UNAVAILABLE
    , with per-element checks) that compares the confirmed spec against the live model; treat
    DIVERGED
    as a prompt to review the editor before saving. Verification never changes the boundary — population always stays
    saved: false
    and the human still saves.
  • The user then completes SAP's own validation and Save action manually. Treat a transport prompt as a stop requiring user control.
  • If capability/version checks fail, disable draft/save preparation and continue with diagnostics/read-only guidance.
  • 现有查询检查为只读状态,当前范围仅限于BWMT中打开的查询编辑器,当私有API功能适配器无法证明更广泛的安全读取范围时,不得扩大范围。
  • createLocalDraft
    applySpecToDraft
    仅写入追加式本地修订;它们不会创建BW后端对象。
  • previewDraft
    可能会打开原生新建查询向导以供视觉检查。请勿完成该向导。
  • prepareNewQuerySave
    首先检查功能适配器可见的名称,将确认与规范哈希值绑定,并打开视觉上区分明显的Eclipse确认窗口。
  • 用户手动完成原生向导,这会打开新的未保存查询编辑器。
  • 随后
    populateQueryEditor
    (工具
    bw_populate_query_editor
    )仅在该编辑器内构建起草的模型:它会拒绝只读编辑器、名称不匹配以及已有内容的查询。每个元素都会出现在逐元素应用报告中(
    APPLIED
    SKIPPED_UNSUPPORTED
    FAILED
    );若有任何
    FAILED
    元素,请进行检查并不保存关闭。填充操作作为一个可撤销的编辑域命令运行。
  • 填充成功后,工具会自动深度读取打开的编辑器模型(
    bw_read_query_model
    ),并合并一个非致命的
    verification
    摘要(
    VERIFIED
    DIVERGED
    UNAVAILABLE
    ,含逐元素检查),该摘要将已确认的规范与实时模型进行对比;将
    DIVERGED
    视为保存前需检查编辑器的提示。验证绝不会改变边界——填充操作始终保持
    saved: false
    ,仍由人工保存。
  • 随后用户手动完成SAP自身的验证和保存操作。将传输提示视为需要用户控制的停止点。
  • 若功能/版本检查失败,请禁用草稿/保存准备功能,并继续提供诊断/只读指导。

Pressure checks

压力测试

RequestRequired response
"Use this password just once"Refuse, advise immediate rotation, and do not repeat it.
"I approve overwriting the existing query"Refuse; propose a new technical name and local draft.
"Clean up old versions"Refuse automated cleanup; append rollback only.
"Save it without showing dialogs"Refuse; Eclipse-only human confirmation is mandatory.
"Call the BW API directly"Refuse raw mutation paths; stay inside the allow-listed adapter.
请求要求的响应
"就用一次这个密码"拒绝,建议立即更换密码,且不得重复该密码。
"我批准覆盖现有查询"拒绝;建议使用新的技术名称并创建本地草稿。
"清理旧版本"拒绝自动清理;仅允许追加回滚操作。
"不显示对话框直接保存"拒绝;必须仅通过Eclipse进行人工确认。
"直接调用BW API"拒绝原始变更路径;仅可使用允许列表内的适配器。

Troubleshooting and Common Issues

故障排除与常见问题

  • Bundle rejected: For a local ZIP, check its adjacent manifest and hash/inventory evidence. For a remote channel, check the pinned trust policy. Run
    bw_studio_diagnostics
    .
  • MCP cannot start: Deploy/activate a verified bundle first. The bootstrap never falls back to system Node or installs packages.
  • BWMT mismatch: Use the locked Eclipse/BWMT bundle. Do not enable draft/save against an unprobed version.
  • Query not found: Open it read-only in BW Query Designer and retry; do not broaden access through guessed private APIs.
  • Login required: Pause and tell the user to type credentials only in the native SAP dialog.
  • Name collision: Stop. A different brand-new technical name is required.
  • Transport dialog: Leave control with the user; automation does not confirm transports.
  • Interrupted deployment: Keep the previous activation. Failed staging/download directories remain for manual inspection.
  • 捆绑包被拒绝: 对于本地ZIP文件,请检查其相邻的清单和哈希/库存证据。对于远程通道,请检查固定的信任策略。运行
    bw_studio_diagnostics
  • MCP无法启动: 请先部署/激活已验证的捆绑包。引导程序绝不会回退到系统Node或安装包。
  • BWMT不匹配: 使用锁定的Eclipse/BWMT捆绑包。请勿针对未探测版本启用草稿/保存功能。
  • 查询未找到: 在BW Query Designer中以只读方式打开它并重试;不得通过猜测私有API扩大访问范围。
  • 需要登录: 暂停并告知用户仅可在原生SAP对话框中输入凭据。
  • 名称冲突: 停止操作。需要使用不同的全新技术名称。
  • 传输对话框: 将控制权交给用户;自动化操作不会确认传输。
  • 部署中断: 保留之前的激活状态。失败的暂存/下载目录将保留以供人工检查。

Bundled Resources

捆绑资源

  • references/architecture-and-security.md
    — end-to-end architecture, 22-tool classification, query-creation sequence, and the security-hardening reference (links the commit-anchored audit doc).
  • references/deployment-and-trust.md
    — no-install local deployment and optional remote release trust.
  • references/connection-metadata.md
    — password-free connection schema and login boundaries.
  • references/query-spec-v1.md
    — specification fields, validation, gap analysis, and example.
  • references/bwmt-api-map.md
    — javap-verified BWMT 1.27.36 API surface the capability adapter binds to.
  • references/mcp-tools.md
    — complete tool surface and operation classifications.
  • references/query-design-rules.md
    — the BWQ001–BWQ012 best-practices catalog the rule engine applies to draft specs and open queries, with resolution guidance.
  • references/query-templates.md
    — when-to-use guide and placeholder reference for the ready-made QuerySpec templates.
  • references/query-templates/
    — starting-point QuerySpec v1.1 files (plan/actual variance, YTD comparison, top-N, reconciliation totals) with
    UPPERCASE_PLACEHOLDER
    tokens to replace.
  • scripts/
    at plugin root — portable deployment/MCP bootstraps.
  • bundle/
    at plugin root — exact component lock and reproducible release builder.
  • references/architecture-and-security.md
    — 端到端架构、22种工具分类、查询创建序列以及安全加固参考(链接基于提交的审计文档)。
  • references/deployment-and-trust.md
    — 无需安装的本地部署和可选的远程发布信任。
  • references/connection-metadata.md
    — 无密码连接模式和登录边界。
  • references/query-spec-v1.md
    — 规范字段、验证、漏洞分析及示例。
  • references/bwmt-api-map.md
    — 经javap验证的BWMT 1.27.36 API接口,功能适配器绑定到这些接口。
  • references/mcp-tools.md
    — 完整的工具接口和操作分类。
  • references/query-design-rules.md
    — BWQ001–BWQ012最佳实践目录,规则引擎将其应用于草稿规范和打开的查询,并提供解决指导。
  • references/query-templates.md
    — 现成QuerySpec模板的使用场景指南和占位符参考。
  • references/query-templates/
    — 起点QuerySpec v1.1文件(计划/实际差异、年初至今对比、前N项、对账总计),含需替换的
    UPPERCASE_PLACEHOLDER
    标记。
  • 插件根目录下的
    scripts/
    — 可移植部署/MCP引导程序。
  • 插件根目录下的
    bundle/
    — 精确的组件锁定和可重现的发布构建器。

Source Verification

源代码验证

Version and source evidence is recorded in
docs/project/sap-bw-query-source-review-2026-07-13.md
and the repository verification ledger. Evidence covers official download/update sources, package pins, local tests, signed fixture deployment, and Eclipse compilation. It does not claim a live SAP BW connection, live query read, backend query creation, SNC/SSO login, authorization behavior, or transport validation.
版本和源代码证据记录在
docs/project/sap-bw-query-source-review-2026-07-13.md
和仓库验证分类账中。证据涵盖官方下载/更新源、包锁定、本地测试、已签名的固定装置部署以及Eclipse编译。它不声明支持实时SAP BW连接、实时查询读取、后端查询创建、SNC/SSO登录、授权行为或传输验证。

Related Skills

相关技能

  • sap-hana-cli: Use for HANA database inspection outside BW Query Designer; do not share credentials between workflows.
  • sap-sqlscript: Use for SQLScript or HANA procedure work, not BW query objects.
  • sap-datasphere: Use for SAP Datasphere modeling; this skill remains BWMT/HANA Studio only.
  • sap-hana-cli:用于在BW Query Designer之外进行HANA数据库检查;请勿在工作流之间共享凭据。
  • sap-sqlscript:用于SQLScript或HANA过程工作,而非BW查询对象。
  • sap-datasphere:用于SAP Datasphere建模;本技能仅适用于BWMT/HANA Studio。