We use third-party software from Ixos to scan a document and then to assign it via SAP t-code OAWD to a select...
category. The category is linked to a SAP t-code which is used during entry of A/P documents. The user goes to his or her inbox, selects a workflow task, and executes it. This action launches not only the SAP data entry screen, but also the document display screen from Ixos which holds the scanned document. The user enters the data and then posts the document. At that point the SAP document number is linked to the scanned image and is stored in external storage.
Our problem is that occasionally, when the user attempts to post, the entire workstation "locks". By pressing "ctrl alt delete," we can see all of the processes running. All the user can do at that point is to shut the system down and re-boot. Our third-party software provider, Ixos, reports it is not their issue.
Is there anything within SAP workflow that we should check to see if the problem is related to our workflow configuration? We need to correct this "locking" of the local desktop. Since the problem only happens occasionally, do you think that this is possibly workflow related?
I would go back to IXOS and SAP and look further there. The new SAPGUI does seem to have quite a few issues and this issue might be due to some incompatibility between your workstation, the IXOS solution and/or the SAPGUI. Good luck.
Dig Deeper on SAP workflow development
Related Q&A from Alon Raskin
An SAP user has created a user decision step in an SAP workflow item and wants to know how an end user can send an attachment to other users.continue reading
Find out how to configure clients so that the same version of an SAP workflow item is used when the workflow is triggered in separate clients.continue reading
A SearchSAP.com reader wants to know how to hide the forward button in an SAP Business Workplace toolbar.continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.