Automated A/PApproval Process

[Griffiths, Mark]

It all depends on the the business scenario Greg - some customers do not use
the park functionality, others do.  If you want to use the standard Invoice
Parking functionality this will also not be very effective when linked to a
scanned image as your triggering events will occur at the wrong time.
 
The simplest solution is to start the workflow directly from the scanning
and present the user with the park document transaction in the first step.
You can then implement oss note 336305 to get the terminating event
triggered for FIPP or BKPF Created using the Open FI Interface.
 
The invoice can then be approved using user decisions with the image
displayed in a secondary method.  Once the document is approved you can post
the parked document and link the scanned image to the invoice.
 
All of this with no additional FI config ...
 
With all these matters there is no right or wrong answers, the important
thing is that the workflow meets the business requirements.
 
Regards,
 
Mark Griffiths,
SAP UK
 
-----Original Message-----
From: Gregory Kowalik [mailto:gkowalik at ashland.com]
Sent: 12 June 2001 13:06
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Automated A/PApproval Process
 
 
Guys,
 
One of the reasons for having invoice parking functionality is to use the
approval process before the invoice is created and hits the books.
Keep in mind that an invoice can be waiting for approval for several days
and you don't want it to affect the books before it is verified.
So why would you go through all those steps other than using invoice
parking workflow?
Secondly, you do not have to use early archiving scenario, use whatever
suits you Wayne. Late archiving with bar codes would work as well.
 
Greg
 
 
 
 
 
"Griffiths, Mark" <mark.griffiths at sap.com>@MITVMA.MIT.EDU> on 06/12/2001
06:52:46 AM
 
Please respond to "SAP Workflow Users' Group" <SAP-WUG at MITVMA.MIT.EDU>
 
Sent by:  SAP Workflow <Owner-SAP-WUG at MITVMA.MIT.EDU>
 
 
To:   SAP-WUG at MITVMA.MIT.EDU
cc:
Subject:  Re: Automated A/PApproval Process
 
 
The only scenarios available as standard in SAP are single step early
archiving workflows.  It is possible using the Archiving workflow wizard
(OAWW) to create your own multistep approval workflows.  The processes
created are not that great but you can use the workflow as a basis for your
process.  I have done this at a number of clients, the sort of process has
been:
 
Scan image, trigger workflow,
Create invoice (displaying iage in a secondary method)
Link invoice and image using IMAGELINK object
Get invoice approved (displaying the image in a secondary method)
If rejected reverse invoice and send back for re-entry in a loop.
 
You can also extend this process to include document parking before the
actual invoice is created.
 
Hope this helps,
 
Mark
 
SAP UK.
 
-----Original Message-----
From: Carson, Wayne [mailto:Wayne.Carson at solvay.com]
Sent: 04 June 2001 17:40
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Automated A/PApproval Process
 
 
Hello Everyone,
 
In the next 6 months, we will be starting a new A/P approval workflow.  We
will be using an iXOS scanner for capturing the invoice information.  For
those familiar with iXOS, we will be using an early archiving scnerario.
The scanning of the invoice is done first followed by a workflow that
triggers the A/P payment transaction.  I know there are 2 different
transactions for payment, one of which is the Invoice Verification.
 
Today we go through an approval process.  I am assuming that it is based on
some sort of dollar amount.  We haven't done a formal requirements document
yet.
 
I would like to know what are the standard workflows that I should be
looking reviewing and if anyone has a skeleton project plan similiar to
this
project.  This is a high visability project and I want to make sure it
works
right the first time.  Is there anything provided "out of the box" with SAP
or do I have to build everything from scratch?
 
Thank you,
 
Wayne Carson
Solvay Information Technologies
713-525-4143