Sap Sac Scripting

SAP Analytics Cloud Scripting

Related Skills

• sap-dependency-security: Use when securing dependency, SDK/tooling, and source-pinned SAC MCP upgrades used in story automation pipelines
• sap-browser-automation: Use for in-app manual authentication, consent-gated Edge profile reuse, fresh Edge/CDP startup, auth-state bootstrap, and browser recovery

When to Use This Skill

Use this skill when writing or debugging SAC Analytics Designer scripts, Optimized Story Experience scripts, widget APIs, data-source filtering/selection logic, planning/version scripts, export/navigation handlers, performance-sensitive story logic, or SAC MCP-assisted automation.

Comprehensive skill for scripting in SAP Analytics Cloud (SAC) Analytics Designer and Optimized Story Experience.

For authenticated SAC browser runtime inspection, use sap-browser-automation for manual in-app authentication, consent-gated Edge profile reuse, fresh Edge/CDP startup, auth-state bootstrap, and recovery. Load local references/edge-cdp-control.md for SAC scripting-specific boundaries. Use CDP for local runtime triage, widget-state checks, and approved screenshots; do not touch unrelated tabs.

Getting Started

When the user invokes this skill with no specific task (e.g. "help with SAC scripting", "use SAC scripting skill", or no follow-up question), respond with this structured orientation:

Welcome! I can help you with SAP Analytics Cloud scripting. First, which environment are you working in? 1. Analytics Designer — application-based scripting, full API 2. Optimized Story Experience — story-based scripting, OSE API (v2025.20) Then, what do you need help with? - Write a new script (filter, planning, navigation, export...) - Debug an existing script - Optimize performance - Find the right API method - Planning operations (version management, data locking...)

Plugin Components

This plugin provides specialized tools for SAC development:

Agents (use via Task tool):

• sac-script-debugger - Debug script errors, trace issues
• sac-performance-optimizer - Analyze and fix performance bottlenecks
• sac-planning-assistant - Guide planning operations and version management
• sac-api-helper - Find correct APIs and provide code examples

Commands (use via /command):

• /sac-script-template - Generate script templates (filter, planning, export, etc.)
• /sac-debug - Interactive debugging guidance
• /sac-optimize - Performance analysis and recommendations
• /sac-planning - Planning operation templates

Hooks:

• Automatic validation on SAC script writes for common issues

MCP Setup

This plugin ships with a .mcp.json that connects to the trusted secondsky/sap_analytics_cloud_mcp server, exposing 90 SAC REST API tools across 11 service areas (Content, Data Export, Data Import, Multi Actions, Calendar, Content Transport, User Management, Monitoring, Schedule & Publication, Translation, Smart Query).

The SAC MCP is source-installed, not npm-installed. Use sap-dependency-security before changing the trusted fork or commit pin because this server receives SAC OAuth credentials and exposes tenant API tools.

Before using MCP tools, check if the server is already installed:

• Look for .claude/sac-mcp.local.md in the project
• Or check if SAC_MCP_PATH is set in the environment

If not installed, ask the user once: "Would you like help setting up the SAC MCP server?"

If yes, guide them through:

1. Clone and build: ``bash git clone https://github.com/secondsky/sap_analytics_cloud_mcp cd sap_analytics_cloud_mcp git checkout 2020235505d98111c2889598ab2217c1619b6943 npm ci --ignore-scripts npm run build ``

1. Configure environment variables:

• SAC_MCP_PATH — absolute path to the cloned repo (e.g. /home/user/sap_analytics_cloud_mcp)
• SAC_MCP_COMMIT — 2020235505d98111c2889598ab2217c1619b6943
• SAC_BASE_URL — SAC tenant root URL (e.g. https://mytenant.eu10.hanacloudservices.cloud.sap)
• SAC_TOKEN_URL — OAuth token endpoint
• SAC_CLIENT_ID / SAC_CLIENT_SECRET — from SAC OAuth client configuration

1. After successful install, write .claude/sac-mcp.local.md (gitignored) with: ```markdown # SAC MCP Installation Record

• Installed: [date]
• Repository: https://github.com/secondsky/sap_analytics_cloud_mcp
• Commit: 2020235505d98111c2889598ab2217c1619b6943
• Path: [absolute path to build/index.js]
• Build command: npm ci --ignore-scripts && npm run build
• Env vars configured: SAC_MCP_PATH, SAC_MCP_COMMIT, SAC_BASE_URL, SAC_TOKEN_URL, SAC_CLIENT_ID, SAC_CLIENT_SECRET ```

This prevents re-prompting in future sessions.

What's New in Q2 2026 (2026.8)

Key scripting enhancements in the latest SAC release:

• Enhanced `onAfterExecute` Event - Upload events now include message, statistics, rejected records, target version, and filename
• Data Export API Job Monitoring - New job monitor tab for delta extraction and calculation jobs
• Data Import Service API - Import master data to public dimensions in SAP Datasphere; import external fact data to private versions
• Multi-Action API Step - HTTP 204 response now allowed; enhanced header field restrictions
• Export to S/4HANA Deprecated - Use write-back integration scenario instead
• Asymmetric Reporting - Differing time ranges, hierarchies, and measures per row/column
• Composite Versioning - Manage multiple composite versions during story design

See references/whats-new-qrc2-2026.md for complete details.

Environment Detection

Before writing or analyzing any script, identify which SAC environment the user is working in.

Detection signals:

When environment is unclear, ask ONE concise question before proceeding:

"Are you scripting in Analytics Designer or Optimized Story Experience? This determines which API reference I use."

Do not ask again after the user answers.

After confirmation, use the correct references:

• OSE → references/ose-api-*.md (8 files, Q2 2026, v2025.20)
• Analytics Designer → references/api-*.md (existing files)

Reporting Story Workflow

Use this workflow for read-only SAC stories, dashboards, and management reports. It is separate from planning: route writeback, version publishing, data actions, allocations, data locking, and other planning operations to sap-sac-planning.

1. Establish the contract: identify the tenant, story, data source, intended audience, and whether the user forbids model changes. Treat a reporting-only request as story-layer work unless the user explicitly authorizes a broader scope.
2. Inspect actual metadata: confirm the selected model and use only its exposed dimensions, measures, hierarchies, time fields, currencies, and comparison categories. Never invent a field because it would be useful for a proposed chart or KPI.
3. Design at the story layer: define pages, widgets, filters, selections, navigation, and supported story calculations. Label comparisons explicitly as actual-versus-budget, forecast, or another available category.
4. Implement safely: before saving, verify that the current SAC area is Story Designer rather than Modeler. Keep common filters and dependent-widget interactions read-only and non-destructive.