FW: Document Imaging Setup

[Narducci, Mike]

Jody,
        We do what you are looking for, but use several small Z-tables to route
the initial workflow to the appropriate A/P clerk's inbox, to service entry
approvers, etc.  At this point our org structures were not set up to the level
required for workflow processing without the maintenance headache you talk about
(too flat, at the cost center).  We gave a presentation at the St. Louis ASUG
meeting last March 20 which details our process (the presentation is posted on
ASUG.com with the meeting info.
Mike Narducci
MIS Consultant
SAP Applications
 
-----Original Message-----
From: Jody I. Chassereau [mailto:JICHASS at westvaco.com]
Sent: Monday, July 23, 2001 1:53 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Document Imaging Setup
 
 
I am beginning work on a project dealing with document imaging.  We will be
working on configuring ArchiveLink to take scanned invoices and route them to
processors for SAP entry.  I have help on ArchiveLink, but the workflow falls on
me.
 
My question to anyone familiar with this deals mainly with transaction OAWS
(Presettings to document types with end user's Inboxes).  Let's say we have 5
different document types we are dealing with.  We want the flexibility to route
a scanned document to a specified person (at scan time) in a group of multiple
processors.  When you set up OAWS, you can specify a userid, position, job, etc.
I have not worked with org structures (we use custom tables for our other
workflows), but I thought that maybe this would make sense to define a small
structure here for defining the processor group.  If I used position linked to a
document type, then you could send it to multiple people, but that is not what
they want.  I can specify userid instead, but doesn't that mean the maintenance
of persons involved is now in the customizing?  I need the flexibility of
choosing userids at scan time AND be able to allow the user group to maintain
the list of processors (when people join or leave the group).
 
I was hoping that someone on this list may have worked with such a project and
could explain my options on the setup of the people involved.  Do I need org
structure in place?  Do I set up the basic structure and can a user maintain the
assignments of person to position?  It defeats the purpose if I have to maintain
the structure in production.  This seems like it should be easy, but I'm having
trouble understanding the proper way to do this.
 
Any advice would be appreciated.  Thanks...
 
Jody Chassereau
jichass at westvaco.com