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

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 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

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]

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

Pricing Condition Type - Not visible to the customer

Dear All,
What all the config need to set up in the pricing procuder for a condition type to ensure customer did not wish to see the value for the particular condition type on the invoice. However it should have the ability to value in the condition type automatically post to the correct accounts at the time of invoicing.
Thanks in advance.
Victor

Hi victor
If nobody should change the condition type at billing level or sales order level also means then go to V/06 and set the field Manual Entries - D .
Secondly, in VTFL change the pricing type to C or D then changing the condition type manually is not possible
Regards
Srinath

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

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

5.000,00 exceeds the limit 100,00 for condition type PR00.

Please help me to resolve this problem as I am not able to find where sud I go to delete the upper and lower limit of condition type PR00..Whene I maintain the record for pr00 for different material it create a error with limits.

Hi
What error message you are getting? Can you check if you have maintained anything for PR00 in SD > Basic Functions > Pricing > Define condition types > Maintain upper and lower limits.
Thank$

Pricing ZCondition Types are not appearing in Condition Record Maintanence

Hi All,
We have a requirement in SAP CRM Opportunity Management where the pricing determination should happen. So, to facilitate the requirement we have done the following
Downloaded the DNL_CUST_CNDALL and DNL_CUST_CND from ECC to CRM
But the Problem is when I am trying to maintain the Condition record in T-Code "/SAPCND/GCM" 　our Z-Condition types are not appearing in the list, also in Product Master Condition Tab.
Please suggest me how to resolve this issue.
Regards,
karthik J

Hi Karthik,
As a best practice -
1. If you are downloading the condition type and pricing procedure from ECC, then it is advisable to use ECC as a master system for all your Z condition type/condition record maintenance.
2. Similarly if you are using Pricing procedure as of ECC, then ensure that the downloaded pricing procedure in CRM is used for pricing procedure determination.
3. The condition record in T-Code "/SAPCND/GCM" is advisable to use if you are mainly using CRM Pricing.
By looking at your problem statement you are using ECC pricing procedure, condition types by downloading it to CRM.
If you have any other comments to make, please give the exact problem statement or any appropriate problem screenshot for further analysis.
Hope this will be useful
Thanks and Regards
DJ

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

Pricing condition type not working

Hi all,
A pricing condition type is present which is supposed to make the netvalue to zero after the order reason is changed to rejection using va02. But even after the order reason is changed to rejection and we tried to genrate new pricing document, the netvalue is not becoming zero. How can I debug this? The condition type is not determined by using condition records.
Thanks in advance.

Hi Smith
This should be working in the following ways.
1) Order Reason/Rejection Reason being a field in the Key combination with 100% Discount triggering Zero Net Value
if this the case, then you should check in Condition Analysis wheather the value has conrrectly flown in the condition table , if not why it has not flown in to the condition table (It could be missing value in the condition record or a prblem in the field catalogue user exit- you need to take Developer's help as suggested by others)
2) Using a Requirement and changing the Net Value Zero without any condition table field.
If so, put a break point in the requirement and check why this has not been successful in this scenario.
I hope the replies would help you to some extent in solviing the issue.
Thanks
Subbu

Function module to change the value for pricing condition type

Hello experts,
I want to change the value for pricing condition type for an item in the transaction CRMD_ORDER.
I used many function modules but none are working.
Please kindly suggest a function module that will change the value for a condition type .
I have used the following function module but its not working, please correct the coding if anything needs to be changed or added. Please help me .
Thank you.
CLEAR PRCD_COND.
     SELECT SINGLE * FROM PRCD_COND WHERE KPOSN = WA_ORDERADM_I-GUID AND
                                          KSCHL = COND_TY.
IF SY-SUBRC = 0.
*    MOVE-CORRESPONDING PRCD_COND TO L_COND_CHG.
*    CLEAR L_COND_CHG-KBETR.
    L_COND_CHG-STUNR = PRCD_COND-STUNR.
    L_COND_CHG-KBETR = COND_PRC.
*    L_COND_CHG-KSCHL = COND_TY.
    INSERT L_COND_CHG INTO TABLE T_COND_CHG.
