Sap Btp Best Practices

This is your go-to reference when architecting or running SAP BTP at scale. It covers the fundamentals you need to get right early (account hierarchies, directory structures, naming conventions) and the production concerns that matter later (failover strategies, Platform Engineering team setup, governance models). The guidance is practical: use Identity Authentication as a proxy for corporate IdPs, avoid BasicAuth in destinations, structure your subaccounts by domain not just by environment. What stands out is the clear separation between infrastructure concerns (handled by Platform Engineering) and application lifecycle (owned by DevOps teams). If you're moving past proof-of-concept into multi-team BTP deployments, this consolidates the architectural decisions and operational patterns you'll need.

skills.sh installs: 1.1K
GitHub stars: 496
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add secondsky/sap-skills --skill sap-btp-best-practices --agent claude-code

Installs into .claude/skills of the current project.

Files

SAP BTP Best Practices

Related Skills

sap-btp-cloud-platform: Use for technical implementation details, CLI commands, and runtime configurations
sap-btp-connectivity: Use for connectivity patterns, destination configuration, and Cloud Connector setup
sap-btp-service-manager: Use for service lifecycle management and programmatic service operations
sap-btp-developer-guide: Use for development workflows, CAP integration, and application patterns
sap-cap-capire: Use when designing CAP applications on BTP or implementing multitenancy
sap-ai-core: Use for AI Core platform setup, model deployment, and orchestration configuration
sap-cloud-sdk-ai: Use for SDK-level AI integration in CAP or standalone BTP applications
sap-fiori-tools: Use for UI deployment strategies and frontend application guidelines

When to Use This Skill

Use this skill when designing a BTP account model, setting up governance, choosing commercial/environment patterns, establishing security and authentication defaults, designing CI/CD and operations practices, or reviewing a BTP landscape before implementation.