Check dupciate condition type in PO pricing calculation schema

Dear Gurus,
In my PO priciing schema I maintain all the condition type manual.
I want to control the duplicacy while enter the same condition type.
Is there any solution to check the duplicacy.
Thanks in advance
With regards
Soumen

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.

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 dependant on Pricing Date

Hi,
I want to know how to make a particular condition type dependant on pricing date. e.g We have a pricing procedure where a couple of condition types are only displayed, when I go to the header details in VA01 and put the pricing date manually in the Sales Tab.
Thanks
Amol

Hi Amol,
Go to V/06 and goto perticular condition type detailes screen, At bottom there is control data 2 in that there is field called 'pricing date' you enter "B" in that field, I think it will fullfill your requirement.
If it is helpfull please reward me with points,
Regards,
Murali

Can anyone explain what a condition type means in pricing.

Hi,
Can anyone explain what a condition type means in pricing. And how to create condition type and how it effects Pricing conditions.
As I am new to this area. Detailed explanation is highly appreciated.
Thanks a lot,
Rasheed

Hello Rasheed,
Below mentioned are the few important things related to pricing.
- You first define Condition Tables .
- Define Access Sequence and assign condition tables to it.
- Define Condition Type and assign Access Sequence to it.
- Now define Pricing Procedure and assign Condition Type to it.
- Now you define Pricing Procedure Determination using Sales Org, Distribution Channel ,Division,Document Pricing Procedure and Customer Pricing Procedure which are the key fields.
The above steps can be done in SPRO.
-Now maintain the Condition Records(for eg:For the specific material what is the cost or for a specific customer what is the cost of the specific material etc) using Txn:VK11.
- Once you maintain the Condition Records , you can reflect the same values in Condition Type in SPRO.
Hope this information is helpful for you to relate Condition Type in Pricing,
Please reward with points if this information is helpful for you.
Regards,
Shanthala.

How to check 2 condition types (kschl)

Hi,
READ TABLE i_komv WITH KEY kposn = ekPo-ebelp kschl EQ 'JEC1' OR
KSCHL EQ 'JMO1'.
how to write this above stmt? I have to check 2 condition types with a single read stmt?
regards,
Star Shankar

I guess Kishan wants to refer as:
READ TABLE i_komv WITH KEY kposn = ekPo-ebelp .
if i_komv-kschl EQ 'JEC1' OR
i_komv-KSCHL EQ 'JMO1'.
....<code>
endif.
As KSCHL is part of internal table I_KOMV.
or
READ TABLE i_komv WITH KEY kposn = ekPo-ebelp .
check i_komv-kschl EQ 'JEC1' OR i_komv-KSCHL EQ 'JMO1'.
....<code>
Kishan,
Correct me if i am wrong.
Regards
Eswar

MRP minus Pricing calculation Schema

Hi,
Can anybody let me know the complete configuration steps including master data settings for implementing the MRP minus pricing in SAP Retail?
Explaining my query here in details
Supplier has provided MRP to the Retailer. Retailer has decided the margin and then calculating the supplier cost on which they will procure the items from supplier. Now here we know MRP, Margin and then calculating cost so doing exactly reverse pricing. There are few doubts in mind and same sharing with you
1. Do I need to maintain first maintain MRP i.e. VKP0 = MRP?
2. Then do i need to flow the VKP0 value to purchasing calculation schema for reverse pricing?
3. What is the role of here SD pricing calculation schema WWS001 if we already know VKP0 = MRP?
Please help me. If it is possible then please mail me complete documents for MRP minus in SAP Retail.
Thanks,
Ashish Kumar

mantain the two condition one is to copy VAT condition and another is for required price which needs to be reversed.
Noe create one routine from ABAPER and assign the same for the VAT condition as well as basic price condition
logic for routine is
Y = X-[(12.5/100)Y]*
regards,
sujit

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

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]

How are US tax condition types XR1 to XR6 calculated

i searched few forums to understand the ways of US taxes getting claculated particularly on condition types XR1 to XR6, is the value available in SAP system or is the percentage value maintained in the taxware or vertex system?
if in SAP where is this maintained, i could see the same input & output tax codes assigned in OBCL settings for many states in US, so i am not able to relate this in FTXP, as different states provide different calculation.
if it is maintained through external system, is there way we can check the values or see in the screen?, how is this link of checking the external system enabled, is it through 301 cal type & its associated function module,
will there be a chance to change this value from the user end or do we need to seek Taxware or Vertex assistance here.
sorry on too many questions.
just got confused with the way it works
Regards
Ilango

