SAP Build covers four tools: Build Apps, Process Automation, Work Zone and Build Code. Here is what each does, who uses it and how they fit together.
AI makes consequential decisions. This post explains responsible AI — fairness, bias, transparency, accountability and what EU AI Act means for organisations.
OData is the protocol that connects SAP Fiori apps to SAP backends, powers the API layer of S/4HANA, and is used in every BTP integration. Yet most people only know it as a URL pattern. This post explains what OData actually is, how it works, the real differences between V2 and V4, and when to use each — clearly and without assuming deep technical knowledge.
Systems that wait to be asked are request-driven. Systems that react to what happens are event-driven. This post explains event-driven architecture — events vs commands vs queries, pub/sub patterns, event brokers like Kafka and SAP Event Mesh, and when this approach makes sense versus when it does not.
SAP Integration Suite is SAP’s iPaaS on BTP — the strategic replacement for PI/PO. This post explains what it is, how its capabilities work, and how they fit together.
CI/CD is how modern software ships reliably. This post explains continuous integration, delivery and deployment — the pipeline, the distinctions and why the process matters.
ABAP is not a legacy relic. It is the language at the heart of every SAP system. This post covers the ABAP fundamentals every SAP professional needs — from data types and internal tables to CDS views, Clean Core, and RAP.
New to SAP BTP? This guide covers the account hierarchy, the five key service areas, Integration Suite, SAP Build, and what to actually do when you first get access.
Microservices architecture breaks applications into independent services. This post explains what that means, the real trade-offs, and when switching actually makes sense.
No articles match your search.