BrowseABAP, RAP and ABAP Cloud
Everything in ABAP
12 of 656
Domain: 2
Signals
Content: Undated
More
Group by: Capability
EntryBySignalsLast activity
ODataSAP and community
Consume Remote Services in a Full-Stack CAP ApplicationConsume Remote Services in a Full-Stack CAP ApplicationExtending the Developer's Guide application with a remote S/4HANA service — connectivity, importing the Business Partner API, and running against it. SAP publishes this as four separate paths: mock server or real S/4HANA Cloud, times Cloud Foundry or Kyma. One entry covers all four, because the difference between them is which backend and which runtime, not what you learn.SAP
Serve your application over MCPCommunity only
Agentic CAP: Build MCP servers and enterprise AI agentsAgentic CAP: Build MCP servers and enterprise AI agentsCAP applications become AI agents over the Model Context Protocol and the Agent2Agent protocol, which is the serve your application over MCP concern, and SAP AI Core is the LLM integration through which AI is embedded in a CAP app, with recommendations from the SAP-RPT-1 model as the abstract's example. The abstract names the two protocols and the one model and does not say which packages carry them. A two-hour TechEd 2026 session in a hands-on room (Tuesday 27 October, Berlin), presented by Daniel Hutzel, Daniel Schlachter, Marc Huber and Sami Lechner, written here from SAP's abstract; the recording is not yet published.
ABAP Cloud readinessSAP and community
Migrate and modernize your custom code using RISE with SAP and agentic AIMigrate and modernize your custom code using RISE with SAP and agentic AIThe Custom Code Migration Agent in SAP Joule for Developers, ABAP AI capabilities, shown on the RISE with SAP path that moves custom extensions from SAP ERP Central Component to SAP Cloud ERP Private: the abstract says the agent adapts the code through MCP tools and the AI for ABAP features in the custom code tools, and that the adapted code is then reworked along the clean core approach, the concern ABAP Cloud readiness covers. Which MCP tools, and what the clean core step changes in the code, the abstract leaves open. A TechEd 2026 session (Tuesday 27 October, Berlin), presented by Hitesh Bindal, Ingo Braeuninger, Jonas Helin of GitHub, Olga Dolinskaja and Thomas Fiedler, 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.
ExtensibilitySAP and community
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.
Extending SAP Autonomous SuiteExtending SAP Autonomous SuiteExtensibility 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 Extensibility, the concern, and to SAP Build Code, 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.
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.
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.
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.
Transport managementSAP and community
Deploy, review, break, fix: Govern cloud transports with agility and AIDeploy, review, break, fix: Govern cloud transports with agility and AIFive BTP services in one delivery chain, as the abstract lays it out: a transport is triggered in SAP Content Agent Service, tested in SAP Cloud Transport Management, its failure is raised by SAP Alert Notification service for SAP BTP and remediated by a SAP Joule agent with SAP Automation Pilot, and SAP Cloud Logging keeps the history for root-cause analysis. The chain from alert to remediation is the operations automation concern; what the Joule agent decides on its own is not in the abstract. A TechEd 2026 session (Thursday 29 October, Berlin), presented by Biser Simeonov, Daniel Funkert, Sven Rullmann and Thorsten Sandfuchs, written here from SAP's abstract; the recording is not yet published.
Use change and deployment management in an ABAP environment with confidenceUse change and deployment management in an ABAP environment with confidenceSAP Cloud Transport Management with SAP Cloud ALM as the governed way to move changes from a cloud-optimised ABAP environment into production: the abstract says the session sets out the process, where it differs from classic transport mechanisms, the current state of every content type it carries, and an outlook on deploying agents through it, which is the transport management concern on the cloud side. What each content type covers, and when agent deployment arrives, is not stated. A TechEd 2026 session (Wednesday 28 October, Berlin), presented by Moritz Gysler and Sven Rullmann, written here from SAP's abstract; the recording is not yet published.