Attach a document to a business record and retrieve it later
RAP / ABAP
Awaiting editorial review · assessed · no Atlas runtime testing
- RAP large-object handling · SAP official · implementation
Retain file content with attachment, MIME type and filename semantics on the application’s RAP business object.
- RAP File Upload & Storage Management · Independent · sample
Maintainer describes an unmanaged RAP file store with upload/download and metadata handling.
RAP large-object handling · conditional
Retain file content with attachment, MIME type and filename semantics on the application’s RAP business object.
Conditions: Use a release supporting RAP large objects.; Adapt the example’s PNG/JPEG MIME restrictions for the required document types.
Remaining work: Model business-record association and authorization; multiple attachments and repository integration need separate assessment.
RAP100 — Enable OData Streams · checked 2026-10-06
RAP File Upload & Storage Management · conditional
Maintainer describes an unmanaged RAP file store with upload/download and metadata handling.
Conditions: Adapt the sample to the application and target release.
Remaining work: Business-record association, licensing, deployment compatibility and production behavior remain unassessed.
kowsick10 — RAP File Upload & Storage Management · checked 2026-10-06
Prototype assessment awaiting review · assessed . No Atlas runtime testing.
Related knowledge
Enhance the business object data model and enable OData streams with SAP BTP ABAP environment.
Why included: Native relationship in the retained Developers snapshot; no runtime claim is inferred. · SAP Developers
Independent explanation of retaining and downloading files on a RAP object.
Why included: Curated supporting reading for this assessment. · Software-Heroes
Official further reading linked by RAP100. Page body was not retrieved; no independent support claim is inferred.
Why included: Explicit further-reading link; target page body was not reviewed. · SAP Help
Source subject or learning resource; applicability is established separately by the scoped assessment.
Why included: Native relationship in the retained Developers snapshot; no runtime claim is inferred. · SAP Developers
Source subject or learning resource; applicability is established separately by the scoped assessment.
Why included: Native relationship in the retained Developers snapshot; no runtime claim is inferred. · SAP Developers
Why this assessment is relevant
- Attach a document to a business record and retrieve it later → RAP / ABAP
Relationships and evidence (13)
Enhance the Business Object Data Model and Enable OData Streams → teaches → RAP (Restful ABAP Programming) Model
Native relationship in the retained Developers snapshot; no runtime claim is inferred.
Basis: source-graph
SAP Developers graph snapshot · checked 2026-10-05T00:55:43.720Z
Enhance the Business Object Data Model and Enable OData Streams → teaches → OData Edm.Stream Type for Binary Media
Native relationship in the retained Developers snapshot; no runtime claim is inferred.
Basis: source-graph
SAP Developers graph snapshot · checked 2026-10-05T00:55:43.720Z
Attach a document to a business record and retrieve it later → associatedWith → Attachments
Discover the shared task through the Attachments concern.
Basis: pilot-assessment
RAP large-object handling → provides → Attachments
Retain file content with attachment, MIME type and filename semantics on the application’s RAP business object.
Basis: pilot-assessment
RAP100 — Enable OData Streams · checked 2026-10-06give end-users the option to upload and download images
RAP File Upload & Storage Management → demonstrates → Attachments
Maintainer describes an unmanaged RAP file store with upload/download and metadata handling.
Basis: pilot-assessment
kowsick10 — RAP File Upload & Storage Management · checked 2026-10-06supports uploading, downloading, and automatically managing file metadata
Enhance the Business Object Data Model and Enable OData Streams → references → Working with Large Objects
Explicit further-reading link; target page body was not reviewed.
Basis: observed-link
RAP100 — Enable OData Streams · checked 2026-10-06give end-users the option to upload and download images
OData Edm.Stream Type for Binary Media → addressesPartOf → RAP / ABAP
Streaming addresses part of retained attachments; it is not equivalent to the task.
Basis: pilot-mapping
Mapping: partial · pending-human-review · authored from cited sources · checked 2026-10-06
RAP100 — Enable OData Streams · checked 2026-10-06give end-users the option to upload and download images
RAP / ABAP → assesses → Attach a document to a business record and retrieve it later
One shared outcome, one scoped assessment.
Basis: pilot-assessment
RAP large-object handling → contributesTo → RAP / ABAP
Retain file content with attachment, MIME type and filename semantics on the application’s RAP business object.
Basis: pilot-assessment
RAP100 — Enable OData Streams · checked 2026-10-06give end-users the option to upload and download images
RAP File Upload & Storage Management → contributesTo → RAP / ABAP
Maintainer describes an unmanaged RAP file store with upload/download and metadata handling.
Basis: pilot-assessment
kowsick10 — RAP File Upload & Storage Management · checked 2026-10-06supports uploading, downloading, and automatically managing file metadata
RAP / ABAP → reading → Enhance the Business Object Data Model and Enable OData Streams
Curated supporting reading for this assessment.
Basis: pilot-assessment
RAP / ABAP → reading → RAP — File Upload (Stream)
Curated supporting reading for this assessment.
Basis: pilot-assessment
Software-Heroes — File Upload (Stream) · checked 2026-10-06If you click on the name, the file is downloaded.
RAP / ABAP → reading → Working with Large Objects
Curated supporting reading for this assessment.
Basis: reference-only
Gaps, source snapshot and retrieval limits
- No reviewed independent reusable RAP attachment package established in this bounded search. An independent sample is included separately.
- The Help reference and SAP Community candidates have not had a full-body review.
- No directly applicable Architecture Center design established. Document extraction is a different task.
- Retrieval uses at most four typed steps within a bounded source index. Source relationships do not establish compatibility.
Developers snapshot checked 2026-10-05 · 33 indexed records from a 9,023-node source snapshot. This is a bounded retrieval view; absence is not evidence that no solution exists. Source relationships and proximity do not establish runtime compatibility.
Mapping version: connected-tasks-2026-10-06-v4+mcp-records-b256b58cfb844590. Task and mapping evidence remain separate from implementation evidence.