Storing non-OnBase PDFs from SAP in current OnBase ArchiveLink content respository

[Carissa_Skaff]

Our SAP team is looking for a way to save server space by storing PDFs in OnBase (our solution is hosted on the Hyland cloud).  These documents do not originate in OnBase and have no ties to OnBase. 

We do have OnBase ArchiveLink established for viewing PDF images in SAP that exist in OnBase, so there is an OnBase content repository already established in SAP.  The team believes if they send the PDF images to the OnBase ArchiveLink content repository (circumventing the OnBase import), that will solve their storage space issue. 

Is this correct?  If so, how would we be able to access these PDFs in OnBase if they have none of the associated keyword metadata that comes from the OnBase import process?

We are a Hyland hosted solution and I tried checking the BIC backup folders associated with our ArchiveLink process and see nothing exists here.  

Any help is appreciated.  Thank you.

[Carissa_Skaff · Accepted solution]

Received an answer from Tech Support if anyone else is looking for info about this topic:

"You could definitely store the docs in OnBase, and they could be retrieved, but without knowing doc handle or indexing the docs (like with IDOCs), it's going to be "harder" to retrieve. With that being said, if you have the metadata somewhere else or you can link the doc with the object in SAP, or if you know to look for 'XXX' doc handle, it should work.

But just to be clear, by sending via Archivelink, you are still importing documents into OnBase, and the docs would be visible in OnBase if the doc type is available for the user and they know the doc handle for instance. You also have the ability to link using workflow web service calls. I also believe there may be some fairly standard SAP "programs" that you could doctor up to send the IDOCs over, but it will take some type of solution design which would be considered a custom solution and is outside the scope of Tech Support"