Creating data mart relationships

To update a data mart with budget data exported from the Pillar application, you must map the budget data to the data mart dimensions.

You must create data mart relationships when you have new budgets and data marts, and when there are changes in your data mart outline or budget metadata.

  1. On Budget Architect (EB10.1), select a budget.
  2. Click Options. The Budget Options (EB19.1) is displayed.
  3. Click Data Mart Link. The Line Items to OLAP Data Mart (EB35.1) is displayed.
  4. Specify this information:
    Application Name
    Specify or select the data mart application name.
    Database Name
    Specify or select the data mart database name.
    Note: For Lawson Financials or Project Accounting Data Marts, you can click the Auto Build button to have Budget Architect automatically create relationships between budget information and data mart dimensions.
  5. Review the Budget Dimension tab. Ensure that the budget is a member of the data mart dimension that is displayed, and that the budget member name is correct. The budget member name must match the name in the outline.
    Note: For Lawson Financials Data Mart, you can use a budget member name specified on Financial Analyzer Dimension Definition (GL87.1), the Scenarios tab, or Budgets (GL87.4). For Project Accounting data mart, you can use a budget member name specified on Dimension Definition (AC87.1), the Scenarios tab, or Budgets (AC87.3).
  6. Review the periods and years on the Time Dimensions tab. Ensure that periods and years are mapped to the data mart dimensions that are displayed.
  7. Click Mbrs to see the periods and years that are members of each dimension.
  8. Review the Types Dimension tab to see the data mart dimension associated with amounts and units. Ensure that the Amounts and Units member names are correct.
    Note: If you export budget units from the Pillar application, then a unit member must exist in the data mart.
  9. Review the Report Dimensions tab. Click Associated To to see how data mart dimensions are mapped to budget dimensions.
    For example, the Lawson Financials Data Mart has separate dimensions for accounting units and accounts, and the Project Accounting data mart has separate dimensions for activities and account categories.
  10. Specify this information:
    Report Type
    Specify the mapping available for all the Pillar application's report types, or for a specific budget report type: Asset, Liabilities and Equity, Revenue, and Expense.
    Data Mart Dimensions
    For the Lawson Financials Data Mart, Accounting Units, and Accounts dimensions are displayed. For the Project Accounting Data Mart, Activity and Accounting Category dimensions are displayed.
    Budget Dimension
    Specify the budget dimension from Budget Architect metadata that corresponds to the data mart dimension.
  11. Update the changes.
  12. Click the Overrides button on EB35.2. The Data Mart Dimension Mapping (EB35.3) is displayed.
  13. To add or substitute the data mart dimension that was populated with the data exported from the Pillar application, specify this information:
    Apply Prefix to Value Names
    Specify a prefix that you can apply to the members that you are exporting from the Pillar application to the data mart.
    No Value Member Name
    Specify a member name to use if the data value exported from the Pillar application is blank.
    Fixed Member Name
    Specify a member name to use for all members in the dimension. This field replaces the data value exported from the Pillar application.
  14. Update the changes. The data mart relationships are created.
  15. Close the open forms to return to the EB10 form.