USD to Document currency conversion

I have a report that fetches all line item imbalances between a company and its trading partner in USD. I need to sum all imbalances and depending upon the selection criteria like imbalances over 10k/20k/30k, the respective line items need to be displayed in Document Currency. I am at the last step of getting all line items in USD and summing all imbalances between a company and its trading partner and now, the problem is how to get those line items in Document currency for whom the overall sum is over 10k/20k/30k USD?
How can I convert the USD to Doc currency at the final step?
Appreciate your answers,
Thanks!

Use this function module CONVERT_TO_LOCAL_CURRENCY
vat do u mean by document currency?
Regards
- Gopi

Similar Messages

USD to LC currency conversion!!!

Hello, I am familiar with LC to Reporting currencies conversion. but my client has a requirement of USD to LC currency conversion, can someone give me an idea on how to do that with lookup?
Thanks.

Thanks YHseo, I have created a code but I am new to this so have a few questions. please note that this is journal.lgf, and they are entering journals in USD only, Datasrc of miscadj and corpadj only.all the questions are commented out. Sorry I havent used your reverse idea, as I am new and want to keep it simple.
Thanks.
*XDIM_MEMBERSET RPTCURRENCY= USD
*XDIM_MEMBERSET DATASRC = miscadj, corpadj
//REST OF THE DIMENSIONS WILL BE WHATEVER USER INPUTS IN THE JOURNALu2026HOW DO WE DO THAT
*LOOKUP RATE
*DIM TIME=TIME
//IS THE TIME=TIME NEEDED?
*DIM VARIABLE1:INPUTCURRENCY=COMPANY.CURRENCY
*DIM VARIABLE2:RATE=ACCOUNT.RATETYPE
*DIM CATEGORY=CATEGORY
*DIM RATESRC="RATEINPUT"
*ENDLOOKUP
//GAVE US THE VALUE OF 48 AS EXCHANGE RATE - WHERE IS THIS STORED? I THINK %VALUE%, AM I CORRECT?
*WHEN ACCOUNT
*IS
//RUN FOR ALL RECORDS THAT WERE ENTERED IN JOURNAL, WILL THIS WHEN LOOP ACCOMPLISH THAT?
REC(EXPRESSION=%VALUE%LOOKUP, RPTCURRENCY=COMPANY.CURRENCY)
//WHERE WILL THE REST OF VALUES FOR THIS RECORD COME FROM?
*ENDWHEN
*COMMIT
Edited by: Zack Thacker on May 20, 2011 6:45 PM
Edited by: Zack Thacker on May 20, 2011 6:50 PM

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
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.
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

%GT 'Document Currency Amount' takes care of automatic currency exchange?

We created a formula KF of %GT 'Document Currency Amount'. Let's assume we've got two records: 1st record with US dollars, 2nd record with Canadian dollars, then the KF column would show the correct percentage number for the %GT 'Document Currency Amount'? or in other words, the currency exchange would be automatically taken care of by the %GT 'Document Currency Amount' when displaying the result?
Thanks!

I know this does not work with quantities (e.g., mix of LB and KG), so I assume it also does not work with currencies. If not, you will have to do the currency conversion on the Document Currency Amount first, then the %GT should be correct. To do this, I would suggest adding a new kf (e.g., "Document Currency Amount in USD") where the currency conversion is done on the Properties screen, then change your formula kf to %GT 'Document Currency Amount in USD'.
Hope this helps...
Bob

Sales document currency

Hi Guys,
I am facing this peculiar condition where even after maintaining the currency in the customer master as USD the document currency in the sales order is showing as INR.
Below is a detailed explanation of what exactly is happening.
I have maintained the currency in customer master as USD. Now when i create a sales order after entering the sold to party and the PO no. a pop up box appears which says "Exchange rate will be redetermined". Now when I go to header details there it shows as INR. Now if i refresh the currency then it displays USD with the conversion rate. If I come out of this screen and go to item details there it shows INR and when I come back to the header details again the currency is resetted to INR.
I got it checked with the FI consultant he says that the currency conversion customisation has no faults.
Please advise on this issue. Appreciate your help.
Thanks in advance.
Zak

To my knowledge, there are two options to check.
1) Check in OC41, whether you have assigned currency exchange rates and
2) Check in OB59 whether you have defined all tabs under Exchange Rate Determination
I am not sure whether this will help you but if it helps, dont forget to reward points.
Thanks
G. Lakshmipathi

Currency conversion issue in SPM. We are getting incorrect results with SPM conversion function from one of the document currency to USD.

Currently we are using SPM 2.0 version and we have been facing currency conversion issues.
Please help me in following aspects.
1) Where actually currency conversion happens in SPM. Is it the global program which does the conversion or other way.
2) We have conversion issue for one of the currency where conversion function is giving incorrect results when converting from one of the document currency to USD. here The respective document currency is considering the 1:1 ratio with Dollar which is actually incorrect.
3) We have verified in both BI side(currency tables) and even ECC side.
Please help me in understanding this issue and let me know if you need more information on this.
Its an production issue and appreciated your immediate inputs.
Thanks
Kiran

Hi Arun,
The following information may be helpful to you.The SSA_HELPER_PROGRAM has options regarding currency settings.
EXCH_RATE_TYPE: This flag governs the exchange rate type which will be used for currency conversion in data management. For example if RSXAADMIN contains an entry EXCH_RATE_TYPE = „ZSPM‟ then the conversion type used for currency conversion is ZSPM. The default value for the exchange rate type is „M‟. More details can be found in the note 1278988.
CURRENCYCONVERSION: By default data management converts all the measures in transaction currency to reporting currency and copies over to the corresponding measure in reporting currency. If the measure in reporting currency is already available in source it might be desirable to disable the currency conversion. To disable the conversion you can make an entry CURRENCYCONVERSION = „ „ in the table RSXAADMIN. This can also be achieved by running the program SSA_HELPER_PROGRAM with the option DEACTIVATE_CURRENCYCONVERSION. The conversion can be reactivated by running the same program with option ACTIVATE_CURRENCYCONVERSION.
UNITCONVERSION: Similar to above. To deactivate unit conversion you can use the program with option and DEACTIVATE_UNITCONVERSION and to reactivate ACTIVATE_UNITCONVERSION. By default both the conversions are switched on
EXTERNAL_CURRENCIES: Normally most of the international currencies are stored with two decimal places however certain currencies do have 0 and 1 decimal place too. For example JPY has 0 decimal places. SAP internal format stores even these currencies with 2 decimal places and at the time of display it changes the value to right decimal places. In case a file from external source is loaded to SPM it might have the format with 0 decimal places in the file. To convert it to SAP standard format post processing needs to be done on this value. If that is the case you can set the flat EXTERNAL_CURRENCIES = „X‟ in the table which will enable the post processing for these values. This flag can also be set and reset using the helper program using the option TURNON_EXT_CURRENCY_FORMAT and TURNOFF_EXT_CURRENCY_FORMAT.
Kind Regards,
John Harris
Senior Support Engineer, SAP Active Global Support

Document Currency to USD problem

In the Account Receivable cube we are using the Document Currency key figures and converting them to USD on a fixed date exchange rate. When checking the receivable balance at company code level, for one company code the result was *. On further analysis there was a message saying that there is no exchange rate available from USD to KWD. I do not understand this since we are converting from DC to USD and there is exchange rate available from KWD to USD. Then why is the message that no conversion available from USD to KWD. Of course on analysis I found out that one customer who has DC in EUR as well as in KWD. When I excluded this customer the balance value came all right without star. The other fact I noticed is that there are no conversion rates available from USD to any currencies and yet I did not receive any message for any other company codes whether multi document currencies are used. Since it appears to be only for KWD, is there any setting somewhere to be done so that it will not expect an exchange rate from USD to KWD and should be able to use the rate from KWD to USD.
Thanks for your help
Ram

I solved the problem like this. Through SPRO I made an entry into table TCUTF -USD to KWD from factor 1 to factor 1 valid from 01/01/1800. Then in table TCURR made an entry for 01/01/2001 from USD to KWD exchange rate 0.304999 for rate type M.
Once these entries were made my query runs all right and when converting KWD no more * comes. I am still curious why KWD is left out by SAP when I have entries for type M from USD to all other currencies valid for 01/01/2001. Appears only KWD is left out. Our BW release is Bw3.5
Ram

Benefits Service - Error occurred during currency conversion from to USD

I am attempting to run the add beneficiaries service in employee self servie and receive the following error message "Error occurred during currency conversion from blank to USD
Has anyone come across this error before?

Both are set up properly. This error only happens on some US teammate records. It seems to occur after we do a refresh of our QA environment from our produciton environment

Required Document on Currency conversion Types

Hi All,
Can any body provide me link or send Document on Currency conversion types
[email protected]
Regards,
C.V.
Message was edited by: P.C.V.

I sent to you an useful how to..
Regards,
Sergio

Currency conversion JPY to USD issue

Hi Friends ,
I am facing an issue while currency conversion from JPY to USD . I have defined currency conversion type in RSCUR , it is working fine for all other currencies except JPY . I have the exchange rate maintained in TCURR but still it shows exchange rate not maintained while running the query . Could you please tell what can be possible reasons for it .
Thanks in Advance .

Hi,
Check the time reference based on which the currency conversion rate is maintained. Run function module READ_EXCHANGE_RATE by giving the date, JPY to USD and check if returns values.

Currency Conversion Document

Hi Friends
I have been given a project to learn about SAP currency conversion. Can anybody please provide any documentation for Currency conversion from SIT to Euro and Old Turkish Lira(TRL) to New Turkish Lira (TRY).
Thanks
SAP FICO

Hi,
Hope the below links are useful:
http://www.sap.com/services/consulting/servicecategories/landscapeoptimization/currencyconversion.epx
http://www.behnmeyer.com/bm_articles.asp?show_article=14
Regards,
Hemanth

Currency Conversion on Piticular date

Dear All,
               I have a requirement where in I have to convert the Purchase Document Currency into USD on PO Creation Date.
I did the Currency Conversion in the BEX by creating a currency translation type using the tcode RSCUR. Following are the   settings I have Used for Conversion
1. Exchange rate type M
2 target currency         USD.
3 Time reference          Current Date.
Problem is the values are not getting converted to USD on PO Creation date.
Moreover I wanted the records whose values are more than 50,000 USD.
Question.
How to convert the currency from one to another on a Particular date.
Date for each record is different from one another as stated above.
Help me out in this case.
Thank You All
Regards
Mahesh

Dear Raj,
Thank you for the reply.
Iam using BI 7 and the tcode rrc1 is obselete in this version.
So I went to the new tcode rscur and created the currency translation type with the settings below.
1. Exchange rate type M
2 Target currency USD.
3 Time reference Current Date.
Used this translation key in the Key figure properties for currency translation.
I went to the source system and on context menu I transferred global settings.
Do I need to maintain currency keys and exchange rates manually even after transferring global settings?
I have set in the time reference the PO creation date
as Special Info Object. Will this work?
Please let me know.
Regards,
Mahesh

Document Currency vs Local Currency in Purchase Order document

Hi Guru
User have created PO with foreign currency in EUR (Local currency = USD) and release strategic is completed in this PO.
Then, buyer increased exchange rate and fix the exchange rate at PO header. The PO net value in EUR still remain the same, system still trigger release strategic reset and manager need to re-approve and set release strategic as completed.
Can you tell me how to check this setting in SPRO? Is it a natural behavoir in SAP system? User asked if this option could be disabled as increase exchange rate but then the whole PO total net value still remain the same in foreign currency. Why should release strategic reset?
Please advise

Closing this Thread as I found the answer
Within the Purchase Order, when the new TOTAL NET ORDER VALUE is higher than the old one, release strategy will be triggered once release charateristic is set for checking rule
System will check through The total net order value which is linked to CEKKO-GNETW for a purchase order.
In purchase order, the currency conversion will act as below:
Purchasing documents: Header currency converted to company code currency.
Company currency converted to characteristic currency
Hence, eventhough the exchange rate is increased but document currency is remained unchanged, the company code currency is increased and hence trigger release strategy.
for more information, please refer to http://wiki.sdn.sap.com/wiki/display/ERPSCM/RELEASE+PROCEDURE

CONVERT_TO_LOCAL_CURRENCY currency conversion errors in Delta mode

Hello,
I have been working with SAP via customer messages for a month now with no resolution. As many of you have experienced, the SAP Level 1 support is pretty useless so I would like to check here to see if I can get some help.
I found a thread where another user has had the exact same problem as I have.
Problem: Exchange rate in Update rules with DELTA mode
However, there was no answer given to him. So, if anyone can help, I appreciate it. Here's the problem:
When a record comes through 2LIS_13_VDITM (for example), it had a document currency of EUR, a local currency of PLN and a statistical currency of USD. The first time the record comes through, it comes through just fine. The exchange rate from EUR to PLN is 3.533. The statistical currency value is calculated by taking the document currency value and multiplying it by the exchange rate from EUR to PLN to get the local currency. Then, this local currency is converted to USD by multiplying itself by the PLN to USD exchange rate of 1.519.
These are the exchange rates that are coming through as key figures on the transaction data. The problem is when a delta occurs. The data goes into the ODS and then once the update rules to the cube get it, the signs are backwards on the exchange rates. This makes sense so that the exchange rate key figures will cancel themselves out, but the SAP code says to calculate the local currency, it must first take the document currency and divide by the exchange rate. It should still be multiplying because the exchange rate from EUR to PLN is still 3.533. The negative on the key figure that is being zeroed out tells the code to divide though.
You cannot simply set the reversal indicator because the values that do come through ok would then be erraneous as the previous poster who had the same issue encountered. This is really causing some bad data for us. This is SAP delivered code. Any help would be appreciated.
Thanks,
Brent

hi,
chk out various application currency conversion links
Need Urgent Help on Currency Conversion Routine
Currency conversion using transformation rule
http://help.sap.com/saphelp_nw04/helpdata/en/bc/058f4073b2f30ee10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/16/088f4073b2f30ee10000000a155106/frameset.htm
Ramesh

Alternate Exchange Rate Type Not Picked while converting from Document Currency to Group Currency

Hello Gurus,
We have setup an alternate Exchange Rate type MNB for rate M for the postings happening in Hungary. Local currency is HUF. Group currency is USD.
If the document currency is, lets say, EUR, latest MNB rate is correctly picked up (EUR to HUF) and postings are correctly converted into local currency (HUF).
Although, for the same document, when a group currency is being calculated (EUR to USD), exchange rate type M is being picked up. Same happens if document currency is HUF. Even then, the conversion is based on exchange rate type M.
Is this a normal SAP behavior? How to prevent/correct this? This is also throwing off balances when we check in FAGLB03 or BSEG values in local and group currencies. In OB22, we have local currency1 and local currency 2 setup with exchange rate type M and we may not want to make any changes there as it is setup at global level.
Do we need to run any valuations after the fact? if so, how?
Thank you for your inputs in advance.
Regards,
Sagar

Hi,
You mentioned that "in OB22, we have local currency1 and local currency 2 setup with exchange rate type M". Then, I'm wondering how MNB is picked up for the first local curr. conversion to HUF? It should be 'M' instead. There must be some settings in your instance for such behavior. Can you check that?
Actually, Group Curr. conversion happens with the rate defined for 2nd Loc.Curr.in OB22 which is 'M' in your case. Therefore, all the transactions are converted with M instead of MNB.
Since you can't change OB22 per global co.policy, the exch.rate defined in OBA7 will overrule OB22. However, you've to make sure it's set up for all doc.types which are affected and posted in different curr. than HUF.
As a workaround, another thought would be to maintain the same conversion rate for both exch.rate types MNB & M, for eg. HUF > USD rate is the same both exch.rate type MNB & M. This way, you ensure all transactions are posted with correct exch.rate irrespective of whatever rate type is used.
From business, & global org. perspective, I'm sure they are sending the 'M' exch.rates to all their sister concerns monthly, so they would like to consolidate results as per standard rate in their system. Then, why ,as a local company, would you like to fiddle with standard process? It's a management decision, please run them through again before going ahead.
Thanks,
Nirav

USD to Document currency conversion

Similar Messages

Maybe you are looking for