Page tree
Skip to end of metadata
Go to start of metadata

Pricing and Conditions  CRM-BTX-BF-PR

Pricing is used to describe the calculation of prices and costs used by Customers and Vendors.

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.

>> Condition Technique is a method by which the system determines prices from information stored in condition records.

The steps show how the various elements in the condition technique work together:

1>    The system determines the pricing procedure according to information defined in the sales document type and the customer master record.

2>    The pricing procedure defines the valid condition types and the sequence in which they appear in the sales order.

3>    Each condition type in the pricing procedure can have an access sequence assigned to it. Each access specifies a particular condition table. The table provides the key with which the system searches for records.

4>    If the access is unsuccessful the system moves on to the next access and finds a valid record.

5>    The system determines the price according to information stored in the condition record. If a pricing scale exists, the system calculates the appropriate price.


The following figure illustrates the relationships between elements of the condition technique.

The system repeats this process for each condition type in the pricing procedure determines a final price.

The following aspects are of significance for controlling pricing:

Condition type

Using the condition types, you define which types of prices, discounts, and surcharges exist in the SAP system. The condition types which are pre-defined in the standard SAP delivery system include-

1> customer-specific discount

2> freight charge

3> material surcharge

4> price list price

Use: A condition type is a representation in the system of some aspect of your daily pricing activities.

Some Condition types in the standard R/3 system-

PR00 - Price; K004 - Material Discount; K005 - Customer-specific material discount; K007 - Customer Discount; K020 - Price group discount; KF00 - Freight surcharge (by item); UTX1 - State Tax; UTX2 - County Tax; UTX3 - City Tax.

Creating and Maintaining Condition types:

Here you can change existing condition types.

 Condition Types Details:

Condition table

 In the condition table, you specify the combination of fields for which you want to create a condition record. For example, you can create a condition record for a price which is dependent on-

1> sales organization

2> distribution channel



Here is the technical view of customer material table##


Access sequence

 The access sequence is a search strategy with which the SAP system searches for valid condition records for each condition type during pricing. The access sequence refers to the fields which are relevant for pricing using the condition tables contained in the access sequence. Using the access sequence, you can control that the SAP system first of all searches for a customer-specific price and then for a price list price.

Access overview of Access sequence PR00##


Fields overview of Access PR00 and Table 5##

Pricing procedure

In the pricing procedure you specify the condition types which are to be used in pricing. At the same time, you define the sequence in which the condition types are to be brought into play. Which pricing procedure is valid for a business transaction depends on the following criteria-

1> customer

2> sales document type

3> sales area

Maintaining pricing procedure screen##
You also need to take the following points into account:

Pricing for a document item depends on its item category. You must make the appropriate settings for all item categories for which pricing should be carried out. Pricing is not activated, for example, for free of charge items.

Also, check how the copying of pricing data is controlled in the SD documents (document flow). For example, you specify in the document flow how prices are copied from a sales order into a billing document.

In addition, you must define master data fields which are relevant for pricing. For example, you must specify a price group for a customer if you want to use this price group for pricing.

Define the degree of responsibility your employees have for conditions.

If the cost price is to be determined during pricing, you must classify the item categories appropriately.

Note: You define pricing for each sales area. You can use sales area assignment to apply the same pricing rules to more than one sales area. (See Section "Define common master data").

Transport interface: In the transport, all objects which were maintained in Customizing for controlling pricing are transported. In the correction which is created for the transport, check the table entries and delete any entries which are not to be transported.

  • No labels