Overview of Workforce Budgeting data integration Designer-based

Workforce Budgeting integration supports metadata transfer from a source system through an integration database, via Infor EPM application processes into the business applications database.

During the standard data integration process, relational modeling is used to prepare, validate, and load source metadata into the integration database prior to loading data into the Infor EPM business applications database.

Table-based integration 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 meta data in related BODs.

Infor EPM supports the storage, analysis, and reporting of Workforce Budgeting data. To describe and organize this data, 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 position or employee information such as their assignment, workforce cost, and other types of data values.

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

You can import 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.

Stored procedures within the integration database can be modified to allow for customized data integration for more complex integrations.

Table-based integration is intended for the initial bulk load of dimension structures that occurs at the beginning of a budgeting process to initialize the system and from the regular data load. The data load includes position, employee or salary table information from a human resources 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.

The table-based integration process requires the use of Designer to update the Designer database and to recreate the OLAP database.