Show TOC

 Differences in the Data Model

SAP CRM uses a different data model for conditions than SAP ERP. The most important properties are described here:

The tables used are the PRICE tables. They correspond to the condition tables in SAP ECC, but also contain information from the tables KONP and KONH in SAP ECC. Therefore, for the use Pricing (PR) for example, the condition amount is now part of the PRICE table. Fields that are not frequently filled are in another table, the SUPPLEMENT table. For every PRICE table there is a SUPPLEMENT table. For every entry in the PRICE table, there is a related record written in the SUPPLEMENT table, only if one of the fields in the SUPPLEMENT table is not initial. If an entry exists in the SUPPLEMENT table, the flag SUPP_EXIST is set to ‘X’ for the higher-level entry in the PRICE table.

Nomenclature: The name of the PRICE table for application CRM and usage PR is made up of the following:

  • Prefix CNC

  • Application, CRM , for example

  • Usage, PR , for example

  • Table names; from the SAP-delivered tables SAPxxxxx

  • User tables CUSxxxxx

For example:

Table A004 in SAP ECC is mapped to CNCCRMPRSAP004.

A750 becomes CNCCRMPRCUS750

Supplement tables have the same nomenclature, but have the prefix ‘CNS’.

Scales

Scales can be defined for every condition record of usage PR (Pricing). A scale exists if an entry in the PRICE table has a SCALE_DIM that is not equal to 0.

The scale information is stored in the CNL* tables.

  • CNLCRMPRSCALEDIM contains the relationship between scales and values.

  • CNLCRMPRSCALEDEF contains information on scale indicators and scale base prices (gross weight-dependent, for example)

  • CNLCRMPRSCxxxLIN contains the scales, where xxx stands for the scale base price. This means that for a gross weight-dependent scale, the scale is defined in a different table than that for net weight-dependent ones.

  • CNLCRMPRSCALEV01 contains the values of the individual scale levels.

  • CNLCRMPRSCALEEVL contains values such as the calculation type.

T he following nomenclature is valid for all other combinations of application and usage:

Prefix /1CN/

C S L, to signify whether it is a condition table, supplement table, or scale table

  • An identifier for the application, for example B for BBP

  • An identifier for the usage, for example P for PR

  • Table names; from SAP-delivered tables SAPxxxxx

  • User tables CUSxxxxx

Example

Table A016 in SAP ECC is mapped to /1CN/CBPSAP016 for the application BBP.

A750 becomes /1CN/CBPCUS750

The supplement tables have the same nomenclature but have the prefix /1CN/S.

Scales

Scales can be defined for every condition record of usage PR (Pricing). A scale exists if an entry in the PRICE table has a SCALE_DIM that is not equal to 0.

The scale information is defined in tables /1CN/L*.

  • /1CN/LBPSCALEDIM contains the relationship between scales and values.

  • / 1CN/LBPSCALEDEF contains information on scale indicators and scale base prices (gross weight-dependent, for example)

  • /1CN/LBPSCxxxLIN contains the scales, where xxx stands for the scale base price. This means that for a gross weight-dependent scale, the scale is defined in a different table than that for net weight-dependent ones.

  • /1CN/LBPSCALEV01 contains the values for the individual scale levels.

  • /1CN/LBPSCALEEVL contains values such as the calculation type.