The OnBase Connector for use with SAP ArchiveLink has long contained a web service endpoint for getting link information from OnBase. But starting with version 22.1, there is now an endpoint to get link information from SAP. This can allow a business process to now include a check to ensure that a link exists on the SAP side of the aisle, or to pull back useful information such as SAP Business Object ID and Business Object Type that can later be used to get back additional metadata.
This new 'GetArchiveLinkConnections' endpoint can be found in the existing GenericLinkingService web service, and like the other endpoints can be called using the OnBase WorkFlow action 'Call Web Service'. As seen in the below examples, the service takes in the OnBase doc handle as well as the SAP sender ID.
When a link is found, a structure is returned that contains one or more sets of link information for that document - information typically stored in SAP table: TOA01. When no link is returned, a value of 'NOTHING_FOUND' returns in the Exceptions Message.
So, how can this be used? Here are a couple thoughts:
- Let's say an SAP user utilizes the GOS button and performs the Store Business Object operation. The document goes to OnBase, but isn't indexed. This document can now go directly into WorkFlow and GetArchiveLinkConnections can be used to get the SAP Object ID (i.e. invoice number, company code, fiscal year) and Business Object Type which can then be used to execute a custom query or an external autofill to fully index the document.
- A business process can be enhanced with a rule to ensure that a link exists in SAP before a document exits a life cycle, or is transitioned to another queue.
What other ideas do you have?
4 Comments
