1. Home
  2. DevOps
  3. Low-code / no-code

SAP Low-Code and No-Code: who builds the app now?

No-code, low-code and pro-code explained for SAP users and consultants, from SAP Query to SAP Build and Joule Studio.

  • SAP Build Apps
  • Process Automation
  • Citizen developer
  • Joule Studio

By · Updated

What is low-code and no-code?

Low-code and no-code, often shortened to LCNC, are ways to build software by putting ready-made blocks together on a screen instead of writing code line by line. With no-code you only drag, drop and configure. With low-code you do the same, plus the odd formula, rule or small script. Pro-code is traditional programming in languages such as ABAP, Java or JavaScript.

In SAP the label covers a family of tools. The best known is SAP Build, launched in November 2022: SAP Build Apps for apps (the former AppGyver), SAP Build Process Automation for workflows and bots, and SAP Build Work Zone for business sites, now joined by Joule Studio for AI agents. Inside SAP S/4HANA, key users have low-code tools of their own to add fields, logic and reports without touching SAP’s code.

Below: the three approaches side by side, a quick test to see which one fits your idea, how SAP got here, the AppGyver story, every SAP tool in one catalogue, and what a citizen developer is, with separate sections for key users and consultants.

For readers outside IT

Think of dinner. No-code is ordering from the menu and choosing the sides: fast, but only what the kitchen offers. Low-code is a meal kit: the ingredients come prepared, you follow the card and add your own spices. Pro-code is cooking from scratch: anything is possible, but you need a cook and more time. Most companies use all three, depending on the evening.

The three approaches

No-code, low-code, pro-code: one spectrum

They are not rivals but points on a line. The further right, the more you can build and the more skill it takes.

  • No-code

    Assemble and configure

    Drag components onto a screen, pick options from lists, connect to data someone has prepared. If the tool can do it, anyone trained can do it; if not, you are stuck.

    • SAP Build Apps
    • Work Zone
    • Custom Analytical Queries
    • Adapt UI

  • Low-code

    Assemble, then add a little logic

    The same building blocks, plus formulas, decision tables, small scripts and API calls. Business people and developers often work on the same project, each on their part.

    • Process Automation
    • Joule Studio
    • Custom Logic
    • BRF+

  • Pro-code

    Write the code

    Developers write, test and version code in a development environment. Nothing is off limits, but every change needs a specialist, tests and time.

    • SAP Build Code
    • ABAP Cloud
    • SAPUI5
    • CAP
Faster to startMore control

Side by side

QuestionNo-codeLow-codePro-code
Who builds itBusiness users and key usersKey users with IT, and developers who want speedProfessional developers
Skills neededSpreadsheet level: forms, lists, simple formulasLogic, data models, APIs, a little scriptingABAP, Java or JavaScript, testing, architecture
How you buildDrag, drop and configureDrag and drop, plus formulas, rules and small scriptsWrite code in a development environment
First versionHours to daysDays to weeksWeeks to months
FlexibilityOnly what the tool offersMost needs, through extension pointsAnything the platform allows
Where it breaksComplex rules, unusual screensVery high volumes, deep integrationBudget and time
Who maintains itThe builder, so name a backupBusiness and IT togetherIT
In SAPSAP Build Apps, Work Zone, Custom Analytical Queries, Adapt UISAP Build Process Automation, Joule Studio, Custom Logic, Fiori elements, BRF+SAP Build Code, ABAP Cloud, SAPUI5, CAP

Quick test

Which approach fits your idea?

Four questions, thirty seconds. Think of one real request from your team and answer for it.

Question 1 of 4Who will build it and look after it?
Question 2 of 4What does it need to do?
Question 3 of 4How does it touch SAP data?
Question 4 of 4Who will use it?

Your answers point to

Answer the four questions

Mostly A answers point to a no-code tool, mostly B to low-code built with IT, mostly C to professional developers.

Start with a no-code tool

A business user can build a first version in hours or days by configuring what the tool offers. Ask IT once for access and data connections, then improve it with the people who use it.

SAP tools to look at

  • SAP Build Apps
  • SAP Build Work Zone
  • Custom Analytical Queries
  • Adapt UI
  • SAP Analytics Cloud

Low-code, built by business and IT together

Drag and drop gets you most of the way; formulas, rules and API calls do the rest. Plan an IT review before the app writes to SAP or goes live for many users.

SAP tools to look at

  • SAP Build Process Automation
  • SAP Build Apps
  • Joule Studio
  • Custom Fields and Logic
  • BRF+

This one needs professional developers

Complex logic, volumes or deep integration call for code, tests and an architect. Business users still shape it: they write the requirements, test it, and may build the screens around it.

SAP tools to look at

  • SAP Build Code
  • ABAP Cloud
  • SAP Fiori elements
  • SAP Integration Suite

Real projects often mix all three: a no-code screen, a low-code workflow and a pro-code API underneath.

Low-code at SAP in four numbers

  • 18

    employees worked at AppGyver, the Helsinki start-up founded in 2010, when SAP bought it in February 2021.

  • 17,000+

    customers used SAP Build solutions worldwide, according to SAP in March 2025.

  • 80%

    of low-code tool users would sit outside formal IT by 2026, up from 60% in 2021, Gartner forecast.

  • 2 million

    developers SAP pledged to train by 2025 when it launched SAP Build, partly through a Coursera certificate.

Evolution

How SAP got here: five steps

SAP has been trying to cut code out of ERP since the 1970s. The word low-code is new; the idea is not. Pick a step.

Step 1 · SAP R/2 and R/3

Settings first, ABAP for the rest

SAP’s founding idea was standard software that each company adapts with settings, not code. Customizing tables did most of the work and ABAP did the rest. Power users soon got tools to build their own lists and load data without a programmer.

Tools of the time

  • Customizing (SPRO)
  • SAP Query (SQ01)
  • QuickViewer (SQVI)
  • Report Painter (GRR1)
  • LSMW
  • ABAP

What it solved

  • One standard system adapted by settings rather than custom code
  • Users built their own lists and simple reports
  • Data loads without writing a program

What still hurt

  • Everything lived in SAP GUI
  • Any new screen or logic meant an ABAP request
  • Results were lists, not apps

Did you know? SAP Query from the R/3 days still runs in SAP S/4HANA. If you have built a QuickViewer report, you were doing low-code years before the word existed.

Step 2 · The NetWeaver years

Rules, workflows and screens you model

SAP NetWeaver brought tools where you draw or fill in a model and the system generates the rest: Visual Composer for portal screens, BRF+ for business rules, the Workflow Builder for approvals. In December 2012 SAP Screen Personas let teams redesign SAP GUI screens without touching the transaction’s code.

Tools of the time

  • Visual Composer
  • BRF+ (BRFPLUS)
  • Workflow Builder (SWDD)
  • Transaction variants (SHD0)
  • SAP Screen Personas

What it solved

  • Business rules kept in decision tables, not in code
  • Simpler screens on top of complex transactions
  • Approval workflows drawn as steps

What still hurt

  • Each tool was its own island
  • Mostly IT used them, rarely the business
  • Built for desktop and portal, not for mobile

Did you know? The first SAP Screen Personas ran in the browser on Microsoft Silverlight, so screens could change without an SAP GUI upgrade.

Step 3 · SAP S/4HANA and the cloud platform

Extend without modifying

SAP S/4HANA 1511 and 1610 brought key user extensibility: Fiori apps to add custom fields, logic, business objects and reports without modifying SAP code. Fiori elements generated screens from annotations, and SAP Intelligent RPA (2018) put software bots on the desktop.

Tools of the time

  • Custom Fields and Logic
  • Custom Analytical Queries
  • Custom Business Objects
  • SAP Fiori elements
  • SAP Web IDE
  • SAP Intelligent RPA

What it solved

  • Extensions survive upgrades because SAP’s code is untouched
  • Mobile-ready screens with little code
  • Repetitive clicks handed to bots

What still hurt

  • Tools still aimed at developers, or key users with IT help
  • No drag-and-drop app builder for business people
  • Workflow, bots and apps were separate products

Did you know? The word “low-code” arrived in this period: the analyst firm Forrester is credited with coining it in 2014.

Step 4 · SAP Build is born

One family for builders

In February 2021 SAP bought AppGyver, a no-code platform from Helsinki. A year later SAP Process Automation joined workflow and bots in one service. On 16 November 2022 SAP launched SAP Build: Apps, Process Automation and Work Zone under one name. In November 2023 SAP Build Code added pro-code with AI.

Tools of the time

  • SAP AppGyver
  • SAP Process Automation
  • SAP Build Apps
  • SAP Build Process Automation
  • SAP Build Work Zone
  • SAP Build Code

What it solved

  • A real drag-and-drop builder for business users
  • One entry point and shared content for apps, workflows and sites
  • Low-code and pro-code on the same platform

What still hurt

  • Connecting to S/4HANA still meant OData and destinations
  • Licensing through SAP BTP confused many customers
  • Governance was left to each company

Did you know? At the SAP Build launch SAP promised to train two million developers by 2025, partly through a Coursera certificate needing no degree or prior experience.

Step 5 · Joule and agents

Describe it, then refine it

Joule for developers (March 2025) drafts processes, forms, rules and code from plain language. Joule Studio builds Joule skills (generally available July 2025) and AI agents (December 2025). In May 2026 SAP announced Joule Studio as a fully managed offering, with an embedded n8n to orchestrate agents visually.

Tools of the time

  • Joule for developers
  • Joule Studio
  • SAP Build MCP servers
  • SAP Build Apps
  • ABAP Cloud

What it solved

  • A first version from a sentence
  • Agents that plan and act across SAP and non-SAP systems
  • Code assistants such as Cursor and Claude Code working on SAP Build projects

Still open

  • Who governs hundreds of agents and apps?
  • Checking what the AI produced is still a human job
  • Consumption costs need watching

Did you know? Through the end of 2026 SAP offers customers and partners free design-time access to Joule Studio, within fair-use limits.

  • Green still in use
  • Gold new in this step
  • Grey dashed replaced or renamed
  • Blue pro-code alongside

Milestones

  1. Dec 2012SAP Screen PersonasRedesign SAP GUI screens without changing the transaction.
  2. 2014“Low-code” gets a nameForrester is credited with coining the term.
  3. 2015–2016Key user extensibilitySAP S/4HANA 1511 and 1610 add custom fields, logic and objects.
  4. 2018SAP Intelligent RPASoftware bots for repetitive SAP tasks.
  5. Feb 2021SAP buys AppGyverA Helsinki no-code company founded in 2010, with 18 employees.
  6. Feb 2022SAP Process AutomationWorkflow and bots in one low-code service.
  7. Nov 2022SAP Build launchedApps, Process Automation and Work Zone, announced at SAP TechEd.
  8. Nov 2023SAP Build CodePro-code for Java and JavaScript, with Joule.
  9. Mar 2025Joule for developersSAP reports more than 17,000 SAP Build customers.
  10. Jul 2025Joule Studio skillsThe skill builder becomes generally available.
  11. Nov 2025MCP servers for SAP BuildCursor, Claude Code and other assistants can work on SAP Build; agent builder follows in December.
  12. May 2026Managed Joule StudioAnnounced at SAP Sapphire, with an embedded n8n.

The AppGyver story

From a Helsinki start-up to SAP Build Apps

SAP did not build its no-code app builder: it bought one. The story explains why SAP Build Apps feels different from the rest of SAP.

  1. 2010AppGyver is founded in Helsinki

    A small Finnish company builds a platform to create web and mobile apps without coding.

  2. 2010sA no-code builder aimed at business users

    Screens are dragged together, logic is drawn as flows and formulas look like spreadsheet functions.

  3. February 2021SAP buys AppGyver

    Eighteen people join SAP, and SAP announces the product will become part of SAP Business Technology Platform.

  4. 2021 to 2022SAP AppGyver on SAP BTP

    The builder moves onto SAP’s cloud platform, with SAP login, connectivity and support.

  5. 16 November 2022Renamed SAP Build Apps

    At SAP TechEd it becomes one of the three pillars of SAP Build, beside Process Automation and Work Zone.

What building in SAP Build Apps feels like

  • UI canvas

    Drag buttons, inputs, lists and images onto the page. Properties are set in panels, not in code.

  • Logic flows

    Each component has events. You connect them to action nodes: when tapped, check, call, navigate, show a message.

  • Formulas

    Where a value must be calculated, a formula editor with spreadsheet-like functions does the job. This is where no-code turns low-code.

  • Data

    Apps read and write SAP and non-SAP data through BTP destinations and APIs, or keep their own data with visual cloud functions.

Not SAPUI5 inside. Because it came from AppGyver, SAP Build Apps uses its own components rather than SAPUI5, so its apps do not automatically look like SAP Fiori. When an app must follow Fiori to the letter, developers reach for SAP Fiori elements or SAP Build Code instead.

SAP Build

Inside SAP Build: one roof, three kinds of builder

SAP Build puts low-code, AI and pro-code tools behind one entry point, on one platform, connected to the same SAP systems.

SAP Build LobbyOne entry point: templates, the SAP Build Store, every project in one list
  • Low-code and no-code
    • SAP Build AppsWeb and mobile apps by drag and drop
    • SAP Build Process AutomationWorkflows, forms, approvals, decisions, bots
    • SAP Build Work ZoneBusiness sites and the launchpad in the cloud
  • AI and agents
    • Joule StudioJoule skills for simple tasks, Joule agents that plan and act
    • Joule for developersDrafts processes, forms, rules and code from plain language
  • Pro-code
    • SAP Build CodeJava and JavaScript apps with CAP, helped by Joule
    • ABAP CloudOn the SAP BTP ABAP environment or inside SAP S/4HANA
SAP Business Technology PlatformLogin and roles · destinations · SAP Cloud Connector · transports · monitoring
  • SAP S/4HANA, cloud or on premise
  • SAP ECC
  • SuccessFactors, Ariba, Concur
  • Non-SAP systems through APIs

SAP lists SAP Build as part of SAP Business Suite and offers a 30-day basic trial. What a company may use depends on its SAP BTP entitlements.

Toolbox

The SAP low-code and no-code toolbox

