Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

See also links
Pricing Troubleshooting Guide
Implementation of an IPC patch
How to check CRM pricing performance

Overview

Pricing functionality in CRM has been designed using Sales and Distribution pricing as reference, so the functionality is the same for the most part.

If you have an scenario with integration between CRM and ECC,  where business transactions must be transferred from CRM to ECC or vice versa, the pricing results for the business transactions should normally be the same, given that customizing and master data is the same as in both systems and the pricing user exits implemented in ECC have also been implemented in CRM. However, please consider that are some functional differences ( see next section).

Pricing functionality in CRM also uses the condition technique for the determination of pricing conditions. Therefore, in the business transaction, there will be a determination of the pricing procedure and for each condition type in the pricing procedure, there will be an access sequence with its list of condition tables where the pricing conditions can be stored.  For more details, you can check the pricing process flow under:

 Pricing process Flow

Differences between pricing in CRM and pricing in ECC

Functional differences.


Most of the functional differences are collected in:

 

Differences in technology

Starting from CRM50 on and up to the current version CRM70 ,the "basis" side that processes the business logic for pricing and product configuration is handled by the Virtual Machine Container (VMC) (notes in component BC-VMC*). The pricing and configuration components are developed in Java but they run  over the VMC, which is installed together with the CRM Server.

We used the term “IPC” (Internet Pricing and Configurator)  in CRM 40 version to refer to a separate java component where Pricing and Configuration functionality was processed. The separate component “IPC” does not exist any more in CRM 50 and higher versions. However the term “IPC” is sometimes still used to refer to the java packages that implement Pricing and Configuration over the Virtual Machine Container
 
For more details see KBA
2125608 - Information about VMC and need of Java stack for IPC

Differences in programming language for customer user exits (java)

As the standard pricing functionality is developed in java, the customer user exits must be developed in java as well. For details about the steps in implementation of customer user exits check the user exit manual attached to SAP Note
809820  Userexit concept for pricing

 

Differences in data model.

The differences in data model should normally not be relevant for your customizing setup or your user exit implementation. Nevertheless, it may be interesting to know them for troubleshooting purposes.

 

Pricing Customizing tables

The ECC and CRM models are similar and for each ECC table there is a matching CRM table, but with different name.

 

ECC

CRM Online   DB

CDB and Mobile Client

Pricing Procedures

T683

PRCC_COND_PPD

CDBC_P_CN_PPD

Pricing Procedure : Detail or pricing proc with list of condition types

T683S

PRCC_COND_PP

CDBC_P_CN_PP

 

Condition Types:  with Detail of each condition type
(but not acc sequence)

T685A

PRCC_COND_CT

CDBC_P_CN_CT

Condition Type and its access sequence

T685

/SAPCND/T685

CDBC_C_T685 

Access   sequences

T682

/SAPCND/T682

CDBC_C_T682  

Elements   (Accesses) in an Access Sequence

T682I

/SAPCND/T682I

CDBC_C_T682I 

Metadata   for condition tables:
contains the names of all condition tables 

T681

/SAPCND/T681

CDBC_C_T681

List of   condition tables and their fields

T681E

/SAPCND/T681E

CDBC_C_T681E 

Field   catalog

 

/SAPCND/T681FA

CDBC_C_T681FA  

 

 Master data tables

 

ECC

CRM   Online

CDB   and Mobile Client

Condition  table  main   data

AXXX (condition table)

 KONH
 KONP

Cond tables that have a corresponding ECC cond  table

CNCCRMPRSAPXXX 
 CNCCRMPRCUSXXX   for customer table, where  XXX >500
   
    Tables that do not have a corresponding ECC table
    ( 5 digits for the cond. Table name)
    CNCCRMPRSAPXXXXX

CNCCRMPRCUSXXXXX

 

Cond  table
CMBCCPSAPXXX

 

(or   CMBCCPCUSXXX for customer condition table    where XXX > 500 )

 

If  supplements exist

 

Supplement tables have   similar names as   cond tables but starting with:
    CNSCRMPR*

Supplement tables have   similar names as   cond tables but starting with:
    CMBSCP*

If   there are scales, apart from   tables above, these ones

KONM

KNOW

CNLCRMPRSCALEV01  
CNLCRMPRSCALEEVL
CNLCRMPRSCALEDIM
CNLCRMPRSCALEDEF
CNLCRMPR*_LIN 

CMBLCPSCALEV01
CMBLCPSCALEEVL
CMBLCPSCALEDIM
CMBLCPSCALEDEF
CMBLCPS*_LIN

 

Details of master data tables in ECC

 

Details of master data tables in CRM

 

 

 

 

 

  • No labels