Archive Attachments in SAP S/4HANA Cloud Public Edition

Quick answer

Attachment archiving in SAP S/4HANA Cloud Public Edition should be planned around the specific business object: which app creates the attachment, which document framework manages it, where is its content stored, and how will it remain retrievable? SAP documents a standard repository on SAP BTP for the Attachment Service, alongside optional integration with external repositories. Connecting a third-party repository through CMIS is therefore an architectural choice, not an automatic requirement for every attachment. [1] [2]

A successful upload does not establish whether a document will remain available and traceable throughout its intended period of use. The project also needs defined retention rules, verified permissions, and a tested retrieval and export process. This guide covers technical planning and acceptance testing, not the legal recognition of an archive solution.

Scope and limitations

This guide covers files and attachment URLs managed in supported apps through supported business objects and document frameworks in SAP S/4HANA Cloud Public Edition. The SAP documentation reviewed is version 2608; the release actually in use and the enabled configuration must be confirmed separately.

It does not cover a blanket configuration for all Fiori apps, the use of on-premise transactions in Public Edition, ERP data archiving, or a complete migration of arbitrary existing archives. It provides no assurances regarding German GoBD requirements, certification, costs, or SLAs. This article does not confirm the suitability of any specific arcana solution.

For a general comparison of interfaces, see ArchiveLink or CMIS?. This guide instead focuses specifically on the lifecycle of a Public Edition attachment.

Phase 1: Define the app, business object, and original file

Start with a narrowly scoped pilot: one specific app, one business object, and one document type relevant to the business. Record the app name, object or node type, object key, framework used, and intended retention purpose. A pilot is only meaningful when these details come from your own system rather than a generic product example.

The Attachments API API_CV_ATTACHMENT_SRV can manage attachments and attachment URLs for business objects. Its documentation describes operations including creating, reading, renaming, and deleting. It also identifies limitations: the API does not support business-object draft functionality and, according to the documentation, is incompatible with consuming applications that support drafts. The content of an existing attachment cannot be updated through this API. These limitations must be checked against the specific app workflow. [3]

Also distinguish an uploaded original file from a stored URL reference. For a link, establish who operates the target and whether the document will remain accessible after changes to the target system. The attachment list alone is not evidence that the original file is safeguarded for the long term.

Phase 2: Record the SAP link and storage location separately

SAP describes two layers: structured information such as the file name and MIME type is managed in SAP database tables, while the actual document content resides in a CMIS-based repository. The repository itself holds both content and metadata. SAP’s standard path uses SAP Document Management Service on BTP through SAP Content Bridge. [1]

For project acceptance, it is therefore advisable to map the business object key, logical document ID, physical document ID, and storage category, where those fields are available in the relevant workflow. The API documentation lists fields such as LogicalDocument, ArchiveDocumentID, LinkedSAPObjectKey, and StorageCategory. [3]

Test two distinct failure scenarios: a file exists in the repository but can no longer be accessed from the business object; or the attachment list displays an entry whose file cannot be loaded. Both scenarios require a defined recovery and escalation process.

Phase 3: Choose the standard repository or a third-party integration

First compare the existing standard repository with the business requirements. If an external repository is selected, SAP documents the customer-managed communication scenario SAP_COM_0597 and integration through SAP Document Management service, integration option, on BTP Cloud Foundry using CMIS. Configuration and the integration of products not developed by SAP are the customer’s responsibility. [2]

SAP recommends certified solutions for this integration path. That recommendation does not confirm that any particular vendor, product version, or use case is currently certified. Before making a selection, verify the relevant evidence against the applicable scenario. [2]

The existing guide to integrating a CMIS document repository with SAP BTP covers the technical connection in more detail. Do not treat that setup as a separate archive project: for Public Edition attachments, app behaviour, SAP links, and the repository must be tested and accepted together.

Phase 4: Check document types, HDM, and storage categories

Harmonized Document Management, or HDM, can bring together supported document frameworks such as DMS and GOS for the configured business object. Without this configuration, the API can return only DMS or GOS attachments for each supplied object type; separate calls may be required to retrieve both. With HDM configured accordingly, the frameworks actively maintained for the object are taken into account. [3]

SAP’s configuration documentation lists 101090 – Define DMS Document Types, 105346 – Activate HDM for Attachment Object Type, and 103583 – Maintain Storage Categories. The last activity applies to customers choosing an external repository for file storage. Use the configuration environment for your release and check the required configuration permissions; these activities are not universal instructions for every app. [4]

After configuration, record which document types are permitted, which framework is actually used, and which storage category is assigned to the pilot case. Test with a newly created file and an existing attachment, rather than relying solely on a successful connection test.

Phase 5: Test access, retention, and deletion behaviour

First define the expected behaviour. Who may read a document? Who may store a new version or change its name? Who may initiate deletion, and what happens during a retention or hold period? These rules must come from the company’s business and legal requirements; the technical integration does not create them automatically.

The API returns information including AttachmentDeletionIsAllowed and AttachmentRenameIsAllowed. Such fields help test a specific operation, but they replace neither a comprehensive authorisation model nor evidence that legal retention requirements are met. [3]

Recommended acceptance tests are:

  1. An authorised person retrieves the original from the correct business object and compares the file with the agreed reference set.
  2. An unauthorised person cannot gain access through either the app or an additional technical access path included in the test.
  3. A permitted name change and a prohibited change or deletion attempt produce the defined behaviour.
  4. A repository outage produces a visible error, follows a documented recovery process, and does not silently lose the link.
  5. Once an agreed period has expired, release approval, any holds, and the deletion decision are recorded in a traceable way.

These steps are project recommendations. Whether the specific product supports them must be demonstrated in the pilot.

Phase 6: Prepare for export and future system changes

Plan retrieval outside the day-to-day app workflow before go-live. An export should provide not only files but also the required mapping to the business object, readable metadata, and a verifiable record of item counts and completeness. Define which information must actually be available for this purpose.

SAP describes onboarding from a customer-managed repository to an SAP-managed repository and offboarding in the opposite direction. For offboarding, SAP refers to Attachment Data Returns, including content linked to business objects and certain output documents. This provides a documented process foundation, not a guarantee of automatic migration between arbitrary third-party archives. [5]

For an existing archive, the SAP archive migration checklist complements the pilot described here. Include a test export in acceptance testing: the original file is readable, the associated business object can be identified, the required metadata is present, and the item-count reconciliation is traceable.

Frequently asked questions

Does every Public Cloud attachment need an external third-party archive?

No. The SAP documentation used here does not establish such a blanket requirement. SAP describes a standard repository and an alternative third-party integration. Which option meets your own business and legal requirements must be assessed separately. [1] [2]

Is a working CMIS connection enough for archive acceptance?

No. The connection initially demonstrates a technical communication path. Acceptance of the attachment workflow also requires checks of the business object link, retrieval of the original, permissions, the defined lifecycle, and a suitable export.

Is a stored attachment URL the same as an archived original file?

No. The API supports both attachments and attachment URLs. With a reference, content availability also depends on the target; long-term safeguarding of the original must be demonstrated within the relevant design. [3]

Sources

arcana Solutions

Discuss your SAP archiving project

Would you like to review your archive migration, repository integration or operating model? Choose a consultation slot and discuss an appropriate next step with our team.