Currencies

You can work with different currencies in drilldown reporting. Note that the currency settings you make are the same for both the drilldown and detail lists. That means that a single column of the drilldown list has the same target currency and currency translation type as the cell of the detail list which corresponds to that column.

Currency translation

Currency translation is defined by the

If a form contains formula columns which use different currencies, the system performs currency translation automatically using translation type 999.

If you perform currency translation on the detail list of a report, the system also translates the corresponding column of the drilldown list.

If you use currency translation, it may make sense to define a dummy column which is ignored during translation. This makes it possible to still display the original currency.

(See also the standard report 0-SAP05 for account-based Profitability Analysis in operating concern S001.)

A report consists of the following four columns:

Currency translation types

Some currency translation types already contain the target currency in their definition.

A few important currency translation types are delivered with the standard R/3 System. These include:

Type:

Description:

1

Mean rate, cutoff date today

2

Selling rate, cutoff date today

3

Buying rate, cutoff date today

4

Selling rate, cutoff date start of period

5

Mean rate, cutoff date start of period

6

Buying rate, cutoff date start of period

 

You can also define your own currency translation types. The functions which let you do this are found in Customizing.

The currency translation type fixes certain details of how the currency translation is to be carried out. It represents a summary of various rules when carrying out a currency translation. These details, which you can combine in a translation key, are:

  1. the exchange rate type (for example, bank buying rate, average rate)
  2. The valid exchange rate types are stored in a central SAP table and can be maintained there.

  3. the currency into which you are translating
  4. This field is optional which means you can leave it empty. This is recommended in most cases. For example, in the transfer of external data to the transaction data table, the target currency is normally implicitly known and can be determined by the transfer program when it runs. If you often want to use the same translation type for different target currencies when translating currency-dependent values in drilldown reporting, then only currency translation types without a specific target currency are suitable.

  5. the flag which indicates whether this is an inverse exchange rate
  6. This is useful if the amounts have already been translated once during the external data transfer and if the original values are to be displayed again in the drilldown report.

  7. the flag which indicates whether this is a fixed or variable translation
  8. A fixed translation date is either the current date or a specific date from which the exchange rate is valid.

    With a variable translation date, you specify the time reference (i.e. period begin, year end).

  9. the flag, which indicates whether the source currency in a data transfer is fixed or variable
  10. With a fixed source currency, the currency of all records sent together is the same and is recognized by the system, for example, DEM.

    With a variable source currency, the currency of each record sent is stored in a field of this record and often varies from record to record. When the currency is translated, the system determines the source currency from the record itself and translates the currency.

  11. the source currency (From-currency)
  12. You leave this field empty for currency translation types for drill- down reporting as the source currency is known for all values.

    See number 5 for currency translation types for data transfer.

  13. the time reference for the time-dependent currency translation.

The following are supported:

  1. Fiscal year end
  2. Period end
  3. Period begin
  4. If the transaction data table contains characteristics with a time dimension (i.e. trading day), the following is also supported:

  5. Exact day

The requirement for using these options for the time reference in a drilldown report is, that the relevant characteristics have been chosen for the report. Where the period is concerned, note that it is only valid in the context of a fiscal year.

Inverse rates

An exact reverse calculation is, however, only possible under certain conditions. In data transfer, several records with different exchange rates cannot be summarized to one record. The data for which the exchange rate is taken from the central SAP table, must either be a specific date (for example, 12/31/94) or be derived from a characteristic, that is contained in a sender record as well as in the drilldown report. To see how this works, see Example: Inverse Rates.