secondsky/sap-skillsGPL-3.011 files

Sap Btp Best Practices

|

Specification
Skill ID
secondsky/sap-skills/sap-btp-best-practices
Publisher
secondsky
Repository
sap-skills
Installs
0
Files
11
License
GPL-3.0
Synced
Sep 23, 2026
How to use it

Open any RiverX project, open the Skills panel in the chat, and search for this identifier. The files are fetched from the source repository at install time.

secondsky/sap-skills/sap-btp-best-practicesInstalls these files
  • README.md
  • SKILL.md
  • agents/openai.yaml
  • references/account-models.md
  • references/ai-development-best-practices.md
  • references/deployment-and-delivery.md
  • references/failover-and-resilience.md
  • references/governance-and-teams.md
  • references/operations-and-monitoring.md
  • references/security-and-authentication.md
  • references/templates-and-examples.md

What this skill tells the agent

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.

Quick Start

  1. Identify the target account model: global account, directories, subaccounts, environments, and regions.
  2. Choose the runtime path: Cloud Foundry, Kyma, ABAP Environment, or a hybrid portfolio.
  3. Apply security defaults from Security and Authentication.
  4. Use the relevant implementation skill for detailed execution: sap-btp-cloud-platform, sap-btp-connectivity, sap-btp-service-manager, sap-cap-capire, or sap-fiori-tools.
  5. Record production-specific gaps in the project plan before changing last_verified.

Documentation-audited SAP BTP implementation guidance based on official SAP documentation. The last_verified date remains stale until the source refresh and any live account checks are completed.

Quick Links:


Table of Contents

  1. Platform Fundamentals
  2. Account Model Setup
  3. Security and Authentication
  4. Connectivity
  5. Governance and Teams
  6. Development
  7. AI Development
  8. Deployment and Delivery
  9. High Availability and Failover
  10. Operations and Monitoring
  11. Cost Management
  12. Bundled Resources

Platform Fundamentals

Account Hierarchy

Global Account (SAP contract)
├── Directory (optional, up to 7 levels)
│   └── Subaccount (region-specific, apps run here)
│       ├── Cloud Foundry Org → Spaces
│       └── Kyma Cluster → Namespaces
└── Subaccount

Key Points:

  • Global account = contract with SAP (one per commercial model)
  • Directory = groups subaccounts (max 7 levels deep)
  • Subaccount = deployed in specific region, enables runtimes
  • Use labels for virtual grouping (Dev/Test/Prod, cost centers)

Environments

EnvironmentUse CaseKey Features
Cloud FoundryPolyglot appsMultiple buildpacks, spaces
KymaCloud-native K8sOpen-source, namespaces
ABAPABAP extensionsRAP, cloud-ready ABAP
NeoLegacyMigrate away - HTML5, Java, HANA XS

Commercial Models

  • Consumption-Based (BTPEA/CPEA): Flexible access, best for pilots
  • Subscription-Based: Fixed-cost for known service needs

Best Practice: Start with consumption-based, move to subscription for stable workloads.


Account Model Setup

Simple Model (3 subaccounts)

Global Account
├── Dev Subaccount
├── Test Subaccount
└── Prod Subaccount

Best for: Initial implementations, single team, <3 projects

Directory Model (scalable)

Global Account
├── Directory: HR
│   ├── hr-dev / hr-test / hr-prod
├── Directory: Sales
│   ├── sales-dev / sales-test / sales-prod
└── Directory: Central IT
    ├── api-management
    └── shared-services

Best for: Multiple teams, cost allocation, complex governance

Naming Conventions

EntityConventionExample
SubaccountNatural language"HR Development"
SubdomainLowercase, hyphenshr-dev-acme
CF OrgCompany prefixacme-hr-dev
CF SpaceConsistent across stageshr-recruiting

Tip: Derive CF org/Kyma names from subaccount names for consistency.


Security and Authentication

Identity Provider Setup

Always use SAP Cloud Identity Services - Identity Authentication

Corporate IdP → Identity Authentication (proxy) → SAP BTP

Critical Steps:

  1. Add multiple administrators (different time zones)
  2. Enable MFA for all admins
  3. Configure security alerts
  4. Set up backup admins in SAP ID Service

Authorization Methods

MethodBest ForNotes
ProvisioningProduction, many usersCentralized roles, automated offboarding
FederationSimple scenariosReal-time sync, but doesn't scale well
ManualTesting onlyQuick setup, not production-ready

Destination Authentication

Recommended:

  • PrincipalPropagation - SAP on-premise systems
  • OAuth2SAMLBearerAssertion - Third-party systems
  • OAuth2JWTBearer - User token exchange

Avoid in Production:

  • BasicAuthentication
  • OAuth2Password

See: references/security-and-authentication.md for complete guidance


Connectivity

Remote System Access

  • Internet Services: Destinations with authentication
  • On-Premise Systems: Destinations + Cloud Connector

Cloud Connector

  • Lightweight on-premise agent
  • Secure tunnel to SAP BTP (no inbound ports)
  • Fine-grained access control
  • Supports RFC and HTTP protocols
  • Enables principal propagation

Note: Each subaccount needs separate Cloud Connector config.


Governance and Teams

Required Teams

Platform Engineering Team (Center of Excellence):

  • Manages cloud landscape infrastructure
  • Handles account operations, build infrastructure
  • Creates governance and compliance guidelines
  • Does NOT manage individual application lifecycles

Cloud Development Teams:

  • Follow DevOps (develop AND operate)
  • Responsible for application lifecycle
  • Regular maintenance (e.g., UI updates every 6 months)

Essential Documentation

  1. Onboarding Doc: Organization, app IDs, timeline, tech stack
  2. Security Doc: Data sensitivity, policies, auth framework
  3. Services Catalog: Templates for destinations, builds, schemas

Development

Programming Models

SAP CAP (Cloud Application Programming Model):

  • Framework with languages, libraries, tools
  • Supports Java, JavaScript, TypeScript
  • Enterprise-grade services and data models

ABAP Cloud:

  • Modern ABAP for cloud-ready apps
  • RAP (RESTful ABAP Programming Model)
  • Extensions for ABAP-based products

Development Lifecycle

  1. Explore: Business opportunity, team roles
  2. Discover: Use cases, technology options
  3. Design: UX design, domain-driven design
  4. Deliver: Landscape setup, development
  5. Run and Scale: Feedback, optimization

AI Development

SAP BTP provides AI capabilities through SAP AI Core for:

  • Generative AI (LLMs, RAG)
  • Narrow AI (classical ML)

Key Resources:

Best Practices:

Use this skill in a project

Open any RiverX project, search the Skills panel for secondsky/sap-skills/sap-btp-best-practices, and install it in one click.

Use this skill