Professional Documents
Culture Documents
1.
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.
Example 1:
Example 2:
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.
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
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.
Distribution channel
Document pricing procedure (can be assigned to a sales transaction, on the third level)
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)
And now a very important step.. Pray to your favorite God that it works.. :-)