Consolidation in Multiple Group Currencies

Use

You can consolidate reported data into more than one group currency.

Reasons to do this might be:

  • You need to have a second reporting currency.

  • You want to do your planning in a different group currency.

  • You want to report in two currencies on the subgroup level: You disclose the subgroup result in the first group currency while reporting the subgroup result to corporate headquarters in their group currency.

    Example Example

    A subgroup reports in Swedish Kronor, but corporate group consolidates in euros.

    End of the example.

You only need to enter the reported financial data in local currency. Then you need to standardize the data, translate it into the group currency, and then periodically use a copy task to translate the reported data, documents, and additional financial data into the second group currency.

Integration

The group currency is not a property of the consolidation group.

The group currency key is a characteristic in the data basis .

You can carry multiple group currencies in each version .

If you only want to carry one group currency in a consolidation area, explicitly specify the value of the group currency key in the consolidation area .

However, if you want to carry multiple group currencies, you need to specify each group currency in the parameters of the Consolidation Workbench.

Features

Copying and Translation of Source Data

To translate reported financial data, documents, and additional financial data into an additional group currency, you use a copy task with a copy method – the copy method contains the currency translation method. The currency translation method, in turn, should have a rounding method.

If the copy method’s source group currency and target group currency vary, the system performs currency translation when the copy task is executed.

The copy task consists of the following steps:

  1. Read source data

  2. Execute mapping (if defined)

  3. Execute the BAdI (if defined)

  4. Currency translation and rounding according to the currency translation method

  5. Write target data in the target version

When totals data is copied, rounding differences can cause additional data rows. When documents are copied, additional document line items can be created.

If you periodically copy data (that is not accumulated), you can create the opening balances by copying the associated totals records one time only using the nonperiodic copy function .

If you copy the totals records cumulatively and copy documents at the same time, the system behaves as follows:

  • Totals records and documents are translated separately. However, documents are always translated periodically.

  • Then the system compares the translated totals records with the sum of the translated documents. Here, the translation of totals records takes precedence.

    If a difference is found, the system creates a correction document. The document text denotes that this is a correction document. The correction document is also listed in the copy task log.

Copy Task Log

When data is translated into another group currency, the copy task log shows the following in addition to the ordinary information:

  • In the source data section: the group currency key of the source version

  • Error messages generated during currency translation

  • In the target data section: rounding differences

  • Correction documents (if created)

Activities

Copy Method

See also the more general description in Defining a Copy Method .

Under Data Type , choose All Data Types .

SettingsTab Page

  • Specify the update mode . We recommend the option Delete All.

  • Specify the input type. We recommend Cumulative Data Entry because this option does not require you to separately create the opening balances, as opposed to periodic data entry (see earlier).

  • Specify a BAdI filter (if applicable).

    (For detailed information, see field help, the system documentation for the UC_DATATRANSFER BAdI, and the documentation of its methods.)

Source/Target VersionTab Page

  • Specify the source and target group currencies, and enter a currency translation method (see below).

  • Specify the source and target versions.

    • Source version = target version:

      To copy all of the data (and, in particular, to retain the hierarchy of consolidation units), copy to the same version.

    • Source version ≠ target version:

      If you do not want to copy all of the data and you want to have different subhierarchies in the two versions (in scenarios such as the subgroup scenario discussed earlier), choose a target version that does not equal the source version.

MappingTab Page

If applicable, define how the fields are mapped. See also Mapping .

SelectionTab Page

If applicable, define a source and/or target selection .

For example, you can restrict the target selection as follows:

  • By posting levels

  • By document types (when copying documents)

  • But not by consolidation unit or group

    Instead, we recommend assigning the copy method to the consolidation units or groups in the copy task. For example, for copying reporting data and standardized reporting data, choose the option Dependent on Consolidation Unit in the Per Consolidation Unit processing type and set the relevant indicator for the consolidation group affected.

Currency Translation Method

Create a currency translation method that translates the data into the second group currency only. This method should only use reference translation since not all functions are available anyway in specific translations. (For example, you cannot determine the relationship between the source and target group currencies according to the additional financial data because no data exists in the target group currency.) The reference translation should have the following settings:

  • Source key figure: value in group currency

  • Exchange rate determination: exchange rate indicator and exchange rate type; current exchange rate

  • Rounding method: If possible, assign a rounding method. This method needs to round in group currency and, at a minimum, should ensure that total assets are equal to total liabilities and equity.

    Note Note

    Reference translations always use the currency translation key “cumulative”.

    End of the note.
Copy Task

See also the general description in Copy Task and Define Copy Task .

  • Specify which data streams should be copied with this task: totals data plus documents (if applicable) and/or additional financial data.

  • We recommend that you define a source task so that any subsequent changes to the source data (such as the entry of additional documents) affect the status of the target task.

  • In order to copy reporting data and standardized reporting data, use the Per Consolidation Unit processing type. If you select the Dependent on Consolidation Unit option, you can, for example, copy the data from various consolidation units from various versions into a target version in which you assign multiple copy methods.

  • To copy documents from the posting levels 02, 12, 20, 22, and 30, use the Per Consolidation Group processing type and choose the consolidation group for which the copy task should be performed.

Inserting the Copy Task into the Task Hierarchy or Task Sequence

Add the copy task to the target hierarchy for the target version.

Task Sequence

In the target version, the copy task is the first relevant task that follows the balance carryforward and period initialization. The tasks for higher posting levels are after the copy task.

Arrange the target tasks in the target version in the following order:

  1. Balance carryforward

  2. Period initialization

  3. Data collection task (if not all consolidation units are copied)

  4. Copy task

  5. Standardizing entries (if applicable)

  6. Tasks for higher posting levels

Executing the Copy Task

You run the copy task in the Consolidation Monitor in the target version using the target group currency.

Example

See the following section: Example: Consolidation in Two Group Currencies .