Sei sulla pagina 1di 26

EHP3 for SAP CRM 7.

0
April 2014
English

CRM Customizing
Replication (B09)
Building Block Configuration Guide

SAP SE
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
SAP Best Practices CRM Customizing Replication (B09): Configuration Guide

Copyright

2014 SAP SE or an SAP affiliate company. All rights reserved.


No part of this publication may be reproduced or transmitted in any form or for any purpose without the
express permission of SAP SE. The information contained herein may be changed without prior notice.

SAP and other SAP products and services mentioned herein as well as their respective logos are
trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other
countries. Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for
additional trademark information and notices.

Some software products marketed by SAP SE and its distributors contain proprietary software
components of other software vendors.

National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only,
without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable
for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate
company products and services are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein should be construed as constituting an
additional warranty.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business
outlined in this document or any related presentation, or to develop or release any functionality
mentioned therein. This document, or any related presentation, and SAP SEs or its affiliated companies
strategy and possible future developments, products, and/or platform directions and functionality are all
subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason
without notice. The information in this document is not a commitment, promise, or legal obligation to
deliver any material, code, or functionality. All forward-looking statements are subject to various risks
and uncertainties that could cause actual results to differ materially from expectations. Readers are
cautioned not to place undue reliance on these forward-looking statements, which speak only as of their
dates, and they should not be relied upon in making purchasing decisions.

SAP SE Page 2 of 26
SAP Best Practices CRM Customizing Replication (B09): Configuration Guide

Revision Change Date Description

1 May 2015

SAP SE Page 3 of 26
SAP Best Practices CRM Customizing Replication (B09): Configuration Guide

Icons

Icon Meaning
Caution

Example

Note

Recommendation

Syntax

Typographic Conventions

Type Style Description


Example text Words or characters that appear on the screen. These include field
names, screen titles, pushbuttons as well as menu names, paths and
options.
Cross-references to other documentation.
Example text Emphasized words or phrases in body text, titles of graphics and tables.
EXAMPLE TEXT Names of elements in the system. These include report names,
program names, transaction codes, table names, and individual key
words of a programming language, when surrounded by body text, for
example, SELECT and INCLUDE.
Example text Screen output. This includes file and directory names and their paths,
messages, source code, names of variables and parameters as well as
names of installation, upgrade and database tools.
EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the
ENTER key.
Example text Exact user entry. These are words or characters that you enter in the
system exactly as they appear in the documentation.
<Example text> Variable user entry. Pointed brackets indicate that you replace these
words and characters with appropriate entries.

SAP SE Page 4 of 26
SAP Best Practices CRM Customizing Replication (B09): Configuration Guide

Contents

1 Purpose.......................................................................................................................... 6
2 Preparation..................................................................................................................... 6
2.1 Prerequisites............................................................................................................ 6
3 Configuration.................................................................................................................. 6
3.1 Preliminary Activities for Replication........................................................................6
3.1.1 Setting Up Error Handler (SAP CRM) 6
3.1.2 Deactivating Mapping Functions (SAP CRM) 7
3.2 Configuration Replication ERP -> CRM...................................................................7
3.2.1 Checking ISO Codes (SAP ERP) 7
3.2.2 Product Hierarchy Structure 8
3.2.2.1 Checking Product Hierarchy Structure in OLTP (SAP ERP) 8
3.2.2.2 Defining Product Hierarchy Structure (SAP CRM) 9
3.2.3 Defining Product ID Settings (SAP CRM) 10
3.2.4 Replication of Customizing Objects (SAP CRM) 11
3.2.4.1 Re-creating Content of Table CRMATAB (SAP CRM) 11
3.2.4.2 Replicating Customizing Objects from ERP OLTP to CRM System 11
3.2.4.3 Monitoring Replication Status (SAP CRM) 13
3.2.5 Setting Up Taxes 13
3.2.5.1 Defining Filter for Import of Tax Types (SAP CRM) 14
3.2.5.2 Defining SAP CRM Tax Types (SAP ERP) 15
3.2.5.3 Defining Business Partner Tax Groups (SAP ERP) 16
3.2.5.4 Defining BP Tax Classification Assignment Settings (SAP ERP) 19
3.2.5.5 Replicating Tax Customizing (SAP CRM) 20
3.2.5.6 Checking Customizing of Data Transfer for Taxes (SAP CRM) 21
3.2.5.7 Monitoring Replication Status (SAP CRM) 22
3.2.5.8 Defining Tax Type and Group (SAP CRM) 22
3.2.5.9 Defining Assignment of Product Tax Data from ERP to CRM 23
4 Pre-Assembled Deployment......................................................................................... 26

