Pricing: condition type PR00 only one time enter

Dear
In sale order we have condition type PR00 and it is manualy condition type , now user was entering the same condition type(PR00)
Two times ,how can we restrict that PR00 is enter only one time in the sale order

Check this thread where the same topic was dicussed.
[how tostop duplicate conditype entry in to prcing at order |Re: how tostop duplicate conditype entry in to prcing at order processing lev;
thanks
G. Lakshmipathi

Similar Messages

Sales Order Pricing - Condition Type:PR00 inactive

Hi
In Sales Order Item level pricing, condition type PR00 become inactive. It shows reason : Inactive via formulae of incorrect.
Sales Order is partially delivered & billed. For remaining deliveries, system not allowing for billing, showing sales order is incomplete.
Condition Type PR00 maintained manually. Order quantity changed several times.
Please guide me on this.
Regards
Uma

Dear Umasankar
Check in VK12 for the material whether the From To Date is maintained for current period.
Also go to V/08 and check your pricing procedure whether any invalid account key is defined.
Thanks
G. Lakshmipathi

Pricing Condition Type PR00.

Hi experts,
I have a scenario where condition type PR00 shoul be mandatory in sales order and document should not proceed further unless the basic price is put while creating sales order. Also, system should not allow double entry of PR00.
I have already marked condition type PR00 as manadatory (still document is precceding in absence of any value ) and incompletion procedure log is applied.
Pl guide on same at the earliest.
Regards,
Pallavi

Hi
Check following points :
1. Check for the properties of condition type. It should has BASE PRICE as the property. And Access sequence should have to be there.
2. Mark check for Mandaotory in the Pricing procedure.
3. Check for your calculation. Your Net value should come as zero- if the PR00 is missing.
So when you will process any sales order it will, give you a incompletion log error as net value is zero- or pricing is missing for the item. And also Mandatory condition type PR00 is missing.
Thanks
Rishi

Pricing condition type pr00 not accepting the decimals.

Hi all,
i have a problem here at my client side, my client they are asking to have the price to be entered manually at the order level, my problem is   the conditon type PR00 is accepting only two decimal..    how to extend the decimal for the condition types.
for eg: Material 36.703.600    has price of 5.413, i am able to enter only 5.41, suppose if i enter the actual values it is saying the
" Input must be in the format __,___,___ V"
It says for decimal point update
"" (decimal point) (applies to numeric fields)
The decimal point occurs here (setting in the user master record)."
Which user master record i have to update.
kindly guide me on this
kumaresh

hi,
My problem is my client user wants to enter the price manually in PR00, since they are dealing with locksets and switches and also the do the shippment for outside the country . basically EU
the price are in euro   for eg 1 euro = 69.80 INR
for a material " 36.703.600" =   5.4135
they wanted to maintain for atleast three decimals
how to do it
regards
kumaresh

Condition type only one time

Hi ,
In pricing procedure there is a manual condition type.Now the user can do entry for this condition type more than one time for the line item.If i want to stop that by the user ,what should i do . Only requirement in the pricing procedure, is the option or there is anything else in the standard SAP ..Please suggest .
Thanks ,
Abhijit.

dear abhijit,
I have faced same problem and for this a solution is to maintain purchase infor record.
like you must be purchasing article from different vendors then you can maintain the different purchasing price for different vendor
Purchasing info records determine the prices suggested in purchasing documents in two ways:
The system,
1st searches under POrg. Data 1 - Conditions:
Conditions are included if they have been maintained for an info record manually or from a quotation (but can be changed manually afterwards)
2nd searches under POrg. Data 2 Last Purch Doc.:
If an info record does not contain any conditions (under POrg. Data 1), the system reads the number of the last purchasing document in the info record and then suggests the price from this document.
Info Update indicator for Conditions (in PO, RFQ/Quotation, Contract) :
for PO the update occurs in POrg Data 2 (last purch doc)
for RFQ/Quotation - the update occurs at POrg Data 1 Conditions (can be changed manually afterwards) and POrg Data 2.
for Contract the update occurs at POrg Data 1 - Conditions, IF at the time of the contract creation there is No info rec. Otherwise the info rec is updated with the last release order under POrg. Data 2.
but please note that the final price will get calculated on one condiition only and not on others.
regards,
Vishal
Edited by: Vishal Jajoo on Feb 19, 2008 2:16 PM

How to Know one condition Type (PR00) used in which pricing procedures

Hi Friends,
I have 20 pricing procdures I need information that condition type PR00 is used in which pricing procedures.
by help of
any report
any table etc
Thanking you
Arun

Dear Customer,
in standard there is no report available for your requirement.
In this case you can only create your own selection report therefore.
regards
Claudia

Pricing limits for condition type PR00

Hi,
I have got a scenario at hand, where i have to assign tolarence limits to all the conditions types in the pricing procedure. i have maintained limits in Transaction OVB2 except Base price condition type i.e. PR00. the problem i am facing is, we have got some where around 1,500 material and 3,200 customers and the price variation between the material is large(3000-150000). The main purpose of maintaining limits is to reduce the risk when entered manually. Please do consider the general business implications while replying.
eg: new pricing procedures, condition records for base price etc makes a hafty job, so can you please suggest me any other means to have a tolerence limit to condition type PR00(PR00 is used as base price for all pricing procedures).
Thank you, Have a nice day at work.
with regards
RVS Prasad

Hi venkata siva
As you are having around 1500 materials in your business . That means you need to maintain condition records for all these materials. While maintaining condition records only , in VK11 for PR00 condition type , maintain upper limit and lower limit in additional data . Then there should not be an problem
Another way of maintaining pricing at upper limit and lower limit is in OVB2.
Regards
Srinath

Condition type PR00 can only be used once

Hi Experts,
Im faced with a strange problem. Request your help in resolving it.
I tried to create my own pricing procedure by copying from RVAA01. Then i deleted all the steps and created my own steps. But when im trying to save the document, it says PR00 can only be used once. I deleted this condition type and tried to save it, it again says K004 can only be used once. Even after deleting all the earlier conditions which i copied from RVAA01, why am i getting this error.
Your help is most appreciated.
Warm regards,
Sarat.

You have deleted a row (i.e. condition type, say PR00).
After that click icon "Save".
Then when you create condition type PR00, system shall accept it.
Currently, you are deleting a condition type (PR00) but it is still "in memory" of the pricing procedure. You can not create the same condition type more than once in a pricing procedure. Therefore you can not create PR00 again & you are getting the error message.
First remove PR00 from the memory of the pricing procedure by clicking "Save", & then you can re-enter the same cond type.

CONDITION TYPE PR00 TO SALES AREA + DOC PP + CUST PP

Hi ,
While defining pricing procedure we only assing condition type pr00 to the procudure ? why is that so ? Since we have many condition types .?

Jerry Jerry,
Condition type PR00 is the base condition price. The whole price calculation is based upon the condition record entered for the condition type PR00. In actuality we assign all the other condition types but all these would turn out to be useless until we enter the base price condition type PR00 in the pricing procedure.
For example if in a pricing procedure we have entered conditions like K007 and KF00 and have not entered the base price condition type PR00 the values of K007 and KF00 will be shown as 0 as for these discounts there is no basis of calculation i.e. no base price.
Hope this answers your question.
Reward points if helpful.
Nagesh Murthy.

Pricing Condition type triggering based on other condition type

Hello sir,
There are some pricing condition types in our system.
Based on condition records you can trigger one condition type based on other    condition type.
For eg: PR00 condition type is there and amount is suppose 1000rs and other condition type is JBED and we made a condition record and put it some percentage so as soon as we some value in PR00 ,JBED condition type is automatically manipulating the value on the base condition record.
Now i want other than condition record can we trigger one condition type based on other condition type through defining user routine under requirement.
Suppose we have condition type ABC and some amount i have given and other condition type DEF , i want that amount of DEF condition type should automatically come from the Condition type and it should manipulate according to my routine .
eg Condition type    Amount
       ABC                  1000
       DEF                    40
The value 40 should come as 4% of 1000.
I am not maintaing any condition record and i want that this should trigger through some requirement created by me.
i created my routine no 905 and i putted the code inside it.
if komtl-kschl = 'DEF'.
komv-kbetr =   ( komv-kbetr * 4) / 100.
endif.
Now problem is that this code is getting trigger when i m giving value in DEF condition type then it is showing 4 % of it.
But i want as soon as i give value for the condition type ABC and some value 1000
then after pressing enter , one condition type DEF should automatically come with value 40 that too in display mode ,not in change mode.
Please suggestions and solutions regarding this matter , I will be grateful to you.
Manish

hi
In V/06 in the calculation type you can see the entries for "D-gross weight" & "E-net weight"
For the required condition type select the calculation type as gross weight or net weight. Save it.
In MM01 - create material master, here in BASIC DATA 1 SCREEN you have fields for gross weight & net weight.
Maintain the condition record in VK11 for the required condition type.
You can also maintain the scales as required like u said
1 to 10 kgs - 100 rupees,
11 to 25 kgs - 1000 rupees.
Another way could be
The BEST practice to do it is, use of VOFM routine for price calculation (VOFM-->Formulae).
Take help from ABAPer and write a routine such that
if weight = 1 - 10
price = 100.
else if weight > 8.
price = 1000.
else
price = 100.
end if
but the maintainnance of routine is big problem as u might be having many records
Hope this will help you
Vishal

How to change exchange rate type for specific pricing condition type

Hello every one,
I have a requirement for billing ie VF01.
currently all the exchange rate are being calculated with exchange rate type 'M' by default.
but now client want it should calculate exchange rate with type 'E' for two pricing condition type for all others it should calculate with type 'M'
Please any body can help me with the exit and code which i can use.
I have checked exits SDVFX008.
but how to change exchange rate with type 'E' only for two conditions.
as changing exchange rate at document header will change exchange rate for all condition type.

You need to assign KOMK-KURST = 'E', for those two condition types. If it had been item number specific, you could have used USEREXIT_PRICING_PREPARE_TKOMK(RV60AFZZ).
Do one thing, put a breakpoint on FM 'PRICING' and then do selective runtime analysis.
Check whether any user exit/BADI/ explicit enhancement are available when condition types are processed in a loop. If nothing is available, try implicit enhancement.
Link to refer for selective runtime analysis - Runtime Analysis for VOFM
Also try with VOFM requirements ( not sure whether changing KOMK-KURST is permissable in requirement as normally we only set sy-subrc values to suppress/allow condition types ). Don't forget to assign requirements against condition types in pricing procedure.

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]

