created a custom ArchiveLink solution for a third-party DMS
I've created a custom ArchiveLink solution for a third-party DMS that isn't officially supported. Despite the lack of out-of-the-box support, I've managed to configure it in OAC0, and the system now correctly stores and retrieves documents tied to SAP objects. I'm looking for insight into potential risks.
Could using a non-certified, custom-interfaced repository lead to any issues with the core SAP system?
Answers
If all technical functions have been thoroughly tested, your solution should be stable. As with any customization, SAP's support would still cover the system up to the point of the ArchiveLink call.
However, be aware that other capabilities, such as Information Lifecycle Management (ILM), often have a list of certified repositories. Your custom solution may not be supported in those contexts. It is highly recommended that you confirm this with SAP before deploying in a production environment.
Your Answer
Latest Topics
