!--a11y-->
Example: Condition
Maintenance in SAP CRM 
Before you can start to plan a trade promotion, you must first maintain certain settings for condition maintenance in Customizing for Customer Relationship Management (CRM) by choosing Marketing ® Marketing Planning and Campaign Management ®Condition Maintenance. In this document you will find an example of these settings in Customizing.
From the SAP Trade Promotion Management Business
Scenario you must download a part of the Customizing from SAP ECC in SAP CRM.
For more information on the finding the required Customizing in SAP ECC and downloading it in SAP CRM, see Conditions and Rebate Agreements in Trade Promotions.
In the standard system, condition maintenance group 1200 (campaign management) is assigned to the CRM application.
The standard system contains the condition generation types 0001 (TPM Standalone with CRM Master Data) and 002 (TPM Standalone with ERP Master Data). We recommend you define a new condition generation type, for example, the condition generation type TPM (TPM Standard).
There are three different scenarios for Trade Promotion Management (TPM) condition maintenance;
...
1. TPM Standalone with SAP CRM master data, where conditions are used in SAP CRM only and are based on master data that has been created in SAP CRM.
2. TPM Standalone with SAP ECC master data, where conditions are used in SAP CRM only but are based on master data that has been downloaded from SAP ECC.
3. Fully integrated TPM scenario, where conditions are used in SAP ECC and are based on master data that has been downloaded from SAP ECC. For more information on the required Customizing in SAP ECC and downloading it in SAP CRM, see Conditions and Rebate Agreements in Trade Promotions
Note: The following condition customizing standard delivery tables apply to the first two scenarios only.
The following Customizing is delivered in SAP CRM based on the condition generation type 0001 (TPM Standalone with CRM Master Data).
Spend type |
Spend category |
Spend method |
Discount method |
Use |
Condition type |
REB |
LUMP SUMS |
DEF |
|
BO |
1202 |
REB |
OTHERS |
DEF |
|
BO |
1202 |
REB |
VARIABLE |
DEF |
CASE |
BO |
1202 |
REB |
VARIABLE |
DEF |
CENT |
BO |
1202 |
REB |
VARIABLE |
DEF |
UNIT |
BO |
1202 |
VTS |
FREE |
OFF |
|
FG |
12N0 |
VTS |
OIV |
OFF |
CASE |
PR |
1203 |
VTS |
OIV |
OFF |
CENT |
PR |
1203 |
VTS |
OIV |
OFF |
UNIT |
PR |
1203 |
REB |
LUMP SUMS |
DEF |
|
BO |
1202 |
The following Customizing is delivered in SAP CRM based on the condition generation type 0002 (TPM Standalone with ERP Master Data).
Spend type |
Spend category |
Spend method |
Discount method |
Use |
Condition type |
REB |
LUMP SUMS |
DEF |
|
BO |
1200 |
REB |
OTHERS |
DEF |
|
BO |
1200 |
REB |
VARIABLE |
DEF |
CASE |
BO |
1200 |
REB |
VARIABLE |
DEF |
CENT |
BO |
1200 |
REB |
VARIABLE |
DEF |
UNIT |
BO |
1200 |
VTS |
FREE |
OFF |
|
FG |
12N0 |
VTS |
OIV |
OFF |
CASE |
PR |
1200 |
VTS |
OIV |
OFF |
CENT |
PR |
1200 |
VTS |
OIV |
OFF |
UNIT |
PR |
1200 |
REB |
LUMP SUMS |
DEF |
|
BO |
1200 |
Note that this predefined Customizing and all condition Customizing that you define in SAP CRM can only be used in SAP CRM. If you want to use, for example conditions in SAP ECC, you must define the required Customizing in SAP ECC and then download it in SAP CRM (see also: Conditions and Rebate Agreements in Trade Promotions).
After the Customizing download from SAP ECC and after defining a new condition type group (for example, TPM) in SAP CRM, you can maintain the Customizing settings for the price determination condition types as follows:
Spend type |
Spend category |
Spend method |
Discount method |
Use |
Condition type |
FTS |
DSF |
DEF |
- |
BO |
ZCB1 |
FTS |
SPF |
DEF |
- |
BO |
ZCB3 |
VTS |
FREE |
OFF |
- |
FG |
ZCN0 |
VTS |
OIV |
OFF |
CASE |
PR |
ZCP1 |
VTS |
OIV |
OFF |
CENT |
PR |
ZCP0 |
VTS |
OIV |
OFF |
UNIT |
PR |
ZCP1 |
VTS |
RBVSC |
DEF |
CASE |
BO |
ZCBO |
VTS |
RBVSC |
DEF |
CENT |
BO |
ZCB2 |
VTS |
RBVSC |
DEF |
UNIT |
BO |
ZCBO |
VTS |
RBVSH |
DEF |
CASE |
BO |
ZCBO |
VTS |
RBVSH |
DEF |
CENT |
BO |
ZCB2 |
VTS |
RBVSH |
DEF |
UNIT |
BO |
ZCBO |
The following standard Customizing is delivered in SAP CRM based on the condition generation type 0001 (TPM Standalone with CRM Master Data), and condition generation type 0002 (TPM Standalone with CRM Master Data).
Condition generation type |
Condition type |
Conflict resolution |
0001 |
1200 |
01 |
0002 |
1201 |
01 |
In the fully integrated TPM scenario, After the Customizing download from SAP ECC you can maintain the condition type for campaign determination in SAP CRM, for example ZCD0.
The following Customizing is delivered in SAP CRM based on the condition generation type 0001 (TPM Standalone with CRM Master Data).
Application |
Use |
Condition type |
Customer type |
Product level |
Condition table |
CRM |
BO |
1202 |
01 Account |
PR Product |
SAP12102 |
CRM |
BO |
1202 |
02 Hierarchy Node |
PR Product |
SAP12110 |
CRM |
CD |
1200 |
01 Account |
PG Product Group |
SAP12102 |
CRM |
CD |
1200 |
01 Account |
PR Product |
SAP12100 |
CRM |
CD |
1200 |
02 Hierarchy Node |
PG Product Group |
SAP12112 |
CRM |
CD |
1200 |
02 Hierarchy Node |
PR Product |
SAP12110 |
CRM |
CD |
1200 |
03 Target Group |
PG Product Group |
SAP12122 |
CRM |
CD |
1200 |
03 Target Group |
PR Product |
SAP12120 |
CRM |
FG |
12N0 |
01 Account |
PR Product |
SAP12000 |
CRM |
FG |
12N0 |
02 Hierarchy Node |
PR Product |
SAP12000 |
CRM |
PR |
1203 |
01 Account |
PS Product Segment |
SAP12001 |
CRM |
PR |
1203 |
02 Hierarchy Node |
PS Product Segment |
SAP12002 |
The following Customizing is delivered in SAP CRM based on the condition generation type 0002 (TPM Standalone with ERP Master Data).
Application |
Use |
Condition type |
Customer type |
Product level |
Condition table |
CRM |
BO |
1200 |
01 Account |
PG Product Group |
SAP12104 |
CRM |
BO |
1200 |
01 Account |
PH Product Hierarchy |
SAP12105 |
CRM |
BO |
1200 |
01 Account |
PR Product |
SAP12102 |
CRM |
BO |
1200 |
02 Hierarchy Node |
PG Product Group |
SAP12112 |
CRM |
BO |
1200 |
02 Hierarchy Node |
PH Product Hierarchy |
SAP12114 |
CRM |
BO |
1200 |
02 Hierarchy Node |
PR Product |
SAP12113 |
CRM |
BO |
1200 |
03 Target Group |
PG Product Group |
SAP12122 |
CRM |
BO |
1200 |
03 Target Group |
PH Product Hierarchy |
SAP12123 |
CRM |
BO |
1200 |
03 Target Group |
PR Product |
SAP12120 |
CRM |
CD |
1201 |
01 Account |
PG Product Group |
SAP12102 |
CRM |
CD |
1201 |
01 Account |
PH Product Hierarchy |
SAP12104 |
CRM |
CD |
1201 |
01 Account |
PR Product |
SAP12100 |
CRM |
CD |
1201 |
02 Hierarchy Node |
PG Product Group |
SAP12115 |
CRM |
CD |
1201 |
02 Hierarchy Node |
PH Product Hierarchy |
SAP12114 |
CRM |
CD |
1201 |
02 Hierarchy Node |
PR Product |
SAP12113 |
CRM |
CD |
1201 |
03 Target Group |
PG Product Group |
SAP12122 |
CRM |
CD |
1201 |
03 Target Group |
PH Product Hierarchy |
SAP12124 |
CRM |
CD |
1201 |
03 Target Group |
PR Product |
SAP12120 |
CRM |
FG |
12N0 |
01 Account |
PR Product |
SAP12000 |
CRM |
FG |
12N0 |
02 Hierarchy Node |
PR Product |
SAP12000 |
CRM |
PR |
1200 |
01 Account |
PG Product Group |
SAP12102 |
CRM |
PR |
1200 |
01 Account |
PH Product Hierarchy |
SAP12104 |
CRM |
PR |
1200 |
01 Account |
PR Product |
SAP12100 |
CRM |
PR |
1200 |
02 Hierarchy Node |
PG Product Group |
SAP12112 |
CRM |
PR |
1200 |
02 Hierarchy Node |
PH Product Hierarchy |
SAP12114 |
CRM |
PR |
1200 |
02 Hierarchy Node |
PR Product |
SAP12110 |
CRM |
PR |
1200 |
03 Target Group |
PG Product Group |
SAP12122 |
CRM |
PR |
1200 |
03 Target Group |
PH Product Hierarchy |
SAP12124 |
CRM |
PR |
1200 |
03 Target Group |
PR Product |
SAP12120 |
Note that this standard customizing does not apply to the fully integrated TPM scenario. In this scenario, you have to perform a Customizing download from SAP ECC, and then, in the condition generation type previously created, you need to maintain the correct entries in Condition Tables.
Application |
Use |
Condition Type |
Customer type |
Product level |
Condition table |
CRM |
BO |
ZCB0 |
Business Partner |
Product group |
CUS523 |
CRM |
BO |
ZCB0 |
Business Partner |
Product hierarchy |
CUS525 |
CRM |
BO |
ZCB0 |
Business Partner |
Product |
SAP017 |
CRM |
BO |
ZCB0 |
Hierarchy Nodes |
Product group |
CUS524 |
CRM |
BO |
ZCB0 |
Hierarchy Nodes |
Product hierarchy |
CUS526 |
CRM |
BO |
ZCB0 |
Hierarchy Nodes |
Product |
CUS522 |
CRM |
BO |
ZCB1 |
Business partner |
Product |
SAP017 |
CRM |
BO |
ZCB1 |
Hierarchy Nodes |
Product |
SAP017 |
CRM |
BO |
ZCB2 |
Business partner |
Product group |
CUS523 |
CRM |
BO |
ZCB2 |
Business partner |
Product hierarchy |
CUS525 |
CRM |
BO |
ZCB2 |
Business partner |
Product |
SAP017 |
CRM |
BO |
ZCB2 |
Hierarchy Nodes |
Product group |
CUS524 |
CRM |
BO |
ZCB2 |
Hierarchy Nodes |
Product hierarchy |
CUS526 |
CRM |
BO |
ZCB2 |
Hierarchy Nodes |
Product |
CUS522 |
CRM |
BO |
ZCB3 |
Business partner |
Product |
SAP017 |
CRM |
BO |
ZCB3 |
Hierarchy Nodes |
Product |
CUS522 |
CRM |
CD |
ZCD0 |
Business partner |
Product |
CUS521 |
CRM |
CD |
ZCD0 |
Hierarchy Nodes |
Product |
CUS522 |
CRM |
FG |
ZCN0 |
Business partner |
Product |
SAP017 |
CRM |
FG |
ZCN0 |
Hierarchy Nodes |
Product |
SAP017 |
CRM |
PR |
ZCP0 |
Business partner |
Product group |
CUS525 |
CRM |
PR |
ZCP0 |
Business partner |
Product hierarchy |
CUS526 |
CRM |
PR |
ZCP0 |
Business partner |
Product |
CUS524 |
CRM |
PR |
ZCP0 |
Hierarchy Nodes |
Product group |
CUS523 |
CRM |
PR |
ZCP0 |
Hierarchy Nodes |
Product hierarchy |
CUS527 |
CRM |
PR |
ZCP0 |
Hierarchy Nodes |
Product |
SAP172 |
CRM |
PR |
ZCP1 |
Business partner |
Product group |
CUS525 |
CRM |
PR |
ZCP1 |
Business partner |
Product hierarchy |
CUS526 |
CRM |
PR |
ZCP1 |
Business partner |
Product |
CUS524 |
CRM |
PR |
ZCP1 |
Hierarchy Nodes |
Product group |
CUS523 |
CRM |
PR |
ZCP1 |
Hierarchy Nodes |
Product hierarchy |
CUS527 |
CRM |
PR |
ZCP1 |
Hierarchy Nodes |
Product |
SAP172 |
In the standard system, condition generation type 0001 (TPM Standalone with CRM Master Data) is assigned to:
· Campaign type price promotion (0001)
· Sales organization 0001 (0 50000001)
· Distribution Channel direct sales (01)
· Division product division 01 (01)
You can use this entry as a base and then assign the condition generation type that you newly define to all relevant sales organizations, distribution channels and divisions, as well as to campaign types which you have defined in Customizing for SAP CRM by choosing Marketing ® Marketing Planning and Campaign Management ® Basic Data ® Define Campaign Types/Objectives/Tactics.
No Customizing is delivered with the standard. Therefore, you need to create your own.
If you use SAP ECC Rebates, you need to maintain the Customizing for SAP CRM by choosing Marketing® Marketing Planning and Campaign Management ®Condition Maintenance ® ERP Rebate Processing ® Determine Agreement Type in a Trade Promotion after having downloaded the required Customizing from SAP ECC.
If you use SAP CRM Rebates, you need to maintain the Customizing for SAP CRM by choosing Marketing® Marketing Planning and Campaign Management ® Condition Maintenance ® CRM Rebate Processing ® Determine Rebate Type in a Trade Promotion
The following table is an example of how you can set up this Customizing.
Spend type |
Spend category |
Spend method |
Discount method |
Related volume |
Agreement type |
FTS |
DSF |
DEF |
|
|
ZCA1 |
FTS |
DSF |
DEF |
|
PURC |
ZCA1 |
FTS |
SPF |
DEF |
|
|
ZCA1 |
FTS |
SPF |
DEF |
|
PURC |
ZCA1 |
VTS |
RBVSC |
DEF |
CASE |
|
ZCA1 |
VTS |
RBVSC |
DEF |
CASE |
SCAN |
ZCA1 |
VTS |
RBVSC |
DEF |
CENT |
|
ZCA1 |
VTS |
RBVSC |
DEF |
CENT |
SCAN |
ZCA1 |
VTS |
RBVSC |
DEF |
UNIT |
|
ZCA1 |
VTS |
RBVSC |
DEF |
UNIT |
SCAN |
ZCA1 |
VTS |
RBVSH |
DEF |
CASE |
|
ZCA1 |
VTS |
RBVSH |
DEF |
CASE |
PURC |
ZCA1 |
VTS |
RBVSH |
DEF |
CENT |
|
ZCA1 |
VTS |
RBVSH |
DEF |
CENT |
PURC |
ZCA1 |
VTS |
RBVSH |
DEF |
UNIT |
|
ZCA1 |
VTS |
RBVSH |
DEF |
UNIT |
PURC |
ZCA1 |