Using same work item for 2 different transactions??
Stephan Becker
stephan.becker at walldorftech.com
Tue May 9 11:11:50 EDT 2000
- Previous message: BDC and Status Management
- Next message: Purchase requisition events Hi Felix, The only thing I can think of is if you are using the value of the requisition in your realease strategy. I would change the classification entry from CEBAN-GSWRT (item value) to CEBAN-GFWRT (total value). Phil ______________________________ Reply Separator _________________________________ Subject: RE: Purchase requisition events Author: "Hassine; Felix" <SMTP:Hassine.Felix@PMINTL.CH> at US Date: 09/05/00 08:00 Philip, I have tried this , but it completely cancels the release strategy (i.e." the PR is not blocked any longer). Is there an additional trick ? Felix > -----Original Message----- > From: Kisloff, Philip (BE) [SMTP:pkisloff@dc.com] > Sent: Tuesday, May 09, 2000 2:39 AM > To: "Hassine; Felix" > Subject: RE: Purchase requisition events > > Felix, > > Not only do you have to check the flag in transaction OMGS, but > also the "OverReqRel" for document type in transaction OMEB. The > event created now belongs to business object BUS2105 (change from > BUS2009 for item level). > > Hope this helps > > Philip Kisloff > Deloitte Consulting > Oberwil-CH. > > > ______________________________ Reply Separator > _________________________________ > Subject: Purchase requisition events > Author: "Hassine; Felix" <SMTP:Hassine.Felix@PMINTL.CH> at US > Date: 08/05/00 11:32 > > > Hi all, > > We need to create 1 workflow instance when a purchase requisition > is > created with the blocking flag on. Only 1 should be started, but the > system > generates as many events as line items in the workflow. As a result, my > workflow may start several times, which is not the desired effect. > > I have tested the "overall" release button in the customizing (Purchase > Req > release Strategy), but then no event al all is then generated. > I have also attempted to create a "change" doc for change document class > "BANF" , but it works only for CHANGED status, not for CREATE. > > Has anybody experienced the same problem ? > > Thanks for any clue. > > Felix Hassine >
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
there are two ways: there is a setting in workflow customizing where you can
specify that subsequent items should be presented to the user immediately if
they are selected agents of both tasks. that way you would still have two
workitems, but have the user work on them in immediate succession.
the other one involves some coding. cut and paste both methods into a new
one. ensure you think about the transactional integrity. what should happen
if the user cancels the first step? what if it fails?
stephan becker
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU]On Behalf Of
Young, Serena
Sent: 09 May 2000 00:29
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Using same work item for 2 different transactions??
Can anyone tell me if it is possible to keep the same work item and execute
2 different transactions? I have a workflow that executes a task to take a
user to a change screen for an invoice (MR42). When they are ready to post,
I have to take them to MR44, which I do through another work item after they
have answered a dialog that they are "ready to post". Is there some way to
keep the same work item? Basically, is there any way to interact with that
user to get a response on whether they are ready to post, get their answer,
then post the document without leaving the current work item?
Thank You,
Serena Young
Phone (281)518-1772
Serena.Young at Compaq.com
- Previous message: BDC and Status Management
- Next message: Purchase requisition events Hi Felix, The only thing I can think of is if you are using the value of the requisition in your realease strategy. I would change the classification entry from CEBAN-GSWRT (item value) to CEBAN-GFWRT (total value). Phil ______________________________ Reply Separator _________________________________ Subject: RE: Purchase requisition events Author: "Hassine; Felix" <SMTP:Hassine.Felix@PMINTL.CH> at US Date: 09/05/00 08:00 Philip, I have tried this , but it completely cancels the release strategy (i.e." the PR is not blocked any longer). Is there an additional trick ? Felix > -----Original Message----- > From: Kisloff, Philip (BE) [SMTP:pkisloff@dc.com] > Sent: Tuesday, May 09, 2000 2:39 AM > To: "Hassine; Felix" > Subject: RE: Purchase requisition events > > Felix, > > Not only do you have to check the flag in transaction OMGS, but > also the "OverReqRel" for document type in transaction OMEB. The > event created now belongs to business object BUS2105 (change from > BUS2009 for item level). > > Hope this helps > > Philip Kisloff > Deloitte Consulting > Oberwil-CH. > > > ______________________________ Reply Separator > _________________________________ > Subject: Purchase requisition events > Author: "Hassine; Felix" <SMTP:Hassine.Felix@PMINTL.CH> at US > Date: 08/05/00 11:32 > > > Hi all, > > We need to create 1 workflow instance when a purchase requisition > is > created with the blocking flag on. Only 1 should be started, but the > system > generates as many events as line items in the workflow. As a result, my > workflow may start several times, which is not the desired effect. > > I have tested the "overall" release button in the customizing (Purchase > Req > release Strategy), but then no event al all is then generated. > I have also attempted to create a "change" doc for change document class > "BANF" , but it works only for CHANGED status, not for CREATE. > > Has anybody experienced the same problem ? > > Thanks for any clue. > > Felix Hassine >
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
More information about the SAP-WUG
mailing list