Chat now with support
Chat with Support

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

Oracle Applications Tab

The Oracle Applications tab feature tools that connect directly to your environments and file servers. Because the functionality behind these tabs is specific to a development environment, they are also service domain-specific. When defining a service domain, your system administrator determines which change management tab, if any, is displayed on its CSRs. Access to these tabs should be restricted to developers and migrators. For more information on security settings, see the Stat System Administration Guide, Chapter 3, “Stat Security.”

In order to associate objects with a CSR, you must specify the environment you want to copy them from. This is done first by opening the CSR window and selecting the Migration Path tab.

Selecting Migration Paths

In Quest® Stat®, migration paths are logical groupings of environments that serve as road maps for object migrations. They are set up by your system administrator.

Your system administrator creates migration paths based on your Business needs. For different situations you have different paths.

2
In the Migration Path drop-down, select the appropriate migration path. The displayed paths vary, depending on the service domain. You should select the path most suited to your current needs.
3
Click the Select Default Developer field and select the developer assigned to most of the objects in the CSR. You can assign different developers to different objects, but this is the person that the objects are assigned to by default.
Note that if your selected Workflow has a default VCM Repository assigned to it, that VCM Repository will automatically be assigned on the migration path.
5
Click Generate Path.

Each drum represents an Oracle Applications environment. This includes the file directories that the environment uses for each of the defined file types. Your system administrator determines which environments are designated as Base and Development. The original, “pre-change” archive of the objects in the CSR is taken from the Base environment and its designated source file locations. The Development environment is where you change the objects.

For more information, see About Archive Sets .

After selecting a migration path, select the Objects tab.

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.

2
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.
3
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:

2
Click in the Environment field and select any environment other than Working Directory that contains the objects.
3
Click in the Object Type field and select the type of setup object you want.
Stat displays object types sorted by object class. If Filter column is checked in Stat Object Type Maintenance, user is presented with an Additional Parameter dialog in order to optionally select additional filters. Stat queries the selected environment and fetches any matching setup objects.

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

2
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.

2
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.
3
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.
4
(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 .
6
Click Add Object.
7
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.

3
Click Verify to check the validity of your equation.
4
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating