Rules for Assigning Field Types

Table 42 lists the rules for selecting valid field types, depending on the build method.

Table 42. Rules for Assigning Field Types Based on Build Method

Build Method

Rules for Assigning Field Types

Generation

  • If GEN numbers do not start at 2, the first member of the specified generation must exist in the outline.

  • GEN numbers must form a contiguous range. For example, if GEN 3 and GEN 5 exist, you must also define GEN 4.

  • Put DUPGEN fields immediately after GEN fields.

  • Put DUPGENALIAS fields immediately after DUPGEN fields.

  • Group GEN fields sequentially within a dimension. For example:

    GEN2,PRODUCT   GEN3,PRODUCT   GEN4,PRODUCT

  • Put attribute association fields after the base field with which they are associated, and specify the generation number of the associated base dimension member. For example:

    GEN2,PRODUCT   GEN3,PRODUCT   OUNCES3,PRODUCT

    The generation number must correspond to the generation of the member in the outline for which the field provides values. For example, the 3 in GEN3,PRODUCT shows that the values in the field are third-generation members of the Product dimension. The 2 in ALIAS2,POPULATION shows that the values in the field are associated with the second-generation member of the Population dimension.

Note:

When using the generation build method to create a duplicate member dimension, the maximum number of generations is 20.

Level

  • Put DUPLEVEL fields immediately after LEVEL fields.

  • Put DUPLEVELALIAS fields immediately after the DUPLEVEL fields.

  • Each record must contain a level 0 member. If a level 0 member is repeated on a new record with a different parent, Essbase rejects the record unless you select the Allow Moves member property. See “Setting and Modifying Member Properties” in the Oracle Essbase Administration Services Online Help.

  • Group level fields sequentially within a dimension.

  • Put the fields for each roll-up in sequential order.

  • Use a single record to describe the primary and secondary roll-ups.

  • Put attribute association fields after the base field with which they are associated, and specify the level number of the associated base dimension member. For example:

    LEVEL3,PRODUCT   OUNCES3,PRODUCT   LEVEL2,PRODUCT

  • The level number must correspond to the level of the member in the outline for which the field provides values. For example, the 3 in LEVEL3,PRODUCT shows that the values in the field are level 3 members of the Product dimension. The 2 in ALIAS2,POPULATION shows that the values in the field are associated with the second level of the Population dimension.

Parent-child

If field type is parent or child, enter 0 (zero) in the Number text box.

Attribute dimension name

The generation or level number must correspond to the generation or level of the associated base member in the outline. For example, the 3 in OUNCES3,PRODUCT shows that the values in the field are the members of the Ounces attribute dimension that are associated with the third-generation member of the Product dimension in the same source data record.

If necessary, move the fields to the required locations. See Moving Fields.

  To move fields, see “Moving Fields” in the Oracle Essbase Administration Services Online Help.