Relationship of Record Attributes to Data Caching Behavior

Read Once

When you map a cube collection to a record that contains a Read Once attribute in the analytic type, the application data is read only once during analytic model load time. Map cube collections to Read Once records to load data that the user should not change during the analytic model's life cycle. You can specify the Read Once attribute for these record types:

• SQL tables.

• SQL views.

• Dynamic views.

• Query views.

Readable

When you map a cube collection to a record that contains a Readable attribute in the analytic type, the application data is read during analytic instance load time and is updated with new data after:

• Each analytic model recalculation.

  You recalculate an analytic model by using the AnalyticModel class Recalculate method. The AnalyticModel class is one of the Analytic Calculation Engine classes.

  See Recalculate.

• Each Save action that is triggered by a PeopleSoft Pure Internet Architecture page with an analytic grid.

• Each time data is updated using the CubeCollection class SetData method.

  The CubeCollection class is one of the Analytic Calculation Engine classes.

  See SetData.

Map cube collections to Readable records to load data that should be refreshed more than once during the analytic model's life cycle.

You can specify the Readable attribute for the SQL table record type.

Writable

When you map a cube collection to a record that contains a Writable attribute in the analytic type, the data in the cube collection is written back to the application database after:

• Each analytic model recalculation.

  You recalculate an analytic model by using the AnalyticModel class Recalculate method. The AnalyticModel class is one of the Analytic Calculation Engine classes.

  See Recalculate.

• Each Save action that is triggered by a PeopleSoft Pure Internet Architecture page with an analytic grid.

• Each time data is updated using the CubeCollection class SetData method.

  The CubeCollection class is one of the Analytic Calculation Engine classes.

  See SetData.

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 instance.

Scen. Mgd (Scenario 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 analytic instance, although 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.

The following table provides an example of a record with a PROBINST key field.

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.

See Scenario Management.

Records based on dynamic views can be Scenario Managed. For these records, the associated SQL must contain a meta string for qualifying the analytic instance.

The following example shows a Dynamic View record:

SELECT PROBINST, QE_BAM_MONTH_FLD, QE_BAM_REGION_FLD, 
			  QE_BAM_PRODUCT_FLD, QE_BAM_UNIT_FLD, 
			  QE_BAM_SALES_FLD, QE_BAM_PRDSALES_FL  
FROM PS_QE_BAM_FACT_TBL
WHERE PROBINST = %ProbInst

If a Union clause is present the WHERE PROBINST= %ProbInst must be added to the individual clauses making up the SQL Union. In addition all the fields that are part of the dynamic view must be selected in the analytic type definition. This is enforced by PeopleSoft Application Designer.