Tchater maintenant avec le support
Tchattez avec un ingénieur du support

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

Identifiers

•
Identifiers are the fields whose combined values make each object of this type unique. In our example, these fields are SETID and PROVIDER_GRP_ID.
•
Each Identifier field must be in the parent table. This is because when adding an object of this type to a CSR, Stat retrieves the object list by selecting from this table all distinct rows for the identifier fields.
•
The Identifier fields do not have to be in any of the other tables in the Data Object definition.

Tables

•
The first table you define is the Parent table (Seq value =1). This does not need to be a true “parent” table in the sense of its database definition. Stat obtains from this table the list of objects that the user picks from when adding objects to a CSR. It is usually the parent table but it does not need to be.
•
All the tables listed in the Data Model contain data that must be included in the definition of the Provider Group data object type. This data needs to be archived/migrated when archiving/migrating an object of this type.
•
If the tables do have a parent-child relationship, the parent table must be listed before the child tables to ensure that its rows are processed before the rows of the child tables.
•
When archiving/migrating, Stat pulls the data from each table using the where clause that you define in the SQL Where Clause fields.
•
The tables do not have to be related but you do need to be able to pull data from the table using the where clause constraints listed below.

Where Clauses

•
The where clause can have hard coded values (e.g., WHERE STATUS = 'A' AND EFFDT > 01-01-2000. The date format must match your RDBMS required format).
•
The where clause can have variables that are filled in during archiving/migrating using any of the identifier fields (e.g., WHERE SETID = %A%, or WHERE GRP_ID = %B%. In this case %B% is replace by the object's value for the PROVIDER_GRP_ID field since 'B' is its identifier ID even though the constraint is on the GRP_ID field).
•
If the where clause contains identifier variables (e.g., %A%, %B%), Stat replaces the variables with the object's field values during archiving/migrating (e.g., if you add to your CSR the Provider Group that has SETID = 'CRM01' and PROVIDER_GRP_ID = 'APLW,' when you archive this object the where clauses will replace %A% with 'CRM01' and %B% with 'APLW').
•
The where clause can have embedded select statements (e.g., WHERE GRP_ID IN (SELECT PROVIDER_GRP_ID FROM PS_RF_PROVIDER_GRP WHERE SETID = %A%)).
•
The tables do not have to be related but you do need to be able to pull data from the table using the where clause constraints listed above.
•
If the tables do have a parent-child relationship, the parent table must be listed before the child tables to ensure that its rows are processed before the rows of the child tables.

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

Table
Where Clause

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

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:

•
PeopleSoft Search Cfg - Add
•
PeopleSoft Search Cfg - Change

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

Value
Description

Active

Indicates if this record is available for selection

PeopleSoft
Database
(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

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation