SAP ABAP NetWeaver Tutorial

SAP CRM uses IPC to determine pricing information when creating a business transaction, such as a quotation, sales order, service process or a contract. For example, the system automatically determines the gross price and the discounts and surcharges that are relevant for a specific customer or for a particular date, in accordance with the valid conditions.

From a technical point of view, pricing in CRM still use condition technique to perform pricing. Here you can find a link about condition technique and the process when determining the price.

Reference

http://help.sap.com/saphelp_crm60/helpdata/en/51/0302403d62c442e10000000a1550b0/frameset.htm

If your company has already got ERP system online, you can direct download the configuration data to the CRM system using CRM middleware. The configuration data contains pricing procedure, condition type, access sequence. The condition master data can also be downloaded to the CRM side. If your company uses the standalone CRM system, the consultant will need to configure everything in CRM directly.

IPC(Internet Pricing and Configurator) is the core part of pricing. The IPC ensures integrated price calculation, regardless of whether prices are calculated for a business transaction in CRM Enterprise, in Telesales, or in SAP E-Commerce. I will post a new blog to make an brief introduction to IPC.

The CRM applications communicate with IPC using pricing communication structure. Usually, the standard structure field does not meet the requirement. We need to add custom field during pricing process. For example, we need to determine price according to product hierarchy which is not contained in the custom communication structure. In this case, we need to do some enhancement to pass custom field to the communication structure. SAP provide an BADI named ‘CRM_COND_COM_BADI’ for this purpose. I will also post a new article to cover this requirement.