BrowseAll ecosystems
Everything in the atlas
9 of 2341
Domain
Signals: No date
Content
More: 2
Group by: None
EntryBySignalsLast activity
ABAP AI SDK powered by ISLM - How to implement your own AI use cases in ABAPABAP AI SDK powered by ISLM - How to implement your own AI use cases in ABAPA Devtoberfest 2026 ABAP-track session (ABA-44) on the ABAP AI SDK: an intelligent scenario development object holds the model and its version, so the ABAP code asks for an API, sends a prompt and reads the completion with its token counts and finish reason, and swapping the model is a change to that object rather than to the code. Four demos go through the ABAP line by line — a bare completion, a system prompt with the temperature set to 0.2, tool calls where the model asks for order details and the result goes back into the message container, and a JSON response schema that returns category, severity and goodwill as fields a program can act on — and a fifth replaces the API with the SDK's own mocks so unit tests run with no network call, which is what the LLM integration edge on the ABAP door rests on. The closing availability matrix separates base scenarios, available across SAP S/4HANA on-premise, private edition, public cloud and the SAP BTP ABAP environment, from the orchestration service and SAP RPT, shown for on-premise and private cloud with transport-based correction instructions back to release 2022 and not yet for the public cloud editions.SAP Developers
CAP Node.js Expert Session #6 - The MCP AdapterCAP Node.js Expert Session #6 - The MCP AdapterDaniel Schlachter and DJ Adams add @cap-js/mcp to a bookshop service, inspect its describe, query and action tools, and query the catalogue through an AI agent. The session distinguishes this runtime adapter from the development-time MCP server and demonstrates automatic registration of the running service with a local agent. The recording describes the adapter as beta in July 2026, with read-only queries and writes through unbound actions.
Data Product Governance in SAP Business Data CloudData Product Governance in SAP Business Data CloudA Devtoberfest 2026 data-track session (DAT-41) on data product governance in SAP Business Data Cloud, released as an MVP: every data product belongs to a domain, a consumer puts one in a cart and raises an access request with a purpose, a target location and acknowledged terms and conditions, and a data steward's approval becomes an access agreement recording who uses which data product where. The demo runs both sides in the BDC cockpit — domains, access management and data product management for the steward, catalog, cart and request for the consumer, with Databricks as the target workspace — and that is what the Cataloguing and lineage edge rests on. It also states the current limits: one default domain until custom domains and subdomains arrive, auto-approved requests for space copies, transports and intelligent content, stewards who cannot yet revoke an active agreement, and an install step still done by hand after approval.SAP Developers
Edge Integration Cell - what's new?Edge Integration Cell - what's new?A Devtoberfest 2026 integration-track session (INT-41) on Edge Integration Cell, the runtime of SAP Integration Suite a customer runs on their own Kubernetes cluster while design, configuration and monitoring stay in the cloud tenant. It names what the customer has to provide — a supported Kubernetes platform, SAP HANA or PostgreSQL, Redis or Valkey as data store, a load balancer — then the Edge Lifecycle Management cockpit with its monthly rolling updates, the inbuilt and the external Cloud Connector options and why a DMZ placement calls for the second, and the adapters available only on Edge: RFC sender, NFS, OFTP2 and UNF. The demo deploys an OFTP-to-file flow to the Edge runtime and shows the same flow rejected when its runtime profile is switched to cloud, which is where the Integration flows edge holds.SAP Developers
Event Add-On for ERP: All you need to know about the new Event StudioEvent Add-On for ERP: All you need to know about the new Event StudioA Devtoberfest 2026 integration-track session (INT-43) on Event Studio, the browser-based part of the Event Add-On for ERP that defines events in an S/4HANA or ECC backend without code and sends them to a broker. A custom sales-order event is built live — fields picked into a payload that is published as a CDS view entity, a trigger on a classic business object, a static topic — and arrives in a queue on SAP Integration Suite, advanced event mesh, which is where the Event Mesh edge holds. The rest of the demo covers health and exception monitoring in SAP Cloud ALM, the AsyncAPI definition replicated to Event Portal, and the AI assistant and MCP server now inside Event Studio.SAP Developers
MCP Gateway in Practice: Architecture, configuration, and hands-onMCP Gateway in Practice: Architecture, configuration, and hands-onA Devtoberfest 2026 integration-track session (INT-21) on the MCP gateway of SAP Integration Suite: curated enterprise APIs served to agents as MCP tools over JSON-RPC, behind the authentication, authorization and traffic policies an API artifact already carries, with the existing API layer left in place. The hands-on half composes S/4HANA plant, material-stock and supplier data with a non-SAP location-risk source into one business data graph, downloads its OpenAPI specification, creates an MCP server artifact with tools, prompts and a surge-protection policy over that endpoint, and publishes it as a product in Developer Hub of API Management, where an agent developer subscribes and gets OAuth credentials. An MCP client then asks for 15 brake pads and ranks plants by stock, location risk and distance from Walldorf, which is what the agent access to your systems edge rests on; the Q&A covers principal propagation to the backend, how errors reach the model, and which Integration Suite editions carry the gateway.SAP Developers
SAP Cloud Integration chamber of horrorsSAP Cloud Integration chamber of horrorsA Devtoberfest 2026 integration-track session that goes through anti-patterns in Cloud Integration iFlows: scripts that re-implement flow steps or make external calls, the ESB_Messaging.send role on every sender channel, default flow-step names, dependence on undocumented platform internals, code that rewrites what the Groovy and Java libraries already hold, XML namespaces stripped to simplify XPath, HTTP calls between iFlows on one tenant where ProcessDirect would stay inside it, externalised parameters too few or too many, and MPL attachments left switched on in production. Each one comes with how to spot it — long scripts, jar files for SFTP communication, the design guidelines and upgrade readiness checks, or a rule in the presenter's own CPILint run locally or in a pipeline — and that pass over flow steps, sender roles, adapters and the message processing log is what the Integration flows edge rests on. The questions afterwards cover the GitHub integration in Cloud Integration, the absence of an official MCP server for building iFlows, and whether generated code shifts the choice between mapping, XSLT and scripting.SAP Developers
SAP HANA Data Lake Files (HDLF) Basic FunctionalitiesSAP HANA Data Lake Files (HDLF) Basic FunctionalitiesA Devtoberfest 2026 data-track session on SAP HANA data lake files, the managed object store inside SAP HANA Cloud that is provisioned from HANA Cloud Central, priced per API call and per stored gigabyte, and reached with the same REST API whichever hyperscaler it runs on. Two product managers set up an instance with its IP allow list, client certificates and trusts, then upload, list, read and delete files over the WebHDFS REST API and the HDLFS command-line utility — the Object storage half — and cover file versions with snapshots, access policies per file, and chunked upload with a server-side merge. They then link the instance to a HANA database and query a CSV file as a virtual table: SQL on files now runs through a file adapter in the database, while the older path through the data lake relational engine is deprecated.SAP Developers
The Full Picture: Federating, Replicating, and Caching Remote Data in CAP — Part 1The Full Picture: Federating, Replicating, and Caching Remote Data in CAP — Part 1Part one of two, and the concepts half: terminology, what CAP already does, and what a project still has to write. It fixes a vocabulary — federation is the umbrella for making remote data part of your model, delegation forwards each request to the remote at query time, replication is a scheduled copy into the local database, and caching is an option on either rather than a third strategy — which collides with CAP's own, since what this series calls replication is what the CAP-level Data Federation guide calls federation. From the ground the Service Integration guide covers, it lists what is left to hand-write: cross-service $expand, navigation filters across the boundary, write forwarding, timeouts and retries, then scheduling, delta detection, backoff, a guard for two app instances sharing one schedule, idempotent writes, and knowing whether the last run succeeded. That list is why the edge to cds-data-federation holds: the second half maps it onto @federation.delegate and @federation.replicate and says which package carries which part — annotations in cds-data-federation, the scheduled engine in cds-data-pipeline, response caching through cds-caching — so it is the design rationale for the annotations, not the API reference. The gap list and the plugins answering it come from the same person who maintains them; cap-replication-demo and SAP's xtravels sample are cited as the hand-written form of the same work. Part 2 is announced as a walkthrough of a demo application and is not covered here.
