You are on page 1of 11

Setting up of Product Pricing in SAP CRM

1.

Step 1: Creation of condition table


You use a condition table to determine the combating of fields of which you want a condition record to consist.
The number of fields used for a condition table is restricted to 10.

Many standard tables are available; but some specific conditions are to be maintained then one can
create their own tables as well.

One common and simple table is SAP004 which contains fields sales org,
distribution channel and product.

Step 2: Create access sequence


In this IMG activity, you determine, depending on the condition type and with help from an access sequence,
the order in which the system should work through the condition tables when searching for certain condition
records. Every condition table contains a certain combination of fields for which the system should search in
the condition records. The search sequence should go from special to general condition records (for example,
search for the field Customer before the field Customer Group).
Using the exclusive indicator, you determine that the system ends the search after the first valid condition
record is successfully accessed.
You determine an access sequence for every condition type for which you create condition records. There are
some condition types for which you do not have to create condition tables (for example, discounts that are not
searched for but rather are entered manually). You do not have to determine access sequences for these
condition types.
Example
Condition table A contains the field combination Product/ Country; condition table B contains the field
combination Product/ Customer. You determine the following sequence in the access sequence for the
condition type Product Substitute:
1. Condition table B (Product/ Customer)
2. Condition table A (Product/ Country)
Now when the product substitution searches for a product, the system firstly searches in the condition records
for a customer-specific product substitute. If it does not find an entry for this, it then searches for a countryspecific product substitute.

Example 1:

Example 2:

Step 3: Creation of condition types

In this IMG activity, you use the condition type to define the properties, field combinations and business
importance of condition records. You can, for example, create different condition types for free goods discount,
sales-dependent rebate or gross price discount.
You can also copy the condition types from SAP R/3.

In SAP CRM, you cannot change condition types that have been copied from SAP R/3.

The name range for customer-specific entries is: A* to Z* and 8*, 9*.
Condition types in pricing
For pricing, a condition type represents a specific aspect of daily pricing activities in the system. You can, for
example, define a condition type for every type of price, discount and surcharge that occurs in your business
transactions. The condition type defines, for example, the calculation type for a product discount. You can also
define that the discount is calculated as a fixed amount or a percentage.
You generally assign an access sequence with the required condition tables to every condition type. There are,
however, condition types to which you do not assign access sequences. This means, however, that the system
doe not automatically search for the condition types during pricing. This makes sense for condition types that
should only be entered manually in the transaction.

Step 4: Creation of procedure

The pricing procedure defines the valid condition types and the sequence of calculation in the transaction. It
also defines the following:
which subtotals are shown on the pricing screen

if manual processing of pricing is possible

on what basis the system calculates surcharges and discounts

which requirements must be met in order that a specific condition type is taken into consideration.
The pricing procedures can also be copied from the R/3 System.

Changes can only be made in the CRM System on data that was created in the CRM System. The data is
identified with the source system field. You can only change data in the CRM System if the field has the value
B.
Namespace for customer-specific entries: A* to Z* and 8*,. 9*.
New Customizing in CRM System can only be copied manually into the R/3 System.
You can find information on data transfer for pricing in the SAP Library under Basic Functions -> Pricing.

Step 5: Determine Pricing Procedures

Pricing procedure can be done using the:


Sales organization

Distribution channel

Document pricing procedure (can be assigned to a sales transaction, on the third level)

Customer pricing procedure (assignment in business partner master)

Do not forget to have the same document pricing procedure you have for your transaction type
Also the customer pricing procedure should be same as maintained for BP ( or you can keep it black here
if you do not want determination based on customer pricing procedure)

Step 6: Setting up price for product


Go to transaction commpr01
Select your product. Go ahead and update the price in conditions tab.

And now a very important step.. Pray to your favorite God that it works.. :-)

You might also like