on 08-05-2010 9:27 AM
Hi All,
There is an issue with related to Re-determination of Exchange rate when the customer currency and document currency is different. As per the standard configuration the ROE is getting determined for F1 invoices. But now the issue is the ROE is getting re-determined for S1 invoices also. As per the business people the ROE should not be re-determined for cancelled invoices.
The value of the invoice for F1 and S1 remains the same. But when the accounting entry is posted there is a difference between F1 and S1 invoices in the accounting document. Hence there is a difference between the sale value.
Regards,
Jagadish
Thank you for the valuable suggestions.
The issue is resolve. There was an issue with time of updation of TCURR table. The TCURR table was not updated when the invoice is created, hence it picked the previous day exchange rate. When the canclled invoice is saved it took the exchange rate of invoice date.
Both are correct, only issue is with mainteance of TCURR table at the right time.
Regards,
Jagadish
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
*
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
The ROE is calcuated perfectly in the invoice document, but the issue is with the Value that is passing to the accounting document.
Regards,
Jagadish
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Can anyone advice on the issue related to ROE determination.
Regards,
Jagadish
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Thank you.
I am not sure i will get the approval from my Client to maintain the copy control, because this will affect the Global Process.
And the billing date is the same as the Invoice date. Only difference is the creation date in VBRK-ERDAT and Accounting document Entry date BKPF-CPUDT. Rest all the dates are the same as in Invoice document.
Regards,
Jagadish
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
There is not copy control settings in VFTT between F1 & S1.
One question , why should be the exchange rate recalcuated for the cancelled billing document. It should pick the same values maintained for F1 invoices.
Thanks,
Jagadish
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Either,
Maintain billing data for S1-cancellation invoice as F1-invoice.
Or
Maintain/Check PricingExchRate type in copying control for Order to Billing in VTFA.
If the date for invoice will be diff for cancellation invoice, then maintain Copying control in VTFF for F1 to S1 for PricingExchRate type.
Don't forget to check Ex.rate type for forgn crncy docs for cancellation doc type in OBA7.
Thanks & Regards
JP
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
There is one more currency type called Local currency or the Currency of the company code.
When the posting is made, it is always made both in local currency and in document currency.
Now check what is the posting value in document currency. It shoudl be same in invoice, cancelled invoice and teh accounting document of the cancelled invoice.
There can be some difference in local currency value for the accounting documents of the invoice and the cancellation. This can be due to the changes in the xnge rate maintained from Document currency to local currency. Here you have to do teh analysis and find out if the xnge rate between doc currency and local currency was changed or not.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
103 | |
12 | |
11 | |
6 | |
5 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.