Chat now with support
Chat with Support

Stat 6.0 - User Guide

Introduction to Stat Connecting to Stat Change/Service Requests Stat Consoles Tasks and Time Entries Stat Projects Search Engines Reports and Graphs Personal Rules Object Tools and Wizards Change Management for PeopleSoft
Object Management (PeopleSoft) Object Archives (PeopleSoft) Object Migrations (PeopleSoft)
Change Management for Oracle Applications
Object Management (Oracle Applications) Patch Management Object Archives (Oracle Applications) Object Migrations (Oracle Applications)
Change Management for Generic Applications
Object Management (Generic Applications) Object Archives (Generic Applications) Object Migrations (Generic Applications)
Appendix: Troubleshooting Chart Appendix: Migration Options Appendix: User-Specific Parameters Appendix: Supported PeopleSoft Proprietary Objects Appendix: Stat Reports

Creating Archive Sets (PeopleSoft)

As you make your changes to objects, you should periodically make interim archive sets. This lets you save your work at that point in time. When all your changes are completed and approved, you should make a final archive set. The procedure for both is the same.

2
In the Type field select the type of archive set you want to create. Your options include Interim and Final. Base sets are automatically created by Stat.
3
In the Environment field select the environment containing the objects you want to include in the archive set.
4
In the Description field enter a short description of the changes you made to the objects.
Select Environment if the source environment is Development and you want to take the file archives from the environment’s source file locations
Select Working if the source environment is Development and you want to take the file archives from the assigned user’s working directories. Or select No if you want to take the archives from the source file locations of Development.
Select VCM if you have associated the CSR with a version control management record and you want to take the file archives from the VCM repository. After selecting this option, a VCM-specific field is displayed (Revision for SVN and P4, Tag/Branch for CVS and Git, Label for PVCS, and Version for TFS). In this field you can specify the particular version of the objects you want to add from the VCM repository. Your system administrator may have configured a default value, but you can override it either by entering the version you want manually or by clicking the control button and selecting the version from the dropdown list. If left blank, Stat adds the most recent version of the objects in the repository.
Stat goes out to the source environment and looks for the object. If it finds the object it displays the value Yes in the corresponding Exists field. If the object does not exist, Stat displays the value No. Objects that do not exist in the source environment cannot be included in the archive set.
If the CSR has managed a PeopleSoft project, then the Synchronize PeopleSoft Ugrade/Action flags option would appear. When the option is selected and objects are included to the PeopleSoft managed project, the Stat Central Agent will synchronize the Upgrade/Action flags against the dev environment.
11
Click OK.

Archive Set Object Information

To see the details of your archive set, double-click on the new row in the archive set table. This re-opens the Archive Set window. The Details tab should look familiar since this is the tab you filled out when you created the archive set. The next tab, Objects, now contains all of the object information for the archive set.

The Objects tab displays the following information:

N/A. Oracle Applications only.

Indicates the class of object. Archivable object classes include PeopleSoft proprietary, data, schema, and file.

The object type.

The object name.

A version number internal to Stat. It indicates the number of times the object has been modified/archived in Stat for a given environment.

Reflects the current status of the object. Possible statuses include:

Archived – Indicates the Stat Central Agent finished archiving the object
Archive Pending – Indicates the Stat Central Agent is in the process of archiving the object
Wait Lock – Indicates the Stat Central Agent is in the process of locking the objects. You can archive only locked objects.
Delete Pending – Indicates the Stat Central Agent is in the process of deleting the objects
Re-archive Pending – Indicates the Stat Central Agent is in the process of archiving the object again

Indicates the number of errors found. See the Logs window for further details.

Indicates the number of warnings found. See Logs window for further details.

If the object is a PeopleSoft proprietary object, this field shows the number of tables and rows in Stat used to complete the archive. If it is a file object, the field shows the exact file location of the archive source in the archive set.

This information is displayed at the bottom of the window. It shows the total number of objects in the archive set and how many of these have been archived.

The Objects tab features the following short cut buttons:

Add – Adds selected objects to the archive set. Click this button and Stat displays a list of the objects.
Delete – Deletes all of the objects in the selected archive set. You cannot delete objects from a base or final archive set.
Re-Archive – Re-archives the objects
Refresh – Refreshes the current display
Print – Prints the contents of the window
Export – Exports the contents of the window
Default Order – N/A. Oracle Applications only.
Reorder – N/A. Oracle Applications only.
View – For file or schema object types only, displays the definition of the selected object in a separate window.

Modifying Object Upgrade and Action Values

After PeopleSoft proprietary objects have been archived in an archive set, you can modify their default Upgrade and Action values. You can change an object’s Upgrade value to “do not upgrade” and its Action value from “copy” to “delete.” Then, when you migrate the archive set, you have the option of using a Stat-created PeopleSoft project, in which case the project uses the objects’ Upgrade and Action values specified in the archive set.

Be aware the Upgrade and Action values for objects specified in the archive set are only used in a migration when a Stat-created PeopleSoft project is used. They are not used when you use a PeopleSoft project contained within an archive set to perform the migration. In this case the Upgrade and Action values are set at the time you archived the project definition, and the Upgrade and Action settings in the archive set are ignored. For more information, see Migration Overview .

Stat lets you delete unwanted objects from selected PeopleSoft environments on a migration path. After adding the unwanted objects to an archive set, you can mark them for deletion. When you migrate an archive set containing objects marked for deletion to an environment, Stat deletes them from that environment. However, you can always recover deleted objects since they remain archived in the Stat Repository.

3
In the Action field, change the setting to Delete.
4

If you decide that you do not want to delete an object marked for deletion before you migrate it, go back to the Migration Flags tab and in the Action field change the setting to Copy. Stat is now configured to migrate the object as it normally would by placing a copy of the object in the target environment rather than deleting it.

When you first add an object to an archive set, the Upgrade option is selected by default, as indicated in the Migration Flags tab. You can de-select this option for any object in an archive set. When the object is migrated to an environment, the PeopleSoft project created by Stat in the staging database includes the object’s modified Upgrade value.

3
Select or de-select the Upgrade option for each object you want.
4
Click Ok to save the CSR.

For PeopleSoft version 8.x, Stat supports subobjects of Record and Field object types (Record Fields for Records and Field Labels for Fields). Adding a subobject to an archive set allows you to modify its values separately from the values of its parent object. For example, in a PeopleSoft patch or upgrade, a Record object definition might have a CopyProp Action value, while one of its Record Field subobjects might have a Delete Action value.

For more information on associating subobjects to CSRs, see Associating Related PeopleSoft Proprietary Objects .

By default, all subobjects are marked Upgrade with an Action value of Copy (unless associated to the CSR by means of the Read Project Wizard, in which case they retain the values specified in the project).
The default Action value of parent objects is CopyProp. This indicates that PeopleSoft will take action on just the property of the parent object, and it will look to the individual subobject for what action to take - Copy or Delete. This is primarily used when a user is trying to delete a field from a record, or trying to add new fields.
If a user overrides the default value CopyProp of a parent objects and sets it to Copy, then all of the subobjects will be copied, regardless of the flags set on them.
4
For each subobject that you want to change the Action value, click in the Action column and select Delete or Copy depending on the action you want taken on the subobject. 
5
Click Ok to save the CSR.

Copying Archive Sets

When you copy an archive set, the copy retains the migration order and any object upgrade and action values set on the source archive set.

3
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating