The instructions in Storing financial data show you how to include your financial data in your database, in a MicroStrategy fact table. With this data stored in a fact table, you are ready to create schema objects to integrate the financial data into a MicroStrategy project.
Your fact table should include a single column that stores the financial data for all of the financial accounts.
To create schema objects for financial data
|1||Using MicroStrategy Architect, you must create a fact to integrate the data into the project. This can be a simple fact that points directly to the column in your database that stores the financial data. For steps to create facts, see Creating and modifying facts.|
|2||Each category used to define the level of data in this fact table must be included in MicroStrategy as an attribute. In addition to the fact table, you may have additional lookup tables that provide the descriptive data for these categories. Within the fact table, the ID column of each category should be included. The image below shows an example of what the fact table might look like in MicroStrategy, with a single fact column (Data) of financial data, and additional attributes to categorize the financial data.|
Notice that a Level3 attribute is included in the fact table above. This is the lowest level attribute included as part of creating the financial line items, as described in Creating attributes for financial line items. It is important to include this column of data and associated attribute in this fact column because it identifies which financial line item is associated with each value in the Data column. Without this column, you cannot accurately identify the values for the Data fact that integrates this data into MicroStrategy.
|3||For additional details on how to create the other attributes required to categorize your financial data, see The Context of Your Business Data: Attributes.|