Currency Conversion - difference in behaviour of NW compared to Microsoft

Hi Everyone,
When migrating from BPC Microsoft 7.0 to Netweaver 7.5NW SP01 we setup the same reporting currency conversion as we had before. A simple conversion of reporting currency from LC into EUR and USD.
We noticed:
- the currency conversion of accounts that had no RATETYPE used to convert at a factor of 1. In NW the system ignores these accounts and does not convert them...USD and EUR are blank
SAP help states this should be possible...
[http://help.sap.com/saphelp_bpc75_nw/helpdata/en/7b/4479fd9b394314a257d92d9be6a71f/content.htm]
- EUR and USD in Microsoft version are considered calculated members and do not allow direct entry into them in the input schedules (the CALC property is Y). In NW version, we can enter directly numbers in these reporting currencies, which makes it confusing for users and may lead to errors
Did anyone experience any of these behaviours?
thanks for sharing,
best regards,
Luis

Hi Luis,
This is off the top of my head, but my experience matches yours. I think you will have to add a new rate type to all your accounts that you want to convert with the multiplier of 1, and set up a business rule with
[COPYLC]
in the formula. Maybe I'm missing something, but it looks to me like the documentation is simply incorrect on this point in the Netweaver version.
As far as EUR and USD, are you using the STORED_CALC property in your MS system? In my brief tests of this functionality I've never been able to get this property to have the desired effect (setting CALC=Y for a base member) in the NW version. You may want to open a message for the issue if this is what you were using on the MS side and it's not working for you. It would be nice to have it working.
Ethan

Similar Messages

Asset adjustment bcoz of currency conversion differences

Hi Good morning,
Have situation in Asset management, while we purchasing assets on month end and some other time, small amounts (3$, or 5$) are capitalizing to the assets account becoz of currency conversions differences rather than gain or loss currency differences account, coming soon we have to avoid this with config changes.
I'm wondering how to reverse or deduct those small amounts from assets to gain or loss exchange account and what configuration has to be carried to avoid permanent.
Could any body help on this to over come..
Thanks in advance and points are available.

Hi Good morning,
Have situation in Asset management, while we purchasing assets on month end and some other time, small amounts (3$, or 5$) are capitalizing to the assets account becoz of currency conversions differences rather than gain or loss currency differences account, coming soon we have to avoid this with config changes.
I'm wondering how to reverse or deduct those small amounts from assets to gain or loss exchange account and what configuration has to be carried to avoid permanent.
Could any body help on this to over come..
Thanks in advance and points are available.

Currency Conversions showing different behaviour

Hi,
I have a strange problem with the currency conversions. I have configured business rules for one application for currency conversions and everything works fine.
For another application, I have written a script logic. This works well for all AST and EXP Account types.
For INC account types :
1. When the logic is included in the default logic, it works fine.
2. When the logic is not included in the default logic, and the currency conversion Data manager package is executed or the logic is executed through UJKT, the calculations are done perfectly but the amounts are negated.
Did anyone see this kind of strange behaviour. I have the currency conversions code as follows:
// *RUN_PROGRAM CURR_CONVERSION
     // CATEGORY     = %C_CATEGORY_SET%
     // GROUP = %GROUPS_SET%
     // TID_RA = %TIME_SET%
     // RATEENTITY = GLOBAL
     // OTHER = [ENTITY=%ENTITY_SET%]//For More than one other scope parameters: OTHER = [ENTITY=%ENTITY_SET%;INTCO=%INTCO_SET%...]
// *ENDRUN_PROGRAM
*SELECT(%REPORTING_CURRENCIES%, "[ID]", "RPTCURRENCY", "[REPORTING] = 'Y'")
*LOOKUP RATE
   *DIM R_ENTITY="GLOBAL"
   *DIM R_ACCT=ACCOUNT_LOE.RATETYPE
   *DIM SOURCECURR:INPUTCURRENCY=FIELD.CURRENCY
   *FOR %CURR%=%REPORTING_CURRENCIES%
   *DIM %CURR%:INPUTCURRENCY="%CURR%"
   *NEXT
*ENDLOOKUP
*WHEN RPTCURRENCY
*IS "LC"
*WHEN ACCOUNT_LOE.RATETYPE
*IS <> ""
    *FOR %CURR%=%REPORTING_CURRENCIES%
         *REC(FACTOR=LOOKUP(SOURCECURR),RPTCURRENCY=%CURR%)
     *NEXT
*ELSE
// take as is
   *FOR %CURR%=%REPORTING_CURRENCIES%
         *REC(RPTCURRENCY="%CURR%")
   *NEXT
*ENDWHEN
*ENDWHEN
*COMMIT
But I don't think there is anything wrong with the code, because it works absolutely fine with the default logic.
Thanks
Vidya

CSS could be getting obfuscated. Set the following in web.xml.
<context-param>
<description>No obfuscation of CSS.</description>
<param-name>org.apache.myfaces.trinidad.DISABLE_CONTENT_COMPRESSION</param-name>
<param-value>true</param-value>*
</context-param>
Also refer
https://technology.amis.nl/2009/07/01/using-adf-faces-11g-skinning-for-setting-the-styles-of-specific-component-instance…

Currency conversion - CO differences

Hi Guys,
We are doing technical currency conversion at data base tableu2019s level from SGD to USD for our company code (EURO solution). During this conversion, FI reconciliation is able to achieve. On the other hand where CO data also changed balances form SGD to USD on fixed rate (exchange rate) conversion base, it will lead some small rounding differences either +/-. Is there any way to adjust these small differences in CO module alone with out impacting to other modules (Running EURO CO reconciliation programs i have idea apart from this any solution Plz)!
Thanks for your valuable inputs.
Vyas
Edited by: vyas on Mar 3, 2009 10:18 AM

Thanks Guys.
We decided to use conversion cost center and element or internal order to write off the differences during currency conversion occured. Once go-live went will block for postings and for reporting management need to omit this.
Thanks...Vyas

(Strange) Currency Conversion on YTD Application

Hi experts
I found a wrong currency conversion on YTD Application and my customer also has the same problem.
Here is the example:
Rate Application
2008.JAN 1 EUR = 1.2 USD
2008.FEB 1 EUR = 1.2 USD
2008.MAR 1 EUR = 1.4 USD
Finance Application (a YTD application)
CV Time: YTD
2008.JAN 10 EUR
2008.FEB 20 EUR
2008.MAR 30 EUR
CV Time: Periodic
2008.JAN 10 EUR
2008.FEB 10 EUR
2008.MAR 10 EUR
For the correct currency conversion (to USD), I should get
2008.JAN 12 USD (10x1.2)
2008.FEB 12 USD (10x1.2)
2008.MAR 14 USD (10x1.4)
2008.Q1 38 USD
But the result is
2008.JAN 12 USD (10x1.2)
2008.FEB 12 USD (10x1.2)
2008.MAR <wrong> USD (10x???)
Is it a bug or my wrong configuration ?
ps. you can try it
Regards,
Halomoan
Edited by: Halomoan Zhou on Jun 20, 2008 8:54 AM

What you see is normal behaviour:
when you do a ytd currency conversion, the YTD LC amount will be translated against the entered rates.
If you then look to periodic data, the ytd previous period amount will be deducted from the ytd current perid amount by OLAP.
This then means that you cannot calculate the periodic LC amounts against the entered rates.
If this wasn't the case, the calculation below will not work on converted numbers:
YTD februari + periodic march = YTD march
I think that the calculation above must always work. BUT I know of one customer that didn't wanted this behaviour, they wanted that the periodic values AND the ytd values calculated against the same entered rate. There are several ways to achieve this; we added a member in the subtables dimensions to store the difference and then adjusted the measures calculation so that this difference was picked up by OLAP when selecting the periodic measure.
AGAIN: I didn't like this because the calculation of "YTD februari + periodic march = YTD march" is in my opinion a holy one.... But the customer is always right
Hope this helps,
Alwin

Currency translation differences with an effect on earnings

Product Version: SAP R/3 46.C
Componente: EC-CS-CSF-E Currency Translation
In currency translation program of ECCS (tx CX40) the prior year portion of translation differences that affects earnings is posted in current period in the earnings retain item (ER) which according to SAP documentation "Currency translation differences with subsequent consolidations" is correct, however when we run the currency translation on subsequents periods this amount is posted again generating a multiplying of differences on each period.
In accordance with section u201CBu201D of SAP note 553586, the carryforward item (retain earnings) was assigned to translation key 5, to avoid multiplications of this difference in every execution of currency translation for current period. This correction was applied successfully, however the problem is now generated when we run the currency translation in every subsequent period.
SAP notes 582815 and 553586 was applied succesfully.
We also verified SAP note 1045402 changing the translation key 5 to 1, for balance carryforward item (retained earnings) this avoids the difference effect on subsequents periods, but generates a translation differential effect undesired on this item, since this is a historical item that not must be altered by currency translation.
Additionally we read SAP note 509509 and we think that this issue corresponds whit symptom 2 of that note.
Step by Step:
Transaction: CX40
Setting of Translation SET in translation method:
1.- MARS-GAP-Monetary:
1.1.- Items of balance sheet
1.2.- Translation Key 1
1.3.- Item for differences: income statement item with an effect on earnings
2.- MARS-GAP-NonMonetary
2.1.- Items of balance sheet
2.2.- Translation Key 6
2.3.- Item for differences: income statement item with an effect on earnings
3.-MARS-MOR-Monetary
3.1.- Items of P&L
3.2.- Translation Key 5
3.3.- Item for differences: income statement item without an effect on earnings
4.-MARS-MOR-NonMonetary
4.1.- Items of P&L
4.2.- Translation Key 6
4.3.- Item for differences: income statement item without an effect on earnings
5.- MARS-HIST
5.1.- Items of balance sheet
5.2.- Translation Key 6
5.3.- Item for differences: Balance sheet item without an effect on earnings
6.- ANI-BS-FX
6.1.- Items of differences SET MARS-HIST and Carryforward Item for special items in transaction CXD3, the same item for the balance carryforward (retained earnings)
6.2.- Translation Key 5
6.3.- Item for differences: Balance sheet item without an effect on earnings (the same item for the SET MARS-HIST)
7.- ANI-BS
7.1.- The special balance sheet item in Transaction CXD3
7.2.- Translation Key 5
7.3.- Item for differences, the same item
8.- ANI-IS
8.1.- The special income statement item in Transaction CXD3
8.2.- Translation Key 5
8.3.- Item for differences, The same item
Note:
1 .- According to the point A of the note 553586 was included the FS Item 484051011(difference item for SET MARS-HIST) in the conversion SET ANI-BS-FX
2 .- According to Section B of the note 553586 was included the account for carried forward 481000001 the special accounts set up in the transaction CXD3 in the conversion SET ANI-BS-FX
3 .- According to Section C of note 553586 are included special accounts set up in the transaction CXD3 390000 and 251200, in the conversion SET ANI-IS and ANI-BS respectively.
When run the currency translation in the new year 1-2011, the prior year portion of translation differences that affects earnings is posted in current period a credit to earnings retain and debit to account difference in SET for this account. This amount is same on special balance sheet item 251200, in tx CXD3, also found on the statistical FS item.
Then in subsequent periods, 2 - 2011 it posting another credit to earnings retain and debit to account difference in SET for this account, generating a multiplying of differences on each period, even though the difference for this account (ER) in the log of the translation currency is equal to the difference posted to the previous period, show this in transaction CX34 for items of translation (1) for this account until 1-2011.
Edited by: Ana Brito on Jul 25, 2010 8:10 PM

Hi,
just a information how I did a workaround about this:
The opening (movement type 100) of the balance sheet item "differences of currency translation" is customized with "don't change...".
Every increase to "differences of currency translation" works with e.g. movement type 120 and will be carried forward to 100.
Maybe this is a scenario you can use...
BR

Local Currency conversion in PO

Hi
Iam facing problem in wrong Local currency conversion while doing GR reversal for foriegn currency Subcontract PO.
Local Currency : EUR
PO Currency : HUF
User has entered wrong Exchange rate in OB08. (Indirect Quotation : HUF -> EUR) & did Goods Receipt with reference to PO. After that Exchange
rate has been corrected immediately, but some GR documents posted with wrong exchange rate.
To correct the wrong entries, Again Wrong exchange rate has been updated in OB08 & reversed those material document in MBST. But the strange issue is system calculating different local currency for those reversed documents. The Local currency Amount of Goods receipt document & reversed document local currency amount is not matching,Ideally both should match.
Following observations on this,
1. Exchange rate are same in both doucments. I have checked in document Header.
2. GR Qty & Reversed Qty are same.
3. PO currency (HUF) amount are same in both doucments.
4. Finished Material & Raw material are managed in standard Price.
5. Document date & Posting date are same in both doucments.
Anybody can explain why the system updates wrong local currency ?
Thanks in Advance.
Regards,
RRS

I do not remember the Tcode, however it is under SPRO>>General setitings>> currency .. guess it is OB90
And if the difference is large. check the following:
Check the exchange rate type you use, next go to OB08 and see if the inverse translation is maintained for your currencies EUR- HUF and HUF- EUR
and then check OB07 and see what settings you have for the ex. rate type you have i.e Inv, fixed ...
You might hit upon something here

Sorting Currency conversion Variables in Query Selection screen

Hi Experts,
I have an issue in sorting variables.
A Currency translation is used here which has two selection options here, one for "Currency" and one for "Currency conversion date". They just pop in somewhere in the selection screen with out order. I want to put them together either in the middle or at the bottom.
They are not visible in the Variable sequence tab of query properties.
I changed the text for each of them (Ex. "XCurrency"), so that it sorts alphabetically, but no difference.
Had anybody come accross this issue before.
regards
G Rai

Hi,
This seems strange that the variable does not show in the query properties. One thing I can suggest it to try changing the technical name/desciption of the variable if that changes the order.
Please update back the thread if that helps.

Currency Conversion issue for YTD model

Hello,
Currently our Client is using YTD (year to date) model to maintain data into BPC 7.5NW, and planning to use BPC for currency conversion from LC to USD. They are not converting the values in Transactional system. When performing this all Balance sheet accounts will be using YTD model for conversion, but income statement accounts should be using Periodic values for conversion.
We have two different Entity FX types: one is USDFNC - USD functional and NUSDFNC - Non USD functional. One of the differences between these two FX types is CTA account, USDFNC is using expense Account to Book CTA and NUSDFNC is using Equity Account to book CTA.
To achieve the above mentioned requirement, I did configure BPC as follows:
1) Use RATE type AVG (average for Income statement accounts)
2) Use RATE type END (spot rate for Balance sheet Accounts)
3) In business rules for Account rate type AVG- formula would be [AVG], apply to periodic flag will be checked.
5) in business rules for Account Rate Type END - Formula would be [END], apply to periodic flag will be blank.
6) To calculate CTA for ENTITY FX type- NUSDFNC, I configured the following in Account Rate type AVG - destination account is equity account, Formula is [END]-[AVG], apply to periodic flag will be blank and Entity FX type is NUSDFNC.
7) To calculate CTA for ENTITY FX type- USDFNC, I configured the following in Account Rate type AVG - destination account is expense account, Formula is [END]-[AVG], apply to periodic flag will be blank and Entity FX type is USDFNC.
Above configuration is giving me correct converted result for all Balance sheet accounts and income statement accounts are showing the correct values when I use the formula (current period LC amount-previous period LC amount)*(current period AVG rate). But I saw difference in Balance sheet, so further analyzed CTA (currency Translation Accounts) and found that the difference is because of CTA amount only. Similar CTA differences exist for both USDFNC entities and NUSDFNC entities. So, I think my logic to calculate CTA is not working.
I am using the standard script logic to run Currency Conversion:
*RUN_PROGRAM CURR_CONVERSION
     CATEGORY = %CATEGORY_SET%
     TID_RA = %TIME_SET%
     CURRENCY = %RPTCURRENCY_SET%
     RATEENTITY = GLOBAL
*ENDRUN_PROGRAM
*COMMIT
Can any one help me to understand whether this configuration is correct? I feel that I may need to change the logic for calculating CTA. But not sure about what and where
Edited by: amarnathputta on Nov 24, 2011 5:36 AM

Thank you Ethan,
Let me try to explain this with few dollar amounts:
Let us consider that I have data for 1st month (Jan) of the year 2011,
Net income for Jan. 2011 in LC = 59916152.19
Net income for Jan. 2011 in USD calculated using Average rate is = $ 9,223,013.14
CTA for the same month is (net income in LC X spot rate) - net income in USD at average rate =((59916152.19)*(0.154617))-9223013.14 = 41,042.564
This value is correct.
For the month of Feb 2011:
Net income for Feb.2011in LC = 60415519.01
Net income for Feb.2011 in USD at average rate (with periodic flag on) = 9,300,112.38 ( I calculated this value manually and it is correct after conversion)
calculated CTA for the same month is (60415519.01*0.154083)-9300112.38 = 8,892.035.
But actually BPC calculated CTA is 18,547.56 (I felt that this may be because I am not using the Flag apply periodic value while calculating CTA and when I flagged that, BPC is giving me a very big difference in CTA)
My balance sheet is exactly off with the difference in CTA.
Hope this helps you to understand my problem.
Edited by: amarnathputta on Nov 25, 2011 2:43 PM

Currency conversion with query selection mask and InfoObject 0Curtype

Hi,
question to following scenario:
in the data source is an column with the currency type. This currency type column contains values like
10 = company code currency
20 = account area currency
So for each data set in the table is an assignment of currency types.
In the cube is an InfoObject called 0Curtype (for currency types 10,20,30 ...).
In the BEx Query should a filter or selection be possible before the whole data is displayed.
The user can select in which currency he wants to display the data. When he selects the 10 the whole data is displayed in different currencies which are available because its local currency (Euro, Dollar etc.). By selecting 20 the whole data is displayed in Euro.
Does anybody knows how to achieve that? Is there any function module availabe which is provided by SAP and it is available for use?
Thank you in advance!!!

Hi There:
You have two options available.
One you can define currency conversion variable in transaction RSCUR. Then use this currency conversion variable at query run time using a formula Key figure and go to Conversions tab and select this variable. Then at query run time the query will convert your key figure from source currency type to target currency type. But this can significantly impact your query run time because the query will calculate this at query run time.
The second option is to use a standard SAP function module CONVERT_TO_LOCAL_CURR in the back end and store this key figure in the back end during data load. This way the query will run faster for you. The difference is significant in my case.
Good luck.
Let me know if you need more information.
MP.

Currency Conversion for Exchange rate type "AS02"

Hi Experts,
I am gonna post the most challenging problem (regarding currency conversion) I ever faced in my 1 year of BW Carrier.Kindly provide a solution.
There are three types of currency to be used in the query for Key Figure 0NET_VALUE (so total 3 Key Figures to be created)
   1.Document currency (may be any currency)
   2.Local Currency (must be EURO)
   3.Global Currency (must be USD)
From Document currency to Local Currency(EURO) we are using Exchange rate Type "M" (in Conversion Type created in Trans RRC1) [There is no problem in this conversion]
Problem starts now--->
From Local Currency(EURO) to Global Currency(USD) we have to use Exchange rate type "AS02" (in conversion type to be created in RRC1)
but there is a Business requirement that currency rate should be as per the last day of the entered period;and this logic should work for the range of periods also.
Example :
we are executing query for the period 006/2006 (posting Period)
Last day of this period is 06/30/2006,
Currency rate would be as per 06/30/2006
And this currency rate should be same throughout the period 006/2006 in query
The example was for single period,but logic must be incorporated for the range of the periods.

Hi..
There is no corresponding source key figure in the InfoSource for the target key figureof the InfoCube.
a. A source key figure of the same type can be assigned to the target key figure
(for example, sales revenue instead of sales quantity revenue).
If the currencies of both of the key figures are the same, no currency
translation can take place.
If the currencies are different, a translation can take place either using a
currency translation type or by simply assigning a currency.
The following table provides an overview of possible combinations with different
currencies in the source and target key figures:
if Source key figure currency is fixed , Target key figure currency is variable then Currency translation (CT) No CT
if Source key figure currency is fixed , Target key figure currency is fixed then Currency translation (CT)   CT
if Source key figure currency is variable , Target key figure currency is fixed then Currency translation (CT)   CT
if Source key figure currency is variable , Target key figure currency is variable then Currency translation (CT) CT or assignment
b. If there is no corresponding source key figure of the same type, then you have
to fill the key figure for the data target from a routine.
If the target key figure has a fixed currency, no currency translation is
carried out. This means that if translation is required, you have to execute
it in the routine.
If the target key figure has a variable currency, you also have to assign
a variable source currency to the routine. Using the F4 help you can
select a currency from the variable currencies in the communication
structure. You have two options:
You can select a variable currency and assign it.
You select a currency translation type and a currency into which you
wish to translate (To currency).
The To currency is, by default, the target currency if it is included in the
communication structure.
Creating a Routine for Currency Translation:
If you want to translate currencies in the update even though the currency translation is not
available for one of the above reasons, you can create a routine. Choose Routine, set the
Unit Calculation in the Routine and choose Create Routine. In the routine editor you get
the additional return parameter UNIT, the value of which is used to determine the target
1. save the query and it under role
   see to it is in   : Restricted and calculated key figures --->   properties of k.f
2. exeute the query
3. the currency translation --> by target currency usd choose OK
conversion type : MEANTODAY Fixed target currency current date (MT)
4. Go back to the query definition by chossing chage query ( global definiton)
5. in the context menu for % share sales vouume of incoming orders, choose properties --> formula collision --> result form this formula choose OK
Note that -
your should alos set the currency translation in the properties for the two key figures sales voule EUR , choose properties ---> currency conversion key : fixed target currency , currrent date ( MT) --> target currency : American Dollar . choose   OK
<b>The translation key is a combination of different parameters that establish how the exchange rate for the translation is executed.
The parameters that determine the exchange rate are the source and the target currency, the exchange rate type and the time reference for the translation.</b>
The source currency is determined from the data record or dynamically from the master data of the specified InfoObject (currency attribute)
The target currency can either be fixed in the translation key or selected at the time of translation.
You can also use an InfoObject (currency attribute) to determine the target currency.
The exchange rate type distinguishes exchange rates that are valid in the same time frame next to each other, for example, the bid rate, ask rate or middle rate. The exchange rate types are stored and can be maintained in a central table (TCURV).
The time reference for the currency translation can be either fixed or variable
The fixed time reference can either be a fixed key date that is stored in the translation type, or be determined using the system date when executing the currency translation.
If the time reference is variable, then the point in time for the exchange rate determination comes from the value of a time characteristic (InfoObject). The reference can, for example, be the end or the start of a fiscal year or a calendar year, a period and a month or even to the exact day. It can also be determined using a customer-specific InfoObject (for example, trading day).
Currency translation in the BEx
When selecting a translation key with a fixed target currency     this currency will be added automatically to the query definition
Also, you can use translation keys selecting their target currency at the time of translation. These can be applied in two different ways:
Selection of a specific target currency in the query definition (1)
Entry by variable (2)
Dynamic translation keys require input from the InfoCube !
InfoObject value will be read during query execution
Examples:
dynamic time reference (p.eg. 0CALDAY)
      time characteristic
target currency determined by InfoObject (currency attribute)
     characteristic which contains currency in its attribute table
the corresponding InfoObject has to be part of the InfoCube
1.Define the currency attribute in the InfoObject maintenance
The currency attribute has to be a unit InfoObject of type currency
The unit InfoObject must be an attribute of the characteristic
The currency attribute should be filled in the master data table of the corresponding InfoObject (manual maintenance or upload via InfoSource)
2.Enter the InfoObject in the translation key maintenance
Only InfoObjects with a currency attribute can be used in translation keys (p.eg. 0COMP_CODE)
At the time of currency translation the value for the source currency / target currency is then derived for every record from the master data table of the specified InfoObject
All values for a query are translated ad hoc (after having executed the query) using a translation key
Depending on the translation key a fixed target currency will be used for translation or you will be able to select the target currency
The ad hoc currency translation offers only restricted functionality (selection of translation key and target currency) compared to the currency translation in the query definition
Do not forget to create your translation keys before starting your work in the Business Explorer Analyzer
Example:
You load the following record to your InfoCube:
Company Code:                1000
Amount in Source Currency:      500,-
Source Currency:                FRF
Target Currency:               ?
In the Update rules, you are now using a translation key which derives the target currency from the InfoObject 0COMP_CODE. During the Update Process the target currency will then be read for Company Code 1000 from the master date table of 0COMP_CODE.
With the currency translation in the Business Explorer, the source currency can currently only be determined from the data record.
Only translation keys with a fixed exchange rate type can be used in the BEx
Translation keys with a dynamic time reference (from an InfoObject) can only be used in the query definition. It is not possible to fill the InfoObject by a variable !
Translation keys getting their target currency from a currency attribute can only be selected in the query definition
When getting the dynamic reference from an InfoObject (p.eg. 0CALDAY) the currency translation will apply to each record read from the database. That means it will use the date in this record for the currency translation.
When using a variable you will restrict the output of your query to a certain amount of data. For example, you would translate all invoices of March 11 with the translation date March 11
This means, the requirement show me all invoices in my cube in group currency, conversion date: 14.07.2001 could not be solved by a variable input for 0CALDAY
I hope this would help...
with regards,
hari

Inputs on Currency Conversion

Hi Experts,
I need some help in the Currency conversion variable that I am using in my report.
I have few caluculated key figures that are caluculated on the basis of difference between current date and the Net Due date. Currency conversion is used in these variables.
I also have few Restricted keyfigures that are restricted on the Fiscal Period. Same currency conversion variables are used in these key figures also. The currency conversion variable is at a Fiscal period level.
However, the currency conversion is not happening on the Caluculated keyfigures but it works for Restricted keyfigures.
Please provide your valuable inputs.
Thanks in advance.

Hello,
Please give us some more information on the calculated key figure. How is it defined? I assume the calculations is based on amounts and not on dates as you've written?
Best regards,
Christoffer Owe

Currency Conversion Error from KRW to EUR in for March 2011

Hi,
We are facing problem in Currency conversion from KRW to EUR in BW Production.
The report shows proper value for JAN, FEB 2011, but when we execute the report for March2011 it shows wrong value.
Month               |   BW Production Value    |           BW TEST Value
Jan2011 u2013        |   102,459                         |              102,459
Feb2011 u2013        |   120,008                         |              120,008
March2011 u2013    |   12,056,385                    |              120,564
As we can see the value for BW Production for the month of March is 2 decimals higher than the value in BW test.
Regards,
Nix
Edited by: nix_mania on Apr 18, 2011 4:20 PM

Hi,
My problem here is that the values for JAN and FEB are correct with their decimal values but only for March it is 2 decimals higher.
Hence the TCURX table wonu2019t come into picture, since if TCURX entry was incorrect then it should show wrong values for JAN and FEB also.
When I checked the data in cubes for BW Test and Production the values for March are same still in the report I am getting the difference.
Report Output:-
March2011:-
BW Test                    12,056,385
BW Production          120,564
Feb 2011:-
BW Test                    120,008
BW Production          120,008
Jan2011:-
BW Test                    102,459
BW Production          102,459
Regards,
Nix

Currency Conversion happend Record wise or on Aggregated Level

Hi ,
Suppose we've currency converison applied on 0CALMONTH.
And suppose we've 5 records for a CALMONTH december. In the Report, we do not ahve Document No as part of rows, so in that case data for a CALMONTH will be aggregated.
So, in that case, whether the Currency Conversion happens on each record and then does the aggregation OR it will first do the aggregation for teh CALMONTH and then does the CURRENCY CONVERSION ?
Thanks & regards,
Jomy

Hi,
You may try to put 0CALMONTH in rows and KFs of Amount in original currency as well as Converted amount into Columns.
First observe Total of converted amount by expanding to 0CALMONTH in rows then remove the characteristics 0CALMONTH from rows and then see Total of converted amount.
If there is no difference it means that our understanding for currency conversion is correct.
Hope that helps.
Regards
Mr Kapadia

Currence conversion

What is the difference between Currency conversion before & after multiplication.
Venkat

Hai
SM30, V_TCURR
maintain an entry for currency exchange type for M, for the relevant currencies... for the date..
Edited by: Ram Manohar on Apr 1, 2008 12:25 PM

Currency Conversion - difference in behaviour of NW compared to Microsoft

Similar Messages

Maybe you are looking for