sap-sac-planning

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

SAP Analytics Cloud Planning Skill

SAP Analytics Cloud (SAC) 规划技能

Related Skills

相关技能

  • sap-sac-scripting: Use for Analytics Designer/OSE scripts that automate planning interactions
  • sap-datasphere: Use for Seamless Planning with Datasphere and data foundation design
  • sap-sac-custom-widget: Use when planning applications include custom widgets
  • sap-dependency-security: Use for source-pinned SAC MCP setup and local tooling trust
Comprehensive skill for building enterprise planning applications with SAP Analytics Cloud.

  • sap-sac-scripting: 用于编写可自动化规划交互的Analytics Designer/OSE脚本
  • sap-datasphere: 用于与Datasphere的无缝规划及数据基础设计
  • sap-sac-custom-widget: 当规划应用包含自定义组件时使用
  • sap-dependency-security: 用于源固定的SAC MCP设置及本地工具信任配置
这是用于基于SAP Analytics Cloud构建企业级规划应用的综合性技能。

Reference Add-Ons (2026)

参考附加组件(2026年)

  • Execution guides:
    references/data-actions.md
    ,
    references/multi-actions.md
    ,
    references/allocations.md
    ,
    references/scheduling-calendar.md
    ,
    references/data-locking.md
  • Modeling & governance:
    references/modeling-basics.md
    ,
    references/version-management.md
    ,
    references/version-edit-modes.md
    ,
    references/version-publishing-notes.md
  • Calculations & intelligence:
    references/advanced-formulas.md
    ,
    references/predictive-conversion.md
    ,
    references/ai-planning-analytics.md
    ,
    references/api-snippets.md
  • Workflow aids:
    references/input-tasks.md
    ,
    references/job-monitoring.md
  • Browser triage: shared
    sap-browser-automation
    for manual in-app authentication, approved Edge profile copying, fresh Edge/CDP setup,
    DevToolsActivePort
    fallback, and target selection; local
    references/edge-cdp-control.md
    retains planning writeback safety
  • Added in 2025:
    references/seamless-planning-datasphere.md
    ,
    references/bpc-live-connection.md
    ,
    references/value-driver-trees.md
    ,
    references/data-action-tracing.md
  • New in 2026:
    references/whats-new-2026-planning.md
  • Ready-to-use templates:
    templates/data-action-checklist.md
    ,
    templates/multi-action-checklist.md
    ,
    templates/parameter-table.md
Use these to keep instructions concise in this file while deep-dives remain one click away.
For authenticated SAC planning browser inspection, use
sap-browser-automation
for the browser/authentication layer and load local
references/edge-cdp-control.md
for planning-specific boundaries. Use CDP for local read-only triage of planning tables, console errors, data action status, and approved screenshots; require explicit approval before any writeback, publish, data action, multi action, or lock-changing interaction.

  • 执行指南:
    references/data-actions.md
    references/multi-actions.md
    references/allocations.md
    references/scheduling-calendar.md
    references/data-locking.md
  • 建模与治理:
    references/modeling-basics.md
    references/version-management.md
    references/version-edit-modes.md
    references/version-publishing-notes.md
  • 计算与智能:
    references/advanced-formulas.md
    references/predictive-conversion.md
    references/ai-planning-analytics.md
    references/api-snippets.md
  • 工作流辅助工具:
    references/input-tasks.md
    references/job-monitoring.md
  • 浏览器问题排查:共享的
    sap-browser-automation
    用于手动应用内认证、已批准的Edge配置文件复制、全新Edge/CDP设置、
    DevToolsActivePort
    回退及目标选择;本地
    references/edge-cdp-control.md
    保留规划回写安全性
  • 2025年新增
    references/seamless-planning-datasphere.md
    references/bpc-live-connection.md
    references/value-driver-trees.md
    references/data-action-tracing.md
  • 2026年新增
    references/whats-new-2026-planning.md
  • 即用型模板:
    templates/data-action-checklist.md
    templates/multi-action-checklist.md
    templates/parameter-table.md
使用这些资源可保持本文档中的说明简洁,同时深入内容只需一键访问。
对于已认证的SAC规划浏览器检查,使用
sap-browser-automation
处理浏览器/认证层,并加载本地
references/edge-cdp-control.md
获取规划特定边界。使用CDP对规划表格、控制台错误、数据操作状态及已批准截图进行本地只读排查;在进行任何回写、发布、数据操作、多操作或锁定变更交互前,需获得明确批准。

Table of Contents

目录

When to Use This Skill

何时使用本技能

Use this skill when working on tasks involving:
Planning Application Development:
  • Creating planning-enabled stories with data entry
  • Building analytics designer applications for planning
  • Implementing input forms and planning tables
  • Configuring planning models with Version and Date dimensions
  • Setting up data sources for planning scenarios
Data Actions & Multi Actions:
  • Creating data actions for copy, allocation, and calculations
  • Building multi actions to orchestrate planning operations
  • Configuring parameters (member, number, string, datetime types)
  • Implementing embedded data actions
  • Setting up API steps for external integrations
Version Management:
  • Managing public and private versions
  • Publishing workflows (Publish As, Publish Private Data)
  • Sharing private versions with collaborators
  • Version creation and deletion via API
Planning Workflows:
  • Setting up calendar-based planning processes
  • Creating general tasks, review tasks, and composite tasks
  • Implementing multi-level approval workflows
  • Configuring data locking tasks
  • Managing task dependencies
JavaScript Planning APIs:
  • Using getPlanning() API for data entry
  • Working with PlanningModel API for master data
  • Implementing DataSource API for filtering and querying
  • Writing scripts for planning automation
  • Handling version management via API
Data Entry & Allocation:
  • Implementing spreading (to child members)
  • Configuring distribution (between siblings)
  • Setting up rule-based allocations
  • Copy/paste operations in planning tables
  • Using advanced formulas for calculations
Data Locking:
  • Configuring data locking on models
  • Setting up lock states (locked, restricted, open)
  • Creating data locking tasks in calendar
  • Implementing event-based data locking
  • Integrating data locking in multi actions
Seamless Planning with Datasphere (2025):
  • Planning models with Datasphere storage
  • Cross-model planning with unified data
  • Direct persistence to Datasphere
  • Enterprise data governance for planning
BPC Live Connection:
  • Planning with BPC Embedded on S/4HANA
  • Running BPC planning sequences from SAC
  • Master data planning via BPC
  • Live data connection configuration
Value Driver Trees:
  • Building business value chain visualizations
  • What-if analysis and scenario simulation
  • Driver-based planning
  • Interactive planning dashboards
Data Action Debugging:
  • Tracing data action execution
  • Adding tracepoints for debugging
  • Analyzing intermediate results
  • Troubleshooting allocation issues

当处理以下任务时使用本技能:
规划应用开发
  • 创建支持数据录入的规划故事
  • 构建用于规划的Analytics Designer应用
  • 实现输入表单和规划表格
  • 配置带有版本和日期维度的规划模型
  • 为规划场景设置数据源
数据操作与多操作
  • 创建用于复制、分配和计算的数据操作
  • 构建用于编排规划操作的多操作
  • 配置参数(成员、数字、字符串、日期时间类型)
  • 实现嵌入式数据操作
  • 为外部集成设置API步骤
版本管理
  • 管理公共和私有版本
  • 发布工作流(发布为、发布私有数据)
  • 与协作者共享私有版本
  • 通过API创建和删除版本
规划工作流
  • 设置基于日历的规划流程
  • 创建常规任务、审核任务和复合任务
  • 实现多级审批工作流
  • 配置数据锁定任务
  • 管理任务依赖关系
JavaScript规划API
  • 使用getPlanning() API进行数据录入
  • 使用PlanningModel API处理主数据
  • 实现DataSource API进行过滤和查询
  • 编写用于规划自动化的脚本
  • 通过API处理版本管理
数据录入与分配
  • 实现分摊(至子成员)
  • 配置分配(在同级成员间)
  • 设置基于规则的分配
  • 规划表格中的复制/粘贴操作
  • 使用高级公式进行计算
数据锁定
  • 在模型上配置数据锁定
  • 设置锁定状态(锁定、受限、开放)
  • 在日历中创建数据锁定任务
  • 实现基于事件的数据锁定
  • 在多操作中集成数据锁定
与Datasphere的无缝规划(2025年):
  • 基于Datasphere存储的规划模型
  • 基于统一数据的跨模型规划
  • 直接持久化至Datasphere
  • 面向规划的企业级数据治理
BPC实时连接
  • 基于S/4HANA上的BPC Embedded进行规划
  • 从SAC运行BPC规划序列
  • 通过BPC进行主数据规划
  • 实时数据连接配置
价值驱动树
  • 构建业务价值链可视化
  • 假设分析和场景模拟
  • 基于驱动因素的规划
  • 交互式规划仪表板
数据操作调试
  • 追踪数据操作执行过程
  • 添加追踪点进行调试
  • 分析中间结果
  • 排查分配问题

Quick Start

快速入门

Creating a Planning-Enabled Story

创建支持规划的故事

  1. Create Planning Model with required dimensions:
    • Version dimension (required)
    • Date dimension (required)
    • Account dimension (recommended)
    • Other business dimensions
  2. Add Table Widget to story and link to planning model
  3. Enable Planning on the table:
    • Select table → Planning panel → Enable Planning
    • Configure version selection (public or private)
  4. Configure Data Entry:
    • Set editable measures/accounts
    • Configure spreading behavior
    • Set up validation rules
  1. 创建规划模型,包含所需维度:
    • 版本维度(必填)
    • 日期维度(必填)
    • 科目维度(推荐)
    • 其他业务维度
  2. 向故事中添加表格组件并关联至规划模型
  3. 在表格上启用规划
    • 选择表格 → 规划面板 → 启用规划
    • 配置版本选择(公共或私有)
  4. 配置数据录入
    • 设置可编辑的度量/科目
    • 配置分摊行为
    • 设置验证规则

Creating an Analytics Designer Planning Application

创建Analytics Designer规划应用

  1. Create Analytic Application (not Optimized Story)
  2. Add Planning Model as data source
  3. Add Table Widget and enable planning
  4. Write Scripts for:
    • Version selection
    • Data submission
    • Custom validation
    • Workflow triggers

  1. 创建分析应用(非优化故事)
  2. 添加规划模型作为数据源
  3. 添加表格组件并启用规划
  4. 编写脚本用于:
    • 版本选择
    • 数据提交
    • 自定义验证
    • 工作流触发

Core Concepts

核心概念

Model Types

模型类型

Planning Model:
  • Supports data write-back
  • Requires Version and Date dimensions
  • Enables spreading, distribution, allocation
  • Supports data locking
  • Used for budgeting, forecasting, planning
Analytic Model:
  • Read-only (no write-back)
  • No required dimensions
  • Better performance for reporting
  • Use when planning not needed
规划模型
  • 支持数据回写
  • 要求包含版本和日期维度
  • 支持分摊、分配、分配操作
  • 支持数据锁定
  • 用于预算、预测、规划
分析模型
  • 只读(无回写)
  • 无必填维度
  • 报表性能更优
  • 无需规划时使用

Version Management

版本管理

Public Versions:
  • Visible to all users with access
  • Shared across the organization
  • Require publish to update
Private Versions:
  • Visible only to creator (unless shared)
  • Used for simulation and what-if analysis
  • Can be published to public or new version
Edit Mode:
  • Temporary private copy when editing public version
  • Changes visible only to editor until published
  • Automatic validation on publish
Reference: See
references/version-management.md
for detailed workflows.
公共版本
  • 对所有拥有访问权限的用户可见
  • 在整个组织内共享
  • 更新需发布
私有版本
  • 仅对创建者可见(除非共享)
  • 用于模拟和假设分析
  • 可发布为公共版本或新版本
编辑模式
  • 编辑公共版本时的临时私有副本
  • 变更仅在发布前对编辑者可见
  • 发布时自动验证
参考:详细工作流请参见
references/version-management.md

Planning API Overview

规划API概述

getPlanning() API - Table planning operations:
javascript
// Check if planning is enabled
var isEnabled = Table_1.getPlanning().isEnabled();

// Get public versions
var publicVersions = Table_1.getPlanning().getPublicVersions();

// Get private version
var privateVersion = Table_1.getPlanning().getPrivateVersion();

// Set user input (data entry)
Table_1.getPlanning().setUserInput(selection, value);

// Submit data changes
Table_1.getPlanning().submitData();
PlanningModel API - Master data operations:
javascript
// Get dimension members with properties
var members = PlanningModel_1.getMembers("CostCenter");

// Create new members
PlanningModel_1.createMembers("CostCenter", [
    {id: "CC100", description: "Marketing"}
]);

// Update existing members
PlanningModel_1.updateMembers("CostCenter", [
    {id: "CC100", description: "Marketing Dept"}
]);

// Delete members
PlanningModel_1.deleteMembers("CostCenter", ["CC100"]);
DataSource API - Filtering and querying:
javascript
// Set dimension filter
Table_1.getDataSource().setDimensionFilter("Version",
    "[Version].[parentId].&[public.Actual]");

// Get members with booked values only
var members = Table_1.getDataSource().getMembers("Account",
    {accessMode: MemberAccessMode.BookedValues});

// Remove filter
Table_1.getDataSource().removeDimensionFilter("Version");
Reference: See
references/api-reference.md
for complete API documentation.

getPlanning() API - 表格规划操作:
javascript
// 检查是否启用规划
var isEnabled = Table_1.getPlanning().isEnabled();

// 获取公共版本
var publicVersions = Table_1.getPlanning().getPublicVersions();

// 获取私有版本
var privateVersion = Table_1.getPlanning().getPrivateVersion();

// 设置用户输入(数据录入)
Table_1.getPlanning().setUserInput(selection, value);

// 提交数据变更
Table_1.getPlanning().submitData();
PlanningModel API - 主数据操作:
javascript
// 获取带属性的维度成员
var members = PlanningModel_1.getMembers("CostCenter");

// 创建新成员
PlanningModel_1.createMembers("CostCenter", [
    {id: "CC100", description: "Marketing"}
]);

// 更新现有成员
PlanningModel_1.updateMembers("CostCenter", [
    {id: "CC100", description: "Marketing Dept"}
]);

// 删除成员
PlanningModel_1.deleteMembers("CostCenter", ["CC100"]);
DataSource API - 过滤和查询:
javascript
// 设置维度过滤器
Table_1.getDataSource().setDimensionFilter("Version",
    "[Version].[parentId].&[public.Actual]");

// 获取仅包含已记账值的成员
var members = Table_1.getDataSource().getMembers("Account",
    {accessMode: MemberAccessMode.BookedValues});

// 移除过滤器
Table_1.getDataSource().removeDimensionFilter("Version");
参考:完整API文档请参见
references/api-reference.md

Data Actions

数据操作

Data actions perform calculations and data manipulation on planning models.
数据操作用于对规划模型执行计算和数据处理。

Step Types

步骤类型

Step TypePurpose
CopyMove data between dimensions/versions
Advanced FormulaComplex calculations
AllocationRule-based distribution
Currency ConversionConvert currencies
Embedded Data ActionRun another data action
步骤类型用途
复制在维度/版本间移动数据
高级公式复杂计算
分配基于规则的分配
货币转换转换货币
嵌入式数据操作运行另一个数据操作

Creating a Copy Step

创建复制步骤

Source:
  Version = Actual
  Year = 2024

Target:
  Version = Budget
  Year = 2025

Mapping:
  Account = Account (same)
  CostCenter = CostCenter (same)
源:
  版本 = Actual
  年份 = 2024

目标:
  版本 = Budget
  年份 = 2025

映射:
  科目 = 科目(保持一致)
  成本中心 = 成本中心(保持一致)

Advanced Formula Example

高级公式示例

// Calculate forecast = Actual + (Budget - Actual) * 0.5
[Version].[Forecast] = [Version].[Actual] +
    ([Version].[Budget] - [Version].[Actual]) * 0.5
// 计算预测值 = 实际值 + (预算值 - 实际值) * 0.5
[Version].[Forecast] = [Version].[Actual] +
    ([Version].[Budget] - [Version].[Actual]) * 0.5

Parameters

参数

Add parameters to make data actions reusable:
  • Member Parameter: Select dimension member
  • Number Parameter: Enter numeric value
  • String Parameter: Enter text (2025+)
  • Datetime Parameter: Select date/time (2025+)
Reference: See
references/data-actions.md
for complete configuration guide.

添加参数使数据操作可复用:
  • 成员参数:选择维度成员
  • 数字参数:输入数值
  • 字符串参数:输入文本(2025年及以上版本支持)
  • 日期时间参数:选择日期/时间(2025年及以上版本支持)
参考:完整配置指南请参见
references/data-actions.md

Multi Actions

多操作

Multi actions orchestrate multiple planning operations across models and versions.
多操作用于编排跨模型和版本的多个规划操作。

Available Step Types

可用步骤类型

  1. Data Action Step: Run data action with parameters
  2. Version Management Step: Publish versions
  3. Predictive Step: Run forecasting scenarios
  4. Data Import Step: Import from SAP sources
  5. API Step: Call external HTTP APIs
  6. Data Locking Step: Lock/unlock data slices
  7. PaPM Step: Run Profitability and Performance Management
  1. 数据操作步骤:带参数运行数据操作
  2. 版本管理步骤:发布版本
  3. 预测步骤:运行预测场景
  4. 数据导入步骤:从SAP源导入数据
  5. API步骤:调用外部HTTP API
  6. 数据锁定步骤:锁定/解锁数据切片
  7. PaPM步骤:运行盈利能力与绩效管理

Example Multi Action Flow

多操作流程示例

1. Clean target version (Data Action)
2. Import actuals (Data Import)
3. Run forecast (Predictive)
4. Calculate allocations (Data Action)
5. Publish to public version (Version Management)
6. Lock published data (Data Locking)
1. 清理目标版本(数据操作)
2. 导入实际数据(数据导入)
3. 运行预测(预测)
4. 计算分配(数据操作)
5. 发布至公共版本(版本管理)
6. 锁定已发布数据(数据锁定)

Cross-Model Parameters

跨模型参数

When using public dimensions, create cross-model parameters to share values across steps in different models.
Reference: See
references/data-actions.md
for multi action configuration.

使用公共维度时,创建跨模型参数以在不同模型的步骤间共享值。
参考:多操作配置请参见
references/data-actions.md

S/4HANA ACDOCP Export

S/4HANA ACDOCP导出

Legacy/deprecated path for exporting native planning data from SAC to SAP S/4HANA's ACDOCP table (central ERP plan data storage). As of Q2 2026, SAP deprecates exporting model data to SAP S/4HANA and recommends the write-back integration scenario instead. Keep this section for maintaining existing landscapes, not as the default design for new planning solutions.
这是将SAC原生规划数据导出至SAP S/4HANA的ACDOCP表(中央ERP计划数据存储)的旧版/已弃用路径。截至2026年第二季度,SAP弃用了将模型数据导出至SAP S/4HANA的功能,建议改用回写集成场景。保留本节用于维护现有环境,而非作为新规划解决方案的默认设计。

Architecture

架构

SAC Planning Model → Data Export Service → Cloud Connector → API_PLPACDOCPDATA_SRV → ACDOCP
SAC规划模型 → 数据导出服务 → 云连接器 → API_PLPACDOCPDATA_SRV → ACDOCP

Prerequisites

前提条件

RequirementDetails
Legacy ModeMust be enabled on planning model
OData ServiceActivate
API_PLPACDOCPDATA_SRV
in
/IWFND/MAINT_SERVICE
Cloud ConnectorRequired for on-premise S/4HANA
要求详情
旧版模式必须在规划模型上启用
OData服务
/IWFND/MAINT_SERVICE
中激活
API_PLPACDOCPDATA_SRV
云连接器本地部署的S/4HANA需要

Required Dimensions for Export

导出所需维度

  • Version (Plan Category): Only public versions can be exported
  • FiscalYearPeriod: Mandatory in export scope
  • Measure: Only ONE target measure per export job
  • G/L Account: Required for ACDOCP mapping
  • 版本(计划类别):仅公共版本可导出
  • FiscalYearPeriod:导出范围中必填
  • 度量:每个导出作业仅支持一个目标度量
  • 总账科目:ACDOCP映射必填

Export Behavior

导出行为

  • Exported data overwrites existing data within scope
  • S/4HANA generates delta records for changes
  • Deletions don't propagate: Set values to 0 and re-export to clear ACDOCP data
  • Filters cannot be changed after export job creation—name jobs descriptively
  • 导出的数据会覆盖范围内的现有数据
  • S/4HANA为变更生成增量记录
  • 删除操作不会传播:将值设为0并重新导出以清除ACDOCP数据
  • 导出作业创建后无法更改过滤器——请为作业命名以清晰描述其用途

Legacy Maintenance Checklist

旧版维护检查清单

Do not create this path for new implementations without confirming the deprecation impact, SAP Note 3707288 guidance, and a supported migration path.
  1. Enable Legacy Mode on planning model
  2. Create S/4HANA connection with Cloud Connector
  3. Data Management → Create Data Export Job
  4. Map dimensions to ACDOCP fields
  5. Define export scope (FiscalYearPeriod + PlanningCategory mandatory)
  6. Schedule or run export
Reference: See
references/s4hana-acdocp-export.md
for legacy configuration details and
references/whats-new-2026-planning.md
for the Q2 2026 deprecation note.

在确认弃用影响、SAP Note 3707288指南及支持的迁移路径前,请勿为新实现创建此路径。
  1. 在规划模型上启用旧版模式
  2. 使用云连接器创建S/4HANA连接
  3. 数据管理 → 创建数据导出作业
  4. 将维度映射至ACDOCP字段
  5. 定义导出范围(FiscalYearPeriod + PlanningCategory为必填项)
  6. 调度或运行导出
参考:旧版配置详情请参见
references/s4hana-acdocp-export.md
,2026年第二季度弃用说明请参见
references/whats-new-2026-planning.md

Seamless Planning with Datasphere

与Datasphere的无缝规划

Seamless Planning unifies SAC planning with SAP Datasphere, enabling enterprise-grade storage and governance for plan data.
无缝规划将SAC规划与SAP Datasphere统一,为计划数据提供企业级存储和治理。

Architecture Overview

架构概述

SAC (Planning Logic & UX) ──Direct Persistence──► Datasphere (Data Storage & Governance)
What stays in SAC: Planning calculations, version management, data actions, calendar workflows What moves to Datasphere: Fact data, public dimensions, physical storage, data governance
SAC(规划逻辑与用户体验)──直接持久化──► Datasphere(数据存储与治理)
保留在SAC中的内容:规划计算、版本管理、数据操作、日历工作流 迁移至Datasphere的内容:事实数据、公共维度、物理存储、数据治理

Key Benefits

核心优势

BenefitDescription
Unified DataCentralized storage ensures consistency
Direct PersistenceChanges in SAC instantly reflect in Datasphere
Optimized ResourcesReduces SAC memory and storage footprint
Enterprise ReusabilityDatasphere modeling extends to planning data
优势描述
统一数据集中存储确保一致性
直接持久化SAC中的变更即时反映在Datasphere中
优化资源减少SAC内存和存储占用
企业级复用性Datasphere建模可扩展至规划数据

Prerequisites

前提条件

  1. SAC tenant on SAP HANA Cloud - Verify in System → About
  2. Co-located tenants - Same SAP data center region
  3. 1:1 tenant linkage - One SAC tenant to one Datasphere tenant
  4. Consistent IdP - Same SAML identity provider
  5. Datasphere space roles - DW Modeler, DW Integrator, or DW Space Administrator
  1. 基于SAP HANA Cloud的SAC租户 - 在系统 → 关于中验证
  2. 同区域租户 - 位于同一SAP数据中心区域
  3. 1:1租户关联 - 一个SAC租户对应一个Datasphere租户
  4. 一致的身份提供商 - 使用相同的SAML身份提供商
  5. Datasphere空间角色 - DW Modeler、DW Integrator或DW Space Administrator

Quick Setup

快速设置

  1. Create new Planning Model
  2. Select SAP Datasphere Space as Data Storage Location
  3. Configure dimensions (public dimensions stored in Datasphere)
  4. Enable Expose to Datasphere in Model Details
  5. Plan normally in SAC - changes persist automatically
  1. 创建新的规划模型
  2. 选择SAP Datasphere空间作为数据存储位置
  3. 配置维度(公共维度存储在Datasphere中)
  4. 在模型详情中启用暴露至Datasphere
  5. 在SAC中正常进行规划 - 变更会自动持久化

Cross-Model Planning

跨模型规划

All models for cross-model operations (data actions, multi actions) must be in the same Datasphere space.
Reference: See
references/seamless-planning-datasphere.md
for detailed architecture, configuration, and troubleshooting.

所有用于跨模型操作(数据操作、多操作)的模型必须位于同一Datasphere空间中。
参考:详细架构、配置及故障排除请参见
references/seamless-planning-datasphere.md

BPC Live Connection

BPC实时连接

SAC supports live data connections to BPC Embedded on S/4HANA, enabling planning with the BPC engine while using SAC's modern interface.
SAC支持与S/4HANA上的BPC Embedded建立实时数据连接,可使用BPC引擎进行规划,同时借助SAC的现代化界面。

Supported BPC Versions

支持的BPC版本

VersionPlanning Support
BPC Embedded (S/4HANA)Full planning features
BPC for NetWeaverLimited (read-only)
BPC StandardExport to BPC required
版本规划支持
BPC Embedded (S/4HANA)完整规划功能
BPC for NetWeaver有限支持(只读)
BPC Standard需要导出至BPC

Planning Features via BPC Live

通过BPC实时连接实现的规划功能

  • Data Entry: Direct input to BPC models
  • Planning Sequences: Execute FOX scripts from SAC
  • Version Management: BPC-controlled categories
  • Master Data Planning: Update dimension properties
  • Data Locking: BPC locks integration
  • 数据录入:直接向BPC模型输入数据
  • 规划序列:从SAC执行FOX脚本
  • 版本管理:由BPC控制的类别
  • 主数据规划:更新维度属性
  • 数据锁定:集成BPC锁定

Running BPC Planning Sequences

运行BPC规划序列

javascript
// Execute BPC planning sequence
PlanningSequence_1.setParameterValue("FISCAL_YEAR", "2025");
PlanningSequence_1.setParameterValue("VERSION", "PLAN");
PlanningSequence_1.execute().then(function() {
    Table_1.getDataSource().refreshData();
});
javascript
// 执行BPC规划序列
PlanningSequence_1.setParameterValue("FISCAL_YEAR", "2025");
PlanningSequence_1.setParameterValue("VERSION", "PLAN");
PlanningSequence_1.execute().then(function() {
    Table_1.getDataSource().refreshData();
});

When to Use BPC Live vs Native SAC

何时使用BPC实时连接 vs 原生SAC

Use BPC Live when: Existing BPC investment, complex FOX scripts, integrated with BW reporting Use Native SAC when: New implementation, simpler requirements, mobile-first applications
Reference: See
references/bpc-live-connection.md
for setup, prerequisites, and troubleshooting.

使用BPC实时连接的场景:已有BPC投资、复杂FOX脚本、与BW报表集成 使用原生SAC的场景:新实现、需求简单、移动优先应用
参考:设置、前提条件及故障排除请参见
references/bpc-live-connection.md

Value Driver Trees

价值驱动树

Value Driver Trees (VDT) visualize how values flow through a planning model, enabling driver-based planning and what-if analysis.
价值驱动树(VDT)可视化值在规划模型中的流动,支持基于驱动因素的规划和假设分析。

Use Cases

使用场景

ScenarioExample
Driver-Based PlanningModel how prices, headcount impact revenue
What-If AnalysisSimulate scenarios, see cascading effects
Strategic PlanningVisualize value chain impacts
Executive PresentationsTouchscreen-friendly boardroom displays
场景示例
基于驱动因素的规划建模价格、员工人数如何影响收入
假设分析模拟场景,查看连锁效应
战略规划可视化价值链影响
高管演示适合触摸屏的会议室展示

Creating a Value Driver Tree

创建价值驱动树

  1. Add Value Driver Tree widget to story or application
  2. Select planning model with Date dimension
  3. Add nodes (auto-create from model or manual)
  4. Configure measures and structures per node
  5. Link nodes (drivers right, outcomes left)
  6. Set presentation date range
  1. 向故事或应用中添加价值驱动树组件
  2. 选择带有日期维度的规划模型
  3. 添加节点(从模型自动创建或手动创建)
  4. 为每个节点配置度量和结构
  5. 链接节点(驱动因素在右侧,结果在左侧)
  6. 设置展示日期范围

Node Configuration

节点配置

SetupDescription
1 Account + 1 StructureSingle row of values
Multiple AccountsRow per account (e.g., sales + quantity)
Multiple StructuresCompare scenarios/currencies
设置描述
1个科目 + 1个结构单行值
多个科目每个科目一行(例如:销售额 + 数量)
多个结构比较场景/货币

JavaScript API

JavaScript API

javascript
// Get VDT reference
var vdt = ValueDriverTree_1;

// Get selected node value
var value = vdt.getSelectedNode().getValue("Revenue", "2025Q1");

// Collapse/expand nodes
vdt.collapseNode("Node_Revenue");
vdt.expandNode("Node_Revenue");
Reference: See
references/value-driver-trees.md
for detailed setup and best practices.

javascript
// 获取VDT引用
var vdt = ValueDriverTree_1;

// 获取选中节点的值
var value = vdt.getSelectedNode().getValue("Revenue", "2025Q1");

// 折叠/展开节点
vdt.collapseNode("Node_Revenue");
vdt.expandNode("Node_Revenue");
参考:详细设置及最佳实践请参见
references/value-driver-trees.md

Data Action Tracing

数据操作追踪

Data Action Tracing is a debugging tool for inspecting intermediate results during data action execution.
数据操作追踪是用于在数据操作执行期间检查中间结果的调试工具。

When to Use Tracing

何时使用追踪

ScenarioHow Tracing Helps
New DevelopmentValidate each step produces expected results
Debugging FailuresIdentify which step causes incorrect data
Performance InvestigationSee which steps process most data
Allocation DebuggingValidate driver ratios and distributions
场景追踪的作用
新开发验证每个步骤产生预期结果
故障排查识别导致数据错误的步骤
性能调查查看哪些步骤处理的数据最多
分配调试验证驱动比率和分配情况

Adding Tracepoints

添加追踪点

  1. Open data action in Data Action Designer
  2. Navigate to step where you want to trace
  3. Click Add Tracepoint (or right-click → Add Tracepoint)
  4. Name descriptively (e.g., "After Copy Step", "Before Allocation")
  1. 数据操作设计器中打开数据操作
  2. 导航至要追踪的步骤
  3. 点击添加追踪点(或右键 → 添加追踪点)
  4. 命名描述性名称(例如:"复制步骤后"、"分配前")

Running Trace Mode

运行追踪模式

  1. Open data action in designer
  2. Click Run with Tracing
  3. Set required parameters
  4. Execute - data captured at each tracepoint
  5. Review results in Tracing Results Panel
  1. 在设计器中打开数据操作
  2. 点击带追踪运行
  3. 设置所需参数
  4. 执行 - 在每个追踪点捕获数据
  5. 追踪结果面板中查看结果

Analyzing Results

分析结果

ViewDescription
Data at TracepointAll values at that point
Changes Since PreviousDelta between tracepoints
Filtered ViewFocus on specific data
视图描述
追踪点处的数据该点的所有值
与上一追踪点的变化追踪点之间的增量
筛选视图聚焦特定数据

TRACE() in Advanced Formulas

高级公式中的TRACE()

// Add tracepoints in script
[Revenue] = [Quantity] * [Price]
TRACE("After_Revenue_Calc")

[Final] = [Revenue] * (1 + [Tax])
TRACE("After_Tax")
Reference: See
references/data-action-tracing.md
for complete debugging guide.

// 在脚本中添加追踪点
[Revenue] = [Quantity] * [Price]
TRACE("After_Revenue_Calc")

[Final] = [Revenue] * (1 + [Tax])
TRACE("After_Tax")
参考:完整调试指南请参见
references/data-action-tracing.md

Planning Workflows (Calendar)

规划工作流(日历)

The SAP Analytics Cloud calendar organizes collaborative planning processes.
SAP Analytics Cloud日历用于组织协作式规划流程。

Task Types

任务类型

General Task: Data entry by assignees
  • Attach work file (story/application)
  • Set due dates and notifications
  • Track completion status
Review Task: Approval workflow
  • Review results of general tasks
  • Approve or reject submissions
  • Automatic notification on status change
Composite Task: Combined entry and review
  • Simplified approval for single-level workflows
  • Driving dimension support for regional planning
Data Locking Task: Schedule lock changes
  • Specify data slice to lock/unlock
  • Set target lock state
  • Event-based triggering
常规任务:由经办人进行数据录入
  • 附加工作文件(故事/应用)
  • 设置截止日期和通知
  • 跟踪完成状态
审核任务:审批工作流
  • 审核常规任务的结果
  • 批准或拒绝提交
  • 状态变更时自动通知
复合任务:结合录入和审核
  • 单级工作流的简化审批
  • 支持驱动维度用于区域规划
数据锁定任务:调度锁定变更
  • 指定要锁定/解锁的数据切片
  • 设置目标锁定状态
  • 基于事件触发

Multi-Level Approval

多级审批

Round 1: Regional Managers review regional plans
    ↓ (on approval)
Round 2: Finance Director reviews consolidated plan
    ↓ (on approval)
Round 3: CFO final approval
    ↓ (on approval)
Data Locking: Lock approved plan data
第一轮:区域经理审核区域计划
    ↓(批准后)
第二轮:财务总监审核合并计划
    ↓(批准后)
第三轮:CFO最终批准
    ↓(批准后)
数据锁定:锁定已批准的计划数据

Task Dependencies

任务依赖关系

Configure predecessor tasks to create sequential workflows:
  • Review tasks automatically start when predecessor completes
  • Data locking tasks trigger on approval events
Reference: See
references/planning-workflows.md
for calendar configuration.

配置前置任务以创建顺序工作流:
  • 审核任务在前置任务完成后自动启动
  • 数据锁定任务在批准事件触发时执行
参考:日历配置请参见
references/planning-workflows.md

Spreading & Distribution

分摊与分配

Spreading (Vertical)

分摊(纵向)

Distributes values from parent to child members:
  • Equal Spread: Divide equally among children
  • Proportional Spread: Maintain existing ratios
  • Automatic: SAC determines best method
javascript
// Spreading happens automatically when entering at aggregate level
// Example: Enter 1000 at "Total Regions" spreads to child regions
将值从父成员分配至子成员:
  • 均等分摊:在子成员间平均分配
  • 比例分摊:保持现有比率
  • 自动:SAC确定最佳方法
javascript
// 在聚合级别输入值时自动进行分摊
// 示例:在"总区域"输入1000,会分摊至子区域

Distribution (Horizontal)

分配(横向)

Moves values between members at same hierarchy level:
  • Select source and target cells
  • Choose distribution method
  • Apply via context menu or script
在同一层级的成员间移动值:
  • 选择源单元格和目标单元格
  • 选择分配方法
  • 通过上下文菜单或脚本应用

Allocation by Rules

基于规则的分配

Configure structured allocations in data actions:
  • Define driver accounts for percentage distribution
  • Set allocation targets
  • Execute via data action or multi action