SAP Build is the headline, but SAP’s LCNC list is longer: tools inside S/4HANA and ECC, analytics, integration, and the classics many people forget. Filter by level or by where the tool runs.

  • SAP Build Apps

    No-code · low-code

    Formerly SAP AppGyver

    Web and mobile apps built by drag and drop, with visual logic flows and spreadsheet-like formulas, reading and writing SAP and non-SAP data.

    SAP BTPBusiness users

  • SAP Build Process Automation

    Low-code · no-code

    Formerly SAP Process Automation (SAP Workflow Management and SAP Intelligent RPA)

    Workflows, forms, approvals, decision tables, bots and document extraction, with more than 400 SAP-delivered content packages, bots and connectors.

    SAP BTPBusiness users, key users

  • SAP Build Work Zone

    No-code

    Formerly SAP Launchpad service (standard edition) and SAP Work Zone (advanced edition)

    Business sites and the launchpad in the cloud: apps, processes, content and news for a team or the whole company on one page.

    SAP BTPBusiness users, IT

  • Joule Studio

    Low-code · AI

    Builds Joule skills for rule-based tasks and Joule agents that plan and act, grounded in SAP data. Announced as a fully managed offering in May 2026.

    SAP BTPKey users, developers

  • SAP Analytics Cloud

    No-code

    Stories, dashboards and planning models built by business users on live or imported data.

    SAP cloudControllers, analysts

  • Custom Analytical Queries

    No-code

    Reports built from released CDS views by dragging fields into rows and columns, published to the launchpad.

    SAP S/4HANAKey users

  • Adapt UI

    No-code

    Moves, hides and groups fields in a Fiori app for everyone or for a role, from the user menu of the app itself.

    SAP S/4HANA (Fiori)Key users

  • Custom Fields and Custom Logic

    Low-code

    New fields published to screens, reports and APIs, and checks or defaults written in a restricted, web-based ABAP editor.

    SAP S/4HANAKey users with IT

  • Custom CDS Views

    Low-code

    Combine released views into new data sources for reports and APIs, without ABAP development tools.

    SAP S/4HANAKey users with IT

  • Custom Business Objects

    Low-code

    Define a new object and its fields; SAP can generate the tables, an OData service and a simple Fiori screen.

    SAP S/4HANAKey users with IT

  • SAP Screen Personas

    No-code · scripting

    Simplifies SAP GUI transactions: hide fields, merge tabs, add buttons, with optional scripts for more.

    SAP GUI (ECC and S/4HANA)Key users, IT

  • SAP Query and QuickViewer

    No-code

    Join tables and build lists without ABAP in SQ01 and SQVI. Decades old and still alive.

    ECC and S/4HANAPower users

  • BRF+

    Low-code

    Business rules in decision tables and expressions. S/4HANA output management uses it to decide which output goes where.

    ECC and S/4HANAKey users, consultants

  • LSMW

    Low-code

    Legacy System Migration Workbench: data loads from recordings and mappings. In S/4HANA, SAP points new migrations to the Migration Cockpit.

    ECCConsultants

  • SAP Integration Suite

    Low-code

    Integration flows drawn graphically, with prebuilt packages for SAP and non-SAP systems.

    SAP BTPIntegration developers

  • SAP Mobile Development Kit

    Low-code

    Native mobile apps described in metadata rather than coded, often used for offline field work.

    SAP BTPDevelopers

  • SAP Fiori elements

    Low-code for developers

    Formerly Smart templates

    Fiori screens generated from annotations on the data model: list reports, object pages, overview pages.

    S/4HANA or SAP BTPDevelopers

  • SAP Build Code

    Pro-code · AI

    Java and JavaScript applications with CAP, Fiori and mobile templates, helped by Joule to generate models, logic and tests.

    SAP BTPDevelopers

  • ABAP Cloud

    Pro-code

    The upgrade-safe way to write ABAP, using only released APIs, on the BTP ABAP environment or inside SAP S/4HANA.

    S/4HANA or SAP BTP ABAP environmentABAP developers

Citizen developer: the colleague who builds

A citizen developer is someone outside IT who builds applications for themselves or their colleagues, with tools IT has approved. The analyst firm Gartner made the term popular in the early 2010s, describing business users who create new applications outside the scope of enterprise IT, and predicting they would soon build at least a quarter of new business applications.

Gartner now speaks more broadly of business technologists, and forecast that by 2026 at least 80% of the people using low-code tools would work outside formal IT departments.

In SAP projects the role already has a familiar name: the key user. The controller who builds her own analytical queries, the accounts payable lead who designs the approval flow, the planner who wants a phone app for the warehouse. SAP Build gives these people the tools; IT gives them the guardrails.

The fusion team: who does what

  1. 1 · Business expert

    Knows the process

    Describes the need, the rules and the exceptions, and tests the result.

  2. 2 · Citizen developer

    Builds with SAP Build

    Screens, forms, workflows and simple automations, inside the guardrails.

  3. 3 · Professional developer

    Builds what is hard

    APIs, complex logic, integrations and performance, in SAP Build Code or ABAP.

  4. 4 · IT and Center of Excellence

    Keeps it safe

    Licences, roles, data access, transports, a catalogue of what exists, and training.

What should a citizen developer build alone?

A simple traffic light many companies adopt in some form. The colour depends on risk, not on how clever the builder is.

  • Green: build it yourself

    • A report for you or your team: a Custom Analytical Query or an SAC story
    • A form that collects requests and routes them for approval
    • A team site with links, news and KPIs
    • A simple app that reads data and shows it on a phone

  • Amber: build it with an IT review

    • Anything that writes to SAP, even through standard APIs
    • Apps used by several departments or countries
    • Bots that run unattended
    • Anything handling personal or salary data

  • Red: leave it to developers

    • Postings that bypass SAP’s standard checks
    • High-volume or batch processing
    • Legal and tax logic, such as e-invoicing
    • Changes to SAP’s own code or tables

Pros and cons

Advantages, and what to watch

Low-code is not free speed. It moves effort from writing code to governing what gets built.

Why companies adopt it

  • Speed. A first working version in days, often shown to users in the first workshop.
  • Built by the people who know the process. Fewer specifications lost in translation between business and IT.
  • A shorter IT queue. Small requests stop waiting behind large projects.
  • A clean core. Extensions live beside SAP or in released extension points, so upgrades stay simple.
  • Prebuilt content. SAP Build Process Automation alone offers more than 400 SAP-delivered packages, bots and connectors.
  • Web and mobile from one tool. The same app can run in the browser and on phones.

What to watch

  • Licences and consumption. SAP Build runs on SAP BTP. Check entitlements and usage before the tenth app, not after.
  • App sprawl. Easy to build means easy to duplicate. Without a catalogue, three teams build the same thing.
  • Orphan apps. When the builder changes jobs, who maintains the app? Name an owner and a backup.
  • A ceiling. Complex logic, high volumes and unusual screens push the tools beyond what they were made for.
  • Lock-in. Apps live inside the platform that built them; moving them usually means rebuilding.
  • Training still matters. No code is not no skill: data models, APIs and testing still have to be learned.

For key users

For key users: six things you could build next month

Good first projects are small, frequent and annoying today: a spreadsheet passed around by e-mail, an approval chased by phone, a report rebuilt every month.

  • Finance

    Supplier change request

    A form for new payment terms, an approval by the right manager, then the change made in SAP. A classic first project.

    Tool: SAP Build Process Automation

  • Controlling

    Your own margin report

    Pick fields from a released CDS view, drag them into rows and columns, publish to your launchpad. No ABAP, no transport request.

    Tool: Custom Analytical Queries

  • Plant

    A shop-floor checklist on a phone

    Equipment checks or stock counts entered on a phone, with photos, sent straight to SAP.

    Tool: SAP Build Apps

  • People

    Onboarding that runs itself

    One request starts tasks for IT, facilities and the manager, with reminders until each is done.

    Tool: SAP Build Process Automation

  • Month-end

    A close cockpit for the finance team

    One site with the close calendar, links to the right apps, KPIs and announcements.

    Tool: SAP Build Work Zone

  • Everyone

    Hide the fields nobody uses

    Rearrange or hide fields in a Fiori app for your role, or simplify an SAP GUI screen.

    Tool: Adapt UI, SAP Screen Personas

Before you build: five questions

  1. Is there already a standard SAP app, or a template in the SAP Build Store?
  2. Which SAP data does it read or change, and who granted access?
  3. Who owns it after go-live, and who is the backup?
  4. How many people will use it, and in how many countries?
  5. How will you know it worked: minutes saved, errors avoided?

For consultants

For consultants: plumbing, governance and things few people know

Most low-code projects stumble on access, connectivity and governance, not on the drag-and-drop. These are the places, transactions and facts that matter.

Where or transactionWhat it is forKind
SAP BTP cockpitSubaccounts, entitlements and role collections. Decides who can use SAP Build, which services are entitled and how much quota is left.Admin
SAP Build LobbyThe single entry point. Create projects from templates, open the SAP Build Store and find every app, process and site.Web
DestinationsNamed connections on SAP BTP. URL and authentication for an S/4HANA, ECC or REST system, reused by apps and processes.Config
SAP Cloud ConnectorThe tunnel to on premise. Lets SAP BTP reach on-premise S/4HANA or ECC without opening the firewall to the internet.Config
api.sap.comSAP Business Accelerator Hub. The catalogue of released SAP APIs and events, with sandbox calls. Look here before building a custom service.Web
/IWFND/MAINT_SERVICEActivate OData services. Registers gateway services on the back end so low-code apps can read and write.SAP GUI
SEGWGateway Service Builder. The classic way to build a custom OData service when no released API fits. Pro-code territory.SAP GUI
Custom Fields · Custom LogicKey user extensibility apps. Add fields to business contexts and publish them to screens, reports and APIs, with checks and defaults.Fiori
Cloud Transport ManagementMove content between landscapes. Transports SAP Build content from development to test to production subaccounts.Admin
Desktop AgentRuns the bots. The SAP Build Process Automation component installed on Windows machines to run attended and unattended automations.Config
BRFPLUSBusiness rules workbench. Decision tables and rules; S/4HANA output management uses BRF+ for output determination.SAP GUI
SHD0Transaction variants. Hide fields, set defaults or skip screens in a transaction without code.SAP GUI
SQVI · SQ01QuickViewer and SAP Query. Join tables and build lists without ABAP; still available in S/4HANA.SAP GUI
  • Connectivity

    ECC can join in too

    SAP Build reaches on-premise systems, ECC included, through SAP Cloud Connector and a BTP destination. Expose the data as OData services or standard APIs, and most of the work is done.

  • Clean core

    Sell low-code as a clean-core tool

    Side-by-side apps on SAP BTP and key user extensions do not modify SAP code, so they do not block the next upgrade. That argument often unlocks the budget.

  • Licensing

    Check entitlements before the demo

    SAP Build is licensed through SAP BTP, and SAP lists it as part of SAP Business Suite. Look at the BTP cockpit first, and use the 30-day trial for demos.

  • UX

    SAP Build Apps is not SAPUI5

    Its apps use their own component library. When the customer insists on strict Fiori, choose Fiori elements or SAP Build Code and say so early.

  • Governance

    Set up roles and transports on day one

    Decide in the BTP cockpit who may create projects, keep separate subaccounts for development and production, and move content with Cloud Transport Management.

  • AI

    Joule writes the first draft

    In SAP Build Process Automation Joule generates processes, decisions and forms from plain language; in SAP Build Code it generates data models, logic and tests. Review everything it writes.

  • Agents

    Skills first, then agents

    Joule Studio separates skills, for rule-based tasks with fixed inputs and outputs, from agents that plan and use tools. Most customers should start with skills.

  • Dev tools

    Your code assistant can work on SAP Build

    Since SAP TechEd 2025, local MCP servers for SAP Build let Cursor, Windsurf, Claude Code, Cline and OpenAI Codex work on SAP Build projects.

  • Sapphire 2026

    Joule Studio, now fully managed

    Announced in May 2026: a managed runtime for agents, an embedded SAP-managed n8n for multi-agent flows, and extension in VS Code or Cursor.

  • Rules

    BRF+ is the forgotten low-code engine

    Decision tables maintained by key users have run inside ECC and S/4HANA for years. Before building rules in a new tool, check whether BRF+ already holds them.

Clean core in one picture: where an extension can live

Low-code is one of SAP’s main arguments for a clean core: extensions sit in released extension points or beside SAP, not inside SAP’s own code.

  • Inside SAP S/4HANAKey user extensibilityCustom fields, logic, CDS views, queries and business objects, through released extension points.
  • Inside, for developersABAP CloudDeveloper extensions on the same stack, using only released APIs.
  • Beside SAPSide-by-side on SAP BTPSAP Build apps, processes, agents and SAP Build Code, talking to SAP through APIs and events.

Quiz

Myth or fact?

Nine things people say about low-code in SAP. Test yourself.

  1. No-code means IT is not involved at all.

    Right.Not quite. Myth. IT still sets up access, data connections, security and transports. The builder just does not write code.

  2. SAP Build Apps was born inside SAP.

    Right.Not quite. Myth. It began as AppGyver, a Helsinki company founded in 2010 and bought by SAP in February 2021.

  3. SAP had low-code tools long before the word existed.

    Right.Not quite. Fact. SAP Query, QuickViewer, Report Painter, LSMW, Visual Composer and BRF+ all let people build without ABAP.

  4. Low-code will make ABAP developers obsolete.

    Right.Not quite. Myth. SAP Build itself includes pro-code: SAP Build Code and ABAP Cloud. Complex logic and APIs still need developers.

  5. SAP Build only works with SAP S/4HANA.

    Right.Not quite. Myth. It reaches ECC and non-SAP systems through SAP Cloud Connector, destinations and APIs.

  6. A no-code app can update data in SAP.

    Right.Not quite. Fact. Through standard APIs or OData services, with the user’s SAP authorizations still applied.

  7. SAP Build is free.

    Right.Not quite. Myth. There is a 30-day trial. Productive use is licensed through SAP BTP or included in SAP Business Suite.

  8. SAP coined the term “citizen developer”.

    Right.Not quite. Myth. The analyst firm Gartner made it popular in the early 2010s.

  9. Adding a field with the S/4HANA Custom Fields app is a form of low-code.

    Right.Not quite. Fact. Key user extensibility is SAP’s low-code inside S/4HANA, with no change to SAP’s own code.

