Document Imaging & Workflow

[Sheth, Neeraja]

We do the same thing - transport the configuration upto Production with the correct archive, then change the configuration in Dev and Test to point to the dev archive.
 
Neeraja
 
> -----Original Message-----
>> From: John A Haworth [SMTP:jhoworth at csc.com]
> Sent: Thursday, September 13, 2001 10:11 AM
> To:   SAP-WUG at MITVMA.MIT.EDU
> Subject:      Re: Document Imaging & Workflow
>
> hi
>
> Previously I have achieved this by creating the correct entries in the Dev
> system (i.e. pointing at the Production archive) releasing the transport,
> and taking it through to production, then changing the config back in dev
> to point at the dev archive. (and do the same for QA but only transport
> those changes to QA)
>
> John
>
>
>
>
> Jody Chassereau <drcakes at hotmail.com>@MITVMA.MIT.EDU> on 13/09/2001
> 14:39:10
>
> 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:  Document Imaging & Workflow
>
>
> 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