Technical data

Converting BAM 8.8 Models to Analytic Models Chapter 16
See Chapter 16, “Converting BAM 8.8 Model s to Analytic Models,” Exporting BAM 8.8 Models,
page 262.
3. Run the PTAEACECONV Application Engine program.
See C
hapter 16,
“Converting BAM 8.8 Models to Analytic Models,” Running the PTAEACECONV
Application E
ngine Program, p ag e 262.
4. Examine the Ap
plication Engine log file.
See C
hapter 16, “Converting BAM 8.8 Models to Analytic Models,” Examining the PTAEACECONV
Log File, page 264.
5. Map the new analytic model to main and aggregate records that hold the application and aggregation
data.
See C
hapter 7 , “Creating Cube Collections,” Mapping a Cube Collection to Main and Aggregate
Records, page 58.
6. Map data cubes and dimensions to fields in the main and aggregate records.
See C
hapter 7,
“Creating Cube Collections,” Mapping D ata Cubes and Dimensions to Fields, page 59.
7. Create People
Soft Pure Internet Architecture pages with analytic grids.
See C
hapter 13, “Creating Analytic Grids,” page 211.
8. View the new analytic model in PeopleSoft Pure Internet Architecture.
See C
hapter 14, “Viewing and Debugging Analytic Models,” page 229.
The PTAEACECO
NV Application Engine program converts most parts and circular formula options into
analytic mod
els.
BAM 8.8 Parts That Can Be Converted
These BAM 8.8 parts c an be converted into analytic models:
•Datacubes.
• Dimensions.
• User functio
ns.
•Expressionmo
difiers.
• Table views.
• Import maps.
•Organizers.
BAM 8.8 Parts That Cannot Be Converted
These BAM 8.8 parts c annot be converted into analytic models:
• Prefix modif
iers.
• Styles.
• Option lists.
Note. References to option lists within the code of data cube rules; user functions and expression modifiers,
however, are converted.
254 Copyright © 1988-2007, Oracl e. All rights reserved.