Local Currency Change for a Consolidation Unit Use A change of the local currency is primarily necessary in the following

cases: A company moves to a different country and reports its financial statements in a different currency. A consolidation unit or an entire country introduces a new reporting currency.

A consolidation unit wants to report its financial data in the group currency rather than in the local currency. When a consolidation unit changes its local currency, this function makes certain that: The balance carryforward data is posted in the new local currency.

All entries are posted in the new local currency starting on the closing date which always must be in line with a new fiscal year. Whenever the system needs to access data of previous years, this data is translated into the new currency on an ad-hoc basis (ad-hoc translation). (Inversions and prior year comparisons need to access prior year data.) Integration In contrast to the euro changeover, a local currency change does not abolish the old currency. Prerequisites Local currency changes must take place at the beginning of a fiscal year. The local currency change must be performed before you carry forward the balances or post new data for the new fiscal year. Otherwise the data could become inconsistent. See also Customizing for a Local Currency Change. Features Functions Affected by Local Currency Changes The following functions are affected by local currency changes: Balance carryforward

When the currency-bearing consolidation unit changes the attribute value for the local currency, the balance carryforward function needs to translate the values in the old currency into the new currency.

Period initialization (task)

Period initialization inverts documents of prior years. When a local currency changes, the system also needs to translate the prior-year documents to be inverted into the new currency. Other tasks that invert documents

These are tasks that post automatically and have document types that automatically invert postings of prior periods . (For example, document types for the elimination of interunit payables and receivables are configured to do this.) These tasks proceed as in period initialization tasks (discussed earlier). Mass reversal

Mass reversals proceed as in period initialization tasks (discussed earlier). Consolidation of investments with goodwill in local currency

If goodwill is carried in the local currency of the investee unit, the goodwill and investment values also need to be translated into the new currency. Validation

Validations sometimes compare prior year values. Such prior year comparisons may need to access data in the old local currency. In this case, the data needs to be translated into the new local currency. Currency Translation and Rounding for Local Currency Changes (Customizing Settings) The local currency key is an attribute of the currency-bearing consolidation unit. The assignment of this attribute is fiscal year dependent. When the local currency changes, starting in the new fiscal year the new currency is used by all functions that work with local currency values. Therefore, functions that access prior year data (in particular, balance carryforward, period initialization, and other inversion functions) need to react to the local currency change: In most cases the system translates the old currency (located in the data rows) into the new currency (according to the local currency key in the master data of the consolidation unit). To enable the system to translate prior year values into the new currency on demand, you specify a currency translation method in the Customizing settings for balance carryforwards.

For the currency translation method, we recommend that you merely specify a reference translation, rather than a specific translation. The system would not be able to take advantage of all of the functionality in specific translations anyway. We recommend also that you assign a rounding method to the currency translation method. You assign the currency translation method to the balance carryforward task. The system then derives the currency translation method that belongs to the consolidation unit from the Customizing settings for the balance carryforward. The system then applies this currency translation method (along with the assigned rounding method) to a set of data records. As a result, the local currency key and the local currency values are replaced by the new values. If necessary, the system calculates and posts any currency translation or rounding differences. Balance Carryforward for the Consolidation Unit with the New Local Currency When a consolidation unit changes its local currency, the balance carryforward function needs to translate the totals data as well as the local currency data of all data streams. The currency translation method to be used for this needs to be assigned to the balance carryforward task. The balance carryforward function then does the following: The function determines whether there are any consolidation units with the local currency to be changed. The function adds the following information to the balance carryforward task log: Currency translation method Exchange rate Old and new currency keys Old and new local currency values Rounding differences (if incurred)

Balance Carryforward for Totals Data, Investment Data, and Equity Data As an option, you can assign a rounding method to the currency translation method. This enables the system to post rounding differences depending on which data streams are used. However, in some cases, rounding differences cannot be posted: Totals data

The system stores translated data records in the totals database, including any rounding differences.

Investment data

Rounding is not possible for investment data. Equity data

Customizing the location of equity data offers you several options with different effects on balance carryforwards: Read from totals database

No equity data is carried forward. Read from additional financial data

No rounding differences are posted if the account assignment for rounding differences is not an equity item. Read from totals database and additional financial data

No rounding differences are posted if the account assignment for rounding differences is not an equity item, or if the account assignment is an equity item but this account assignment is read from the totals data. Special Case: New Local Currency Is Same as Group Currency In this case, the system does not apply any special logic. Note that ad-hoc translations can produce results that differ from historical currency translation. However, if you enter accumulated local currency data only in local currency, these differences automatically balance during the first period of the new fiscal year. If you want to continue to carry these historic differences between local and group currencies in the new group currency, you can either enter the data as period data or enter the data simultaneously in local currency and group currency (using flexible upload). Treatment of Values in Transaction Currency The system treats data in transaction currency differently, depending on whether the item has a breakdown by transaction currency: Items with breakdown by transaction currency:

The values in transaction currency remain unchanged. Items without breakdown by transaction currency:

After translation, the values in transaction currency are replaced with the default currency: Posting levels 00, 01, 10: Value is replaced by the local currency value. All other posting levels: Value is replaced by the group currency value.

****************************************** Customizing for a Local Currency Change Purpose You use this process to define your Customizing settings for local currency changes. Process Flow We recommend that you make the settings in the order shown below. If you have already carried forward the balances or posted new data for the new fiscal year before performing the local currency change (despite our recommendation), see SAP Note 722764. 1. Entry of the New Local Currency As soon as you know that a consolidation unit intends to change its local currency, perform the following steps: a. In the parameters of the Consolidation Workbench, temporarily change the fiscal year to the year, at the beginning of which the local currency is going to change. b. In the Customizing settings for the consolidation unit, specify the new local currency and save your entries (in the process view of the Workbench at Master Data Consolidation Units). c. In the parameters of the Workbench, change the fiscal year back to what it was before the temporary change (in step u201Cau201D). 2. Currency Translation Method with Rounding Method Create a currency translation method to be used exclusively for the local currency change u2013 even if you are still in the year prior to the change. This method merely needs to contain a reference translation with the following settings: Source key figure: period value in local currency Exchange rate determination: current exchange rate

 Rounding method: If possible, assign a rounding method. At a minimum, this method should ensure that the total assets are equal to the total liabilities and equity. Note that rounding must be done in local currency. Reference translations always take place in conjunction with the currency translation key. 3. Assignment of the Currency Translation Method to the Balance Carryforward Task Assign the currency translation method to the balance carryforward task. (You should make this assignment no later than the first period of the new fiscal year; but you can make it earlier than that, as well. You do not need to reverse the assignment later on.) Result When you perform the balance carryforward task, the system translates all of the values to be carried forward into the local currency. The task log includes information about the local currency change (see the section Local Currency Change for a Consolidation Unit).