Want to restrict VFX3 from re-calculating taxes

[former_member645378]

Hi Team,

Our client is calculating tax at invoice level through third party OTSM. OTSM is returning tax % and tax amount which gets saved in the invoice. If the invoice gets stuck for accounting we release the document through transaction VFX3.

At the time of release through VFX3, system is recalculating taxes based on the % returned from OTSM and the net value present for that particular document item.

The requirement is once the tax gets saved in the invoice it should not get changed even through release from VFX3.

Is there any way by which we can deactivate the change of tax condition value after releasing the document through VFX3.

Regards,

Aditya Sahai.

[phanikumar_v3]

As suggested by santosh--go to VTFL and please keep the pricing type as D for your item.

if not --go to the relevant condition type of TAX and remove condition category-D Tax(which the origin to tell the system to redetermine Taxes controlled by pricing type in VTFL).

Also remember if you change this condition category--it is too risky while taking reports in the tax amounts paid to Government in the year end.

But any way you may try to get this report from your third party tool.

Phanikumar

[former_member645378]

Hi Laxmipathi,

The tax gets calculated from OTSM only at the time of creation of invoice through VF01, VF04 or VF06. The objective of this is once the tax gets calculated through OTSM it should not get changed either through VF02 or VFX3.

OTSM does not gets called through VFX3 or VF02. OTSM return tax rate in % and amount to SAP. Based on the % returned from OTSM and the net value of the invoice item, SAP is recalculating tax amount which in-turn is causing the issue.

We removed the From and To in Pri. Proc, base value calculation formula, made the tax condition type as fixed value from % base but nothing worked.

Is there any change we can do at the pricing procedure, condition type, copy control etc. to restrict SAP from recalculating the tax amount.

Regards

Aditya Sahai.

[Lakshmipathi]

As rightly pointed out by Santosh, you need to check with the third party vendor OSTM to eliminate this error.  Also since I am not sure what input parameters are being passed to SAP from OSTM and what is the periodicity for OSTM job.

If you are sure that this cannot be controlled from OSTM, then you can try with USEREXIT_PRICING_CHECK in program MV61AFZA where you can validate the field RFBSK from VBRK and force the system not to change any tax value

G. Lakshmipathi

[former_member645378]

The tax gets calculated only in the billing document. The preceding contract does not have any tax amount. OTSM is used as a third party engine to calculate tax and update the invoice with the amount.

e.g. OTSM return 5% rate and 9 USD as amount for a tax condition type for an item whose Net value is 200 USD. This gets stored in the invoice document. Now when we go to VF02 the tax amount is recalculated based on the Net value and the % and the same gets stored in the invoice. i.e. 5% of 200 which is 10 USD is stored.

The original tax amount was 9 USD returned from OTSM. There is a mismatch in the tax amount and the accounting document does not gets saved.

The same thing happens when we release the invoice through VFX3.

Is there any was by which we can restrict SAP from re-calculating the tax amount based on the % returned from OTSM and the Net value. We want to retain the tax which is returned from OTSM.

Regards,

Aditya Sahai

[eduardo_hinojosa]

Hi,

Taxes is a pricing object. Please, see SAP Note 24832 - Pricing rules / TVCPF, check the userexits in include RV61AFZA mentioned in this note. Check if values for status related with accounting is available in them.

I hope this helps you

Regards

Eduardo

[former_member186385]

Hi,

do you mean, Tax is getting re-calculated at the Billing document level ?

Can you check if your tax value is same in sales order and Billing ?

If you dont want tax to differ from sales order to Billing, you can control it in VTFL, by putting  PRICING TYPE as D

If your OTSM is feeding tax for Billing document before releasing to accounting document, probably you should check the code from OTSM to Billing

regards,

santosh