infinite loop of TS7869 (ImageAssign)

[Liu, Yan Y SSI]

Kristine,
 
I have un-checked the global for Image/Assigned/Workitem in event linkage
table.  Yes, it has prevented the looping for TS7869 if it's linked to a
gloal document type directly(SOA0).
 
However, if TS7869 is called from a workflow (with re-assigned global doc
type), two workitems(TS7869) were created.  One was able to complete, but
the other gets into an infinite loop (forever in status In Process).
 
Thanks for your advice, I understand my problem better now.
 
Yan
 
> -----Original Message-----
>> From: Alsandor, Kristine KH SSI [mailto:KA199408 at MSXSSC.SHELL.COM]
> Sent: Thursday, January 27, 2000 2:35 PM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Re: infinite loop of TS7869 (ImageAssign)
> Importance: High
>
>
> Yan, have checked the boxed for  enable global in the event
> linkage table. I
> can not remember exactly what it is called , but I think we
> had that in
> Rumba.
>
> > -----Original Message-----
> > From: Liu, Yan Y SSI [SMTP:YD186300 at MSXSSC.SHELL.COM]
> > Sent: Thursday, January 27, 2000 1:40 PM
> > To:   SAP-WUG at MITVMA.MIT.EDU
> > Subject:      infinite loop of TS7869 (ImageAssign)
> >
> > Hello,
> >
> > This is a question related to both Optical Archiving and Workflow.
> >
> > I am encountering an infinite loop of TS7869 after calling
> it from my WF.
> > After the executing TS7869, the R/3 document was posted and
> an entry was
> > made to the link table.  However, a new workitem (TS7869) appears in
> > users'
> > inbox.  The task carried all the parameters assigned via
> task binding
> > within
> > the WF.
> >
> > Any Advice?  This only happens when we link WF to a global
> document type
> > and
> > call TS7869 within the WF....  no problem if we link TS7869
> directly to a
> > global document type.
> >
> > Here are the task (TS7869) binding with WF:
> >
> > ArchiveLink image       <==     &IMAGE&
> >
> > SAP ArchiveLink         <==     &IMAGE.IMAGELINKARCHIVEID&
> >
> > Archive doc. ID         <==     &IMAGE.ARCHIVEDOCID&
> >
> > Document type           <==     ZIAPINER02
> > Description             <==     Invoice Processing
> > Document class          <==     FAX
> > _WI_Object_Id           <==     &IMAGE&
> >
> >
> > Here is the WF Document Type(ZIAPINER02) definition: (SOA0)
> >
> > Document type   ZIAPINER02
> > Description        A/P Services Maintenance Invoices - Park
> > Process type      NCI_INPUT
> > Object type        BKPF
> > Method              CREATE
> > Task                  nothing here
> >
> > We have applied following OSS Notes:
> >         85778  TS7869: no link after document type changed
> >       94502  Two work items after document type changed
> >
> > But the problem remains.
> >
> > Thanks, Yan
>