SAP FIORI RESOURCE HUB · 2026
SAP BTP Tutorial: Getting Started Guide for US Developers (2026)
If you're a developer and you've been told "we're moving to BTP," this guide gets you from a blank trial account to a real, deployed app not just a conceptual overview. If you're still figuring out what SAP BTP actually is before you commit to building on it, start with our SAP BTP overview first, then come back here when you're ready to get hands-on.
$ cf login
Target: SAP BTP Trial ✓
$ cf push my-first-app
Deploying... 3/3 instances running
$
TABLE OF CONTENTS
- What You Actually Need Before You Touch BTP
- Your First 10 Minutes on BTP — Getting the Trial Running
- Neo or Cloud Foundry? The Decision That Locks In Your Whole Setup
- Subaccounts, Entitlements, Spaces — The Part That Actually Confuses Everyone
- Ship Your First App — A Real, Working Example
- The Services You’ll Reach for Constantly
- Connecting BTP to S/4HANA Without Breaking Your Next Upgrade
- Mistakes That Cost Beginners Days (Not Minutes)
- CLI, Business Application Studio, or Your Own IDE? Setting Up How You’ll Actually Work
- You’ve Got BTP Running — Here’s What Actually Comes Next
- FAQs
- Related Resources
What you actually need before you touch BTP
An SAP account ree to create if you don't already have one; you'll need it to sign up for the trial.
Basic comfort with Java or Node.js you don't need to be an expert in either, but if you've never written a line of code in one, expect this guide's later steps to take longer than the estimated time.
General cloud familiarity helps but isn’t required. If you’ve used AWS, Azure, or Google Cloud before, BTP’s concepts (accounts, subaccounts, spaces) will feel familiar quickly. If this is your first cloud platform, that’s fine too — just budget extra time for Section 4 below.
You do not need ABAP knowledge to get started with BTP. That’s a common assumption, and it’s wrong for most BTP development — ABAP matters more if you’re extending S/4HANA specifically using RAP, which is a separate (later) skill, not a prerequisite for this guide.
What you don’t need, despite what some older guides suggest:
- SAP Basis experience — BTP’s cloud-native setup is deliberately more self-service than classic on-premise administration; you won’t be touching transport requests or kernel patches to get started.
- A paid SAP license to begin — the trial account is genuinely sufficient for learning and prototyping; a production license only becomes relevant once you’re deploying something real for actual users.
- Deep prior SAP ecosystem knowledge — plenty of developers coming from a general web or cloud background pick up BTP’s core concepts within a day or two of hands-on use, without years of SAP-specific tribal knowledge.
How To Schema
Your first 10 minutes on BTP — getting the trial running
Go to the BTP trial signup page
Go to the current Fiori Apps Library address and open it in a supported modern browser.
Choose your region
Some functions or SAP resources may require an SAP Universal ID or additional authentication. If basic catalog browsing is available without authentication, you can begin your research immediately.
Confirm what's included
Go to the current Fiori Apps Library address in a supported modern browser.
Neo or Cloud Foundry? The Decision That Locks In Your Whole Setup
|
Aspect
|
Neo
|
Cloud Foundry
|
|---|---|---|
|
Hosting
|
SAP's own data centers
|
Multi-cloud (AWS, Azure, GCP)
|
|
Interface
|
Legacy catalog experience
|
Modernized interface
|
|
Search
|
Catalog-based browsing
|
Updated search and filtering
|
|
Filtering
|
More limited
|
Broader filtering capabilities
|
|
Best use
|
Older references
|
Current app discovery
|
Subaccounts, Entitlements, Spaces — The Part That Actually Confuses Everyone
The structure, visually:
How To Schema
Ship Your First App — A Real, Working Example
Open Business Application Studio
Or use the CLI locally if you prefer your own IDE.
Create a minimal app from a template
Start with a basic Node.js or Java template, not a blank project.
Confirm what's included
Go to the current Fiori Apps Library address in a supported modern browser.
The Services You'll Reach for Constantly
Integration Suite
Connecting BTP to S/4HANA and outside systems.
Extension Suite
Building side-by-side extensions and custom apps.
Fact sheet
Show detailed information about an object — a customer, material, or document — and its related data.
Connecting BTP to S/4HANA Without Breaking Your Next Upgrade
Side-by-side extensibility keeps custom logic outside the S/4HANA core, following clean-core principles — the same approach we use when building custom Fiori apps.
Side-by-side extensibility keeps custom logic outside the S/4HANA core, following clean-core principles — the same approach we use when building custom Fiori apps.
Mistakes That Cost Beginners Days (Not Minutes)
Wrong environment choice
Starting in Neo, then rebuilding everything in Cloud Foundry later.
Wrong environment choice
Starting in Neo, then rebuilding everything in Cloud Foundry later.
Wrong environment choice
Starting in Neo, then rebuilding everything in Cloud Foundry later.
The Services You'll Reach for Constantly
Recommended
Business Application Studio
CLI (cf, btp)
Local IDE + Extensions
You've Got BTP Running — Here's What Actually Comes Next
Thinking about formalizing your skills with a certification?
14. Frequently Asked Questions
Is SAP Fiori free?
Fiori is not generally purchased as one standalone product. Many Fiori applications are delivered with the relevant SAP solution, but licensing can depend on the specific application, product, deployment model, and underlying capabilities. Verify the licensing position for your specific scenario.
What's the difference between SAP Fiori and the Fiori Launchpad?
Fiori is SAP’s broader user experience and design system, while the Fiori Launchpad is the role-based application shell and entry point through which users access applications and navigation. Fiori describes the broader experience; the Launchpad provides the environment through which that experience is accessed.
Is SAP Fiori the same as SAPUI5?
No. SAPUI5 is SAP’s web UI development framework used to build many Fiori applications. Fiori is the broader design and user experience system, while SAPUI5 is one of the core technologies used to implement that experience.
Do I need SAP Fiori for S/4HANA?
S/4HANA can support classic SAP GUI-based applications for certain functions, but Fiori is the primary modern user experience for many S/4HANA business processes and is the standard user experience in many S/4HANA Cloud scenarios. The exact application experience depends on the S/4HANA edition and release.
Can I customize SAP Fiori apps?
Yes. Depending on the application and SAP environment, organizations can use in-app extensibility, developer extensibility, or side-by-side extensibility to adapt or extend functionality. Custom applications can also be developed using technologies such as SAPUI5 and Fiori elements when standard applications do not meet the business requirement.
Does SAP Fiori replace SAP GUI completely?
Not entirely. Fiori provides modern application experiences for many business processes, but classic SAP GUI remains relevant for various back-office, technical, and configuration activities. SAP environments can therefore use Fiori and SAP GUI alongside each other.
How long does it take to roll out SAP Fiori?
There is no single timeline. A limited rollout using a small number of standard applications can be relatively straightforward, while an enterprise-wide deployment involving authorization design, Launchpad configuration, integrations, testing, custom applications, change management, and training can take considerably longer. The scope and complexity of the SAP landscape determine the actual timeline.
More Questions?
We’re always ready to help you out.
RELATED RESOURCES
SAP BTP — Main Overview
BTP Certification Guide
Fiori Custom Development Guide
Building something more complex than a tutorial app?
Tell us what you're working on — we'll tell you exactly where to start.