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

Creating File Objects

With proper security rights, you can create a new file object, add it to a CSR, and move it to the assigned working directory of the developer. When creating a file object, you can use a file template, or base it on an existing object.

In Quest® Stat®, file templates are associated with particular file types. They help standardize development by defining in a reusable format the basic characteristics and structure of new file objects. This way, when you need to create a file object of a particular type, you can use an associated template as a starting point. This saves time and helps enforce adherence to development standards.

When new Oracle® file objects are created from an existing object, Stat remembers the new objects association with the source object. When the source object is identified during a patch impact analysis, Stat indicates the source object was used to create a new object. This alerts you that a patch may impact this custom object.

To create a file object:
1
On the Objects tab, select an environment and object type.
2
Click New Object.
Stat opens the New Object window, with the assigned developer and object type that you previously selected displayed as default values.
3
(Optional) In the Assigned To field select a different developer.
4
In the Source field, do one of the following:
•
Select Existing Object if you want to base the new file object on an existing object
•
Select Template if you want to base the new file object on a template
5
(Optional) In the File Type field select a different file type.
6
Do one of the following:
•
If basing the new file object on a template and your system administrator has defined more than one template for the selected file type, select the file template you want to use in the Template field. Then select the language and product you want to associate with the object in the New object Language and Product fields.
•
If basing the new file object on an existing object, select the active environment in which the object resides in the Environment field. At this point, if the object you are basing the new object on is a predefined (i.e. non-custom) Oracle file type, Stat prompts you to select the product and language the existing object is associated with. Select the product and language and click Fetch. Stat queries the environment and retrieves all the objects of the selected type, product, and language. Select the object you want and, if applicable, then select the language and product you want to associate with the new object in the New object Language and Product fields.]
* 
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, if you are basing the new object on an existing, custom Oracle file type object, you are not prompted to specify a product or language for either the existing object or the new object. After you select an environment, Stat queries that environment and retrieves all the objects of the custom file type you selected.
7
In the New Object Name field, enter a name for the new object.
The appropriate file extension is automatically appended to the name based on the file type you selected.
8
Click Create.
Stat displays a series of warning messages telling you that the object does not exist in each environment in the migration path. For each environment, Stat asks you if you want to add the object to the CSR.
9
Click Yes for each instance of the object that you want to add to the CSR. Click No for each instance of the object that you do not want to add.

Stat adds each instance of the new object that you selected to the CSR. At this point, the file object exists only in the working directory of the assigned developer but is not yet archived. For more information on archiving, see Creating Archive Sets (Oracle Applications) .

Editing File Objects

You can open file objects directly from Quest® Stat® for editing purposes. Stat opens the object in whichever program your operating system uses to open files of that type.

It is important to remember that when you edit an object, you are editing only the version of the object that exists in the particular environment you selected. The same object may exist in other environments, and these versions are not affected by any changes you make to the edited version. Because you can edit only one version of the object at a time, the changes you make to the object in one environment do not affect the version in the other environment. If you want all your environments to contain the same version of an object, you have to migrate that object to each environment. For more information on migrating, see Documenting Migrations and Process Requests (Oracle Applications) .

If you want to edit a file object associated with a CSR, you can open it directly from Stat with whichever program your operating system uses to open files of that type. When selecting a file object to edit, remember that you can choose from different versions of the same object. These include the versions that exist in users’ working directories as well as all the source file locations defined for any of the environments on the migration path of the CSR. However, because source file locations do not include drive information, Stat cannot open a file object from the same location in which it resides for a selected environment. Instead, Stat copies the file to the file download directory. For Windows 7/8 it is C:\Program Data\Quest Software\Stat\temp.

To edit a file object:
1
In an object list, right-click on the row for the working directory or environment that contains the version of the file object you want to edit.
Object lists are displayed in the Change Management tabs of the CSR window and in the Objects tab and Object Management tab (Environment Info view) of the Change Management/Version Control window.
* 
NOTE: You can only edit a file object that resides in a user’s working directory after an archive set containing that object has been either migrated to the working directory or created from it. Also, to access the Edit Object feature for a file object residing in a user’s working directory, you must be in the Environment Info view of the Object Management tab. In this object list, select the row that has the value “WORK” displayed in the environment column. For more information, see Documenting Migrations and Process Requests (Oracle Applications) .
2
In the pop-up menu, select Edit Object.­­
Stat opens the file object in whichever program your operating system uses to open files of that type.
3
Edit the file object as needed. Then save your work.

Comparing and Merging Objects (Oracle Applications)

After adding objects to a CSR, you can use the Quest® Stat® object comparison tools to compare the definition of two objects or two versions of the same object. The object comparison tools can be used to compare objects in the following ways:

•
Versions residing in two different environments on the migration path, including objects in the assigned developer's working directory and a VCM repository (if your system administrator has defined any VCM records and you have associated one with the CSR).
•
Versions archived in two different archive sets on a CSR
•
Versions residing in any combination of environment, archive set, or patch.
* 
TIP: You can also run the object comparison tools from the Object Mgmt menu. When run from this location, you can compare objects contained in any non-merged, active Oracle Apps patch stored in the Stat Repository. This feature supports any Oracle® Apps object type defined in the Object Type Maintenance table, except setup object types, which cannot be compared from within patches. For more information, see Object Tools and Wizards .

In the case of data objects, you can use the Object Comparison Wizard to compare two different objects as long as they are of the same object type. Also, for data objects that do not contain blob data, you can use the Object Merge Wizard to combine the two versions into a new object definition. The merged object definition is then automatically archived on a new Stat-generated archive set. This way, you can keep your data objects updated and synchronized across environments.

For file objects, you can use the File Comparison Tool to compare the contents of two file objects and easily identify differences. Like the Object Merge Wizard, this tool also enables you to merge the two objects by overwriting sections of one file with sections from the other file. The newly merged versions can then be saved to the assigned developer’s working directory and later included in a new archive set.

For setup objects, you can view the differences between two versions of an object, either in an archive set, in an environment, or between the two.

Developer objects are a type of file object and consist of form (fmb), form library (pll), and report (rdf) objects. If you have configured Stat to support developer object comparison, you can view the differences between developer objects in an archive set, environment, or in any combination of the two. Unlike with other file objects, however, Stat does not support merging developer objects.

* 
TIP: For more information on configuring Stat to support developer object comparison, see the Stat 5.7.0 Install Notes or Upgrade Notes. For detailed instructions on using Stat object comparison tools, see Object Tools and Wizards .

Viewing your Object Environment (Oracle Applications)

The Object Management tab displays information pertaining to object development within Oracle® Applications environments. From here, you can view information regarding all the environments in a migration path as well as create and migrate object archives. For more information, see Creating Archive Sets (Oracle Applications) and Documenting Migrations and Process Requests (Oracle Applications) .

This Object Management tab is divided in two sections. The left section is a tree view showing all of the possible groupings of the information that appears on the right section of the tab. The tree allows you to navigate through the objects associated with the CSR as well as all the archives created for the CSR.

The buttons located on the top of the tap page, Environment Info and Archive Sets, control what type of information you see in the right section of the tab. When you click Environment Info, the window displays object information. When you click Archive Sets, the window displays object archive information.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating