Chat now with support
Chat with Support

Stat 6.1 - 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

Assigning Developers

Before adding the objects to the CSR, you need to decide which Quest® Stat® user is going to be making the changes to the objects and therefore needs to be assigned the object lock. If the user is the default user in the Assigned To field, then you can just add the objects and the default user will obtain the lock. If another user needs the lock on the objects, select that user from the drop down list in the Assigned To field. When you add the objects, the user in this field is assigned the object locks. For more information, see Selecting Lock Options .

Selecting Objects

You can select the objects you want to add to your CSR manually, or you can use the wizards to select groups of objects. The procedure for manually selecting the objects you want to associate with your CSR is slightly different depending on the class of objects.

NOTE: Workflows can contain status rules that do not allow users to add or lock objects while the CSR is in a restricted status. When this is the case, Quest® Stat® prevents you from adding or locking objects until the CSR changes to an unrestricted status. Any object reservations that were in place before the CSR was transferred to a restricted status, however, are treated the same, meaning they are converted into locks when the objects become available.

To select a data or schema object, first select the Oracle® Applications environment, then the object class and the object type.

Click in the Environment field and select the environment that contains the objects.
The initial object snapshot, the base archive set, always comes from the Base environment. No matter which environment you select in the Environment field, Stat copies the objects from the Base environment. Even if you add objects later, they still come from the Base environment.
When you select an environment, the Object Type field displays a “Loading...” message. During this time, Stat connects to the selected Oracle Applications environment and checks which object types are available.
Click in the Object Type field and select the type of object you want.
TIP: If Stat returns a large number of objects, you can quickly locate the particular object you want by typing the first few letters of the object name in the Quick Filter field. As you type, Stat filters the list of objects so that only objects with matching names are displayed.

Stat supports a number of predefined setup object types by default. Although you can archive and migrate most any supported type of setup object, be aware of the following considerations:

Click in the Environment field and select any environment other than Working Directory that contains the objects.
Click in the Object Type field and select the type of setup object you want.

You can associate with a CSR any Oracle Applications patch that has been uploaded to the Stat Repository.

Click in the Environment field and select Patch Inventory.
In the Object Type field, Standard Patch is automatically selected.

To associate file objects with a CSR, you first select the Oracle Applications environment and the type of file object you want.

Click in the Environment field and do one of the following:
Select Working Directory if you want to add files that exist in the assigned user’s working directory but not in any of environments to which Stat has access.
Select VCM Repository if you have associated the CSR with a VCM record and you want to archive and migrate objects that reside in the VCM repository.
Click in the Object Type field and select the type of file you want.
IMPORTANT: If the Oracle Agent is not running when you click Fetch, Stat is unable to process the request and displays a warning message. When this is the case, re-start the agent and click Fetch again. Also, for Stat to locate a user-defined file object, the name of the object must begin with the name of the product it is associated with. See section, Creating File Objects for more information.
(Optional) Select Copy to Working.
NOTE: This option is selected by default if the Copy Files to Working option is selected in the Stat User Options window. For more information, see Removing Objects from a CSR .
Click Add Object.
Click OK.

If you have added a large number of objects to a CSR, you can filter the list of objects so that only the objects you want to view are visible. You can then save the filter settings so that the object list remains filtered the next time you open the CSR.

Click Verify to check the validity of your equation.

Selecting Lock Options

After you select the object(s), you should decide which locking options to use. Your ability to change locking options is determined by security settings. For more information on object locking, see The Object Locking Process .

Table 1. Lock options

All on Migration Path

The default setting. Select this option to add and lock/reserve the object(s) in all environments. Stat searches in each environment to determine if the object is already locked or reserved on another CSR.

Current Environment

Select this option if you want to add the object from each environment on the migration path but lock/reserve the object(s) only in the current environment. Stat checks for reservations and locks/reserves the object(s) only in the current environment.


This option adds the object(s) to the CSR from each environment on the migration path without issuing a lock on any of them. Although you can archive an object that is not locked in an environment, you cannot migrate the object to an environment in which it is not locked. You should select this option if you are associating the object(s) to a CSR for documentation purposes only, and you are not going to make any changes to the object(s).

Reserve if locked

This option automatically requests a reservation if the object(s) are locked by another CSR. If this box is not checked and the object(s) are locked by another CSR, Stat prompts you for an action.

Adding Objects

After you select the object(s), locking options, and assign a developer, click Add Object, or double-click on the object(s), or drag and drop them into the Object List field.
At this point, if you selected the lock options All on Migration Path or Current Environment, Stat connects to the environment(s) and adds the selected objects to the Object List. If Stat is unable to connect to one or more environments, it displays a warning message for each environment it failed to connect to and adds the object to the CSR without a lock.
Click Save on the Stat toolbar or select File | Save.

While the Stat Central Agent processes the locks, the Object Management tab goes into read-only mode and the following occurs:

The Read CSR button is temporarily replaced by a message indicating how many objects are left to process.
The Workflow tab and certain CSR fields are disabled both in the Stat Windows client and in Stat Web. These include the CSR Type, Application, Status, and Workflow fields. This is done to prevent users from modifying the CSR while the Stat Central Agent is still processing data.

For each object, Stat then:

When adding an object, Stat connects to all environments on your migration path in order to verify modification status. If it finds an object that exists in another environment, but not in the environment from which you are working, it displays an advisory message.

TIP: You can update the lock status of objects displayed in the Object List table by clicking Refresh. This will show if you any of the reserved objects have since received a lock since the last time you saved the CSR.

When Stat adds the object to the CSR, a row for each environment on the migration path is added to the Object List table. Each row displays information concerning the development, archiving, and migration activity that takes place for that object in that environment. For more information on the Object List table, see CSR Object Documentation (Oracle Applications) .

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating