LIV 'R' block workflow reqmnt in R/3 4.7

[John A Haworth]

Hi Mark.

The R block that we are looking at though can be due to price, quantity or 
quality variances, WS20000397 only looks at price. The workflow has to 
determine the responsible person, for each type of variance, but the 
concept seems the same.

Cheers
JOhn


----------------------------------------------------------------------------------------
This is a PRIVATE message. If you are not the intended recipient, please 
delete without copying and kindly advise us by e-mail of the mistake in 
delivery. NOTE: Regardless of content, this e-mail shall not operate to 
bind CSC to any order or other contract unless pursuant to explicit 
written agreement or government initiative expressly permitting the use of 
e-mail for such purpose.
----------------------------------------------------------------------------------------





"Mark Pyc" <mark.pyc
@gmail.com>
Sent by: sap-wug-bounces
18/07/2006 17:11
Please respond to "SAP Workflow Users' Group"
 
        To:     "SAP Workflow Users' Group" <sap-wug at mit.edu>
        cc: 
        Subject:        Re: LIV 'R' block workflow reqmnt in R/3 4.7


G'day John,
 
What's wrong with the loop concept as shown in the standard Price Block 
flow WS20000397?
 
Why reinvent the wheel?
 
Have fun,
Mark

 
On 7/18/06, John A Haworth <jhoworth at csc.com> wrote: 

Hi everyone. 

Can anyone offer advice. I want to create a new workflow that is looking 
for an R block invoice. The event is issued when the invoice is first 
posted, thats ok. But if there are multiple reasons for an R block ie due 
to price and quantity, clearing only one of the problems and trying to 
re-post, correctly the invoice is still R blocked. BUT the event isnt 
re-issued (and i need to restart the workflow in order to find the next 
person responsible for the next reason of the R block). 
My question, is there a user exit or BADI on the Posting of a LIV invoice 
which I could use to reissue the same event if an R block still exists. 

Any advice welcome. 

Thanks 

John


---------------------------------------------------------------------------------------- 

This is a PRIVATE message. If you are not the intended recipient, please 
delete without copying and kindly advise us by e-mail of the mistake in 
delivery. NOTE: Regardless of content, this e-mail shall not operate to 
bind CSC to any order or other contract unless pursuant to explicit 
written agreement or government initiative expressly permitting the use of 
e-mail for such purpose. 
----------------------------------------------------------------------------------------

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug


_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20060719/a399274f/attachment.htm