Lesson 1 of 6
SAP Build Code and Joule: what you get and what it costs
10 min
Listen to this lesson
Contoso's after-sales team wants a small app to take warranty claims for alternators that fleet customers send back: Great Lakes Fleet Services reports a failed CMC-ALT-100, a claim is opened, reviewed and approved or rejected. It's a textbook side-by-side extension on SAP BTP, and Elena, the BTP developer on Kenji's team, has two weeks. She plans to start in SAP Build Code with Joule, then continue in VS Code with SAP's MCP servers and a coding agent. This course follows her app from first prompt to a production decision, and keeps asking the question a test lead like Priya will ask: how do we know the generated app is right?
What SAP Build Code is
SAP describes SAP Build Code as an AI-powered cloud development environment for CAP, SAP Fiori, mobile and SAPUI5 developers. It isn't one product but a bundle: SAP Business Application Studio as the IDE, plus the services an extension project usually needs. With Joule, SAP says it can generate application code, data models, services and sample data.
Plans, entitlements and where Joule works
| Item | What SAP documents | Why it matters |
|---|---|---|
| Service plans | Standard, free and trial application plans in enterprise accounts; the trial runs in the US10 region | Trial and free plans have limits; don't judge production effort from a trial |
| Joule generation | Available only in the build-code or build-default plan | A plain SAP Business Application Studio subscription doesn't give you Joule generation |
| Free plan | Two dev spaces, one running, 4 GB each, two deployments from the full-stack dev space, and a limited monthly quota of AI requests per user | Enough to learn, not enough to build Elena's app end to end |
| Roles | Role templates Build Code Administrator and Build Code Developer | Developers need the Developer role in the subaccount |
| Admin switch | Administrators can enable or disable AI features, including AI Chat, at account level | Check this first when Joule "isn't there" |
SAP Build Code plans and AI availability as documented on the SAP Help Portal (checked October 2026).
Joule and AI Chat are not the same thing
Business Application Studio now has two AI entry points. Joule is SAP's assistant with scenario-specific features: slash commands that generate CAP data models and services, sample data, application logic and unit tests, and /ui5 commands for freestyle UI5 apps. AI Chat is a general coding assistant in the IDE. In the build-code and build-default plans it comes with preconfigured models for limited use under per-user fair-use limits, which SAP says may change or be discontinued. For production work SAP points you to a configured provider: SAP AI Core, a third-party LLM provider through your own service key, or GitHub Copilot credentials.
Watch the dates. When SAP ended the free Joule for Developers promotion for ABAP on 30 September 2026, its September 2026 announcement kept the promotion for SAP Build generative AI features running to 31 December 2026 and said AI Chat in SAP Build Code continues after that under fair use, with your own provider as the long-term option. Ask your account team in writing what your contract provides for Joule's generation features from January 2027, and record the answer in the project plan before a team builds its way of working around them.
A practical consequence for planning: AI help in the IDE is metered and governed by entitlements and admin settings, not by the developer's enthusiasm. Before Elena starts, Sam checks that the cmc-ext-dev subaccount has the build-code plan, that AI features are enabled, and that her user has the Build Code Developer role.
What "generated" means for quality
Generated code is a draft written very quickly by something that has read a great deal of CAP and Fiori code but has never met Contoso's after-sales process. It will follow common patterns, and it will fill gaps in the prompt with assumptions. Some assumptions will be right. Others, such as who may approve a claim or how old a claim may be, are business rules that only Contoso can decide. The quality job doesn't change because the code was generated: someone must read it, test it against the rules and take responsibility for it. What changes is the speed at which drafts arrive, which makes review and testing the bottleneck. Plan for that from day one rather than discovering it in the sprint review.
What would you do?
To get going quickly, Elena wants to connect AI Chat in Business Application Studio to her personal account with a third-party model provider, and to load a CSV of last year's real warranty claims as sample data "so Joule understands the business". What should Kenji say?
- SAP Build Code is Business Application Studio plus lifecycle and runtime services, with Joule generation.
- Joule generation needs the build-code or build-default plan; the free plan has a limited monthly AI request quota.
- AI Chat can use SAP's preconfigured models (fair-use limits), SAP AI Core, a third-party key or GitHub Copilot.
- Keep personal data out of project files; with your own key, provider terms and data handling are your responsibility.
Check your understanding · not graded
Lesson check
1. Which plans does SAP name for Joule generation in Business Application Studio?
2. Why must Contoso keep personal data out of its CAP project files?
3. What does SAP say about the preconfigured models in AI Chat?
4. Joule is missing for a developer in a correctly subscribed subaccount. What should the admin check first?