This website is not affiliated with, sponsored by, or approved by SAP AG.

Tax condition types in tax and SD procedures

Logistics : SD and its sub-modules (Inquires, Quotes, Order Entry, SIS, Sales Contacts, Dist. & Billing)

Moderators: Snowy, thx4allthefish, mike_ac, Lost Identity

Re: Tax condition types in tax and SD procedures

Postby Martin_US » Tue Apr 01, 2014 8:52 pm


you might want to name the country where you encounter this.
Seems rather strange taxation.

Anyway MWST in German means Mehrwertsteuer. A term that would vaguely translate to Value Added Tax.
However, it is not in use in Germany since the 1960's. Instead they use Umstatzsteuer.

Now, that's the legal aspect. Since MWST was so widely used as a terminology, many still refer falsely to it.
The difference is how the taxes are past on between industries to the consumer and the accounting of it compared to the Umstatzsteuer. A little Google could help.

The last time I did a Google on MWST it is rarely still used. Countries listed were Switzerland and the USA.

In the context of your post, MWST is just a preconfigured condition that if not needed, can be ignored.
In the SD area it wouldn't really make a difference for as long as the condition type is marked as tax (which you have done)

Come to think of it, there are some gotchas based on the country you do business in, but again, this is more an FI issue. In most EU countries Tax is due at billing time. So, it's vital for tax reporting when billing is done.
This is why taxes are commonly calculated at billing and never copied, cause a tax rate can change between order in take and billing.
Posts: 663
Joined: Thu Nov 07, 2002 9:40 am
Location: Walking amidst the Stars

Re: Tax condition types in tax and SD procedures

Postby Frank Lai » Thu Apr 03, 2014 6:38 am


It is kind of unusual that you want to apply two different VAT tax rates. As to your question about MWST in FTXP answer are:

1. No MWST plays no specific role in the tax procedure in FTXP, in fact if you look at the content of the tax procedure say TAXD for Germany, you won't see MWST at all. The output tax is in fact MWAS. Therefore adding the two new ones by the same name is not necessary per say unless you really want to have a nameing convention to keep them the same.
2. The link from SD to FTXP is actually the tax code. What you will likely need to do is to create one tax code ( say A1) for the 15% and set the value in FTXP for your country and tax code. When you run VK11 for ZVAT, put in the tax code and SAP will call up FTXP for you and bring back the 15% into KBETR. Create another tax code the 1% and repeat
3. You control what get taxed by 15% or 1% within your SD pricing procedure no different than any other pricing conditions

Frank Lai
Posts: 1718
Joined: Mon Oct 21, 2002 8:03 am
Location: Canada

Return to Logistics SD

Who is online

Users browsing this forum: No registered users and 2 guests

This website is not affiliated with, sponsored by, or approved by SAP AG.