About loading dimensions

Updated: 2009-04-30

Consider the following guidelines when you load data into Planning Business Modeler.


You must be a member of the Data Administrator role to load dimensions by using tools in Planning Business Modeler or to load data by using the Planning Command Utility. For more information, see Security roles.

System rows

When a new application is created, some dimensions are pre-populated with system rows. When you add rows to a dimension that contains system rows, the MemberIds of the rows you add are set to 5001 or larger. For system dimensions that do not have predefined members and for user-defined dimensions, the MemberIds of the rows that are created begin at 1


   If you try to update or delete a system row, the row will not load and the BizSystemFlag value will become a 900+ error code.

The NONE row, where the MemberId is set to -1, is a system row that cannot be deleted, added, or updated in a dimension. NONE rows can be added to and deleted from a hierarchy but cannot be a parent or child within that hierarchy.

Models Site and Subsite

It is important know if the model site from which you load data is a root site or a subsite. If you load from a root site, the dimension members will belong to the root site. If you load from a subsite, the dimension members will belong to a subsite. In other words, the ownerID (ID of modelsite) that you enter is ignored because the system assigns the ownerID of the site from which the data is loaded.

Dimension Loading Order

Because of the relationships between some of the predefined system dimensions, we recommend that you load the system dimensions in the following order:

  1. Account

  2. Currency

  3. ExchangeRate

  4. Flow

  5. ConsolidationMethod

  6. Scenario

  7. Entity

Loading these dimensions in a different order can cause unexpected load failure. If you have created new dimensions, load the new dimensions after you load these dimensions. When you load the new dimensions, load them in a sequence that makes sure that references are maintained.

Dimensions That Cannot Be Loaded

The following predefined dimensions cannot be loaded because new members cannot be added to them:

  • BusinessProcess

  • Intercompany

  • Time

  • User


When you use Planning Business Modeler to load dimension data in the staging database, Planning Business Modeler automatically validates the data before loading it, unless explicitly instructed otherwise.

However, when you use the Planning Administration Console to load dimension data, validation is an option that you can enable or disable. See the Scriptable data integration topic for more information.

If you are reloading data that has rows with BizSystemFlag >= 900 or BizValidationStatus != 0, remember that these are ignored during the loading process and remain in the staging database.

The following list describes possible responses for rows that do not load.

  • View the corresponding error description and fix the error. After fixing the row or rows, set the BizSystemFlag to its original value and then load it again. Otherwise, Planning Server will ignore the rows. Planning Server assumes that rows with BizSystemFlag = 100 are in the application database

  • Ignore the row or rows that do not load to the application staging database. The next time that you synchronize, Planning Server deletes the rows that were ignored.

  • Delete the rows yourself.

Download this book

This topic is included in the following downloadable book for easier reading and printing:

See the full list of available books at Downloadable content for PerformancePoint Planning Server.

See Also