TalkTalkA recorded or written talk.See every one →SAP TechEd — session catalogue
Extending SAP Autonomous Suite
Extensibility across SAP Autonomous Suite: AI-enabled development in SAP Build solutions, the ABAP Cloud model among them, as the way extensions are designed, generated and deployed, and a direction for making extensions ready for agentic AI. The abstract names the suite, SAP Build and the ABAP Cloud model and no single feature, so the edges are to ExtensibilityExtensibilityLetting a customer change delivered behaviour without modifying it — key-user fields and logic, developer extensions, and the released extension points that make either safe across an upgrade.SAP and community, unassessed, the concern, and to SAP Build CodeSAP Build CodeSAP's development environment on BTP for SAPUI5, SAP Fiori, mobile and CAP applications that run on the SAP BTP, Cloud Foundry Runtime, in which Joule generates models, services, logic, tests and apps.sap official, btp, the SAP Build solution held here in which Joule generates and deploys development; which other SAP Build solutions the session shows is not stated. A TechEd 2026 session (Tuesday 27 October, Berlin), presented by Alexander Rother and Khaled MUSILHY, written here from SAP's abstract; the recording is not yet published.
Where it sits
Explains
ExtensibilityABAPExtensibilityLetting a customer change delivered behaviour without modifying it — key-user fields and logic, developer extensions, and the released extension points that make either safe across an upgrade.SAP Build CodeCAPUI5BTPSAP Build CodeSAP's development environment on BTP for SAPUI5, SAP Fiori, mobile and CAP applications that run on the [SAP BTP, Cloud Foundry Runtime](artifact:btp-cloud-foundry-runtime), in which Joule generates models, services, logic, tests and apps.
Properties
About this work
Published on
Group by12 of 12 pieces
Piece, what it offersStill applies
Enhancing Customer Master with a Custom Tab Using SAP TAXI Framework (BAdI + SE80)Enhancing Customer Master with a Custom Tab Using SAP TAXI Framework (BAdI + SE80)Walks through adding a custom "Repayment" tab to the Customer Master (XD01/XD02/XD03) using SAP's TAXI framework: an append structure on table KNB1, a subscreen built in SE80, and two BAdI implementations — CUSTOMER_ADD_DATA and CUSTOMER_ADD_DATA_CS — registered through SPRO. The BAdIs are the released extension points that keep the tab upgrade-safe without modifying standard code, the developer-extension half of the capability's tiered model.Divya_palem, published 2026-06-01
Extending Standard S/4 HANA OData API'sExtending Standard S/4 HANA OData API'sWalks through extending a standard S/4HANA OData API with a custom field, preferring OData V4 over V2 for its closer OASIS compliance and simpler service enablement, then tracing the extensibility objects documented for the entity before touching any code. The custom field reaches the API by layering three CDS view extensions — extendView on I_Product, extendViewEntity on R_ProductTP and on A_Product_3 — following the projection chain down to where the base table is first selected, built in ABAP Development Tools for Eclipse.JuanDK78, published 2026-04-08
Clean Core maturity and the new Extensibility LevelsClean Core maturity and the new Extensibility LevelsSets out SAP's Clean Core Level concept, the successor to the 3-Tier Development Model, which grades extensibility by how upgrade-safe it is rather than by where it runs: Level A covers on-stack extensions on released RAP and CDS views plus side-by-side apps on BTP, Level B covers upgrade-stable classic APIs listed in the Cloudification Repository, Level C covers internal-object use flagged through SAP's Changelog for SAP Objects, and Level D covers direct modifications and implicit enhancements that ABAP Test Cockpit checks must block. Choosing between an on-stack and a side-by-side implementation is left to the SAP Application Extension Methodology, and the official Level classifications are filed under SAP Note 3578329.EmilianoAyub, published 2025-12-19
S/4HANA公有云版的内部ABAP拓展S/4HANA公有云版的内部ABAP拓展Argues that S/4HANA Cloud public edition's in-app ABAP extensibility is still real ABAP development, just under stricter rules: developer extensions require ABAP Development Tools rather than SAP GUI transactions, data models are defined as CDS views instead of SE11 tables, business logic is a RAP behavior definition instead of a function module, and service exposure is an auto-generated OData service from a Service Definition instead of a hand-built RFC/BAPI. The piece walks a worked example — a Fiori app that triggers the Purchase Requisition API — through CDS, RAP, OData activation on SAP Gateway, and authorization via business catalogues, and frames the whitelist of released APIs and CDS views as upgrade-safety rather than a restriction.ArthurYang, published 2025-11-24
Clean Core清洁核心概况介绍Clean Core清洁核心概况介绍Explains Clean Core as SAP's architecture methodology for decoupling custom code from standard code, and walks through the A-D grading SAP uses for a single extension's cleanliness: D for direct modification of standard tables, programs, classes or functions, or disallowed patterns such as implicit enhancements; C for internally developed functions calling unreleased APIs; B for using only SAP's classic or released APIs (BAPI, ALV Grid, BAdI); A for side-by-side extensions reached only through released interfaces onto the SAP Build extension suite. It lays out a six-step roadmap for reaching Clean Core — inventorying existing extensions, setting a reduction target, surveying SAP's extension routes (SAP GUI SE80, Fiori custom fields and logic, BTP high/low-code, workflow/RPA), writing a decision tree, splitting new development from legacy migration, and reviewing periodically — while noting that in-app development is not inherently unclean and that real decisions should weigh ROI rather than follow the theory absolutely.ArthurYang, published 2025-11-10
Enhancing Standard BAPIs: When and How to Do ItEnhancing Standard BAPIs: When and How to Do ItWalks through why a standard BAPI needs enhancing — a missing field, an extra validation, logic before or after the call, or a performance tweak — and five ways ABAP offers to do it: a BAdI found in SE18/SE19, an append structure for extra fields, a classic user exit wired through SMOD/CMOD, a wrapper function module copied from the original, or an implicit enhancement when no other extension point exists. Each technique gets its own steps, and two carry a short ABAP code example.Shantalinga, published 2025-09-29
AI-first, API-first: What changes when AI becomes the userAI-first, API-first: What changes when AI becomes the userWhat changes in an architecture when an AI agent is the caller: AI-first and API-first principles, SAP's API governance, extensibility and the composable enterprise, with lessons the speaker draws from SAP's and other enterprise AI initiatives. The extensibility edge rests on the abstract naming extensibility as a principle and nothing more specific; no API, product or tool is named, so the talk is attached to the broadest concern it touches. A TechEd 2026 session (Wednesday 28 October, Berlin), presented by Tomasz Wilk, written here from SAP's abstract; the recording is not yet published.
Build agentic SAP extensions with Google CloudBuild agentic SAP extensions with Google CloudGoogle Cloud's architectures for agentic AI apps on SAP with a clean core: SAP Business AI Platform, SAP S/4HANA and SAP Business Data Cloud joined with BigQuery, Gemini and Google's Agent Development Kit. The abstract names zero-copy data agents, developer API workflows and ABAP extensions for AI integration, the last of which is the Extensibility concern; Business Data Cloud is the one atlas entry it names, and how any piece connects to another is not stated. A TechEd 2026 session (Wednesday 28 October, Berlin), presented by Ekaterina Kruse, Ian Moria and Stany Winkler, written here from SAP's abstract; the recording is not yet published.
The journey with clean core continues for SAP Cloud ERP PrivateThe journey with clean core continues for SAP Cloud ERP PrivateClean core in SAP S/4HANA Cloud Private Edition as it stands in 2026: what is new in extensibility, new capabilities in the dashboard for the RISE with SAP Methodology, how AI helps make custom code compliant with clean core, and new guidance on data, integration and clean core in relation to SAP's API policy. The edges are to Extensibility, the concern the session is about, and to ABAP Cloud readiness, the concern behind making custom code compliant; the abstract names no tool for either and the dashboard is not held here. A TechEd 2026 session (Wednesday 28 October, Berlin; also TM108V, virtual), presented by Markus Goebel and Olga Dolinskaja, written here from SAP's abstract; the recording is not yet published.
From intent to extension: Joule and the future of solution extensibilityFrom intent to extension: Joule and the future of solution extensibilityHow Joule turns natural-language intent into extensions across SAP Autonomous Suite: intent-based agent extensions, enriching the agents SAP delivers, packaging options for partners and what SAP calls a harmonised extensibility experience. The edges are to SAP Joule, which does the translating, and to Extensibility, the concern; the abstract names the directions and no feature that ships today. A TechEd 2026 session (Wednesday 28 October, Berlin), presented by Amitha Kamath, Oren Shatil and Richard Kuba, written here from SAP's abstract; the recording is not yet published.
Navigating the road map for SAP Cloud ERP: Today, next, and beyondNavigating the road map for SAP Cloud ERP: Today, next, and beyondSAP's near-term and long-term plans for SAP Cloud ERP by theme: embedded AI, process automation, lifecycle management and extensibility, with timelines and adoption paths toward what SAP calls the Autonomous Enterprise. SAP Cloud ERP has no artifact here, so the edges are to the two concerns the road map names, Extensibility and Process automation; the abstract names no product or feature under either, and whether its process automation is SAP Build Process Automation is not stated. A TechEd 2026 session (Tuesday 27 October, Berlin; also TM815V, virtual), presented by Lawrence Martin and Sasa Markovic, written here from SAP's abstract; the recording is not yet published.
What's next in extensibility for SAP Autonomous SuiteWhat's next in extensibility for SAP Autonomous SuiteAgent-driven extensibility across SAP Autonomous Suite as SAP sees it ahead: what is coming for making extensions ready for agentic AI and how SAP's assistants are meant to help with it. The edge is to Extensibility, the concern; the abstract names no assistant, no feature and no date. A TechEd 2026 session (Wednesday 28 October, Berlin), presented by Alexander Rother and Oren Shatil, written here from SAP's abstract; the recording is not yet published.
Details
Graph
Extensibilitycapability, core and community
SAP Build Codeartifact
SAP TechEd — session cataloguepublishing source
SAP TechEd — session cataloguebuild/teched
Source
Type
talk
Published on
Host
sap.com
Discovered via
First seen
History
- Entered the atlasDiscovered via SAP TechEd — session catalogue · build/teched.
For your agent
- Ref
content:teched-2026-st122- JSON
- /content/teched-2026-st122.json
- MCP
- Connecting an agent