Condition Maintenance in a SAP ERP Integrated Scenario
You can use this function to maintain conditions when you are using a SAP ERP Central Component (SAP ERP) integrated scenario.
As part of condition maintenance, you must first add the key field MVGR1
to
the condition table in SAP ERP. This enables you
to maintain usages, pricing, rebates, free goods and campaign determination
and move condition maintenance to SAP Customer Relationship Management (SAP
CRM).
The condition tables must contain the key field MVGR1
.
To do this, carry out the following steps:
In the ABAP Dictionary (transaction SE11
),
add the field MVGR1
to the structure KOMPAZ
in SAP
ERP. Use data element MVGR1
.
Add the field MVGR1
to the field
catalog for SAP ERP. Do this for the following
usages:
Usage A (pricing): In SAP ERP, in Customizing
for Sales and Distribution
under
Usage E (rebate): In SAP ERP, in Customizing
for Sales and Distribution
under
In SAP CRM, maintain the mapping relationship
for field MVGR1
using transaction Maintain
Table Views
(SM30
) in the view V_CND_MAP_CNVFLD
.
Set up PRC_GROUP1
as a table field
in the local system and MVGR1
as the table
field in the external system. Create an entry for each table field for conversion
rule A and B and always choose A as the conversion type (no conversion routine,
copied directly).
After creating the condition table in SAP ERP, you need to download the Customizing to SAP CRM.
To use product categories, additional Customizing settings are necessary in SAP ERP and SAP CRM.
For more information, see SAP Note 335202.
In addition to these settings, you must also maintain the following
settings in the view V_CND_MAP_CNVFLD
using
transaction Maintain Table Views
(SM30
).
Maintain the mapping relationship for fields PRODH1
, PRODH2
and PRODH3
, as specified in the SAP Note above and create the additional entries for
conversion rule B (from local system to external system).
In Customizing for SAP ERP, maintain
new condition tables, condition types and access sequences for each of the
four usages Pricing (A),
Free
Goods (N),
Rebate (E),
and Campaign
Determination (3).
Ensure in doing so, that the condition
tables for usages A, N, and E contain the key field Campaign
.
Pricing (Usage A)
Maintain the following in Customizing for Sales
and Distribution
under :
Define Condition Tables
Define Access Sequences
Define Condition Types
Define and Assign Pricing Procedures
Rebate (Usage E)
Maintain condition tables, condition types, and access sequences
in Customizing for Sales and Distribution
under .
Free Goods (Usage N)
Maintain the following in Customizing for Sales
and Distribution
under :
Maintain Condition Tables
Maintain Access Sequences
Maintain Condition Types
Maintain Pricing Procedures
Campaign Determination (Usage 3)
Maintain the following in Customizing for Integration
with Other mySAP.com Components
under :
Maintain Condition Tables
Maintain Access Sequences
Maintain Condition Types
Maintain Determination Procedure
Activate Campaign Determination
Note
Ensure you maintain the number range interval 01
for
the number range object KON3
. You do this in
SAP ERP in Number Range Object Maintenance
(transaction SNUM
).
Maintaining Conditions in SAP CRM
Campaign determination can also take place in SAP
CRM after the Customizing download. You do this in Customizing
for Customer Relationship Management
under .
For more information on Customizing for conditions in SAP CRM, see Customizing for Condition Generation in SAP Solution Manager.
Displaying Campaign IDs
The external name for campaign IDs is not displayed within the
condition maintenance in SAP ERP by default, in
other words, you can only identify a campaign by the campaign ID and not with
a short text. However, it is possible to display the external name for campaign
IDs in condition maintenance using the Business
Transaction Event (BTE) 00503306
.
There are two different types:
The BTE 00503306
is not yet implemented
In this case you only need to activate the BTE. In SAP
ERP, go to SAP Business Framework: Business Transaction
Events
(transaction FIBF
) and
then . You can implement
function module CMPB_CMPGN_TEXT_DETERMINATION
without
making further adjustments.
The BTE 00503306
is already implemented
for other customer-specific purposes
In this case, the
coding for function module CMPB_CMPGN_TEXT_DETERMINATION
should
be included in the customer-specific function module. The external name for
a campaign ID is determined in this case by function module CMPB_CMPGN_GUID_TEXT_GET
.
Condition records for condition types and tables that have been created in SAP ERP are maintained by default in SAP ERP. As part of Trade Promotion Management business scenario, you must move condition maintenance to SAP CRM.
In SAP ERP, maintain the appropriate
entries in Customizing for Integration with Other mySAP.com
Components
under . Choose the CRM
Server as the logical system.
In SAP CRM, replicate the contents of
the SAP ERP table MNTCNT
to SAP
CRM. For more information on replicating the content of table MNTCNT
,
see the section Transfer Condition Customizing from SAP ERP to SAP
CRM in Transferring Conditions from SAP CRM to SAP
ERP in SAP Solution Manager.
Note
You need to modify the filter for the object DNL_CUST_CNDALL
to
include table MNTCNT
.
Example: Maintenance of the Price Determination Usage
Example: Maintenance of the Rebate Usage
Example: Maintenance of the Campaign Determination Usage
Example: Maintenance of the Free Goods Usage
Example: Moving Condition Maintenance