WF & Archivelink: Scanned image not linked to Invoice created

[MacPherson, Graeme (AU - Melbourne)]

Thanks to all who responded.
 
The answer to this riddle is in OSS Note 352927. The check function module
(ARCHIV_WORKFLOW_ASSIGN) on the event IMAGE.ASSIGNED was missing.
 
This also answers my own question as to where (and when) the image and
object are linked: ARCHIV_WORKFLOW_ASSIGN. The SAP transaction only raises
the event IMAGE.ASSIGNED.
 
Regards
 
Graeme MacPherson
Senior Consultant
Deloitte Consulting, Melbourne
Ph: +613 9208 7100
Mob: 0414 473 554
 
 
-----Original Message-----
From: phillips, tim [mailto:tim.phillips at SERuk.com]
Sent: Friday, 22 June 2001 18:36
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: WF & Archivelink: Scanned image not linked to Invoice
created
 
 
Graham:
 
I am on version 4.6B
 
________________
 
Timbo:
 
OK, I use 4.0b - but I shall try and help, nevertheless.
 
________________
 
Graham:
 
and we are using the early archiving method for
scanning of invoices (Object method IMAGE.IMAGEASSIGNEARLY). The workflow
has worked perfectly through Unit, Integration and UAT testing (3 separate
environments) but in a pre production client the Object (BKPF Invoice) and
image are not being linked in TOA01. The workflow is executed, the invoice
transaction FB01 is called and the agent enters the invoice. The terminating
event IMAGE.ASSIGNED is being raised and the workflow is therefore
terminating but the link in TOA01 is not appearing.
 
Logic indicates that the pre production client has some settings which are
not in place to make this work. I have checked the Configuration,  security
of the agent etc but cant see any problems. From looking into the code, my
understanding is that the link must be created in the transaction (FB01) as
I cant see code in the Object method which does this. Am I correct ?
 
________________
 
Timbo:
 
Yes - the link is created as part of function module 'WF_COMMIT', called
from program MF05AFF0 (an include for SAPMF05A).
 
________________
 
Graham:
 
Also, are there archiving settings unique to a production environment which
might be causing a problem ?
 
________________
 
Timbo:
 
Not that I am aware of, and I have had very recent experience of the problem
you describe.
 
My first inclination would be to check your customising settings again;
particularly in OAC3.
 
If they are correct, my suspicion is that something must be afoot in the SAP
standard code.
 
Check to see if 'WF_COMMIT' is being called from SAPMF05A, and that the
table submitted 'wfltab' is being filled correctly.  Maybe, a patch has been
applied to the production system that has led to a deviation between codes.
 
 
That was, after all, the source of my problem.
 
Regards,
 
Tim