You are on this page of the wizard because you selected the “Override default data load bindings” check box on the Cube Schema Options page of the wizard. Use this dialog box to override the default load bindings that will be used for loading data.
These guidelines apply to data load mapping:
Data is loaded at the leaf level of the hierarchy, including recursive hierarchies; therefore, you define the data load mapping at the lowest level of the hierarchy.
For a pure user-defined multichain hierarchy, only one default load binding can be specified at the leaf level for the entire hierarchy. Check boxes are enabled in the Data Load Binding column, and you can select only one check box per pure user-defined hierarchy.
For mixed multichain hierarchies, that is, hierarchies that contain relational chains and user-defined chains:
One data load binding can be specified for each unique leaf level.
The check box for the leaf level of all user-defined hierarchy chains can be selected.
For a measure hierarchy, there is no restriction on the number of bindings that can be specified. They only condition is that they are specified at the leaf level.
For a calendar hierarchy, you must complete the procedure in this topic. You must specify a default data load binding for the lowest level in that hierarchy. If you do not specify a default data load binding, the Essbase model cannot be built.
If you add data load bindings to an existing cube schema from which an Essbase model has already been created, the cube schema and model will be out of sync. If you deploy from the existing Essbase model, the model will not pick up the new data load bindings, resulting in invalid deployment results. To deploy a cube using the new data load bindings, you must create a new Essbase model and deploy from the new model.
To specify default data load bindings in the Cube Schema Wizard:
In the Define data load mappings window, review the hierarchies displayed in the Cube Schema Elements column to determine for which hierarchies you want to specify default data load bindings.
Note the entries in the Key Binding column.
The Key Binding column contains:
Key bindings for elements whose data load binding can be changed.
The definition of user-defined members.
The status “Delayed” for any dimension elements that have a Delayed key binding.
The key bindings, definitions, and status in this column are read-only and are presented for your reference.
In the Data Load Binding column, click in the row of the lowest level of a selected hierarchy and take the appropriate action :
For relational, recursive, and calendar hierarchies whose key binding you want to change, click the ellipsis button,
, to launch the Default Load Binding dialog box, and proceed to step 4.For pure user-defined multichain hierarchies, select one check box.
For mixed multichain hierarchies, build a data load binding expression (step 4), or select the check box at the leaf level of one or more user-defined hierarchy chains.
For single or multichain measure hierarchies, specify a data load binding for one or more chains (step 4).
To build a binding expression, in Default Load Binding, under Formula, click the Source tab and navigate to the physical element on which you want to build a binding expression; then follow these steps:
Drag the physical element from Source to the Expression box.
Optional: Click the Functions tab and navigate to the function that you want to use in your expression, then drag that function to the Expression box.
Optional: Click the Operators tab and navigate to the operator that you want to use in your expression, then drag that operator to the Expression box.
Note:
You must place functions and operators precisely where they belong in the expression. Essbase Studio does not drop these items automatically into their correct places.
Click OK to close the Default Load Binding dialog box and return to the Define data load mappings page of the Cube Schema Wizard.
For hierarchies that contain user-defined members, indicate the default load member as follows:
For a pure user-defined, single-chain hierarchy, the lowest level in the hierarchy will automatically be selected for a data load, signified by a check mark in the Data Load Binding column. This check mark cannot be cleared.
In a pure user-defined, multichain hierarchy, select the lowest level from only one of the chains as the default load member (signified by a check mark in the Data Load Binding column).
For a mixed, single-chain hierarchy, where the lowest level is relational or column-based, click
and complete the substeps in step 4 to build a binding expression for the default load member.For a mixed, multichain hierarchy, where the lowest level is relational or column-based, click
for only one of the chains, and complete the substeps in step 4 to build a binding expression for the default load member. The default load member can be specified for only one chain in a multichain mixed hierarchy.
Click Finish to begin building the cube schema and, if you specified it, build the Essbase model.
Optional: When the process is complete, review the graphical representation of the Essbase model in the work area of the Essbase Studio Console.