Exporting budgets to data marts

This chapter contains procedures for exporting budgets from the Pillar application to an OLAP data mart.

You can export budgets to a Lawson Financials, Strategic Ledger, or Compensation data mart created using the Lawson Analytic Architect.

Note: You can also use these procedures to generate a CSV file.

It is important to note that Budget Architect updates Pillar budget data to an existing data mart. Budget Architect does not create a data mart.

The budget member name must exist in the data mart outline. You can create the budget member name using the Essbase Outline Editor. For the Lawson Financials and data marts, you can define the budget member in Analytic Architect Data Mart Manager (IA10), Parameters (GL87 and AC87), Scenarios tab.

You can use a unique budget member name for budgets that you create in the Pillar application and update to the data mart using Budget Architect. If the budget member name for Pillar budget data is unique, then Analytic Architect will not overwrite budget data with General Ledger or budgets. For example, you can name the budget member Budget 999. If you never create data in budget 999 in General Ledger, then Analytic Architect will not overwrite the Pillar data that you populate in the Budget 999 member.

This diagram illustrates the flow of budget data to the data mart:

Note: When you use Analytic Architect to load data from Lawson to the data mart, be careful about how you set the Data Clear parameter in Information Transfer Profiles (IA11.1). If this is set to Y and you have exported budgets from the Pillar application to the data mart, then Data Mart Load (IA120) may overwrite or clear the budgets.

This diagram shows the tasks involved in exporting budgets from the Pillar application to a data mart: