Price condition - Price determination analysis

Hello everybody!
i would like to know how is possible to modify a price condition type; so, the condition is about the transportation of the material and look at the vendor, the purchasing organization and the society. I would like to insert also the plant in the condition but when i go to the purchase order transaction - bottom of the page - condition folder - i click on "Analisys" and the system shows me all the conditions that found when it tries to create the purchasing price. There i find my condition of the transportation that gaves a percentual value: now i would like to add another filter for the plant.
Does anybody know where i can modify the fields involved in the condition?
Thanks a lot
Bye bye
Edited by: Andrea Stefani on Jun 24, 2008 12:24 PM

Hi,
1. Check the 'Sch Grp Vendor' assigned in the relevant Vendor Master-Purchasing view.
2. Also check the combination of 'Sch Grp Porg + Sch Grp Vendor+ Pr Pocedure' in
    Determination of Caculation Scheema in SPRO.
   Plz note that, whatever schema procedure assigned above, the relevant Condition types will be
   populated while creating Purchase order.
3. Pick up the condition type you want to change from above schema, and modify the way you
   want.
Thanks,
PNRao

Similar Messages

Price Determination Analysis Not Saved

Price determination analysis is not saved when a document is saved in CRM. Price details are displayed, but the "Accesses" button yields the "No pricing analysis available" message unless the price update button is pressed. This is not possible when a document is complete. Questions about how a price condition was chosen are unanswerable. Is there a way to save the pricing analysis every time a document is saved?

Hi
When a document is saved and you try to display the conditions , the data is fetched directly from database . At this point of time there is no condition access made and that is the reasn why you dont see pricing analysis available.
The pricing analysis data is determined runtime and not stored when the document is saved .
When you press update button , then Repricing is triggered and you will see pricing analysis when you click "Access button".
Regards
Me

The Condition for service price determination incomplete

Dear experts,
I run the System with EC&O Best Practice. Howerver, I can not enter Services on tab Service of Sales Order: Short text of Service, Quantity, UOM, Gross Price. the error "Condition for service price determination incomplete" occours when I press Enter key.
Conditions for service price determination incomplete
Message no. SE477
Diagnosis
Either the calculation schema for services does not exist or the condition types have not been defined correctly.
Procedure
Please check your Customizing settings for service conditions.
If you have not yet defined any conditions for services, you can adopt the standard SAP settings from client 0.
Please help me check this issue on the attached file.
Thank you very much.
Thanks,
Binh Tran
<Personal details shared by OP is removed by Moderator. >
Message was edited by: Jyoti Prakash

Hi All,
Thank you very much for your inputs.
I checked all the notes, 25357, 27024 and 1383066. Everything is ok in the system. and these notes explained more on the MM part not on the SD- BOS. However, still i am not able to complete the Inquiry, same error exists.
This error is in SD not in MM, while i am creating the inquiry BOS.
If any one come across it and solved it, please let me know.
Regards,
Suresh

Condition Types in Price Determination Process

Hi
Can any one explain me about in Detail about the VARIOUS TABS that work in the CONDITION TYPE of PRICE DETERMINATION PROCESS
Thanks & Regards,
Senmani.

hi
hi
control data 1 :
Condition Class is a grouping that lets you control each condition type differently.
For example, the condition type "taxes" defines that the taxes in a document must be recalculated if the country of the ship-to party changes.
Condition category (examples: tax, freight, price, cost)
A classification of conditions according to pre-defined categories (for example, all conditions that relate to freight costs).
Condition category basically identifies the type pf cost the Condition type is being used for & can be used for .
Calculation type
Determines how the system calculates prices, discounts, or surcharges in a condition. For example, the system can calculate a price as a fixed amount or as a percentage based on quantity, volume, or weight.
The calculation type can be set when generating new condition records. If this does not happen, the calculation type maintained here is valid for the condition record
Rounding rule
The rule that determines how the system rounds off condition values during pricing. The last digit will be rounded.
Example
In the standard rounding rule '_', values are rounded off according to business standards:
10.454 -> 10.45 DEM
10.455 -> 10.46 DEM
In rounding rule 'A', values are always rounded up:
10.459 -> 10.46 DEM
10.451 -> 10.46 DEM
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.
Structure condition
controls whether the condition type should be a duplicated condition or a cumulated condition.
This control is only helpful when you use bill of materials or configurable materials.
Aduplicated condition is duplicated into all assigned items.
A cumulated condition contains the net value of all assigned items.
control data 2 :
promotions
Specifies that the condition type in question is only valid for Promotions.
Use
Conditions for which this indicator has been set can only be maintained via the 'Promotion' menu - not via the Purchasing menu.
Accrual (e.g. Freight)
Indicates that the system posts the amounts resulting from this condition to financial accounting as accruals.
Use
If you mark this indicator, the condition appears in the document as a statistical condition.
Before Release 4.0 variant conditions (VA00) had to be created with the condition category 'O'
Problem: It was not possible to indicate a 'Variant condition' at the same time as 'Internal costing condition' and 'Freight'.
Solution: For this reason more indicators are being set up in 4.0 for the condition type:
'Variant condition' (KVARC)
'Internal costing condition' (KFKIV)
The characteristic values O and I for the condition category must no longer be used.
For more information, see the note 93426.
inv.list condi
Condition for invoice list
Marks the condition type as relevant for internal costing.
Quantity conversion
This field controls the quantity conversion during determination of the condition basis.
The field is only relevant for calculation rule 'C' (quantity- dependent.
It is relevant if the sales quantity unit and the condition quantity unit are identical (and is different to the basis quantity unit).
Deactivated: The condition basis quantity is converted via the quantity to the stockkeeping unit. This means that the condition quantity is determined for planned factors. This means that a change to the conversion factors in the delivery or the order are not taken into account.
Rounding errors can occur during quantity conversion.
Activated: If the sales quantity unit and the condition quantity unit are identical, the quantity of the document item is used, i.e. the actual quantity.
Condition for inter-company billing
Conditions for Internal Costing, for example PI01 and PI01 were defined before Release 4.0 by KNTYP = I (Price for internal costing).
Problem: It was not possible to indicate 'Freight condition' at the same time as 'Internal costing condition' and 'Variant condition'.
Solution: Therefore a new indicator 'Internal costing condition' (KFKIV) has been set up. You can use this to indicate a freight condition as an internal costing condition. For more information, see note 93426.
Scale :
Scale basis indicator
Determines how the system interprets a pricing scale in a condition. For example, the scale can be based on quantity, weight, or volume
Checking rule for scale rates
Indicates whether the scale rates must be entered in ascending or descending order.
Scale Type
Indicator that controls the validity of the scale value or percentage:
From a certain quantity or value (base scale)
Up to a certain quantity or value (to-scale)
Alternatively, it is possible to work with interval scales. Interval scales must be stored in the condition type, that is, the scale type "interval scale" cannot be changed in the condition record. The reason for this is technical restrictions resulting from the programming within pricing.
Formula for scale base value
Formula for determining the scale base value.
Use
You can use this formula to specify calculation methods that are not provided in the standard system.
reward points if helpful
thanks and regards
ravikant dewangan

Conditions for service price determination is incomplete.

Dear Gurus,
I am facing an error in Bill of services like "Conditions for service price determination is incomplete".In bill of services when am trying to enter the services in service entry sheet the system through the above errorr.S o can any one rspond immediately.
Thanks in advance
Rams

Hey
While creating Service PO
mainatain account assignment category
Maintain item category
Then enter the material description.
Automatically service tab will populate.
In this maintain service no ( the same can be created in AC03)
For the service maintain the conditions in ML33 or ML39 or ML45
Then create PO, The conditions will come automatically.
Regards,
Raman

Conditions for service price determination incomplete

Hi All,
While doing the VA11 through SD-BOS, I am getting the following.
Conditions for service price determination incomplete
Message no. SE477
Diagnosis
Either the calculation schema for services does not exist or the condition types have not been defined correctly.
Procedure
Please check your Customizing settings for service conditions.
If you have not yet defined any conditions for services, you can adopt the standard SAP settings from client 0.
Please let me know did you anyone got the same kind of error.
Thanks,
Suresh.

Hi All,
Thank you very much for your inputs.
I checked all the notes, 25357, 27024 and 1383066. Everything is ok in the system. and these notes explained more on the MM part not on the SD- BOS. However, still i am not able to complete the Inquiry, same error exists.
This error is in SD not in MM, while i am creating the inquiry BOS.
If any one come across it and solved it, please let me know.
Regards,
Suresh

Condition not Appearing in Account Determination Analysis

Hi,
we have some new conditions. these are CRM based. for some reason they are not appearing in the account determination analysis
config Condition 1
Class: Prices
Calc Typ : Percentage
Not possible to process Manually
Item Condition
pricing procedure
Condition 1
Statistical
has Account Key.
thanks for the help.

Its a Pricing condition that u have configured. It will appear in Pricing analysis.
regards

MIGO : Price determination

Hi all,
I got a problem when I try to do the good receipt for a purchse order in MIGO. SAP occures an error :
"Transaction cannot be posted due to errors in price determination
[X]Error during maint. of delivery costs in master conditions
Delivery cost conditions in different validity periods not identical "
What does it mean ? Where can I find the place where those validity periods are customized ?
I've already checked in the RFQ, and the period value of the delivery cost condition seems to be OK for all the costs...
Someone got another idea ?
Thanks all !

Hi Prasad,
Indeed this PO already has a GR, but this GR was cancelled.
Now when we try to do again the GR, we get that error.
But I check the PO and the delivery costs are still here. If I erase the delivery cost from the PO, I can do the GR. If I put back manually the delivery costs, I get the error during the GR.
So, do you have a solution ?
Thanks,
Mathieu

Price determination date control in Scheduling agreement (ME33)

<<Do not ask for or offer points>>
Dear SAP chams,
I have one doubt at the time of scheduling agreement creation. I am creating scheduling agreement trough t'code ME33. In the same, Select line item, go to item data, go to Additional data. Here the field Pr. Date Cat (Price Determination (Pricing) Date Control) contains the value "5" (i.e. GR date). I want to change this value. How can i change this determination ??...
Helpful answers will surely be awarded by points.
Thanks and regard,
Tarpan Vadaliya
Edited by: Matt on Feb 27, 2010 10:47 PM

Hi
Price determination category 5 cannot be change in scheduling agreement if your document type is time dependent. (See config spro>mm>purchasing>scheduling agreement>define document type. In that you will see a tick for time dependent condition)
If the config tick is removed then you can change price determination to any other option.
Regards
Antony

Price determination after historical simulation

I am confused about price determination after value at risk historical simulation run, my evaluation day is 2014.March.31, for commodity forward, the floating leg is based on price 42.17286 (the eighth shift for VaR calculation, my holding period is 10 days), which is shown in the attached picture, but my commodity price curve is showing 41.***,if I click "commodity price" under calcuation basis tab, it shows in March.31.2014, my commodity price is 41.57 USD. thus I will like to know how 42.17286 derived, is it from commodity price curve or commodity price? at which point of time? and the difference between commodity price curve and commodity price, if in March.26 , commodity price curve show 42.68, but commodity price shows 41.57, is it inconsistent?

hi,
it s really interesting issue!
this may not be the right solution but i ve tried and it worked right.
1-go to ME12 click the conditions tab on header line.
2-click the scales and click the details for scale type and choose "B" "last scale" for the scale type.
save and exit..
you ll be able to do PO-migo-and miro.
i hope it ll help.
regards.

Price Determination (Pricing) Date Control - Purchase Order

Hi,
We are exploring the Price Determination (Pricing) Date Control in the Purchase Order.
Clientu2019s requiring is, correct me if it is a wrong requirement:
We have created Tax Codes:
C2 - CST 2% valid from 01.04.2010
C3 - CST 3% valid from 01.04.2010
We have created a purchase order with Tax Code C2 - CST 2% on 30.03.2010 as we are in doing back log entries. Since the tax code is valid from 01.04.2010 only , the purchase order is not displaying the Tax Code Value .
Now we are doing the Goods Receipt on 01.04.2010, the system will not pass the entry for the CST as at time of GR, the System picks up the Tax data from the Purchase Order.
Now we want that the System should pick up the Data at the Goods Receipt, not from the Purchase Order. Some one advised me to use put GR Date in Pr. Date Cat. Under Item-> Condition Control tab. We are able to view the Pr. Date Cat by changing the Screen Layout of ME21N.
We want to know what use of the same & under what condition is, we use this.
Our suggestion:
1. We are of the view that we should create the Tax Codes with Valid Date from 01.01.2010 (not from 01.04.2010 as currently maintained)
2. Or since we are doing the back log entry, we should create all the Open Purchase Orders dated 01.04.2010.
Is this the correct way which we are suggesting?
Please note that we are dealing with Excise Materials also?
Please guide.

Thanks for the reply,
While testing the same, I also encountered the somewhat same problem.
You are suggesting that we should change the Tax Code Valid From Date.
What do mean by the follwoing:
Pricing date category "GR date" can't be set in PO if price is entered manually (with condition type PBXX). This also means manually entered conditions at Po will not be used.
Regards,

NEW FIELDS FOR PRICE DETERMINATION in MM

Hi all experts,
we have added new field in customizing so that in the purchase order in MM we can use new fields for price determination.
However we do not finde the exit or program were we can set a value for these fields.
for instance, we want to differenciate countries belonging to the EU and not. We create a yes/no field and get its value from table T005 where each country has this info. Everything seems to be ok, but our field is not populated into KOM* tables and therefore we don't go through the condition price...
Any ideas? Thanks.

Hi,
You can try using Info Record.
Thanks,
Venkat

How the Purchase Price determination process works in sap-mm?

Hi,
Can anybody tell in detail or have step by step document on Purchase Price determination process?
Thanks,
Pradip

Hi,
You can go for pricing manually or automatic. If you need pricing automatic you have to go for use of Access Sequences and Schema Group of Vendor. You can customize your pricing procedure according to your requirement such as like Domestic, Import and Stock transport.
For the above individually you have to configure Pricing Procedure and the following steps are:
SPRO->MM->Purchasing->Conditions->Define Price determination process
1. Define Condition Table:
2.Define Access Sequence,
3.Define Condition Type,
4.Define Calculating Schema,
5.Assign Calculation Schema, Access Sequence and Condition Type,
6.Define Schema Group Of Vendor,
7. Define Schema Group Of Purchasing Organization,
8.Assign Schema Group Of Vendor to Purchasing Organization,
9.Assignment of Schema Group Of Vendor ,Schema Group Purchasing Organization and Calculation Schema.
10. Assign Vendor to Schema Group of Vendor (XK02)
11.Maintain Condition record (MEK1)
after above steps, you can go for create PO in ME21N.
In the case of Import PO, you have to activate Import PO.
SPRO->Materials Management -> Purchasing -> Foreign Trade/Customs ->Control Foreign Trade Data in MM and SD Documents -
Regards,
Biju K

Using formula in price determination process for PO

Hi, dear experts,
I would like to define some conditions types for purchasing orders that allow me to calculate an insurance amount using the formula:
Insurance = [CF)((C+F)10%)]T
Where: C is the Gross price, F is the Freight and T is a factor that the user has to input
For that, I define a condition type for gross price, for the freight and for the T value
How can I have to define a condition type to do this operation?
On the other hand, the freight is a percentage of the gross price, but for this operation I need the amount, how can I make reference to this amount? (Result of gross price * freight (%))
Also, there is a link where can I find information regarding the price determination process?
Thanks in advance,
Mairo.

Hi,
You can store (surely you have them in data) the data for C and F in values that you can config in pricing procedure in the field 'SubTo'. After, you can obtain the amount with a formula VOFM and set it in M/08 in field 'AltCTy'. You can check this links to know how to do it:
http://saptechsolutions.com/pdf/InsideVOFM.pdf
http://saptechsolutions.com/pdf/VOFMFormulaRoutines.pdf (althouth it's for SD, pricing procedure in SD (tcode V/08) and in MM (M/08) are the same.
I hope this helps you.
Regards,
Eduardo

Vendor consignment issue price determined by Customer

hi all expert,
i have the following business requirement.
we have vendor consignment stock. the consumption price for the vendor is based by the customer which we are selling to.
i have configured stock determination, movement type 601K is used for sales order outbound delivery. it picks up the info record price of the vendor directly.
however, the info record doesn't not have customer information. therefore i have tried to create a new access sequence table 817 copied from standard table 17. field KUNNR is added as following:
LIFNR     KOMK     LIFNR     Vendor
MATNR     KOMP     MATNR     Material
EKORG     KOMK     EKORG     Purch. Org
WERKS     KOMP     WERKS     Plant
ESOKZ     KOMP     ESOKZ     Info record cat.
KUNNR     KOMK     KUNNR     Sold-to party
corresponding condition record is also been maintained.
any chance that this access sequence is being run by the standard system when the price determination happen during the PGI for sales order?
do i need to activate any user-exit for this business requirement?
anything that i have missed?
i have also activated the customer field in MB1B 411K movment type. hoping that price determination also take this customized access seq. to determine the price when moving K-stock to own stock.
many thanks!
Matthew

