Database Reference
In-Depth Information
Figure 3.27 Specifying dimensions.
Figure 3.27 shows a single column as the measures. This is done because, in the spe-
cific model, the measures dimension was built from a recursive table as a standard hier-
archy type leveraging the parent/child relationship. The fact table used for this build
contains a single data column (“Amount”).
What do you do, however, if you are simply creating a prototype with Studio and
either do not have a data file or want to load the data from a process external to Studio?
In either case, you can trick Studio into believing you have a measures column. Instead
of adding a true data column to the Cube Schema wizard, you can add any column with
a numeric data type to this portion of the uI to simply move forward. For example, in
Figure 3.28, ProDuCtID from the Product table is added to the measures area of the
Cube Schema Wizard. once in place, the uI lets you move forward to the next step as
in Figure 3.29.
If you plan to employ this trick during the deployment phase, make sure you think
ahead when adding a data source to Studio and confirm that it has a numeric column in
one of tables or text files.
Note: This trick only works if you use a standard hierarchy as your Accounts/measures
dimension. This hierarchy is added to the standard dimension area like products, time,
or any other hierarchy. If you have a “measures” type hierarchy and you want to add it
to your Essbase cube, this definition must be added to the measures hierarchy area on
the cube schema wizard (Figure 3.30).
Search WWH ::




Custom Search