btp-business-application-studio
Skill1 starsChanged 4 months agoMITView on GitHub
SAP Business Application Studio (BAS) — dev spaces, CAP project creation, Fiori tools, debugger setup, hybrid testing, deployment workflows, source control. Use when working in BAS, creating dev spaces, configuring extensions, or troubleshooting BAS connectivity.
- Installs packages
- Commits and pushes
In this repository413 other files it gives its agents.
- .agents/AGENTS.mdAGENTS.md
- AGENTS.mdAGENTS.md
- .codex/AGENTS.mdAGENTS.md
- .cursor/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- sap-router-skillCopilot instructions
- .cursor/rules/sap-router.mdcCursor rule
- abap-cloud-migrationSkill
- abap-cloudSkill
- abap-code-patternsSkill
- abap-code-reviewSkill
- abap-docs-referenceSkill
- abapgitSkill
- abapSkill
- abap-snippetSkill
- abap-sql-amdpSkill
- abap-system-infoSkill
- abap-unit-testingSkill
- arc-1-skillsSkill
- atc-cloudificationSkill
- authorization-iamSkill
- automation-pilot-catalog-explorerSkill
- automation-pilot-command-generationSkill
- automation-pilot-command-reviewSkill
- automation-pilot-content-management-via-apiSkill
- automation-pilot-debuggerSkill
- automation-pilot-executions-apiSkill
- automation-pilot-executor-executescriptSkill
- automation-pilot-executor-httprequestSkill
- automation-pilot-mcp-server-generationSkill
- automation-pilot-scheduled-executions-apiSkill
- badi-enhancementSkill
- btp-abap-environmentSkill
- btp-best-practicesSkill
- btp-build-work-zoneSkill
- btp-ciasSkill
- btp-cloud-foundrySkill
- btp-cloud-identitySkill
- btp-cloud-loggingSkill
- btp-cloud-platformSkill
- btp-cloud-transport-managementSkill
- btp-connectivitySkill
- btp-developer-guideSkill
- btp-diagram-generatorSkill
- btp-integration-suiteSkill
- btp-job-schedulingSkill
- btp-master-data-integrationSkill
- btp-service-managerSkill
- cap-add-remote-serviceSkill
- cap-developerSkill
- cap-triviaSkill
- capture-answerSkill
- cap-upgradeSkill
- cds-view-entitiesSkill
- claude-abap-skillsSkill
- claude-memSkill
- clean-abapSkill
- context-modeSkill
- cpi-iflow-developmentSkill
- engine-cap-developmentSkill
- The first 60 shown.
The file
Files
SAP Business Application Studio (BAS)
Cloud IDE on SAP BTP for CAP, Fiori, and full-stack development. Browser-based, no local install needed.
Prerequisites
- SAP BTP subaccount with SAP Business Application Studio entitlement
- Subscribed to BAS app (BTP Cockpit → Service Marketplace → Subscribe)
- Space Quota with sufficient memory (min 4 GB for dev space)
- Cloud Foundry CLI installed locally for
cfcommands outside BAS - GitHub/GitLab account or SAP Git repository for source control
Dev Space Types
| Type | Key Extensions | Best For |
| Full Stack Cloud Application | CAP, CDS, Fiori tools, MTA | CAP + Fiori apps |
| SAP Fiori | Fiori tools, UI5 Adaptation | Freestyle UI5, adaptation |
| SAP HANA Native | HANA tools, DB Explorer, HDI | HANA DB artifacts |
| Basic | None (manual install) | Custom setup, non-SAP |
Steps
1. Create a Dev Space
- Open BTP Cockpit → Service Marketplace → SAP Business Application Studio → Go to Application
- Click Create Dev Space → Enter name
- Select type: Full Stack Cloud Application (for CAP + Fiori)
- Optionally add extensions (defaults are sufficient for most workflows)
- Click Create → wait ~2 min → status shows RUNNING
- Click dev space name to open the IDE in browser
2. Create a CAP Project
# In BAS terminal (Terminal → New Terminal)
cd /home/user/projects
cds init my-app --add java,nodejs,mta,fiori,sample
cd my-app
npm install
# Create Fiori app from template
# Use View → Find Command → "Fiori: Open Application Generator"
# Choose floorplan (List Report, Object Page, etc.)
# Select OData service → Configure → Generate3. Clone an Existing Project
cd /home/user/projects
git clone https://github.com/myorg/my-cap-app.git
cd my-cap-app
npm install4. Hybrid Testing with BTP Services
Bind local CAP runtime to BTP-backed services (HDI, XSUAA, destination) for realistic testing:
# Bind to running BTP service instances
cds bind -2 my-hdi-container,my-xsuaa
# Start dev server with hybrid profile
cds watch --profile hybrid
# Test endpoint locally — hits real BTP backends
curl http://localhost:4004/odata/v4/catalog/Books5. Set Up the Debugger
- Open the
.jsor.tshandler file in BAS editor - Click the gutter next to a line number to set a breakpoint (red dot)
- Press
F5→ select debug configuration: CDS with Node.js - Debugger pauses at breakpoint — use:
F10: Step OverF11: Step IntoShift+F11: Step OutF5: Continue
- Watch variables in the left panel; use Console for expressions
6. Build and Deploy
# Compile CDS → CSN/EDMX/SQL
cds build
# Build MTA archive
mbt build
# Deploy to Cloud Foundry
cf login -a https://api.cf.us10.hana.ondemand.com -o <org> -s <space>
cf deploy mta_archives/my-app_1.0.0.mtar
# Push to git
git add -A && git commit -m "feat: initial CAP app"
git push origin mainPitfalls
| Cause | Solution |
| Dev space stopped unexpectedly | Dev spaces auto-stop after 30 min idle. In BAS launcher, click Start to resume. Work is preserved. |
cds bind fails with "service not found" | Service instances must exist in the current CF space. Run cf services to verify. Create missing instances with cf create-service. |
| Large node_modules exceeds 10 GB limit | Dev spaces have 10 GB storage. Run npm prune --production or delete .cache/ dir. Use npm ci instead of npm install for deterministic builds. |
| Only one dev space running | Free-tier subaccounts allow only 1 running dev space. Stop others before starting a new one. |
| Extension not found in marketplace | BAS uses the Open VSX Registry, not the VS Code Marketplace. Install custom extensions from .vsix files via Extensions → ... → Install from VSIX. |
mbt build fails — Makefile not found | Run cds add mta first to generate the mta.yaml and Makefile. Ensure mbt CLI is installed: npm install -g mbt. |
| Debugger won't attach | Ensure cds watch is not already running on the same port. Stop it, then start via F5 debug config. Check .vscode/launch.json exists. |
Verification
# Dev space is running
# (Check in BAS launcher — status should be "RUNNING")
# CAP project structure is valid
cds compile srv/ -2 sql 2>&1 | head -5 # No errors = valid model
# Dev server responds
curl -s http://localhost:4004/odata/v4/catalog/$metadata | head -3
# MTA archive built
ls -la mta_archives/*.mtar # Should show .mtar file
# Deployment succeeded
cf apps # App should show "started" state
curl -s https://my-app.cfapps.<region>.hana.ondemand.com/odata/v4/catalog/$metadata | head -3
# Git push succeeded
git log --oneline -3 # Shows recent commits
git status # Shows "up to date"Checklist:
- Dev space shows status RUNNING in BAS launcher
cds watchserves OData endpoint atlocalhost:4004- Hybrid binding resolves real BTP service instances
- Breakpoints hit correctly in debugger
mbt buildproduces.mtarwithout errorscf deploycompletes with all modules started- Git repository is up to date (
git statusclean)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

