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

Similar Messages

TS1702 I don't understand how the report a problem process works

I was advised by an app support team member that I need to report a problem on their app to get my money refunded. The purchase was an in-app purchase for an upgrade to MVP in the Mapmyride app.The mapmyride support said that thre is a bug in their app tha will not allow such in-app upgrade. I went to my itunes account and picked the report a problem button and nothing happened. I expected it to go farther to ask me what the problem was and there was nothing. Is there more for me to do to get my money refunded for this purchase? my purchase was on 3/28 in the mapmyride app. Thankyou.

There are two ways in which drop zones are available in the Keynote title template. What Luis has shown you is the normal way in which a title placed over a clip shows you the original clip with the title text. That is called a Final Cut placeholder type of drop zone. Keynote also offers a drop zone to be used as a background choice instead of a gradient or solid as you see in Luis's post. This makes a very nice title effect as you can use any clip for that background. That is what I thought you were refering to when you you said drop zone. Keynote is one of the nicer titles we have available in FCP because of this feature. Glad you got it sorted out.

How the stock determination process works

Hi All
Can any one tell me how the stock determination process works in inventory management?
if possible give me the steps involved in stock determination process .
Regards
M S K

Hi
i hope this helps
http://help.sap.com/saphelp_47x200/helpdata/en/d8/2f3746996611d1b5480000e82de955/frameset.htm
regards
maniraj

How to find out what is the purchase price keyed in Initial Quantity

Dear Experts,
The stock valuation is Standard Costing.
Before this, someone else keyed in initial quantity and the purchase price in the Initial Quantities module.
Now when I issued a PO to a vendor (price list tagged with Last Purchase Price), the price shown is different.
How do I find out if the price keyed in initial quantity is correct or not? Any tables I can refer to?
I tried to track from the Inventory Posting List and the smartlink only bring me to the journal entry for the initial quantity posting. I don't have the details like item no., qty, price.\
Thanks in advance.

Hi Joyce,
Go to Inventory->Inventory transactions->Initial Quantities, Inventory Tracking, and Inventory Posting. Open Inventory Posting Tab and select your price list and items if you want or check you can see there Item quantity and old price also price list wise.
Thanks
Sachin

How do I stop Mac App Store apps listing as "Accept" rather than the purchase price?

Hi there,
I'm attempting to buy iPhoto '11 from the Mac App Store but it lists as "Accept" rather than the purchase price.
When I click on Accept a message pops up saying "These apps cannot be accepted by your Apple ID: These apps were already assigned to another Apple ID, and they will be available in that Apple ID's Purchases list. If you don't have access to that Apple ID and want to receive future updates, you will need to purchase the applications."
The pop-up gives the option to hit OK and there are no other buttons.
iPhoto '11 is not in my purchases list. I have never bought it before. I am using a second hand Mac and I suspect the previous owner may have downloaded iPhoto but it is no longer installed anywhere on the system and I am the sole user of it. There are no other accounts on this Mac and it looks like it was reformatted back to scratch before I bought it.
The problem is I cannot find any way to reset the "Accept" option so I can actually purchase the App.
Does anyone know how to fix this issue?

i also am having this EXACT same problem and alot of others seem to be too? i wonder what is going on here! if anyone from apple reads this, maybe it is something you can look into? My mac did not come with a start up disk and i accidently deleted the iphoto app... i have 2 apple I.Ds but i dont use the one originally registered. i am aware i will have to buy the app again in this case so please let me buy iPhoto please! and thanks!

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

How the right price picking at the time of creating P.Order?

Hai Experts,
I have a doubt when creating P.order how the right price is picking?Pls sugest me in detail.But i have an idea through Pricing procedure for this explain me in detail.
Thanks to all in advance

HI,
The primary job of a pricing procedure is to define a group of condition types in a particular sequence. The pricing procedure also determines:
Which sub-totals appear during pricing
To what extent pricing can be processed manually
Which method the system uses to calculate percentage discounts and surcharges
Which requirements for a particular condition type must be fulfilled before the system takes the condition into account
The term pricing is used broadly to describe the calculation of prices (for external use by customers or vendors) and costs (for internal purposes, such as cost accounting). Conditions represent a set of circumstances that apply when a price is calculated.
The condition technique refers to the method by which the system determines prices from information stored in condition records.
In MM module, pricing procedure is used during RFQ and PO creation. Total value of material based on all addition and subtraction like discount, surcharge, tax, freight, etc. In this we are defining pricing procedure and linking to vendor and purchase department through the virtual schemas.
Following steps for pricing procedure as,
1. Define conditions.
2. Define pricing procedure.
3. Define virtual purchase organization and vendor.
4. Info Record.
Customization for Pricing Procedure :
1. Definition of Conditions :
/NMEK0-condition typeu2026condition types- definition (define for basic price, net price, discount, surcharge, tax etc.)
2. Defining pricing procedure :
/NMEK0- calculation schema-calculation schemasu2014New entries (Define procedure and put the conditions like formula so that final price will be net price / total value as per company requirement)
3. Linking pricing procedure to independent condition types.
/NMEK0-condition typeu2026condition types- definition for position for defined conditions (Enter the defined pricing procedure in the each independent conditions u201CPricing Procedureu201D box)
4. Defining Schema group for Vendor :
/NMEK0- calculation schema-schema groupsu2014vendoru2014New Entries.
5. Defining Schema group for Purchase Organization--- New entries.
/NMEK0- calculation schema- schema groups---- purchasing organization--- new entries.
6. Linking Virtual Purchase Organization to actual Purchase Organization.
/NMEK0- calculation schema- schema groups----- Assign P.Org. (in actual P.Org, enter virtual P.Org)
7. Linking Pricing procedure to virtual P.Org and virtual vendor :
/NMEK0- calculation schema- Determine Schema--- -Standard --- New entries (Enter virtual schema and P.Org. along with pricing procedure)
8. Linking virtual vendor to actual vendor-- /NXK02 then enter schema group vendor in Purchasing Data )
9. Info Records (/NME11)---- click on u201CPurch. Org. data1u201D and enter condition types and pricing procedure
What are the steps in pricing determination in MM? Condition, Access sequence and schema.
In the SAP MM Pricing is more important. Just yesterday I have completed the Pricing as I am doing the SAPMM now. I can give some light on this Topic, not 100%. After 2 days definitely some more I can share.
The Basic thing is Condition Technique. In which there are
1. Access Sequence 2. Condition Record 3. Condition Type 4. Condition Table.
A Access Sequence access a Condition Record of a Condition Type in a Condition Table is a Condition Technique.This is a simple logic
Here the Condition Type is very important like PB00, PBXX,RA01 etc.
In the background every Condition Type has its own defition means the purpose of the Condition Type like, is it for Pricing or Percentage, Quntity base, Accrual Feilds etc is to be defined to work this functions.
Normally we use the existing ones without any risk. But some cases, we have to Create a New Condition Types as per the organisation requirement.
The Pricing Schema is useful to minimise condition types while mention prices for Vendor on the basis of Pricing Schema which we defined according to organisation requirement.
The Pricing Schema means the calculations procedure of Condition Type.
Ex. RA01 - Discoount % is caclulated on PB00 - Gross Price means
RA01 is based on PB00 like that we have to define in the Pricing Schema
which makes easy to use in realtime.
Here PB00 has the Access Sequence - 0002.
But RA01 does not have the Access Sequence.Why because it is a dependent on PB00. But both are Condition Types.
In the system, by default some standard Scheme will be there at Vendor Schema Group in the Vendor Master Screen means the standard one is assigned which is very lengthy which may fullfil our requirement. But some cases which may not fullfil our requirement, in such we have to define.
For the configuration, I may not able to explain properly through here but will give some Idea.
Configuration: SPRO-IMG-Material Management- Purchasing- Conditions-Define Price Deternmination Process
1. Define Access Sequence
2. Define Condition Type
3. Defince Calculation Schema:- Here you have to define the Schema
Define Schema group
1. Define Schema Group vendor
2. Define Pricing Schema group
3. Schema group for Purchase Organisation
4. Assign Schema group to Purchase Organisation
Define Schema determination
1.define calculation schema for Standard purchase organisation
After completion of the Schema Group, we have to assign it to Vendors.
Then whenever we use any transaction with this Vendor, the concerned Schema will work as configured by us.
I think this will help you. Actually the Pricing is a vast. Becuase each Condition have its own importance and each Access Sequence have its own importance. So you need not bother about this. First you learn how to define the Calculation Schema through the above.
Here we can create many Calculation Schemas which can assign one schema to Local vendors
another schema to out side vendor one more schema to foreign vendors like that we can classify.
Definitely it will help you something.
Regards,
Deepak.

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

Purchase Price Determination in VKP5

Hi,
For Determining Sales Pricing Procedure, we assign Pricing Procedure in Pricing Type and Pricing Type is assigned to Sales Org and DChn.
However, I am not sure how Purchase Price Procedure is determined in VKP5. We do not enter purchase org/Group etc in VKP5 screen and hence not sure how the system determines Pricing Procedure for Purchasing.
Any Pointers will be appriciated.
Many Thanks!

Hi ,
In VKP5 calculation,Purchase price Schema is pulled from Purchase price determination sequence.
In PP Determination sequence we can give PP schema based on PP determination type.
If the PP type is A,system will fetch the PP Schema from Standard schema maintained in MM.
Regards,
Krish

CST and VAT amount (non deductible) is debiting in the purchase price

Hi
          1)     We are maintaining standard price as price index
          2)     Pricing procedure as TAXINJ
          3)     While GR the CST and VAT amount (non deductible) is debiting in the purchase price
                 variance, and credit in the GR/IR
          4)     Which has to debit in the raw material account
          5)     Is there is any notes for the this
          6)     or any other solution plz send your reply

HI..
it is not done in OBq3
See in OBQ3..you define Pricing procedure.against pricing Procudure you will give the account Key against the condition type in the Pricing Procedure.
For this Account Key ..you Define it as Detuctable or not in OBCN.
so it determines whether to add to raw material account or not..
but see in early post which is also valid even if you have define the sdame in OBCN.
Hope so it helps
Regards
Anjanna

Newstand in app purchase made in DPS is appearing in store with "error" below instead of the purchase price/download.

Newstand in app purchase made in DPS is appearing in store with "error" below instead of the purchase price/download. Not sure why, as the product ID number matches up between itunesconnect and DPS. Any idea how to fix?

same here. this thread suggest that it's carrier related issue
http://supportforums.blackberry.com/t5/Payment-Service/Error-quot-The-Item-you-requested-is-invalid-...
Twitter: @gyubok

Custom defined FM for purchase price determination

Hi all,
can anybody help me with the problem below..
In IS-retail im assigning a custom defined function module for purchase price determination (MM42 -> sales view -> PP det. seq - 06).
example FM for which is WV_EXAMPLE_01.
but in the import parameter (structure KALP) im not getting the vendor number eventhough it is specified in the screen..
I need vendor number along with material(which im getting) to calculate purchase price..
Can anyone tell me wat the problem is and a solution for it.
Thanks in advance.

Hi ,
In VKP5 calculation,Purchase price Schema is pulled from Purchase price determination sequence.
In PP Determination sequence we can give PP schema based on PP determination type.
If the PP type is A,system will fetch the PP Schema from Standard schema maintained in MM.
Regards,
Krish

How the IVI New Session.vi works with the ivi.ini?

Hi,all
Does anyone know how the IVI New Session.vi works with the configuration file ivi.ini?
And when the ivi application running, how the ivi calss driver refers to the right specific instrument drivers without changeing the program?
Thanks,
njzhw
人的生命是有限的，但知识是无限的！
南京众知维测试技术有限公司

Which VI or function are you referring to? There is neither an "IVI New Session.vi", nor a corresponding "Ivi_NewSession" function in C.
The Ivi Class Drivers determine which specific driver to use at run-time, by looking up the resource descriptor (a Logical Name, or Virtual Instrument) and determining the associated Instrument Driver. That configuration information is settable by the user through MAX (Measurement and Automation Explorer).
--Bankim
Bankim Tejani
National Instruments

CST amount is debit in the purchase price variance

Hi
We are maintaining std in the materials master
and price procedure as taxinj
While doing migo, the CST amount is debit in the purchase price variance and credit in the GR/IR RM,
We need to debit the CST amount in the in the Raw material account
what are the settings i need to carry out Plz give suitable suggestions.
in tax code we are not maintining any G/L account for the CST
Edited by: K. Raghuram on May 19, 2009 12:48 PM
Edited by: K. Raghuram on May 19, 2009 1:02 PM

Hi Raghuram,
I think,the only possiblity for this to happen is due to the standard Price in the Mterial Mater you are using.
Means in the Material Master ,the Price key is a standard pricing.
So ,when ever you do a GRN ,the PO value will go and hit the Material account upto to the Standard price maintained in the material Master.
if the amount is more than it ,then amount difference will hit the Price variance account.
so in your case ,the CST is inventorised one ,i believe.. so that is the reason it is behaving so.
if there is somethig else required.provide a clear insight of the Problem.
Regards
Anjanna

Capture the purchase price during sales order creation

Hi,
User wanted to capture the item purchase price when a sales order is raised.
Currently, the sales order capture the VPRS whcih is coming from the material valuation (MAP) price.
Is there a standard condition type that will captured the purchase price in the PIR record or the PP condition?
Thanks

Hi
As far as i know it is not possible to fetch the purchase price in sales order.
May be you can define an another condition type asa statistical and maintain the condition records for that. But it will be a tedious job for maintaining all the things.
regards
Prashanth

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

Similar Messages

Maybe you are looking for