Pricing determination...

Hai ,
I have maintained 3 pricing procedure..
Now i am going to cteate the PO. How the system knows for required
Pricing procedure in those three..Which one the po will pick ?
b)Supplemetary Pricing Procedure ( Cal Schema) necessary?
c) How the Linking the GL accounts(a/c deter) in Condition type ?
Thanks
Roshan

Hi Roshan,
The pricing procedure defines the conditions permitted for a <b>document and</b> the sequence in which the system takes these conditions into account during pricing.
A standard pricing procedure is defined in the standard SAP system. It contains conditions most commonly used. These include material prices, discounts, and surcharges, such as freight, or tax.
This concept is referred to in the Sales and Distribution (SD) area as a pricing procedure.
In the calculation schema (pricing procedure), you specify which condition types are to be taken into account in which sequence.
In the price (or cost) determination process, the SAP System automatically determines which calculation schema is valid for a business transaction and takes into account, one after another, the condition types it contains.
You assign purchasing transactions and processes to a calculation schema; that is, you specify the cases in which a certain schema is used.
For standard purchase orders
(depending on the schema group of the vendor and the purchasing organization)
For stock transport orders
(depending on the supplying plant, the document type and the schema group of the purchasing organization
To enable the system to find the relevant account for provisions (for accrued delivery costs or miscellaneous provisions, for example), you must assign a transaction/event (internal processing) key to each condition type that is relevant to provisions in the step Define Calculation Schema.
Calculation schemas may also be referred to as "pricing procedures.
Define schema groups for purchasing organizations and vendors.
Assign schema groups to your purchasing organizations.
You assign vendors to schema groups in the relevant vendor master records.
For the G/l accounts i have already answered to your additional query.
regards
kp
Please award points if you find the solution in it .

Similar Messages

Pricing determination for free goods

Hi Experts,
Please help me for the following issue:
This is with regarding pricing determination. I have a requirement that, for each 10 quantities of Material ABC sold out, 3 quantities of same material ABC is given free. In VBN1, I have set the requirements as such.
Material ABC has Basic discount of 20%, Excise duties and VAT.
While entering 10 quantities in 1st line item of Sale order, automatically 2nd line item generates with 3 quantities of the Same material. Item category for 2nd line items is TANN:
ORNORM_______+ TAN = TANN.
In VOV7, have defined Pricing as "B =Pricing for free goods(100% discount)" for TANN. The issue here is,
For the 2nd line item (Free goods), negative values and Tax values are getting updated because system calculates BED, VAT, 20% discount for both line items in the sale order.
When I changed the Pricing as Blank (No Pricing) in TANN item category. 2nd line item also (i.e free goods) behaves like 1st line item (Chargeable). I want the system to calculate VAT, BED, 20% discount only for the chargeable item not for free goods.
Please suggest.
Thanks in advance.

Hi Experts,
Thank you for your valuable time.
R100 condition type is already being used before taxes and discount.
System calculation as below:
1st line item (Chargeable): For 10 quantities
DNP -
5000
Discount 4% -
200 (Negative)
BED 10.3% -
468.6
Vat 13.5%----
648
Total----{4800 + 468 (BED) + 648 (Vat)}
2nd Line item (Free goods): For 3 Quantities
DNP----
1500
R100 Discount----1500 (Negative) = Value is getting zero here itself {DNP - R100 (1500 - 1500)}
Discount 4%----
60 (Negative)
BED 10.3%----
140
Vat 13.5%----
194.4
Total----{60(Negative) + 140(BED) + 194.4 (Vat)}
For the 2nd line item, negative 60 value, BED and Vat values are being calculated.
Hope that I have specified my requirement clearly, can you please let me know what should be done, if there should be no 4% discount, BED and Vat values for 2nd line item (Free goods).
Thank you,
Vijay N

Problem in pricing determination in VA03

Hi All,
I am facing in pricing determination. There is inconsistency problem for pricing determination. For one of condition type ZCN1, we have maintained the price in condition record(VK11) but even after than the condition record does not get copied in the order. This is happening for some of the orders and not for all orders and not for all items for one order.
In VA03 T.code
E.g
Sales order:30000123 line item 15
The pricing date is 29.04.2007, but pricing in ZCN1 condition type could not be determined. In the pricing analysis screen it shows the confition record for the condition type ZCN1 but displays ''condition record found but not set'' we cheched for other orders/ line items this price was successfully copied. we are having such inconsistencies often.
Can any body suggest some solution.
Regads ,
Geetha

If it's a standard configuration that is not working, I would suggest to move this question to SD forum. Otherwise, if you have any user exits in pricing determination, the problem might be there. If it's a small piece of code, please post it here for a review.
Also in the pricing condition analysis take a look at what keys are used for the price determination. Often the problem is that the keys are incorrectly populated in the program.

FAQ:Pricing determination的基本知识(3)

这是关于Pricing determination基本功能介绍的最后一贴。帖子里涉及到的note，请大家参阅附件。
之后的下一个帖子我准备说说在日常使用pricing功能出现异常时一些简单的自查方法。
<Group conditions>
Use of group conditions
Compensation of rounding differences for percentage and fix amount conditions. Example:
Item 10 16% MWST based on 100,90 DEM = 16,14 DEM
Item 20 16% MWST based on 100,90 DEM = 16,14 DEM
but as u201Ereal tax baseu201C the total value must be used (legal requirement):
16% of 201,80 = 32,29 DEM !!!
cumluation of scale base value. E.g. 10 apples and 5 lemons are sold to a customer but there is a discount based on the total amount of ordered fruits (15 pieces)
split functionality: condition values or rates entered on header level are distributed to items. Example: Split a value of 100 DEM to 100 items (= 1 DEM set for each item).
Handling of structure conditions (KUMU). Example: Price is set on lower level item but the main item is relevant for billing
The processing of group conditions is performance critical, in standard there are only a few group conditions, e.g. MWST, SKTV
<Condition exclusion>
There are two possibilities to achieve exclusion
Exclusion indicator KZNEP
Is set in the condition record or in the condition type (customizing)
Restrictions: it is not possible that a condition will exclude itself and if a condition is entered manually exclusion will not take place
Exclusion with KZNEP is achieved by using requirements (e.g. standard requirement u201A2u2018). Review note 92090, 41490
Exclusion groups
Have to be setup in customizing, IMG: Sales and Distribution -> Basic Functions -> Pricing -> Condition Exclusion
Flexible: can be set up for groups of conditions or individual condition types or records
Rules are used to judge which conditions are excluded, e.g. best price
Restrictions: it is not possible to use different rules in parallel, zero values of conditions are not used for exclusion in standard (note 39641)
<T-cd:VOFM>
Maintenance for requirements and formulas
Requirements
Formulas for
Scale base
Condition base value
Condition Value
Structure of group key
Copying requirements
Data transfer routine
Requirements and formulas are entered in pricing procedure
Customer name space:
Group key routines 50-99
All others 600-999
VOFM problems in 46C should be fixed by note 385067 (SP 16)
<Pricing copy>
If Document A is created with reference to document B
call of PRICING_COPY using
DOCUMENT_NUMBER_FROM - to read the pricing result of the origin document
DOCUMENT_NUMBER_TO - to assign the conditions to the right document (e.g. cancellation)
MODE - pricing type: rough filter, to figure out which conditions should be copied Normally given by the customizing of copy control.
SOURCE - direct source. Means that a condition should be directly taken from order, delivery, freight calculation etc.
SOURCE_KOMV - if PRICING_COPY should not read the data stored in KONV the calling application has the possibity to pass in condition information directly
TKOMV - includes conditions which survive the check and filter mechanism of PRICING_COPY. This table later on is used for the PRICING call.
Conditions are always copied on item level. Any header and group condition property is lost.

Dear Lakshman Iyer,
Thank you for your answer. It does not work, maybe due to
wrong setup. What do I wrong?
Define Condition Exclusion Groups
I created 1 excl. group = 10.
Assignment of Condition Exclusion <-> Condition Types
Assigend 3 condition types to 10.
Assignment of Condition Exclusion <-> Calculation Schema
entered:
Snr. 1 then group A and then group 10.
A is the condition excl. procedure.
But If I create a PO all three freight conditions are available.
And the last (with the access sequence is filled with 5%).
Then I enter the manual condition type with 100 Euro. And
now I have 2 conditions filled.
The goal is: if I fill manually the condition the condition
with the percentage should not be filled anymore.
Best regareds,
Eric.
Entered grou

How will i configure pricing determination

how will i configure pricing determination.....

Hi,
Pricing determination based on condition technique
formula of pricing determination is
SalesorganiztionDCdivisoncustomer pricing procedureDocument pricing procedure+ Pricing procudure
Go to img-Sales and distribution-Basicfunctions-Pricing- pricing procedure detrmination
First define ur document pricing procedure in ova8
Then define ur customer pricing procedure in customer master sales tab
then go to basic functions define table assign table to access sequence again accesequence assign to condition type place the condition type in the pricing procedure.
Then assign pricing procedure to sales areDPPCPP
Maintain condition record in vk11 for pr00 condition tupe
Then pricing procedure automatically determines.
Regards,
Murthy V.N

Please explain me about pricing determination procedure in SAP SD ?

Could you please explain me about the pricing determination procedure in SAP SD ?
Edited by: Piruthiviraja on Aug 18, 2009 8:00 AM

Hello,
Please go through the following
An Overview of Determination & Configuration of Pricing Procedure is as follows:
In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
In SD, the steps to configure Pricing procedure are as under:
Step 1:
Condition table: If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG u2013> Sales & Distribution u2013> Basic Function u2013> Pricing Control u2013> Condition Table (select the required fields combination, which will store condition record).
Step 2:
Access Sequence: If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG u2013> Sales & Distribution u2013> Basic Function u2013> Pricing Control u2013> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
Step 3:
Condition Type: If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG u2013> Sales & Distribution u2013> Basic Function u2013> Pricing Control u2013> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.
Step 4:
a. Pricing Procedure: It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG -> Sales & Distribution u2013> Basic Function u2013> Pricing Control u2013> Pricing Procedure -> Maintain Pricing Procedure.
b. Pricing Procedure: After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG -> Sales & Distribution u2013> Basic Function u2013> Pricing Control u2013> Pricing Procedure -> Determine Pricing Procedure.
Step 5:
Condition record: Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc.
SANTOSH

Campaign Pricing Determination

Hi,
Does anyone knows if Campaign Determination for Pricing is only for Campaign for category Trade Promotion only ? So how about Campaigns ? How does Campaign Determination for Pricing work ? Using Events?
Regards,
Niversphere.

hi
for that you need to get through the difference between the campaign and TP,the only thing that is different in Tp is that it is for particular account type,due to this particular property of Tp the campaign determination is triggered for TP by default
but you can trigger campaign also by setting your condition types,then assocate those condition with the access sequence,the system will look through the sequence for the condition type,and based on the condition you have maintained the campaign is triggered.
the condition table by default fill the value for Trade Promition and when you do campaign determiantion the system pick the value from the table and that valuse is for TP only,that is the reason for Tp determination.
but as i said you can determine campaign by the above said way of mine.
guess it will help you
i will advise you also study the pricing determination procedure to get better hold of the concept
best bregards
ashish

PRICING DETERMINATION WITHOUT CONDITION RECORD

HI ALL,
can anybody explain me when you creating one purchase order if there no condition record for this material (for an example info record) how the price can automatically picked up and sit into the net price field.
What is big-pricing procedure (RM0000)?.
PLEASE EXPLAIN ME IN DETAILS WITH A PROPER EXAMPLE.

Hi
There is a condition type P101 to adopt the price from the Material master. Apart from this the Price is determined based on the info update indicator, this will creat an info recoprd automatically, if you see the inforecord then the price will not be present as this info record has not been manully created.
RM0000 is the Standard Pricing procedure given by SAP.
Determination of Purchase Price (Example)
Purchasing creates a PO for 100 swivel chairs at $250 each, to be supplied by vendor Miller Co. No outline purchase agreement exists with this vendor. The agreed condition (discount of $10 granted on each chair purchased) is stored in an info record. No general price stipulations apply.
The system carries out the following price determination process:
Assignment of price calculation schema:
RM0000
Search for condition records belonging to the condition types listed in the calculation schema:
The system searches only for condition records belonging to condition types that are marked in the schema as non-manual.
Condition type PB00
Determination of access sequence
0002
Accesses within access sequence 0002
Accessing of condition table 068 (plant-specific agreement item) is not carried out
Accessing of 016 (contract item) is not carried out.
Table 017 (info record) is accessed and the condition record is found.
Condition records belonging to the other condition types are then sought.
In the example, no further condition records are found because condition type RB00 (discount) is a supplementary condition belonging to condition type PB00 and thus has no access sequence of its own.
The system then suggests a price of $240 per chair in the purchase order. The buyer can then enter further conditions (covering delivery costs, for example).
Hope this clears your doubts.
Please go through the link for more details
http://help.sap.com/saphelp_erp2004/helpdata/EN/75/ee1fa755c811d189900000e8322d00/frameset.htm
Thanks & Regards
Kishore

PROBLEM IN PRICEING DETERMINATION

HI, WHEN WE R DOING PRICEING PROCEDURE DETERMINATION(OVKK), THAT TIME WE R USEING BASE PRICE CONDITION TYPE(PR00). MY POINT IS WHY WE R USEING BASE PRICE CONDITION TYPE.IF I WL USE CUSTOMER DISCOUNT(K007) IS THERE ANY PROBLEM.

Dear Mohan,
As per my understanding about your thread,
We can enter any condition type instead of the base price.
What ever the condition type you maintain there it will reflect in the sales order at item screen next to the plant and batch there you can change or enter the value again for that condition type with out going to conditions tab.
I think this is only use of this entry no other specifications
i hope it will help you
Regards,
Murali.
Edited by: Murali Mohan.T on Mar 6, 2008 6:32 AM

New pricing Determined when a material is swapped

We have a scenario where a Item already priced Eg: 1012 might be later replaced by 1013 in VA02 doing this means the item category will be re-determined & re-priced .
Is there any way to keep the old pricing intact ( from material 1012) even though a new material substitution is made
Please advise
Thx,
Vinay

I think we found a UE to accomodate this requirement:
USEREXIT_NEW_PRICING_VBAP

While doing pricing determination procedure in ovvkk

while doing pricing procedure process i.e., creating condition tables, accseques, types and finally assigning in ovkk, is there a necessary to declare the condition type or it directly takes it, another thing do we require a condition table for PR00 also.

write-up on pricing procedure:
Check the Pricing Procedure:
In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
In SD, the steps to configure Pricing procedure are as under:
Step 1:
Condition table (T.Code: V/04): If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).
Step 2:
Access Sequence (T.Code: V/07): If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
Step 3:
Condition Type (T.Code: V/06): If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.
Step 4:
a. Pricing Procedure (T.Code: V/08): It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.
b. Pricing Procedure (T.Code: VOK0): After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.
5. Condition record (T.Code: VK11 / VK12): Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc. Condition Record is maintained in T.Code: VK11 / VK12, which are captured in Sales Order & Billing.
Also check document pricing procedure in Sales Document Type (T.Code: VOV8 - Sales order Type, VOFA: Billing Type (If Required)), customer pricing procedure in Customer Master Data (T.Code: XD02), ... are in place.
Regards,
Rajesh Banka
Reward suitable points.
How to give points: Mark your thread as a question while creating it. In the answers you get, you can assign the points by clicking on the stars to the left. You also get a point yourself for rewarding (one per thread).

Pricing determination in SMI

We will be setting up suppliers to use SMI. In our ECC system, we will have purchase contracts by plant, but PIRs by Purchase Org (so a PIR can span multiple plants).
When a supplier creates a Replenishment Order in SNC, how will the resulting PO determine pricing? Will it look at the PIR, or will it pull the price from the contract?

Hi Sott,
System will pick the price from contract if you have created transportation lane by CIFing the Contract.(ECC to SNC)
Regards,
Nikhil

Pricing determination not possible after updateing customer master data

Hi Gurus,
We are trying to set up CRM 7.0 standard sales scenario to make it to work. We picked a BP, a sold-to party which was loaded from ECC. Changed the role to sold-to party, and added the sales area data that we have in CRM. Added currency "CAD" to the "billing' tab as well. However, when we create a standard sales order (TA), we picked this BP as sold-to, and also picked the right product, we also made sure the pricing procedure determination config is done. However, system keeps giving the error "item category cannot be determined", and the "currency" and "pricing procedure" fields in the header section remain blank.
It seems to us that system needs some sort of refresh to "see" the new configuration data. Don't know why. I remember in other projects we did, we had to wait overnight to see some pricing/org. data updated.
Can someone advise how to fix it without having to wait till the next day?
Many thanks!
Jerry

About buffer problem - yes, organizational data must be refresh if they are changed. You can clear buffers with /$sync.
About your error "item category cannot be determined", i would say that you are missing the customazing. check settings under spro>crm>transactions>basic settings>define item category determination (and also 3 options before that one).

Pricing determination of MIGO (goods receipt)

How is 'Amount in LC' field in the tab 'Quantity' of MIGO (goods receipt) determined by SAP?
To my understanding, 'Amount in LC' is determined by the conditions, but I don't have a clear understanding on this process.
Appreciate if anyone can shrow me some idea on this.
Points will be assigned! Thank you.

thank you very much for your answer, srinivas kona,
However this answer does not help much on our situation below.
Much appreciate your help in advance.
In the PO history of 1st line item, we posted the following material documents.
1. wrongly post MIGO as follows.
Movement Type = 101
quantity = 400;
'amount in LC' = $ 400
2. Now we reversed material doc in step 1 using MIGO cancellation, and we seccessfully cancel the wrong material document.
However we are driven crazy by SAP because the system post a new material doc with wrong 'amount in LC' again!
Movement Type = 102
quantity = - 400;
'amount in LC' = $ - 500
'amount in LC' should be $ - 400 to reverse the material doc in Step 1.....how come system posted a wrong 'amount in LC' in cancellation document....

Pricing determination for services purchase order

Hi All,
Please provide the configuration and assignment steps involved for service Purchase orders.
Regards
Vijay

Hi Vijay
Please check the following links,
Service Pricing Conditions
Hope Help U..
Regards
Vikrant

Pricing determination...

Similar Messages

Maybe you are looking for