Price determination category

HI
we create purchase order number 3 or 4 months before delivery.
But we negociate with our suppliers that we have to buy the goods with
the price at the delivery date.
The concerned purchase order numbers are created with price date
category "GR date" under folder condition control.
In my above mentioned example the system will create a price difference
payment block, because the system compares the PO Net price with the
invoice price.
Should the system compare for the purchase order numbers which are
created with condition "GR date" the valid info record price at the GR
date with the invoice price?
Regards
GP

Hi,
Why can not use "Pricing Data Control " as GR date in vendor master in Purcahsing data view in vendor master which you used in craetion of PO(ME21N). Pricing Data Control is used for price determination purposes of material with various criteria's.
Regards,
Biju K

Similar Messages

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 date category problem

Hi.
while Scheduling Agreement without any reference the price determination date category set as "5" "GR Date" by default. But we want to use the price date category 2 "Delivery date" but it is not updated in SA. Even if in vendor master and purchase info record Price date category is 2 "Delivery Date".
And also field of price date category is non editable.
Pls help
Dhiraj Bhaskar

Hi
Check the Customizing for the document type of the scheduling agreement (spro->MM>purchasing--->scheduling agreement ---> define document types).A price determination only occurs during the creation of the scheduling agreement if the 'time-dependent conditions' indicator is not set.
If you want 'time-dependent conditions' indicator is set then it will always be 5. and you cannot change. price date category is editable only for time independent conditions. Thats why it is always editable in PO.
Regards
Antony

How to update open PO price based on Price date category in contract?

I've created a contract/ outline agreement with Price date category as '2'- Delivery date. (Path is Item details> More Functions> Additional Data). This means that PO price should be determined based on its delivery date.
In contract, there are two date ranges for conditions. PO creation and delivery date falls under different ranges. Now, the open PO price is getting updated based on PO creation date but not on delivery date. We have tried using MASS transaction for this.
Can someone suggest any solution?

The Price Date category field was visible in contract but not in our PO. Due to this, MEMASSPO was not updating the field value and we were changing the value to '2' manually by debugger. Hence some table updates were missing and causing the whole issue.
The solution is to change the screen layout for PO. If Price date cat field is hidden, then you need to make it optional entry in SPRO- Purchase Order - Define screen layout at document level--> Quantity and Price for ME21N , ME22, ME22N and for field selection key assigned to PO document type.
This field will be available in ME22N- Condition Control TAB.
Regards
Ankita

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,

Purchase Info Record - Price Determination (Pricing) Date Control

Dear Guru,
Can i get some advice here for the "Price Determination (Pricing) Date Control" (Pr. Date. Cat ) setting which is maintain in the Purchase Info Record --> Purchasing Organization Data 1.
Can anyone advice me on the purpose and where is the configuration?
Thank You very much,
Regards,
Chee Wee

Hi
If you maintain Pricing date category in info record then different pricing date can be considered for a certain material supplied by a particular vendor.
If you maintain in the Vendor master then the same price determination date will be considered for all the vendors materials.
For example,
If you want to maintain two pricing for the materials with different periods then you can use the validity periods according to the requirement.
Validity periods,
1. 01.11.2010 to 31.12.2010
2. 01.01.2011 to 31.01.2011
Regards,
BK

MM - Price determination per business types

Hello,
I need to determine multiple price determination for the same material purchased to same vendor.
Indeed, depending on the business type (purchase for production, for trial or for aftersales), one single material can have different price towards the same supplier.
The business type must be set up at purchase order item level, and depending on the business type, a different price must be determined.
Do you know how to proceed? Can the field “sub-item category” be used in the pricing procedure?
Any other idea?
Thank you for your help,
Nathalie

If you want to a single material can contain multiple price..
And all valuation will be as per different price, then the better option will be split valuation.
Here you have to use valuation type for each material which you want to set the different price..
Suppose you want to use price 10 for material which will be purchased, then you can use one valuation type for the material..
And you want to use price 20 for material which will be used for trial, then you can use another valuation type for the material.
Both valuation type can contain different valuation class and different price but material will be only one...
Regards
Dev

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

Error in the price determination procedure in the Delivey NL

Hi Gurus,
I'm working in a project and the customer wants the delivery note with value. Then I have activated the Price determination procedure for the delivery NL ( deliveries to transport material between plants ) and the determination doesn't work correctly, The conditions doesn't appears but if you push "analisys" and you check the conditions PR02 and MWST, the condtions record are determined but not printed in the document.
It print the following message:This message tells you that the condition record exists, but has not been set in the document...
Some ideas?? thanks in advance for your help
Francisco Javier Fernandez

Hello,
Solved, in the customizing, you need check if the price determination procedure for the item category NLN is active, how?? spro>sales>basic functions>pricing>pricing control>define pricing by itgem category.
Check if your item category NLN have "x" Active price determination procedure.
Is nothing related with the reference to a PO, or copy rules...
Best regards,
Francisco Javier Fernandez

Price date category in PIR

Hi gurus,
Could you please let me know the significance of price date category: current date
what is meant by current date, is it the date of posting of GR or IR
If it is the date of GR then what is diff between Price date category GR date and current date

Hi
price date category: Determines which date is to be used for price determination (pricing) purposes.
If you choose the date of goods receipt, for example, a new price will be determined upon the arrival of the goods, causing the item to be revaluated at this time.
current date; this is the date when tou are creating documant.
GR date : this is the date when your are receiving the goods

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

Updating the Price Determination Field in the Material Master (MBEW-MLAST)

I'm doing a material conversion into an existing SAP system and the program to load the materials didn't load a value in the price determination field (MBEW-MLAST). Normally this field is required but because the conversion BAPI doesn't do as much validation as MM01 it was possible to create the record without a value. The field is not open to input when I use MM02, and even though it appears to work, when I do MM17 mass change the field is also not updated. Finally I tried transaction CKMM - Change Material Price Determination for Material Ledger but it required an entry in the Old Price Determination field and it won't let me enter blank.
We've since corrected the program but my problem is that I've converted about 5000 materials without a value in the field meaning the FI guys can't release cost estimates which is causing a bunch of problems for the testing that we want to do in this system. We've taken about 3 weeks to do this conversion so going back and doing it again is a terrible option. Does anybody know a way to get a value into this field other than what I've mentioned above (MM02, MM17, CKMM)?
Suggestions please.

have a look into OSS Note 1491364 - BAdI CKML_SET_VPRSV: Price determination cannot be changed

Override consignment price determination during goods issue process

Hi ALL,
My requirement is that User is asking want to override consignment price determination during
goods issue process. Is there any BADI/User Exit or Enhancement spot which can override the price value and in the
database level during Goods issue.
If yes provide me the enhancement details and where I can implement.
I will very thankful to you all if I get your valuable input.
Regards
Subhasis

Dear Laxman,
Check these links,
https://wiki.sdn.sap.com/wiki/display/ERPLO/Batch+Determination
Automatic batch determination
Re: how to make the batch determination process automatic
Regards
Mangalraj.S

Price determination category

Similar Messages

Maybe you are looking for