Purchase requisition - collective release

[Márton Zsolt]

Hi all!
Yes, that was the problem, but I've get over that.=20
But, my life is not so easy:), because I still have some problems with =
the event linkage. It says, that the release code, as an import element =
is missing. ( Message OL 365) If I set the event linkage to "not change" =
my workflow is moving along.=20
Anyway, I can finish my workflow, but the wf administrator gets a lot of =
error message.
This problem is arising, even if I use the standard, with transaction =
ME54, single release, but only since I've been using the ZBUS2105, =
delegated to BUS2105.
Zsolt
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of =
Maorriyan
Sent: Monday, November 22, 2004 4:15 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Purchase requisition - collective release
 
You mean, after user executing the workitem, the work
item not move to outbox?
Check your workflow log. Just in case you found
something wrong. Alternatively, check something
complete check box in your task. This is to make user
the workitem is completly executed.
Actually this related with your task whether is
synchronous or asynchronous.
 
 --- Marton Zsolt <Zsolt.Marton at t-systems.co.hu>
wrote:
> Hi Maorryian!
> Thanks for your advice. I've copied the BUS2105 and
> I created a new method which is pointing to the
> transaction ME55. (with CALL TRANSACTION).
> It's working, but not correctly, so I still have a
> problem. You can reach the me55 and release the
> requisitions, but the work item it still remains in
> the user's inbox with the status 'in process' and
> the workflow is stopped. If you leave the me55 you
> will find yourself in the root menu and not in the
> SBWP.
> Anyway, I have a half solution by now.:) Do you have
> any further advice?
> Thanks
> Zsolt
>
> -----Original Message-----
>> From: SAP Workflow
> [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
> Maorriyan
> Sent: Thursday, November 18, 2004 2:43 PM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Re: Purchase requisition - collective
> release
>
> Hi Zsolt,
> Just modify your own BUS2105 (overall release) or
> BUS2009 (single release). Create a subtype to hold
> your new method for collective.
>
>  --- Marton Zsolt <Zsolt.Marton at t-systems.co.hu>
> wrote:
> > Hi all!
> >
> > We have 4.6c and a workflow for requisition
> release
> > where I'm using the standard task TS20000159. The
> > customer will is to release the requisition in the
> > transaction ME55 Collective release, and not in
> the
> > ME54. I know, in the task the method is
> > singlerelease, but I'm still asking: it's possible
> > that the standard (or whatever, a new) task to
> lead
> > the user into the transaction ME55?
> >
> > Any proposal is welcome.
> >
> >
> >
> > Regards
> >
> > Zsolt
> >
>
> =3D=3D=3D=3D=3D
> Maorriyan
>
>
________________________________________________________________________
> Yahoo! Messenger - Communicate instantly..."Ping"
> your friends today! Download Messenger Now
> http://uk.messenger.yahoo.com/download/index.html
>
 
=3D=3D=3D=3D=3D
Maorriyan
 
________________________________________________________________________
Yahoo! Messenger - Communicate instantly..."Ping"
your friends today! Download Messenger Now
http://uk.messenger.yahoo.com/download/index.html