API_CV_ATTACHMENT_SRV. Display name “SAP List Attachments”. Off by default.
Authentication and enablement
Requires a workspace SAP integration.base_url and authorization are injected. Enable the tool and bind the integration.
Naming the object
Two forms, and exactly one of them per call:
There is no shorthand. The tool composes no keys and defaults no object type — one that guessed either would list the attachments of the wrong document. Build the key from fixed-width parts with no separators, each zero-padded to its SAP width:
Count the characters before sending. SAP answers a key that matches no document with an empty list, not an error, so a key short by one digit reads as “this document has no attachments”.
Outputs
attachments — each with FileName, MimeType, FileSize, CreatedByUser, CreationDateTime, and the key fields sap_get_attachment needs (DocumentInfoRecordDocType, DocumentInfoRecordDocNumber, DocumentInfoRecordDocVersion, DocumentInfoRecordDocPart, LogicalDocument, ArchiveDocumentID, LinkedSAPObjectKey, BusinessObjectTypeName) — plus total, business_object_type and object_key.
Limits and errors
- An object with no attachments returns an empty list, not an error.
- A wrong or unpadded
object_keyalso returns an empty list. That is SAP’s behaviour, not a bug here — check the key before concluding there are no attachments. - A deleted document refuses the call: SAP disables attachment handling once the document is gone.