cancel
Showing results for 
Search instead for 
Did you mean: 
Subscribe

Hi All Sap Experts

I am using TAXINJ as taxing procedure.

when i am adding BED % as 16 and Edu2% and Heducess1% in tax code suppose V3

and save.

After saving again when i saw the tax code the values are disappearing from tax code v3

it is not updating ,where is the problem.

Tax juricdiction is assigned to tax procedure properly.

can anybody focus on it,which entry is missing.

Rgds

Ana.

0 Likes
View Entire Topic
Former Member
0 Likes

Hello ragvendra

Lines are activated,but what i have done i have deleted entry from FV11,what i think if i am using Taxinj i should not use FV11 boz my excise duty should flow from FTXP.

From that onwards my entry in ftxp is not updating.

kindly focus on this issue.

Rgds

ana

Former Member
0 Likes

Hello,

That is because of database inconsistency.Check SAP Note: 911364

Reason and Prerequisites

This is due to database inconsistencies in table A003 or A053.

If internal tax jurisdiction codes are active in the country of the tax code, the condition records are not stored in table A003 but in table A053. However, if you use tax jurisdiction codes together with an external control system (for the US or Canada, these include Vertex, Taxware or Sabrix), then the condition records are stored in A003, and this is also the case if you do not use any tax jurisdiction codes at all.

Solution

In most cases, there are database inconsistencies in table A003 or A053. You can only correct these inconsistencies by deleting the rates for the conditions that cannot be saved (percentage rates).

Search the rates in A003 or A053:

Example for the structure of table A003 (similar to A053):

MANDT KAPPL KSCHL ALAND MWSKZ KNUMH

001 TX MWAS FR C3 0000343815

001 TX MWAS FR C4 0000343816

All rates with reference to a tax code have

KAPPL = TX

Call transaction FTXP to transfer the values for the fields ALAND (departure country), MWSKZ (tax code) and KSCHL (condition type).

The percentage rates themselves are saved in the tables KONH and KONP, which have the key KNUMH.

Database inconsistencies occur, for example, if in KONH or KONP the KNUMH rate from A003 (or A053) is missing or incorrect. Incorrect rates in KONH or KONP may have other values in KAPPL, KSCHL or MWSKZ than the original A003 rate (or A053-rate).

You can delete the conditions by running a report or by using transaction SE16.

Regards