Hierarchy
SAP_ABA (Software Component) Cross-Application Component⤷
CA-GTF-DCM (Application Component) Data Transfer⤷
BKD (Package) Tools for (external) data transfer
Basic Data
| Data Element | CFNUMBR |
| Short Description | Number of translation key in currency translation |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CFNUMBR | |
| Data Type | NUMC | Character string with only digits |
| Length | 3 | |
| Decimal Places | 0 | |
| Output Length | 3 | |
| Value Table | T242Q |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | NBR | |
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Type |
| Medium | 15 | Curr.trans.key |
| Long | 20 | No.of cur.trans.type |
| Heading | 3 | Ty. |
Documentation
Definition
You come across the term "currency translation type", in the context of currency translation, in two different places:
- when transferring external data to the transaction data table, if a currency translation is to take place at the same time.
- In drilldown reporting, when translating currency-dependent values into currencies which differ from those in the transaction data table.
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:
- the exchange rate type (for example, bank buying rate, average rate).
The valid exchange rate types are stored in a central SAP table and can be maintained there. - the currency into which you are translating;
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. - the flag, which indicates whether this is an inverse exchange rate;
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. - the flag, which indicates whether this is a fixed or variable translation;
A fixed translation date is either the current date or a specific date from which the exchage rate is valid.
With a variable translation date, you specify the time reference (i.e. period begin, year end). - the flag, which indicates whether the source currency in a data transfer is fixed or variable;
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. - the source currency ('From-currency');
You leave this field empty for currency translation types for drilldown reporting as the source currency is known for all values.
See number 5 for currency translation types for data transfer. - the time reference for the time-dependent currency translation. The following are supported:
1 Fiscal year end
2 Period end
3 Period begin
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.
=========================Appendix======================================
3.) the flag, which indicates whether this is an inverse exchange
rate.
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 drill-down report. The following examples should clarify this:
The three records to be transferred to the transaction data table should have the following structure:
Fiscal year Period Posting day Sales area | Sales |Currency
--------------------------------------------------|--------|---------
1995 001 1.5.95 B3Z | 100 | DEM
1995 001 1.9.95 A3F | 200 | DEM
1995 002 2.7.95 27A | 200 | DEM
The records are to be posted in USD to the transaction data table, which does not contain the posting day as a characteristic. The following possibilities arise:
- Translation on a specific date, e.g. 12/31/1994, using the bank buying rate. Example exchange rate is 0.7 USD/DEM.
The records in the transaction data table then appear as follows:
Fiscal year Period Sales area | Sales |
--------------------------------------|--------|
1995 001 B3Z | 70 |
1995 001 A3F | 140 |
1995 002 27A | 140 |
Sales of 350 USD for fiscal year 1995 will be displayed in the drilldown report. You can calculate this from the inverse exchange rate
1 / (0.7 USD/DEM) = (1 DEM)/(0.7 USD)
and get the value
350 USD * (1 DEM)/(0.,7 USD) = 500 DEM, i.e. the original
amount.
Note that, the reverse calculation always works if you have translated with an exchange rate unique to a specific date during the data transfer. - Time-dependent translation at period end using the bank buying rate. The example exchange rate for this is:
0.6 DEM/USD for 1/31/1995
0.8 DEM/USD for 2/28/1995.
The records in the transaction data table appear as follows:
Fiscal year Period Sales area | Sales |
--------------------------------------|--------|
1995 001 B3Z | 60 |
1995 001 A3F | 120 |
1995 002 27A | 160 |
Sales of 340 USD for fiscal year 1995 are displayed in the drilldown report. If you chose the fiscal year and the period or, alternatively, the 7-digit Period 'yyyymmm' when defining the report, then you can also calculate the original amount from the inverse exchange rate. The drill down report works with the inverse period exchange rates
1 / (0.6 USD/DEM) = (1 DEM)/(0.6 USD) and
1 / (0.8 USD/DEM) = (1 DEM)/(0.8 USD)
and calculates the value
(60 USD + 120 USD) * (1 DEM)/(0.6 USD) +
( 160 USD ) * (1 DEM)/(0.8 USD) = 500 DEM, i.e the
original amount. - Time-dependent translation for the posting date using the bank buying rate. Example exchange rates for this:
0.6 DEM/USD for 1/5/1995
0.8 DEM/USD for 1/9/1995
0.8 DEM/USD for 2/7/1995.
During data transfer the posting date will be ignored as this is not contained in the transaction data table as a characteristic. (see above)
The records in the data transfer table will then appear as follows:
Fiscal year Period Sales area
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in |