Condition Type PR00 on materials and the price

Hi,
When I try to create a Sales Order by using VA01, in the item level, I am inputting the material number, quantity and profit center. Then when I select the same line and click on item conditions, automatically, condition type PR00 and the and amount is getting defaulted. However, for certain other materials when I click on item conditions, no condition type PR00 is being picked up. I need to manually input PR00 and the amount.
My question, I would like to know if there is any report available which shows, which materials are automatically defaulted with PR00 and what is the price automatically defaulted. I would also like to know, which are the materials are not automatically defaulted with PR00. (the cases where required to enter manually).
I am looking for any report or query etc.
Thanks in advance.

Adding to Shiva's comments...
The value for PR00 will be determined in the order only if the system could find a valid condition record exisitng. I guess, the condition type PR00 has been configured as...with value 'B - Automatic entry has priority' for the field Manual Entries. You can check the same using Tcode V/06. You are entering the values in the sales order item level for PR00 if the system fails to find a valid condition record. As Shiva mentioned, you can check the existing Condition records using the transaction V/LD for the report '15-Material Price'.
Thanks,
Ravi

V-41 tcode error :Table 304 is not defined for use with condition type PR00

Hi All,
I am trying to create a BDC using the transaction V-41.
The first screen has fields:
ConditionType and Table, where I have to fill values ZPM1 and 800 respectively.
But as soon as I enter the tcode v-41 and say enter, the above mentioned fields are already having the values 'PR00' and ' 304'. Normally if you take an example fo t-code VA02, all fields are blank.
Then an error message is displayed:
Table 304 is not defined for use with condition type PR00
This behaviour is not allowing me to use the BDC feature.
Please advise me on why this is happening. What are the possible solutions I can use to clear these values programmatically?
Can anything be done via customizing?
Regards,
Namita.

