Pricing condition type issue

Hi gurus,
i have a problem with pricing conditon type. The problem is the Conditon type which i am working as header condition and this condion in header coming correctly. Now the question the same conditon coming in item also why so. one morehting this condition type coming twice in the detail screen. Why so.
thanks & Regards
Ponts will awarded

Hi,
Please check V/06 conditiontype functionlality of tht condition type. There it might have been activated for both header level and item level. that is the reason it is printing in both levels. Please do needful setting there..
Regards
Sankar

Similar Messages

Pricing condition type Issue YPR0--- ZPR1

Hi All,
WE have a pricing issue, for example we have a condition type YPR0 and we use a pricing procedure which i will call ZME600, we are basically creating a new condition type to be called ZPR1 to replace YPR0, now in the copy control, delivery document to billing, for item category YBHP, the price type setting is ''G ''which means copy pricing elements unchanged and redetermine taxes, if we use this option, when we upload new price list, create a billing document, it will change the price on all open sales orders rather than keep the original price, so option is, change the pricing type setting to a ''D'' which basically copies all pricing elements unchanged, will this be a better solution? what happens when we start using new condition type ZPR1 to replace YPRO, the system will no longer recognise YPR0, if there any options to work around this, some have suggested linking YPR0 to ZPR1 in the pricing procedure??

Hi,
Please check V/06 conditiontype functionlality of tht condition type. There it might have been activated for both header level and item level. that is the reason it is printing in both levels. Please do needful setting there..
Regards
Sankar

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

Pricing Conditions Rounding Issue

Currently, our system has two pricing condition types. ZP,ZD. The ZP conditions represent a base price and the ZD represent a differential(- discount or + surcharge). Both are based on the same hierarchy. ZP00,ZP01,ZP02.ZP03,ZP04. A ZP01 overrides a ZP00 and ZP03 overrides ZP00, ZP01,ZP02 and so on and so forth. All transactions are settled in USD. However, most of the time the ZP, ZDs are based on prices that extend out more than two decimal places. I am experiencing and issue because SAP calculates the ZP and ZD separately and is rounding each. For example the ZP or base price in this case is $2.245. This times quantity of 3,999Gal = $8,977.755. SAP rounds this to $8,977.76. SAP then calcs. the differential ZD $.0235X3,999Gal = $93.9765. SAP rounds to $93.98. This is a total price of $8,977.76+$93.98 =$9,071.74. However the unit price is ZP $2.245 + ZD $0.0235 = $2.2685. If you take this price multiplied by the quantity $2.2685 X 3,999Gal = $9,071.7315. So the actual total price is off by 1ct because SAP treats the ZP and ZD as two separate calculations. I have seen various ideas on how to fix, from creating another pricing condition, to user exits. I was wondering if there was a preferred method? Or if there is a simpler solution?

Good Evening,
1. Please review OSS NOTE 80183 regarding Rounding.
   Values calculated in pricing are always rounded to the amount of
   decimal places which the used document currency owns. As subsequent
   processing steps setup on this rounded value rounding differences can
   occur in the calculation of the price per unit or in subtotal line.
   To bypass such effects note 80183 describes possible solutions to
   reduce / bypass this effect.
   A few problems in rounding after applying note 80183, variant 2 have
   been recorded where it was recommended to use the formulas 919 and
   920 on all discounts and surcharges that appear before NETP and the
   problem was solved.
2. In transaction V/06 there is a field under header 'Control data1'
   which can effect how the system rounds off condition values during
   pricing:
   ->> Rounding rule
       The rule that determines how the system rounds off condition
       values during pricing. The last digit will be rounded.
Example
o In the standard rounding rule '_', values are rounded off according
   to business standards:
   10.454 -> 10.45 DEM
   10.455 -> 10.46 DEM
o In rounding rule 'A', values are always rounded up:
   10.459 -> 10.46 DEM
   10.451 -> 10.46 DEM
o In rounding rule 'B', values are always rounded down:
   1045.9 -> 1045 LIT
   1045.1 -> 1045 LIT
   In this example, the currency of the condition rate is Italian Lira.
   The Italian Lira does not have any places after the point.