L_HEAD_GUID = CRMD_ORDERADM_H-GUID.
L_ITEM_GUID = WA_ORDERADM_I-GUID.
INSERT L_HEAD_GUID INTO TABLE HEAD_GUID.
INSERT L_ITEM_GUID INTO TABLE ITEM_GUID.
    CALL FUNCTION 'CRM_ORDER_READ'
     EXPORTING
       IT_HEADER_GUID                    = HEAD_GUID
       IT_ITEM_GUID                      = ITEM_GUID
     IMPORTING
       ET_ORDERADM_H                     = LT_ORDERADM_H
       ET_ORDERADM_I                     = LT_ORDERADM_I
       ET_PRIDOC                         = IT_PRIDOC_RD
       ET_DOC_FLOW                       = T_DOC_FLOW
*     CHANGING
*       CV_LOG_HANDLE                     =
*     EXCEPTIONS
*       DOCUMENT_NOT_FOUND                = 1
*       ERROR_OCCURRED                    = 2
*       DOCUMENT_LOCKED                   = 3
*       NO_CHANGE_AUTHORITY               = 4
*       NO_DISPLAY_AUTHORITY              = 5
*       NO_CHANGE_ALLOWED                 = 6
*       OTHERS                            = 7
    IF SY-SUBRC <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
MOVE-CORRESPONDING LS_PRIDOC_RD TO L_PRI_COND.
INSERT L_PRI_COND INTO TABLE PRI_COND.
LOOP AT IT_PRIDOC_RD INTO LS_PRIDOC_RD.
MOVE-CORRESPONDING LS_PRIDOC_RD TO L_PRIDOC_CHG.
L_PRIDOC_CHG-PRIC_COND = PRI_COND.
L_PRIDOC_CHG-REF_GUID = LS_PRIDOC_RD-GUID.
L_PRIDOC_CHG-COND_CHANGE = T_COND_CHG.
INSERT L_PRIDOC_CHG INTO TABLE PRIDOC_CHG.
ENDLOOP.
LOOP AT LT_ORDERADM_H INTO LS_ORDERADM_H .
MOVE-CORRESPONDING LS_ORDERADM_H TO L_HEADER.
INSERT L_HEADER INTO TABLE HEADER.
ENDLOOP.
LOOP AT LT_ORDERADM_I INTO LS_ORDERADM_I.
MOVE-CORRESPONDING LS_ORDERADM_I TO L_ITEM.
INSERT L_ITEM INTO TABLE ITEM.
ENDLOOP.
L_FIELD-FIELDNAME = 'STUNR'.
INSERT L_FIELD INTO TABLE FIELD.
L_FIELD-FIELDNAME = 'KBETR'.
L_FIELD-CHANGEABLE = 'X'.
INSERT L_FIELD INTO TABLE FIELD.
L_INPUT-FIELD_NAMES = FIELD.
L_INPUT-REF_KIND = 'E'.
L_INPUT-REF_GUID = LS_PRIDOC_RD-GUID.
L_INPUT-OBJECTNAME = 'PRIDOC'.
INSERT L_INPUT INTO TABLE INPUT.
    CALL FUNCTION 'CRM_ORDER_MAINTAIN'
     EXPORTING
       IT_PRIDOC                     = PRIDOC_CHG
     IMPORTING
       ET_EXCEPTION                  = EXCEPT
     CHANGING
       CT_INPUT_FIELDS               = INPUT.
    IF SY-SUBRC <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
REFRESH EXCEPT.
CALL FUNCTION 'CRM_ORDER_SAVE'
EXPORTING
    IT_OBJECTS_TO_SAVE         = HEAD_GUID
*   IV_UPDATE_TASK_LOCAL       = FALSE
*   IV_SAVE_FRAME_LOG          = FALSE
*   IV_NO_BDOC_SEND            = FALSE
*   IT_ACTIVE_SWITCH           =
IMPORTING
   ET_SAVED_OBJECTS           = SAVED
   ET_EXCEPTION               = EXCEPT
   ET_OBJECTS_NOT_SAVED       = UNSAVED
* CHANGING
*   CV_LOG_HANDLE              =
* EXCEPTIONS
*   DOCUMENT_NOT_SAVED         = 1
*   OTHERS                     = 2
IF SY-SUBRC <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
COMMIT WORK AND WAIT.

Hi,,
To be able to call a function module in an update work process, you must flag it in the Function Builder. When you create the function module, set the Process Type attribute to Update with immediate start
Alternatively u can use this function module.
CRM_STATUS_DATA_SAVE_DB
BAPI_CUSTOMERCRM_CHANGE (If u wish to use a bapi for this).
Also , Let me know what error you got when implementing other function module.Does the function module didnt return any error but still the value is not changed for pricing condition type?

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 condition type pr00 not accepting the decimals.

Similar Messages

Maybe you are looking for