Payment Block On Vendor Invoice

[Stevens, Seth]

Thanks for the responses.  To answer your question Mike, there is
document simulation that runs to check the invoice before posting.  If
there are any errors we do not attempt to post the invoice and use
advance with dialog to immediately display the errors to the user.
Setting the payment block is a part of this simulation step and needs to
happen before posting so that the user can review.
 
We have developed a work around that we think will be acceptable.  It
will break advance with dialog for a very small percentage of work items
but we somehow got the users to agree.
 
Thanks for the help!!!

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Edward Diehl
Sent: Tuesday, June 05, 2007 12:12 PM
To: SAP Workflow Users' Group
Subject: RE: Payment Block On Vendor Invoice


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.


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





-----------------------------------------
*Please note my E-Mail Address has changed.  Please update your
contact list*

Anadarko Confidentiality Notice:  
This electronic transmission and any attached documents or other
writings are intended only for the person or entity to which it is
addressed and may contain information that is privileged,
confidential or otherwise protected from disclosure.  If you have
received this communication in error, please immediately notify
sender by return e-mail and destroy the communication. Any
disclosure, copying, distribution or the taking of any action
concerning the contents of this communication or any attachments by
anyone other than the named recipient is strictly prohibited.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20070605/fdc2f130/attachment.htm