Dear ILHAN ,
Well the problem you are facing is having the following solution:
Table 304 is not defined for use with condition type PR00
Message no. VK024
Diagnosis
The selected condition type does not fit in the condition table, that is the basis for the condition record. Alternatively the selected condition type is not included in the condition types that were selected on the selection screen or that are defined in the variant of the standard selection report.
Procedure
Úse F4 help to choose a valid condition type.
If this does not give you the required condition type, check in Customizing for condition types and the related access sequences.
In the condition maintenance also check Customizing for the selection report (pricing report), that you have selected in the navigation tree, using the standard condition table as a reference.
I hope this helps.
It has worked for me.
I gave it a try and what I am getting using the transaction V-41 is create Price condition (PR00) : Fast Entry.
Please award points if you find it useful.
Regards,
Rakesh

Use of conditino category in pricing condition type

Hi,
Can anybody please guide about the exact use of condition category in the pricing condition type. In text it is mentioned that it is used for grouping of similar condition types but what exactly is the requriement for this? Does it have any control function like the feild condition class has( like for example grouping in this is used in redeterminations etc) ?
Please guide about the use of this feild and if maintained or not maintained then how will it matter?

Hi,
It serves some purposes.
1. It is used for the classification of condition types. During implementations, consultants classify the condition types into condition categories (Prices, Discounts, Taxes) and later use these categories to print the value of condition types in the forms. Coding based on condition categories reduces the effort instead of hardcoding on the condition type.
2. They also have some inbuilt property for some of the condition types like VPRS, SKTO etc where the categories are important for the behaviour the condition type, the way they are expected to behave.
3. Some of the condition categories will be applicable only for some specific processes and not for all the processes. for example e during downpayment.
But the complete function of this field can be only learned over a period of time when we implement new functionalities for the business.

Pricing: condition type PR00 only one time enter

Similar Messages

Maybe you are looking for