Facts Transaction Currency
The Facts Transaction Currency integration table stores financial data in the transaction currency. The transaction currency can differ from the local currency, which is stored in the Facts Local Currency integration table.
In Financial Consolidation, transactions relate only to group accounts that are configured for these consolidation processes:
- Consolidation of Expenditures and Revenue
- Consolidation of Debts
Business data from the Facts Transaction Currency integration table is not used in Budgeting & Planning and Workforce Budgeting. In Financial Consolidation, use of that data is optional.
This table shows the properties of the Facts Transaction 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 Financial Consolidation, data load translates periods in this way:
For more information, 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 |
integer | 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 | ||
| Entity | Base level record from the Entities business object. | nvarchar | R | R | R |
| Intercompany | Entity ID for an internal trading partner. Used for intercompany amounts only. An account must allow intercompany transactions. If left blank, transaction records cannot be loaded to Financial Consolidation. |
nvarchar | R | ||
| 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 | ||
| 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. Can be used, for example, to load opening balances or other details such as increases or decreases. Opening balances are loaded typically into subschedules. This property is not used for financial data in a transaction currency. |
nvarchar | U | ||
| Currency | Three-letter ISO code of the transaction currency. Can differ from the entity's local currency. 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 | ||
| Analysis02 | Base level record from the Analysis 2 business object. If left blank, transaction data is not assigned to Analysis02. |
nvarchar | U | ||
| Analysis03 | Base level record from the Analysis 3 business object. If left blank, transaction data is not assigned to Analysis03. |
nvarchar | U | ||
| Analysis04 | Base level record from Analysis 4 business object. If left blank, transaction data is not assigned to Analysis04. |
nvarchar | U | ||
| Analysis05 | Base level record from Analysis 5 business object. If left blank, transaction data is not assigned to Analysis05. |
nvarchar | U | ||
| Analysis07 | Base level record from Analysis 7 business object. If left blank, transaction data is not assigned to Analysis07. |
nvarchar | U | ||
| Analysis08 | Base level record from Analysis 8 business object. If left blank, transaction data is not assigned to Analysis08. |
nvarchar | U | ||
| Analysis09 | Base level record from Analysis 9 business object. If left blank, transaction data is not assigned to Analysis09. |
nvarchar | U | ||
| Analysis10 | Base level record from Analysis 10 business object. If left blank, transaction data is not assigned to Analysis10. |
nvarchar | U | ||
| Analysis11 | Base level record from Analysis 11 business object. If left blank, transaction data is not assigned to Analysis11. |
nvarchar | 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 | ||
| 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 | ||
| 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 | ||
| 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 transaction currency of an entity. 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 |