Sap Sac Planning

SAP Analytics Cloud Planning Skill

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.

Reference Add-Ons (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.

Table of Contents

• When to Use This Skill
• Quick Start
• Core Concepts
• Data Actions
• Seamless Planning with Datasphere
• BPC Live Connection
• Value Driver Trees
• Data Action Tracing
• What's New in 2026
• Bundled Resources

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

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

Creating an Analytics Designer Planning Application

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

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.

Planning API Overview

getPlanning() API - Table planning operations:

// 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:

// 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:

// 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.

Data Actions

Data actions perform calculations and data manipulation on planning models.

Step Types

Creating a Copy Step

Source:
  Version = Actual
  Year = 2024

Target:
  Version = Budget
  Year = 2025

Mapping:
  Account = Account (same)
  CostCenter = CostCenter (same)

Advanced Formula Example

// Calculate forecast = Actual + (Budget - Actual) * 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.

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

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)

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.

S/4HANA ACDOCP Export

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.

Architecture

SAC Planning Model → Data Export Service → Cloud Connector → API_PLPACDOCPDATA_SRV → ACDOCP

Prerequisites

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

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

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.

Seamless Planning with Datasphere

Seamless Planning unifies SAC planning with SAP Datasphere, enabling enterprise-grade storage and governance for plan data.

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

Key Benefits

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

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

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.

BPC Live Connection

SAC supports live data connections to BPC Embedded on S/4HANA, enabling planning with the BPC engine while using SAC's modern interface.

Supported BPC Versions

Planning Features via BPC Live

• 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

Running BPC Planning Sequences

// Execute BPC planning sequence
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

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.

Value Driver Trees

Value Driver Trees (VDT) visualize how values flow through a planning model, enabling driver-based planning and what-if analysis.

Use Cases

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

Node Configuration

JavaScript API

// 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.

Data Action Tracing

Data Action Tracing is a debugging tool for inspecting intermediate results during data action execution.

When to Use Tracing

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")

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

Analyzing Results

TRACE() in Advanced Formulas

// 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.

Planning Workflows (Calendar)

The SAP Analytics Cloud calendar organizes collaborative planning processes.

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