Double tax conditions in pricing procedure

[IvanLPG]

Dear colleagues,

I am facing an issue in pricing that i can not explain. I am using a pricing procedure, which is copied from RVAARU Standard - Russian Federation, especially in the are of tax conditions, where i copied following lines:

915 0 MW01 Tax Trigger       
916 0 MWR1 Sales Tax Manual         X 5   16
917 0 MWR2 Sales Tax Sett. Man. 916   
918 0 MWR3 SlsTax Sett.Rev.Man. 916   
919 0 MWR4 Sls Tax Manual Local         X 5   16
920 0 MWR5 SlsTax Sett.Man.Loc. 900   
921 0 MWR6 SlsTax Sett.Rev.Loc. 900   

When I create a sales order and branch to th epricing, I can see the condition types MWR1, MWR3 and MWR5 double.

Any idea where it comes from?

thanks a lot

[IvanLPG]

it turns out, the porblem was in FI, The tax codes were not imported correctly from SAP reference in Tcode FTXP.

[Lakshmipathi]

Update here, after clicking the "Analysis" button in the same condition tab, what message system shows against these condition types.  Also have a look at the following note whether it helps you:-

Note 633422 - Add-On Solution for Russian Core Functionality

G. Lakshmipathi

[IvanLPG]

This is how the analysis looks like:

MWR1: MWR1 008 Condition record exists (removed manually)

MWR1: MWR1 207 Condition has been found (without condition record)

MWR2: MWR2 208 Condition record has been found

and so on,

All the conditions MWr1, MWR2 ;WR3 are shown double and MWR1 even triple.

What could cause this?

[Lakshmipathi]

It seems the condition record has been maintained for multiple combinations in which case, system will populate twice or thrice.  Ensure that condition record is maintained only for one combination.

G. Lakshmipathi

[IvanLPG]

Sorry, but i dont get it,

The calculation is activated through the tax trigger MW01 which has reference condition MWST.

Foe MWSt with country RU and customer tax classif. 1 and material tax classif.1 there  is only 1 record.

why would those multiply?

[Former Member]

Hi Ivan,

If there's only one active MWR1 condition, you shouldn't have problems.

However, I suggest you to analyze the access sequence for MWST: check wether the field "Exclusive" is checked for the different accesses.

Hope it's useful.

Regards,

Ornella