secondsky/sap-sac-planning
| SAP Analytics Cloud (SAC) planning guidance for planning models, planning-enabled stories, data actions, multi actions, version management, data locking, calendar/input workflows, allocations, value driver trees, BPC live planning, and Seamless Planning with SAP Datasphere. Use this for planning design, planning APIs, data action debugging, planning performance reviews, and authenticated SAC planning story triage in Microsoft Edge via CDP; use sap-sac-scripting for non-planning SAC scripts and sap-datasphere for Datasphere modeling.
npx skills add https://github.com/secondsky/sap-skills --skill sap-sac-planningComprehensive skill for building enterprise planning applications with SAP Analytics Cloud.
references/data-actions.md, references/multi-actions.md, references/allocations.md, references/scheduling-calendar.md, references/data-locking.mdreferences/modeling-basics.md, references/version-management.md, references/version-edit-modes.md, references/version-publishing-notes.mdreferences/advanced-formulas.md, references/predictive-conversion.md, references/ai-planning-analytics.md, references/api-snippets.mdreferences/input-tasks.md, references/job-monitoring.mdsap-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 safetyreferences/seamless-planning-datasphere.md, references/bpc-live-connection.md, references/value-driver-trees.md, references/data-action-tracing.mdreferences/whats-new-2026-planning.mdtemplates/data-action-checklist.md, templates/multi-action-checklist.md, templates/parameter-table.mdUse 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.
Use this skill when working on tasks involving:
Planning Application Development:
Data Actions & Multi Actions:
Version Management:
Planning Workflows:
JavaScript Planning APIs:
Data Entry & Allocation:
Data Locking:
Seamless Planning with Datasphere (2025):
BPC Live Connection:
Value Driver Trees:
Data Action Debugging:
Planning Model:
Analytic Model:
Public Versions:
Private Versions:
Edit Mode:
Reference: See references/version-management.md for detailed workflows.
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 perform calculations and data manipulation on planning models.
| Step Type | Purpose |
|-----------|---------|
| Copy | Move data between dimensions/versions |
| Advanced Formula | Complex calculations |
| Allocation | Rule-based distribution |
| Currency Conversion | Convert currencies |
| Embedded Data Action | Run another data action |
Source:
Version = Actual
Year = 2024
Target:
Version = Budget
Year = 2025
Mapping:
Account = Account (same)
CostCenter = CostCenter (same)
// Calculate forecast = Actual + (Budget - Actual) * 0.5
[Version].[Forecast] = [Version].[Actual] +
([Version].[Budget] - [Version].[Actual]) * 0.5
Add parameters to make data actions reusable:
Reference: See references/data-actions.md for complete configuration guide.
Multi actions orchestrate multiple planning operations across models and versions.
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)
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.
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 Planning Model → Data Export Service → Cloud Connector → API_PLPACDOCPDATA_SRV → ACDOCP
| Requirement | Details |
|-------------|---------|
| Legacy Mode | Must be enabled on planning model |
| OData Service | Activate API_PLPACDOCPDATA_SRV in /IWFND/MAINT_SERVICE |
| Cloud Connector | Required for on-premise S/4HANA |
Do not create this path for new implementations without confirming the
deprecation impact, SAP Note 3707288 guidance, and a supported migration path.
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 unifies SAC planning with SAP Datasphere, enabling enterprise-grade storage and governance for plan data.
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
| Benefit | Description |
|---------|-------------|
| Unified Data | Centralized storage ensures consistency |
| Direct Persistence | Changes in SAC instantly reflect in Datasphere |
| Optimized Resources | Reduces SAC memory and storage footprint |
| Enterprise Reusability | Datasphere modeling extends to planning data |
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.
SAC supports live data connections to BPC Embedded on S/4HANA, enabling planning with the BPC engine while using SAC's modern interface.
| Version | Planning Support |
|---------|------------------|
| BPC Embedded (S/4HANA) | Full planning features |
| BPC for NetWeaver | Limited (read-only) |
| BPC Standard | Export to BPC required |
// Execute BPC planning sequence
PlanningSequence_1.setParameterValue("FISCAL_YEAR", "2025");
PlanningSequence_1.setParameterValue("VERSION", "PLAN");
PlanningSequence_1.execute().then(function() {
Table_1.getDataSource().refreshData();
});
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 (VDT) visualize how values flow through a planning model, enabling driver-based planning and what-if analysis.
| Scenario | Example |
|----------|---------|
| Driver-Based Planning | Model how prices, headcount impact revenue |
| What-If Analysis | Simulate scenarios, see cascading effects |
| Strategic Planning | Visualize value chain impacts |
| Executive Presentations | Touchscreen-friendly boardroom displays |
| Setup | Description |
|-------|-------------|
| 1 Account + 1 Structure | Single row of values |
| Multiple Accounts | Row per account (e.g., sales + quantity) |
| Multiple Structures | Compare scenarios/currencies |
// 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 is a debugging tool for inspecting intermediate results during data action execution.
| Scenario | How Tracing Helps |
|----------|-------------------|
| New Development | Validate each step produces expected results |
| Debugging Failures | Identify which step causes incorrect data |
| Performance Investigation | See which steps process most data |
| Allocation Debugging | Validate driver ratios and distributions |
| View | Description |
|------|-------------|
| Data at Tracepoint | All values at that point |
| Changes Since Previous | Delta between tracepoints |
| Filtered View | Focus on specific data |
// 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.
The SAP Analytics Cloud calendar organizes collaborative planning processes.
General Task: Data entry by assignees
Review Task: Approval workflow
Composite Task: Combined entry and review
Data Locking Task: Schedule lock changes
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
Configure predecessor tasks to create sequential workflows:
Reference: See references/planning-workflows.md for calendar configuration.
Distributes values from parent to child members:
// Spreading happens automatically when entering at aggregate level
// Example: Enter 1000 at "Total Regions" spreads to child regions
Moves values between members at same hierarchy level:
Configure structured allocations in data actions:
Protect planning data during and after planning cycles.
| State | Data Entry | Owner Can Edit |
|-------|------------|----------------|
| Open | Yes | Yes |
| Restricted | No (except owner) | Yes |
| Locked | No | No |
| Mixed | Varies | Varies (selection contains multiple states) |
// 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.
Create, update, and delete dimension members dynamically at runtime.
// 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"
});
Application.refreshData() after member changesReference: See references/analytics-designer-planning.md for complete API documentation.
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);
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();
// 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.");
}
// 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.
Check:
Debug:
console.log("Planning enabled: " + Table_1.getPlanning().isEnabled());
var lockState = Table_1.getPlanning().getDataLocking().getState(selection);
console.log("Lock state: " + lockState);
Check:
Check:
Debug: Use data action tracing table with "Show Only Leaves" option.
Check:
Essential Resources:
Planning Model & Data:
Data Actions & Multi Actions:
Version Management:
Data Locking:
Calendar & Workflows:
Allocations & Spreading:
Learning Resources:
This skill includes comprehensive reference documentation (26 files):
API & Scripting:
Core Planning Features:
Workflow & Collaboration:
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
When using this skill:
[Dim].[Hierarchy].&[Member]10. Link to documentation - Include relevant SAP Help links in responses
For troubleshooting:
Reference: See references/whats-new-2026-planning.md for detailed descriptions, usage instructions, and source citations.
references/data-actions.md - Data actions configuration and executionreferences/multi-actions.md - Multi-action orchestrationreferences/allocations.md - Allocation methods and spreadingreferences/scheduling-calendar.md - Workflow schedulingreferences/data-locking.md - Data locking configurationreferences/version-management.md - Version management best practicesreferences/api-reference.md - Planning API referencereferences/javascript-patterns.md - JavaScript scripting patternsreferences/edge-cdp-control.md - Planning-specific add-on for the shared sap-browser-automation Edge/CDP and authentication layertemplates/data-action-checklist.md - Data action implementation checklisttemplates/multi-action-checklist.md - Multi-action setup guidetemplates/parameter-table.md - Parameter table templateLicense: GPL-3.0
Version: 1.5.0
Maintained by: Eduard Jiglau
Email: [email protected]
Website: https://sap-ai-skills.com
Repository: https://github.com/secondsky/sap-skills
Take secondsky/sap-sac-planning from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.