SD Billing Pricing - Tax Amount Rounding

[Former Member]

Hello experts,

I would like to know if it is possible, in SD pricing, to have internal calculation for a tax condition type with 3 decimal places.

Example:

Discount Basis	Tax %	Tax Amount (round 2 decimal places)	Tax Amount (round 3 decimal places)
1,11	23%	0,26	0,255
1,11	23%	0,26	0,255
1,11	23%	0,26	0,255
1,11	23%	0,26	0,255
1,11	23%	0,26	0,255
1,11	23%	0,26	0,255
1,11	23%	0,26	0,255
1,11	23%	0,26	0,255
23,50	23%	5,41	5,405
64,60	23%	14,86	14,858
58,31	23%	13,41	13,411
84,57	23%	19,45	19,451
16,57	23%	3,81	3,811
34,17	23%	7,86	7,859
227,29	23%	52,28	52,277
17,47	23%	4,02	4,018
16,66	23%	3,83	3,832
34,51	23%	7,94	7,937
42,06	23%	9,67	9,674
10,09	23%	2,32	2,321
11,64	23%	2,68	2,677
		149,62	149,57

Thanks in advance.

Regards,

AN

[Lakshmipathi · Accepted solution]

Set "W" to Calculation Type for your tax condition type and try.  Also have a look at OSS note 2056214

G. Lakshmipathi

[Former Member · Accepted solution]

Hello Lakshmipathi,

Thank you for your reply.

However I think that your solution is not applicable to my requirement, as I don’t want to increase the tax rate with 3 decimal places as suggested by OSS note 2056663 and 2056214.

The requirement is to have the tax amount calculated with 3 decimal places.

Please consider the example provided in my first post. Our tax percentage is 23%. As you can see there are differences in tax amount, for each item, if it is considered 2 or 3 decimal places.

Is there any chance to have 3 decimal places in tax amount calculation?

Thanks in advance.

Regards,

Andreia Nascimento

[former_member185462 · Accepted solution]

You mean ,you need to increase the condition value field KWERT to have 3 decimals??

[Former Member · Accepted solution]

Yes. Is that possible?

[former_member183879 · Accepted solution]

Hi Andreia,

The number of decimal places cannot be controlled at the condition type level. It is only controlled at the currency level. If the currency allows 3 decimal places, then the value of all the condition types will appear with 3 decimals. In this case your tax condition type also will have the tax value with 3 decimal places.

If your currency supports only 2 decimals, then tax value (KWERT) will also have only 2 decimal places. Enabling this to 3 decimals only at condition value level is not possible.

I also dont see any business reason in having tax condition value with 3 decimals while all other values are in 2 decimals. I hope it is not a legal requirement in a country where the currency is measured with 2 decimals. That will be unreal.