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

Removing Objects from a CSR

To remove objects from a CSR, select them and click Remove.

* 
NOTE: You should remove an object only if it was added to the CSR in error. Modified objects should remain associated with a CSR for historical purposes.

Objects in the Base Environment

Objects in the Base Environment

There are several situations when an object may exist in other Oracle® Apps 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:

•
You create a new object in the Development environment, which means it would not exist in any other environment
•
You work on an object that was previously created in the Development environment but not yet migrated to any other environment
•
You work on a new object that exists in the AUD, Demo, or System environment but not in any other
•
You create a new file object in your working directory, which means it would not exist in any other environment

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.

To add objects that do not exist in the Base environment:
1
On the Objects tab of the Change Management/Version Control window, select the environment in which the object exists.
2
In the Object field, select the object.
3
In the Lock in environment field, select Current environment.
To add objects that exist inside and outside the Base environment:
1
On the Objects tab of the Change Management/Version Control window, select the environment in which the object exists.
2
In the Object field, select the object.
3
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.

Quest® 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, Quest® 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 Oracle® Applications 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.

* 
NOTE: In the case of OAF file objects, Stat also copies files from any subdirectories in the assigned user's working directory. Be aware, however, that when migrating OAF objects into a working directory, the same subdirectories have to exist. Stat is not able to create them. This is also the case if the Copy to Working option is selected. See Associating Objects with CSRs (Oracle Applications) for more information.
To set up a default working directory:
1
Select User Options | Stat Options. Then open the User Default Directories tab of the Stat User Options window.
2
In the Module field, select Oracle Applications.
3
In the Default Working File Server field, select the server for the default working directory.
4
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.
5
Click Apply or OK.
To set up a file type working directory:
1
Select User Options | Stat Options. Then click the User Default Directories tab of the Stat User Options window.
2
In the Module field, select Oracle Applications.
3
In the File Type column, select the file type you want to have a working directory for.
This activates the text box in the corresponding Working File Server column.
4
In the Working File Server column, select the server that the working directory is on.
5
In the Working File Path column, enter the path of the working file location starting after the file server’s root or home path.
6
Click either Apply or OK.

Associating Objects from Other CSRs

You can use the Read CSR Wizard to add objects that are associated with another CSR.

To run the Read CSR Wizard:
1
On the Objects tab, click Read CSR.... Stat opens the CSR Read Wizard.
2
Click the Lookup button.
Stat opens the Search CSR Engine, which locates specific CSRs in the database based on the selected search criteria, including CSR number, customer, open date, department, and tracking number. For more information, see Search Engines .
3
Locate the CSR you want in the Search CSR Engine. Then click OK.
Quest® Stat® closes the Search CSR Engine and displays all the objects associated with the CSR in the bottom portion of the Read CSR Wizard.
4
Select the objects you want. Use the <Shift> and <Ctrl> keys to make multiple selections, or click Select All to select all the objects.
5
Click OK.
Stat adds the selected objects to your CSR. If the objects happened to be locked on the other CSR for the same environments specified in your CSR’s migration path, Stat reserves them on your CSR.
* 
NOTE: The assigned developer and lock options specified on the Objects tab of the CSR are applied to any objects added to the CSR by way of the Read CSR Wizard.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating