Purpose of Analytic Type Definitions
You create analytic type definitions for use with PeopleSoft Optimization Framework and Analytic Calculation Engine. In PeopleSoft Optimization Framework, you create analytic type definitions to group optimization records, optimization transactions, and optimization plug-ins together as one entity.
In Analytic Calculation Engine, you create analytic type definitions to group records and an analytic model together as one entity. You follow the same procedure to create analytic type definitions for both PeopleSoft Optimization Framework and Analytic Calculation Engine.
When creating a new analytic model definition, you create the analytic type definition in this developmental sequence:
Create and save an analytic model definition.
Create an analytic type definition and define records.
Associate the analytic model with the analytic type.
In the cube collection properties, map a main record in the analytic type to the cube collection.
You can also map an aggregate record in the analytic type to the cube collection.
In the cube collection properties, map the fields in the record to data cubes and dimensions.
When updating an analytic model definition, create an analytic type definition during this developmental sequence:
Update the records in the analytic type definition.
Create a new cube collection in the analytic model definition.
In the cube collection properties, map one of the updated records to the cube collection.
In the cube collection properties, map fields of the updated record to data cubes and dimensions.
The following example illustrates the typical process for creating an analytic type definition to be used with a new analytic model. In this example, you create an analytic type definition called QE_ACE_DGCPROB and define the records that are used in the analytic model. You insert all of these records (except derived/work records) into the analytic type definition and set the attributes of the records.
Note: For simplicity, this example maps only one cube collection to a main record, although the analytic model definition in this example contains several records which would be used with several cube collections. The record used in this example is mapped to a read/write cube collection for loading data from the database, receiving end user input, and persisting data back to the database.
To create an analytic type definition to be used with a new analytic model:
Define the records within the QE_ACE_DBCPROB analytic type definition.
Using the information in the following table, you create an analytic model definition called QE_ACE_DGCMODEL, with data cubes and dimensions that are related in this manner.
SALARY input data cube
These dimensions are attached to the SALARY data cube:
EXPENSE input data cube
These dimensions are attached to the EXPENSE data cube:
BONUS_PERCENT input data cube
These dimensions are attached to the BONUS_PERCENT data cube:
Note: At this step in the process, you do not create the analytic model definition's cube collections.
On the Models tab, you associate the QE_ACE_DBCPROB analytic type to the QE_ACE_DGCMODEL analytic model.
You open the analytic model definition and create a read/write cube collection called QE_ACE_EMPLOYEE1_IN.
On the General tab of the cube collection's properties, you map the cube collection to the QE_ACE_EMPL1 main record.
Note: This cube collection does not use an aggregate record.
On the Field Map tab, you map the fields in the QE_ACE_EMPL1 record to the data cubes and dimensions.
Note: When mapping dimensions and data cubes, you may want to map dimensions to the key fields in the main record and data cubes to the non-key fields in the main record. The PeopleSoft system, however, does enable you to map dimensions to non-key and data cubes to key fields. To perform the most appropriate mapping, you must have a deeper understanding of the relationship between data cubes and dimensions.