Technical data

Understanding the Relationship of Analytic Types to Analytic Models Chapter 12
See Enterprise PeopleTools 8.49 PeopleBook: PeopleSoft Optimization Framework, “Designing Analytic
Type Definitions,” 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.
ThefollowingexampleshowsaDynamicViewrecord:
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 s elected in the
analytic type definition. This is enforced by PeopleSoft Application Designer.
See Also
Enterprise Pe
opleTools 8.49 Peop leBook: PeopleCode API Reference, “Analytic Type Classes”
Enterprise PeopleTools 8.49 PeopleBook: PeopleSoft Optimization Framework, “Designing Analytic Type
Definitions,” Configuring Analytic Type Records
Synchroniza
tion Order
In PeopleSoft Analytic Calculation Engine, the synchronization order indicates the order in which the analytic
calculation engine reads the records in the analytic type definition. Records that are used as aggregate records
should have a higher synchronization order than records that are used as main records.
208 Copyright © 1988-2007, Oracl e. All rights reserved.