Document Imaging & Workflow

[Jody Chassereau]

Thank you Brian for your response.  I think I understand, but let me make
sure.  If we are dealing with 3 tiers (dev, QA, prod) and we want to
maintain separate archives for each, it is possible for me to create them
all in dev and transport them up.  Then I would need a separate transport
dealing only with pointing all the doc types to QA (and then one for
everything to prod).  My only problem with this is the transport strategy
here usually goes through all 3 - where this would need dev->QA only and
dev->prod only.  Is this correct?
 
Thanks...
 
 
>From: Brian Bennings <bennings.bj at pg.com>
>Reply-To: SAP Workflow Users' Group <SAP-WUG at MITVMA.MIT.EDU>
>To: SAP-WUG at MITVMA.MIT.EDU
>Subject: Re: Document Imaging & Workflow
>Date: Thu, 13 Sep 2001 09:49:59 -0400
>
>Hello Jody,
>
>All of this configuration is transportable.  We move the configuration from
>our
>dev system to all non production systems using the same logical archive.
>However, for the production systems, we have a separate transport that
>changes
>the logical archive (through OAC3) so that we can separate prod and
>non-prod
>images.  Note that all of this configuration is client dependent, with the
>exception of the logical archive itself (through OAC0).
>
>Brian
>
>
>
>
>  Internet Mail Message
>  Received from host:      cherry.ease.lsoft.com
>  [209.119.0.109]
>
>
>
>From: Jody Chassereau <drcakes at hotmail.com>@MITVMA.MIT.EDU> on 09/13/2001
>09:39
>AM AST
>
>  Jody Chassereau <drcakes at hotmail.com>           To:
>SAP-WUG at MITVMA.MIT.EDU
>                       @MITVMA.MIT.EDU>           Cc:    (bcc: Brian
>Bennings-BJ/PGI)
>                                          Subject:      Document Imaging &
>Workflow
>
>                 Sent by:  SAP Workflow
>         <Owner-SAP-WUG at MITVMA.MIT.EDU>
>                    09/13/2001 09:39 AM
>        Please respond to "SAP Workflow
>                          Users' Group"
>               <SAP-WUG at MITVMA.MIT.EDU>
>
>
>
>
>
>I'm hoping that someone in the workflow group that has set up configuration
>in conjunction with document imaging & ArchiveLink can help answer this
>question for me.  Now that we have a process in place in our development
>system that seems to meet most of our needs, I need to move up the process
>to our QA environment.
>
>What I am wondering is: do you (or can you) use transports to define your
>ArchiveLink configuration in other systems?  It is generally our policy to
>not open up config, but it seems that may be the only option here.
>Specifically I am referring to entries created under OAC0 (defining the
>archive id), OAC3 (links to document types), OAC2 (maintaining global
>types), SOA0 (maintaing doc types), etc.  If there can only be one
>archiveid
>defined for a document type, do you have to recreate everything in QA/prod
>to point to the applicable archive?
>
>I hope this makes sense.  Just wondering how others have dealt with this.
>I
>know some things like SM59 for the RFC destination can just be set up
>directly without any problem.  Please pass on suggestions if you have
>worked
>with this.
>
>Thanks in advance...
>Jody Chassereau
>drcakes at hotmail.com
>
>_________________________________________________________________
>Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
 
 
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp