plugins/sap-btp-developer-guide/skills/sap-btp-developer-guide/SKILL.md
Develops business applications on SAP Business Technology Platform (BTP) using CAP (Node.js/Java) or ABAP Cloud. Use when: building cloud applications on SAP BTP, deploying to Cloud Foundry or Kyma runtimes, integrating with SAP HANA Cloud, implementing SAP Fiori UIs, connecting to remote SAP systems, building multitenant SaaS applications, extending SAP S/4HANA or SuccessFactors, setting up CI/CD pipelines, implementing observability, or following SAP development best practices. Keywords: SAP BTP, Business Technology Platform, CAP, Cloud Application Programming Model, ABAP Cloud, Cloud Foundry, Kyma, SAP HANA Cloud, SAP Fiori, SAPUI5, CI/CD, observability, multitenant, SaaS, SAP BTP ABAP environment, SAP Business Application Studio, SAP Cloud SDK, SAP Integration Suite, SAP Event Mesh, SAP Connectivity Service, SAP Destination Service, XSUAA, OAuth, OpenID Connect, OData, CDS, Core Data Services, ABAP CDS, ABAP RESTful Application Programming Model, RAP, ABAP development, SAP BTP development
npx skillsauth add secondsky/sap-skills sap-btp-developer-guideInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Comprehensive guidance for developing, deploying, and operating business applications on SAP Business Technology Platform.
Use when:
For detailed runtime comparison: See references/runtimes.md
| Criteria | CAP (Cloud Foundry/Kyma) | ABAP Cloud | |----------|--------------------------|------------| | Languages | Node.js, Java, TypeScript | ABAP | | Best For | New cloud-native apps, extensions | Organizations with ABAP expertise | | Runtime | Cloud Foundry or Kyma | SAP BTP ABAP Environment | | Persistence | SAP HANA Cloud, PostgreSQL | SAP HANA Cloud (ABAP-managed) | | UI Framework | SAP Fiori Elements, SAPUI5 | SAP Fiori Elements, SAPUI5 | | IDE | SAP Business Application Studio, VS Code | ABAP Development Tools (Eclipse) |
CAP provides three operational profiles:
Key capabilities:
For CAP details: See references/cap-development.md
Build intelligent side-by-side extensions by combining CAP with SAP AI Core:
aicore, plan: extended)@sap-ai-sdk/orchestration) in CAP event handlers — never raw HTTP calls202 Accepted and use cds.spawn for background processing to avoid BTP load balancer timeoutsVector(1536) type in CDS entities for RAG scenariosFor complete code examples, see sap-cap-capire skill (AI Integration section) and sap-cloud-sdk-ai skill (CAP Integration subsection).
ABAP Cloud uses four foundational technologies:
For ABAP details: See references/abap-cloud.md
User Experience Design
Technology Design
Security in Design
For design patterns: See references/design-patterns.md
CAP Development:
# Initialize CAP project
cds init my-project
cd my-project
# Add SAP HANA support
cds add hana
# Add authentication
cds add xsuaa
# Run locally
cds watch
Key development tools:
Coding standards:
For tools catalog: See references/tools.md
Cloud Foundry Deployment:
# Build MTA archive
mbt build
# Deploy to Cloud Foundry
cf deploy mta_archives/my-project_1.0.0.mtar
Kyma Deployment:
# Use Helm charts or Terraform
terraform init
terraform apply
ABAP Deployment:
For deployment details: See references/deployment.md
Monitoring:
Scaling:
Cost optimization:
For operations: See references/operations.md
| Service | Purpose | |---------|---------| | SAP HANA Cloud | Database-as-a-Service, multi-model | | SAP Connectivity Service | On-premise/VPC connections via Cloud Connector | | SAP Destination Service | Routing, authentication management | | SAP Event Mesh | Event distribution between applications | | SAP Integration Suite | API Management, Cloud Integration |
| Tool | Purpose | |------|---------| | SAP Business Application Studio | Primary cloud IDE | | SAP Build | Low-code/no-code development | | Cloud Foundry CLI | CF deployment and management | | kubectl/Helm | Kyma/Kubernetes management | | Terraform Provider for SAP BTP | Infrastructure as code |
For architecture details: See references/architecture.md
For security details: See references/security.md
For connectivity details: See references/connectivity.md
SAP Continuous Integration and Delivery provides pre-configured pipelines:
Setup steps:
For CI/CD details: See references/cicd.md
OpenTelemetry is the industry standard for instrumentation.
For observability details: See references/observability.md
Sample applications:
For tutorial details: See references/tutorials.md
sap-btp-developer-guide/
├── SKILL.md # This file - Main guidance
├── README.md # Quick reference with auto-trigger keywords
└── references/ # Detailed guides (22 files)
├── Architecture & Setup
│ ├── architecture.md # Platform services and architecture
│ ├── runtimes.md # Runtime comparison (CF vs Kyma vs ABAP)
│ ├── setup.md # BTP landscape setup and Terraform
│ └── tools.md # Development tools catalog
├── Development
│ ├── cap-development.md # CAP development guide
│ ├── abap-cloud.md # ABAP Cloud development guide
│ ├── design-patterns.md # Design patterns and DDD
│ ├── extensions.md # SAP solution extensions
│ ├── mta.md # Multitarget applications
│ ├── testing.md # Testing strategies
│ └── ux-design.md # UX design and Fiori
├── Integration & Security
│ ├── connectivity.md # Connectivity patterns
│ ├── security.md # Security implementation
│ ├── hana-cloud.md # SAP HANA Cloud
│ └── resilience.md # Resilience patterns
├── Deployment & Operations
│ ├── deployment.md # Deployment options
│ ├── cicd.md # CI/CD pipelines
│ ├── observability.md # Monitoring and logging
│ ├── operations.md # Operations and scaling
│ └── partners.md # ISV/Partner development
└── Additional Resources
├── tutorials.md # Learning paths and missions
└── whats-new.md # Changelog and updates
architecture.md - Platform services overview and architecture patternsruntimes.md - Runtime comparison and selection guidesetup.md - BTP landscape setup with sizing recommendationstools.md - Complete development tools catalogcap-development.md - CAP development with Node.js/Javaabap-cloud.md - ABAP Cloud development with RAPdesign-patterns.md - Domain-driven design and patternsextensions.md - Side-by-side extensions for SAP solutionsmta.md - Multitarget application packagingtesting.md - Testing strategies and frameworksux-design.md - SAP Fiori UX design guidelinesconnectivity.md - Cloud-to-on-premise connectivitysecurity.md - Authentication, authorization, and securityhana-cloud.md - SAP HANA Cloud databaseresilience.md - Application resilience patternsdeployment.md - Deployment to CF, Kyma, and ABAPcicd.md - CI/CD pipelines with SAP toolsobservability.md - Monitoring, logging, and tracingoperations.md - Operations, scaling, and cost optimizationpartners.md - ISV/partner development guidelinestutorials.md - Hands-on missions and tutorialswhats-new.md - Latest features and changelogFor partner details: See references/partners.md
Official Documentation:
Design Resources:
Learning:
Source Documentation:
| Error | Cause | Solution |
|-------|-------|----------|
| Third-party cookie issues | Browser deprecation | See SAP Note 3409306 |
| XSUAA binding failures | Missing service instance | Run cf create-service xsuaa application |
| HANA deployment errors | Wrong target container | Check requires in mta.yaml |
| ATC Priority 1 findings | Non-cloud-compliant code | Use ABAP_CLOUD_DEVELOPMENT_DEFAULT variant |
tools
Use when automating SAP BW query inspection, InfoProvider metadata reads (characteristics, key figures), metadata-verified specification review, unsaved draft preparation, or human-confirmed query draft population through Eclipse or HANA Studio with BW Modeling Tools.
tools
Use when an agent must inspect or operate an authenticated SAP web UI through an in-app Browser, Microsoft Edge CDP, or an existing Playwright client, especially when SAP SSO reuse, isolated Edge profiles, deterministic target selection, screenshots, or browser bootstrap recovery is required.
tools
Evidence-based assessment of whether an SAP API/interface usage scenario aligns with the SAP API Policy (v.4.2026a). Use whenever someone asks whether a way of calling SAP is allowed/compliant — e.g. Published API vs internal/private/"confidential" API status, "Documented Use", whether a third-party tool / iPaaS / middleware / RPA bot / AI agent / MCP server may call SAP APIs, agentic or generative-AI access to SAP, bulk data extraction or replication into a lake/warehouse, custom Z/Y OData or RFC/BAPI wrappers and Clean Core, ADT/developer-tooling boundaries, ODP-RFC and other "not permitted" interfaces, partner Integration Certification, or RISE integration remediation. Trigger even when the policy is not named, e.g. "are we allowed to…", "is it compliant to…", "can we connect X to SAP…", "will this break under the new API policy". Produces a sourced technical assessment with a confidence level — explicitly NOT legal advice and NOT a final SAP compliance decision.
development
SAP-RPT-1-OSS local tabular prediction workflows for FI/CO prototype datasets. Use when preparing SAP finance CSV exports for classification or regression experiments with source-verified setup, leakage checks, and governance review.