Condition type in tax and pricing

Hello Guru's
I have a purchase order in which  tax is say X7 for which condition type is appearing as MWVZ in taxes but in condition tab condition type is appearing as NAVS.Can any one tell how to check mapping of condition type appearing in taxes with respect to condition type appearing in pricing that is how system has derived condition in tax MWVZ to NAVS in pricing(that is in condition tab).
Is this SAP defined setting?Can we add /change it?How to check the same.?
Thanks
Regards
Atharva G

Hi
Thanks for reply.I wan't to know how value in conditions in tax is assigned to different conditions in pricing.Can we see that link.
Regards
Atharva G

Similar Messages

  • Relation B/W tax and pricing condition types

    HI friends
    I want to know relation b/w tax and pricing condition types.
    Here, i think we are giving relation in pricing procedure, how we are giving that relation, what is that mean.
    How sys will carry the values from tax condition types to pricing condition types.
    plz give me the details early.
    with regards
    lakky

    Hi...
    Actually in priciing procedure it is only sequential arrnagment of COnt type could be price, dicount or tax ... so that system calculates as process given by client.
    now when u see tax condition types .. they are also created in FI and also in Sd with same controls and linked via the account key...
    Account key MWS, MW3 are created in Fi and only used in Sd but azccount keys like ERL, ERF, ERS are created in Sd and used for account det in VKOA ...
    also MWS, MW3 used in VkOA but are used in TAx procedure also and are assigned G/L in Tax code ...
    now when u c the pricicng in a Sd doc .. sales order then all totals calculated and net price given and below that a Tax total given ... how system calculates tax totals is that in the tax conditio type in condition category .. we give Taxes as D so that all cond types with this cond catefory gets added and totalled to this tax total figure ..
    Reward if helpful
    Krishna

  • Condition types in Taxes, MM and SD

    Hi Experts,
    There are different kinds of condition types For Taxes( t.code obq1), MM (m/06) and SD( v/06). how are these condition types are useful. please explain the difference among these condition types.
    Regards,
    babu

    Hi Babu,
             Vendor purchasing price is made up of with differenct pricing elements. Ex . Material basic prices , freight charges , discount etc. To reprsent each element different condition types are used in MM pricing procedure.
             In the similar manner for Finishe goods selling prices is made up of diffeent price elements. Ex. Finished goods basic price , frieght charges, discoutn etc , To reprsent each element different condition types are used in SD pricing procedure.
              The total tax amont also is made up of with diffrent tax elements or different taxes are there. Ex input tax , out put tax , basic tax , surcharge , education cess etc. To represent these taxes various condition types are used in Tax procedure..
    Hope its clear........
    Regds
    Chandra

  • Create a new condition type for tax... and assign in the Tax determniation

    Hi,
    I need to add custom condition tax type, i tried creating the condition in OBQ1 and add that condtion in FI pricing OBQ3, now I want to confirm what is basic conept means whenever we create on condtion in OQB1 and add in OBQ3.
    i need to add that in Sales order and need to maunally populate that in the sales order.
    could anybody suggest to create a new condition type for tax.(full process).
    Thanks
    shankar

    Hi,
    Goto the T.Code "V/06".Create one new "Z" condition type.
    Maintain the Condition Class as "D(Taxes)".
    Calculation type as "A(percentage)".
    Cond. Category as "D(Tax)".
    Select the tick mark for "Group Condition" if it is applicable for you.
    In the next step assign this condition type to your pricing procedure by using the T.Code "V/08".
    Also maintain access sequence by using the T.Code "V/07" and assign it to your Condition type.
    Now this condition type will appeared in your sales order after maintain teh condition records.
    Regards,
    Krishna.

  • How to add Import PO condition types in PO and Scheduling Agreements

    Dear Friends,
    Pl tell me the procedure of adding Import PO condition types in PO and Scheduling agreement as these are not visible in the condition drop down list in ME21N and ME31L transaction. In pricing procedure theses conditions are available.
    Conditions are as follows:
    JCDB     IN Basic customs
    JCV1     IN CVD
    JECV     Ed.Cess on CVD
    J1CV     H.Ed.Cess on CVD
    JSDB     Ecess on BCD
    JEDB     Sec Ecess on BCD
    JADC     Addl.Customs Duty 4%
    Regards,
    ASK

    Hi
    1) please maintain tax code 0 on invoice tab
    2) check condition record for these condition through mek1/mek2
    3) check your defaulit condition in taxinn
    spro-logistic general-tax on good movement-india -basic setting-determination of excise duty-maintain excise defult
    Regards
    Kailas

  • Condition type field when Define Pricing Procedure Determination

    Hello Gurus,
        there is a condition type field when Define Pricing Procedure Determination. what does it mean ?
    Many thanks,
    Frank Zhang

    Here is are the details of various fields while configuring pricing procedure.
    A. STEP
    This indicates the number of step-in the procedure.
    B. COUNTER
    This is used to show a second ministep
    C. CONDITION TYPE
    This is the most important component in the pricing procedure. The rates are picked up from this element, on the basis of the properties described.
    D. DESCRIPTION
    This forms the description of the condition type.
    E. FROM
    This is used to define the progression of the calculation and range of subtotals
    F. TO
    This is used to define the progression of the calculation and range of subtotals
    G. MANUAL
    This function enables to allow the condition type to be entered manually also apart from automatic pickup.
    H. MANDATORY
    This function identifies the conditions that are mandatory in the pricing procedure. The sales price is a mandatory condition type.
    I. STATISTICS
    This can be used to represent the cost price of the material sold, generally used for study statistical impacts of price
    J. PRINT
    The activation of this function will enable the printing of the values and conditions to the document.
    K. SUBTOTAL
    A key is assigned from the drop down menu; this can be used by the system in other area like Sis for reporting purpose also
    L. REQUIRMENT KEY
    This function is used to assign a requirement to the condition type. This requirement can be used to exclude the system from accessing the condition type and trying to determine the value. This can be used to specify that the condition type should only be accessed if the customer has a low risk credit.
    M. ALTERNATE CALCULATION TYPE
    This function allows you use a formula as an alternative in finding the value of the condition type, instead of standard condition technique. this can be used to calculate complex tax structures.
    N. ALTERNATE CONDITION BASE VALUE.
    The alternative condition base value is a formula assigned to a condition type in order to promote an alternative base value for the calculation of a value.
    O. ACCOUNTS KEY
    The account keys form part of account determination. These keys are used here to define the posting of the revenue generated to respective account heads& to subsequent assignment to GL accounts.
    PR00- ERL
    K007/KA00- ERS.
    KF00- ERFu2026u2026u2026u2026.& so On.
    P. ACCRUAL KEY.
    The accrual keys form part of account determination. These keys are used here to define the posting of the revenue generated to respective account heads& to subsequent assignment to GL accounts and payment to respective parties.
    Kalpesh

  • Error-- Condition type MWST tax code A0 does not exist

    I have an Invoice and it didnu2019t pass for accounting entry.
    The error is promptu201D Condition type MWST tax code A0 does not existu201D, It never came at the time of Sales order creation.
    Diagonosis says the following
    When calculating tax, the system tried to determine the condition amount and the condition number from tables A003 and A053 using the specified condition type and tax code. However, no values were found there.
    Procedure says the following thing
    Check the Customizing settings for the specified tax code. Check whether the validity period (possible with tax jurisdictions) is defined.
    Please guide.

    Christiano,
    First let analyze the situation.
    1. Execute Tcode VA02 --> Item Details --> Conditions tab --> Click Analysis button. Try to find for condition Type MWST whether values are flowing.
    If it is not there then you have not maintained condition record.
    2. Tax Code.
        Execute FTXP Tcode , Check For A0 Tax code check whether you have maintained any value. if yes then check in condition record, whether you created record with Tax Code - A0
    If everything  above is perfect and correct
    3. Check Copy Controls and Pricing type
    Check the Validation period (it should not be the problem)
    Check and Revert
    Regards
    Sathya
    Edited by: Sathya Pavan Yedavalli venkata on Apr 21, 2009 2:06 PM

  • Error message FF762 " Condition type MWVS tax code A8 does not extist- MIRO

    Dear all,
    after support packagesi mplemented , I've the problem with transaction MIRO,
    because I cannot released the invoic for the folloqiong error:
    FF762 " Condition type MWVS tax code A8 does not extist.
    Please, could you help me.
    Thanks in advance for your cooperation
    Gaetano

    Hi,
    Go to FTXP and give the tax code A8.
    In the resultant screen, select the condition type MWVS, and link the condition type to an account key.
    Make sure all the other tax determination settings are fine
    Now, try the transaction it should work fine.
    Hope this helps you

  • Condition type MWST tax code A1 does not exist

    Hi all,
    I'm facing the problem while I'm releasing Billing doc to Accounting. This is the error
    Condition type MWST tax code A1 does not exist
    Message no. FF762
    Diagnosis
    When calculating tax, the system tried to determine the condition amount and the condition number from tables A003 and A053 using the specified condition type and tax code. However, no values were found there.
    System Response
    The specified amount cannot be posted in FI.
    Procedure
    Check the Customizing settings for the specified tax code. Check whether the validity period (possible with tax jurisdictions) is defined.
    I have already checked FTXP, and the Tax Code is already there.
    I have already checked the condition record, and it is already there,
    Maybe I have missed something...?
    Thanks before for all your help
    Regards,
    Rizki Harris

    Hi Typewriter,
    1. Check in a previously created invoice, accounting document - the tax code? (FB03) is it A1?
       --> the tax code is A1
    2. In VK12, MWST do you have other values of % tax (e.g. 0%). In a sales order, give appropriate Tax classification values for CMR, MMR so that MWST value = 0. Create invoice and check if you are getting the message
       --> in VK12 for Key Combination Domestic Taxes :
            TaxCl1Cust   TaxCl.Mat     Name                                 Amount     Valid from    Valid To         Tax Code
            0                    1                  Tax Exempt  Full Tax                          25.07.2011   31.12.9999    A0
            1                    0                  Liable For Taxe No Tax                        01.01.2008   31.12.9999    A1
            1                    1                  Liable forTaxeFull Tax              10       25.07.2008  31.12.9999    A1
         --> I still don't understand what do you mean by CMR, MMR ?
    3. Condition type MWST is not allowed to be processed manually..
    Regards,
    Rizki Harris

  • In sales order for the condition type MWST, **Tax code** is displaying wron

    Hi
    In sales order for the condition type MWST, *Tax code* is displaying wrongly at header level i.e. FF instead of AO (under account determination tab)
    AO tax is 0% but for FF it is 19%
    I have checked with the Access sequence it is picking access 08 correctly according to this it should show AO in tax code field for MWST but it is not so..
    There is a manual change for tax classification for material master in va02 initially it was blank now it is changed to ' 0 ' is any way influencing....?
    Even if I consider material tax classification and customer tax code  should not be FF because  tax code  FF is not maintained for the combination of access sequences for condition type MWST
    Please help me.
    Rajendra Prasad

    Dear Rajendra,
    There is a manual change for tax classification for material master in va02 initially it was blank now it is changed to ' 0 ' is any way influencing....?
    Definitely material Tax classification will influence to determine the Tax code.
    -->So Make sure that customer and material master having proper tax classification indicator.
    -->Have you Update the price after changing the tax classification in the sales order.by going to item dat -->condition tab then click on Update push button bottom of the conditions screen.
    -->Once again the check the condition record maintanence also for your MWST access sequence.
    I hope this will help you,
    Regards,
    Murali.

  • New condition type, new tax codes

    Hi,
    I have created new condition type for tax procedure TAXIN. I have defined the account key for it. The condition type is basically for exempted input tax transaction. Then I created new tax codes by using the new condition type. The percentage of the tax codes is 0 as it is exempted.
    When I am trying to post invoice by using above taxcodes, it gives me error that the tax code is not defined in taxprocedure TAXIN.
    What could be the reason?

    Did you create the tax code in the development or prouction system?
    If in development you need to export the tax code by going to FTXP and selecting Tax Code -> Transport -> Export. Then when you release the transport you should go to the Production system and select Tax Code -> Transport -> Import.

  • Tax and pricing info are not flowing into Idoc orders02-eledp04 and 05

    Hi,
    We are carrying out SRM5.5 -SUS and ECC6.0 Integration using PI 7.
    We are configuring for the MM-SUS Scenario.
    Now,to accomodate the Tax / Pricing we have installed the add on
    component LOCINSUS and we are having doubts on how to use it:
    1) Tax and pricing information are not flowing into IDOC- orders02
    (e1edp04 and e1edp05 segments are not present in the created IDOC). The
    condition print indicator in checked on ECC System and we have also
    implemented SAP note 995986.
    2)In create ASN transaction , we are not able to see the Excise Invoice
    Number and Date field in Basic data tab as expected from SAP Library
    document although we have installed the Localization Add on component.
    Please help us to reso1ve these issues,
    Regards,
    Mani
    099890-22217.

    Mani,
    Did you resolve this issue, because we are having the same issue in ECC6 with IDoc ORDERS02.
    If you did resolve this issue could you please let us know how, much appreciated.
    Bill.

  • Same condition type on header and item level = printing problem

    Hi
    I have a customer using some condition types on both item level and header level in quotations, orders, invoices ...
    In the pricing procedures it is customized (V_T683S-DRUKZ) that the conditions must be printed on header level (that is at the bottom of the documents).
    My job is to make the Smartform to print the documents, and I want it of course to be as close to SAP standard as possible.
    SAP standard will print these conditions on header level even if the conditions are at item level, but my customer wants the conditions created on header level to be printed on header level and conditions created on item level to be printed on item level.
    I'm no pricing expert, so my question is:
    Will it be fair if I tell the customer that using the same condition types on header and item level is bad practices - or at least bad karma?
    Best regards
    Thomas Madsen Nielsen

    Hi Shiva Ram and Madhu
    I have no problem understanding header vs. item conditions, so I really don't see anything in oss note 876617, that is relevant in this case.
    Madhu - I do not agree that everything is fine. My issue is that I want to stick as closely to SAP standard customizing as possible. In SAP standard customizing of a condition type you can use the flag V_T683S-DRUKZ to determine if the condition should be printed on header OR item level - you can not choose both header AND item level.
    I have a SAP standard smartform using two functions modules for reading header and item conditions. RV_PRICE_PRINT_ITEM and RV_PRICE_PRINT_HEAD. These function modules are based on the DRUKZ customizing flag and a condition marked for printing on header level will be supplied by RV_PRICE_PRINT_HEAD even when the condition is on item level.
    My point is: SAP standard customizing does not support printing of same condition on both header and item level. I can of course write tons of code to work around this problem, but that would be bad practices

  • HM00 -Condition type not present in pricing procedure.

    I have included HM00 as manual condition type in pricing procedure attached to the sales order through prcing procedure detrmination. But in sales order when I am entering the value manually for HM00, the error is "HM00 -Condition type not present in pricing procedure", but actually it is present in pricing procedure.
    Any idea how to fix thie problem ?

    Hi Sunil,
    Just check in V/08 > <b>YOUR</b> pricing procedure and see if HM00 is included in it or not.
    Hope this will definitely solve your issue
    Reward suitably
    Regards
    SD

  • Condition type MWST tax code S0 does not exist

    Hi, Pls advice how can I eliminate that idoc error message:
    "Condition type MWST tax code S0 does not exist"
    Should I maintain tr VK13 as well?

    Does S0 exist in FTXP?
    If not create it there?
    If it does, check the config to make sure it picks up a GL account and account key MWS

Maybe you are looking for