Condition type MWST in Pricing procedure US

Hi ,
I have added the MWST condtion type in pricing procedure for US .This condition type is not appearing in pricing procedure.This condition type has an access sequence MWST.Can anybody guide me on this how to correct this
Thanks in advance
Regards,
Nitin Amritkar

HI,
The MWST condition typeeither has 'manual tick ' in the pricing procedure.If that has u have to enter the condition type by F4 selection only.Otherwise u remove that tick and ckeck u can get MWST condition type automatically in all condition types.
Regards,
Andra

Similar Messages

Problem of DIFF (Rounding Off) Condition Type in Sales Pricing Procedure

Hi All,
This problem is related to Sales Order. The system is not picking up a condition type in the pricing procedure.
For example when I am raising a sales Order where the Trade Price is being calculated with the help of a Alternative Calculation Type , Subtotal 1 , X in the the Print column and Posting Key ERL are assigned to it.Here in the end the condition type DIFF is not getting populated in the pricing though it is maintained in the pricing procedure. When I am checking in the pricing analysis the error message and its detailed description which is shown as follows -
DIFF 011 Condition ignored (requirement 013 not fulfilled)
The requirement 1. was assigned to this condition in the pricing procedure. This requirement was not met in the preliminary condition step, and so the condition was excluded from further processing.
You can use Additional information to display the requirements used.
Now considering the above scenario please suggest to attain my requirement.
Thanks & Regards
Priyanka

Dear Priyanka,
The "reqt" field in the pricing procedure basically tells d system that the routine mentioned in this field is a sort of prerequisite without fullfilling of which the associated condition type will not get xecuted.
In ur case u have selected "1" which is for condition types A001, B001 etc used in "material listing / xclusion" function.
For condition type DIFF, the correct value is "13" i.e "Rounding as per T001R".
So just replace "1" with "13", things will b fine.
Please close the thread if answered.
regards
Param

Including Condition type (JEXS) in Pricing PRocedure

All SAP Gurus,
I have included the condition type JEXS in pricing procedure since 01 May 2008.
But still while creting some POs this condition type is not picked up (although maintained in Pricing procedure), what may be the reason?
What can be done with the old POs when this condition thpy was not maintained?
Regards

Hi Raj,
Please check your PO link to pricing procedure as mentioned below,
1.What have schema group assigned in PO ventor master?
2.What have pricing procedure assigned in schema group?
MM > Purchasing > Conditions > Define price etermination process > Define schema determination.
3.Then check your condition type(JEXS) whether it is in that pricing procedure.
4.Also check your condition type(JEXS) validity period.
Please reward points if my information useful.
Best Regards,
Nagapandian.

To make the Pricing Condition types inactive in Pricing Procedure

Hi Experts,
I am facing a senario where, in a sales order, pricing procedure, if one of the pricing condition type does not exist, then two other condition types (even though they are determined by condition records), should be either made inactive or should not appear in the pricing procedure.
Example: If I have 3 condition types in Pricing Proc say
YYY1, YYY2, YYY3, then the scenarios are
a. If one of the condition types YYY1 is not determined, then, YYY2 and YYY3 should not be either determined in the sales order or should be made inactive. This same logic applies to both YYY2 and YYY3.
b. If all three condition types are determined in Pricing Proc of the sales order, then, the price should be considered.
If it was just YYY1 then, I could have done it in VOFM by writing a routine and assigning it to YYY2 and YYY3 in pricing proc. However, the scenario is to check the other condition types as well and make YYY1 inactive if any of the other condition type does not exist. Both condition types are determined after YYY1 which is another difficulty.
I tried creating a dummy condition type and assigning it to Pricing Proc (at the end of Pricing Proc). For this dummy condition I put in a pricing requirement which checks for all three condition types and if one does not exist, then it make other conitions inactive.
However, this does not work in VA02 and VA03 as XKOMV is either not getting filled up or even if is getting filled, it is not having the condition type. It some times has condition records, and sometimes not... (not very sure why)
So, I was thinking of using user exit for the same. However, I was unable to find a suitable user exit for the same where KONV table can be read or XKOMV can be filled.
Can you please suggest if any user exit can be used for this or if we can implement it in a different way?
Regards,
Mukund S

Hi,
I think you can use condition exclusion functionality to select best pricing condition from a set of conditions in pricing. You can compare conditions in many ways.
I believe you can plot a solution with little research. The below link is for your reference.
[http://help.sap.com/saphelp_40b/helpdata/fr/93/743483546011d1a7020000e829fd11/content.htm]

Access for Condition Type of a Pricing Procedure

Dear CRM Gurus,
I have a scenarion whereby we have replicated the pricing procedures of ECC in CRM. In ECC I controll the activity of display of a condition type through the step no. Similar access control is desired in the CRM too.
I was advised for an object in CRM but that works best if the pricing procedure is of CRM origin only, as mine is from ECC it is non editable in CRM.
Would request kind guidance on this please.
Regards,
Tariq

Hi Try this.
CALL FUNCTION 'RV_PRICE_PRINT_REFRESH'
TABLES
    tkomv = tkomv.
g_komk-mandt = sy-mandt.
    g_komk-belnr = itab_disp1-vbeln.
    g_komk-knumv = itab_disp1-knumv.
   g_komp-matnr = itab_disp1-matnr.
    g_komv-zaehk = '01'.
    g_komv-kappl = 'V'.
    at end of knumv.
      call function 'RV_PRICE_PRINT_ITEM'
        exporting
          comm_head_i       = g_komk
          comm_item_i       = g_komp
     LANGUAGE          = ' '
   IMPORTING
     COMM_HEAD_E       =
     COMM_ITEM_E       =
        tables
          tkomv             = g_komv
          tkomvd            = g_komvd
      append g_komv.
    endat.
endloop.

Manual change of condition types in a pricing procedure

Hi,
I want to know the difference between
a) Setting value as C (Manual entry has priority) in the Manual Entry field of the condition type (transaction V/06) and
b) Setting the checkbox of "Condition determined manually" checked in the pricing procedure screen (transaction code V/08) aginst a specific condition type.
Please let me know in case of any other details.

Dear Christino
a) Let us assume, your pricing condition is PR00 and you set this as Manual entry has priority. You are maintaining some value in VK11. While creating sale order, system will pick from VK11 but however, you can change manually which will over write the system generated price.
b) Let us assume, for your pricing condition PR00, in V/08, you set the box Manual and also you have maintained in VK11. When you create sale order, in the condition tab, you wont see any condition value and all values will be zero. Once you input PR00 manually, other conditions will flow.
thanks
G. Lakshmipathi

Condition type EK02 In pricing procedure

I'm having a problem with theis condition type as follows:
Create sales order
Add material A to line item
Pricing procedure kicks in
EK02 shows fixed value 7700 EUR
Delete material A from line item
Add material B to line item
Pricing procedure kicks in
EK02 shows fixed value 7700 EUR
I'm not sure where this value is coming from at this point. Can anyone point in the right direction?
Thanks, Mark

Hi mark
EK02:
If you use this condition type, the result of unit costing is simply a statistical value which you can compare with the price.
It has the condition category Q ( costing )
Now when you go to VOV8 , in the condition type field you can see the option EK02. because this condition type when used will be flowing to the controlling .That is the reason we assign EK02 to our sales doc type
Check in V/06 and select EK02 and go to its condition type details and check the calculation type field wheather it is in fixed value or not
Regards
Srinath

Config required for EK02 condition type in Sales Pricing procedure

Dear friends,
I am trying to derive a costing run for sales order. I would like to know what are the config steps required to arrive a percentage factor for GP.
Kindly guide me in this regard,
Thanks in advance,
Vinayak

Hi,
If you are doing sales order costing then you will have to define the condition type EK02. Go to V/08. Select the Procedure used in SD. Click on Control. Enter the condition EK02 - Calculated Cost and mark it as statistics.
You sales order cost will be stored in such condition type.
Regards,
Jigar

Consignment process and Condition types in Export Pricing Procedure

Hi,
Can any body tell me the
1. consignement process i.e which document are used at which level
2. when we are going for exports sales then which condition types are used and on which calulation is based on.
thanks
harmeet singh

Hi there,
Consignment is a business process where the goods are stored at the customer / consignee location but are billed only when they are actually consumed.
It has 4 processes:
Consignment Fillup: order type KB, item catg KBN, Schedule line catg E0 or E1. This is when the stocks are moved from the plant stock to the consignee location.
Consignment Issue: Order type KE, item catg KEN, Schedule line catg C0 or C1. This is when the customer actually uses the goods for cunsumption.
Consignment Return: order type KR, item catg KRN, Schedule line catg D0. This is when the customer puts back the goods into the consignment stock (returns to condignee location)
Consignmnet pickup: order type KA, item catg KAN, schedule line catg F0, F1. This is when the stocks are put back into the plant stock from the consinment special stock. That is from the consignee location to the plant.
For all the above order types it has standard delivery LF & returns delivery LR delivery types.
Stocks at the consignee location are maintained as consignment special stock. Controlled by indicator W in item catg KEN.
Regards,
Sivanand

Use of MM condition type into Sales Pricing

Dear All
I am having two MM Condition types in STO pricing procedure which are statistical in nature. Condition type A is having condition category G (Cost) and B is having H (Base Price). I have created both the condition types in SD side using V/06 with dummy access sequence without maintaining condition record. Condition type having contion category G is getting populated in sales pricing automatically but second condition type having condition category H is not getting populated automatically from the MM condition records which was maintained in the MM side using MEK1.
Please advice whether I can populate the above condition records automatically from the MM side. If yes, then please guide me with steps to achieve the above requirement.
Thanks in advance....
Regards
Animesh
Edited by: Lakshmipathi on Oct 11, 2011 10:30 PM
Thread Locked as duplicate post is not allowed

Dear Shiva
Thanks for u'r prompt reply.
I will try the same as advised by you and confirm.
Regards
Animesh

Condition types for import pricing

hi,
     the conditions types for import pricing procedure are not appearing.
please suggest all the notes from where i can take reference and create the condition types for import process.
please also suggest what are they?
with regards

Hi anitha,
In case of import purchase. u have to configure the conditions in pricing procedure. The condition types are as follows:
1)jcdb               basic customs
2)jcv1               CVD
3) jec1               ECS on CVD
4)jed1              cess on customs
5) j1cv                secess on cvd
6) jsdb               secess on customs
Go to the master note no 1032295 for recent budget changes.
award points if found useful
chintu

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ã

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

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

How to assign a pricing type to the pricing procedure ?

Business Scenario : When the prices change from the time the order is taken to the time the invoice is created, how can setup the system to handle the changes automatically ?
I would like to know How to create a pricing type and How to assign a pricing type to the pricing procedure so that I can use the 'new pricing document' function in the sales document and 'Update prices' on the condition screens in the Billing document.
Thanks for your input in advance.
Oscar

Hi !! Oscar,
1) For pricing type definition you would require the help of a developer.
2) However, most of the commonly occuring requirements are supplied with standard SAP.
You can assign a pricing type to pricing procedure as follows:-
IMG>S & D >Basic Functions>Pricing>Pricing Control>Define & Assign pricing procedures>Maintain pricing procedure> Here, locate your pricing procedure , in the fourth coloumn using the drop down list, you can assign a pricing type to the pricing procedure.
Now you can use the 'new pricing document' function in the sales document and 'Update prices' on the condition screens in the Billing document !
Regards,
PATHIK
Message was edited by:
Pathik Pandya

Condition type MWST in Pricing procedure US

Similar Messages

Maybe you are looking for