Parked Invoice - TIPS

[Mike Pokraka]

G'Day Phil,

The customising Tom described activates the Workflow flag on one of the
invoice tabs.

RLEASE resets the flag, making the "Post" button available again.
CHANGEPOST lets a user manually post it.
POST and POSTASYNCHRON are background methods for posting.

Between these four methods you have a variety of ways in which you can
manage your posting according to business needs.

Of course it is always possible for a customer to find a scenario not
covered by all this flexibility. In this case I recommend writing your own
ZCL_WF_PARKED_DOCUMENT class :-)

Oh, and yes users can change parked docs. This is a nice scenario for
field restrictions on change documents so that only certain changes will
restart the WF. I've done this with a custom class and it works well.

Cheers,
Mike


On Mon, July 9, 2007 3:18 am, Soady, Phil wrote:
> Hi WUGers
>
> I was looking for a couple of basic tips on Parked invoice and
> workflows.
> VERSION 4.6
>
> Assumptions:
> Main object is FIPP.
>
> Q1 ) If you wish to park invoices and have a workflow release them,
> what is the correct option in FV60.  There was SAVE, PARK, Complete and
> Post.
>
> q2) SWELS is on.
>     Complete and Park didn't result in an entry in SWEL.
>     Is there app config required ?
>
> q3  When the workflow does its stuff,  which method on FIPP results
> in the accounting document being posted for real.
>
> Q4) Can uses change parked invoices ?
>    Do I need to listen to events so that the running worklfow is shot
>    because a new one should start ?
>
> ANy other tips or suggestions you might have.
>
> thanks
> Phil.
>
> Phil Soady
> Solution Architect
> Netweaver Consulting
> SAP Australia
> M  +61 412 213 079
> F  +61 2 9957 7263
> mailto:phil.soady at sap.com
>
>
>
> _______________________________________________
> 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