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

Objects in the Base Environment

There are several situations when an object may exist in other PeopleSoft environment or source file locations on the migration path but not in the Base environment. Since the initial archive of objects comes from the Base environment, these objects are not included in the base archive set.

Possible reasons an object exists in one environment but not in others are:

If you want to archive an object that does not exist in the Base environment, there are two different ways to do it for two different types of situations.

In the Object field select the object.
In the Lock in environment field select Current environment.
In the Object field select the object.
In the Lock in Environment field select All on Migration Path.

By choosing the second method, the objects that exist in the Base environment are included in the base archive set. Those that do not exist are not added to the base archive set. You can include these latter objects in any interim or final archive sets taken from the environment where they reside.

Stat cannot create a base archive set if the objects in your CSR do not exist in your Base environment. While attempting to locate the objects, Stat permanently displays the value In Process in the Status field of the Archive Set window, and it will be unable to complete the archive set. If this happens, create an interim or final archive set from the environment that contains the objects and use this archive set to update the other environments with the new objects.

Defining Working Directories for File Objects

When you are assigned a file object, Stat places a copy of that object in one of your predefined working directories. These working directories are defined either by a system administrator in a maintenance table, or you can define them yourself in the User Default Directories tab of the Stat User Options window.

The User Default Directories tab displays a list of the active file types defined in Stat for PeopleSoft environments. From here you can define your default working directory and a separate working file directory for each file type. Defining a working directory for a file type is optional. If a file type working directory is not defined, Stat places copies of the migrated file objects in your default working directory.

To set up a default working directory:

Select User Options | Stat Options. Then open the User Default Directories tab of the Stat User Options window.
Click in the Default Working File Server field and select the server for the default working directory.
In the Default Working File Path field, enter the path of the default working file location starting after the file server’s root or home path.
Click Apply or OK.
Select User Options | Stat Options. Then click the User Default Directories tab of the Stat User Options window.
In the Module field, select PeopleSoft.
Click either Apply or OK.

Associating Related PeopleSoft Proprietary Objects

Certain types of PeopleSoft proprietary objects are related to other PeopleSoft proprietary objects. Using default Stat settings, you must add these objects individually to your CSR. However, you can configure Stat to add these related objects automatically. You do this by selecting a user preference that prompts you for related objects whenever you add a supported object type. This feature behaves in a similar manner to the prompt in PeopleSoft when inserting objects into a project.

To configure Stat to prompt you to add related objects, select User Options | Stat Options. Stat displays the Stat User Options window. Select Prompt for PS Related Objects. If the option is not selected, Stat will not prompt for related objects and will not add them automatically.

For PeopleSoft version 8.x, Stat supports subobjects of Record and Field object types (Record Fields for Records and Field Labels for Fields). Associating subobjects allows you to modify their values in an archive set separately from the values of their parent objects. 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.

You should add subobjects to a CSR only when you need to mark their Upgrade and Action values separately from their parent objects. For more information, see Modifying Object Upgrade and Action Values .

PeopleSoft projects may also include ‘orphaned’ subobjects, meaning that the project does not include parent objects. If this is the case, Stat adds the parent objects automatically to the CSR when you add the orphaned subobjects through the Read Project Wizard (described in the following section, Associating Objects in PeopleSoft Projects ).

Parent objects added by Stat for orphaned subobjects are indicated by a red folder icon in the Flags column of the Object List. This is for informational purposes only. If for any reason you want to change the designation of a parent object in relation to orphaned subobjects, select the parent object, right-click and in the pop-up menu, select either Mark as parent for orphans to flag the object as a parent object or UnMark as parent for orphans to remove the flag.

NOTE: Once you select an object type, the Add button is activated and the Ignore button is deactivated. Also, you can use the Select All and Deselect All icon buttons to select or deselect all the listed object types.
(Optionally) Keep the Apply for all objects option selected if you want Stat to apply the same action you are currently specifying (Add or Ignore) to any other affected object being added to the CSR.

Associating Objects in PeopleSoft Projects

Stat can read a PeopleSoft environment and add all the PeopleSoft proprietary objects associated with a project to your CSR. This is done with the PeopleSoft Project Read Wizard. Use this wizard to associate multiple PeopleSoft proprietary objects to a CSR.

For PeopleSoft version 8.x, you can also use the Project Read wizard to read in the objects of a PeopleSoft patch (defined in terms of a maintenance project). This way, Stat automatically populates the Patch tab of the CSR with the information contained in the project, such as incidents and dependencies.

To read in a patch with the Project Read Wizard, the patch must be designated as a Maintenance Project in PeopleSoft. In addition, to display this information in Stat, the Patch tab must activated for the CSR.

For more information on the Patch tab, see Patches Tab .

On the Objects tab, click Read Project....
In the PeopleSoft database field select the environment containing the project.
Select Add project definition to CSR if you want to add the PeopleSoft project definition to the CSR, where it can be locked, archived, and migrated along with the other objects. A comment is automatically written for each object saying that it was added by way of the Read Project Wizard and the name of the project used to bring in the object. This allows you to track the project by name throughout the lifecycle of the CSR. For more information, see Archiving PeopleSoft Project Definitions .
Select Add only objects with a changed target status if the project contains an especially large number of objects and you want to decrease processing time by adding only the objects that have been modified to your CSR.
Select Overwrite properties for existing objects if you want to update the existing CSR objects’ upgrade and copy properties to reflect the objects’ upgrade and copy properties in the project. This will also update the subobjects and their properties.
Select Make selected project the CSR managed project if you want to keep the project’s object list as defined in App Designer synchronized with the project’s object list as managed in the CSR. Selecting this option enables you to quickly update the objects associated with a CSR via the Project Read Wizard whenever the project is changed in App Designer. For more information, see the following section Synchronizing Project Definitions .
Click Next>.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating