cancel
Showing results for 
Search instead for 
Did you mean: 

Currency Exchange Rate

Former Member
0 Kudos

Hi Gurus,

I have created a sales order and now its created billing document.

Billing doc has billing date as 18.10.2013 and Pricing date as 01.10.2013.

In OB08,Currency Exchange Rate defined for 30.09.2013 and 15.10.2013, so as per Pricing date 01.10.2013, Currency Exchange Rate should reflect as defined in 30.09.2013 (nearest date against pricing date) but its reflecling the price define in 15.10.2013.

could you please help on this.

Accepted Solutions (0)

Answers (2)

Answers (2)

Lakshmipathi
Active Contributor
0 Kudos

Currency Exchange Rate at item level (VBRP-KURSK) will depends upon the copy control settings in VTFL for Delivery related billing and VTFA for Order related billing.  Since your case is order related billing, check in VTFA what is maintained for the field 'Pricing Exc.Rate type".

G. Lakshmipathi

Former Member
0 Kudos

Hi Sir,

I have defined new currency price rate types. Could you please suggest me how i can map these so that these will come automatically in my billing document type.

Thanks in advance.

Lakshmipathi
Active Contributor
0 Kudos
I have defined new currency price rate types

It is a standard behaviour that the conversion of local currency into statistics currency always occurs with exchange rate type 'M'.  Check OSS note 1035594 for more information on this topic.

G. Lakshmipathi

Lakshmipathi
Active Contributor
0 Kudos

If you want to change this standard behaviour, check the following note

  • Note 1035003 - Wrong exchange rate type for curr transltn to statistcs curr


and do the coding corrections as recommended in the above note

G. Lakshmipathi

jignesh_mehta3
Active Contributor
0 Kudos

Hello Gourav,

Check the Exchange Rate setting in following two places:

1. T-Code - VTFL (Delivery to Invoice Copy Control) at Item Level, Check the entry in PricingExchRate Type.

2. T-Code - OBA7 - Docment Type RV - Check Ex. Rate type for forgn crncy docs under Default Values.

Thanks,

Jignesh Mehta