About the NONE member

PerformancePoint Planning Business Modeler uses a special dimension member called the NONE member. In effect, the NONE member acts as a default member of a dimension when no other default member has been specified. Thus, for example, when Planning Business Modeler performs a system-defined calculation, and no other dimension member has been specified to hold the results of the calculation, then Planning Business Modeler uses the NONE member to store the results.

Planning Business Modeler automatically includes a NONE member in several predefined dimensions, and in all user-defined dimensions.

What do you want to learn more about?

Important characteristics of the NONE member

Special characteristics of the NONE member in financial models

Predefined dimensions and the NONE member

Important characteristics of the NONE member

The following list describes characteristics of the NONE member that are important for Data Administrators, Modelers, and Business Analysts.

  • The NONE member must not have children.

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

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

  • The NONE member cannot be deleted from a dimension. You can remove the NONE member from a member set, but you cannot delete the member from the dimension.

  • The NONE member must have a label of 'NONE' that cannot be changed.

    However, if you create your own dimension member, and give that member the label 'NONE,' that member will not have the special behavior described in this topic.

    Planning Business Modeler assigns a special member ID of -1 to a system-defined NONE member. The special characteristics of a system-defined NONE member depend on this ID. When a user defines a dimension member and then assigns the member a label of 'NONE,' Planning Business Modeler does not assign the special member ID to the user-defined member.

  • Some predefined rules, such as the Aggregation rule, reference a member that has a label 'NONE.'

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

    For example, Planning Business Modeler uses the NONE member to perform cross-model allocation when there is a mismatch between source dimensions and destination dimensions. When a dimension exists only in the source model, Planning Business Modeler writes the allocated data to the NONE member in the destination dimension.

  • When you add a new dimension to a model, Planning Business Modeler adds a new column to the fact table in the application database to represent that dimension. Then, Planning Business Modeler writes a value of -1 in every row of the new column. Because -1 is the member ID for a system-defined NONE member, Planning Business Modeler associates the fact rows for the newly added dimension with the NONE member.

    If a newly added dimension does not contain a NONE member, the data might 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 take the following steps:

    1. Create a copy of the model.

    2. Load data for the new dimension to the copy.

    3. Create a model-to-model association between the original model and the copy.

    4. 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 create and use an association, see How do I use an association to move data between models?

Top of Page

Special characteristics of the NONE member in financial models

The following list delineates the 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.

    Thus, when you use 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 in 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 write-back validation will reject all other combinations of flow and account data.

  • The Intercompany Reconciliation process treats fact data in the NONE member as a non-intercompany transaction. That is, Intercompany Reconciliation rules ignore the NONE member.

    Therefore, NONE is the only valid Intercompany selection for Account types with Intercompany = False or for Entity types with Intercompany = False.

    In the Account dimension, the Intercompany property indicates whether an account type can be used in an Intercompany transaction. In the Entity dimension, the Intercompany property indicates whether an Entity can have intercompany transactions with sibling companies.

Top of Page

Predefined dimensions and the NONE member

When it creates predefined dimensions, Planning Business Modeler adds a NONE member to some of the dimensions and not to others. If the NONE member is added to a predefined dimension, it must be located in the All Members list.

The following table shows which predefined dimensions contain the NONE member.


Contains NONE member?



Business Process








Exchange Rate












Top of Page

Share Facebook Facebook Twitter Twitter Email Email

Was this information helpful?

Great! Any other feedback?

How can we improve it?

Thank you for your feedback!