Recently, I checked where attachments to financial documents are currently saved, whether the storage is the SAP database or the server, for example, IXOS or another. It took me a while to find this. If you are also looking for this information or you are not sure where it is better to save attachments, this example can be helpful.
The Generic Object Services attachment that is connected to the financial document in the transaction (tcode FB03 or another containing GOS) is stored depending on how is attached and the settings we currently have in the system.
That is if we use the path GOS -> Create -> Create Attachment, the attachment will be saved in SAPoffice. Regardless of whether users manually attach an attachment to an accounting document or in bulk (for example using GUI Script/RPA).
However, if the path GOS -> Create -> Store business document is used, the attachment will be saved using Archivelink, and the storage location will be indicated by the configuration (tcode OAC3).
In our case, attachments are added to SAPoffice and the storage location is SOFFDB and the current configuration indicates a record in the SAP database. This has been verified in the OAC0 tcode. Some additional information is also available in KBA 2571570.
We had to consider where to store attachments, whether on the IXOS server or in the SAP database. It is worth estimating the scale of the added attachments so as not to burden the system base too much, but also what are the terms of the IXOS contract for the amount of data transfer. Usually, if the amount of data exceeds a certain level, then you have to reckon with an additional fee. On the other hand, too much load on our SAP base may result in lower system efficiency. Therefore, here the decision will be based on the needs’ analysis.