Rel: 4.70 -- Archive Link and Workflow problem

[Mike Pokraka]

Hi John,
Curious, the Create document step is terminated by a IMAGE.ASSIGNED
event, yet the following step is the one that assigns the image....
something isn't making sense.
Could you give us more detail on what IMAGE.ZIMAGEPROCESS does?
Cheers,
Mike

John Wiese wrote:
> Dear Fellow Workflowers . . .
> 
>  
> 
> We are on the verge of a 4.70 Upgrade weekend (May 26 thru 29, 2006) and
> we are running into an interesting issue
> 
> with Early Archiving and Workflow . . .
> 
>  
> 
> Here are “some” of the details . . . (please see attachment for full
> details):
> 
>  
> 
> WORKFLOW PROBLEM – SAP 4.7 Archive Link and Workflow
> 
>  
> 
> Problem statement: after creation of a Logistics Invoice (transaction
> MIRO), the LIV document should be assigned to the scanned image and the
> workflow should end successfully. Instead, the workflow loops back
> around so that the user is once again prompted to create and link a new
> document to the scanned image. Even though an LIV doc is created
> successfully and the image is linked to the document. Hence, the
> assignment of image to document isn’t recognized by the workflow.
> 
>  
> 
>     * WS90000034 – ESRI ImgNew – for early archiving of scanned documents
>     * Workflow essentially loops until flagged completed
>     * One branch of the loop is problematic – namely steps 381, 386 and 391
>     *  
>     * [Workflow  Builder – Display ‘ESRI ImgNew’]
>     *  
>     * 381 is the Create R/3 Document step – it eventually calls
>       IMAGE.ZIMAGEPROCESS (tcode MIRO)
>     * Screen shots below are the drill down into this step of the workflow
>     * It dynamically calls the appropriate transaction (MIRO) for the
>       document type (ZFI_LIVDOC in our case)
>     * Possible outcomes of the step are Process Abandoned, Processing
>       rejected and Document type assigned. Process Abandoned and
>       Processing rejected work fine. “Document type assigned” is not
>       reached.
>     * The “Document type assigned” outcome is a result of a terminating
>       event defined in the task. This seems to be the problem point.
>     * The other problem is that occasionally the workflow simply
>       bypasses those two steps (386 & 391) and then loops around again,
>       prompting the workflow user to process, abort or otherwise make
>       the initial decision of the workflow.
>     *  
>     * [Additional screen shots]
>     *  
>     *  
> 
>  
> 
>  
> 
> Does anyone have any idea as to how-to trouble-shoot / resolve this problem?
> 
>  
> 
> Thanks for your time and your help!
> 
>  
> 
> John Wiese
> 
> ESRI, Inc.
> 
> Redlands, Calif.  92373
> 
> (909) 793-2853 x2381
> 
>  
> 
>  
> 
> 
> 
>  
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug