Stat 6.2 - User Guide

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.

Selecting Data and Schema Objects

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

To select a data, or schema object:

In the CSR window, select the Objects tab.

Click in the Environment field and select the environment that contains the objects.

Note that any environments on the migration path that have been inactivated are not listed. If you need to select objects from an inactive environment, see your system administrator.

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.

Stat gives you this option of environments in order to reduce the number of hits made against your Base, or Production, environment. By selecting another environment, Stat connects to that environment and retrieves the list of objects. Once the objects are selected, the “pre-change” object snapshot is created 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.


	NOTE: If you are adding a schema object type, Stat displays the Select Schema Owner window, which prompts you to specify the object’s schema owner. This reduces the amount of time it takes for Stat to return the list of matching objects. The window includes a Quick Filter field which lets you quickly parse the list to the schema owner you want (including Public). Select the owner and click OK.

Stat displays object types sorted by object class. When you select an object type, Stat displays a list showing all available objects of that type.


	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.

In the list of objects, select the object(s) you want. To select multiple objects, hold down the <Shift> or <Ctrl> key as you make your selections.

Selecting Setup Objects

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:

•

Archiving and migrating the setup object type Workflow Item Type is not supported in Stat. Instead, the WFT File object type should be used to archive and migrate Oracle Workflows. The Workflow Item Type object type is only used with Patch Impact to display the impacted workflow item types when a patch modifies a WFT file.

•

For setup objects that include an application field, Stat returns only objects for installed, shared, or customized applications

•

Stat supports archiving and migrating Key Flexfields. However, once the Key Flexfield has been used in Oracle Applications, it should not be modified or migrated in Stat.

To select a setup object:

In the CSR window, select the Objects tab.

Click in the Environment field and select any environment other than Working Directory that contains the objects.


	NOTE: Any environments on the migration path that have been inactivated are not listed. If you need to select objects from an inactive environment, see your system administrator.

Setup object definitions are not supported in users’ working directories.

Click in the Object Type field and select the type of setup object you want.

Stat displays object types sorted by object class. Stat queries the selected environment and fetches any matching setup objects.

In the list of setup objects, select the object(s) you want. To select multiple objects, hold down the <Shift> or <Ctrl> key as you make your selections.


	CAUTION: Stat currently supports setup objects with names less than 200 characters in length. Any objects that exceed that limit will not be returned.


	NOTE: For multi-language environments, a list of supported languages display. You may select one or more languages for the object to be added to the CSR. Non-US records will automatically be assigned a higher migration order than the US records in the base archive set.

Selecting Patch Objects

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

To select a patch object:

In the CSR window, select the Objects tab.

Click in the Environment field and select Patch Inventory.

In the Object Type field, Standard Patch is automatically selected.

In the list of patch objects, select the object(s) you want. To select multiple objects, hold down the <Shift> or <Ctrl> key as you make your selections.

Selecting File Objects

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

To select a file object:

In the CSR window, select the Objects tab

Click in the Environment field and do one of the following:

•

Select an environment if you want Stat to look through that environment’s source file locations to get the list of file names for a particular file type. Source file locations are the file server directories where file objects reside. Your system administrator can define multiple source file locations for each environment.

•

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.


	IMPORTANT: In the case of OAF file objects, Stat also adds 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 (as described below).

•

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.

Note that any environments on the migration path that have been inactivated are not listed. If you need to select objects from an inactive environment, see your system administrator.

Click in the Object Type field and select the type of file you want.

The list displays both the proprietary file object types that Stat supports by default and any generic and custom file types. If you select a custom file type, you are prompted to specify the product and language of the object type (certain custom file types are defined without a language, in which case you are only prompted to specify a product). After selecting the product and language, click Fetch.


	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.

Stat displays a list of all the files that have the matching file extension. No file names are returned if there are no source file locations defined for the selected file type and environment, if no working directory has been defined for the assigned user, or if no matching objects reside in the VCM repository.

Also, when adding objects from the assigned user’s working directory, Stat retrieves the objects based on their file extension. However, certain Oracle file object types share the same extension (such as SQL Reports and SQL Scripts), which means that Stat returns all the objects for both object types. A similar issue occurs with generic file objects of the same type, but for different products or different languages. When you add generic files from a working directory, Stat lists all the files of the matching type for all products and languages.

(Optional) Select Copy to Working.

If selected, Stat copies the files from the base environment to your working directory after adding them to the CSR.


	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 .

In the list of files, select the file(s) you want.

Click Add Object.

Stat adds the selected objects to the object list. At this point, you must save your CSR in order to lock the objects.

Click OK.

Click the Save button on the Stat toolbar or select File | Save.


	CAUTION: Be careful when you associate a file object with a CSR if (1) your system administrator has defined migration paths for an Oracle Applications environment and either a PeopleSoft or a generic application environment, and (2) the source file locations are the same in both environments. Stat allows users operating in different modules to associate the same object to a CSR at the same time, which could result in developers overwriting each other’s work.

Filtering the Object List

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.

To filter the object list:

In the Objects tab, click Filter.

This opens the standard Specify Filter dialog box

Create a filter equation using the Operator tool buttons and statements listed in the Functions and Columns fields.

Click Verify to check the validity of your equation.

Stat displays a message box telling you if your equation is valid or not.

Click OK.

The Objects tab now displays a “Filter On” notification and the number of objects currently hidden by the filter. Any objects you add to the CSR while a filter is on may be hidden from the list of objects.

Optionally, if you want to save the filter for the next time you open the CSR, select the Save Filter option.

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 .


	NOTE: It is recommended that you keep the default lock setting, All on Migration Path. Locking only in the current environment could lead to version inconsistencies if another developer modifies the same object in a different environment.

Table 1. Lock options
Option	Description
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.
None	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). NOTE: When you add an object to a CSR without a lock, Stat does not create a base version for the object(s) or mark the object(s) as having been modified. The object(s) are therefore considered “Undocumented” by the Undocumented Object Wizard.
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

To add 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.

This enables Stat to finalize your object locks.

While the Stat Central Agent processes the locks, the Archive Sets 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.


	NOTE: If the message does not go away after certain amount of time this may indicate that the agent encountered a problem or timed out.

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:

•

Verifies the object is not already on the list of objects associated with the CSR

•

Checks for any existing locks or reservations for the object by other CSRs

•

Checks for the object’s existence by searching in each source file location defined for each environment along the migration path. If no source locations have been defined for the file type in any of the environments on the migration path, Stat cannot add the object to the CSR.

•

Adds the object to the CSR and locks it

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

Selecione seu produto:

Para podermos atendê-lo melhor, informe o Propósito de seu chat:

Soluções recomendadas para seu problema

Stat 6.2 - User Guide

Assigning Developers

Selecting Objects

Selecting Lock Options

Adding Objects