on 12-14-2012 12:31 PM
Hi
We are calling a routine in Pricing procedure to calculate VAT and using the condition record in the sales price. I have assigned an accrual key EVT in the pricing procedure and maintained G/L account determination in VKOA for combination of EVT and other account determination parameters. When iam posting an invoice to accounting, iam getting this error "Error in account determination: table T030K key EVENT". There are no Ob40 settings need to be required since iam calculating the value from routine and posting into accounting document.
Am i missing something when calling a routine in pricing procedure.
The condition record properties are cond class D (Taxes) and Calculate type B (Fixed amount).
In Pricing procedure the value is calculate and stored in KOMV-KWERT, the routine is storing the value in condition value and account key is EVT when i see in item condition details.
Appreciate your help in resolving this.
Thanks,
Vaishnavi
Dear Vaishnavi
There are no Ob40 settings need to be required since iam calculating the value from routine and posting into accounting document.
When ever there is Tax Condition you have to do the settings in OB40, to post in FI, regardless in whatever way you are calculating your condition value of that tax condition type.
In VK11/12 with your condition record please check weather you given tax code there and maintain the settings in OB40.
Check with the same and update.
Thanking you!
Ashish Mishra
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I agree with Lakshmipathi Sir.
Further, you can refer my suggestion in the following link, which might help in this error:
- http://scn.sap.com/thread/2122411
Regards, JP
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
i think if you are having conditon Class of tax type the GL should be in ob40. you will need to define the txn in OBCN too apart from SD area
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We are calling a routine in Pricing procedure to calculate VAT
Since it is a customised routine, you have to take the help of ABAPer, check in debug mode by executing VF02 where exactly system stops and give that warning. But in standard, for VAT, you need to have data in OB40 for whatever Account Key you assigned in Pricing Procedure against tax condition types. In your case, it would be EVT for which, I feel, there should be an entry in OB40 but I am not sure, based on what coding logic, you skip this control.
G. Lakshmipathi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
98 | |
12 | |
10 | |
6 | |
6 | |
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.