Data in Local Currency

You can import actuals or other data to the Infor d/EPM business applications from the BudgetingMain integration import table.

In Financial Consolidation, this financial data from several entities within a group is combined, usually for reporting purposes. In Finance, the consolidation process includes importing data, mapping a local chart of accounts to a group chart of accounts, normalizing consolidated data, and producing consolidated financial statements. The frequency of performing financial consolidation differs from entity to entity and often depends on regulatory requirements.

In Infor d/EPM Budgeting & Planning, fact data is typically used for comparison of actuals and budget data. Fact data can also be used as initial data for forecasting or proposal data for budget.

The data is stored in an entity's local currency.

The use of business data from the Data in Local Currency integration table is required in Budgeting & Planning and Financial Consolidation. In Workforce Budgeting, that data is not used.

This table shows the properties of the Data in Local Currency table and uses these abbreviations:

  • BP: Budgeting & Planning
  • WB: Workforce Budgeting
  • CO: Financial Consolidation
  • R: Required
  • U: Used but optional
Field Description Type BP WB CO
Period Period number.

In Budgeting & Planning, Business Modeling data import translates periods in this way:

  • 0 to 01
  • 13-16 to 12
  • The remaining periods are translated to two-digit periods (PP).

Business Modeling data import merges a period and year to the PP_YYYY format, for example, 01_2019.

In Financial Consolidation, data load translates periodic data in this way:

  1. 0 to an opening balance. The Schedule definition for the corresponding group accounts with opening balances is required.
  2. The remaining periods 1-12 are recalculated as YTD periods.

    Data from periods 13-16 is aggregated under period 12.

In Financial Consolidation, YTD values are loaded in this way:

  1. Data from periods 1-12 is loaded to the corresponding periods in Financial Consolidation.
  2. Data from periods 0 and 13-16 is not loaded into Financial Consolidation. The opening balances for the remaining periods are loaded with the corresponding Schedule Details definitions. For example, the opening balance for period 1 and schedule D is loaded with schedule detail D_OB and period = 1.

See "Periods 13-16 in the Infor d/EPM business applications".

 integer R R R
Year Translated to the YYYY format.

Business Modeling data import merges a period and year to the PP_YYYY format, for example, 01_2019.

 integer R R R
Entity Base level record from the Entities business object. nvarchar R R R
Version Used to separate past data, such as facts or actuals, from the future period data, such as forecasts or rolling forecasts. Can also be used in simulations.

If left blank, then data is loaded to the Actuals element of the Version dimension.

Note: Currently, you can load data to multiple versions only in Financial Consolidation.
 nvarchar U
Level Represents consolidation stages of entities. Enables a local GAAP creation with separate levels for data entries, adjustments, and reclassifications. For example, an adjustment stage of transitioning from local GAAP to IFRS or to US-GAAP, corrections, currency translation, or intercompany matching of an entity.

If left blank, then data is loaded to the Imported Data element of the Adjustment Levels dimension.

Note: You can load data to multiple levels only in Financial Consolidation.
 nvarchar U
Intercompany Entity ID for an internal trading partner.

Used for intercompany amounts only. An account must allow intercompany transactions.

If left blank, transaction data is considered as external.

 nvarchar U U
Organization Base level record from the Organizations business object, for example, a company cost center.

If left blank, transaction data is not assigned to any organization.

 nvarchar U U
Account Base level record from the Accounts business object. nvarchar R R R
ScheduleDetail Identifier of a schedule detail from the Schedule Details business object.

In Financial Consolidation, schedule details can be used, for example, to load opening balances or other details such as increases or decreases.

Opening balances are loaded typically into subschedules.

In Financial Consolidation, to load periodic data with schedule details from periods 1-16, these conditions must be met:

  • Periods must be in the range of 1-16.
  • The referenced group account must have a schedule assigned.
  • The ScheduleDetail field must be populated with a schedule detail that is linked to the assigned schedule. Otherwise, data cannot be loaded.

In Financial Consolidation, to load opening balances, these conditions must be met:

  • For periodic data, a record's period must be 0. For YTD data, you must specify a schedule detail ID for each period from the range of 1-12 to which to load an opening balance.
  • The referenced group account must have a schedule assigned and that schedule must have the Opening Balance property enabled in Business Modeling.
  • For periodic data, the ScheduleDetail field can be blank. Data is automatically loaded as an opening balance into Financial Consolidation. Values in the ScheduleDetail field are not considered because data is loaded to built-in elements for opening balances.

In Budgeting & Planning, you can load data to the existing elements of the Schedule Details dimension.

See "Loading opening balances into Financial Consolidation" and "Transforming financial data into YTD in Financial Consolidation".

 nvarchar U U
Currency Three-letter ISO code of the entity currency.

Business Modeling data import adds the _LC suffix to the currency code, for example, EUR_LC.

Not applicable for statistical accounts of M or O types that are not associated with a currency, for example, volume.

 nvarchar R R R
Analysis01 Base level record from the Analysis 1 business object.

If left blank, transaction data is not assigned to Analysis01.

 nvarchar U U
Analysis02 Base level record from the Analysis 2 business object.

If left blank, transaction data is not assigned to Analysis02.

 nvarchar U U
Analysis03 Base level record from the Analysis 3 business object.

If left blank, transaction data is not assigned to Analysis03.

 nvarchar U U
Analysis04 Base level record from Analysis 4 business object.

If left blank, transaction data is not assigned to Analysis04.

 nvarchar U U
Analysis05 Base level record from Analysis 5 business object.

If left blank, transaction data is not assigned to Analysis05.

 nvarchar U U
Analysis07 Base level record from Analysis 7 business object.

If left blank, transaction data is not assigned to Analysis07.

 nvarchar U U
Analysis08 Base level record from Analysis 8 business object.

If left blank, transaction data is not assigned to Analysis08.

 nvarchar U U
Analysis09 Base level record from Analysis 9 business object.

If left blank, transaction data is not assigned to Analysis09.

 nvarchar U U
Analysis10 Base level record from Analysis 10 business object.

If left blank, transaction data is not assigned to Analysis10.

 nvarchar U U
Analysis11 Base level record from Analysis 11 business object.

If left blank, transaction data is not assigned to Analysis11.

 nvarchar U U
PrimarySegment Base level record from the Segments 1 business object.

An account must support segmentation.

If left blank, transaction data is not assigned to PrimarySegment.

 nvarchar U U
SecondarySegment Base level record from the Segments 2 business object.

An account must support segmentation.

If left blank, transaction data is not assigned to SecondarySegment.

 nvarchar U U
TertiarySegment Base level record from the Segments 3 business object.

An account must support segmentation.

If left blank, transaction data is not assigned to TertiarySegment.

 nvarchar U U
PrimaryInterSegment Base level record from the Segments 1 business object.

An account must support segmentation.

If left blank, transaction data is not assigned to PrimarySegment.

 nvarchar U
SecondaryInterSegment Base level record from the Segments 2 business object.

An account must support segmentation.

If left blank, transaction data is not assigned to SecondarySegment.

 nvarchar U
TertiaryInterSegment Base level record from the Segments 3 business object.

An account must support segmentation.

If left blank, transaction data is not assigned to TertiarySegment.

 nvarchar U
Value Transaction amount in the functional currency of an entity.

Budgeting & Planning stores period movement amounts. Financial Consolidation translates period movement amounts to YTD amounts. Expense amounts from the E-type accounts and Schedule Detail that represents a decrease are stored as negative numbers. Amounts from all other account types are stored as positive numbers.

 float R R R
Related topics