Share via

About the NONE dimension member

  • Article

The NONE member is a specialized member of a dimension. Planning Business Modeler uses the NONE member when it performs system-defined calculations and when a member of a dimension must be selected for a system process. In predefined dimensions, the NONE member is often the default member of the dimension.

The following predefined dimensions contain the NONE member: Account, ConsolidationMethod, Currency, Entity, Exchange Rate, Flow, and Intercompany. When Planning Business Modeler creates the following predefined dimensions, it adds the NONE member to the dimension.

The following predefined dimensions do not contain the NONE member: Business Process, TimeDataView, User, and Time.

User-defined dimensions include a NONE member that Planning Business Modeler includes when the dimension is created.

Characteristics important for users

The following list describes characteristics of the NONE member that are important for users to consider.

  • The NONE member must not have children

    The NONE member must be leaf level. If a NONE member has children, data writeback fails for various financial intelligence processes.

  • If you create a dimension member with the label NONE, that member will not have the special behavior described in this topic for other dimensions. Planning Business Modeler assigns a special member ID to a system-defined NONE member, and the special characteristics of a system-defined NONE member depend on this ID.

Other characteristics

The following list describes other characteristics of the NONE member.

  • The NONE member must have label of "NONE." This label cannot be changed.

    Some predefined rules, such as the Aggregation rule, reference a member with label NONE.

  • The NONE member must have member ID of -1

    Planning Business Modeler assigns the member ID of -1 to a NONE member to a system-defined NONE member. However, Planning Business Modeler does not assign a member ID to a user-defined member with a label NONE.

  • The NONE member must be unique throughout a dimension and a member set.

  • The NONE member must be located in the All Members list for some system-defined dimensions, but not all.

  • The NONE member cannot be deleted from a dimension

    Planning Business Modeler does not include a mechanism that can delete the NONE member from a dimension. However, you may remove the NONE member from a member set.

  • NONE is used as the default location for data when a new dimension is added to a model.

    When Planning Business Modeler adds a new dimension to a model, Planning Server adds a new column to the fact table to represent that dimension, and fills this column with -1. When Planning Business Modeler creates a system-defined NONE member, it assigns a member ID of -1. Therefore, if a new model dimension contains a NONE member, Planning Server associates the fact rows for the newly added dimension with the NONE member.

    If a new dimension does not contain a NONE member, the data may not be considered valid and will not be deployed when the cube reprocesses. To make sure that data for a new dimension is correctly processed, we recommend that you create a copy of the model. Then, load data for the new dimension to the copy. Finally, move the data from the model copy to the new dimension in the original model by using a Data Movement job.

    For more information about how to do this, see How do I create an association to move data between models?

  • In cross-model allocation rules, if a dimension exists only in one model, and is not explicitly scoped, Planning Business Modeler writes the data to the NONE member for that dimension.

Special characteristics in financial models

The following list shows characteristics of the NONE member that are valid only for financial models

  • In financial models, NONE is the only Flow dimension member that has data for Income Statement accounts and Non-financial accounts.

    For this reason, when you are using a financial model, the flow member set that you select should include the NONE member.

    Income Statement and Non-financial accounts can contain data ONLY at the NONE member in the Flow Dimension. However, Balance Sheet accounts cannot use the NONE member. Balance Sheet accounts can ONLY be used with the other members of the flow dimension.

    Data writeback validation will reject all other combinations of flow and account data.

  • The Intercompany Reconciliation process treats fact data in the NONE intercompany member as a non-intercompany transaction.

    In a financial model, any data found in the NONE slice for intercompany is considered not an intercompany transaction. Intercompany reconciliation rules ignore this value.

  • In financial models, NONE is the only valid Intercompany selection for Account types with Intercompany = False or for Entity types with Intercompany = False.

    Both Account dimension members and Entity dimension members have an Intercompany property. In the Account dimension, the Intercompany property indicates which account types can be used in an Intercompany transaction. In the Entity dimension, the Intercompany property indicates which Entities can have intercompany transactions with sibling companies.

    Planning Server will reject data if a user tries to submit an intercompany transaction to one of these accounts. In this situation, the user should write to the NONE member.

See Also

Other Resources

Predefined dimensions
Dimensions and members in Planning Business Modeler