Chat now with support
Chat mit 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

Audit the System

You can run the wizard to find all objects that were changed but not documented in Stat, as well as new, undocumented objects created in your application environments. This ensures that developers are documenting changes they make to objects.

The wizard reports modified objects as being either “undocumented” or “version-changed.” A modified object is reported as undocumented if it has not been associated with a CSR in Stat, or, if it has been associated with a CSR, it has been modified after the CSR was closed or the object was unlocked. A modified object is reported as version-changed if its CSR is open and the object is locked in its application environment but its version number has been changed in its application environment after the object lock was obtained.

Undocumented objects indicate that at some point proper business practices were not followed. Remember that the goal is to have all modified objects documented in a CSR at all times. Version-changed objects, on the other hand, are reported for informational purposes only. They can be used by Project Managers to keep tabs on what is currently being modified in the application environments during project life cycles.

When proper business procedures are followed, it is not necessary to run the wizard very often. Since this is not always the case, the wizard can be run on a periodic basis to monitor undocumented changes and add undocumented objects to CSRs.

Identify Schema Changes in an Environment

With the Undocumented Object Wizard, you can scan the schema object definitions in a selected PeopleSoft, Oracle Applications, or generic application environment and identify any modifications to these objects that are not recorded on a CSR. The Wizard compares the date-time stamping of schema objects with the stamping documented in Stat; if a schema object has a later date-time stamp, the wizard reports it as undocumented.

Assist with PeopleSoft Compare Reports

If you install Stat during a PeopleSoft upgrade, the wizard assists you with your PeopleSoft compare reports. The wizard tells you which objects have been changed, eliminating this time-consuming step in the compare process.

The Wizard and Version Control

The Undocumented Object Wizard facilitates version control by automatically adding all the undocumented objects that it finds in the application environment to a CSR. You can then lock these objects on the CSR and create an archive set that serves as the baseline archive of the objects. If you run the wizard against the base environment in a migration path, Stat creates a base archive set automatically after you lock the objects on the CSR; for all other environments, an interim archive set must be created manually.

* 
NOTE: If you simply want to document the objects located by the wizard, lock them after they are added to a CSR, save the CSR and then unlock the objects. This documents the objects. When you run the Undocumented Object Wizard again, these objects will not appear in the results.
To run the Undocumented Object Wizard:
1
Select Object Mgmt | Undocumented Object Wizard.
2
In the Module field, select the appropriate change management module.
3
In the Database field, select the environment you want.
4
In the Object Type(s) field, scroll through the list of object types and select the type(s) you want. To select more than one object type, hold down the <Shift> or <Ctrl> key while you make your selections.
For application environments running on SQL Server 2005/2008 or on Oracle version 10 or higher, the list includes schema object types. For PeopleSoft environments, the list also includes PeopleSoft proprietary object types, except the following:
•
Access Groups
•
Cube Definitions
•
Cube Definition Instances
•
Dimensions
•
Indexes
These object types are excluded because they do not include date stamps or user ids. For a complete list of PeopleSoft proprietary object types supported by Stat, see Appendix: Supported PeopleSoft Proprietary Objects .
5
Click Next>.
If you selected PeopleSoft Proprietary object types, the wizard prompts you to specify compare criteria. If you selected schema object types, the wizard skips this window and searches the selected environment.
6
Select the compare criteria you want and specify any additional parameters as needed.
You can select one of three options:
•
PeopleSoft Date/Time Stamping — When you select this (default) option, the wizard displays a list of release dates contained in the PS Release table. The wizard then compares the release date you select to the date and time that each object was last updated. If an object date is more recent, the wizard then checks if that object is documented in Stat.
•
Date/Time — This option allows you to specify a date that is different than a release date. After you specify a date, the wizard then compares it to the date and time that each object was last updated. If an object date is more recent, the wizard then checks if that object is documented in Stat
•
PeopleSoft Oprid — This option allows you to specify a PeopleSoft OPRID that is either equal or not equal to the OPRID of the objects. If you selected Equals (=), the wizard identifies the objects with a matching OPRID and then checks if each object is documented in Stat. If you selected Not Equals (<>), the wizard identifies the objects that do not have a matching OPRID and checks if they are documented.
7
Click Next>.
The wizard processes your search and displays the number of modified objects it has found and of these how many are undocumented. If you want to cancel the search during processing, click Stop Search. The Modified Object Count number is always equal to or greater than the Undocumented Count.
8
If the wizard found undocumented objects and you want to add these objects to a CSR, click Next>. If the wizard did not find any undocumented objects, or you do not want to add any objects to a CSR, click Finish.
In the next window, you can associate the undocumented objects with a CSR. The left side of the window lists the undocumented objects and/or version-changed objects. Undocumented objects are separated from version-changed objects by a header within the list. The header shows the number of objects in that category. When the list shows both undocumented and version changed objects, you can only work with one category at a time. You cannot cross-select.
* 
NOTE: You can export the list of undocumented and version-changed objects by clicking the Export button. The report includes the date and time the objects were last updated and by which user (as identified by Operator ID).
Objects under the Versions Changed heading, if any, need to be updated to the PeopleSoft environment version. To do this, select the object and click Update button. This updates the version of the object in Stat so that it matches the version in the PeopleSoft environment.
You can add undocumented objects to existing CSRs or to new CSRs. When selecting a CSR or creating a new one, you need to make sure of three things:
•
That the current status of the CSR allows users to add and lock objects. Workflows can contain status rules that do not allow users to add or lock objects while the CSR is in a certain status. When this is the case, you will be unable to add or lock objects until the CSR status changes to one that allows objects to be added and locked.
•
That the change management tab displayed on the CSR matches the module of the objects you want to add. The wizard cannot add objects to a CSR that displays the wrong change management tab
•
That the CSR has a migration path that includes the base environment for the objects you want to add. You receive an error message if you attempt to add an object to a CSR that does not have a migration path or the migration path it does have does not include the base environment of the selected object(s).
To specify existing CSRs, click Lookup CSRs.... This opens the Search CSR Engine, which you can use to locate the CSRs you want. In the Search CSR Engine window, select the CSRs in the results list and click Add.
If you want to create a new CSR, click New CSR.... After you create the CSR and save it, it is automatically added by the wizard.
9
Specify the CSR(s) to which you want to add the undocumented objects.
10
After you have added CSRs, select a CSR and the objects you want to add to it. To select multiple objects, use the <Shift> and <Ctrl> keys or the Select All or Select None buttons.
11
Click Add>>.
This adds the object(s) to the CSR only. It does not request a lock or reservation for the object.
12
Click Finish.
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen