Currency Translation Issue

I want certain accounts to be transferred as per historic rate. Historic rates are the inputs for each account which I have captured at the given combination.
mbrAcc is a account variable.
Reporting_Curr variable captures parent currency.
Parent_Curr = Hs.Parent.DefCurrency(pov_Ent)
Reporting_Curr = "RC_" & Parent_Curr
Hist_Rate = HS.GetCell("A#"&mbrAcc &".I#[ICP TOP].C1#" &Reporting_Curr &".C2#DefaultDataEntry.C3#HistoricRateCapture.C4#TOTC4.V#<Entity Curr Total>")
But in the rule this does not capture a rate for that parent currency. If currency is hardcoded (e.g. 'USD' instead of variable) then the rule works fine.
Can anyone help me on this as I dont want to hardcode the value?

Hi. On #1, try force translating these entities on their own. If that works, then I would call support about the all entities process not working. On #2, most people don't bother clearing the data after translating - just update it as needed. If you really want to clear it, you'll need an if/then in your calculate subroutine that runs the clear when at the reporting currency.
Eric

Similar Messages

Currency translation issue on SP08 when I use Force close option

Hi,
I am using three RATETYPES (AVG,END, HIST) in account dimension,
Income and expenes accounts   - AVG
BS accounts (except equity accounts) - END
Equity account - HIST
Business Rule Configuration
1) For AVG:
AVG Rate ( In Formula)
2) For END
Source FLow               DesitinationFlow    DestinationAcct             Formula
F00 (OpenBal)                                                                                OPEEND
F00 (OpenBal )                  F80( CTA)                                             [END]-[OPEEND]
F15 (periodic activity)                                                                     [AVG]
F15 (periodic activity)        F80 (CTA)                                            [END]-[AVG]
F99 (Closing Balance)                                                                    [END]
3) FOR HIST
Source FLow               DesitinationFlow    DestinationAcct             Formula                             Forceclose
F00 (OpenBal)                                                                                AS_IS                               True
F00 (OpenBal )                  F80( CTA)                                             [END]-[OPEEND]                     True
F15 (periodic activity)                                                                     [AVG]                                     True
F15 (periodic activity)        F80 (CTA)                                            [END]-[AVG]                            True
And in my master data in the Flow dimension for member F99 (closing balance )for property FLOW_TYPE is equal to "CLOSING" and F00 (Opening balance) is "OPENING"
Scenario:
1) Loaded LC YTD Trial balance for 2011.NOV
2) Run Fx Translations (it worked well as expected)
3) Run Carry forward to 2011.DEC with LC and USD
4) Loaded LC YTD Trial Balance for 2011.NOV
5) Run Validation report with local currency (my balance sheet looks good for openingbalance, current period activities and closing balance)
6) Run Validation report in USD for Opening balance, Still it balances for opening balance as its carry forwarded from previous period.
7) Run Fx translation package for DEC.2011
8) after FX translation my balance sheet is out of balance.
Error:
My Balancesheet is out of balance after running Currency translations when we have opening balances. it is out of balance with the amount for the same for the opening balance. I mean before running currency translation for opening balance total for balancesheet items is zero but after running currency translations the opening balance is out of balance and CLosing balance sheet is also out with same dollar number.
I am assuming the force close option is not working correctly. When we are on SP05 I remember it was working without any issue.
I appreciate if any comments on this issue.
Thanks,
Sri

Hi. On #1, try force translating these entities on their own. If that works, then I would call support about the all entities process not working. On #2, most people don't bother clearing the data after translating - just update it as needed. If you really want to clear it, you'll need an if/then in your calculate subroutine that runs the clear when at the reporting currency.
Eric

FI-SL Currency Translation issue , Tcode - GWUL

HI
When I use the T-Code GWUL to run the currency translation something is happening in November with some of the equity accounts. I will use our Japan company code as an example. In period 1 through 5 of FY14 when I run the translation the Common stock account stays static (and it should as it is associated with a historic rate). It is associated with ER IND 5 which has an exchange rate for 100 JPY = .92518 to 1 USD.
The Yen value for this account is 4,039,919 which translates to $37,376.52. However, when I ran the report for Period 6 ( and there was no change/activity in the Common stock account) it is reflecting a translation difference of $37,376.42 yet it is still showing the rate in the system as .92518. We are also seeing something similar happen in other equity accounts.
Period 5
Period 6

HI
Thanks for reply
I mean on translation difference column .
GWUL is ran for updating special purpose ledger
We need to specify ledger to be translated before executiong tcode GWUL
So GWUL will translate ledger on basis of ex rate type configured for its special purpose ledger
In above screen shot CH is ledger and Ex rate indicator are ex rate types which are different for different set of GL accounts defined .

FX Trans currency Translation issue..

Hi Friends,
In my Sales Application i have the following Dimension.
Accnt
Category
ENtity
Time
Data Src
HMaterial
RPTCurrency.
Now we i am executing the FX Trans.lgf through Logic debugger by filerting all the value of above dimenison, and also given a single material, it is executing and showing correct result.
But Now we i am executing the FX Trans.lgf through Logic debugger by filerting all the value of above dimenison, EXCEPT HMATERIAL DIMENSION VALUE, it is showing that
__*The logic cannot be processed because the SQL Query being generated is too complex or long . Try Modifying XDIM_MAXMEMBERS._
Can you please throw a light how to rectify the same.
Thanks
Viv

Hi Nilanjan
In the logic debugger, when i am executing the package in simulatiom mode with checking a single material , i can the translated value. But when i am leaving the Material Dimension blank , or in other words take all the value , its saying No Record to Process.
After adding the *XDIM_MAMMEMBERS= 20 , i am not getting the messgae any more , but the currency translated value are not coming.
Looking forward to your mail.
Thanks
Viv

Currency translation key issue on web

Dear BI Colleauges,
I am facing a problem with respect to currency translation.Issue is that.When i execute the report on web(Please note variable exists for 0currency).I do right click and use the Global currency option.I am trying to convert EUR to USD.When i use the currency translation option,it successfully changes the value to USD.But the unit remains still in EUR.I am wondering does this Unit also changes or it remains same as its database currency.
As a prerequisite,I have defined currency translation type in RSCUR.Exchange rate as M with Dynamic Ex.rate determination.In currency tab,For source currency its 'Source currency from data record".For target currency its "Target currency selection with translation.In Time ref,its current date.I have not used this currency translation type in keyfigure ( In KF properties conversions tab).I do use this type in run time whn i execute the report.I did try option of creating variable also and using the same variable in report.But the result is same.
Please observe the report looks like this.First column material,second column is currency and third column is value.
It would be great if anybody can give your inputs on the same.
BR
Robby

Hi Ace,
Under rows which info objects are there in your query definition.
Thanks,
Vijay.

Currency Translation with a Calculate Key Figure

Hi,
Does anyone have experience with applying currency translation in BEX/Query Designer on a Calculated Key Figure?
I have a need for a calculated key figure to be converted to a target currency of USD (which is already defined via RRC1). I also need the Results Row to display the summation in USD.
Currently, my calculated key figure displays two currencies (MYR and USD) and an incorrect summation of both currencies.
Here is how I have defined my calculated key figure:
NODIM ( 'Consumption (STOs)' ) * NDIV0 ( 'Material Source Plant Cost' / NODIM ( 'Source Plant Price Unit' ) )
I am multiplying a quantity field by amount field and then dividing by a price per unit field. I have applied NODIM on the other fields so that the amount field will retain it's properties.
Running this query through transaction RSRT and clicking on the Generate Report button, I get the following message:
"<b>Currency translation cannot be carried out for element 20 (my calculated key figure). Element 20 neither contains a Basic key figure nor a variable with type Amount. For this reason, you cannot and do not need to perform a currency translation</b>."
From the above message, I must be setting my calculated key figure incorrectly.
Any ideas?
Thanks!
Hau

Hello Ajeet and N Ganesh,
Thank-you for your help. I verified that the dimensions of my key figure 'Material Source Plant Cost' was of type 0AMOUNT, so that was not the issue.
The issue was in the error message that was returned when I pressed the Generate Report button in RSRT. Essentially, currency conversions in BEX can only be performed on basic key figures or simple replacement path variables.
I can perform the currency translation on a SIMPLE calculated key figure that contains only the replacement path variable (where 'Material Source Plant Cost' is an attribute of my master data characteristic ZMAT_SRC). However, I found that I cannot perform the currency translation on COMPLEX calculated key figures, like in my example above.
To get around this currency translation issue and as suggested by the error message, I created a SIMPLE calculated key figure for replacement path variable 'Material Source Plant Cost' and performed the currency translation. The problem with this solution is that while I get my currency translation, I also get a calculated key figure that is aggregated, according to the query layout.
To get around the aggregation issue, I also created a dummy counter as a master data attribute (of ZMAT_SRC) to capture the aggregation. I assign a value of 1 to this dummy counter/master data attribute in the update rules to my ZMAT_SRC infoobject.
I then divide my new (aggregated) calculated key figure for 'Material Source Plant Cost' by the dummy counter (which is also aggregated). Essentially, I divided the aggregated replacement path variable by the scaling factor. The result is that I get a new calculated key figure that has been translated into the target currency and in the correct scaling factor. I can use the new calculated key figures in the above formula; regardless of the report is rolled-up.
Again, thanks for your help. It gave me the pieces to solve this puzzle.

Currency Translation not working with "Time Reference from Variable"

We have created several Currency Translations using RSCUR with a fixed "Key Date". All have been working fine until we got the request to allow a variable date for the exchange rate date. I have built a variable on 0DATE which I am putting a default date value into using user exit. This default date is the SAME date as the fixed "Key Date" which we have been using. Unfortunately when we use the "Time Reference from Variable" option and use this new variable, no currency conversion is taking place, instead it only shows the original currency values. I am 100% sure that my variable is getting a value and it is the same date we are using for the fixed "Key Date" value so both methods should be using the exact same exchange rates. The documentation that I can find states:
●      Time reference: The time reference for the currency translation can be either fixed or variable.
If the time reference is fixed, the time at which the exchange rate is determined is independent of the data. You have the following options:
○       You can establish that the time reference be determined upon translation.
○       You can select the current date.
○       You can specify a fixed date as the key date.
○       You can specify any variable that exists for InfoObject 0DATE.
○       You can establish that the query key date be used. This is determined in the query settings.
In my case I am only switching from option "You can specify a fixed date as the key date"=(Key Date) to "You can specify any variable that exists for InfoObject 0DATE"=(Time Reference from Variable).
What am I missing? Any help is appreciated.

I neglected to mention that we are calling this currency translation through a WAD button using the SET_CURRENCY_TRANSLATION command. I did do a test by applying the currency conversion within query key figure. This seems to work. So it appears the issue is with how the WAD is processing the variable, not the query. When I display the variable in a drop down item within the WAD it does have the default value that I have assigned in user exit.

Currency Translation feature in BEx reports

Hi colleagues,
As you know, when creating queries, you can right click a given key figure and from Currency Translation frame you can select a customized Currency Conversion Key so OLAP engine displays the "converted" value of such Key figure. Standard TCURR table is used for the conversion.
Also, RRC1 txn. code can be used to create Currency Translation Keys to be used in query designer as described before.
I have created a "currency translation key" (let's name it ZTAXILOC) in RRC1.
I have changed my query in the query designer to use this "customized Currency Conversion Key (ZTAXILOC)". My query uses an InfoSet as "infoprovider".
However, when executing query on BEx Analyzer, I receive error message "Cannot apply currency translation type ZTAXILOC in infocube ZTXA04LA3", where ZTXA04LA3 is the name of my infoset that feeds my query.
The Diagnosis is: "You tried to translate a query element with the currency translation type ZTAXILOC. The translation type ZTAXILOC, however, has VARIABLE TIME REFERENCE, relevant to "DH Document Date" characteristic, which is not available in ZTXA04LA3 infoprovider....".
The "DH Document Date" characteristic exists in the ZTXA04LA3 infoset, but technical name changes since for Infosets, BW system dynamically assigns a technical name for each element in the join and it differs from technical in source ODS.
My question is:
Can I use custom "currency translation keys" in query designer if my query uses an infoset as infoprovider? or is custom "currency translation key" just allowed in queries that use an ODS/InfoCube as infoprovider? or should I provide RRC1 with technical name for "DH Document Date" existing on ZTXA04LA3 infoset?
Please advise.
Thank you.
Mario Vallejo.

We are running into similar currrency conversion issues on an infoset. We have an existing currency conversion key created using RRC1. The existing currency key is set up as follows:
TO_USD Convert to USD (Billing)
Exchange Rate Type = Standard translation at average rate
Dynamic Exchange Rate Determination = Yes
Inverse Exchange Rate = No
Source Currency from Data Record = Yes
InfoObject for Determining the Source Currency = No
Selection of Target Currency with Translation = No
Fixed Target Currency = Yes = USD
InfoObject for Determining Target Currency = No
Fixed Time Reference = No
Variable Time Reference = Yes = To the Exact Day = Special InfoObject (0BILL_DATE)
Query Key Date = No
We convert sales amounts to USD using this conversion key on existing cubes. When trying to apply the same conversion key to the new infoset, we received the following error:
Diagnosis:You tried to translate a query element with the currency translation type TO_USD. The translation type TO_USD, however, has variable time reference or variable target currency relevant to characteristic Billing doc. date. Characteristic Billing doc. date is also not available in InfoProvider ZBILLCOST and it references either none or more than one characteristic () of the InfoProvider for Billing doc. date, or Billing doc. date is not a base characteristic.
We have tried to steps in the response to this thread and continue to receive the error.
In Step 1, the only thing that we think we can change is the info object text in the infoset, not the technical name, is this correct?
In Step 2 & Step 3, we have never used variables for currency conversion. We create the currency key using the RRC1 and select the info object for conversion. We did try creating a new currency key in RRC1 and tried to find the newly named (text) info-object for billing date on the infoset, but it wasn't listed as an option under special info-object. Do you have more information on how to create the variable in query designer and how it is used and how to assign to the currency translation?

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

EBS currency translation not "posting date"

Hello,
We implemented EBS ealier this year. The currency translation date on the FF_5 postings is taking the "document date" and not the "posting date" when determining which currency exchange rate to use. This is only an issue for a couple days at month end when the document date is in the current month, but the posting date is in the prior month.
What do we need to do to change the currency selection back to "posting date". I have never seen SAP use anything but posting date. I have tried reviewing all the configuration of doc type and other set up during EBS implementation and cannot see how we have triggered this date.
Any help appreciated.
Regards,
Morgan

I neglected to mention that we are calling this currency translation through a WAD button using the SET_CURRENCY_TRANSLATION command. I did do a test by applying the currency conversion within query key figure. This seems to work. So it appears the issue is with how the WAD is processing the variable, not the query. When I display the variable in a drop down item within the WAD it does have the default value that I have assigned in user exit.

Currency translation on Query level (YTD exchange rate)

Hi Experts,
I want to implment the currency translation logic in query as below. Please advise what I should do.
Case 1
Variable entry screen
Posting date (range): 01.09.2007 - 31.03.2008
Query result
Sales amount figures from 01.09.2007 - 31.12.2007 => use exchage rate at 31.12.2007
Sales amount figures from 01.01.2008 - 31.03.2008 => use exchage rate at 31.03.2008
Case 2
Variable entry screen
Posting date (range): 01.09.2006 - 30.06.2008
Query result
Sales amount figures from 01.01.2006 - 31.12.2006 => use exchage rate at 31.12.2006
Sales amount figures from 01.01.2007 - 31.12.2007 => use exchage rate at 31.12.2007
Sales amount figures from 01.01.2008 - 30.06.2008 => use exchage rate at 30.06.2008
In query, key figure sales amount will be shown in ONE column. Please give a hint how to implement this issue.
Thanks in advance.
Cheers,
Helen

Hi Helen,
I guess you are trying to user conversion based on data record. data record intunr dependent on variable entry.
So for the definition of currency translation, use time reference as end of calender year/quarter and info object as posting date.
This should work fine for the same key figure, based on posting date, as per the example provided by you.
Hope I am clear enough.
Naveen.A

Message no. 06211 Currency translation error in net price calculation

Hi,
When i am creating purchase order i am changing currency from INR to JPY for FOB condition type only, And system issuing error message Currency translation error in net price calculation. Document currency is INR.
When i am using USD i am not getting this error.
I have checked table OB08 and both conversion maintained INR to JPY AND JPY to INR valid from 01.01.2012
Any solution for this please.
Thanks in advance.

Hi, Check in T-code M/08 for your import prizing procedure,what have you maintained for subtotal for gross price condition (PBXX,PB00), Maintain over there as '9', also for JPY currency there is issue with decimal also, ratio maintained in 100:1 ratio.
Edited by: tej yadav on Jan 6, 2012 1:29 PM

Currency translation taking more time at first time in the report

Hi All,
Here is an issue regarding the currency translation in the report. when we click on the currency translation from the contaxt menu on the report, its taking more time for the first time to get the selection options. But it is fast from the second time onwards. It will be not user friendly if its takes more time for the first time. Is there any way to fast up the processing time for the first time when i go for the "currency translation" option at report level for the first time.
let me know why it takes more time for the first time when we go for this option at report level.
Thanks,
Jack

Once again from the top.
This is undoubtedly not a database issue.
I doubt you can fix it in the database.
You can, however, spend a lot of hours asking questions and poking around if you are a consultant paid by the hour.
But as long as you are looking for something to do here are some that won't fix the problem but may be worth a few minutes of your time.
WHERE 1 = 1Are you kidding? Drop this nonsense. The Oracle optimizer is not brain dead. If it were my database I would also drop the parallel hint like a bad habit.
/*+ parallel(rp1, 8) */Again the Oracle optimizer is not brain dead. Ask for parallel threads that don't exist and the database will just queue your SQL and let it sit there until sufficient resources become available.

Foreign Currency Translation at Year End - How SAP Works for P&L items?

Hi All,
I wanted to know "How SAP works on Foreign Currency Translation at year end" from Local Currency to Group Currency for P&L Items.
I know how SAP works for Balance sheet items but am really confused with when the translation was done for P&L Items.
Configuration:
We are on ECC 6.0 . Local Currency is CAD and we have 2nd Local Currency as "USD - Group Curr".
We have set up Valuation Method - 4
We have set up Valuation Area - 40
For Account Determination for Currency Translation, GL accounts (Loss, Gain and B/S Adj) were setup for the combination of Chart of Accounts, Val Area and Fin Stmt Ver.
Sales Account Balance
CAD (LC)        USD (2nd LC)
1000                   920
Using tcode "FAGL_FC_TRANS", we translated our P&L items.
Local Currency is CAD and Group Currency is USD.
CAD 1000 and USD 920 are cumulative balances over a period of time.
Since at the end of year CAD became stronger, exchange rate is 1.11 as an example
Sales Account Balance
CAD (LC)        USD (2nd LC)        Translated Value in USD
1000                   920                        900
System passed the following entry in USD:
Debit Balance Sheet Adj A/c 20
Credit Translation Gain / Loss A/c 20
Here are the questions:
1. How does over all translation work? - Should we get any Gain / Loss and have an effect on P&L when all accounts (P&L, B/S) are translated?
2. How can there be a gain entry when USD value has really fallen from 920 to 900 in the current case.
Thanks for your time.
Vijay

Hi,
I had this issue too. The entry was just opposite to what it should be. I just flipped the accounts in table FAGL_T030TR.
Example: 410000 is sales account which normally should have a credit balance. Here are some entries that were posted to sales in 03/2009 and I am running FAGL_FC_TRANS at the end of the month.
March 1, 2009 Cr. Sales CAD 1000- USD 900-
March 2, 2009 Cr. Sales CAD 500- USD 480-
During FC translation transaction, system takes the balance in the account for the period (if you execute it with 'Val. period balance only' checkbox checked) and not the cumulative balance. SAP recommends translating period balance only (and not cumulative balance) for P&L accounts. It sees a balance in LC (this again depends on the config. you have in OB22 - whether the indicator is 1 (TC as source currency) or 2 (LC as source currency for translation)) which is 1500, converts that at month end rate. After conversion, lets say the balance is 1400-.
In this case, we expect a credit entry on sales account
March 31, 2009 Cr. Sales CAD 0 USD 20-
But system was just posting the opposite. I then flipped the accounts in FC translation configuration. I know it is misleading. In that configuration, system says balance sheet adjustment account, but what you should actually give there is your gain/loss account. Our gain/loss a/c. falls in the same GL account range as the main account. For example, for 410000, it is 410999 and for 510000, it is 510999. We report accounts 410000 to 410999 in the same node in the FSV.
Pl. feel free to ask further questions about this. Pl. test in your system and correct me if my above reply is wrong.
Cheers!

Currency Translation Type - Problem with Posting Period (0FISCPER3)

Hi Gurus,
We are currently working on an Implementation project in Integrated Planning (BI 7.0) and are having issues with Currency Conversion for each Month. The requirement is that Client will maintain Currency Exchange rates on a month on month basis for Exchange rate type P.
In all the Info providers we have used Posting Period 0FISCPER3 as a Time characteristic and NOT 0FISCPER ( Fiscal Year / Period ). Eventhough 0FISCPER appears as a Standard time characteristic in all Info providers , we have not even considered the same in all the Aggregation levels.
When we are now defining a Currency Translation Type thru RSCUR transaction , we select Variable Time Reference as "Beginning of Period" and the ONLY Standard Info Object available there is 0FISCPER and not the Posting Period 0FISCPER3.
Is there anyway that we can include 0FISCPER3 also as a Standard Info Object !!!!! If not , is there any way out ..... Do we have to include 0FISCPER necessarily as a characteristic in the Aggregation Level ? Please advise.
Regards,
Venkat.

Hi,
In the IP modeler you can also use the FOX formula for conversion.
CURC(<amount>, <d>, <exchange rate type>, <curr_from>, <curr_to>)
This reads the RSCUR table, and you can write your own date from fiscal or calander. So it is most flexibel.
Maybe this helps.
Regards,
Juriaan

Currency Translation Issue

Similar Messages

Maybe you are looking for