Database Reference
In-Depth Information
fact data have a home in Essbase? how can data not have been loaded? I have two good
reasons why data might not be correct:
1. As I previously related, data can still fall through the cracks through illegal
characters. Per President reagan, “trust in your data, but verify.”
2. There is this guy named murphy, and he has a law “If anything can go wrong,
it will.”
I do not live my life by hoary old maxims, but these are two sayings that any cau-
tious/continually employed Essbase developer should take to heart. I have, hence these
validation steps.
1. Pkg_Extractvalidatereport in Figure 2.19 runs an Essbase report Script to
disk, imports it to a table, and then compares the Essbase data to the summed
fact data through the following objects and steps. The Set variable vAr_
maxLScriptname value is set to validate.
2. The Declare variables vAr_Appname and vAr_Dbname are passed from the
calling Load Plan PLAn_ASosamp.
3. The Set variable vAr_maxLreportname is set to validate.
4. The oS Command object oS_maxLreportrun is passed the parameters for the
Essbase application, database, maxL script, and report Script name, which it
then runs. The report Script validate.rep produces a report for the current year
and month at a total dimension level for original Price, Price Paid, returns,
units, and transactions.
Figure 2.19
Package PKG_ExtractValidateExport.