SAP SE Page 5 of 26
SAP Best Practices CRM Customizing Replication (B09): Configuration Guide

CRM Customizing Replication: Configuration


Guide
1 Purpose
This building block (Configuration Guide) describes the necessary activities to replicate
customizing data from the ERP system to the CRM system.
This building block is the prerequisite for the installation of all CRM scenarios delivered by
SAP Best Practices.
This building block is not required if you run the CRM in a standalone mode, that is without an
OLTP back-end system.
The Configuration Guide describes how to set up the configuration of a building block
manually.

2 Preparation
Prerequisites
Before starting with the installation of this building block, please see the document Quick
Guide to Implementing SAP Best Practices for CRM.

3 Configuration
Preliminary Activities for Replication
Setting Up Error Handler (SAP CRM)

Use
In this step, you define an ERP e-mail recipient for each BDoc type. Recipients automatically
receive messages in the Business Workplace Inbox if errors occur in the related BDoc.

Procedure
1. Access the activity using the following navigation options:
Transaction code SPRO
SAP CRM IMG menu Customer Relationship Management CRM Middleware
and Related Components Message Flow Setup Assign
Error Actions to Messages

2. Select Default Error Action.


3. Choose Execute (F8).
4. Select Maintain Configuration (F9).
5. Select Mail as Error Action.
6. Enter the following data as Mail Parameters:
Field name Value
E-Mail Address of Receivers <USER ID> of the user that is logged on
E-Mail Type B (SAP User)

7. Choose Save Configuration (Ctrl + F1).

SAP SE Page 6 of 26
SAP Best Practices CRM Customizing Replication (B09): Configuration Guide

8. Choose Execute (F8).


For other Error Handler settings please see the documentation of the IMG activity.

Result
An ERP e-mail recipient for each BDoc type is determined. This recipient automatically
receives messages in his/her Business Workplace Inbox if errors occur in the related BDoc.
The e-mail recipient is specified as the user (the installation user) that is currently logged on
to the system.

Deactivating Mapping Functions (SAP CRM)


Use
In this step, you will deactivate a setting relevant to business partner relationship replication.

Procedure
1. Access the activity using the following navigation options:
Transaction code SPRO
SAP CRM IMG menu Customer Relationship Management CRM Middleware
and Related Components Mobile Scenario Setup
Activate Mapping Functions

2. On the Change View Customer- Specific Flow :Overview screen,


Field name Value Field name Service Function Entry
Active
BUPA_REL MOB Mboc BP_REL_CR BP_REL_CRM_T x
Notification Multiple M_TO_CDB O_CDB

3. Deselect checkbox of Entry Active.


4. Choose Save.

Result
Deactivate a mapping function for business partner relationships.

Configuration Replication ERP -> CRM


Checking ISO Codes (SAP ERP)

Use
Before starting the Customizing replication, verify that entries for the ISO codes are unique in
the following ERP tables:
Language keys (table T002 field LAISO)
Currency codes (table TCURC field ISOCD)
Countries (table T005 field INTCA).
Although SAP delivers these tables in a consistent state, duplicate ISO entries can occur
because this is not a key field in those tables (especially if own entries have been set up with
copy functions).

Procedure
1. Access the activity using one of the following navigation options:

SAP SE Page 7 of 26
SAP Best Practices CRM Customizing Replication (B09): Configuration Guide

Transaction code SE16


SAP ERP GUI menu Tools ABAP Workbench Overview Data Browser

2. In the table name field enter T002.


3. Choose Table Contents (Enter).
4. Choose Execute (F8).
5. Check the column LAISO for duplicate entries.
6. Repeat these steps for the other tables.

If duplicate ISO codes are detected, they have to be replaced by new ISO codes. The
final result has to be that all tables mentioned hold unique ISO code entries. Multiple
entries with empty ISO codes are possible.
Regarding table TCURC:
You may use several SAP currency keys for the same ISO code. To ensure a unique
assignment of the ISO code to an SAP currency key, one of the SAP currency keys
must be selected as the primary currency key for the ISO code.
If the assignment between SAP currency key and ISO code is unique, you do not
need to select this field.
In order to make ISO codes unique access these tables via the following ERP IMG
activities:
Table TCURC:
SAP NetWeaver General Settings Currencies Check Currency Codes.
Table T005:
SAP NetWeaver General Settings Set Countries Specify Countries in
mySAP Systems (CRM, SRM, SCM, )

Result
You have checked the ISO codes in the three ERP tables.

Product Hierarchy Structure

Please check the Delta Guide.

Checking Product Hierarchy Structure in OLTP (SAP ERP)

Use
The structure of the product hierarchy has to be checked in OLTP (SAP ERP).

Procedure
1. Access the activity using one of the following navigation options:
Transaction code SE11
SAP ERP GUI menu Tools ABAP Workbench Development ABAP
Dictionary

2. In the ABAP Dictionary: Initial Screen, enter PRODHS in the field View.
3. Choose Display.

SAP SE Page 8 of 26
SAP Best Practices CRM Customizing Replication (B09): Configuration Guide

4. In the Dictionary: Display Structure screen the number of components corresponds to the
number of levels in the CRM system (defined in the next paragraph). The field Length
defines the number of digits for each level.

Result
You have checked the structure of the product hierarchy.

Defining Product Hierarchy Structure (SAP CRM)


Use
This step shows you how to define the product hierarchy structure in SAP CRM.

Procedure
1. Access the activity using the following navigation options:
Transaction code SPRO
SAP CRM IMG menu Cross Application Components SAP Product Product
Category Define Category Numbering Schemes

2. Choose New Entries.


3. Make the following entries:
Field name Entry
Number Scheme R3PRODHIER
Scheme Description Numbering Scheme ERP
Scheme Description (DE) ERP Nummerierungsschema
Scheme Description (ES) Esquema de numeracin ERP
Scheme Description (PT) Esquema de numerao ERP
Scheme Description (ZH) ERP
Scheme Description (FR) Schma numerous ERP
Scheme Description (JA) ERP
Scheme Description (RU) ERP
Scheme Description (AR) ERP
Choose Enter twice and ignore the warning message after the first Enter.
4. Mark number scheme R3PRODHIER and double-click on folder Define Numbering
Scheme Levels.
5. Choose New entries and enter the matching levels and number of digits for each level.
They need to be exactly the same as in the OLTP system.

Example (SAP standard delivery):


Level Number of Chars
1 5
2 5
3 8

6. Choose Enter for all entries that have been made and ignore the warning message.
7. Save (Ctrl + S) the entries.

SAP SE Page 9 of 26
SAP Best Practices CRM Customizing Replication (B09): Configuration Guide

Result
You have successfully defined the product hierarchy structure.

Defining Product ID Settings (SAP CRM)


Use
The output format and storage form of product IDs have to be defined.
If you intend to replicate product data to an ERP system, the number of characters you
specify will determine whether you can use the product ID as the material number.
This activity describes how to synchronize the product IDs in the CRM system and the ERP
system.

Procedure
1. Access the activity using one of the following navigation options:
Transaction code COMCPRFORMAT
SAP CRM IMG menu Cross-Application Components SAP Product Basic
Settings Define Output Format and Storage Format of
Product Ids

2. Check the product ID settings in the ERP system by calling transaction OMSL in the ERP
system.
3. Enter the following values on the Material Number Format screen in the CRM system.
Choose New Entries (F5) if no number format exists.
Field Value
Prod. ID Length Value of field Material No. Length in the ERP system
(Transaction OMSL)
Template for ID Value of field Material Number Template in the ERP
system
Display Leading Zeros Value of field Leading Zeros in the ERP system
Save Lexicographically Value of field Lexicographical in the ERP system

4. Save (Ctrl + S) your entries.

For more information, see SAP Note 545824.

Result
The product IDs have been successfully synchronized in the CRM and the ERP systems.

Replication of Customizing Objects (SAP CRM)


Re-creating Content of Table CRMATAB (SAP CRM)

Use
Table CRMATAB contains all of the tables for which the initial load Customizing is allowed. If a
new object is created or activated, the table CRMATAB is not automatically updated. This may
lead to failures in initial load execution (see Note 1498111 for details).
We here launch the re-creation of table content to be sure theres no entry missing.

SAP SE Page 10 of 26
SAP Best Practices CRM Customizing Replication (B09): Configuration Guide

Procedure
1. Access the activity using one of the following navigation options:
Transaction code SE38
SAP CRM GUI menu Architecture and Technology ABAP Workbench
Development ABAP Editor

2. In the ABAP Editor: Initial Screen, enter following value:


Field Value

Program SMOF_FILL_CRMATAB
3. Choose Execute (F8).
4. In Program SMOF_FILL_CRMATAB screen, enter following values
Field Value

Source Site Name CRM

Objectname
All Objects X
5. Choose Execute (F8).
6. In Program SMOF_FILL_CRMATAB screen, enter following values
Field Value

Source Site Name OLTP

Objectname
All Objects X
7. Choose Execute (F8).
8. Choose Back

Result
Content of table CRMATAB has been re-created.

Replicating Customizing Objects from ERP OLTP to CRM


System
Use
The following objects are relevant to the download from ERP OLTP to the CRM system.
Object Name Description
DNL_CUST_ACGRPB Accounting Group Business Partner
DNL_CUST_ACGRPP Account Group Product
DNL_CUST_ADDR Regional structure
DNL_CUST_BASIS Basis CRM online
DNL_CUST_BASIS2 Basis CRM online
DNL_CUST_BASIS3 Basis CRM online
DNL_CUST_BASIS5 Basis CRM online
DNL_CUST_BASIS6 Basis CRM online

SAP SE Page 11 of 26
SAP Best Practices CRM Customizing Replication (B09): Configuration Guide

Object Name Description


DNL_CUST_BNKA Banking Master
DNL_CUST_KTOKD Business Partner: Acc. Group
DNL_CUST_PAYPL Payplan
DNL_CUST_PRICE Sales pricing and pricing item
DNL_CUST_PROD0 Material number conversions
DNL_CUST_PROD1 Product: categories
DNL_CUST_PROD3 Material: ERP sales status
DNL_CUST_SALES Sales
DNL_CUST_SCE SCE varcond
DNL_CUST_SHIP Sales shipping
DNL_CUST_SPROD Sales product item
DNL_CUST_S_AREA Organizational Unit: Divisions
DNL_CUST_T502T Business Partner: T502T
DNL_CUST_TBRC Business Partner: Industries
DNL_CUST_TKUKL Business Partner: TKUKL, TKUKT
DNL_CUST_TNLS Business Partner: TNLS, TNLST
DNL_CUST_TPFK Business Partner: TPFK, TPFKT
DNL_CUST_TSAB Business Partner: TSAB, TSABT
DNL_CUST_TVAST Sales Document Blocking Reason
DNL_CUST_TVFS Sales Document Billing: Block
DNL_CUST_TVGF Business Partner: TVGF, TVGFT
DNL_CUST_TVIP Business Partner: TVIP, TVIPT
DNL_CUST_TVKN Business Partner: Attributes
DNL_CUST_TVLS Deliveries: Blocking Reasons/C
DNL_CUST_TVPV Business Partner: TVPV, TVPVT
DNL_PLANT Plant

Not performing the replication for more than, for example, 5 objects at the same time
avoids possible low performances.

Procedure
1. Access the activity using one of the following navigation options:
Transaction code R3AS
SAP CRM GUI menu Architecture and Technology Middleware Data
Exchange Initial Load Start

2. In the Load Object field, enter an object from the table above.
3. In the Source Site (Sender) field enter OLTP and in the Destination Site (Receiver) field,
enter CRM.
4. To run the replication, choose Execute.

SAP SE Page 12 of 26
SAP Best Practices CRM Customizing Replication (B09): Configuration Guide

5. Repeat this step for all other objects listed above.

Result
You have successfully replicated all the customizing objects from the ERP OLTP to the CRM
system.

Monitoring Replication Status (SAP CRM)


Use
The replication status has to be monitored in the SAP CRM.
Procedure
1. Access the activity using one of the following navigation options:
Transaction code R3AM1
SAP CRM GUI menu Architecture and Technology Middleware Data Exchange
Initial Load Monitor Objects

2. Enter the replicated object in the Object Name field to get the download status of this
object.
To get the status of all replicated objects, leave the field empty.
3. Choose Execute.

Result
The replication is complete if all objects have the status Done.

Choose Refresh to update the object status.

