The data for the baseline archive set is stored in the Stat repository. Oracle Apps objects are handled differently than PeopleSoft objects.
Stat has an internal set of object mover instructions that tell the Stat agent which tables to copy data from based on the PeopleSoft object type.
The user selects the environment to make the archive set from.
Only the baseline is created automatically and it is always created from the “Base” environment as indicated on the migration path. Subsequent “interim” archive sets are created from the environment that the user selects.
The create archive set window default to the “Dev” environment as most sites only modify objects in Dev.
However, the user can override that setting and select which ever environment they want to copy the data from.
They can take additional interim copies from the base environment if they wish to or if their business process indicates that they should.
Most sites specify the Production environment as base so that Stat will automatically take a copy of their “gold standard” when first starting a CSR.
As far as copying to the target, the user initiates the migration by selecting the archive set and dragging it to the target environment on the Stat Object Management tab. A project is written to the Stat staging db by the Windows client. That project is either created by Stat, or is contained inside the archive set. The Stat agent copies the archived data from the Stat repository to the Stat staging database, which is a PeopleSoft database of the same PS version created for use with Stat. When that process has completed, the Stat Windows client initiates PeopleSoft approved CLI statements to copy the project from the staging db to the target db.