Chat now with support
Chat with Support

We are currently experiencing issues on our phone support and are working diligently to restore services. For support, please sign in and create a case or email supportadmin@quest.com for assistance

Stat 6.3 - 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: REST Web Services API Appendix: SOAP-Based Web Services API Appendix: Troubleshooting Chart Appendix: stat.conf Configuration Appendix: Custom Report Files

Creating Tables and Views

A table or view must be created in each PeopleSoft environment in which you want to conduct searches. For example, in the case of an employee-based search, the view must contain the following fields:

EMPLID

COUNTRY

NAME

SSN

ADDRESS 1

COMMENTS

ADDRESS 2

COMPANY

ADDRESS 3

PAYGROUP

ADDRESS 4

DEPTID

CITY

DEPTNAME

STATE

WORK_PHONE

ZIP

WORK_PHONE_EXT

EMAIL_ADDR

EMAIL_ADDRESS2

CUSTOM1

CUSTOM2

SIN

 

For employee-based searches, Stat parses the NAME column based on the original PeopleSoft format of Employee table Name column: LastName, FirstName.

In addition, for any column, you may insert a space instead of a value, or indicate a default value. You may wish to populate the comment, custom1 or custom2 fields from other employee related fields.

The following are examples of views. The first example below displays an employee view formatted for PeopleTools versions prior to 8.48, while the second example displays the format for PeopleTools versions 8.48 and higher. In both examples the phone extension, SSN, SIN and second email address values are not being populated from PeopleSoft. The employee's job title is being placed into the comment field. This is configurable based on your site needs.

Employee View Example (Pre PeopleTools Version 8.48)

Employee View Example (PeopleTools Version 8.48 and Higher)

Country View Example

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating