Technical data

Chapter 12 Understanding th e Relationship of Analytic Types to Analytic Models
• Each time data is updated u sing the CubeCollection class SetData method.
The CubeCollection class is one of the Analytic Calculation Engine classes.
See Enterprise
PeopleTools 8.49 PeopleBook: PeopleCode API Reference, “Analytic Calculation Engine
Classes,” SetD
ata.
You can specify the Read Once attribute for the SQL table record type.
If the analytic type contains a writable-only record that uses a primary key field, you must set up the application
to clear the data in the database for the writable record before recalculating the analytic insta nc e.
Note. After the data is written back to the database, the data cubes that a re mapped to the writable-only record
are cleared from the analytic instance, resulting in 0 or empty values in the analytic grid.
Note. When a cube collection is mapped to either a Writable-only record or a record with the Readable and
Writable attributes, all data cubes in the cube collection should share the sa me set of dimensions .
Scen. Mgd (Sc enario Managed)
Use the Scenario Managed attribute to indicate that the record pertains to multiple analytic instances. A
scenario managed record is read from and written back to the database according to the other attributes
that are specified for the record.
Typically, one user views and edits one a nalytic instance, although PeopleSoft Analytic Calculation Engine
supports multiple users per analytic instance.
Records that contain the scenario managed attribute must have a PROBINST key field. The PROBINST key
field is used to segment the data of scenario managed records, resulting in a different data set loaded for each
analytic instance. This is an example of a record with a PROBINST key field:
PROBINST key
field
ACCT field TRANS_DATE f
ield
REGION field
BUDGET01 100
January
EUROPE
BUDGET01 100
Feb
EUROPE
BUDGET02 110
Feb
ASIA
BUDGET02 110
March
ASIA
BUDGET03 120
March
USA
In this example:
• The users of the BUDGET01 analytic instance can access only the first and second rows of this record.
• The users of the BUDGET02 analytic instance can access only the third and fourth rows of this record.
• The users of the BUDGET03 analytic instance can access only the fifth row of this record.
Note. Data cubes that exist in a cube collection that is mapped to a main record with the Scenario Managed
attribute cannot exist in any other cube collectionthatismappedtoaderived/workmainrecord.
Copyright © 1988-2007, Oracl e. All rights reserved. 207