MWST issue

Dear SAP friends,
I have a problem with a sales order in which MWST is calculating on wrong coditional base value .Indetail we are creating credit memo request for one quantity with referance to origial invoice(quantity 25) then automatic price condition type calculated condition base value considering 25 qty instead of 1 qty which is first identified problem and then there is a manual price condition type which we used to override the automatic price condition type we have given but still MWST is calculating based on the old condition base value( value based on automatic price condition type with 25 qty which is wrong) instead of calculation with new condition base value (price * 1 qty) .
We have checked requirement routine and calculation type routing which are standard and working fine in testing system.Also checked from config side like copycontrols and condition records.
Any advices would be appreciable .
Thanks in advance!
Regards
Amar

Hi Chidam,
I checked in testing & prod copycontrol ,both are having pricing type D and in testing it is working fine but not in prod.But as a temporary solution we have already asked to update credit memo req manually using pricing type G and it worked fine .Issue has been closed temporarily I guess but I am not satisfied the way I have given solution instead of finding rootcause.
Thanks for your response Chidam .

Similar Messages

MWST Issue-Reg.,

Eventhough customer setup for all three invoices in the attachment is the same (Sold-To 123456 in romania, Ship-To 654321 in Germany) in all three cases the tax determination is different. Invoice 1 shows 0 MWST with DE/RO/1/1. Invoice 2 shows 19% MWST with DE/1/1 but the delivery shows 0 MWST with DE/RO/1/1. Invoice 3 shows 19% MWST with DE/1/1 and delivery shows 19% MWST with DE/1/1.
Can someone please explain the difference in MWST in all three cases and why in one case invoice MWST differs from delivery MWST.
Thanks in Advance.

Hi Human Lion,
From your data, it is clear that there are two condition records for the condition type MWST.
1.Now check out the Document and pricing dates for all your sales and billing documents with the condition record validity dates. The problem may be with the validity periods of your condition records.
2. And about delivery and billing difference, The difference is coming because of your copy controls, in pricing type you would have maintained G/B/C
regards,
prasad

Mwst .invoice issue

Hi,
when i am doing invoice , pop-up-tax code b4 invlid is coming . when we are doing the invoice we are deleting the conditionn type mwst manuaally
please suggest
Thanks @regards
siva

Hi,
You first maintain MWST condtion record in VK11 With Tax code AN not B4 as per standard system...
This will resolve ur problem..
Regards,
San Rao.

SO raising-MWST

Hi Gurus,
While raising the Sales order : I am getting a Error message:
"Mandatory condition MWST is missing"
I have followed the steps from WIKI and I have also removed from V/08: Mandatory tick mark from MWST of RVAA01.
Still the problem exists.
can somebody share their ideas.
working on ECC 6.0
Thanks & Regards
Srikanth

Hi Srikanth,
happy to see you using the forum efficiently, going to Wiki also.
coming to the issue, once you remove the mandatory tick from pricing procedure at V/08 for MWST, also please ensure you have saved it. then create a new sales order to see its effect. the old sales order would still behave as if the tick is not removed as it was created before the config change at V/08.
However the otherway is actually maintain the condition records for MWST at VK11 for the required key combination, so that it will pick up at the sales order level.
regards
sadhu kishore

Tax Departure Country in Consignment Issue

Hi,
I have read lots of thread regarding this issue but all of them ended with suggestion related to plants abroad which in our case will not resolve the issue.
Let me again put the question and hopefully somebody will answer to this.
We are doing an implementation for one of our UK client.
The issue is regarding consignment fill up for country in Europe.
I understand that we need to file consignment fill up in the INTRASTAT reporting. This can be achieved by using billing type WIA with 100% discount.
but the issue over here is, when we create consignment issue, the tax departure country is getting determined as customer country because of which the tax is not getting determined from condition records.
We are getting an error of mandatory condition type MWST required which is correct as we are getting a value of tax.
Can anybody help me over here?
I don't think it is an issue of plants abroad.

I am already stating the reason.
MWST has 3 standard condition tables.
1. Departure and Destination country..
In our case --> Departure Country is GB and Destination country is DE
But in case of consignment issue it fetching departure country as DE and destination country as DE
2. Domestic Tax -->
Departure tax will be on GB country
3. Export Tax
Country will be GB and export country will be DE.
but in all the cases departure country is coming as DE and not GB.

Creation of new condition type: MWST

Hi, Everyone.
I would like to ask for some help regarding this issue: Creation of new condition type: MWST with the following details:
1. For the country French Polynesia, Create a new VAT condition of 10%.
2. Create a new one called : Class : Z u2013 Designation : France : TOM corresponding to 10 % of VAT to be invoiced
and then associate this new VAT code u201CZu201D to the applicant Nr 221860
If you could provide me a step by step process on how to resolve this, it would be very much appreciated. Thank you so much.

Hello
What type of condition type you want.
It is always advisable to create a new conditon type copying a standard condition type.
For gross price condition types select PB00/PBXX
For freight charges, Copy FRA1/FRB1
Regards

MWST not getting determined in CRM Sales Order

Hi All,
I am working on a scenario where we are using MWST for tax calculations. I am able to get the tax calculations correctly in ECC but when I create a Sales Order in CRM, MWST is not getting determined.
I have maintained the following
1) Downloaded the ECC customizing into CRM
2) Downloaded the pricing procedure into CRM
3) Downloaded the pricing conditions into CRM
4) Downloaded the pricing condition tables into CRM
5) Maintained the tax classification for Business Partner
Thanks in advance.
Regards,
Sandeep

Hi Sandeep,
did you try to use the price analysis in SAP GUI (set user parameter PRC_TRACE = X in SU3) to get further details what is missing for MWST determination? There could be multiple reasons for this issue.
Best Regards,
Michael

UK VAT - MWST Condition Rate in Sales Order different to Billing Document

We are testing the UK VAT Rate Change.
Condition MWST has a rate of 15% until today and 17.5% from tomorrow.
When I create a sales order with a requested delivery date of tomorrow and a pricing date of today the MWST Condition is shown as 17.5% at both header and lin eitem.
If I create a delivery, post goods issue and create a billing document today, the billing document correctly shows the MWST Condition rate as 15%%.
But the Sales document still displays the MWST Condition rate as 17.5% .
?? How can I get the sales document to display the actual condition rate ??
I cannot find a solution to this anywhere and would be grateful for any help.
Regards,

Hi Michael,
If the pricing date for the Sales Order and the Billing Document are the same, the VAT should be also be the same.
But the pricing date for both document does not always have to be the same.
If the real goods issue date is different from the planned goods issue date and you use it as a reference for the pricing date, then both dates will be different & that's OK. The same would happen if a discount is changed after the Sales Order is introduced but before billing & a new price determination takes place during billing.
IMHO the Billing Document is the critical document and needs to have the right VAT rate.
The Sales Order should have the data calculated based on the best information available at creation time, but does not need to be corrected after Billing.
Best Regards,
Franck

Pricing and MWST Condition Type

Hi,
I am trying to create a sales order but everytime i get this message
"Mandatory condition MWST missing"
I went to the pricing procedure control and unchecked the mdt button for this condition type....but still i get this message.
Can someone advise me on this?
Thanks and Regards,
Aditya

hi aditya,
the message is coming because its set as mandatory in the pricing procedure. Once you remove the tick against MWST for mandatory it will not come. Probably you are looking at the old order still. Whatever orders you create after removing the tick the system will not ask for MWST again.
But anyways to understand MWST is the output tax which actually needs to be maintained may be on cust/mat tax classification, domestic tax etc depending on the set access sequence key combinations at VK11.
pl let me know if the issue is resolved.
Thanks
Sadhu Kishore

Pricing Conditions Rounding Issue

Currently, our system has two pricing condition types. ZP,ZD. The ZP conditions represent a base price and the ZD represent a differential(- discount or + surcharge). Both are based on the same hierarchy. ZP00,ZP01,ZP02.ZP03,ZP04. A ZP01 overrides a ZP00 and ZP03 overrides ZP00, ZP01,ZP02 and so on and so forth. All transactions are settled in USD. However, most of the time the ZP, ZDs are based on prices that extend out more than two decimal places. I am experiencing and issue because SAP calculates the ZP and ZD separately and is rounding each. For example the ZP or base price in this case is $2.245. This times quantity of 3,999Gal = $8,977.755. SAP rounds this to $8,977.76. SAP then calcs. the differential ZD $.0235X3,999Gal = $93.9765. SAP rounds to $93.98. This is a total price of $8,977.76+$93.98 =$9,071.74. However the unit price is ZP $2.245 + ZD $0.0235 = $2.2685. If you take this price multiplied by the quantity $2.2685 X 3,999Gal = $9,071.7315. So the actual total price is off by 1ct because SAP treats the ZP and ZD as two separate calculations. I have seen various ideas on how to fix, from creating another pricing condition, to user exits. I was wondering if there was a preferred method? Or if there is a simpler solution?

Good Evening,
1. Please review OSS NOTE 80183 regarding Rounding.
   Values calculated in pricing are always rounded to the amount of
   decimal places which the used document currency owns. As subsequent
   processing steps setup on this rounded value rounding differences can
   occur in the calculation of the price per unit or in subtotal line.
   To bypass such effects note 80183 describes possible solutions to
   reduce / bypass this effect.
   A few problems in rounding after applying note 80183, variant 2 have
   been recorded where it was recommended to use the formulas 919 and
   920 on all discounts and surcharges that appear before NETP and the
   problem was solved.
2. In transaction V/06 there is a field under header 'Control data1'
   which can effect how the system rounds off condition values during
   pricing:
   ->> Rounding rule
       The rule that determines how the system rounds off condition
       values during pricing. The last digit will be rounded.
Example
o In the standard rounding rule '_', values are rounded off according
   to business standards:
   10.454 -> 10.45 DEM
   10.455 -> 10.46 DEM
o In rounding rule 'A', values are always rounded up:
   10.459 -> 10.46 DEM
   10.451 -> 10.46 DEM
o In rounding rule 'B', values are always rounded down:
   1045.9 -> 1045 LIT
   1045.1 -> 1045 LIT
   In this example, the currency of the condition rate is Italian Lira.
   The Italian Lira does not have any places after the point.
3. Also check if the condition type is set as item condition as well
   as group condition in transaction V/06. What this means is that
   the system will calculate the value of the condition on header level
   and compares it with the sum of item values in the document.
   Any rounding difference (KONV-KDIFF) detected, will be populated
   in the line item with greatest value or in first line item if all are
   of equal value.
   In other cases where there is no adjustment because there is no
   rounding difference when comparing the header value and the sum of
   item values.
   ->> Solution to this scenario -
       If you remove the 'group condition' setting, the system will then
       calculate amount for the items directly and you will not get the
       rounding. You must decide which setting is more suited for your
       business. This is not a bug, but works as per designed.
       EXAMPLE: MWST - tax condition (a group condition)
                Item 10     16%   of 100.90 = 16.14
                Item 20     16%   of 100.90 = 16.14
                                       Total = 32.28
I hope this helps you!
Kind Regards,
Martina McElwain
SD Forum Moderator

Condition type MWST

Hi Friends,
We set up condition type MWST (output tax) for our European customers. The rate is 17.5%.
Our issue is for some customers we won't charge 17.5% at all. (two scenarios could apply to one customer)
My question is
Is that possible that I am able to set up this condition type with a default of 17.5%, and be able to change it at ltem level to 0% whenever I needed?
Thanks you for your help in advance.
Linda

Hi Linda,
For the same scenario: same customer, same material, same country, the same rate should apply, so I think you can do this depending on the values you set in your master data.
If this is not the case, create a new condition by copy of MWST, let's say ZWST, and on condition type maintenance (SPRO -> Sales and Distribution -> Basic Functions -> Pricing -> Pricing Control -> Define Condition Types -> Maintain Condition Types) allow manual changes on field 'Manual Entries'.
Assign it to your pricing procedure and you should be able to perform this change.
Regards,
Joã

Condition value on Output tax (MWST) is wrong calculated

Hi experts,
I am facing an error when we are creating sales orders using the function module BAPI_SALESORDER_CREATEFROMDAT2. For different sales order position with the same price I am obtaining different condition value.
For example,
Sales Document item = 20 for Material1
CnTy
Name
Amount
per
UOM
Condition Value
ZE01
Price list SB
1.333,33
100
PC
13,33
ZE02
Customer Price SB
1.600,00
100
PC
16,00
MWST
Output Tax
20,000%
2,67
ZE03
Rounding Off
0,00
0,00
Sales Document item = 110 for Material2
CnTy
Name
Amount
per
UOM
Condition Value
ZE01
Price list SB
1.333,33
100
PC
13,33
ZE02
Customer Price SB
1.600,00
100
PC
16,00
MWST
Output Tax
20,000%
2,63
ZE03
Rounding Off
0,00
0,00
I don't know which could be the reason why the output tax is differing in both items with the same price (2,67 vs 2,63). Could you please guide me to get a solution?
Lots of thanks,
Javier

Hi G. Lakshmipathi,
I was trying to find the differences explained but I can't identify the issue.
These are the screen shots of both item positions:
Item number 20:
Ítem number 110:
Hope it helps to find a solution.
Thanks again,
Javier

Making net value statistical but MWST should be calculated correctly

Hi,
We have a requirement where we need to raise debit or credit notes, for correcting incorrect VAT invoices. The customer wants it done like this: Create new debit / credit memo request types, by copying DR / CR. These will have a pricing procedure which has the net value statistical but the MWST should be calculated correctly. Then debit / credit memos will be created for these requests. How to do this ?
I have tried making the net value statistical, but then the MWST becomes zero as the tax base is zero. I tried giving discounts like RB00 but this reduces the tax base value and hence the tax becomes zero.
Thanks beforehand !!

Dear Friend,
I faced a similar issue recently at client site & this is how I solved it:
I created a new Pricing Proc for these cases (& new Document Pricing Procedure - DoPP) & made settings in OVKK... which you have already done...
Now in the new Pricing Procedure, I made my basic Price Condition as Statistical.
The Tax (Tax Condition - MWST in your case) was calculating normally from Basic Price Condition (statistical)
I also inserted a new Condition Type which was Manual Condition Type to Enter Re. 0.01 (1 Paisa) because without a single Revenue Account you cannot post Sales Invoice (Including Credit / Debit Memo).
The above worked fine & client accepted the solution..
Hope this helps...
Thanks,
Jignesh Mehta

Mandatory condition MWST is missing - Non EU countries only

We are getting the common MWST pricing error but only for customers based outside of the EU (we are UK based).
The pricing analysis is as follows:
Access Details 10 - The requirement 007 was assigned for this access in the access sequence. This requirement was not met in the preliminary condition step and so the access was not executed.
I'm puzzled as to why countries within the EU (e.g. Germany and France) calculate okay using this access procedure as it seems to be for Domestic Taxes.
Any help would be appreciated.
Thanks
John

Hello John,
On the basis of the issue which you had raised on access sequence for MWST, i had digged around the requirement "007". This requirement talks about Domestic transaction but with the help of a ABPer you shall find that there are few validation put up based on the field called t005-xegld. This field is nothing but Indicator: European Union Member. I think for the following set of countries you shall get this indicator active.
Austria
Belgium
Germany
Denmark
Spain
Finland
France
United Kingdom
Greece
Ireland
Italy
Luxembourg
Netherlands
Portugal
Sweden
I think in order produce the condition type MWST properly for these sort of Countries, you need to set a new requirement taking these countries into consideration.
Hope this helps !!
Regards,
SARTHAK

Mandatory condition MWST is missing V1801

Hello Xperts,
I have an Order that loaded without a MWST condition record (Mandatory condition MWST is missing V1801).
Pricing Procedure – checked OK -MWST setup as ‘Required’ with Req 10.
MWST setup OK in VK13. (10% )
Customer Tax Indicator -1 – ok
Material Tax Indicator -1-ok
In analysis tab page of order item, for MWST material Tax Indicator, value is not coming in order, instead of that is coming(Exclamation in yellowcircle).
Tried to Update Price (by qty change and pricing update in conditions tab)but still the same issue.
Searched the forum threads and cud not find more info except for the below link which is not my case.
_ http://scn.sap.com/thread/1570584
Any inputs would be appreciated.
Thanks in advance.

Thanks for your assistance xperts.
This seems to be an issue because the material gets refreshed on the first of every month (future planning date). I think when this order was loaded, the refresh job was running and the material was locked which prevented the tax classification from being read.
Any subsequent changes/new orders do not seem to have this issue.
Once gain great to have your inputs.
Cheers,

MWST issue

Similar Messages

Maybe you are looking for