Setting Up Taxes
In CRM standard, there is no automatic generating and transferring function for the entire
configuration about taxes from OLTP to CRM yet. To transfer it from OLTP to CRM, it is
necessary to maintain a mapping table in the CRM system.
The new mapping allows you to have more complex tax determination combined with easier
setup. The determination is based on the combinations of: country + region + tax type + tax
group. The tax group of a certain tax type determines, for example, if a product is fully or
partly taxed or exempt from this tax.
This information is also used by a third party program that finally determines the applicable
tax rate.
How does the transfer logic from ERP OLTP to CRM work?
Products: All existing tax data which is material based (table MLAN) is transferred.
To function correctly the mapping of tax setup needs to be consistent on both sides.
Otherwise the data transfer stops.
Business Partners: The mapping of the tax classification is already done in ERP. The
new configuration objects also have to be maintained in the ERP system since the
business partner mapping is done in ERP system. The Configuration load imports data
from the following tables of the ERP system into the following tables of the CRM system:

ERP System CRM System


Tax Types TSTL TB070
BP Tax Groups TB071_CM TB071

SAP SE Page 13 of 26
SAP Best Practices CRM Customizing Replication (B09): Configuration Guide

ERP System CRM System


Mapping of business TB072_CM CRMC_TAX_MAP_BP
partner relevant
information of
Condition records

The new configuration objects are:


TB070_CM: Tax Types
TB071_CM: BP Tax Groups
TB072_CM: Mapping BP Tax Classification ERP CRM
Condition Records: The data transfer of Condition records for tax
calculation requires the mapping for Products and Business Partners.

This setup of Tax Types can be disabled if the setup for taxes is not required for
Business Partners and Products.

Defining Filter for Import of Tax Types (SAP CRM)

Please check the Delta Guide.

Use
A filter criterion is defined within the business adapter object MATERIAL to select the
countries you need to manage tax information for.

In a typical productive scenario, tax types should be imported for all those countries
where:
a subsidiary of the modeled company exists
the accounting of this subsidiary is managed in SAP ERP
ERP Sales Orders or ERP Quotations need to be created in SAP CRM
The current activation procedure models a company located in a single country
(United States) without foreign subsidiaries. The management of different countries is
possible in SAP ERP but it needs to be covered by additional customizing, which is
not part of the current pre-configured solution.
Procedure
1. Access the activity using one of the following navigation options:
Transaction code R3AC1
SAP CRM menu Architecture and Technology Middleware Data
Exchange Object Management Business Objects

2. Set the filter for the adapter object MATERIAL by clicking on the filter symbol.
3. Make sure that you are in change mode. Choose Display -> Change (Ctrl+F1).
4. In the field Source Site Name choose OLTP.
5. Specify the Countries to replicate Tax information for. Select table MLAN and field
ALAND.

SAP SE Page 14 of 26
SAP Best Practices CRM Customizing Replication (B09): Configuration Guide

Table/Structure Field OP Low High Incl./Excl.


MLAN ALAND EQ <Low number> Inclusive defined
set/array

Enter a distinct line for every Country listed in the Delta Guide.
6. Choose Save (Ctrl+S).
7. Choose No to all on the first dialog box.
8. Choose Continue (Enter)on the second dialog box.
9. Choose Filter Sync.
10. Choose Continue (Enter) on the dialog box.

Result
The filter for tax types has been set up.

Defining SAP CRM Tax Types (SAP ERP)

Please check the Delta Guide.

Use
This step describes the necessary settings that the system requires to download tax
information from customer master records in SAP ERP to business partner master records in
SAP CRM.
These are the customer tax categories and tax classifications that are maintained on the
Billing Document tab in the sales area data in the customer master record. These settings
need to be assigned to the corresponding tax types and tax groups from the business partner
master in SAP CRM.
When customer master records are downloaded from SAP ERP to SAP CRM, the system
assigns the business partner master records to the correct tax types and tax groups.
In this step the tax types are defined in SAP ERP that are used in SAP CRM.
The tax types in SAP CRM are maintained in the following SAP CRM IMG activity:
Basic Functions Taxes Basic Setting Tax Types and Tax Groups Define Tax Types
and Tax Groups.

Procedure
1. Access the activity using the following navigation option:
Transaction code SE16
SAP ERP menu Tools ABAP Workbench Overview Databrowser

2. Enter TSTL field Table Name.


3. Choose Table Contents (Enter).
4. In field Country enter a Country for which you would like to download tax information from
customer master records in SAP ERP to business partner master records in SAP CRM, e.g.
US.
5. For every relevant combination of country and tax category in table TSTL (Tax categories
by countries) a corresponding entry needs to be available in table TB070_CM.
Access the activity using the following navigation option:
Transaction code PITC

SAP SE Page 15 of 26
SAP Best Practices CRM Customizing Replication (B09): Configuration Guide

SAP ERP IMG menu Integration with Other mySAP.com Components


Customer Relationship Management Basic Functions
Taxes Business Partner Tax Groups Define SAP
CRM Tax Types and Business Partner Tax Groups

6. Branch to the Define Tax Types screen.


7. Check if entries for the relevant countries and tax types exist - if not, proceed as follows:
8. Choose Define Tax Types.
9. Choose New Entries.
10. Enter the Country.
11. Enter the Tax Type.
12. Indicate, via the checkboxes, if the tax type is relevant for the Business Partner, Product,
or both.
13. Choose Save.

Example of correct mapping

Result
You have successfully defined the tax types.

Defining Business Partner Tax Groups (SAP ERP)

Please check the Delta Guide.

Use
In this step the tax groups are defined in SAP ERP that are used in SAP CRM.

Procedure
1. Access the activity using the following navigation option:
Transaction code SE16
SAP ERP menu Tools ABAP Workbench Overview Databrowser

2. For every relevant country and tax category in table TSTL determine the tax
classifications in table TSKD.
Enter TSKD field Table Name.
3. Choose Table Contents (Enter).
4. In field Tax Category enter a Tax Category for which you would like to download tax
information from customer master records in SAP ERP to business partner master records in
SAP CRM, e.g. UTXJ.

SAP SE Page 16 of 26
SAP Best Practices CRM Customizing Replication (B09): Configuration Guide

5. For every relevant combination of country and tax category and tax classification in table
TAKD (Tax Groups by Tax Categories) a corresponding entry has to be available in table
TB071_CM consisting of country, tax type and tax group has to exist.
Access the activity using the following navigation option:
Transaction code PITC
SAP ERP IMG menu Integration with Other mySAP.com Components
Customer Relationship Management Basic Functions
Taxes Business Partner Tax Groups Define SAP CRM
Tax Types and Business Partner Tax Groups

6. Select a country and tax type combination.


7. Choose Assign BP Tax Group. Check if an entry according to table TSKD exists.
If not proceed as follows:
8. Choose New Entries.
9. Enter the Country.
Enter the Region, if required.

If you calculate tax via the jurisdiction method, you must maintain a region. If this
field contains no value, the settings made apply to all regions defined for the
country.
10. Enter the Tax Type.
11. Enter the Tax Group.
12. Choose Save.

Example of correct mapping


The country Germany (DE) has the tax category MWST (Mehrwertsteuer). This customizing
in the SAP ERP table TSTL now has to be maintained in the SAP ERP table TB070_CM
(CRM Tax Types) with the following fields and values: country DE, tax type MWST and the
relevance for Business Partner (BP) and Product.
In the SAP ERP table TSKD the tax category MWST has 2 tax classifications, Tax Exempt
and Liable for Taxes. This customizing now has to be maintained in the SAP ERP table
TB071_CM (BP Tax Group) for each corresponding country. In this example two entries have
to be created for the country Germany DE, one for BP Tax Group FULL (=Liable for Taxes)
and one for BP Tax Group NONE (=Tax Exempt).

SAP SE Page 17 of 26
SAP Best Practices CRM Customizing Replication (B09): Configuration Guide

Result
The tax category and tax classification that is assigned to a business partner master record in
the ERP system is mapped to the tax type and tax group in the corresponding business
partner master record of the CRM system.

SAP SE Page 18 of 26
SAP Best Practices CRM Customizing Replication (B09): Configuration Guide

Defining BP Tax Classification Assignment Settings (SAP


ERP)

Please check the Delta Guide.

Use
With this activity you replicate ERP tax categories and tax classifications to the CRM system.
You have to map the newly created CRM tax types and tax categories created in the
preceding activities to the corresponding ERP tax categories and tax classifications.

Procedure
1. Access the activity using one of the following navigation option:
Transaction code PITM
SAP ERP IMG menu Integration with Other mySAP.com Components
Customer Relationship Management Basic Functions
Taxes Business Partner Tax Groups Assign SAP CRM
BP Tax Groups to Tax Classifications

2. On the screen Tax Classification: Mapping ERP <-> CRM, choose New Entries.
3. Enter the Country.
4. Enter the Region.
5. If you calculate tax via the jurisdiction method, you must maintain a region.
6. Enter the CRM Tax Type.
7. Enter the CRM Tax Group.
8. Enter the ERP Tax Category.
9. Enter the ERP Tax Classification.
10. Choose Save.

Result
The newly created CRM tax types and tax categories have been mapped to the
corresponding ERP tax categories and tax classifications.

SAP SE Page 19 of 26
SAP Best Practices CRM Customizing Replication (B09): Configuration Guide

Example of a correct mapping


In this example in the ERP-CRM Assignment (ERP table TB072_CM, ERP Transaction PITM)
two entries have been maintained for the country Germany DE.

Replicating Tax Customizing (SAP CRM)

Use
The tax customizing has to be replicated into the SAP CRM client.

Procedure
1. Access the activity using one of the following navigation options:
Transaction code R3AS
SAP CRM GUI menu Architecture and Technology Middleware Data
Exchange Initial Load Start

2. In the Load Object field, enter DNL_CUST_TAX.


3. In the Source Site (Sender) field enter OLTP and in the Destination Site (Receiver) field
enter CRM.
4. To run the replication, choose Execute (F8).

SAP SE Page 20 of 26
SAP Best Practices CRM Customizing Replication (B09): Configuration Guide

Result
The replication has been successfully executed.

Checking Customizing of Data Transfer for Taxes (SAP CRM)


Use
You have to check the customizing of the data transfer for the taxes in SAP CRM.

Procedure
1. Access the activity using one of the following navigation options:
Transaction code CRM_TAXCUST_VALIDATE
SAP CRM IMG menu Customer Relationship Management Basic Functions
Taxes Basic Settings Tax Types and Tax Groups
Check Data Transfer Customizing Settings

Sometimes, as soon as transaction CRM_TAXCUST_VALIDATE is launched, you


may experience that the program aborts and shows a system dump. This may be
due to inconsistencies in data contained in tax tables (the ones filled in sections
Error: Reference source not found to Error: Reference source not found). In this
case content of tax tables needs to be reviewed to eliminate data inconsistencies. In
case this is not successful, you may consider to completely delete tax tables in
CRM and then re-import them from the ERP executing the relevant sections above.
2. The Check Results screen is displayed.

3. Check the results and correct the errors according to the messages.

Result
The data has been successfully checked.

Monitoring Replication Status (SAP CRM)


Use
This activity describes how to monitor the replication status in the SAP CRM.

SAP SE Page 21 of 26
SAP Best Practices CRM Customizing Replication (B09): Configuration Guide

Procedure
1. Access the activity using one of the following navigation options:
Transaction code R3AM1
SAP CRM GUI menu Architecture and Technology Middleware Data
Exchange Initial Load Monitor Objects

2. In the Object Name field, enter the downloaded object DNL_CUST_TAX to get the
download status of this object.

Result
The replication is complete if all objects have the status Done.

In case of problems during replication, call transaction SMWP (Middleware


Portal) and search for error states in the area Runtime Information.

Defining Tax Type and Group (SAP CRM)

Please check the Delta Guide.

Use
In this activity you establish the tax types with the relevant tax groups for products. The
assignment of the appropriate tax types and groups for Product and Business Partner serves
the purposes of tax determination.

The tax types/groups and the assignment of the business partner tax groups
have been maintained in the ERP system and have been replicated already from
the ERP system to the CRM system in the activity Replicating Tax Customizing.

Procedure
1. Check ERP tables TSTL and TSKM using transaction SE16.
2. In CRM, call transaction SM30. Specify view COMV_TAX_GROUP. Choose Maintain.
3. For each combination of Country, Tax Category and Tax Classification in the ERP system
(tables TSTL and TSKM) make sure a corresponding combination (of Country, Tax Type
and Product Tax Group) exists in the CRM (view COMV_TAX_GROUP). In case any
entry is missing, create it choosing New Entries.

Result
You have defined the tax types with the relevant tax groups for products.

SAP SE Page 22 of 26
SAP Best Practices CRM Customizing Replication (B09): Configuration Guide

Example of a correct mapping

Defining Assignment of Product Tax Data from ERP to CRM

Please check the Delta Guide.

Use
In this activity, you can assign the SAP ERP material tax classification (TAXMx) to the
combination of country, region (optional), tax type, and tax group defined in the SAP CRM
system in the IMG activity Defining Assignment of Tax Data for Products from ERP to CRM.
When data is imported from an SAP ERP system to an SAP CRM system, all existing tax data
in the SAP ERP system (table MLAN) is transferred to the SAP CRM system for each
material. This requires the tax settings to be assigned from the SAP ERP system to the SAP
CRM system correctly. If this is not the case, the data transfer process stops.

Procedure
1. Access the activity using the following navigation options:
Transaction code SPRO
SAP CRM IMG menu Customer Relationship Management Basic Functions
Taxes Basic Settings Tax Types and Tax Groups
Assign Tax Groups to SAP ECC Tax Classifications (Product)

2. Check tables TSTL and TSKM in the ERP system.


3. For each combination of country, tax category and tax classification in the tables TSTL
and TSKM you have to create an entry in the table CRMC_TAX_MAP in the CRM system
as follows:
4. Run IMG activity Assign Tax Groups to SAP ECC Tax Classifications (Product).
5. Choose New Entries.
6. Enter values for country, tax type, product tax group, tax sequence and tax classification.

Example:
In the SAP ERP client

SAP SE Page 23 of 26
SAP Best Practices CRM Customizing Replication (B09): Configuration Guide

Table TSKM
TATYP TAXKM
CTX1 0
CTX1 1
CTX2 0
CTX2 1
CTX3 0
CTX3 1

Table TSTL
Country LFDNR TATYP
CA 1 CTX1
CA 2 CTX2
CA 3 CTX3

In the SAP CRM client


Table CRMC_TAX_MAP (assignment) which is also the IMG activity Assign Tax Groups
to SAP ECC Tax Classifications (Product)
Country Region Tax Type Tax Group Tax Seq. Tax Class.
CA CTX1 NON 1 0
CA CTX1 FULL 1 1
CA CTX2 NON 2 0
CA CTX2 FULL 2 1
CA CTX3 NON 3 0
CA CTX3 FULL 3 1

Result
The product tax data is maintained in the CRM system and synchronized with the ERP
system.
The tax information in the product master data will be downloaded in the following way:

SAP SE Page 24 of 26
SAP Best Practices CRM Customizing Replication (B09): Configuration Guide

SAP SE Page 25 of 26
SAP Best Practices CRM Customizing Replication (B09): Configuration Guide

4 Pre-Assembled Deployment
Use
If you follow the pre-assembled deployment approach, some parts of the SAP Best
Practices for CRM content are already activated, whereas others still need to be activated.
Therefore, all configuration tasks are classified into one of the following categories:
Pre-Assembly (Pre): Configuration tasks classified as Pre-Assembly have already
been executed and do not need to be re-activated during an implementation project.
Post-Processing (Post): Post-Processing configuration tasks still need to be
performed in the target system landscape.
Some tasks can be classified as both Pre-Assembly and Post-Processing; this
means that these tasks have been pre-assembled, but need to be checked and
potentially modified during the post-assembly phase.

ERP Integrated CRM Standalone


Configuration Task System
Pre Post Pre Post
Setting Up Error Handler (SAP CRM) X n.a. n.a. CRM
Deactivating Mapping Functions X n.a. n.a. CRM
Checking ISO Codes (SAP ERP) X X n.a. n.a. ERP
Checking Product Hierarchy Structure in OLTP (SAP X n.a. n.a. ERP
ERP)
Defining Product Hierarchy Structure (SAP CRM) X n.a. n.a. CRM
Defining Product ID Settings (SAP CRM) X n.a. n.a. CRM
Re-creating Content of Table CRMATAB (SAP CRM) X n.a. n.a. CRM
Replicating Customizing Objects from ERP OLTP to X n.a. n.a. CRM
CRM System
Monitoring Replication Status (SAP CRM) X n.a. n.a. CRM
Defining Filter for Import of Tax Types (SAP CRM) X n.a. n.a. CRM
Defining SAP CRM Tax Types (SAP ERP) X n.a. n.a. ERP
Defining Business Partner Tax Groups (SAP ERP) X n.a. n.a. ERP
Defining BP Tax Classification Assignment Settings X n.a. n.a. ERP
(SAP ERP)
Replicating Tax Customizing (SAP CRM) X n.a. n.a. CRM
Checking Customizing of Data Transfer for Taxes X n.a. n.a. CRM
(SAP CRM)
Monitoring Replication Status (SAP CRM) X n.a. n.a. CRM
Defining Tax Type and Group (SAP CRM) X n.a. n.a. CRM
Defining Assignment of Product Tax Data from ERP X n.a. n.a. CRM
to CRM

SAP SE Page 26 of 26