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

Similar Messages

Referencing condition values when creating return order is wrong...

Hello Experts,
Lets say I have a billing document that has 3 line items namely material A, B and C.
Now, I created a return order for material A with 2 separate line items because of different
storage locations. Now, is there a user-exit that lets my 2nd line item copy the condition values of the
1st line item of the reference billing document? because they are of the same material(A).
Currently, we are having problems when creating a return order having multiple line items of the same material
because the succeeding line items copies the wrong condition values of the referenced billing doc.
For example:
Original billing document:
Material      Discount
A          100
B          200
C          300
Return Order:
Material     Discount
A          100
A          200
A          300
The succeeding line items of my return order must point to the first line item since they are of the
same material. Hope you can help me guys. Thank you and take care!

You may need to explore in the copy control definition, especially the pricing type defined. Check if any customized requirements exists for condition which checks w.r.t to the document number instead of reference document number item.

Condition Type in an Invoice for Output tax

Hi,
In our Invoice we have different condition types for Output tax. These are the condition types :- MWST, IDM2, ZVLT and IDM3. All thse condition tpye refer to Output tax, although only MWST holds the actual value. But there is certain setting (i guess structure ikomv) which is sending all the condtion types in the IDOC. As the remaining conditon types are not required it is further giving an Error in XI. Please tell us which is the transaction that configures these condtions and also the required changed in our configuration.
regards,
Milan Thaker

I think this can be handled by adding a filter by condition type in the distribution model. See transaction BD64.

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

While creating VK11 for output tax it should allow only Output taxcode

Hi all,
while creating condition record VK11 for output tax ,in condition record only output tax code should be possible ,if they use any input tax code then error messsage should come or system should not allow to create.how we do this.
Thanks in Advance,
Bala

Hi ,
If you see it practically in Production..You will be maintaing condition record once and even if changes, it won't be so often. Secondly in Tax procedure what ever Tax codes are present that will displayed as a choice while maintainig condition record.
If it affecting by maintaining wrong code then better would to be educate Business users as per my understanding.
Thanks,
Veerendra

Condition Values different fro Billing and Excise Invoice in some cases

Hi All,
Excise Invoice for domestic sales is having different condition values.
I am scenerio like this when Billing doc manually VF01, excise Invoice in generated automatically and condition values
were corrrect.But when I create Billing Document using BAPI in program, Excise Invoice is not generating,then
we are running BDC for T-code J1IIN and creating Excise Invoice.Excise Invoice generated in second case (by BDC)
is having wrong condition values.
Can anyone explain why it is happing.Is there any user exist to copy Billing Doc condition values to Excise Invoice?
Thanks in Advance ,
Rayudu

Thanks for you response Lakshimipathy.
The above mentioned configurations were all ready done.Excise Invoice is getting generated when we create Billing Doc online.
Problem here is Excise invoice is not getting generated automatically when Billing Doc is created by our program,so we were running BDC code to created excise Invoice.
Condition values ( Duties :AED,Ecess,SHEcess) were getting calculated wrongly in excise Invoice which is created by running BDC code in program. But the Excise invoice which was created automatically while saving Billing doc manually is having correct condition values. But the billing document condition values remain the same & correct for both.
Regards,
Rayudu

While creating VK11 for output tax error should be ther for input tax codes

Hi all,
while creating condition record VK11 for output tax ,in condition record only output tax code should be possible ,if they use any input tax code then error messsage should come or system should not allow to create.how we do this.
Thanks in Advance,
Bala

Hi Jelena Perfiljeva ,
Thanks for the Reply
Its JIVP,JIVC , VAT condition types (India).

Prob. in Implement User Exit for wrong calculation of Surcharge during MIRO

Dear All,
In our system the calculation of Surcharge is wrong during MIRO.
So i write this issue to the SAP, the below solution is provided by them :
Use the user exit 'J_1I7_USEREXIT_PROCESS_TKOMV' to redetermine
the additional VAT condition type value. This user exit will be
called after the FM 'J_1I4A_TAX_CONDITIONS', where the
redetermination of the VAT will take place on the basis of
the changed excise duties.
So, userexit can be implemented by CMOD and SMOD, but this userexit actually a Function Module.
But now the problem is how can i implement the 'J_1I7_USEREXIT_PROCESS_TKOMV' function Module.
Regards,
Nitin Garg

Dear,
Thanks. I already make a enhacement in this function Module and write the below code:
ENHANCEMENT 1 ZMIRO. "active version
DATA : WA_XKOMV TYPE KOMV.
DATA : WA_KBETR TYPE KOMV-KBETR,
IDX TYPE SY-TABIX.
LOOP AT XKOMV WHERE KSCHL = 'ZSUR'.
IDX = SY-TABIX.
WA_KBETR = XKOMV-KBETR / 10.
READ TABLE XKOMV INTO WA_XKOMV WITH KEY KSCHL = 'JVRD'.
XKOMV-KWERT = WA_XKOMV-KWERT * WA_KBETR / 100.
MODIFY XKOMV INDEX IDX TRANSPORTING KWERT.
ENDLOOP.
ENDENHANCEMENT.
ZSUR is a custom surcharge condition type. But still surcharge is wrong calculated.
Nitin Garg.

Condition value of Tax gets wrongly added to Total value of Contract

Hi All,
I'm currently investigating an issue where there are 2 line items in an SAP Sales Contract. There is a human error in the second line where the billing end date is less than billing start date in the billing plan. Consequently, the second line has null Outgoing target value.
However, the header Total value in the Contract gets wrongly calculated as Basic condition value of 1st line + Condition value of tax condition type of line one due to this. When I modify the billing end date for the second line item to be a date greater than the billing start date, the above problem disappears and the total value of the contract does not include the tax component.
For eg.
Normal Error free Contract
Total Value at Header = 700.00 EUR
Material Outgoing Target val
Item 0010 MAT1 450.00 ( 450 + 50 (tax ) )
Item 0020 MAT2 150.00
Contract with billing plan error in second line
Total value at Header = 550.00 EUR
MAterial Outgoing target val
Item 0010 MAT1 450.00 ( 450 + 50 (tax ) )
Item 0020 MAT2 0.00
Any inputs would be most welcome.
Regards,
Venkatesh.

Got the solution by making the condition type as manual.
Thanks.
Dhruba

Modify MWST (tax condition) value

Dear All,
I got requirement to modify the value of tax (condition type MWST in Sales Pricing procedure).
Example: base value is 1000, --->tax 10% (automatic by SAP) is 100. However, I want to change this value to 120.
Can I do that, please suggest with the routine or instruction.
Thank you very much,

Hi,
I guess this may be ur requirement..
Go to V/06 select ur condition type MWST under the tab Changes which can be made mark the filed Value if its unmarked..
Now create sales order and u will be able to change the value of MWST cond.type manually..in condtion tab
Reg
JJ

Condition value of Tax condition type gets added to Total Value in Contract

Hi All,
I'm currently investigating an issue where there are 2 line items in an SAP Sales Contract. There is a human error in the second line where the billing end date is less than billing start date in the billing plan. Consequently, the second line has null Outgoing target value.
However, the header Total value in the Contract gets wrongly calculated as Basic condition value of 1st line + Condition value of tax condition type of line one due to this.   When I modify the billing end date for the second line item to be a date greater than the billing start date, the above problem disappears and the total value of the contract does not include the tax component.
For eg.
Normal Error free Contract
Total Value at Header =   700.00 EUR
                   Material          Outgoing Target val
Item 0010    MAT1               450.00                          ( 450 + 50 (tax ) )
Item 0020    MAT2               150.00
Contract with billing plan error in second line
Total value at Header =   550.00 EUR
                        MAterial       Outgoing target val
Item 0010         MAT1             450.00                    ( 450 + 50 (tax ) )
Item 0020         MAT2              0.00
Any inputs would be most welcome.
Regards,
Venkatesh.
Edited by: Venkatesh Gopalarathnam on Jan 24, 2012 9:48 AM

No, i didn't.
Actually, i enter condition type and amount in sales order manually.
At that time my program which i modified at 'Define And Assign Pricing Procedures' in IMG should be run.
But the result of running is different from my purpose.
To change Condition value of condition type in sales order, are there any solution?

How to manual maintain TAX condition value while creating sales order

Hi
I am creating one Tax condition suppose JLST without access sequence .
while creating sales order I am manually maintain the % value of TAX. suppose it is 1%
then I see It show some value in TAX .
save that sales order & creating delivery document for that but when I create Invoice its show error.
" Tax code in procedure CMTAXP is invalid ".
I know the configuration only for Tax condition with vk11 condition record .
BUT now I want to maintain TAX condition at the time of creating sales order.
so I remove the access sequence of that condition .
but It shows tax code error while billing.
My main question is that If i maintain condition record while creating sales order then how i can assign Tax code .
Can it is possible ?
if yes then How?
please help me.
thank you

Hi,
The "straight-forward" answer for Tax Code creation is contact the FI consultant. He shall help you, by creating Tax codes.
I have tested, with creating a tax cond type (copy of MWST) & manually entering values. I can create Sorder, Dlv and Bill but I cannot create an Accounting document. That is because of every line (amount) a Tax code is necessary.
I THINK, you can NOT have manually filled tax codes; access sequence is needed to get the tax value (%) and the Tax code from the condition record.
There is lot of material on the web to understand Tax classification, code etc. etc. See a useful link below -
http://www.sapgeek.net/2010/04/sd-determines-tax-code/
In short Tax code is a must and take the help of your FI consultant for the configuration of the same.
BTW - Tax code is already made created for MWST, therefore I suggested that you can use MWST. Furthermore, you can change the values corresponding to Tax codes in FTXP.
But if you are a beginner in these things, better take help.

Eror message FF805 when mwst based condition value is zero

Good morning,
I got the FF805 (Tax statement item missing for tax code L1) error when i am trying release a billing document to accounting.
I have three pricing conditions to the item: z001, mwst and z002. The tax condition is based on z001. Sometimes the z001 value is zero and z002 has always value. When the z001 is zero i get that error message.
The tax value (mwst condition) only is required if the z001 has value.
The z001 condition may have a value or may be 0. When the z001 has value there is no problem.
There is a way that i can have this without getting this error?
Thanks in advance.

Hi Sandrina,
Please Go thru the threads below,
Error : Tax statement item missing for tax code
FF805 Tax statement item missing for tax code
FF805 Tax statement item missing for tax code O0
Tax code error
Thanks,
Swamy H P

Mandatory Condition Output Tax MWSI is missing

Hello Experts,
We have a situation where the access sequence MWST is using the customer specific tables A509, A902, A906, A908

Hello Experts,
We have a situation where the leading system is ECC and the pricing
procedures, condition types and condition tables are downloaded to the CRM
system. The access sequence MWST used for the condition type MWSI in the
pricing procedure is using the customer specific tables A509, A902, A906, A908.
We got these tables developed in the CRM system as they did not existed
earlier using the below given SAP Notes and blogs:
514952
- Download of customer-specific tables
441083 - Transferring conditions for
material group MATKL to CRM
https://scn.sap.com/community/crm/master-data-and-middleware/blog/2014/02/11/condition-master-data--customizing-download
1070997 - Condition
download:Parameter BADI CND_MAP_CNV_FIELD .
As a result the customer specific condition tables are
created and filled in the CRM system after the downloads.
But, when we are creating an order, we are getting an error Mandatory
Condition Output Tax MWSI is missing and the tax is not determined
in the transaction.
Do we have to do some additional developments to get the
taxes determined in the CRM system.
Thanks,
Rishit

In which table do the Excise &Tax condition values of PO get saved?

Hai All,
Pls let me know the table in which the tax and excise condition values (JMO1, JEC1, JIP5) of the PO get saved. I also need to print the excise percentage in the PO. Pls advice.
Regards
sampath

Hi Sampath,
Pl forward the same program to us.We too hv the same issue.
If not possible pl give some ideas or suggestions..
If anyone else hv any ideas or suggetions on this issue pl help me out.
Thanks in Advance!!!
Edited by: Ranganayahi Chandirasekaran on Sep 18, 2008 9:34 AM

Condition value on Output tax (MWST) is wrong calculated

Similar Messages

Maybe you are looking for