Data loads into Financial Consolidation from the business perspective

This section describes the processes and use cases that are related to loading data from a source system, such as ERP, into Financial Consolidation. It contains only business and functional descriptions. No technical details are described.

This section references this data:

  • Data in Local Currency

    Financial data in a local currency. This data is stored in the BudgetingMain integration table in relational modeling. This data is required in Financial Consolidation.

  • Data in Transaction Currency

    Financial data in a transaction currency. This data is stored in the FactsTransactionCurrency integration table in relational modeling. This data is optional in Financial Consolidation.

  • Exchange Rates

    Historical exchange rates. This data is optional in Financial Consolidation.

Data structure

These types of data can be loaded into Financial Consolidation:

  • Periodic data

    Related to a specific financial year or month. Records with the same structure are aggregated.

  • YTD data

    Aggregated at the year-to-date level. Each period and year represent the data aggregation from the beginning of a financial year.

For each entity, you can configure which type of data to load into Financial Consolidation.

Data load types

To integrate data between source systems and Infor d/EPM, these types of financial data load into Financial Consolidation are defined:

  • Initial data load

    Performed at the beginning of an integration project. A consultant or an administrator loads historical data from a source system into Infor d/EPM.

  • Selective data load

    Performed regularly, typically monthly. For this type of data load, a source system must be in sync with Data Lake, which is a single source of truth for data and metadata within Infor d/EPM.

User roles

Users of these roles are involved in data loads into Financial Consolidation:

  • Administrator or Implementation Consultant

    Typically, performs all steps of an initial load. For selective data loads, the user ensures that the source system data is available in the Infor d/EPM integration tables and the metadata is up to date in Business Modeling.

  • Consolidation Modeler

    Does administrative tasks in Business Modeling. For example, if there is a change in the chart of accounts, entity structure, or other metadata, the user ensures that this change is applied in Business Modeling and published to OLAP before data load.

  • Entity Accountant

    Performs selective loads of data from the Data in Local Currency and Data in Transaction Currency tables.

  • Group Accountant

    Loads the Exchange Rates data.

Related topics