We have designed a solution that allows the vendor consignment price to be discounted based on the Customer we are selling to. Although this is an old thread, I wanted to post in case it is of benefit to others in the future.
In summary, we created a new pricing condition table that includes Customer (KUNNR). In a user exit that is available in the pricing routine for movement 411K, we retrieve the sold-to customer number. In our case, we do this only when picking an outbound delivery. Our business rule is that consignment stock is automatically moved to unrestricted stock at time of picking and we have already automated the 411K movement via our custom RF picking solution (by calling HU_CREATE_GOODS_MOVEMENT). Since we know the delivery line we are picking, we can get the sold-to customer. We are HU managed and already have our own ZHUMO transaction (a copy of HUMO) that we could modify so the user can optionally enter Customer when manually executing 411K for an HU, which would execute the same pricing user exit described below - still determining business rules for HUMO piece.
Details...
Passing Customer Number to Pricing:
1. At time of picking with custom RF transaction, call function module HU_CREATE_GOODS_MOVEMENT to execute 411K movement.
2. Extend User Exit EMM115 to get the Customer number (from delivery) and Vendor at time of 411K and pass it to the pricing procedure.
Pricing Procedure - Create new Condition Table, Condition Type, and Access Sequence:
When 411 K movement is posted, the system will grab the info record pricing (maintained in MEK1) for pricing condition PB00 from Pricing Procedure ZM0000 - access 0002, and now also grabs our new pricing condition - access ZCPD, if conditions are met as described below:
- Append u201CField Catalog (Pricing Purchasing)u201D - ABAP programmer adds Customer (KUNNR) representing Sold-to in the purchasing catalog
   - Create New Condition Table (ex: u201C514u201D) with the following fields:
      1. Sold-to Customer (KUNNR)
      2. Vendor (LIFNR)
      3. Material (MATNR)
      4. Plant (WERKS)
- Create new Access Sequence ZCPD and attach the new condition table
- Add Access Sequence ZCPD to new Pricing Condition ZCPD - Consignment Discount %
- Modify ZM0000 Pricing procedure (Calculation Schema) to access ZCPD.
Maintain New ZCPD Condition Record:
- Once Condition Table has been set up and associated to new Pricing Condition ZCPD, a condition record will need to be maintained in MEK1. The condition record will house the specific combination of Material / Plant / Vendor and the line items will contain the Customer # & Discount %.

Price condition - Price determination analysis

Similar Messages

Maybe you are looking for