3. Also check if the condition type is set as item condition as well
   as group condition in transaction V/06. What this means is that
   the system will calculate the value of the condition on header level
   and compares it with the sum of item values in the document.
   Any rounding difference (KONV-KDIFF) detected, will be populated
   in the line item with greatest value or in first line item if all are
   of equal value.
   In other cases where there is no adjustment because there is no
   rounding difference when comparing the header value and the sum of
   item values.
   ->> Solution to this scenario -
       If you remove the 'group condition' setting, the system will then
       calculate amount for the items directly and you will not get the
       rounding. You must decide which setting is more suited for your
       business. This is not a bug, but works as per designed.
       EXAMPLE: MWST - tax condition (a group condition)
                Item 10     16%   of 100.90 = 16.14
                Item 20     16%   of 100.90 = 16.14
                                       Total = 32.28
I hope this helps you!
Kind Regards,
Martina McElwain
SD Forum Moderator

In Stock trasfer order how to pick pricing condition types

Dear Experts,
I am new to SAP MM my question is In Stock transfer order (plant to plant through purchasing) it is picking PI01 pricing condition types? how it is picking? what are the Accounting doc are updating?

Hi,
Goto the following node SPRO > IMG > Materials management > Purchasing > Conditions > Define Price determination process > Define shcema determiantion
Define schema for transport orders under which you will be able to see RM2000, when you try to open the RM2000 through M/08 transaction code.
You will be able to see the PI01 as the basic price condition type.
Accounting entries
During Goods Issue.
The stock account in the supplying plant gets Credited with the MAP value.
The stock account in the receivving plant gets debited with the MAP value.
If there exists any diffeence then the key AUF will get hitted.
During Goods Receipt.
No accounting doucment gets generated.
Regards,
DilliB

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.

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

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]

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.

PO Condition Type Issue

Hi All,
I have encounter a PO condition type issue, hope to get someone to enlighten me.
I have create both cuztomize condition type ZOT2 AND ZOT3.
With config in Control data 1
Cond. Class - A Discount or Surcharge
Calculat. type - B Fixed Amount
Cond. category - B Delivery cost
Group Condition
Select for Group cond. & RoundDiffComp
GrpCond.routine - 1 Overall Document
ZOT2 in header condition should be divided into item via value.
ZOT3 in header condition should be divided into item via quantity.
Both condition type havemanually enter with value 300
In the test PO I have created 3 materials:-
Material     Quantity     Net Price     Item Net
A     100     1,615.00     161,500.00
B     100          16.15         1,615.00
C     1000          16.15       16,150.00
In the Item view calculation for both condition type as stated below:-
ZOT2 - 270.27 : 2.70 : 27.03 (Ratios base on Value 100:1:10)
ZOT3 - 270.27 : 2.70 : 27.03 (Rations base on Quantity 1:1:10) the amount result should be 25: 25: 250 but the result I get from the system for condition type ZOT3 is the same as ZOT2.
Please advise how to reticfy the configuration. Thank you.

Eugenia Foong Pui Mun wrote:
Hi Shiva,
>
> I have try to config with the info you have suggested, but it does not seem to get the expected result.
Hi Eugenia...
I tested scenario with values you have mentioned. It works perfect both ways. Pls follow this....
1. Pls avert the changes I had suggested in my prev reply for changing the condition types. (group condition active, round diff condition & group cond routine, keep them as they are)
2. While you enter value in header with condition type ZOT2. the value gets properly distribute by the ratio 100:1:10 and thats perfect......Now
3. While you enter the values for condition type ZOT3 in the header...Pls note that your Total Qty is 1200 and the total condition value is 300 this means per unit qty the value is 300/1200 =0.25...
Now while you enter the values for ZOT3 in the header, enter 300 in the Amount column and 1200 in the Per column, meaning that the total of 300 shoud be divided into 1200 units irrespective of quantities per Line Item
Now check the results and you will have the distribution ratio 1:1:100
NB:For ZOT3 (Qty base) to work the UoM for all the line items must be similar
Pls check and revert
Regards
Shiva
Edited by: Shivaspatil on Nov 24, 2011 12:42 PM

Table for existing PO/Sch.Agg pricing condition types

Hi Experts,
Which table will have PO / Sch.Aggrement - pricing condition types with values as maintained in PO (like freight / P&F etc). I have the input of PO/Sch.Agg ref, plant, vendor & material.
We have created Z condition types for freight/ P&F and using the same in PO/Sch.Agg.
Thanks,
Jeeva

HI,
Same status.
In table EKKO also field "Doc. condition no." is updating for PO only, which is same as we find in EKKI. For Sch.Agg it it not updating the Doc.Condition no and remains blank.
Any way i have gone thro a different route. since I am looking for delivery condition for a completed GR, I can pick the conditions from EKBZ table.
Thanks.
Jeeva.

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

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

Pricing condition type issue

Similar Messages

Maybe you are looking for