Overview of data integration for the Base Data Store Designer-based

Data integration for the Base Data Store does not require Infor ION, Infor Business Vault, or Infor Business Vault Base Data Store. Instead, use the delivered Base Data Store stored procedures to import budgeting and planning content from GL related BODs.

The Infor d/EPM business applications support the storage, analysis, and reporting of budgeting, planning, and strategy management data. To describe and organize this data for use by the Infor d/EPM business applications, structures are built in OLAP databases. The OLAP databases are known as models or cubes, and are formed by some number of dimensions, which are lists or hierarchies of dimensional elements. Like the rows, columns, and tabs of a spreadsheet, these dimensions provide the means to store and retrieve financial numbers and other types of data values.

Data and the required dimensional elements and structures can be loaded in a variety of ways.

This section describes importing from standard Microsoft SQL Server tables. For some scenarios and environments, this can be a relatively straightforward approach, using commonly understood database column mapping and SQL scripting concepts.

One method is to use the Base Data Store user interface for integration with the Base Data Store source system. Data mapping is done through user interface within the Infor d/EPM business applications. Stored procedures within the Integration database handle the transfer of data from the Base Data Store source system to the Infor d/EPM business applications.

The basic approach allows for importing data from a wide variety of source systems. ION, Business Vault, or Base Data Store are not required but can be used to import core financial data from published GL-related BODs. Stored procedures within the Integration database can be modified to allow for customized data integration for more complex integrations.

Data integration for the Base Data Store is intended for the initial bulk loading of structures and data from external source systems. For example, the chart of accounts from a financial system, or position information from a human resources system. This typically occurs at the beginning of the budgeting process to initialize the system. Incremental changes to the structure and data can be made by doing additional imports on existing content and opting to update existing elements and hierarchies.

This data integration process requires the use of Designer to update the Designer database and to recreate the OLAP database.