Database Reference
In-Depth Information
Figure 2.17
Years suspense SQL output.
Figure 2.18
Package PKG_dLoadData.
1. A data loading Interface is inextricably tied to the target Essbase database, thus
preventing reuse.
2. Essbase dimension names with spaces create a failure in the data loading
Interface. Three of ASosamp's dimensions, [transaction type], [Payment
type], and [Income Level] have spaces in their names.
Pkg_dLoadData in Figure 2.18 loads the current year and month data from the fact
source through the following objects and steps:
1. The Declare variables vAr_Appname and vAr_Dbname are passed from the
calling Load Plan PLAn_ASosamp.
2. The Set variable vAr_maxLScriptname is set in this Package to LoadData.
3. The vAr_Appname, vAr_Dbname, and vAr_maxLScriptname are passed
to the oS_maxLDataLoad object that runs the script LoadData.msh.
4. If LoadData.msh's StDErr produces a LoadData.err file with a file length
greater than zero bytes, a failure notice is written to the LoadStatus table or else
a success message is written.
2.4.5 Validating Data
“Wait,” you say, “how can the data not be good?” (you are at least thinking this, right?)
What about all of those many, many steps that guarantee that all members in the source