Pick Fact or Myth on each card.Your score: right out of answered, 9 statements in all.

Frequently asked questions

What is the difference between no-code, low-code and pro-code?

No-code means you only configure ready-made blocks. Low-code adds formulas, rules or small scripts to those blocks. Pro-code is programming by developers. In SAP, SAP Build Apps and SAP Build Work Zone lean towards no-code, SAP Build Process Automation and Joule Studio towards low-code, and SAP Build Code and ABAP Cloud are pro-code.

What is SAP Build?

SAP’s family of tools for building apps, automations, business sites and AI agents, launched at SAP TechEd in November 2022 and running on SAP BTP. The low-code side is SAP Build Apps, SAP Build Process Automation and SAP Build Work Zone; the pro-code side is SAP Build Code and ABAP Cloud; Joule Studio covers AI agents. SAP Build Lobby is the shared entry point.

What happened to AppGyver?

SAP bought the Helsinki company in February 2021. Its product became SAP AppGyver on SAP BTP and, on 16 November 2022, SAP Build Apps. The AppGyver name is gone; new projects start in SAP Build Apps.

Is SAP Build free?

Not for productive use. SAP offers a 30-day basic trial. Beyond that, SAP Build is licensed through SAP BTP, and SAP lists it as part of SAP Business Suite, so check your entitlements in the SAP BTP cockpit before buying anything. For Joule Studio, SAP offers free design-time access through the end of 2026, within fair-use limits.

Do I need to know how to code?

Not for simple apps, forms and workflows. As an app grows you will meet formulas similar to spreadsheet functions, data models and API connections. That is the point where a consultant or the IT team usually joins in.

Does SAP Build work with SAP ECC, or only with S/4HANA?

Both, and with non-SAP systems. On-premise systems connect through SAP Cloud Connector and a BTP destination, using OData services or other APIs. SAP S/4HANA ships many more released APIs, so the work is usually easier there.

Will low-code replace SAP developers and consultants?

No. SAP Build itself puts pro-code beside low-code. Low-code takes small requests off the queue, so developers spend their time on integration, complex logic and the APIs that low-code apps depend on. Consultants who understand both the business process and the platform are the ones projects look for.

What is a citizen developer in SAP?

Someone outside IT who builds apps or automations with tools IT has approved. In SAP projects this is usually a key user: a controller, a buyer, an HR analyst or a planner who knows the process well.

Is low-code secure?

SAP BTP handles login and roles, and SAP authorizations still apply when an app reads or writes SAP data. The real risks are organisational: who may build, which data may be used, and who reviews an app before it goes live.

What is the difference between SAP Build Apps and SAP Fiori?

SAP Fiori is SAP’s design system and the apps SAP ships with it, built on SAPUI5. SAP Build Apps uses its own components, so its apps do not automatically look like Fiori. For a Fiori-standard app with little code, developers use SAP Fiori elements.

Where does key user extensibility fit?

It is SAP’s low-code inside SAP S/4HANA: Custom Fields, Custom Logic, Custom CDS Views, Custom Analytical Queries and Custom Business Objects. Changes stay within released extension points, which keeps the core clean and upgrades simple.

I am a consultant. What should I learn first?

SAP BTP basics first: subaccounts, entitlements, destinations and SAP Cloud Connector. Then SAP Build Process Automation and SAP Build Apps on a trial, and the APIs of your own module on the SAP Business Accelerator Hub. Add Joule Studio once the process side feels familiar.

References

Checked in November 2026.