Hi Ilango,
Check my responses to your respective questions:
i searched few forums to understand the ways of US taxes getting claculated particularly on condition types XR1 to XR6, is the value available in SAP system or is the percentage value maintained in the taxware or vertex system?
In SAP, only Condition Type XR1 to XR6 are only condition which is responsible for computation of tax in US & Canada. Where, even condition types UTXD & UTXE are equally essential to this. These condition types used for external tax calculation.
if in SAP where is this maintained, i could see the same input & output tax codes assigned in OBCL settings for many states in US, so i am not able to relate this in FTXP, as different states provide different calculation.
Well, I don't think there much from SD side to explorer here. As Tax procedure hardly have any role to play in SD business process for tax rate determination. But, that is very significant from GL Account determination for respective Tax Transaction in SD.
Refer my posts on
Tax code and SAP SD - ERP Operations - SCN Wiki
Plant-wise Different Tax General Ledger Accounts - ERP Operations - SCN Wiki
Whereas, configuration for Non-Taxable transaction as maintained in TCode OBCL, generally comes in picture when Tax Jurisdiction is not maintained in respective Ship-to master. Based on that configuration system will determine Tax Jurisdiction for those Ship-to.
% are maintained in FV11, not in FTXP.
if it is maintained through external system, is there way we can check the values or see in the screen?, how is this link of checking the external system enabled, is it through 301 cal type & its associated function module,
301 is not the only Routine associated. As like UTXD & UTXE there respective routines 500(collect tax input - export to IVP) & 501(get tax output data - import from IVP) are equally important with others 301 to 306(Set tax values and percentage into condition structure and fill tax base amount based on FM GET_TAX_RESULTS_FOR_301_306)
Refer SCN Wiki Tax jurisdiction - ERP SD - SCN Wiki
will there be a chance to change this value from the user end or do we need to seek Taxware or Vertex assistance here.
Hope you are aware, these tax IVPs are tool that is used to calculate taxes for the US tax rules.Yes, you might need to ask respective Tax IVP.
In Taxware, it provides the tax jurisdictions codes for master data addresses in SAP. Based on combination of both tax jurisdictions, the Taxware product code and dates, Taxware returns rates and amounts of tax and which jurisdictions get the tax.
Hope that helps you. If you still have any specific question, do revert back.
Thanks, JP

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 before CST/VAT calculation

Dear Friends ,
Is it possible to create a condition type which will get added only after excise duty calculation but before CST calculation.
If its possible kindly tell me how to go about it.
Regards,
DGN

Hi,
you will have to add an additional condition type in TAXINN procedure as "Freight Before Vat" , mantain it as statistical as it is only for calculation. and mantain FV11 for the same.
Further The same freight amount will also have to be entered in the PO pricing Procedure for Inventorization , payment etc.
first you have to make a tax condition type , make 2 , one as Value adn other percentage based. assign it to your tax procedure in steps which are before subtotaos: "Total excsie duty +cess" and "base for sales tax" , make sure to change the "to" part of base for sales tax .also make sure to tick these new conditions as statistical .Mantain FV11 for the Freight conditions.
The above config will only help you in calculating Correct Vat , this has nothing to do with PO pricing procedure. Freight will have to be entered in PO Pricing procedure normally as well.
Regards,
Vikas

Quantity based condition type for excise duty calculation in tax procedure

Hi,
If any one has worked on the issue of excise duty calculation on Quantity of items purchased Quantity based condition type.
[For a formula based calculation procedure TAXAU]
Example : If quantity purchased = 10 units
Duty to be calculated @ Rs.3 per unit
Duty on the 10 units = Rs.30
Other than SAP Note 816835 any help is appreciable.
Thanks a lot,
Uma
Message was edited by: Uma

I could not find this condition type/Tcode in our client system.
Even we are on 4.6c.
Thanks,
Message was edited by: Uma

Check dupciate condition type in PO pricing calculation schema

Similar Messages

Maybe you are looking for