Pricing Procedure_100% discount

Dear Sir,
We have required to charge Basic + Excise duty on invoice & -Debit only Basic value to customer-. how to MAP the pricing procedure. we have already defined ZFRE 100% discount condition for Excise duty, but after that Basic & excise duty debit to customer.
Please guide in to the matter.
Regards
BK GAIKWAD

Hello,
In pricing procedure used, check there will be an ACCOUNT KEY assigned against the EXCISE DUTY condition type & mark that as statistical..
Thanks & Regards
JP

Similar Messages

Pricing (header discount) based on VC characteristics

Hi everyone,
We manufacture and sell make-to-order products and use variant configuration to capture the specific characteristics required by the customer. The order quantity we use is EA. However, we wish to price by the square metreage of the product. At item level this is OK because VC can set a pricing variant according to its calculation of the square metreage and this is passed into the pricing conditions.
However, we wish to offer a discount based on the TOTAL square metreage of product within the order that is distributed proportionately across the items in the order.
Has anyone done anything similar?

Devon
1) My suggestion would be to include the threshold by date in a custom Infostructure ( S500+) in flexible planning- MC93.
2) Also activate Infostructure S001 for customer analysis to update synchronously.
3) Now include a Pricing Requirement against the discount condition to compare the value in S001 with SXXX and apply it only when the threshold is crossed.
4) Maintain Discount rate in a (dummy) condition record, but you may need a alt. Cond. Base value formula also.
Hope this helps.

Oracle Pricing- Using Discount Feature

Hi,
I'm Anil Wadhwa and i'm working for Amtrex Hitachi Appliances ltd., Ahmedabad (India). I'm handling the OM Module and I was trying to use the Discount feature availabe in the Oracle Advanced Pricing. As of now we have defined a modifier which we have given the name as a 'Manual discount' and this helps us in changing the unit selling price while doing order entry at the line level. We are not using any qualifiers.
We are trying to explore a feature whereby we would like to give a discount say @10% to the customers who belong to the class 'DLR'. For this I defined a Qualifier by the name of 'Dealer Discount' in the Context I chose Customer and in the attribute I chose 'Customer Class', operator '=' and Value= 'DLR '.
Then I defined a Line Level Modifier where I took a modifier Type as discount and the application method as 'percent' and chose the value as 10. Then I attached the qualifier at both the Line Level and header level.
I defined a new customer at the customer master level and defined the Class as 'DLR'.
Now when I'm doing the order entry the unit selling price which is coming from the price list does not get reduced by 10%, instead the value remains the same.
Can someone in this community who has used this feature of Oracle Advanced Pricing help me out.
I will be highly obliged.
Regards,
Anil Wadhwa

Hello Mr. Ramesh,
Many thanks for your prompt reply and the suggestion you gave. I don't know much about the Build Sourcing Rule concurrent program and for that I'll have to go through the user guide or search in the help section. Well I will do that, meanwhile can I send you a screen shot of the setups I have done at my end so that you can analyse and verify the same at your end. My e-mail ID is [email protected], I will be highly obliged if you can acknowledge my request on this e-mail ID.
I also want to know more about the Incompatibility Groups and Phase Events, in terms of how you have done the setups and how it is to be used at the modifier level.
Regards,
Anil Wadhwa

SD Pricing Requirement - Discount budget

Hi Friends,
We need a solution for discount requiremement scenario to be mapped in SAP SD.
A Discount budget is given to a region which is then allocated to area offices under this region at the descrition of the Regional manager
Ex :- For Region R1 an discount amount of Rs.1000/- is given which is split in to areas such as Area 1 - 500, Area 2 - 300 and Area 3 - 200.
A Master will be created for a combination of Material / Customer / Discount amount
Now when the discount is given in sales orders , the discount gets consumed and this should consider cummulative values of discount amounts of Areas ( A1 + A2 + A3) and validate with the discount amount of Region R1.
Please let me how can this be mapped in Pricing for SD.
Regards
Venkat.

Hi,
The Budget feature is not availble in SD module,
You can carry out enhancement, wile doing enhancement take help of PM,CS & CO consultant help,becauze this feature is available in PM/CS Module.
Kapil

HTML Quoting & Advanced Pricing Integration (Discount Modifiers not working

Hello Gurus,
Customer is using HTML Quoting, we have created Pricing Discount Modifiers in QP.
But these Modifier are not getting applied in HTML Quoting?
Customer is on R12
regards
girish
Edited by: 849679 on Oct 9, 2012 2:24 PM

Verify your setups by going thru' the following presentation.
http://www.ncoaug.org/NCOAUG%20Training%20Day%20Feb%202009/Sundeep%20Sharma%20-%20Integrating%20Advanced%20Pricing%20with%20Purchasing%20in%20Release12.pdf
It is for R12 but most of it is applicable to 11 too.
Hope this helps,
Sandeep Gandhi

Implementing customer's pricing and discounts

Hello, I'm totally new to Weblogic and have a longtime client who has just purchased the Weblogic Commerce Server to put their catalog online. They have both domestic sales and international distributors with a complex discount structure in place. Naturally, they have all sort of currency conversions.
My question to those most familiar with the existing code is what would be the preferred method to implement these changes.
At first glance I'm thinking of creating a new custom tag class which would be used like com.beasys.commerce.ebusiness.catalog.tags.GetPropertyTag to add methods to retrieve the calculated "MSRP" price and currency, which changes depending on the type of customer, and the purchase price, which is discounted by customer. I would then change the cat.tld to use my custom tag class. The custom tag class would call the standard GetPropertyTag to retrieve the base values.
The product/customer pricing would be in custom tables which would be exported from the ERP system and are not part of the Dublin framework.
Does anyone have any other ideas regarding how to implement this type of functionality?

Hi Anirban,
I got your response, but that does not help as I had already verified that setting. That was one of my first checks to make sure that IPC pricing had been triggered. However, now that I have conducted more investigation I have found issues in regards to the lack of condition types in ISA. After review of the logs I found that certain condition tables have not been created and a mismatch of attributes exists. Can anyone comment on their experience of the IPC Dataloader and issues like the ones described when running an initial load for the first time?

In Oracle 11.5.10.2 Advance Pricing, quantity discount in ranges

In Oracle 11.5.10.2 Advance Pricing, we have a requirement. free item promotion based on range of items ordered. Eg: If customer buy 10 qty then 2 free, else, if customer buy 20 qty. then 5 qty free, else, if if customer buy 30 then get 8 qty free. How to achieve in Advance Pricing. Is it possible to achieve a range of free quantities in Advance Pricing?

In Oracle 11.5.10.2 Advance Pricing, we have a requirement. free item promotion based on range of items ordered. Eg: If customer buy 10 qty then 2 free, else, if customer buy 20 qty. then 5 qty free, else, if if customer buy 30 then get 8 qty free. How to achieve in Advance Pricing. Is it possible to achieve a range of free quantities in Advance Pricing?

Pricing - Group Discounts

Hi Everybody,
We have a situation where we need to give a discount of say 10 % if the total qty of all the items is 144 EA and if it is 180 EA we give a discount of say 20%. I can create a condition type which Z001 and flag it as Group Condition and put scales in teh condition records. Everything works fine.
An order comes in as -
Item 10 - qty 120
Item 20 - qty 60.
So condition records pick up and as the total quantity is 180 he gets a discount of 10%. An Order Acknowledgent goes out to the customer and he sees a discount of 10%. Fine till now.
Now due to planning and business reasons after 10 days, we decide not making/selling the item 20 in the sales order. So, we reject it. Now the total quantity is 120. Now, the discount of 10% goes off from the order. The Business requires to keep the same discount applicable if once determined in the order.
In other terms, it is our problem and so we cant remove the discount just becuase we are not selling the item. We do not want to add the discount manually as we might have some 150 orders a day and we cant monitor it.
Any thoughts would be appreciated.
Thanks & Regards,
Vidya

HI Rajesh,
I do agree this is not possible logically and hence am asking ideas from you.
As far as the lines are concerned, we do not delete them. Rather we just reject them. Putting a delivery block might not help me as I have to stop planning of the item. A delivey block might just stop the item from getting delivered but not the planning.
Any ideas?
Thanks & Regards,
Vidya

Query for MM Pricing Procedure & tax Procedure

Hello,
Can someone advice me on following.
I need one Condition in MM Pricing Procedure : Discount should be reduced after Calculation of Excise duty and Taxes on PO.
Discount should not be calculated for Excise Base amont & or Tax (CST /VAT) base amount.
Calculation
Basic :          100
Freight            20
Subtotal        120 (Excise Base)
Excise duty:   30
Subtotal:       150 ( Tax Base)
Tax   @4%       6
Subtotal        156
Discount         10
Total Price     146
My Requirement is how to add Discount at the Place shown above.
Regards,
Manish

Dear Manish,
                    After subtotal 120 put in subtotal column 7 and after subtotal 156 put 1.
Truly, I was bit surprised to see your first post, now I got the reason what kept you held.
I tell you why this happens.
I believe you are using tax procedure TAXINN. The routine 362 (in tax procedure) has the program which fetches the data from your pricing procedure and on what amount the taxes have to calculated is the value passed into BASB condition type of tax procedure. One should always read the routine 362 in tax procedure with the help of ABAP consultant. This will give you clarity on the concept of calculation. the subtotal field i.e is KZWI plays important role in calculation.
Currently I do not have access to any test system. If you put the subtotal what I have mentioned the result will come.
Another layman tip I am giving you for tax procedure calculation. where ever you are calculating subtotal just give value from 1 to 7 in subtotal column with different combination one by one and see the results, you will have good idea how the system behaves. Say if you put subtotal as 1, the system response will be different from if you give subtotal 4.
Why this is important to understand is when in future if you are going to add any new condition type you will know how the system response is towards the tax calculation.
That is why I suggested you to read the routine 362.
Moreover, if I see your procedure, excise duty, CST and LST should not be calculated on freight charges. Legally this is not correct. Freight charges are in the preview of service tax. In many implementations I came across the similar scenario where the client insisted on the similar procedure. This all happens due to ignorance of client. We have shown the client the official documents as well we also arranged the official meetings with excise commissioners to clear there doubt.
This scenario is usually insisted in the case of freight billed what client says. this is not correct.
Regards
Rajesh

Pricing, Directory and what's missing...

A rather open ended thread I fear but it might spawn others...
Pricing; I'm not sure what the situation in America but here in the UK it appears that Apple is squeezing us (well, ok, ME) out.
Leopard Client 98 pounds, Leopard Server cheapest option (10 user licence) 250 pounds
Snow Leopard Client 25 pounds, Snow Leopard cheapest option (unlimited) 400 pounds
I run Leopard Server on a small network of about 6 users and want to use it primarily as a web server for internet groups - hence 10 user licence is ideal. The unlimited version is overkill for me and very expensive on my budget.
Does anyone else have an opinion?
Directory: I spent most of the life cycle of wiki 1 arguing that a web based directory listing of users and their contact details, editable by users via HTML was vital for my needs. Apple clearly thought it was useful in principle because a directory.xsl file sat, unused in the theme folder.
With wiki 2 I argued during seeding that the directory service in the wiki was a "deal breaker" for me but was reassured to see that the directory.xsl file was still there (updated from wiki 1) and held my breath. Here we are at v433 and release date and it's still not implemented. I fear the deal is broken!
It seems to me that Apple have positioned Snow Leopard as a network server (designed for a network of Macs) rather than a web server (designed for the internet). I have no real complaints about that, they have the focus groups and market surveys which tell them what will sell but it's really disappointing to me that I don't fit their business model.
If anyone can correct my understanding that only mac users can view and update the address book server it might moderate my chagrin.
And finally, on a more positive note,
are there any other things that people feel are missing from wiki 2 so that we can start feeding that back to Apple so that wiki 3 REALLY provides everything a person could want?
My own personal favourite being a Forum to go with wiki and Blog - it really wouldn't be that hard for someone to write would it? It would just need stiching into the services provided by the wiki. (On which note. see the post that I am about to post regarding 3rd party plug-ins (probably on the web section))

Nothing is missing.
from the "Student and Teacher Edition FAQ":
"Adobe Student and Teacher Editions are the same full versions of some of our commercial software titles, priced at discounts for students, faculty, teachers, and administrators. "

PRICING SUBTOTAL

HI
in pricing procedure subtotal can we give same subtotal key say 1 KOMP_KZWI1 to different ctypes
say PRoo & zhbo Discount
Will it create any problem

Dear Friend.
It depends what your requirment is. It is possible. and should not create any problem. this subtotal will be stored in the perticular field and then you can reuse it for further calculations.
The sub total field is used to cumulate the condition types values. e.g if you want all discounts to be calculated together in one field for further references...you want different pricing conditions to be cumulated and so on,
The example you have used tells about pricing conditions and discount conditions which will be cumulated in one field outcome will be stored in perticular field and you can use that for further calculatons. But mixing pricing and discount seems unlikely.
I hope clears your doubt.
Regards,
Paresh

Pricing Problems

Hello Gurus,
I am currently working on Pricing, all of a sudden some one (admin) configured our SAP and we have lost all of our Z-data (tables, account groups, partners,etc.). But then, I have re-created all of them as per my requirements, my concern is that.. although I have done that I am facing a few problems with Pricing, they are:
1. In my pricing procedure, I have about 4 condition types (2 pricing, 1 discount, 1 taxing class) and 2 lines which dont have any condition type assigned to them. So, when I am trying to create a sales document, I find those 2 lines (lines without the condition types) by default, but I dont those 4 which have the condition types (although, if I look into the possible entries - I can find them and can do the assignment), but I wanted them to appear by default rather than me going and pulling them from the possible entries every time, Please suggest me a way to do it so that they appear by default
2. Even the SAP pricing does not work, I mean even the pricing procedure RVAA01 which is the standard SAP does not do the calculation.. and I dont find the reason why, because everything worked fine before the system was configured, how do I get them to work ??
3. As we are aware of the fact that in most of the cases PR00 is a mandatory condition and still then, it is not present in the sales document by default, everytime I have to go into the possible entries screen and pull it up. How can I make it appear by default.
Please help me out.
thanks.

Hi Raj,
Check your condition types in V/06 if they are automatic or not.This can be checked under "Changes which can be made" and in manual entries field it should be automatic.
After making your conditions automatic,maintain the values of those copndition types in T-code "VK11" at sales org or customer level and it will appear in your sales order automatically.
As far as calculating the value is concerned check the from and to field for your condition types and also make sure that the conditions are mandatory in pricing procedure.
Reward points if it helps.
Regards
Karan

Is the 20% discount added before or after a reward certificate?

Hello again. I got another question regarding the 20% discount. Is the 20% discount added before or after a reward certificate. So say for example, if I purchased a game for $60 and I had a $20 certificate, would my 20% discount activate first? Thus making the price 47.99 and then the $20 certificate reduced from that, making it 27.99 total. Or would it be the opposite and the certificate reduces off the $60 game first resulting in a grand total of 31.99?

Hey again JRxPHANTOM,
Good question! My Best Buy reward certificates are considered to be a form of payment, so they're applied to purchases after any applicable bundle pricing or discounts. Unlike traditional forms of payment though, they're applied before sales tax is calculated.
Here's how it would work using the example you provided (a $60 game, 20% Gamers' Club Unlocked discount, and a $20 reward certificate):
The base total is calculated ($60.00)
Your GCU discount is applied ($60.00 - 20% = $48.00)
The reward certificate is applied ($48.00 - $10.00 = $38.00)
Sales taxes are calculated ($38.00 x local rate)
The remaining balance due would then be collected, as with any other purchase.
I hope this helps.
Aaron|Social Media Specialist | Best Buy® Corporate
Private Message

Step by Step process for Pricing in SAP

Hello Experts,
Can any one please send me the documentation for whole process of pricing in SAP , So that it will explain me how it works in SAP.
I don´t need the steps for the configuration.
Thanks

Hi
Pricing and Conditions
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. For example, a particular customer orders a certain quantity of a particular product on a certain day. The variable factors here - the customer, the product, the order quantity, the date - determine the final price the customer gets. The information about each of these factors can be stored in the system as master data. This master data is stored in the form of condition records.
refer link below
<a href="http://www.sap-basis-abap.com/sapsdlog.htm">PRICING</a>
PRICING:
Pricing is the combination of creating correct pricing procedure that map the business needs & processes, such as correct pricing & discounting, & keeping to the legal requirements placed on the business, such as adhering to the tax laws of the country.
SPRO- IMG- SD- Basic Functions- Pricing- Pricing Control
Create Condition Table: V/03, V/04, V/05
Define Access Sequence: V/07
Define Condition Types: V/06
Define & Assign Pricing Procedure
Maintain Pricing Procedure: V/08
Define CuPP: OVKP
Define DoPP: OVKI. The DoPP indicator is used to determine pricing in conjunction with the sales area & CuPP.
Assign DoPP to Order Types & Billing Types: OVKJ & OVTP
Define Pricing Procedure Determination: OVKK
Create Condition Table: V/03, 04, 05
Put the most general field for e.g., Sales Orgn in the highest position & the most specific field in the lowest. After organizational fields, place fields from doc header before those that come from item level (customer comes before material).
Sales Orgn, Distbn Channel, Div, Cust, Mat: Customer Specific Price
Sales Orgn, Distbn Channel, Div, Price List Type, Mat: Price List
Sales Orgn, Distbn Channel, Div, Mat: Material Price.
Maintain Access Sequence: V/07
Go to new entries, define 4-digit acc seq. Select acc seq, go to Accesses and place the cond tables and check exclusive indicator (which determines that if a cond record is successfully found, the system will stop searching further). Select each cond table and go to Fields.
There are some cond types for which you do not create cond records (header discounts that you can only enter manually). These cond types do not require an access sequence.
Define Condition Type: V/06
They are used in the pricing procedure to define how the cond is going to perform, such as either a %tage or a fixed amount. The cond type can be automatic or it can allow manual changes. Copy the required cond type and rename. Then assign acc seq to cond type.
If you use different calculation types for what are otherwise the same conditions (for e.g., %tage, as fixed amt, qty dependent), you do not have to define different cond types in customizing. You can set different calculation type when maintaining cond records.
Functionality of Condition Types:
Access Sequence
Condition Class: surcharge & discounts or prices
Plus/Minus: -ve, +ve or both
Calculation Type: fixed amt, %tage, qty, wt, voln
Rounding rule: commercial, round up and round down
Group Cond
Manual Entry: whether manual or automatic entry has priority
Header Cond: after entering the header cond type click on the button activate. The cond amt of the header conditon is copied as it is to all the line items in the doc.
Item Cond
Amount/ Percent: check & u can change the amount or % for the cond type during data processing
Delete: check & the cond record may be deleted from the doc.
Value: check & the value of the cond type can be changed during data processing
Calculation Type: check & the cal type can be changed during doc processing
Valid from & to
Scale Basis: determines how the system interprets a pricing scale in a cond, for e.g., the scale can be based on qty, wt, voln
Check Value: indicates whether the scale rates must be entered in ascending or descending order.
Define and Assign Pricing Procedure: V/08
A pricing proc consists of a lists of cond types in a defined order, such as price less discount plus tax. Go to new entries, define 6-digit pricing proc with descp. Select the 6-digit pricing proc and go to Control Data, you will be faced with an empty structure.
Step: the no that determines the sequence no of a cond type with in a procedure
Counter: second mini step with in an actual step
Conditon type: specify the cond type
From & To: if you specify the ref steps in these fields, the cond values of the 2 steps specified and steps in between are totaled
Manual:
Mandatory: whether a cond type is mandatory when system carries out pricing
Statistical: the value represented in this step will not alter the overall value
Print: which cond types should be printed on a doc (order confirmation, invoices)
Subtotal: controls whether & in which fields the cond amts or subtotals are stored
Requirement: for a cond type to be executed in the sales doc the requirement specified here must be satisfied. (It is a gateway)
Alternative Calculation Type: alternative formula to the formula in the std system that determines the cond. In the std SAP system for the cust expected price EDI1, the alt cal type is 9, which means it contains a routine with a logic which states that the difference between the customer expected price & the net value is zero.
Alternative Cond Base Value: alternative formula for determining the cond basis (amt to which the discount or surcharge in a scale refers)
Account Key: this field enables the system to post the sales value to different G/L accounts. ERL: sales revenues, ERS: sales deductions, ERF: freight revenue.
Accruals: this is exclusively for rebate cond types BO01 & BO02. Key, which identifies various types of G/L accounts for accrual postings.
TAX: MWST
Tax is calculated on the following parameters:
Plant
Ship to party region
Customer tax classification
Material tax classification
Pricing Procedure Determination: OVKK: Determination Rule
Before one can proceed with the determination rule, one needs to maintain the CuPP & DoPP. One needs to assign a single character alphanumeric key with a short descp. Then assign the DoPP to the sales doc types. This will ensure that for e.g., all sales orders created using order type OR, which has been assigned a DoPP of 1, will all use the same pricing proc if created in the same sales area & with the same CuPP. In some instances, you may not want to have the same pricing proc for a sales doc, as you may want in a billing doc. For this reason, you may allocate a different DoPP to a billing doc.
Do not forget to assign the CuPP indicator to your CMD in the Sales Screen
Sales Orgn + Distbn + Division + CuPP indicator + DoPP indicator = Pricing Procedure
To Create own Sales Doc Types:
SPRO- IMG- Sales Doc- Sales Doc Header-
Define sales doc types: VOV8. Copy std order type& rename
Assign Sales area to Sales Doc Types:
Combine sales orgn
Combine Distbn channel
Combine division
Assign sales order types to permitted sales area
To create Price List Types:
SPRO- IMG- SD- Basic Functions- Pricing- Maintain Price Relevant Master Data:
Define price list category for customers: OVSI: assign to CMD sales area screen in price list type field, in sales tab page in pricing and statistics section.
Define pricing group for customers: OVSL: assign to CMD sales area screen in price group field, in sales tab page in pricing and statistics section.
Define material group: OVSJ: assign to sales orgn 2 view of MMR in Mat Pricing Group Field.
2 digits character key with description
Cond Type Description Cond Class Calculation Type
BO01 Group rebate Exp reimbursement Percentage
BO02 Mat rebate Exp reimbursement Qty (fixed)
BO03 Cust rebate Exp reimbursement Percentage
BO04 Hierarchy rebate Exp reimbursement Percentage
BO05 Hierarchy rebate / Mat Exp reimbursement Percentage
BO06 Sales Independent Rebate Exp reimbursement Fixed amount
EDI1 Cust Expected Price Prices Quantity
HB00 Discount (value) Discount / Surcharge Fixed amount
HD00 Freight Discount / Surcharge Gross weight
K004 Material Discount / Surcharge Qty / absolute
K005 Customer / Material Discount / Surcharge Qty / absolute
K007 Customer discount Discount / Surcharge Percentage
K020 Price group Discount / Surcharge Percentage
K029 Material Pricing Group Discount / Surcharge Absolute discount by wt
K030 Customer/ Mat Group Discount / Surcharge Percentage
K031 Price Grp/ Mat Pr Group Discount / Surcharge Percentage
K032 Price Grp/ Material Discount / Surcharge Quantity / absolute
KF00 Freight Discount / Surcharge Gross weight
NRAB Free Goods Discount / Surcharge Quantity
PI01 Inter company price Prices Quantity (fixed)
PI02 Inter company % Prices Percentage
RB00 Discount / value Discount / Surcharge Fixed amount
PR00 Price Prices Quantity
VPRS Cost Prices Quantity
RL00 Factoring Discount Discount / Surcharge Percentage
MW15 Factoring Discount Tax Taxes Percentage
SKT0 Cash discount
Customer Specific Price: sales orgn, distbn, division, customer & material
Price List Price: sales orgn, distbn, division, price list type & material
Material Price: sales orgn, distbn, division & material
Customer discount: sales orgn, distbn, division & customer
Customer material discount: sales orgn, distbn, division, customer & material or sales orgn, distbn, customer & material.
Material discount: sales orgn, distbn, division & material or sales orgn, distbn & mat.
Condition Records:
Condition records allow you to store & retrieve pricing data in the system. Pricing elements are generally managed at the sales orgn & distbn channel level. There fore you always have to specify organizational level when creating cond records. In the case of cond records for price groups, freight charges, & cust specific prices & discounts you must also enter the division. As a result, you can create conditions according to product groups with these price elements.
Pricing Elements in Sales Order:
Price: the basis of pricing during sales order processing is the gross price of the mat. The system selects the most specific record- the cust specific price. If it does not exist, the system looks for price list type. If it also does not exist then system takes the basic material price. You can define price list types by customer groups (wholesale or retail) or by currency (price lists for each foreign country dealt with)
Surcharge & Discounts:
Freight Costs: you can create cond record either based on: the first part of the inco term (for e.g. FOB) or on the combination of part 1 & 2 (for e.g. FOB & Boston). There are 2 predefined freight conditions
o KF00: applies to each item in a sales doc.
o HD00: applies to entire document.
Sales Taxes:
Prerequisites for Automatic Pricing:
Necessary data must be maintained in MMR & CMD:
Material Master Data: the price related fields can be found in sales orgn 1 & 2.
Tax Classification
Price Material: you can specify another material as ref for pricing info
Material Group: defines a group of materials for which you want to apply the same cond record.
Cash Discount: whether or not mat qualifies for cash discount
Customer Master Data: the price related fields appear on sales data screen.
CuPP: specify the pricing proc for a customer
Price List: Allow you to apply a mat price in a particular currency to a group of customers e.g. wholesale customers.
Price Group: price group lets you apply a discount to a particular group of customers.
Tax Classification: billing tab page.
HEADER & ITEM CONDITIONS:
The standard system includes cond types that you can apply at only the header level, the header conditions. Cond types that you can only use for items are called item conditions. There are some cond types that can be used at both header & item level:
RA01: percent from gross
RB00: absolute discount
RD00: weight discount
Header Conditions: you cannot create cond records for it; it is entered manually in order processing. Automatic pricing does not take place for them.
HA00: percent discount
HB00: absolute discount
HD00: freight
HM00: order value
Item Conditions: in the std SAP most cond types are defined as item conditions:
K004: mat discount
K005: cust/ mat discount
K007: cust discount
PR01: mat price
KF00: freight
Distribution between Header & Item:
Header conditions apply to all items in the doc & are automatically distributed to all the items. It can be either percentage or an absolute amount.
If you enter a header cond that is based on a percentage (e.g., a dis of 2% ) the system automatically applies this percentage to all the items in the doc.
If the header cond is an absolute amount, there are 2 ways in which the system can distribute the amount among the items in the doc:
Distributed proportionally among the items
Amount entered at header level is duplicated for each item.
You control the distribution of absolute header condition in the Group Price Field per cond type.
HB00: header discount distributed as percentage because it is marked as a header cond & group condition. The system distributes the amt proportionally among the various items, in this case according to the value of the items. The distribution of an absolute header cond need not be based on value. For e.g. you can specify in customizing for sales that the distribution is based on weight & volume of the different items. You can specify the basis of distribution in the Alternative Cond Base Value field in the pricing screen.
RB00: assigns the header discount to each item identically, because it is only marked as header condition.
<b>
REWARD IF HELPS</b>
Message was edited by:
SHESAGIRI GEDILA

List of sales condition types for a material

Hi,
I have a material and maintained pricing and discount condition types for that material. I guess VK33 helps to view what condition types maintained for that material.
However when I tried VK33 and selected the material from the conditions from the node on the left hand side and entered the sales org, dist. channel and material and executed after I clicked on the display icon on the condition type, Sales org, Dchl material no conditions are displayed.
Please let me know how I can view the list of sales condition maintained for a specific material.
Thanks.

Hi Giri,
Thanks for the response.
In VK13 I should enter the condition type then I can hit condition information so that the details of all records maintained for a specific condition type will only be displayed but not for other condition types.
In V/LD, I am getting the list only for individual prices. If I insert 17 u2013 Discounts and surcharges by customer or 18 u2013 Discounts and surcharges by material, I am unable to get the list. Is it anything because of the u2018release statusu2019? We had not checked the u2018release statusu2019 field for the tables assigned to access sequence for the condition types.
As per the requirement business wants to view the list of u201CDiscounts and surcharges by customer/materialu201D. I think this is possible if I run the report provided by inserting values 17 or 18 but the unable to view the list. Any config settings required to activate?
Please let me know how to view the list of condition types.
Thanks

Pricing Procedure_100% discount

Similar Messages

Maybe you are looking for