QUESTION POSED ON: 28 November 2005
We have a problem but we are not sure if this is due to an incorrect setting within workflow configuration. We have workflow set up to use task TS30001128 in a "storage for subsequent entry" scenario.
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?
|
