一键导入
sap-s4
Read SAP S/4HANA finance data — cost centres, GL accounts, variance analysis, journal entries, vendors, plants, materials, production orders.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Read SAP S/4HANA finance data — cost centres, GL accounts, variance analysis, journal entries, vendors, plants, materials, production orders.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Read the plant-floor Azure IoT surface — device twins (spindles, conveyors, robotic arms, vision systems), time-series telemetry with pre-annotated alarms, downtime events with cause codes and lot ids, and per-line OEE rollups (Availability × Performance × Quality).
Share generated files (PDFs, charts, CSVs) with Frank by writing them to /tmp and referencing the absolute path. The frontend auto-converts /tmp paths into download links.
Build the downloadable incident brief PDF — cover + KPI strip + OEE chart + downtime timeline + root-cause narrative + supplier/material signals + recommended actions + sign-off, per SOP §7.1. Renders via the inline HTML template + Playwright.
Microsoft 365 surface — READ Frank's mailbox / Wes's calendar / OneDrive (shift reports, SOPs) AND a strict H-I-T-L workflow to draft and send an email (e.g. brief Wes on the morning incident).
Compute and plot OEE — a 7-day trend chart with target/threshold lines, an overlay of telemetry alarms and downtime stops, plus a flat CSV export. Saves /tmp/oee-trend-<plant>-line-<N>-<date>.png + .csv.
The Olympus Cleveland-plant Standard Operating Procedure — alarm thresholds, escalation matrix, supplier quality-hold rules, OEE definitions, incident-brief template requirements. Cite the section number when answering.
| name | sap-s4 |
| description | Read SAP S/4HANA finance data — cost centres, GL accounts, variance analysis, journal entries, vendors, plants, materials, production orders. |
| enabled | true |
This is the read interface to sap-s4-mcp-server. Every cost centre, GL code, JE id, vendor id, plant, or material the user mentions must be resolved through one of these tools before you answer. Never fabricate financial data.
| User intent | Tool |
|---|---|
| List cost centres (optionally by org / owner / status) | sap_list_cost_centres |
| One cost centre with full detail (budget, owner_user_id) | sap_get_cost_centre |
| List GL accounts (filter by type Asset / Liability / Revenue / COGS / OpEx / Other) | sap_list_gl_accounts |
Variance analysis for a period — debit GL × cost-centre with normal / watch / investigate flags | sap_get_variance_analysis |
| List journal entries — by period, status, type | sap_list_journal_entries |
| One JE with full line detail (Dr/Cr/CC/memo) | sap_get_journal_entry |
| Find a vendor by name substring | sap_search_vendors_by_name |
| One vendor with credit / sanctions / block detail | sap_get_vendor |
| Plants / materials / production orders (manufacturing demos) | sap_list_plants, sap_list_materials, sap_list_production_orders, sap_get_production_order |
Platform Engineering (CC-0011), Software & Subscriptions (GL 6400), JE-30099, Sentinel Observability Inc (V-1102).sap_propose_journal_entry, sap_post_journal_entry) live in the journal-entry-proposal skill — they are H-I-T-L gated.owner_user_id is a workday EMP-* id — hand off to the workday skill to resolve to a human name. Vendor invoice expected? Hand off to m365-graph m365_search_messages to see if AR has emailed about it.Prefer compact tables with column headers; lead numeric columns with the currency or the unit ($, %, qty). Don't dump raw JSON — synthesise.