Chatta subito con l'assistenza
Chat con il supporto

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

Defining Data Objects

After defining any necessary application version numbers, you can define the data object type. The Data Object Maintenance window features three tabs that correspond to the change management modules featured in Stat.

Naming Data Objects

To begin defining a data object type, the name of the object type must be saved in the Stat Repository.

To name a data object type:
1
Select the tab for the change management module tab that the data object is associated with.
Each tab displays the names of the data object types that have been defined for that change management module.
2
Click New.
3
In the Object Name field type the name of the object.
4
Click OK or Apply.
This saves the object type definition in the Stat Repository and activates the Edit button. At this point, you can complete the definition of the object type by specifying its application version number, identifiers, and data tables.

The Edit Data Objects Window

You complete the definition of a new data object, or edit the definition of an existing one, in the Edit Data Objects window. This window is divided into three sections:

•
The Version section displays all the module-specific application version numbers defined on the first tab of the maintenance window. For each application version number, you can define a different definition for the data object type.
•
The Identifiers section displays the name and type of each table field that uniquely identifies a data object type
•
The Tables Definition section displays each data table that defines the object type, including the SQL Where Clause

If more than one application version number has been defined, select the version number you want in the Versions section to view the object definition associated with that version.

You can edit any active object definition associated with an application version number. When defining a new data object type or a new version of an existing one, the first step is to select the application version number you want to associate with the object type.

Defining Object Identifiers

You need to specify the table fields that uniquely identify each object of this object type. This is done in the Identifiers section of the Edit Data Objects window. The identifying table fields are used when specifying the SQL Where Clause in the table definitions. Each field defined as an identifier must be in the table that is defined with sequence 1. It must be also part of that table’s Where Clause.

To define data object identifiers:
1
In the Versions section, select the application version number you want to associate with the data object type.
2
In the Identifiers section, type the name of the table field that uniquely identifies the object in the Identifier Field of row A.
3
In the Type field, select the field type.
Options include Number, Character, and String.
4
Repeat steps 2 and 3 for each table field that uniquely identifies the object.
You can specify up to 7 identifier fields.
5
Click OK or Apply.
Defining Tables

You must define at least one table for Stat to save the definition of the data object type. The first table you define is considered the parent table which holds each unique object of this object type. Its Where Clause must use each Identifier. When users add data objects to their CSRs, Stat obtains the list of objects for the selected object type from this table.

To define a table:
1
Click New.
Stat activates a new row in the Table definitions section. By default, the Where Clause displayed in the SQL Where Clause field uses each identifier specified in the Identifiers section. You can modify this Clause as needed, but the first table must contain each identifier. Subsequent tables must contain at least one identifier.
2
Type the name of the table in the Table Name field.
The name of the table should begin with the schema, if applicable.
* 
CAUTION: For Oracle Applications users, make sure the name of the table is preceded by the name of its schema, such as GL, AP, AR. For example, the table RA_CUSTOMERS belongs to the AR schema, which means in the Table Name field you would enter “AR.RA_CUSTOMERS.”
3
(Optional) Modify the Where Clause in the SQL Where Clause field as needed.
4
(Optional) In the Table Keys field specify the fields that uniquely identify the table.
This information is used when performing an object comparison between two versions of the same data object.
At this point, the names of table columns and blobs (if any) need to be entered in the List of Columns and Blob fields, respectively. You can do this manually of you plan on running the SQL script outside of Stat, or you can have this information entered automatically by running the SQL script in the Create Archive Table window.
5
Do one of the following:
•
Enter the names of the table columns and blobs in the List of Columns and Blob fields, respectively. When finished, click Apply.
Do this if you plan on running the SQL Script outside of Stat.
•
Click Create Tables.
This opens the Create Stat Archive Table window. Here you specify the tablespace in the Stat Repository where you want to maintain an archive of the table definition and the application environment that contains the original SQL script. If you want to write the table definition to the Stat Repository, you can do so by running the SQL script.
To create a table:
1
(Optional) Specify a different tablespace in the Tablespace field.
By default, an archive of the table definition is written to the STSWAT tablespace in the Stat Repository.
2
In the Environment field, select the environment that contains the SQL Script for the table.
When you select the environment, the SQL Script is displayed in the SQL section of the window.
3
If you want to write the table definition to the Stat Repository, click Run SQL.
The Status section displays the results of the SQL script. The values specified in the SQL Script are automatically entered in the List of Columns and Blob fields of the Edit Object window. Any previous values are overwritten.
4
(Optional) Click Export if you want to save the SQL Script to a directory outside of Stat.
5
When finished, click Close. Then in the Edit Data Objects window, click Apply.
Copying Data Object Definitions

You can save time by copying the definition of a data object to other application versions. You can also use the copy function to overwrite data objects defined for a particular application version, so long as the data objects of that version are not already associated with a CSR. To maintain referential integrity, Stat does not permit data objects already associated with CSRs to be modified.

To copy a data object definition:
1
In the Edit window, click Copy.
This opens the Versions window, which displays a list of application versions to which you can copy the data object definition.
2
In the Versions window, select the application version you want to copy the definition to. Then click OK.

Data Object Example

The following example is taken from PeopleSoft and is meant to illustrate the process of defining data object types in Stat. In this example, the goal is to configure Stat to support Provider Group data objects, which can then be archived and migrated from the CRM Field Service module to a PeopleSoft CRM environment. We will use the PeopleSoft-delivered Data Model to define our Provider Group data object type. The Provider Group tables and identifiers are detailed in the diagram below.

Provider Groups are associated with PeopleSoft version 8.40. Before defining the Provider Group data object type, the first step is to associate it with the appropriate application version number. To lock, archive, and migrate Provider Group data objects, make sure all the PeopleSoft environments in the CSR’s migration path are defined in the PeopleSoft Environment Connection Maintenance table with the Data Object Version ‘8.40’.

The parent table for Provider Groups is PS_RF_PROVIDER_GRP. Each unique combination of values for the fields SETID and PROVIDER_GRP_ID represents a Provider Group.

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione