infinite loop of TS7869 (ImageAssign)

[Liu, Yan Y SSI]

Felix,
 
Thanks for the information.  It's a big help.  However, I am in version 3.1h
which doesn't have the WF wizard.  How do I get a copy of the WF replacing
TS7869 for 3.1h?  ... contact SAP?
 
Regards,  Yan
 
> -----Original Message-----
>> From: Hassine, Felix [SMTP:Hassine.Felix at PMINTL.CH]
> Sent: Thursday, January 27, 2000 8:48 PM
> To:   SAP-WUG at MITVMA.MIT.EDU
> Subject:      Re: infinite loop of TS7869 (ImageAssign)
>
> Yan,
>
>         I have had similar problems a few months ago. After a strong
> debugging, I havce realized that the terminating event for the TS7869 is
> not
> receiving the proper IMAGE key, on purpose. The TS7869 is async, and
> requires the key of the image to terminate, but instead it receives the
> key
> of IMAGE + an append of the document CLASS. After opening a OSS note,
> someone in Walldorf - on the phone - said to me that TS7869 is not
> supposed
> to be used inside a WF. For this, they have created a wizard which
> generates
> you a full WF replacing the functionality of TS7869.
>
> This is the one you should use, as a SubFlow in your workflow. I did, and
> it
> worked. I hope this helps.
>
> Regards,
>
>         Felix
>
> > -----Original Message-----
> > From: Liu, Yan Y SSI [SMTP:YD186300 at MSXSSC.SHELL.COM]
> > Sent: Thursday, January 27, 2000 8: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