在数据操作中配置结构化分配:
  • 定义用于百分比分配的驱动科目
  • 设置分配目标
  • 通过数据操作或多操作执行

Data Locking

数据锁定

Protect planning data during and after planning cycles.
在规划周期期间和之后保护规划数据。

Lock States

锁定状态

StateData EntryOwner Can Edit
OpenYesYes
RestrictedNo (except owner)Yes
LockedNoNo
MixedVariesVaries (selection contains multiple states)
状态数据录入所有者可编辑
开放
受限否(所有者除外)
锁定
混合因情况而异因情况而异(选择包含多种状态)

Configuration

配置

  1. Enable Data Locking on planning model
  2. Define Driving Dimensions (e.g., Region, Version)
  3. Assign Owners to data slices
  4. Configure Lock Regions via model settings
  1. 在规划模型上启用数据锁定
  2. 定义驱动维度(例如:区域、版本)
  3. 为数据切片分配所有者
  4. 通过模型设置配置锁定区域

Script Example

脚本示例

javascript
// Get data locking object
var dataLocking = Table_1.getPlanning().getDataLocking();

// Get lock state for selection
var selection = Table_1.getSelections()[0];
var lockState = dataLocking.getState(selection);

// Check if locked
if (lockState === DataLockingState.Locked) {
    Application.showMessage("This data is locked.");
}
Reference: See
references/planning-workflows.md
for data locking patterns.

javascript
// 获取数据锁定对象
var dataLocking = Table_1.getPlanning().getDataLocking();

// 获取所选内容的锁定状态
var selection = Table_1.getSelections()[0];
var lockState = dataLocking.getState(selection);

// 检查是否锁定
if (lockState === DataLockingState.Locked) {
    Application.showMessage("此数据已锁定。");
}
参考:数据锁定模式请参见
references/planning-workflows.md

Members on the Fly

动态成员

Create, update, and delete dimension members dynamically at runtime.
在运行时动态创建、更新和删除维度成员。

Supported Operations

支持的操作

javascript
// Create new member
PlanningModel_1.createMembers("CostCenter", {
    id: "CC_NEW",
    description: "New Cost Center"
});

// Update existing member
PlanningModel_1.updateMembers("CostCenter", {
    id: "CC_NEW",
    description: "Updated Description"
});

// Get single member
var member = PlanningModel_1.getMember("CostCenter", "CC_NEW");

// Get members with pagination
var members = PlanningModel_1.getMembers("CostCenter", {
    offset: "0",
    limit: "100"
});
javascript
// 创建新成员
PlanningModel_1.createMembers("CostCenter", {
    id: "CC_NEW",
    description: "New Cost Center"
});

// 更新现有成员
PlanningModel_1.updateMembers("CostCenter", {
    id: "CC_NEW",
    description: "Updated Description"
});

// 获取单个成员
var member = PlanningModel_1.getMember("CostCenter", "CC_NEW");

// 分页获取成员
var members = PlanningModel_1.getMembers("CostCenter", {
    offset: "0",
    limit: "100"
});

Important Restrictions

重要限制

  • Dimension Type: Only "Generic" dimensions supported (NOT Account, Version, Time, Organization)
  • Refresh Required: Call
    Application.refreshData()
    after member changes
  • Custom Properties: Use prefixes to avoid naming conflicts (e.g., "CUSTOM_Region")
Reference: See
references/analytics-designer-planning.md
for complete API documentation.

  • 维度类型:仅支持"通用"维度(不支持科目、版本、时间、组织)
  • 需要刷新:成员变更后调用
    Application.refreshData()
  • 自定义属性:使用前缀避免命名冲突(例如:"CUSTOM_Region")
参考:完整API文档请参见
references/analytics-designer-planning.md

Common JavaScript Patterns

常见JavaScript模式

Finding Active Version by Attribute

根据属性查找活动版本

javascript
var allVersions = PlanningModel_1.getMembers("Version");
var activeVersion = "";

for (var i = 0; i < allVersions.length; i++) {
    if (allVersions[i].properties.Active === "X") {
        activeVersion = allVersions[i].id;
        break;
    }
}
console.log("Active Version: " + activeVersion);
javascript
var allVersions = PlanningModel_1.getMembers("Version");
var activeVersion = "";

for (var i = 0; i < allVersions.length; i++) {
    if (allVersions[i].properties.Active === "X") {
        activeVersion = allVersions[i].id;
        break;
    }
}
console.log("Active Version: " + activeVersion);

Setting Filter from Planning Cycle

根据规划周期设置过滤器

javascript
Application.showBusyIndicator();
Table_1.setVisible(false);

// Find active planning cycle
var cycles = PlanningModel_1.getMembers("PlanningCycle");
var activeCycle = "";

for (var i = 0; i < cycles.length; i++) {
    if (cycles[i].properties.Flag === "ACTIVE") {
        activeCycle = cycles[i].id;
        break;
    }
}

// Apply MDX filter
Table_1.getDataSource().setDimensionFilter("Date",
    "[Date].[YQM].&[" + activeCycle + "]");

Table_1.setVisible(true);
Application.hideBusyIndicator();
javascript
Application.showBusyIndicator();
Table_1.setVisible(false);

// 查找活动规划周期
var cycles = PlanningModel_1.getMembers("PlanningCycle");
var activeCycle = "";

for (var i = 0; i < cycles.length; i++) {
    if (cycles[i].properties.Flag === "ACTIVE") {
        activeCycle = cycles[i].id;
        break;
    }
}

// 应用MDX过滤器
Table_1.getDataSource().setDimensionFilter("Date",
    "[Date].[YQM].&[" + activeCycle + "]");

Table_1.setVisible(true);
Application.hideBusyIndicator();

Version Publishing

版本发布

javascript
// Get forecast version
var forecastVersion = Table_1.getPlanning().getPublicVersion("Forecast2025");

// Check if changes need publishing
if (forecastVersion.isDirty()) {
    forecastVersion.publish();
    Application.showMessage("Version published successfully.");
}
javascript
// 获取预测版本
var forecastVersion = Table_1.getPlanning().getPublicVersion("Forecast2025");

// 检查是否需要发布变更
if (forecastVersion.isDirty()) {
    forecastVersion.publish();
    Application.showMessage("版本发布成功。");
}

Data Action Execution

数据操作执行

javascript
// Execute data action with parameters
DataAction_1.setParameterValue("Version", "Budget");
DataAction_1.setParameterValue("Year", "2025");

DataAction_1.execute();

// Or execute in background
DataAction_1.executeInBackground();
Reference: See
references/javascript-patterns.md
for more examples.

javascript
// 带参数执行数据操作
DataAction_1.setParameterValue("Version", "Budget");
DataAction_1.setParameterValue("Year", "2025");

DataAction_1.execute();

// 或在后台执行
DataAction_1.executeInBackground();
参考:更多示例请参见
references/javascript-patterns.md

Performance Best Practices

性能最佳实践

Data Action Optimization

数据操作优化

  1. Use Input Controls: Link to parameters to reduce data scope
  2. Embed Related Actions: Combine actions on same model/version
  3. Minimize Cross-Model Operations: Keep data in single model when possible
  4. Use Batch Processing: Group operations in single transaction
  1. 使用输入控件:关联至参数以减少数据范围
  2. 嵌入相关操作:合并同一模型/版本上的操作
  3. 最小化跨模型操作:尽可能将数据保留在单个模型中
  4. 使用批处理:将操作分组为单个事务

Story Performance

故事性能

  1. Enable Data Locking Selectively: Only on models that need it
  2. Use Growing Mode: For large tables with pagination
  3. Limit Visible Dimensions: Reduce data cells displayed
  4. Optimize Filters: Apply story filters before data entry
  1. 选择性启用数据锁定:仅在需要的模型上启用
  2. 使用增长模式:用于带分页的大型表格
  3. 限制可见维度:减少显示的数据单元格数量
  4. 优化过滤器:在数据录入前应用故事过滤器

API Performance

API性能

  1. Use Booked Values Filter: Retrieve only posted data
  2. Limit getMembers() Results: Set limit parameter
  3. Cache Member Lists: Store in script variables when reusing
  4. Use Busy Indicator: Improve perceived performance

  1. 使用已记账值过滤器:仅检索已过账的数据
  2. 限制getMembers()结果:设置limit参数
  3. 缓存成员列表:重复使用时存储在脚本变量中
  4. 使用忙碌指示器:提升感知性能

Troubleshooting

故障排除

Issue: Data not saving

问题:数据未保存

Check:
  1. Planning enabled on table?
  2. User has planning permissions?
  3. Data locked?
  4. Validation rules failing?
Debug:
javascript
console.log("Planning enabled: " + Table_1.getPlanning().isEnabled());
var lockState = Table_1.getPlanning().getDataLocking().getState(selection);
console.log("Lock state: " + lockState);
检查项
  1. 表格是否启用了规划?
  2. 用户是否拥有规划权限?
  3. 数据是否被锁定?
  4. 验证规则是否失败?
调试
javascript
console.log("Planning enabled: " + Table_1.getPlanning().isEnabled());
var lockState = Table_1.getPlanning().getDataLocking().getState(selection);
console.log("Lock state: " + lockState);

Issue: Version not publishing

问题:版本无法发布

Check:
  1. Valid changes only? (Invalid changes discarded)
  2. Data access control allowing write?
  3. Version not already published?
检查项
  1. 是否仅包含有效变更?(无效变更会被丢弃)
  2. 数据访问控制是否允许写入?
  3. 版本是否已发布?

Issue: Data action failing

问题:数据操作执行失败

Check:
  1. Source data exists?
  2. Target version writable?
  3. Dimension mappings correct?
  4. Parameters set correctly?
Debug: Use data action tracing table with "Show Only Leaves" option.
检查项
  1. 源数据是否存在?
  2. 目标版本是否可写?
  3. 维度映射是否正确?
  4. 参数是否设置正确?
调试:使用数据操作追踪表并选择"仅显示叶子节点"选项。

Issue: getMembers() returns empty

问题:getMembers()返回空值

Check:
  1. Dimension name correct?
  2. Model connected?
  3. User has read access?
  4. Using correct API (PlanningModel vs DataSource)?

检查项
  1. 维度名称是否正确?
  2. 模型是否已连接?
  3. 用户是否拥有读取权限?
  4. 是否使用了正确的API(PlanningModel vs DataSource)?

Official Documentation Links

官方文档链接

Essential Resources:
Planning Model & Data:
Data Actions & Multi Actions:
Version Management:
Data Locking:
Calendar & Workflows:
Allocations & Spreading:
Learning Resources:

核心资源
规划模型与数据
数据操作与多操作
版本管理
数据锁定
日历与工作流
分配与分摊
学习资源

Bundled Reference Files

捆绑参考文件

This skill includes comprehensive reference documentation (26 files):
API & Scripting:
  1. references/api-reference.md: Complete Analytics Designer API for planning
  2. references/analytics-designer-planning.md: Planning scripting, setUserInput, versions, data locking, members on the fly
  3. references/api-snippets.md: Quick API code examples and snippets
Core Planning Features: 4. references/data-actions.md: Data Actions, Multi Actions, parameters, steps 5. references/multi-actions.md: Orchestrate multiple planning operations 6. references/allocations.md: Rule-based distribution and allocations 7. references/advanced-formulas.md: Complex calculations and formulas 8. references/predictive-conversion.md: Predictive forecasting integration
Workflow & Collaboration: 9. references/planning-workflows.md: Calendar, tasks, approvals, data locking 10. references/scheduling-calendar.md: Planning calendar setup 11. references/input-tasks.md: Collaborative data entry tasks 12. references/job-monitoring.md: Track data action execution
Version Management: 13. references/version-management.md: Versions, publishing, sharing, edit mode 14. references/version-edit-modes.md: Version editing workflows 15. references/version-publishing-notes.md: Publishing best practices
Integration & Advanced: 16. references/s4hana-acdocp-export.md: Legacy/deprecated S/4HANA ACDOCP export reference for existing landscapes 17. references/ai-planning-analytics.md: AI-powered planning features
Development: 18. references/javascript-patterns.md: Code snippets, patterns, best practices 19. references/modeling-basics.md: Planning model fundamentals 20. references/data-locking.md: Configure and manage data locks 21. references/edge-cdp-control.md: SAC planning browser add-on for the shared
sap-browser-automation
authentication, Edge/CDP, and recovery layer
New in 2025: 22. references/seamless-planning-datasphere.md: Seamless Planning architecture, prerequisites, configuration with SAP Datasphere 23. references/bpc-live-connection.md: BPC Embedded live connection, planning sequences, master data planning 24. references/value-driver-trees.md: Value driver tree setup, node configuration, JavaScript API 25. references/data-action-tracing.md: Data action tracing, tracepoints, debugging techniques
New in 2026: 26. references/whats-new-2026-planning.md: QRC1 and QRC2 2026 planning features, asymmetric reporting, composite versioning, AI-assisted data actions, API enhancements

本技能包含全面的参考文档(26个文件):
API与脚本
  1. references/api-reference.md:用于规划的完整Analytics Designer API
  2. references/analytics-designer-planning.md:规划脚本、setUserInput、版本、数据锁定、动态成员
  3. references/api-snippets.md:快速API代码示例和片段
核心规划功能: 4. references/data-actions.md:数据操作、多操作、参数、步骤 5. references/multi-actions.md:编排多个规划操作 6. references/allocations.md:基于规则的分配和分摊 7. references/advanced-formulas.md:复杂计算和公式 8. references/predictive-conversion.md:预测集成
工作流与协作: 9. references/planning-workflows.md:日历、任务、审批、数据锁定 10. references/scheduling-calendar.md:规划日历设置 11. references/input-tasks.md:协作式数据录入任务 12. references/job-monitoring.md:追踪数据操作执行
版本管理: 13. references/version-management.md:版本、发布、共享、编辑模式 14. references/version-edit-modes.md:版本编辑工作流 15. references/version-publishing-notes.md:发布最佳实践
集成与高级功能: 16. references/s4hana-acdocp-export.md:用于现有环境的旧版/已弃用S/4HANA ACDOCP导出参考 17. references/ai-planning-analytics.md:AI驱动的规划功能
开发: 18. references/javascript-patterns.md:代码片段、模式、最佳实践 19. references/modeling-basics.md:规划模型基础 20. references/data-locking.md:配置和管理数据锁定 21. references/edge-cdp-control.md:用于共享
sap-browser-automation
认证、Edge/CDP及恢复层的SAC规划浏览器附加组件
2025年新增: 22. references/seamless-planning-datasphere.md:与SAP Datasphere的无缝规划架构、前提条件、配置 23. references/bpc-live-connection.md:BPC Embedded实时连接、规划序列、主数据规划 24. references/value-driver-trees.md:价值驱动树设置、节点配置、JavaScript API 25. references/data-action-tracing.md:数据操作追踪、追踪点、调试技术
2026年新增: 26. references/whats-new-2026-planning.md:2026年QRC1和QRC2规划功能、非对称报表、复合版本管理、AI辅助数据操作、API增强

Instructions for Claude

给Claude的说明

When using this skill:
  1. Check model type first - Ensure planning model (not analytic) for write operations
  2. Verify planning enabled - Table must have planning enabled
  3. Use appropriate API - PlanningModel for master data, getPlanning() for transactions
  4. Handle versions correctly - Private for drafts, publish to public when ready
  5. Respect data locking - Check lock state before suggesting edits
  6. Use busy indicators - For long operations to improve UX
  7. Follow MDX syntax - For dimension filters:
    [Dim].[Hierarchy].&[Member]
  8. Test data actions - Use tracing before production deployment
  9. Consider performance - Apply filters to reduce data scope
  10. Link to documentation - Include relevant SAP Help links in responses
For troubleshooting:
  • Check console for script errors
  • Verify model connectivity
  • Review data action logs
  • Test with simplified scenarios first
  • Check user permissions and data access
使用本技能时:
  1. 首先检查模型类型 - 确保是规划模型(而非分析模型)以进行写入操作
  2. 验证是否启用规划 - 表格必须启用规划
  3. 使用合适的API - 主数据使用PlanningModel,事务使用getPlanning()
  4. 正确处理版本 - 草稿使用私有版本,完成后发布至公共版本
  5. 遵守数据锁定规则 - 在建议编辑前检查锁定状态
  6. 使用忙碌指示器 - 长操作时提升用户体验
  7. 遵循MDX语法 - 维度过滤器格式:
    [Dim].[Hierarchy].&[Member]
  8. 测试数据操作 - 生产部署前使用追踪功能
  9. 考虑性能 - 应用过滤器以减少数据范围
  10. 链接至文档 - 响应中包含相关SAP帮助链接
故障排查时:
  • 检查控制台的脚本错误
  • 验证模型连接性
  • 查看数据操作日志
  • 先使用简化场景测试
  • 检查用户权限和数据访问

What's New in 2026

2026年新功能

QRC1 2026 (2026.3)

2026年QRC1(2026.3)

  • AI-Assisted Data Actions: Generate advanced formula scripts from natural-language comments, or generate comments from existing scripts.
  • Live Data Connectivity to Snowflake: Planning-capable models can connect live to Snowflake.
  • Story Versioning: Up to 10 major versions of stories for safe iterative development.
  • AI辅助数据操作:从自然语言注释生成高级公式脚本,或从现有脚本生成注释。
  • Snowflake实时数据连接:支持规划的模型可实时连接至Snowflake。
  • 故事版本控制:最多保留10个主要故事版本,支持安全的迭代开发。

QRC2 2026 (2026.8)

2026年QRC2(2026.8)

  • Asymmetric Reporting: Tables with differing time ranges, hierarchies, and measures per row/column. Supports planning data entry.
  • Composite Versioning: Manage up to 10 versions of composites with rollback support.
  • Data Export API in Job Monitor: Track data extraction and delta calculation jobs.
  • Data Import Service API Enhancements: Import master data into Datasphere public dimensions; import external fact data to seamless planning private versions.
  • onAfterExecute Event Enhancement: Additional upload info (message, statistics, rejected records, target version, file name).
  • Multi-Action API Step: HTTP 204 Response: Accepted as success response.
  • Calendar: Team References Retained: Teams auto-sync on event activation.
  • Mixing Advanced Filters in Just Ask: Exclude date members with date range filters.
  • Deprecation: Export Model Data to S/4HANA: Use write-back integration instead.
Reference: See
references/whats-new-2026-planning.md
for detailed descriptions, usage instructions, and source citations.

  • 非对称报表:表格的行/列可使用不同的时间范围、层次结构和度量,支持规划数据录入。
  • 复合版本管理:管理最多10个复合版本,支持回滚。
  • 作业监控器中的数据导出API:追踪数据提取和增量计算作业。
  • 数据导入服务API增强:将主数据导入Datasphere公共维度;将外部事实数据导入无缝规划私有版本。
  • onAfterExecute事件增强:提供额外上传信息(消息、统计数据、拒绝记录、目标版本、文件名)。
  • 多操作API步骤:HTTP 204响应:被接受为成功响应。
  • 日历:保留团队引用:事件激活时团队自动同步。
  • Just Ask中混合高级过滤器:使用日期范围过滤器排除日期成员。
  • 弃用:将模型数据导出至S/4HANA:改用回写集成。
参考:详细描述、使用说明及来源引用请参见
references/whats-new-2026-planning.md

Bundled Resources

捆绑资源

Reference Documentation

参考文档

  • references/data-actions.md
    - Data actions configuration and execution
  • references/multi-actions.md
    - Multi-action orchestration
  • references/allocations.md
    - Allocation methods and spreading
  • references/scheduling-calendar.md
    - Workflow scheduling
  • references/data-locking.md
    - Data locking configuration
  • references/version-management.md
    - Version management best practices
  • references/api-reference.md
    - Planning API reference
  • references/javascript-patterns.md
    - JavaScript scripting patterns
  • references/edge-cdp-control.md
    - Planning-specific add-on for the shared
    sap-browser-automation
    Edge/CDP and authentication layer
  • references/data-actions.md
    - 数据操作配置与执行
  • references/multi-actions.md
    - 多操作编排
  • references/allocations.md
    - 分配方法与分摊
  • references/scheduling-calendar.md
    - 工作流调度
  • references/data-locking.md
    - 数据锁定配置
  • references/version-management.md
    - 版本管理最佳实践
  • references/api-reference.md
    - 规划API参考
  • references/javascript-patterns.md
    - JavaScript脚本模式
  • references/edge-cdp-control.md
    - 用于共享
    sap-browser-automation
    Edge/CDP及认证层的规划特定附加组件

Templates

模板

  • templates/data-action-checklist.md
    - Data action implementation checklist
  • templates/multi-action-checklist.md
    - Multi-action setup guide
  • templates/parameter-table.md
    - Parameter table template

License: GPL-3.0 Version: 1.5.0 Maintained by: Eduard Jiglau Email: hello@sap-ai-skills.com Website: https://sap-ai-skills.com Repository: https://github.com/secondsky/sap-skills
  • templates/data-action-checklist.md
    - 数据操作实施检查清单
  • templates/multi-action-checklist.md
    - 多操作设置指南
  • templates/parameter-table.md
    - 参数表格模板

许可证:GPL-3.0 版本:1.5.0 维护者:Eduard Jiglau 邮箱hello@sap-ai-skills.com 网站https://sap-ai-skills.com 仓库https://github.com/secondsky/sap-skills