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
- Identify the target account model: global account, directories, subaccounts, environments, and regions.
- Choose the runtime path: Cloud Foundry, Kyma, ABAP Environment, or a hybrid portfolio.
- Apply security defaults from Security and Authentication.
- 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.
- 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
- Platform Fundamentals
- Account Model Setup
- Security and Authentication
- Connectivity
- Governance and Teams
- Development
- AI Development
- Deployment and Delivery
- High Availability and Failover
- Operations and Monitoring
- Cost Management
- 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
| Environment |
Use Case |
Key Features |
| Cloud Foundry |
Polyglot apps |
Multiple buildpacks, spaces |
| Kyma |
Cloud-native K8s |
Open-source, namespaces |
| ABAP |
ABAP extensions |
RAP, cloud-ready ABAP |
| Neo |
Legacy |
Migrate 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
| Entity |
Convention |
Example |
| Subaccount |
Natural language |
"HR Development" |
| Subdomain |
Lowercase, hyphens |
hr-dev-acme |
| CF Org |
Company prefix |
acme-hr-dev |
| CF Space |
Consistent across stages |
hr-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:
- Add multiple administrators (different time zones)
- Enable MFA for all admins
- Configure security alerts
- Set up backup admins in SAP ID Service
Authorization Methods
| Method |
Best For |
Notes |
| Provisioning |
Production, many users |
Centralized roles, automated offboarding |
| Federation |
Simple scenarios |
Real-time sync, but doesn't scale well |
| Manual |
Testing only |
Quick 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
- Onboarding Doc: Organization, app IDs, timeline, tech stack
- Security Doc: Data sensitivity, policies, auth framework
- 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
- Explore: Business opportunity, team roles
- Discover: Use cases, technology options
- Design: UX design, domain-driven design
- Deliver: Landscape setup, development
- 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 service keys for secure authentication
- Implement PII data masking
- Build RAG with SAP HANA Cloud Vector Engine
- Configure content filtering
- Monitor model drift
Use Cases: 20+ samples including chatbots, PDF extraction, procurement.
CAP + AI Integration Patterns:
- Use SAP Cloud SDK for AI (
@sap-ai-sdk/orchestration) inside CAP event handlers — never raw HTTP calls to LLM providers
- Bind AI Core service instance to CAP app via MTA (plan:
extended) — credentials are managed by BTP, not in code
- Always process LLM calls asynchronously in production: return
202 Accepted, process in background via cds.spawn. LLM responses can take 30-60 seconds, exceeding BTP load balancer timeouts
- Externalize prompts into JSON files or CDS entities so they can be updated without redeployment
- Use HANA Cloud
Vector(1536) type in CDS entities for RAG scenarios with the HANA Vector Engine
- Allocate at least 512MB memory for Node.js containers processing large text payloads with the AI SDK
- Implement resilience: validate LLM outputs before writing to the database (prevent injection attacks), cache frequent responses for cost control
See: references/ai-development-best-practices.md for patterns and examples. For CAP-specific code patterns, see sap-cap-capire skill. For SDK integration, see sap-cloud-sdk-ai skill.
Deployment and Delivery
Deployment Methods
Cloud Foundry/Neo:
- Package as MTA archive
- Deploy via: BTP Cockpit, CF CLI, Business Application Studio
Kyma:
- Docker images (Dockerfile or Cloud Native Buildpacks)
- Helm charts for production
- Deploy via SAP Continuous Integration and Delivery
CI/CD Approaches
SAP Continuous Integration and Delivery:
- Low expertise required
- Ready-to-use infrastructure
- Direct SAP support
Project "Piper":
- High expertise required
- Jenkins-based
- Open-source community support
Best Practice: Combine CI/CD with SAP Cloud Transport Management for governance + agility.
See: references/deployment-and-delivery.md for detailed configs
High Availability and Failover
Multi-Region Architecture
Custom Domain URL
│
Load Balancer
├── Region 1 (active)
└── Region 2 (passive/active)
Failover Implementation
Four Core Principles:
- Deploy in Two Regions: Near users and backend systems
- Keep Synced: CI/CD pipeline or Cloud Transport Management
- Define Detection: Monitor 5xx errors, timeouts
- Plan Failback: Visual differentiation, user-driven
Legal: Check cross-region data processing restrictions.
See: references/failover-and-resilience.md for implementation details
Operations and Monitoring
Go-Live Checklist
- Deploy to production
- Set go-live timeframe (avoid quarter-end)
- Embed in SAP Fiori Launchpad
- Provision business users
- Configure role collections
Monitoring Tools
SAP Cloud ALM (Enterprise Support):
- Real User Monitoring
- Health Monitoring
- Integration and Exception Monitoring
- Job Automation Monitoring
SAP Cloud Logging:
- Observability across CF, Kyma, Kubernetes
SAP Alert Notification:
- Multi-channel notifications (email, chat, ticketing)
Cost Management
Best Practices
- Check Costs and Usage monthly
- Provide minimal required entitlements
- Use labels for cost allocation
- Set up automated alerts (Usage Data Management + Alert Notification)
Contract Strategies
- Consolidate subscriptions in one global account
- Use hybrid accounts for mixed workloads
- Note: Consumption credits non-transferable between global accounts
Bundled Resources
This skill provides comprehensive reference documentation:
Account & Governance
Security & Connectivity
references/security-and-authentication.md (13K lines)
- Complete auth methods comparison
- Destination configuration
- Kyma RBAC manifests
- Identity lifecycle management
Deployment & Operations
High Availability
references/failover-and-resilience.md (12K lines)
- Multi-region architecture
- Load balancer configurations
- Failover automation scripts
Templates & Examples
references/templates-and-examples.md (18K lines)
- Complete code templates
- Kubernetes RBAC manifests
- MTA descriptors
- Helm charts
- CI/CD configs
AI Development
references/ai-development-best-practices.md (6K lines)
- Generative AI patterns
- RAG implementation
- 20+ use cases catalog
Progress Tracking
- Implementation status
- Coverage details
- Validation checklists
Administration Tools
| Tool |
Use Case |
| SAP BTP Cockpit |
GUI for all admin tasks |
| btp CLI |
Terminal/automation scripting |
| REST APIs |
Programmatic administration |
| Terraform Provider |
Infrastructure as Code |
| SAP Automation Pilot |
Low-code/no-code automation |
Shared Responsibility Model
SAP Manages:
- Platform software updates/patches
- Infrastructure and OS monitoring
- BTP service monitoring
- Capacity management and incidents
- Global account provisioning
- HANA database operations
- Kyma
kyma-system namespace
You Manage:
- Global account strategy and subaccount config
- Application development, deployment, security
- Role assignments and integrations
- Application monitoring and health checks
- Open source vulnerability scanning
- Triggering HANA revision updates
Last Updated: 2026-06-16
Review Progress: See SAP_SKILLS_REVIEW_PROGRESS.md
Next Review: Source refresh pending; do not advance last_verified without primary-source evidence.
1---
2name: sap-btp-best-practices
3description: |
4 SAP BTP best practices for enterprise architecture, account management, security, and operations, with verification evidence tracked in the repository ledger. Use when planning BTP implementations, setting up account hierarchies, configuring environments, implementing authentication, designing CI/CD pipelines, establishing governance, building Platform Engineering teams, implementing failover strategies, or managing application lifecycle on SAP BTP.
5
6 Keywords: SAP BTP, account hierarchy, global account, directory, subaccount, Cloud Foundry, Kyma, ABAP, SAP Identity Authentication, CI/CD, governance, Platform Engineering, failover, multi-region, SAP BTP best practices
7license: GPL-3.0
8metadata:
9 source: https://skillmd.com/skills/secondsky/sap-btp-best-practices
10 maintainer: "Eduard Jiglau"
11 maintainer_email: "hello@sap-ai-skills.com"
12 website: "https://sap-ai-skills.com"
13 version: "2.4.1"
14 last_verified: "2025-11-27"
15---
16
17# SAP BTP Best Practices
18
19## Related Skills
20
21- **sap-btp-cloud-platform**: Use for technical implementation details, CLI commands, and runtime configurations
22- **sap-btp-connectivity**: Use for connectivity patterns, destination configuration, and Cloud Connector setup
23- **sap-btp-service-manager**: Use for service lifecycle management and programmatic service operations
24- **sap-btp-developer-guide**: Use for development workflows, CAP integration, and application patterns
25- **sap-cap-capire**: Use when designing CAP applications on BTP or implementing multitenancy
26- **sap-ai-core**: Use for AI Core platform setup, model deployment, and orchestration configuration
27- **sap-cloud-sdk-ai**: Use for SDK-level AI integration in CAP or standalone BTP applications
28- **sap-fiori-tools**: Use for UI deployment strategies and frontend application guidelines
29
30## When to Use This Skill
31
32Use 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.
33
34## Quick Start
35
361. Identify the target account model: global account, directories, subaccounts, environments, and regions.
372. Choose the runtime path: Cloud Foundry, Kyma, ABAP Environment, or a hybrid portfolio.
383. Apply security defaults from [Security and Authentication](#security-and-authentication).
394. 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`.
405. Record production-specific gaps in the project plan before changing `last_verified`.
41
42Documentation-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.
43
44**Quick Links**:
45- **Official Guide**: [https://github.com/SAP-docs/btp-best-practices-guide](https://github.com/SAP-docs/btp-best-practices-guide)
46- **SAP Help Portal**: [https://help.sap.com/docs/btp/btp-administrators-guide](https://help.sap.com/docs/btp/btp-administrators-guide)
47
48---
49
50## Table of Contents
51
521. [Platform Fundamentals](#platform-fundamentals)
532. [Account Model Setup](#account-model-setup)
543. [Security and Authentication](#security-and-authentication)
554. [Connectivity](#connectivity)
565. [Governance and Teams](#governance-and-teams)
576. [Development](#development)
587. [AI Development](#ai-development)
598. [Deployment and Delivery](#deployment-and-delivery)
609. [High Availability and Failover](#high-availability-and-failover)
6110. [Operations and Monitoring](#operations-and-monitoring)
6211. [Cost Management](#cost-management)
6312. [Bundled Resources](#bundled-resources)
64
65---
66
67## Platform Fundamentals
68
69### Account Hierarchy
70
71```
72Global Account (SAP contract)
73├── Directory (optional, up to 7 levels)
74│ └── Subaccount (region-specific, apps run here)
75│ ├── Cloud Foundry Org → Spaces
76│ └── Kyma Cluster → Namespaces
77└── Subaccount
78```
79
80**Key Points**:
81- Global account = contract with SAP (one per commercial model)
82- Directory = groups subaccounts (max 7 levels deep)
83- Subaccount = deployed in specific region, enables runtimes
84- Use labels for virtual grouping (Dev/Test/Prod, cost centers)
85
86### Environments
87
88| Environment | Use Case | Key Features |
89|-------------|----------|--------------|
90| **Cloud Foundry** | Polyglot apps | Multiple buildpacks, spaces |
91| **Kyma** | Cloud-native K8s | Open-source, namespaces |
92| **ABAP** | ABAP extensions | RAP, cloud-ready ABAP |
93| **Neo** | Legacy | **Migrate away** - HTML5, Java, HANA XS |
94
95### Commercial Models
96
97- **Consumption-Based** (BTPEA/CPEA): Flexible access, best for pilots
98- **Subscription-Based**: Fixed-cost for known service needs
99
100**Best Practice**: Start with consumption-based, move to subscription for stable workloads.
101
102---
103
104## Account Model Setup
105
106### Simple Model (3 subaccounts)
107```
108Global Account
109├── Dev Subaccount
110├── Test Subaccount
111└── Prod Subaccount
112```
113Best for: Initial implementations, single team, <3 projects
114
115### Directory Model (scalable)
116```
117Global Account
118├── Directory: HR
119│ ├── hr-dev / hr-test / hr-prod
120├── Directory: Sales
121│ ├── sales-dev / sales-test / sales-prod
122└── Directory: Central IT
123 ├── api-management
124 └── shared-services
125```
126Best for: Multiple teams, cost allocation, complex governance
127
128### Naming Conventions
129
130| Entity | Convention | Example |
131|--------|------------|---------|
132| Subaccount | Natural language | "HR Development" |
133| Subdomain | Lowercase, hyphens | `hr-dev-acme` |
134| CF Org | Company prefix | `acme-hr-dev` |
135| CF Space | Consistent across stages | `hr-recruiting` |
136
137**Tip**: Derive CF org/Kyma names from subaccount names for consistency.
138
139---
140
141## Security and Authentication
142
143### Identity Provider Setup
144
145**Always use SAP Cloud Identity Services - Identity Authentication**
146
147```
148Corporate IdP → Identity Authentication (proxy) → SAP BTP
149```
150
151**Critical Steps**:
1521. Add multiple administrators (different time zones)
1532. Enable MFA for all admins
1543. Configure security alerts
1554. Set up backup admins in SAP ID Service
156
157### Authorization Methods
158
159| Method | Best For | Notes |
160|--------|----------|-------|
161| **Provisioning** | Production, many users | Centralized roles, automated offboarding |
162| **Federation** | Simple scenarios | Real-time sync, but doesn't scale well |
163| **Manual** | Testing only | Quick setup, not production-ready |
164
165### Destination Authentication
166
167**Recommended**:
168- `PrincipalPropagation` - SAP on-premise systems
169- `OAuth2SAMLBearerAssertion` - Third-party systems
170- `OAuth2JWTBearer` - User token exchange
171
172**Avoid in Production**:
173- `BasicAuthentication`
174- `OAuth2Password`
175
176**See**: `references/security-and-authentication.md` for complete guidance
177
178---
179
180## Connectivity
181
182### Remote System Access
183
184- **Internet Services**: Destinations with authentication
185- **On-Premise Systems**: Destinations + Cloud Connector
186
187### Cloud Connector
188
189- Lightweight on-premise agent
190- Secure tunnel to SAP BTP (no inbound ports)
191- Fine-grained access control
192- Supports RFC and HTTP protocols
193- Enables principal propagation
194
195**Note**: Each subaccount needs separate Cloud Connector config.
196
197---
198
199## Governance and Teams
200
201### Required Teams
202
203**Platform Engineering Team (Center of Excellence)**:
204- Manages cloud landscape infrastructure
205- Handles account operations, build infrastructure
206- Creates governance and compliance guidelines
207- **Does NOT** manage individual application lifecycles
208
209**Cloud Development Teams**:
210- Follow DevOps (develop AND operate)
211- Responsible for application lifecycle
212- Regular maintenance (e.g., UI updates every 6 months)
213
214### Essential Documentation
215
2161. **Onboarding Doc**: Organization, app IDs, timeline, tech stack
2172. **Security Doc**: Data sensitivity, policies, auth framework
2183. **Services Catalog**: Templates for destinations, builds, schemas
219
220---
221
222## Development
223
224### Programming Models
225
226**SAP CAP (Cloud Application Programming Model)**:
227- Framework with languages, libraries, tools
228- Supports Java, JavaScript, TypeScript
229- Enterprise-grade services and data models
230
231**ABAP Cloud**:
232- Modern ABAP for cloud-ready apps
233- RAP (RESTful ABAP Programming Model)
234- Extensions for ABAP-based products
235
236### Development Lifecycle
237
2381. **Explore**: Business opportunity, team roles
2392. **Discover**: Use cases, technology options
2403. **Design**: UX design, domain-driven design
2414. **Deliver**: Landscape setup, development
2425. **Run and Scale**: Feedback, optimization
243
244---
245
246## AI Development
247
248SAP BTP provides AI capabilities through **SAP AI Core** for:
249- **Generative AI** (LLMs, RAG)
250- **Narrow AI** (classical ML)
251
252**Key Resources**:
253- Repository: [SAP-samples/sap-btp-ai-best-practices](https://github.com/SAP-samples/sap-btp-ai-best-practices)
254- Documentation: [https://btp-ai-bp.docs.sap/](https://btp-ai-bp.docs.sap/)
255
256**Best Practices**:
257- Use service keys for secure authentication
258- Implement PII data masking
259- Build RAG with SAP HANA Cloud Vector Engine
260- Configure content filtering
261- Monitor model drift
262
263**Use Cases**: 20+ samples including chatbots, PDF extraction, procurement.
264
265**CAP + AI Integration Patterns**:
266- Use SAP Cloud SDK for AI (`@sap-ai-sdk/orchestration`) inside CAP event handlers — never raw HTTP calls to LLM providers
267- Bind AI Core service instance to CAP app via MTA (plan: `extended`) — credentials are managed by BTP, not in code
268- Always process LLM calls asynchronously in production: return `202 Accepted`, process in background via `cds.spawn`. LLM responses can take 30-60 seconds, exceeding BTP load balancer timeouts
269- Externalize prompts into JSON files or CDS entities so they can be updated without redeployment
270- Use HANA Cloud `Vector(1536)` type in CDS entities for RAG scenarios with the HANA Vector Engine
271- Allocate at least **512MB** memory for Node.js containers processing large text payloads with the AI SDK
272- Implement resilience: validate LLM outputs before writing to the database (prevent injection attacks), cache frequent responses for cost control
273
274**See**: `references/ai-development-best-practices.md` for patterns and examples. For CAP-specific code patterns, see **sap-cap-capire** skill. For SDK integration, see **sap-cloud-sdk-ai** skill.
275
276---
277
278## Deployment and Delivery
279
280### Deployment Methods
281
282**Cloud Foundry/Neo**:
283- Package as MTA archive
284- Deploy via: BTP Cockpit, CF CLI, Business Application Studio
285
286**Kyma**:
287- Docker images (Dockerfile or Cloud Native Buildpacks)
288- Helm charts for production
289- Deploy via SAP Continuous Integration and Delivery
290
291### CI/CD Approaches
292
293**SAP Continuous Integration and Delivery**:
294- Low expertise required
295- Ready-to-use infrastructure
296- Direct SAP support
297
298**Project "Piper"**:
299- High expertise required
300- Jenkins-based
301- Open-source community support
302
303**Best Practice**: Combine CI/CD with SAP Cloud Transport Management for governance + agility.
304
305**See**: `references/deployment-and-delivery.md` for detailed configs
306
307---
308
309## High Availability and Failover
310
311### Multi-Region Architecture
312
313```
314Custom Domain URL
315 │
316 Load Balancer
317 ├── Region 1 (active)
318 └── Region 2 (passive/active)
319```
320
321### Failover Implementation
322
323**Four Core Principles**:
324
3251. **Deploy in Two Regions**: Near users and backend systems
3262. **Keep Synced**: CI/CD pipeline or Cloud Transport Management
3273. **Define Detection**: Monitor 5xx errors, timeouts
3284. **Plan Failback**: Visual differentiation, user-driven
329
330**Legal**: Check cross-region data processing restrictions.
331
332**See**: `references/failover-and-resilience.md` for implementation details
333
334---
335
336## Operations and Monitoring
337
338### Go-Live Checklist
339
3401. Deploy to production
3412. Set go-live timeframe (avoid quarter-end)
3423. Embed in SAP Fiori Launchpad
3434. Provision business users
3445. Configure role collections
345
346### Monitoring Tools
347
348**SAP Cloud ALM** (Enterprise Support):
349- Real User Monitoring
350- Health Monitoring
351- Integration and Exception Monitoring
352- Job Automation Monitoring
353
354**SAP Cloud Logging**:
355- Observability across CF, Kyma, Kubernetes
356
357**SAP Alert Notification**:
358- Multi-channel notifications (email, chat, ticketing)
359
360---
361
362## Cost Management
363
364### Best Practices
365
3661. Check *Costs and Usage* monthly
3672. Provide minimal required entitlements
3683. Use labels for cost allocation
3694. Set up automated alerts (Usage Data Management + Alert Notification)
370
371### Contract Strategies
372
373- Consolidate subscriptions in one global account
374- Use hybrid accounts for mixed workloads
375- Note: Consumption credits non-transferable between global accounts
376
377---
378
379## Bundled Resources
380
381This skill provides comprehensive reference documentation:
382
383### Account & Governance
384- **`references/account-models.md`** (11K lines)
385 - Detailed account structure patterns
386 - Naming conventions and examples
387 - Cost allocation strategies
388
389- **`references/governance-and-teams.md`** (13K lines)
390 - Platform Engineering team structure
391 - Onboarding processes
392 - Documentation templates
393
394### Security & Connectivity
395- **`references/security-and-authentication.md`** (13K lines)
396 - Complete auth methods comparison
397 - Destination configuration
398 - Kyma RBAC manifests
399 - Identity lifecycle management
400
401### Deployment & Operations
402- **`references/deployment-and-delivery.md`** (10K lines)
403 - MTA descriptor templates
404 - CI/CD pipeline configs
405 - Transport management setup
406
407- **`references/operations-and-monitoring.md`** (11K lines)
408 - Go-live procedures
409 - Monitoring setup guides
410 - Troubleshooting checklists
411
412### High Availability
413- **`references/failover-and-resilience.md`** (12K lines)
414 - Multi-region architecture
415 - Load balancer configurations
416 - Failover automation scripts
417
418### Templates & Examples
419- **`references/templates-and-examples.md`** (18K lines)
420 - Complete code templates
421 - Kubernetes RBAC manifests
422 - MTA descriptors
423 - Helm charts
424 - CI/CD configs
425
426### AI Development
427- **`references/ai-development-best-practices.md`** (6K lines)
428 - Generative AI patterns
429 - RAG implementation
430 - 20+ use cases catalog
431
432### Progress Tracking
433 - Implementation status
434 - Coverage details
435 - Validation checklists
436
437---
438
439## Administration Tools
440
441| Tool | Use Case |
442|------|----------|
443| **SAP BTP Cockpit** | GUI for all admin tasks |
444| **btp CLI** | Terminal/automation scripting |
445| **REST APIs** | Programmatic administration |
446| **Terraform Provider** | Infrastructure as Code |
447| **SAP Automation Pilot** | Low-code/no-code automation |
448
449---
450
451## Shared Responsibility Model
452
453**SAP Manages**:
454- Platform software updates/patches
455- Infrastructure and OS monitoring
456- BTP service monitoring
457- Capacity management and incidents
458- Global account provisioning
459- HANA database operations
460- Kyma `kyma-system` namespace
461
462**You Manage**:
463- Global account strategy and subaccount config
464- Application development, deployment, security
465- Role assignments and integrations
466- Application monitoring and health checks
467- Open source vulnerability scanning
468- Triggering HANA revision updates
469
470---
471
472**Last Updated**: 2026-06-16
473**Review Progress**: See SAP_SKILLS_REVIEW_PROGRESS.md
474**Next Review**: Source refresh pending; do not advance `last_verified` without primary-source evidence.