SAP BTP Solution Architect Hackathon Curriculum
Overall Goal: Build technical and architectural capability to design intelligent enterprise solutions on SAP BTP across application development, automation, integration, data & analytics, AI, architecture methods, and cost estimation.
🧭 Program Snapshot
Item | Structure |
Duration | 20 Days |
Total Effort | 80 Hours |
Learning Style | Hackathon-style, hands-on, collaborative |
Primary Case Study | ACME Corporation |
Core Platform | SAP Business Technology Platform |
Main Outcome | Solution architecture capability with practical design artifacts |
🗺️ 20-Day Visual Roadmap
Week | Theme | Days | Main Focus |
Week 1 | 🏗️ Foundations & Platform Management | 1–5 | Enterprise architecture, BTP basics, accounts, cost, security, connectivity |
Week 2 | 🧩 Application Development & Automation | 6–10 | Clean Core, SAP Build, CAP, automation, runtime environments |
Week 3 | 📊 Data & Analytics Mastery | 11–14 | Data products, HANA Cloud, Datasphere, SAC, Business Data Cloud |
Week 4 | 🔗 Integration & AI-Powered Solutions | 15–20 | Integration Suite, API management, Event Mesh, ISA-M, Joule, AI Foundation |
✅ Participant Setup Checklist
Create or access an SAP BTP Trial Account
Open the SAP BTP Cockpit
Prepare a working notes page for daily artifacts
Maintain diagrams, assumptions, and decisions for each challenge
Use SAP BTP Discovery Center, Cost Estimator, solution diagrams, and icons where relevant
Collaborate, discuss constraints, and document trade-offs
Week 1 — 🏗️ Foundations & Core Platform Management
Week Goal: Understand SAP BTP as a strategic enterprise platform and learn how to structure accounts, security, cost, connectivity, and data persistence.
Day 1 — Understanding Enterprise Architecture & SAP BTP Value
Area | Details |
Learning Objectives | Evaluate the value of enterprise architecture; understand EA as a city-planner model; connect SAP BTP to strategic alignment, cost optimization, and risk reduction |
Key Concepts | Enterprise Architecture, Strategic Alignment, Technical Debt, SAP BTP as a strategic toolkit |
Challenge | Identify three ACME pain points caused by chaotic IT and propose how EA + SAP BTP can turn them into advantages |
Expected Outcome | Brief report on ACME’s IT challenges and the strategic value of EA and SAP BTP |
Day 2 — SAP BTP Basics & Account Model Setup
Area | Details |
Learning Objectives | Describe SAP BTP; understand Global Account, Directory, Subaccount, Region, services, plans, entitlements, quotas, environments, subscriptions, instances, and applications |
Key Concepts | PaaS, Multi-Cloud Strategy, Resource Hierarchy, Tenant Isolation |
Challenge | Design ACME’s BTP account model for global divisions, project stages, GDPR, and data residency |
Expected Outcome | Visual account model diagram with hierarchy, regions, and resource allocation logic |
Day 3 — Commercial Models & Cost Estimation
Area | Details |
Learning Objectives | Compare Trial, Consumption, Subscription, Always Free, and Free Tier; estimate SAP BTP service costs |
Key Concepts | CPEA, PAYG, Cloud Credits, SBOM |
Challenge | Estimate the monthly cost of a side-by-side extension using SAP Build Code, Cloud Foundry Runtime, and SAP HANA Cloud |
Expected Outcome | Documented estimate with model selection and future transition analysis |
Day 4 — Foundational Services: Security & Compliance
Area | Details |
Learning Objectives | Understand SAP Cloud Identity Services, IAS, IPS, platform users, business users, and compliance support |
Key Concepts | SSO, MFA, User Lifecycle Management, GDPR Compliance |
Challenge | Design ACME’s onboarding/offboarding access workflow using IAS and IPS |
Expected Outcome | Workflow diagram showing secure access, provisioning, de-provisioning, and compliance considerations |
Day 5 — Foundational Services: Connectivity & Persistency
Area | Details |
Learning Objectives | Understand SAP HANA Cloud, Object Store, PostgreSQL, Redis, Connectivity Service, and Destination Service |
Key Concepts | Cloud Connector, Data Residency, Secure Tunnel, Address Book for Applications |
Challenge | Connect a custom BTP app to on-premise S/4HANA and design structured + unstructured storage |
Expected Outcome | High-level solution diagram covering connectivity and persistence |
Week 2 — 🧩 Application Development & Automation
Week Goal: Learn how to extend SAP cleanly using SAP Build, CAP, automation, runtime environments, and deployment capabilities.
Day 6 — Clean Core, Extensibility Models & SAP Build Overview
Area | Details |
Learning Objectives | Understand Clean Core, S/4HANA extensibility, side-by-side, key-user, developer extensibility, and SAP Build |
Key Concepts | Upgrade Paralysis, TCO, Agility, Released APIs, ABAP Cloud |
Challenge | Choose the right extensibility model and Clean Core level for a custom Business Partner field and UI |
Expected Outcome | Extensibility recommendation with Clean Core justification |
Day 7 — Low-Code/No-Code Development with SAP Build Apps
Area | Details |
Learning Objectives | Describe SAP Build Apps, citizen development, visual development, UI components, and backend connections |
Key Concepts | Citizen Developer, Visual Development, SAP BTP Destinations |
Challenge | Prototype a mobile app for ACME’s New Vendor Onboarding process |
Expected Outcome | Functional or partial SAP Build Apps prototype |
Day 8 — Pro-Code Development with SAP Build Code
Area | Details |
Learning Objectives | Understand SAP Build Code, generative AI, CAP, RAP, SAPUI5, Fiori Elements, CI/CD, and ABAP ADT |
Key Concepts | GenAI for Code, CAP, RAP, ABAP Cloud |
Challenge | Design a CAP-based Partner Validation App backend |
Expected Outcome | High-level design document covering model, runtime, and AI-assisted development |
Day 9 — Process Automation with SAP Build Process Automation
Area | Details |
Learning Objectives | Understand workflows, RPA, intelligent document processing, fusion development, and process automation |
Key Concepts | BPM, RPA, Workflow, Fusion Development |
Challenge | Design an automated vendor onboarding workflow using RPA and API calls |
Expected Outcome | Workflow diagram showing automation steps and SAP Build components |
Day 10 — Runtime Environments & Advanced Application Capabilities
Area | Details |
Learning Objectives | Compare Cloud Foundry, Kyma, ABAP Environment, SAP CI/CD, Transport Management, and Work Zone |
Key Concepts | Microservices, Containers, ABAP Cloud, DevOps, Portals |
Challenge | Propose deployment pipeline and unified UX for the Partner Validation App |
Expected Outcome | Deployment and user-experience proposal |
Week 3 — 📊 Data & Analytics Mastery
Week Goal: Build the ability to design enterprise data architecture, analytics use cases, business data products, and advisory-methodology deliverables.
Day 11 — Data Terminology: Fabric, Mesh, Products
Area | Details |
Learning Objectives | Define Data Warehouse, Data Lake, Data Fabric, Business Data Fabric, Data Mesh, and Data Product |
Key Concepts | ETL, Object Storage, Data Silos, Semantic Layer, Data Autonomy |
Challenge | Identify three ACME data products for business domains |
Expected Outcome | Data product list with sources, metadata, consumers, and business value |
Day 12 — SAP HANA Cloud & SAP Datasphere
Area | Details |
Learning Objectives | Understand HANA Cloud, Datasphere, business data fabric, data integration, and master data governance |
Key Concepts | DBaaS, Multi-Model Database, Business Data Fabric, Data Virtualization, Semantic Modeling |
Challenge | Design ACME’s data architecture across S/4HANA, CRM, and legacy sales systems |
Expected Outcome | High-level architecture diagram showing Datasphere, HANA Cloud, and data flows |
Day 13 — SAP Analytics Cloud for Insights
Area | Details |
Learning Objectives | Understand SAC, BI, planning, predictive analytics, Smart Discovery, Smart Insights, Smart Predict, and Just Ask |
Key Concepts | Augmented Analytics, Stories, Predictive Modeling, NLP |
Challenge | Design an augmented analytics use case for regional sales performance |
Expected Outcome | Scenario showing how ACME’s sales team uses SAC smart features |
Day 14 — SAP Business Data Cloud & DAAM
Area | Details |
Learning Objectives | Understand SAP Business Data Cloud, SAP Databricks, BW integration, Knowledge Graph, governance, and DAAM phases |
Key Concepts | Business Data Cloud, Delta Sharing API, SAP Knowledge Graph, Data Governance |
Challenge | Apply DAAM Phase I and II to ACME’s data-driven transformation initiative |
Expected Outcome | Statement of Work, business outcome, use cases, and supporting data products |
Week 4 — 🔗 Integration & AI-Powered Solutions
Week Goal: Design modern integration, API, event-driven, advisory, Joule, and AI Foundation solutions for enterprise scenarios.
Day 15 — SAP Integration Strategy & Integration Suite
Area | Details |
Learning Objectives | Understand SAP’s integration strategy, Integration Suite, iPaaS, prebuilt content, governance, security, and scalability |
Key Concepts | iPaaS, Integration CoE, Citizen Integrator, Open Integration |
Challenge | Define ACME’s Integration Center of Excellence and Integration Suite strategy |
Expected Outcome | Strategic integration outline mapped to SAP’s five imperatives |
Day 16 — Cloud Integration & API Management
Area | Details |
Learning Objectives | Understand iFlows, message processing, QoS, API lifecycle, Open Connectors, and secure API exposure |
Key Concepts | iFlows, Adapters, QoS, API Security, Developer Hub, Unified API |
Challenge | Design data sync from on-premise S/4HANA to Salesforce and expose secure internal APIs |
Expected Outcome | Two integration designs: one iFlow and one API architecture |
Day 17 — Event-Driven Architecture with SAP Event Mesh
Area | Details |
Learning Objectives | Understand EDA, events, brokers, producers, consumers, queues, topics, and SAP Event Mesh |
Key Concepts | Events, Topics, Queues, Loose Coupling, Real-Time Responsiveness |
Challenge | Redesign vendor onboarding using S/4HANA events and SAP Event Mesh |
Expected Outcome | Event-driven solution diagram with producer, broker, event, and consumers |
Day 18 — SAP Integration Solution Advisory Methodology
Area | Details |
Learning Objectives | Understand ISA-M phases: Assess, Design, Define Best Practices, Enable Practice |
Key Concepts | Integration Domains, Integration Styles, Use Case Patterns, Deployment Models |
Challenge | Apply ISA-M Phase 1 to purchase-order integration scenarios |
Expected Outcome | ISA-M categorization and explanation of Integration Assessment usage |
Day 19 — SAP AI Strategy & Joule
Area | Details |
Learning Objectives | Understand SAP Business AI, Joule, Joule Agents, informational, navigational, transactional, and analytical interaction patterns |
Key Concepts | GenAI, Agentic AI, Copilot, Grounding, Tool Orchestration |
Challenge | Design procurement scenarios using Joule and Joule Agents |
Expected Outcome | Scenario with three Joule interactions and one proactive Joule Agent task |
Day 20 — AI Foundation & AI in BTP Services
Area | Details |
Learning Objectives | Understand AI Foundation, Unified AI Portal, Joule Studio, Generative AI Hub, Document AI, Knowledge Graph, HANA Vector Engine |
Key Concepts | RAG, Vector Embeddings, MLOps, AI-Driven Integration Flow Generation, Intelligent Document Processing |
Challenge | Design invoice automation and grounded company-policy Q&A for ACME |
Expected Outcome | Two-part AI solution design using SAP Document AI, Generative AI Hub, and HANA Cloud Vector Engine |
🧱 Artifact System
Use the same artifact pattern every day so the curriculum stays searchable and easy to maintain.
Artifact Type | Naming Rule | Example |
Daily Notes | Day##_Topic_Notes | Day03_Cost_Estimation_Notes |
Diagram | Day##_Topic_Diagram | Day05_Connectivity_Persistency_Diagram |
Challenge Output | Day##_Challenge_Output | Day12_Data_Architecture_Output |
Reflection | Day##_Reflection | Day19_Joule_Scenario_Reflection |
🧠 Learning Flow Per Day
flowchart LR A[Concept Brief] --> B[Architecture Discussion] B --> C[Hands-on Challenge] C --> D[Artifact Creation] D --> E[Peer Review] E --> F[Reflection]
🏁 Final Capstone
Capstone Challenge: Design an intelligent enterprise solution for ACME Corporation using SAP BTP services across architecture, development, integration, data, analytics, and AI.
Capstone Deliverables
SAP BTP account model
Solution architecture diagram
Cost estimate
Security and identity strategy
Connectivity and persistence design
Clean Core extensibility recommendation
Application development approach
Automation workflow
Data and analytics architecture
Integration and API strategy
Event-driven architecture
AI and Joule use-case design
Final architecture narrative
📂 Recommended Document Organization
Category | Rule |
Curriculum Master | Keep the full roadmap and day-wise structure here |
Daily Artifacts | Store all daily outputs using the naming convention above |
Architecture Diagrams | Keep diagrams separate for easy reuse |
Costing Files | Store estimates and SBOM documents together |
Capstone Package | Collect final deliverables in one folder or page section |
Visual Rule: Every day should produce one visible artifact — a diagram, table, workflow, estimate, prototype, or scenario map.