<html>
<head>
<style>
P
{
margin:0px;
padding:0px
}
body
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body>
You could perhaps use a Secondary Method type AFTER, but I'm not sure that is executed by WF-BATCH. You might check that out.<BR>
<BR><BR>> Date: Tue, 5 Jun 2007 17:44:33 +0100<BR>> Subject: Re: Payment Block On Vendor Invoice<BR>> From: asap@workflowconnections.com<BR>> To: sap-wug@mit.edu<BR>> <BR>> Hi Seth,<BR>> <BR>> Let me get this right: is the posting also done in dialog? So if they have<BR>> auth to post then why not give auth to change? Or else could you not do a<BR>> background step after all the advance with dialog stuff?<BR>> <BR>> Otherwise fire an event and do a background update asynchronously in a<BR>> separate task.<BR>> <BR>> Cheers,<BR>> Mike<BR>> <BR>> On Tue, June 5, 2007 4:32 pm, Stevens, Seth wrote:<BR>> > All,<BR>> ><BR>> > Does anyone have any suggestions for the below scenario? We have a<BR>> > workflow used for approving and posting FI vendor invoices. Before the<BR>> > workflow posts the document we need to, possibly, set a payment block on<BR>> > the invoice based on some business rules.<BR>> ><BR>> > We have written a call transaction to set the block; however, in most<BR>> > cases the user does not have edit access so the call transaction won't<BR>> > work if running under the user's ID. We cannot set this as a background<BR>> > task because there is a requirement to have advance with dialog. I<BR>> > cannot find a function module to accomplish this and obviously didn't<BR>> > want to do a direct table update.<BR>> ><BR>> > Any help or ideas would be greatly appreciated!<BR>> ><BR>> > Thanks,<BR>> > Seth<BR>> ><BR>> ><BR>> ><BR>> > -----------------------------------------<BR>> > *Please note my E-Mail Address has changed. Please update your<BR>> > contact list*<BR>> ><BR>> > Anadarko Confidentiality Notice:<BR>> > This electronic transmission and any attached documents or other<BR>> > writings are intended only for the person or entity to which it is<BR>> > addressed and may contain information that is privileged,<BR>> > confidential or otherwise protected from disclosure. If you have<BR>> > received this communication in error, please immediately notify<BR>> > sender by return e-mail and destroy the communication. Any<BR>> > disclosure, copying, distribution or the taking of any action<BR>> > concerning the contents of this communication or any attachments by<BR>> > anyone other than the named recipient is strictly<BR>> > prohibited._______________________________________________<BR>> > SAP-WUG mailing list<BR>> > SAP-WUG@mit.edu<BR>> > http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> ><BR>> <BR>> <BR>> -- <BR>> Mike Pokraka<BR>> Senior Consultant<BR>> Workflow Connections<BR>> Mobile: +44(0)7786 910855<BR>> <BR>> _______________________________________________<BR>> SAP-WUG mailing list<BR>> SAP-WUG@mit.edu<BR>> http://mailman.mit.edu/mailman/listinfo/sap-wug<BR><BR></body>
</html>