Pricing condition type is inactive in pricing procedure

hi,
We have two base price in our pricing procedure ,
fixed -pr00
and wight wise.-pr01
both have condition class-B
while doing VA01 conditon type is showing as inactive(-Y-inactive because of subsequent price.
Please need ur help

Thanks for your early reply,my client do not want to make the !st conditiontype (PR00) as discount and surcharge.
let me elabrate the pricing procedure more detail.. we have two pricing procedure for export sales.
1-export sales -zabexp
2-Deemed export sales-zadexp
pricing procedure -zabexp
condition type                                     from      to      manual       required
proo(base price)                                      -            -         -                   -
pr01 (base price weight wise )                -           -           -                   -
it is runing well in zabexp. but the same setting is not running in zadexp.
Need Help.

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

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 is missing in Pricing Procedure determination

Hi experts,
We have a problem with Pricing Condition type in CRM.
We have created a Transction in CRM as a follow up for the Transaction which is replicated from ECC to CRM the pricing procedure has been determined. But the net value is "0".
when I checked in the conditions tab page "the condition type is missing" I checked Pricing Procedure the condition type is very much there. Then I checked for access sequence for that Condition type "Access sequence is also maintained.
Then I checked copy controls for the Source and Target Item categories, for copy conditions the indicator is set up as "copy conditions,Redetermine taxes" then I changed it to "Copy all conditions".
But still it is not happening.
Can any please help me in this regard? Did I miss any configuration?
Any help will be rewarded with points.
Regards,
Frederick.

Hi Fredrick,
This requirement must be assigned in your Pricing Procedure for condition type VKPO.
The system first checks whether the requirement is fulfilled and than only execute that condition type.
Requirements are nothing but Java Routines, which check for some condition before executing a condition type.
For this Go to path
IMG: CRM-> Basic Functions-> Pricing-> Define settings for Pricing-> Create Pricing Procedure.
Choose your pricing procedure here. Here for the condition type VKPO requirement 41 must be assigned in column REQ. The requirements are coded in JAVA in SAP CRM.
If this Pricing Procedure has been downloaded from SAP R/3, u can check in R/3 itself (Tcode: V/08) what the requirement is meant for, but choosing F1 and than the path for customizing.
Regards,
Shalini Chauhan
Edited by: Shalini Chauhan on Apr 29, 2008 2:43 PM

Condition type EK01 missing in pricing procedure A V (error message V1206)

Hi gurus,
We get error message "condition type EK01 missing in pricing procedure A V" when creating a Billing request from a SErvice Order through TX-DP90.
We reviewed customizing regarding this issue:
ODP4 - SD Document linked to condition EK01 (this condition shall bring the actual cost in the order)
ODP1 - Dinamyc item profile to create Billing Request.
Pricing procedure: sales area assignments, condition types (including EK01)
but error still shows.
Any idea what additional setting is necessary in customizing so EK01 is transfered to the SD doc in DP90?
Thanks,
VL

Hi Lakshmipathi,
Thanks for your answer.
I have taken a look to note you mentioned but it is related to Resource Related Down Payments customizing, which is not our actual requirement.
The note mentions though condition type EK01 for the purpose I am commenting: "...when the system processes a final invoice date, it determines condition type EK01 as the active price condition, thereby billing the actual costs".
Condition Type is in our pricing procedure with all the usual SD customizing settings, why is the system unable to process the costs?
Thanks for your always great help,
VL

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

Problem with pricing condition type in case of proforma invoicing

Hello All,
the problem is related to a pricing condition type in case of proforma invoice where the details are as follows -
Name of Condition Type - ZADC - Add 10% on Cost                                         Access seq.   Z038 Diff
                                                                                Plus/minus    A Positive
Cond. class - A Discount or surcharge
Calculat.type - A Percentage
Cond.category - Blank
Manual entries      D Not possible to process manually
Amount / Percent - Checked
Item Condition - checked
Scale Basis - Quantity
Currency Conversion - Checked
Quantity Conversion - Checked
This condition type has been kept as statistical in the pricing procedure. Still in the proforma invoice the condition type is not getting reflected automatically , whenever I am updating with " carry out new pricing " option the condition type is getting populated.In case of other commercial invoices this very condition type is getting populated automatically without any updates.Along with this point to be noted is that the Condition type in which the actual costi is captured has been kept active.
What more needs to be configured or what are the changes to be done to populate the condition type automatically as statistical during the time of proforma invoicing?
Thanks & Regards
Priyanka Mitra

Hi,
Kindly do the pricing analysis and check whether you have the following error such as
Inactive condition type because of subsequent price,
Regards,
Ravi

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.

Additional Pricing Condition Type Determination in Returns Oder

Hi Guys
I am working on Returns Sales Process, but I have stuck in pricing?
The thing is I have to determine the additional condition type based on transaction type .i.e. returns order when I create the returns order with ref. to sales order the pricing condition types which is present in the sales order has been copied but the additional condition type is not determined automatically?
I have created the 2 pricing procedure one of sales order and other for returns order.
Can anybody help me out?
Thanks advance

Hi,
All you have done is right. just assign the other pricing proceduere which you created for the document re.
To the combination of sales orgdistribution chaneldivision + cpp( in customer master)+ dpp( for the document re )
So now when you create with the re doument you will automatically get that pricing procedure.
hope this solves.
regrds\
preetham

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

Reset a pricing condition type value when generating billing document

Hi experts,
I have a delivery-related billing type. In sales order, there is a pricing condition type Z001, with value = 100, I would like to reset it to zero when generating billing document. Is there any configuration or user exits can do this? Thanks.

Hello,
You can do this in BILLING provided , if the Condition type is Manual condition type
To achieve this you have to do some configuration in the condition types as,
Goto transaction code V/06 and select your condition type and maintain the MNAUAL ENTRIES as C which means you can process it manually and in the V/08 chose your pricing procedure and against your condition type check the Manal entry .
Now you can change the value of the condittion type to 0 in the Billing document.
Hope this is clear,
regards,
santosh

Export pricing condition types

Hi Gurus,
Can any body tell me what are the condition types uses in export pricing procedure.
Thanks in advance

hi
the flow for pricing is same in domestic and export mostly.
Its better to have seperate pricing procedure for export.
In case of export you have to specifically check with CIF or other inco term related conditions such as sea freight , air freight, inland transport, insurance, LD discount etc.
these are depending upon agreed delivery realted charges.
other components like basic price sales discounts , commissions will remain same.
and conditions applicable locally like CST,VAT, and other taxes are not applicable.
excise,education cess and higher ecess etc depend upon the way goods are exported whether under rebate, on payment of duty or exempted .
regards
mandar

Problem in Copying Pricing Condition Type

Hi All,
This problem is regarding copying pricing condition type in Sales Order. The problem is given below with an example -
Qty of Material A - 10 PC.
Condi Type   Amount Currency   Per UOM Condition value Currency
ZP06             100         INR          1     PC      1000.00             INR
ZP07                2         INR          1      PC         20.00             INR
ZP08               98        INR          1      PC        980.00             INR      Statistical
ZP01               98        INR          1      PC        980.00             INR      Mandatory with ERL A/c Key Active
The condition types ZP06 & ZP07 have access sequence maintained for them and ZP08 has been derived deducting ZP07 from ZP06.
I want the above mentioned scenario where the values of Condition Type ZP08 which is a Statistical Condi Type will be copied exactly & entirely to condition type ZP01 where It will remain active alongwith posting key ERL.
I have tried copying it by 100 % copy but the value is getting changed as 100% instead of 98 INR.
Considering the above scenario please suggest some soluitons.
Thanks & Regards
Priyanka

Hi Tarpan,
First of all thanks for checking my post.
In the problem I am not looking for the value of ZP08 to be maintained manually.I want the system to copy the exact details of ZP08 to ZP01 entirely where the condition type ZP01 will remain active alongwith the posting key ERL.
I have tried copying the condition type ZP08 by using 100% copy of condition type but in ZP01 the resultant value becomes 100% in place of 98 INR.
Please suggest some solutions.
Thanks & Regards
Priyanka

Table to link FI document number, line item and pricing condition type

Hi,
I am looking for tables to link the FI document number, line item and PO pricing condition type.
Appreciate any help on this.
Thanks.

For any PO in ME23n in which Goods receipt has happened, you can check in the itemdetails->Po history tab in ME23n.
Here you will find the material document number. Just click on the material document, it will take you to anpther screen here you will find a button for FI document.
Click that button for FI document. In PO history istelf you can see the Condition types.
Hope this helps.

Pricing condition type is inactive in pricing procedure

Similar Messages

Maybe you are looking for