ServiceServiceA BTP service you subscribe to and bind, rather than install. It has plans and regions, not versions, and may deliver a product that lives outside the atlas.See every one →What this type is →by SAPby SAPPublished by SAP itself. A visible facet, never an input to a reading — a dormant official plugin reads exactly like a dormant independent one.See every one →
SAP Document Management service, integration option
A BTP service of APIs and a reusable UI5 component for adding document management, with folders, versions and status, to a business application over SAP's repository or a CMIS-compliant one.
SAP Document Management service, integration option adds document management to a business application that has to keep files beside its records. It comes in two shapes: APIs for building a document management layer into an on-premise or cloud application, and a UI5-based reusable component embedded in the application for the same scenarios. The documents live in a repository it connects to, either the repository option of the same service or a CMIS-compliant on-premise or cloud repository the customer brings. Over that repository it organises files and folders in a hierarchy with versioning and status management, and an internal repository can be onboarded with encryption under keys the customer controls.
Where it sits
Who is behind it
SAPSAPMaintains this
In the atlas: maintains 137, wrote 14@SAPmaintainer
In the atlas: maintains 137, wrote 14@SAPmaintainer
What it declares
Every artifact
- Type
- Service
- Origin
- By SAP
As a service
- Plans
- 5
- Regions
- 39
- Support component
- BC-CP-CF-SDM-INTBC-CP-CF-SDM
Connections
Group by
NodeRelationBasis
Functional
AttachmentsAttachmentsStoring uploaded files next to the record they belong toSAP and community, unassessed
provides
stated
provides Attachments
Files and folders for the documents an application keeps, through APIs or an embeddable UI5 component, stored in SAP's repository option or a CMIS-compliant repository. CAP applications can use [@cap-js/sdm](artifact:cap-js-sdm) to store attachments in the Document Management repository.
“Leverage the APIs to build a customized document management layer on your on-premise or cloud applications.”“Bring your choice of CMIS-compliant, on-premise or cloud repository to connect with Document Management Service and leverage the capabilities of the service.”“Embed an easy-to-use, UI5-based, reusable component into your application for document management scenarios.”“Use Document Management Service, Repository Option to securely store and manage your business documents and attachments.”“Organize your enterprise content with the document management capabilities like file and folder hierarchy, versioning, status management, etc.”“Use the encryption feature while onboarding internal repositories and have control over your data.”“This plugin can be consumed by the CAP application deployed on BTP to store their documents in the form of attachments in Document Management Repository.”
Storing uploaded files next to the record they belong to
Technical
@mi8y/cap-agents-sdm-backend@mi8y/cap-agents-sdm-backendDeep Agents filesystem over an SAP Document Management repositoryindependent, cap
connected from
derived
connected from @mi8y/cap-agents-sdm-backend
The agent's file operations, translated into CMIS Browser Binding requests against the document repository; the client sends the CMIS calls to the URI from the service binding, and the HTTP requests go through the SAP Cloud SDK.
“The backend translates them into requests to the document repository via the CMIS 1.1 protocol”“HTTP requests use the SAP Cloud SDK.”“It sends CMIS calls to `credentials.uri`.”
Deep Agents filesystem over an SAP Document Management repository
@cap-js/sdm@cap-js/sdmCAP attachments stored in an SAP Document Management repositorysap official, cap
needed by
derived
needed by @cap-js/sdm
“Create a SAP Document Management Integration Option [Service instance and key](https://help.sap.com/docs/document-management-service/sap-document-management-service/creating-service-instance-and-service-key). Using credentials from key [onboard a repository](https://help.sap.com/docs/document-management-service/sap-document-management-service/onboarding-repository). Configure the [REPOSITORY_ID](https://github.com/cap-js/incidents-app/blob/9327f550cde9f9666a1ffb3cbc727295b8d6fdb7/mta.yaml#L19) with the repository you want to use for deploying the application. Set the SDM instance name to match the SAP Document Management integration option instance you created in BTP and update this in the mta.yaml file under the [srv module](https://github.com/cap-js/incidents-app/blob/9327f550cde9f9666a1ffb3cbc727295b8d6fdb7/mta.yaml#L13) and the [resources section](https://github.com/cap-js/incidents-app/blob/9327f550cde9f9666a1ffb3cbc727295b8d6fdb7/mta.yaml#L134) values in the mta.yaml. Currently only non versioned repositories are supported.”
CAP attachments stored in an SAP Document Management repository
@mi8y/cap-agents-sdm-backend@mi8y/cap-agents-sdm-backendDeep Agents filesystem over an SAP Document Management repositoryindependent, cap
needed by
derived
needed by @mi8y/cap-agents-sdm-backend
The repository the agent's workspace lives in: an existing SDM CMIS repository whose virtual root folder is already created, reached either through a Cloud SDK destination pointing at the SDM API base URL or through an SDM service binding in Cloud Foundry.
“An existing SDM CMIS repository and either a Cloud SDK destination pointing to the **SDM API base URL** (not the UAA URL or `/browser`) or an SDM service binding in Cloud Foundry”“The repository and `virtualRootPath` folder must already exist; the backend does not validate or provision them.”“When `destination` is omitted, the client selects the CF service binding labeled `sdm` and exchanges the **current CAP HTTP request's Bearer JWT** using the binding's nested `credentials.uaa`.”“This is JWT-bearer-only: requests without a bearer JWT fail; there is no client-credentials or background-job fallback.”
Deep Agents filesystem over an SAP Document Management repository
com.sap.cds:sdmcom.sap.cds:sdmCAP Java plugin for attachments in SAP Document Managementsap official, cap
needed by
derived
needed by com.sap.cds:sdm
“3. Create a SAP Document Management Integration Option [Service instance and key](https://help.sap.com/docs/document-management-service/sap-document-management-service/creating-service-instance-and-service-key). Bind your CAP application to this SDM instance. Add the details of this instance to the resources section in the `mta.yaml` of your CAP application. Refer the following example from a sample Bookshop app.”
CAP Java plugin for attachments in SAP Document Management
Reports Assistant with SAP Document ManagementReports Assistant with SAP Document ManagementCAP agent writing reports into a shared SDM document workspaceindependent, cap
needed by
derived
needed by Reports Assistant with SAP Document Management
The shared workspace: an onboarded internal repository whose ID is set in the project, holding the reports the agent writes, and the reuse UI component the application embeds to show them.
“Requires a SAP BTP Cloud Foundry environment with AI Core, Document Management,
Destination, XSUAA, and HTML5 Application Repository runtime services.”“then set `cds.requires.sdm.settings.repositoryId` in `package.json`.”“I added a basic reports assistant example in the repository demonstrating this pattern in a CAP application with an embedded SAPUI5 Document Management ReuseUI and an agent chat.”
CAP agent writing reports into a shared SDM document workspace
sap-cap-sdm-pluginsap-cap-sdm-pluginCAP Node.js plugin mapping CDS entities to SAP Document Managementindependent, cap
needed by
derived
needed by sap-cap-sdm-plugin
“To use the all-in-one features provided by this plugin, you'll need a paid instance of the [SAP Document Management service](https://help.sap.com/docs/document-management-service?locale=en-US).”
CAP Node.js plugin mapping CDS entities to SAP Document Management
Download
Others providing
Compare all 3 on the Attachments page →AttachmentsAttachmentsStoring a file somebody uploaded next to the record it belongs to, and getting it back out — where the bytes actually live, who may read them, and what the UI shows while they are being scanned.SAP and community, unassessed
- ui5-upload-controlsui5-upload-controlsA reusable UI5 control library for file upload and download under the miyasuta.ui5uploadcontrols namespace, built to sit in front of a CAP service.independent, ui5UI5 control library for file upload and download in front of CAP
- @ui5/webcomponents@ui5/webcomponentsSAP's UI elements as standard custom elements, ui5-button among them, implementing SAP Fiori design and usable from plain HTML, React, Angular or Vue.sap official, ui5SAP's UI elements as standard custom elements
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
discovered viaAdded by hand
first seen in the atlas
ecosystem and domainbtp, data-and-persistence
History in the atlas
- ui5, cap
- First seen.
For your agent
- Ref
artifact:btp-document-management-integration- JSON
- /artifacts/btp-document-management-integration.json
- MCP
- Connecting an agent