BrowseAll ecosystems
Everything in the atlas
4 of 2341
Domain
Signals
Content
More: 3
Group by: Kind
EntryBySignalsLast activity
Content
API Policy - FAQAPI Policy - FAQSAP’s June 2026 FAQ, version 1.3, explains the scope and use conditions of the SAP API Policy, including published and non-published APIs, ADT developer access, AI-driven usage and third-party MCP servers. It also addresses data extraction and the responsibilities of customers and partners. The FAQ is informational: it does not modify contracts, and applicable agreements and product documentation prevail if they conflict with it.
CAP JavaでObject Pageの項目の動的な入力制御を実装するCAP JavaでObject Pageの項目の動的な入力制御を実装するTwo ways to make an object page field editable or not from the value of another field in CAP Java, with the same rule implemented both ways. The first routes the decision through a separate entity holding default values, reached by Side Effects annotations; the second adds a virtual element the Java event handler fills. The piece is about the trade the two make — annotation-only versus a handler that runs — rather than about which is correct, and the running code is the repository it links.published 2025-10-13
Configure an MCP Server Created from an HTTP EndpointConfigure an MCP Server Created from an HTTP EndpointDocuments configuring API Management’s HTTP-source MCP server tools, resources, prompts and policies. Resources are selected from GET operations and have URI templates/content types; prompts define User/Assistant messages with optional arguments, alongside MCP policy configuration.
MCP Server — SAP Integration SuiteMCP Server — SAP Integration SuiteSAP's own page for the MCP Server artifact in SAP Integration Suite, and where the gateway that runs it is described: MCP clients and API clients reach the same backends through two gateways that share security, traffic management and multi-protocol connectivity. Sets out the three primitives a server may expose — tools derived from API operations with an input and output schema, resources addressed by URI for context rather than action, and prompts as reusable interaction patterns. Says availability depends on the Integration Suite service plan, and points at the three creation paths as separate pages.