Chat now with support
Chat with Support

Stat 6.0 - System Administration Guide

Overview of Stat Administration Administrative Utilities Stat Security General Maintenance Tables
System Maintenance Service Domain Maintenance Department 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

Tables

Where Clauses

The Provider Croup tables, along with their Where Clauses, include:

PS_RF_PROVIDER_GRP (Parent Table)

SETID = %A% AND PROVIDER_GRP_ID = %B%

PS_RF_GRP_MEMBER

SETID = %A% AND PROVIDER_GRP_ID = %B%

PS_RF_PROVGRP_RGN

SETID = %A% AND PROVIDER_GRP_ID = %B%

PS_RF_COST_CAT_GRP

SETID = %A% AND PROVIDER_GRP_ID = %B%

PS_RF_COST_CAT

SETID = %A% AND COST_CAT_CD = (SELECT COST_CAT_CD FROM PS_RF_COST_CAT_GRP WHERE SETID = %A% AND PROVIDER_GRP_ID = %B%)

PS_RF_COST_CAT_MEM

SETID = %A% AND PROVIDER_GRP_ID = %B%

All the tables, where clauses, table keys, columns, and blobs in the Data Model must be entered in the Tables Definition section of the Edit Data Objects window.

The PS_RF_PROVIDER_GRP and PS_RF_GRP_MEMBER tables contain Blob fields. This information need to be defined in the Blob Column fields.

The next step is to create the Stat Archive table, which contains the object archives.

At this point, Provider Group data objects are fully defined in Stat and now can be added to a CSR, archived, and migrated.

PeopleSoft Search Configurations

The PeopleSoft Search Configuration table specifies the PeopleSoft environments from which customer, department or country information can be retrieved and inserted into the Stat Repository. Information can be retrieved from PeopleSoft employee, department or country views.

PeopleSoft security is controlled by the following user class rights:

The PeopleSoft Search Configurations table is displayed in a standard maintenance window. To open this window, select Maintenance | General | PeopleSoft Srch Configs.

Active

Indicates if this record is available for selection

PeopleSoft
Environment
(Required Value)

The PeopleSoft environment that contains the customer information

Description
(Required Value)

Description of the configuration or environment

Search View Name
(Required Value)

An 18-character field that contains the name of a table or view in PeopleSoft against which the search is conducted. See the next section, Creating Tables and Views .

Type
(Required Value)

Indicates the type of PeopleSoft view that is the basis for the search. Options included Employee, Department or Country.

Last Update
(Read Only)

The date and time this record was last updated

Update By
(Read Only)

The user who last updated this record

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.

Related Documents