Chat now with support
Chat with Support

Stat 6.1 - System Administration Guide

Overview of Stat Administration Administrative Utilities Stat Security General Maintenance Tables
System Maintenance Service Domain Maintenance Department Maintenance Issue Tracking Maintenance Country Maintenance Customer Maintenance Object Type Maintenance PeopleSoft Environment Connection Maintenance Pre/Post Migration Steps Parameters Oracle Applications Configuration Oracle Applications Connection Maintenance Generic Application Connection Maintenance Schema Object Parameters Maintenance Data Object Maintenance PeopleSoft Search Configurations Stat Report Definition Maintenance Version Control Management Connection Maintenance
Service Domain-Specific Maintenance Configuring the Stat Central Agent Email Configuration Object Security Appendix: Sample Service Domain Configuration Appendix: User Class Rights Appendix: Creating a Staging Database Appendix: Database Tuning Appendix: Oracle Applications File Type Directory Appendix: Ports and Firewalls Appendix: Stat Web Services Appendix: Troubleshooting Chart Appendix: stat.conf Configuration Appendix: Custom Report Files

File Type User Directories

In the File Type User Directories tab, you can specify for each active Stat user a separate working directory for the selected file type. This way, whenever an archive set containing a file object of a certain type is migrated to the working directories of the Development environment, Stat migrates the file object in the archive set to the assigned user’s working directory defined for that type. From there it can then be modified as needed.

If you don’t define a separate file type working directory for a user, whenever a file object of that type is assigned to the user and migrated to the “working directory,” Stat places the file object in the user’s default working directory. See the following section for more information on user default directories.

When defining file type user directories, keep in mind the following considerations:

•
User can define their own working directories in the Stat User Options window. For more information, see the “Object Management” sections in the change management chapters of the book, Stat User Guide.
•
You can also define working directories by user in the User File Directories tab of the Other User Information window. For more information, see Defining Stat Users .
•
Make sure you use the proper syntax when specifying directories. For more information, see File Path Syntax .
Value
Description

Stat User
(Key Value)

The Stat user’s ID

Working File Server

Server where the working folder is located

Working File Path

File server path where the working folder is located

Last Update
(Read Only)

The date and time this record was last updated

Update By
(Read Only)

The user who last updated this record

VCM Locations

In the VCM Locations tab, you can specify subdirectories for specific object types for any defined VCM connection.

Value
Description

Active

Indicates if this subdirectory is activated in Stat

VCM

VCM Connection

Path

Subdirectory off of main VCM Connection Project Path for specific object type

Last Update
(Read Only)

The date and time this record was last updated

Updated By
(Read Only)

The user who last updated this record

File Templates

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

For more information on using file templates, see the “Object Management” sections in the change management chapters of the book, Stat User Guide.

To open the File Template Maintenance window, select the file type you want to create a template for and click the File Templates button (or the Templates/Generate button in the case of Oracle Applications custom file types).

To create a file template:
1
Click New.
2
In the Template Name field, type a name for the template.
3
In the Template field, browse and locate the file out on your network that you want to use as the basis for the template. Click Open.
Stat displays the location of the file in the Origin field.
4
Click OK or Apply to save your work.
The actual file is copied to the Stat database.
To modify a file template:
1
Click New.
2
In the Template Name field, type a name for the template and add a version number.
3
In the Template field, browse and locate the file on your network that you want to use as the basis for the template. Click Open.
Stat displays the location of the file in the Origin field.
4
Click OK or Apply to save your work.
5
Inactivate the original template.
6
Click OK to save your work.

Setup Object Types for Oracle Applications

The Stat-supported Oracle Apps Setup object types allow for archiving and migrating data stored in Oracle Applications tables and views. The Stat Oracle Agent utilizes the FNDLOAD utility provided by Oracle to download or upload rows of data from one Oracle instance to another. FNDLOAD in turn uses a set of instructions available in an Oracle-provided .lct file, which defines the fields that are extracted, as well as the actual Sql statement for downloading and uploading the data item.

A unique object type can be defined in Stat for any Setup object, if:

•
Oracle has provided an .lct file for that object type.
•
The .lct file is defined in such way that allows for download and upload of a unique record for that object type.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating