Setup and Load Guide

(SLG)

Last Updated: June, 5th 2002

™
SAP CRM Setup and Load Guide

Copyright

©Copyright 2000 SAP AG. All rights reserved.

No part of this brochure may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP AG. The information contained herein may be
changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary
software components of other software vendors.

Microsoft®, WINDOWS®, NT®, EXCEL®, Word® and SQL Server® are registered
trademarks of Microsoft Corporation.

IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®,
AS/400®, OS/390®, and OS/400® are registered trademarks of IBM Corporation.

ORACLE® is a registered trademark of ORACLE Corporation, California, USA.

INFORMIX®-OnLine for SAP is a registered trademark of Informix Software Incorporated.

UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of The Open Group.

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide
Web Consortium, Laboratory for Computer Science NE43-358, Massachusetts Institute of
Technology, 545 Technology Square, Cambridge, MA 02139.

JAVA® is a registered trademark of Sun Micro systems, Inc., 901 San Antonio Road, Palo
Alto, CA 94303 USA.

JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for
technology invented and implemented by Netscape.
SAP, SAP Logo, [Link], [Link] Marketplace, [Link] Workplace,
[Link] Business Scenarios, [Link] Application Hosting, Web Flow, R/2, R/3,
RIVA, ABAP, SAP Business Workflow, SAP Early Watch, SAP Archive Link, BAPI,
SAPPHIRE, Management Cockpit, SEM, are trademarks or registered trademarks of SAP AG
in Germany and in several other countries all over the world. All other products mentioned are
trademarks or registered trademarks of their respective companies.

SAP AG page 2
SAP CRM Setup and Load Guide

Icons

Icon Meaning
Caution

Example

Note

Recommendation

Syntax

Tip

SAP AG page 3
SAP CRM Setup and Load Guide

1 INTRODUCTION .......................................................................................6
1.1 Setup activities after the installation.........................................................................................7
1.1.1 Generating Industry-Specific Runtime Objects ..................................................................11
1.1.2 Regenerating Filter Objects After Client Copy ..................................................................12

1.2 Site IDs and Subscription setting ............................................................................................12

1.2.1 R/3 Site definition...............................................................................................................12
1.2.2 Mobile Client Site definition ..............................................................................................14
1.2.3 Subscriptions ......................................................................................................................15

2 APPLICATIONS COMPONENT INITIAL LOAD TO CRM SERVER AND

TO CDB .........................................................................................................17
2.1 Preparing for Initial load .........................................................................................................17
2.1.1 Performance and Database issues .......................................................................................17
2.1.2 Setting up the Middleware for Master Data transfer...........................................................19

2.2 The flows of the objects loading ..............................................................................................27

2.2.1 Customizing objects ...........................................................................................................28
2.2.2 Business Application objects..............................................................................................35

2.3 Configuration & Customizing initial load ..............................................................................37

2.3.1 Manual definition of the product hierarchy structure .........................................................37
2.3.2 Definition of the product key (length, display, save) in CRM............................................40
2.3.3 Definition of the plant.........................................................................................................40
2.3.4 Initial Customizing load .....................................................................................................40
2.3.5 Mapping Account group and classification for business partners ......................................42
2.3.6 Setup Taxes ........................................................................................................................49
2.3.7 Define Assignment of Tax Data for products from R/3 to CRM........................................52
2.3.8 Define Assignment of Tax Data for Tax Condition Records from R/3 to CRM ................54

2.4 Setting up the Organizational Management ..........................................................................56

2.4.1 Analysis of the relevant sales areas in OLTP .....................................................................58
2.4.2 Definition of the replace division in CRM .........................................................................58
2.4.3 Definition of the Distribution Channel in CRM .................................................................59
2.4.4 Maintain Organizational Model (Root definition) ..............................................................59
2.4.5 Creating sales organizations ...............................................................................................60

2.5 Application Data (initial) .........................................................................................................64

2.5.1 Initial load of Customers ....................................................................................................65
2.5.2 Customer hierarchy and business partner group.................................................................69
2.5.3 Initial load of Plants............................................................................................................71
2.5.4 Initial load of Materials and Services .................................................................................75
2.5.5 Initial load of Conditions ....................................................................................................79
2.5.6 Initial load of further objects ..............................................................................................85

3 DELTA LOAD OF MASTER DATA.........................................................85

3.1 MW Server Job-Scheduling.....................................................................................................85
3.1.1 Overview ............................................................................................................................85
3.1.2 Statistics..............................................................................................................................86
3.1.3 Activate Delta Events .........................................................................................................86
3.1.4 Replication & Realignment Queues ...................................................................................87

3.2 Reduction of Log-Levels ..........................................................................................................88

SAP AG page 4
SAP CRM Setup and Load Guide

4 APPENDIX...............................................................................................90
4.1 Mapping Business Partner number ranges in R3 and CRM ................................................90
4.1.1 Business Partner Concepts in R/3 and CRM ......................................................................90
4.1.2 Defining Number Assignment Strategy for Business Partners ...........................................91
4.1.3 Mapping Business Partner Master Data from R/3 to CRM ................................................93
4.1.4 Identifying Relevant R/3 Account Groups .........................................................................94
4.1.5 Defining Number Ranges for CRM Business Partners (Part 1)..........................................94
4.1.6 Defining CRM Business Partners Groupings (Part 1) ........................................................94
4.1.7 Creating R/3 Reference Customer ......................................................................................95
4.1.8 Assigning Consumer to Reference Customer .....................................................................96
4.1.9 Creating Account Group for CRM Consumers ..................................................................96
4.1.10 Mapping R/3 Account Groups to CRM Classifications......................................................97
4.1.11 Mapping Business Partner Master Data from CRM to R/3 ................................................98
4.1.12 Defining Number Ranges for CRM Business Partners (Part 2)..........................................99
4.1.13 Defining CRM Business Partners Groupings (Part 2) ......................................................100
4.1.14 Creating R/3 Business Partner Number Ranges ...............................................................100
4.1.15 Creating R/3 Account Groups ..........................................................................................101
4.1.16 Mapping CRM Classifications to R/3 Account Groups....................................................102

5 CHECKLIST ..........................................................................................104
This checklist was developed to provide you with a list of sequential tasks for setting up the CRM
3.0 Server after the installation.........................................................................................................104

5.1 Setup activities directly after an installation or an upgrade of the CRM 3.0 Server........104

5.2 Site IDs and Subscription setting ..........................................................................................104

5.3 Preparing for Initial load .......................................................................................................104

5.4 The flows of the objects loading ............................................................................................104

5.5 Configuration & Customizing initial loa ..............................................................................105

5.6 Setting up the Organizational Management ........................................................................105

5.7 Application Data (initial) .......................................................................................................105

5.8 Delta load of Master Data ......................................................................................................106

6 CONTACT .............................................................................................107

SAP AG page 5
SAP CRM Setup and Load Guide

1 Introduction
This guide describes the necessary post-installations steps for the CRM component
landscape:
x The R/3 OLTP system where the R/3 applications are installed
x The R/3 OLTP plug-in where add-on functionality to the R/3 OLTP is installed
x The SAP CRM Server

The OLTP system in the above is the abbreviation of On-Line Transaction Processing
system and this guide will deal with the SAP R/3 OLTP system from now on.

Please make sure all available Support Packages have been applied, i.e. Support Packages
for OLTP, Support Packages for OLTP plug-in, Support Packages for the CRM Server, etc.
Also, please note that the latest qRFC version should be used in all systems. Please refer to
note 438015 to find the latest available qRFC version.
Also, please refer to note number 418886 to prevent major problems in the advanced steps of
the documentation.
In chapter "Solution" and the related notes you will get detailed information that you have to
consider before setting up a new CRM/EBP system

Integration of SAP CRM and SAP APO-ATP:

Please refer to the proper documentation for integration of SAP CRM with SAP APO-
ATP. You can access this documentation using SAP online help for SAP Customer
Relationship Management \ Basic Functions \ Availability Check \ Integration of
CRM and APO-ATP

SAP EBP:
The information in this guide applies to CRM.
Although customers with SAP EBP will find this guide contains some useful
background information, they should not perform any of the procedures described
here.

SAP R/3 PI (Plug-Ins)

For CRM and EBP functionality (Upgrading or new installation of PI), please
refer to note 0214503: “Release strategy for PI and PI-A add-ons”.
You can find detailed information regarding plug-ins on the SAPNet under the alias
R3-PLUG-IN.

SAP AG page 6
SAP CRM Setup and Load Guide

1.1 Setup activities after the installation

You must perform a number of activities in the CRM components. Details of these
configuration steps are described in the SAP Implementation Guide (IMG):
Customer Relationship Management o CRM Middleware and Related Components

For information on an activity, click on .

SAP AG page 7
SAP CRM Setup and Load Guide

The following screen contains sample IMG text.

SAP AG page 8
SAP CRM Setup and Load Guide

All the activities you may need to perform depending on your CRM landscape are outlined in
CRM Middleware and Related Components.
x In the CRM Server
You need to perform all the relevant steps described under the main chapters:
I. Generating industry-specific objects and services
II. Communication Setup
1) Set up logical systems
2) Create RFC users
3) Define RFC destinations
4) Define Middleware parameters
a) Logical system name for Mobile Clients
b) BW communication
c) BW customer fact sheet
d) APO communication
e) OLTP R/3 customer fact sheet and order status
f) OLTP R/3 credit check
g) Internet Pricing and Configurator communication

This activity can also be performed by using transaction R3AC6 - Define Middleware
Parameters.

For more detail about the Middleware configuration, please refer to the Adapter
Framework documentation (You can access this documentation using SAP online
help for SAP Customer Relationship Management \ Basis Technology \ CRM
Middleware \ Adapter And Site Types \ Adapters \ The Adapter Framework ).
III. Queue Setup
IV. Error Handler Setup
V. Mobile Scenario Setup
VI. External Data Load
VII. Check ISO Codes
VIII. Reorganization

x In the OLTP R/3 system

You must perform the following activities.

Read the relevant descriptions for the following setting activities for the OLTP, R/3
system which are described in the IMG of the CRM system under CRM Middleware
and Related Components:
- Set Up Logical Systems
- Create RFC users
- Define RFC destinations

SAP AG page 9
SAP CRM Setup and Load Guide

- Define R/3 Back-End Parameters

To define the OLTP R/3 parameters

o You need to maintain two tables, ‘CRMCONSUM’ and ‘CRMRFCPAR’ by using
the transaction code SM30 in the OLTP system. To work with this, please make
sure you have installed the latest available plug-in version.
o The following parameter must be entered in CRMPAROLTP on R/3.
o CRM_NO_BEFORE_IMAGES
ƒ Parname2 : SALESDOCUMENT
ƒ Parval1 : X
ƒ Consumer : CRM

In other CRM components (such as BW, APO) you must at least set up logical systems,
create RFC users, and define RFC destinations to enable communication. Details of the
above steps can be found in the IMG under SAP Web Application Server o Distribution
(ALE) o Sending and Receiving Systems.

SAP AG page 10
SAP CRM Setup and Load Guide

1.1.1 Generating Industry-Specific Runtime Objects

The following information on industry parameters does not apply to EBP.

The industry template should not be changed once it has been generated in case the
subscriptions for the site have been maintained.

The description for the sites and subscriptions will be followed in the next chapter.

x To perform the following steps, your logon language should be English so that you
can obtain complete message information.

x Industry-specific runtime objects must be generated only once because they are
client-independent. That means, for instance, if you specify PH for pharmaceutical
industry in clients 100 and 200 of your CRM system, you need to generate the
industry-specific objects either in client 100 or 200.

x Go to transaction /nSM30 and choose the table name ‘SMOHPARIND’ to set industry-
Specific runtime object for your CRM system.

x Make sure the client in which you create these objects allows changes to repository
and cross-client configuration (SAP Implementation Guide: Basis o System
Administration o Change and Transport System o Configure Clients).

SAP AG page 11
SAP CRM Setup and Load Guide

1.1.2 Regenerating Filter Objects After Client Copy

Generating all filters separately is normally not necessary because the filter objects are part of
the initial installation. Filters need only to be regenerated if you make a client copy.
For example, if you work in the CRM system in client 100, and make a new copy to another
client 200, then you have to regenerate the filter objects.

Use the standard generating transaction:

1. Call the generation Workbench (Transaction GNRWB or from the SAP Menu:
Middleware Î Development Î Generation Î Generation Î Generation
Workbench).
2. Select the generator group R3ADP R/3 Adapter.
3. In the left-hand frame select all the BDocs and in the right-hand frame select
R3ADP_FILTER.
4. Click on Generate.
For more details, see the Adapter framework documentation.

1.2 Site IDs and Subscription setting

As of SAP CRM 3.0, OLTP R/3 System has to be defined as a site, like the other systems of
the distribution model. CRM and CDB sites are already predefined so you need only to create
the R/3 site and Mobile client sites.
Once you have created the sites, you then have to define the distribution rules
(subscriptions), which determine which data a site is to receive.

x All of the objects have to be loaded to the CRM system first, even though you wish to
load the data from the OLTP system to the CDB. There are two steps for loading the
data:

The first step is from OLTP to CRM system applications component (site type CRM)
and the second step is from CRM system to CDB.
You access to the site definition from the CRM menu, Middleware o Administration
o Administration console (Transaction code: SMOEAC)

1.2.1 R/3 Site definition

Please note that RFC Destination for connection to OLTP R/3 must be defined before
performing R/3 Site definition
1. Choose object type in left screen as Sites

SAP AG page 12
SAP CRM Setup and Load Guide

2. Choose Create icon,

3. Type the name of the site and the description and choose the site type R/3.

4. Choose ‘site attributes’ next to site type.

5. Enter the RFC destination for the site.

SAP AG page 13
SAP CRM Setup and Load Guide

6. Press Button 'Get values' then the R/3-Release and Logical System fields should be
automatically filled.
7. Save the new created site.

1.2.2 Mobile Client Site definition

When creating a Mobile Client Site type,
1. Choose the object type as Sites.

2. Choose Create icon, .

3. Define the name of the Mobile client.
4. Select the type as Mobile client.
5. Click the Site Attributes button and you will see the popup box indicating the Connection
group and the Transfer group, as below.

SAP AG page 14
SAP CRM Setup and Load Guide

1.2.3 Subscriptions
After the definition of the R/3 OLTP and Mobile client sites you need to create subscriptions
by subscription wizard. It should be done in the same screen like the site definition. Choose
the object type as Subscriptions and follow the subscription wizard instructions, which will pop
up when you choose create icon. This is necessary to enable uploading of the data from
CRM to OLTP.

Please note that the Middleware functionality does not allow automatic upload of a
product from a CRM to an R/3 OLTP system. You can only upload a single product using the
transaction COMMPR01 - Maintain Products.

Upgrade issue
Please note that as of SAP CRM 3.0 the edit functionality for subscriptions is not part of the
subscription wizard.

How to upload orders or business partners from CRM to OLTP

With the Administration Console, create subscriptions for the publication ‘All Business
Partners (MESG)’ and ‘All business transactions (MESG)’ and assign it to your OLTP sites.
Please note that you need to create subscriptions for publications of type Simple intelligent
(msg) and Simple bulk (msg), whose replication objects are assigned to site type R/3 in the
BDoc Modeler and which you would like to upload.

SAP AG page 15
SAP CRM Setup and Load Guide

Please refer to the Administration Console documentation for further information on how to
create subscriptions.
The business and condition objects that can be loaded from CRM to OLTP, or CDB to CRM,
are available for viewing under SAP Menu Æ Middleware Æ Data exchange Æ Object
management. (See whether ‘Upload mapping modules’ depend on the source and target
systems for each object maintained.)

SAP AG page 16
SAP CRM Setup and Load Guide

2 Applications Component Initial Load to CRM

server and to CDB
The following sections describe the initial load into the CDB and into CRM Server Applications
Component (site type CRM). Support for initial load problems regarding configuration
/configuration problems of the CRM system is given on the OSS component CRM-MD, e.g.
CRM-MD-BP for Business Partners or CRM-MD-PRO for Products.

General OSS note for analyzing the problems, which might occurs during the data
exchange between a CRM and an OLTP R/3 system is 443900.

For the initial load you should activate full middleware tracing in order to record CRM
application errors and detailed information.

Select Middleware o Administration o Define Middleware Parameters and set the

trace level by adding an entry in table SMOFPARSFA with the key CRMGENERAL.
e.g.:
Column Setting
Key CRMGENERAL
Paramname TRACE LEVEL
Paramname2  ENV=I
Paramname3 CMP=*
Paramval Level= 3

For more precision on how to set the middleware trace monitor please refer to the
online documentation: SAP Customer Relationship Management \ Basis
Technology \ CRM Middleware \ System Monitoring \ Monitoring the Message
Flow \ The Middleware Trace Monitor

2.1 Preparing for Initial load

2.1.1 Performance and Database issues

Please refer to the note 350176 for performance improvement.

[Link] Oracle Database: Optimizing the OLTP load time

To optimize OLTP load time set the parameter optimizer_index_cost_adj in file init<SID>.ora
to value 10.

For further information see SAP Note 114716

[Link] Oracle Database: Starting Initial load

In order to avoid time-out problems on the CRM Middleware server during initial load on an
Oracle database, start a report. This deletes Oracle index statistics on the CRM Middleware
Server (see also note 162956).

SAP AG page 17
SAP CRM Setup and Load Guide

[Link] MS SQL Server: Adding a Startup Parameter

1. Access the SQL Server Enterprise Manager
2. Add startup parameter -p.

SAP AG page 18
SAP CRM Setup and Load Guide

2.1.2 Setting up the Middleware for Master Data transfer

[Link] Configuring the CRM server for message processing
The server requires jobs and RFC destinations for automatically processing messages that
are stored in internal queues, one for reorganizing log data and a further one for handling
statistics updates.

1. Creating RFC destinations for Replication &Realignment Queues

One RFC destination has to be created for client 000 and each other client running
SAP CRM Middleware.
a. Log on to the CRM server.
b. Start transaction SM59.
c. Click on RFC destinations.
d. Choose Create.
e. Enter the following data:
i. RFC Destination:
You have to adapt the following naming convention SAPCRM_MW_RR_<client>,
e.g. SAPCRM_MW_RR_000.
ii. Connection type: L
iii. Logon frame:
In the frame Logon you have to enter the log on data of the user of the
Replication and Realignment work processes.
The language field is supposed to be blank.

SAP AG page 19
SAP CRM Setup and Load Guide

iv. Save your settings.

2. Maintain number range objects for the Replication & Realignment Queues
For each of your middleware clients you have to maintain five number range objects
(each object refers to a specific internal Replication & Realignment Queue) in order to
handle the work processes of each queue in the right sequence.
a. Log on to the CRM server.
b. Start transaction SNRO.

SAP AG page 20
SAP CRM Setup and Load Guide

c. Enter object RRSEQ_AC.

d. Click Number ranges.
e. Click Change intervals.
f. Click Insert Interval.
g. Enter the following:
No From number To number
1 00000000000000001 9999999999999999

h. Save your entries.

i. Repeat steps a to h for each of the following objects:
x RRSEQ_SU
x RRSEQ_RE
x RRSEQ_EX
x RRSEQ_EB

NEVER transport the number range intervals, because the actual counter status
will be transported too, which may cause mistakes in the target system.
3. Creating background job for Reorganization

SAP AG page 21
SAP CRM Setup and Load Guide

Depending on the selected level for tracing and logging, the system writes many
entries into internal tables.
This job triggers reports for reorganization of log data and trace data.
a. Log on to the CRM server.
b. Start transaction SM36.

SAP AG page 22
SAP CRM Setup and Load Guide

Enter the following entries:

Name: MW_REORG
Steps: ABAP-Program Name SMO6_REORG
Variant SAP&_MW_REORG
Start- Date/Time Once a day
Date:

Starting SMO6_REORG with variant SAP_MW_REORG will delete all entries

older than 7 days.
If you prefer to use a different time period or in case the variant does not exist in
your system, please create another variant with a different variant name and time
period by using the transaction SE38.

Please refer to note 206439 for more details.

SAP AG page 23
SAP CRM Setup and Load Guide

[Link] Workflow Customizing

1. Log on to the CRM system
2. Enter /n in the transaction code field.
Perform the following activities.

1. Automatic configuration
Enter /n in the transaction code field
Transaction code: SWLD and select Utilities o Automatic Workflow Customizing

Choose the icon to activate auto configuration after putting your cursor on the object you
wish to perform auto configuration.

SAP AG page 24
SAP CRM Setup and Load Guide

2. Creating the Workflow User

Transaction code: SU01
User name: wf-batch
Password: <XXX>
User type: CPIC
Profiles: SAP_ALL, SAP_NEW
3. RFC destination
Transaction: SPRO (IMG)
In CRM IMG, choose SAP Implementation Guide o Basis o SAP Business Management o
SAP Business Workflow o Basic Settings (System, SAP Business workflow) o Create
logical System for tRFC
Activity: Create logical destination for RFC
Assign the password <XXX> to user wf-batch

[Link] Error Handler Setup

1. E-mail recipient
An e-mail recipient must be determined for each BDoc type. This recipient automatically
receives messages in case of errors in the connected BDoc.
Transaction: SMW00 in CRM system
‰ Pick the default tab, choose the mail column and click the ‘Detail’ button.

SAP AG page 25
SAP CRM Setup and Load Guide

‰ Enter mail recipient in the Receiver field.

2. Choose the other tabs.

‰ Mass maintenance can be performed by choosing edit Æ mark all and edit Æ complete
actions.

SAP AG page 26
SAP CRM Setup and Load Guide

2.2 The flows of the objects loading

x You may check the flow, source, and destination site for the objects by checking the
table ‘SMOFINICON’ from transaction /nse16.
x For further details, refer to the Adaptor framework documentation.

SAP AG page 27
SAP CRM Setup and Load Guide

2.2.1 Customizing objects

x The flow of data exchange
1. From the OLTP to the CRM:

OLTP

Data
Request CRM

Mapping

Finished

CRM
Configuration
Table

Relevant objects:
Source Target Object Name Description
site site
OLPT CRM DNL_CUST_ACGRPP Account Group Product
OLPT CRM DNL_CUST_ADDR Regional structure
OLPT CRM DNL_CUST_BASIS Basis CRM online
OLPT CRM DNL_CUST_BASIS2 Basis CRM online
OLPT CRM DNL_CUST_BASIS3 Basis CRM online
OLPT CRM DNL_CUST_BASIS5 Basis CRM online
OLPT CRM DNL_CUST_BASIS6 Basis CRM online
OLPT CRM DNL_CUST_BNKA Banking Master
OLPT CRM DNL_CUST_CND Conditions: Cust. [Link].
OLPT CRM DNL_CUST_CNDALL Conditions: Customizing total
OLPT CRM DNL_CUST_FGD Free goods

SAP AG page 28
SAP CRM Setup and Load Guide

Source Target Object Name Description

site site
OLPT CRM DNL_CUST_PAYPL Payplan
OLPT CRM DNL_CUST_PRC Conditions: Cust. Pricing
OLPT CRM DNL_CUST_PRICE Sales pricing and pricing item
OLPT CRM DNL_CUST_PROD0 Material number conversions
OLPT CRM DNL_CUST_PROD1 Product : categories
OLPT CRM DNL_CUST_PROD3 Material : R/3 sales status
OLPT CRM DNL_CUST_SALES Sales
OLPT CRM DNL_CUST_SCE SCE varcond
OLPT CRM DNL_CUST_SHIP Sales shipping
OLPT CRM DNL_CUST_SPROD Sales product item
OLPT CRM DNL_CUST_SRVMAS Customizing: Service Master
OLPT CRM DNL_CUST_T502T Business Partner: T502T
OLPT CRM DNL_CUST_TAX Customizing: Taxes
OLPT CRM DNL_CUST_TBRC Business Partner: Industries
OLPT CRM DNL_CUST_TPFK Business Partner: TPFK, TPFKT
OLPT CRM DNL_CUST_TSAB Business Partner: TSAB, TSABT
OLPT CRM DNL_CUST_TVAST Sales Document Blocking Reason
OLPT CRM DNL_CUST_TVFS Sales Document Billing: Block
OLPT CRM DNL_CUST_TVGF Business Partner: TVGF, TVGFT
OLPT CRM DNL_CUST_TVIP Business Partner: TVIP, TVIPT
OLPT CRM DNL_CUST_TVLS Deliveries: Blocking Reasons/C
OLPT CRM DNL_CUST_TVPV Business Partner: TVPV, TVPVT

SAP AG page 29
SAP CRM Setup and Load Guide

2. From the CRM to the CDB:

Please, note that the load of objects from CRM to CDB is not necessary if you are not
using CRM Mobile scenario.

CRM

Data
CDB
Request

Mapping

Sync. Boc

CDB

Replication

Outbound

Clients

Relevant objects
Source Target Object Name Description
site site
CRM CDB BOTVAK_OBJECT BOTVAK_OBJECT
CRM CDB BOTVAPO_OBJECT ATP Profile per line item cate
CRM CDB CRM_DNLPRDOBJFA Product Object Family
CRM CDB CRM_DNLPRDSCHEM Numbering Scheme for Hierarchy
CRM CDB CRM_DNLPRODTYPE Definition of Product Types
CRM CDB CRM_DNLSUBJPROF Subject profile
CRM CDB CRM_DNL_ACT_CAT Activity Category
CRM CDB CRM_DNL_ACT_H Activity
CRM CDB CRM_DNL_ACT_OBJ Activity Objective

SAP AG page 30
SAP CRM Setup and Load Guide

CRM CDB CRM_DNL_ACT_PRI Activity Priority

CRM CDB CRM_DNL_BNKA Banking Master
CRM CDB CRM_DNL_CODEPRG Code Profile
CRM CDB CRM_DNL_CODEPRO Code Profile
CRM CDB CRM_DNL_COPYCU Service Transtion type
CRM CDB CRM_DNL_CYCLE Sales cycle of the Opportunity
CRM CDB CRM_DNL_CYCPHAS Sales cycle of the Opportunity
CRM CDB CRM_DNL_ICATEG Service Item Category Group
CRM CDB CRM_DNL_ITMTYPE Item type
CRM CDB CRM_DNL_IT_ASSG Item Assignment
CRM CDB CRM_DNL_OPPIPOR Opportunity Class
CRM CDB CRM_DNL_OPPORTH Opportunity header customizing
CRM CDB CRM_DNL_OPPTYPE Object/Opportunity Sub-Type
CRM CDB CRM_DNL_ORGMAN CRM_DNL_ORGMAN
CRM CDB CRM_DNL_PAR_FCT Partner function
CRM CDB CRM_DNL_PAR_PDD Partner determination definiti
CRM CDB CRM_DNL_PAR_PDP partner determination procedur
CRM CDB CRM_DNL_PHASE Funnel Phase
CRM CDB CRM_DNL_PPFTCON PPF: Actions
CRM CDB CRM_DNL_PPFTCU PPF: Trigger type
CRM CDB CRM_DNL_PRDCT Service Valuation types
CRM CDB CRM_DNL_PRDOBJF Product Object Family
CRM CDB CRM_DNL_PROCTYP Process Type
CRM CDB CRM_DNL_PRODUCT Material number conversions
CRM CDB CRM_DNL_PRT_PFT MSE Partner Function Categorie
CRM CDB CRM_DNL_QPC Code
CRM CDB CRM_DNL_QPG Code Group
CRM CDB CRM_DNL_SCAPPT Appointment type
CRM CDB CRM_DNL_SLSITEM Sales item customizing
CRM CDB CRM_DNL_SOURCE Opportunity source
CRM CDB CRM_DNL_SRVCUST Service Header Customising
CRM CDB CRM_DNL_SRV_TY Service types
CRM CDB CRM_DNL_STAREAS Status Reason
CRM CDB CRM_DNL_SUBOB Service Object types for BTH
CRM CDB CRM_DNL_SUBOB_I Service Object types for BTI
CRM CDB CRM_DNL_TAXCNT TB070
CRM CDB CRM_DNL_TAXCN_T TB070T
CRM CDB CRM_DNL_TEXT_O Text Object Definition

SAP AG page 31
SAP CRM Setup and Load Guide

CRM CDB CRM_DNL_TEXT_P Text determination procedure

CRM CDB CRM_DNL_TG_TT TB071
CRM CDB CRM_DNL_TIMECTE Date set profile
CRM CDB CRM_DNL_TJ02 System Status
CRM CDB CRM_DNL_TJ20 Status profile
CRM CDB CRM_DNL_TJ30 User Status
CRM CDB CRM_DNL_TQ15 Code Catalog type
CRM CDB CRM_DNL_TTXID Texts on text ID's
CRM CDB CRM_DNL_TTXOB Defaults for object types
CRM CDB CRM_DNL_VAL_TY Service Valuation types
CRM CDB CRM_TTE_CNTDEP Country dependent customizing
CRM CDB CRM_TTE_COMMUNI Community
CRM CDB CRM_TTE_INTDATA Cust. Int Data
CRM CDB CRM_TTE_MAP Cust. Mapping
CRM CDB CRM_TTE_SYSDATA Cust. System Data
CRM CDB CRM_TTE_TAXABIL Cust. Taxability
CRM CDB CUST_CHAN_WRITE Campaign channels
CRM CDB CUST_CTYPT_WRT Campaign Type
CRM CDB CUST_PCAUT_WRT Campaign authorization
CRM CDB CUST_PCOBJ_WRT Campaign Objective
CRM CDB CUST_PCTAC_WRT Campaign Tactics
CRM CDB CUST_PRCPROCDET Determination of Pricing Proce
CRM CDB CUST_PRCPROC_DE CUST_PRCPROC_DET-SalesDoc
CRM CDB CUST_PRIOR_WRT Allocation Priority
CRM CDB CUST_PRIOTX_WRT Campaign Priority
CRM CDB CUST_STUS_WRITE Allocation itrem status
CRM CDB DNLITEMSTATUS Opportunity item status
CRM CDB DNL_CRM_IBA_CTY Ibase(service) component Type
CRM CDB DNL_CRM_IBA_TYP Ibase Types
CRM CDB DNL_CUST_ART_NO Product : categories
CRM CDB DNL_CUST_AU_CON Sales Document Types: Texts
CRM CDB DNL_CUST_BNKA1 Banking information CRM->CDB
CRM CDB DNL_CUST_CLASS Sales
CRM CDB DNL_CUST_COUNTR Business Partner :T005 series
CRM CDB DNL_CUST_CREDIT Business Partner: TFACT
CRM CDB DNL_CUST_CURREN Currency
CRM CDB DNL_CUST_CUST1 Business Partner: 151,188,189
CRM CDB DNL_CUST_CUST2 Business Partner: TPRIT

SAP AG page 32
SAP CRM Setup and Load Guide

CRM CDB DNL_CUST_CUST3 Business Partner :TVGFT

CRM CDB DNL_CUST_GLOBAL Business Partner: TSAB, TSABT
CRM CDB DNL_CUST_INDUST Business Partner: T016T
CRM CDB DNL_CUST_IT_CAT Sales document item categories
CRM CDB DNL_CUST_LANGU Business Partner: T002, T002T
CRM CDB DNL_CUST_MAT1 Sales shipping
CRM CDB DNL_CUST_MTART Item Category Group
CRM CDB DNL_CUST_PAFUNC Partner Function Groups
CRM CDB DNL_CUST_PERS1 Business Partner: TPKFT, SABT
CRM CDB DNL_CUST_PERS3 Business Partner: TB010
CRM CDB DNL_CUST_SD_CON DNL_CUST_SD_CON
CRM CDB DNL_CUST_SD_OR1 Business Partner: Vast
CRM CDB DNL_CUST_SD_OR2 Business Partner : VFST
CRM CDB DNL_CUST_STOCK Process Type
CRM CDB DNL_CUST_SYSMSG Messages
CRM CDB DNL_CUST_SYS_TB Contains SMONRIV
CRM CDB DNL_CUST_UNITS

SAP AG page 33
SAP CRM Setup and Load Guide

3. From the OLTP to the CDB

Be aware of that some of the few objects that are only relevant for mobile are
considered for this scenario.

OLTP

Data
Request CDB

Mapping

Sync. BDoc

CDB

Replication

Outbound

Clients

SAP AG page 34
SAP CRM Setup and Load Guide

2.2.2 Business Application objects

OLTP

Data CRM
Request

Mapping

Messaging Bdoc

Flow

Validation
service
Flow
Messaging Bdoc
Sync. Bdoc
Mobile
‘ON or OFF’ Bridge CDB
S-Flow

Replication
Replication and
Realignment

Outbound
Outbound

Clients
Clients

When the mobile bridge is activated, the objects for loading are automatically loaded to the
CDB. In the other case, you need to load the data in two ways, for example, one from the
OLTP to the CRM and the other one from the CRM to CDB.
To see or modify the mobile bridge,
1. Go to the transaction code /nsm30.
2. Type the table name ‘SMW3FDCUST’.

SAP AG page 35
SAP CRM Setup and Load Guide

3. Select the Bdoc type in the list.

4. If there is no entry, it means that the mobile bridge is deactivated or does not exist. If
there are some entries, see the flag ‘Active’ (drag the scroll button to the right or make the
table narrower). According to the ‘Active’ field checkbox, the mobile bridge can be
activated or deactivated.

Please refer to notes 430392 and 446899 for more detailed information about Mobile
Bridge Customizing.

SAP AG page 36
SAP CRM Setup and Load Guide

2.3 Configuration & Customizing initial load

2.3.1 Manual definition of the product hierarchy structure

The R/3 product hierarchy together with material group and material type is used for Mobile
client configuration.
Each product category has to have a product category ID. This ID can be assigned according
to a numbering scheme. The IDs of the lower-level categories contain the ID of the higher-
level category as a prefix, and differ in the digits following the prefix.

Example:
x 01 Printers
- 0101 Monochrome printers
* 010101 Dot matrix printers
* 010102 Ink jet printers
* 010103 Laser printers
- 0102 Color printers
* 010201 Color ink jet printers
x 02 Hard disks
As a result the structure of the hierarchy is coded by the category IDs, making it possible, for
example, to select sub-trees in the hierarchy easily. In the above example, all monochrome
printers can be selected as 0101*.
In this step, you define a numbering scheme. You decide on the maximum number of levels
the hierarchy is to contain and specify how many digits are assigned at each level.
a. In the OLTP system

Enter transaction code SE11

‰ View: PRODHS

SAP AG page 37
SAP CRM Setup and Load Guide

‰ Define the field length for each of the components (PRODH1~ PRODH9, PRODHX).
‰ The number of the components stands for the number of level in CRM.

b. On CRM online
IMG Æ Customer relationship management Æ Master data Æ Product Æ Product category Æ
Define category numbering schemes

SAP AG page 38
SAP CRM Setup and Load Guide

‰ Create a new entry for numbering schemes with the name R3PRODHIER and add a
description as numbering scheme
‰ Click on ‘R3PRODHIER’ that you have created and choose the left dialog structure,
Define Numbering Scheme Levels. The levels and number of digits for each level need to
be exactly the same as in the OLTP system (for example, 5-5-8 for SAP standard
delivery).

SAP AG page 39
SAP CRM Setup and Load Guide

2.3.2 Definition of the product key (length, display, save) in

CRM

In this activity, you define:

x How the product ID appears on the interface
x How the product ID is saved in the database (essential in the case of purely numeric
product IDs)

No presetting has been made in the standard system because of the critical nature of
Implementation activity. In particular, it requires you to decide carefully whether
product IDs are to be stored lexicographically or not because this decision can no
longer be changed once purely numeric product IDs have been created.
Unless you define the product ID length otherwise, the system assumes a length of
40 characters.

‰ In the Implementation Guide, choose CRM o Master data o Product o Basic settings o
Define Output Format and Storage Form of Product IDS.
The entry should have a Prod. ID length of ”18”, or less than “18” depending on the R/3
definition, in order to connect to an R/3 system. Create this entry if it does not exist.

2.3.3 Definition of the plant

Unlike the R/3 OLTP system, the plant is not regarded as a configuration object, but as a
business application object in the CRM system. Refer to chapter 2.5.4 to gain an idea how to
load the plant object from the R/3 OLTP system to the CRM system.

2.3.4 Initial Customizing load

Before the initial load of the other business objects is performed,

x You must evaluate whether filter conditions are useful for restricting the data for
content- and/or performance reasons. For details about filtering, please refer to the
Adapter Framework documentation.
x You have to verify that entries for the ISO codes are unique in the following tables:
x Unit of measures (T006 field ISOCODE); language keys (T002 field LAISO), currency
codes (TCURC field ISOCD) and countries (T005 field INTCA).
x Although SAP delivers these tables in a consistent state, duplicate ISO entries can
occur since this is not a key field in those tables (especially if a customer sets up own
entries with copy functions). Multiple entries with empty ISO codes are possible.
x Some more parameters have to be maintained dependent on the Release and
Support Package. The information given in the status line or message window
contains an OSS note. Please print out the OSS note and perform the necessary
steps.
1. Logon to the CRM server in English.

SAP AG page 40
SAP CRM Setup and Load Guide

2. Choose Middleware o Data Exchange o Initial load o Start.

3. Choose an object from the customizing objects you wish to load and Enter.

You can choose multiple customizing objects by using the report variant function.
4. Enter again to obtain source and destination site automatically when the object has
unique source and destination sites.

Choose possible entries (F4) for the object source and destination sites if the object has
multiple source and destination sites, pick the source and destination site you wish to
transfer from the possible entries.

5. Choose execute (F8) and watch the status line for messages (logon in English
necessary)
6. Repeat steps 4 to 6 for all customizing objects individually.
7. To check whether the load was successful: Choose Middleware -> Data Exchange ->
Initial load -> Monitor Objects. Here you can check the status of the initial load for all
objects. The initial load of customizing tables is successfully completed only if all traffic
lights have become “green”. In the event of problems (yellow or red lights) please read
note 0309734 (e.g. see inbound queue SMQ2 on the CRM system). Finally, if all
customizing objects have been loaded successfully, compare the entries of the following
tables in CRM and R/3 OLTP. The number of entries should be identical:
CRM R/3
TZONE TZONE
BNKA BNKA
CRMC_PMNTTRMS T052

SAP AG page 41
SAP CRM Setup and Load Guide

Please note that there is no automatic delta load for customizing data. In order to obtain
actual customizing data from R/3 OLTP to CRM online, you need to follow the initial load
procedure once again. But for the delta load from CRM online to CDB, a comparison
mechanism is triggered. (See Adapter Framework documentation).

2.3.5 Mapping Account group and classification for business

partners

Please refer to the Appendix for more specific issue concerning Business Partner
Account group, classification and Numbering range.

[Link] Distribution of the BP master data from CRM to R/3 system

1. On the OLTP system

Enter the transaction code /nPIDE and choose CRM Æ R/3 Assign BP Classification to
account group and specify the account groups for consumer, customer, prospective
customer and competitor.

SAP AG page 42
SAP CRM Setup and Load Guide

1. Classification
The distribution of business partner master data from the CRM to the R/3 system depends on
the business partner classification as follows:

1. Consumer:
It is important to know whether the business partners in the business partner data that
you create in CRM as consumers are organizations or persons.
o Organizations are distributed to the R/3 system as business partner master
data for customers, and not for consumers. Therefore the sales area data
that was copied from the reference business partner to business partner
master records for consumers in CRM is distributed to customer master
records in the R/3 system. Create an account group in the R/3 system
specifically for business partner master records with the classification
Consumer: Organization of the CRM system. Do not use an existing account
group that you created in the R/3 system for customer master records for
consumers.
o Persons are distributed as business partner master data for consumers to the
R/3 system (as of Release 4.6). The sales area data copied from the
reference business partner to the business partner master records for
consumers in the CRM is not distributed to the customer master records in
the R/3 system. The sales area data for consumers in the R/3 system is
determined from the reference customer. For these data use an existing
account group you created as customer master records for consumers in the
R/3 system.
If you have maintained neither an account group for consumers, nor a reference
customer in the R/3 system, or if the release of your R/3 system precedes 4.6, do not
assign an account group for these data but use the new account group for both
situations, organizations or persons.

2. Customer:
Assign the account group that is relevant in the R/3 system for customers. This is also
assigned when the business partner is additionally classified as a prospective customer
and a competitor in the CRM system.

3. Prospective customer in CRM:

Assign the account group that is relevant in the R/3 system for prospective customers.
This is also assigned when the business partner is additionally classified as a
competitor in CRM.

4. Competitor:
Assign the account group that is relevant as competitors in the R/3 system.

2. Account group

If the account group is determined as the external number range assignment, the
customer number of the R/3 is created with the same number as the business partner
master record in the CRM system. Specify the account groups with external number
range assignment only when you are sure that the numbers of business partner master

SAP AG page 43
SAP CRM Setup and Load Guide

records from the CRM have not been assigned to the customer master records in the R/3
system.
SAP recommends you use the internal number range assignment.
Business partner master records that you have not specified as an account group cannot
be created as the customer master records in the R/3 system. In this case, the business
partner master data are not distributed from the CRM to the R/3 system.
To analyze the relevant account groups and assigned the number ranges,
1. Enter the transaction code /nOVT0

<The list of account groups>

SAP AG page 44
SAP CRM Setup and Load Guide

2. Choose the account group you want to analyze.

3. Go to the number range entry field and press ‘F4’.

Examples of R/3 Account Groups you can assign for different CRM classifications:
Classification Account Group
Consumer: Org. Z123
Customer 0001
Prospective customer 0005
Competitor 0006
Consumer: Person 0170

SAP AG page 45
SAP CRM Setup and Load Guide

Examples of R/3 account groups assigned by the system for different CRM classifications for
organizations:
Consumer: Org. Customer Prospective Customer Comp. R/3 Account Group
X Z123
X X Z123
X X Z123
X X Z123
X X X X Z123
X 0001
X X 0001
X X 0001
X X X 0001
X 0005
X X 0005
X 0006

Examples of R/3 account groups assigned by the system for different CRM classifications for
persons:
Consumer: Pers. Customer Prospective Customer Comp. R/3 Account Group
X 0170
X X 0170
X X 0170
X X 0170
X X X X 0170
X 0001
X X 0001
X X 0001
X X X 0001
X 0005
X X 0005
X 0006

SAP AG page 46
SAP CRM Setup and Load Guide

- There is no automatic comparison function of field settings between R/3 and

CRM system. For this reason you need to keep the identical settings for account
groups, for example, in the OLTP system and the BP roles in the CRM system.
- The settings you make here only affect the customer master record during its
creation in the R/3 system. The changes made afterwards to the business
partner master data in the CRM do not affect the account group when the data
are distributed to the R/3 system. Change the account group in the R/3 system
when you need to do it by choosing change account group (Transaction code
/nXD07).

[Link] Distribution of the BP master data from R/3 to CRM system

1. On the OLTP system

Enter the transaction code /nPIDE and choose R3 Æ CRM assign account grp. to
BP classification. Specify the classifications, the account groups and the number
range demarcation (internal or external).

SAP AG page 47
SAP CRM Setup and Load Guide

For each account group you specify the creation of business partner master records in the
CRM system as below:

1. Classification

Indicates how the business partner is used in the CRM.

Choose one of the following;
- Consumer
- Customer
- Prospective customer
- Competitor

2. Grouping

Determines the number range and the number range assignment

3. Number range assignment

The number range assignment determines whether the relevant grouping has an
external or internal number range assignment. If the number range assignment is
external, the business partner in the CRM system is created with the same
number as the customer in the R/3 system. Specify the groupings with external
number assignments only when you are sure that the numbers of the R/3
customer master records have not been assigned to a business partner in the R/3
system. SAP recommends you use an internal number range assignment.

2. On the CRM system

Business Partner Number range and Grouping should be maintained.

1. Choose the following menu path, IMGÆcross-application component Æ SAP
business partner Æ business partner Æ Basic settings Æ number ranges and
grouping Æ Define groupings and Assign number range.
2. Every business group has to have a standard internal or external number range by
indicating the radio button on the right hand side of the box.
3. If you load without choosing one of the radio buttons for each business group you will
see an error message, 'No internal standard grouping is maintained'.

For further information see SAP Note 317406

SAP AG page 48
SAP CRM Setup and Load Guide

Account Group Classification Grouping External Number Assignment

0005 Prospective customer 0001

0006 Competitor 0002

0003 Customer

0170 Consumer 0002

x Customer master records with account group 0005 in the R/3 system are created as
business partner master records with the classification Prospective customer and
grouping 0001 in the CRM system.
x Customer master records with account group 0006 in the R/3 system are created as
business partner master records with the classification Competitor and grouping 0002
in the CRM system.
x Customer master records with account group 0003 in the R/3 system are not created
as business partner master in the CRM system.
x Customer master records with account group 0170 in the R/3 system (the account
group for customer master records for the consumers) are created as business
partner master records with the classification Consumer and grouping 0002 in the
CRM system.

2.3.6 Setup Taxes

The tax classification has a new design in SAP CRM [Link] CRM system uses 20 digit fields
instead of one digit field for the tax classification. Therefore you need to perform mapping
activities for the Taxes.
From SAP CRM 3.0, the Customizing Object DNL_CUST_TAX includes additional tables
TB072_CM and TSTL.

There is no automatic generating and transferring function for all the configuration of 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 make more complex tax determinations, 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, whether a product is
fully or partly taxed or exempted from this tax.
This information is also used by a third party program that finally determines the applicable
tax rate.

Activities Data Transfer Taxes:

1. R/3 OLTP: Maintain Tax Types, Business Partner Tax Groups and the Assignment to
CRM
2. R/3 OLTP: Check Business Partner Tax Customizing (execute report with transaction
SE38: CRM_TAX_CUST_VALIDATE_BP)
3. Customizing Download Taxes (DNL_CUST_TAX)

SAP AG page 49
SAP CRM Setup and Load Guide

4. CRM: Maintain Product Tax Groups and the Assignment of Product relevant Tax
Data from R/3 to CRM
5. CRM: Check Business Partner Tax Customizing (execute report with transaction
SE38: CRM_TAX_CUST_VALIDATE)
6. CRM: Validation of Data Transfer Customizing

How does the transfer logic from R/3 OLTP to CRM work?
x Products: All existing material-based tax data (table MLAN) are transferred. To
function correctly the mapping of tax setup needs to be consistent on both sides.
Otherwise the data transfer stops.
x Business Partners: The mapping of the tax classification is already done in R/3. The
new configuration objects also have to be maintained in the R/3 system since the
business partner mapping is done in R/3 system (see chapter 2.3.5 in this guide). The
Configuration load imports data from TSTL in the R/3 into the CRM table, TB070 for
the Tax Types, TB071_CM in the R/3 into TB071 for the BP Tax Groups, and from
TB072_CM in the R/3 into CRMC_TAX_MAP_BP for the Mapping business 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 R/3 CRM
x Condition Records: The data transfer of Condition records for tax calculation
requires the mapping for Products and Business Partners.

What needs to be checked

x OLTP:
1. Check tables TSTL, TSKD and TSKM.
2. Maintain new configuration object table TB070_CM Tax Types (Input table TSTL) -
transaction PITC.
3. Maintain table configuration object TB071_CM BP Tax Groups (Maintain according to
table TSTL and TSKD) - transaction PITC -> (see next picture).
4. Maintain table configuration object TB072_CM Mapping BP Tax Classification R/3
CRM (Maintain according to table TSTL and TSKD) - transaction PITM.

SAP AG page 50
SAP CRM Setup and Load Guide

Example of correct mapping

SAP AG page 51
SAP CRM Setup and Load Guide

2.3.7 Define Assignment of Tax Data for products from R/3 to

CRM

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

You can assign the R/3 material tax classification (TAXM1) to the combination of country,
region (optional), tax type, and tax group defined in the CRM system in Customizing for Taxes
in Define Tax Types / Groups. This is important for transferring large amounts of data
simultaneously. Make sure that all combinations for materials in the R/3 OLTP exist and that
they are mapped in the two CRM tables.

Table CRMC_TAX_MAP_ALLOC can be maintained in the Implementation Guide, /nspro:

choose CRM o Basic Functions o Taxes o Data Transfero Define Assignment of Product
Tax Data from R/3 to CRM

SAP AG page 52
SAP CRM Setup and Load Guide

After the assignment has been done you can check it for correctness in the Implementation
Guide. Use transaction /nspro: choose CRM o Basic Functions o Taxes o Data Transfer
o Check Customizing Of Data Transfer
Please refer to the description in the Implementation Guide for detailed information.

Regions are not presently supported when data are loaded from R/3. To ensure
that data are synchronized correctly, create entries only where the region field is
blank.

CRM:
1. Maintain Product Tax Groups (Table CRMC_TAX_GROUP)
2. Maintain Mapping Product Tax Groups (Table CRMC_TAX_MAP)

Example of correct mapping:

SAP AG page 53
SAP CRM Setup and Load Guide

2.3.8 Define Assignment of Tax Data for Tax Condition

Records from R/3 to CRM

In this activity you can assign the R/3 BP relevant tax classification of tax condition records to
the combination of country, region (optional), tax type and tax group defined in the CRM
system in Customizing for Taxes in Define Tax Types / Groups. The initial load will import
these tables, please, check that these tables (V_TB071 and CRMC_TAX_MAP_BP) are
empty before you start the Import. There is no maintenance necessary in CRM!

Regions are not presently supported when the data are loaded from R/3. To
ensure that data are synchronized correctly, create entries only where the region
field is blank.

SAP AG page 54
SAP CRM Setup and Load Guide

Example of correct mapping:

CRM Condition
Cntry Tax Product BP Tax ... Rate
R/3 Condition Type Tax Group Group
Cntry Tax TAXM1 TAXK1 Rate DE MWST FULL FULL 16%
Category DE MWST HALF FULL 7%
DE MWST 0 1 0% DE MWST NONE FULL 0%
DE MWST 1 1 16%
DE MWST 2 1 7% Assignment of BP Data for condition R/3 -> CRM
Cntry Reg Tax BP Tax R/3 Tax R/3
R/3 Condition Type Group Category Classification
Cntry Region Tax TAXM1 TAXK1 Rate DE MWST FULL MWST 1
Category DE MWST NONE MWST 0
CA BC CTX1 0 0 0% CA CTX1 FULL CTX1 1
CA BC CTX1 1 0 0% CA CTX1 NONE CTX1 0
CA BC CTX1 0 1 0% CA CTX2 FULL CTX2 1
CA BC CTX1 1 1 7% CA CTX2 NONE CTX2 0
CA BC CTX1 0 2 0% CA CTX3 FULL CTX3 1
CA BC CTX1 1 2 7%
CA CTX3 NONE CTX3 0
CA MB CTX2 0 0 0%
CA MB CTX2 1 0 0%
CA MB CTX2 0 2 0% Product R/3 - CRM Assignment
CA MB CTX2 1 2 7% Cntry Reg Tax Tax R/3 Tax Tax R/3
Type Group Category Seq. Classification
DE MWST FULL MWST 1 1
DE MWST HALF MWST 1 2
DE MWST NONE MWST 1 0
CA CTX1 FULL CTX1 1 1
CA CTX1 NONE CTX1 1 0
CA CTX2 FULL CTX2 2 1
CA CTX2 NONE CTX2 2 0
CA CTX3 FULL CTX3 3 1
CA CTX3 NONE CTX3 3 0

SAP AG page 55
SAP CRM Setup and Load Guide

2.4 Setting up the Organizational Management

This is where you make the settings for organizational management and automatic
determination of organizational data in the business transaction.
You can distribute the organizational structure of your company from your leading system to
the CRM Online System or create it in configuration for CRM.
In the section Organizational Data Determination, you can maintain the determination rules
and organizational data profiles that you require for automatically determining organizational
units and other organizational data.

The following notes should be considered before you transfer the organizational data.
x 333144: Master data cannot be taken over because of missing organizational data
x 312090: Integration HR –BBP/CRM
x 323842: Organizational units with name length >35
All sales organizational configuration data in the OLTP are automatically transferred to the
CRM system while loading the configuration data from the OLTP to the CRM system.

Please note that there is no automatic transfer of the divisions and the distributions channels.
Therefore, you should maintain them manually before you transfer the sales organizations
(refer to chapter 2.4.2 for division and chapter 2.4.3 for distribution channel).

To execute the automatic organizational data transfer from the OLTP to the CRM system,
follow the menu from IMG o Customer Relationship Management o Master data o
Organization management o Data Transfer o copy R/3 sales structure in CRM system.

SAP AG page 56
SAP CRM Setup and Load Guide

SAP AG page 57
SAP CRM Setup and Load Guide

After you push the button ‘Generate’ the screen should appear as below:

In case you wish to have your own sales areas in CRM perform the following steps
2.4.1 to 2.4.5.

2.4.1 Analysis of the relevant sales areas in OLTP

In the OLTP R/3, the configuration of the organizational units in sales must be analyzed. This
includes the sales areas (sales organizations, distribution channels, divisions), sales offices
and sales groups.
Decide which sales areas you need to have in the CRM Online system.
If you only use one division in R/3 you can enter this division as a dummy division in CRM.

2.4.2 Definition of the replace division in CRM

Please note that there is no object for downloading division setting from OLTP R/3 to
CRM system, as it is not required to use divisions in CRM. Therefore, you need to
manually maintain division if you want to use them in CRM.

SAP AG page 58
SAP CRM Setup and Load Guide

Defining the replace division for data exchange with OLTP R/3:
To define the replace division in Configuration (IMG = Transaction SPRO) in CRM system,
Choose CRM o Master Data o Organizational Managemento Division settings o Define
Division. You can find further information in the IMG documentation for the activity Division
Settings

2.4.3 Definition of the Distribution Channel in CRM

Please note that there is no object for downloading Distribution Channel setting from
OLTP R/3 to CRM system. Therefore, you need to manually maintain Distribution
Channel in CRM.
Defining the Distribution Channel for data exchange with OLTP R/3:
To define the Distribution Channel in Configuration (IMG = Transaction SPRO) in CRM
system,
Choose CRM o Master Data o Organizational Managemento Organizational Data for Sales
Scenario o Define Distribution Channels. You can find further information in the IMG
documentation for this activity.

2.4.4 Maintain Organizational Model (Root definition)

In the Configuration IMG, choose
CRM o Master Data o Organizational Management o Organizational Model o Create
Organizational Model.

1. Confirm the date.

A root organization is automatically created.

2. Enter an abbreviation and a name for the organizational unit

(You can also enter a description)

SAP AG page 59
SAP CRM Setup and Load Guide

3. Save your data.

2.4.5 Creating sales organizations

In the Configuration IMG, choose
Customer Relation Management o Master Data o Organizational Management o
Organizational Model o Change Organizational Model
1. Select the root organizational unit and click the right mouse button.

SAP AG page 60
SAP CRM Setup and Load Guide

2. Choose Create.
3. Select the option Is Line Supervisor of Organizational Unit.

SAP AG page 61
SAP CRM Setup and Load Guide

4. Enter an abbreviation and a name for the organizational unit.

5. On the 'Address' tab, maintain an address for the organizational unit.
6. On the 'CRMATTR' tab, choose scenario Sales.

7. Mark the check box 'Sales Organization'.

The field 'R/3 Sales Organization' is ready for input.

SAP AG page 62
SAP CRM Setup and Load Guide

8. Enter the corresponding R/3 Sales Organization (Use F4-Help).

9. On the 'Attributes' tab, enter the values for the attributes Distribution Channel and
Division as they are in the sales areas in R/3.

Repeat these steps for each sales area with different sales organization.
You can maintain the distribution channels and divisions for a sales organization for each
sales area under the same sales organization.

Further hints for creating an organizational model

x You can also insert organizational units that are not marked as sales organizations under
the root organizational unit, for example, regional offices. These can be useful for
structuring the organizational plan. In this case you do not assign attributes to these
organizational units.
x You can create other organizational units under the sales organizations, for example,
sales offices, and assign attributes to them to create sales areas in CRM.
For example, you can create sales organization 1000 with division 00 and assign two
sales offices to it, A and B. Then you assign distribution channel 10 to sales office A and
distribution channel 12 to sales office B. Thus you have created the following sales areas
in CRM:
- 1000/10/00
- 1000/12/00
x If you do not use all the sales organizations from R/3 in CRM you can set a filter on those
sales organizations that you use in CRM when you load the master data.

SAP AG page 63
SAP CRM Setup and Load Guide

2.5 Application Data (initial)

Here you can perform the load activity for objects that are considered as application business
objects, for example ‘Business partner’, ‘Business partner hierarchy’, ‘Plant’, ‘Product’ and
‘Conditions’, from OLTP to CRM.

Examples of objects loaded from the OLTP to the CRM system:

Category Object name Description
Business partner CUSTOMER_MAIN Customer Master
DNL_REFCUSTOMER Business Partner Reference
CUSTOMER_REL Customer Master
Relationships
Business partner hierarchy DNL_BUPA_KNVH Initial Load Group Hierarchy
Plant DNL_PLANT Plant
Product MATERIAL R/3 Material Master
SERVICE_MASTER R/3 Service Master
SCE Product Configuration
BOM Inter-linkage Objects
Condition configuration DNL_CUST_CND Conditions: Customizing.
Condition technique
DNL_CUST_PRC Conditions: Customizing.
Pricing
Condition DNL_COND_A002 Conditions: A002
DNL_COND_A003 Conditions: A003
DNL_COND_A004 Conditions: A004
DNL_COND_A005 Conditions: A005
DNL_COND_A006 Conditions: A006
DNL_COND_A007 Conditions: A007
DNL_COND_A011 Conditions: A011
DNL_COND_A020 Conditions: A020
DNL_COND_A029 Conditions: A029
DNL_COND_A030 Conditions: A030
DNL_COND_A031 Conditions: A031
DNL_COND_A032 Conditions: A032
DNL_COND_A057 Conditions: A057
DNL_COND_A078 Conditions: A078
DNL_COND_A190 Conditions: A190
DNL_COND_A191 Conditions: A191
DNL_COND_A192 Conditions: A192
DNL_COND_A304 Conditions: A304
DNL_COND_A305 Conditions: A305

SAP AG page 64
SAP CRM Setup and Load Guide

DNL_COND_A306 Conditions: A306

Objects loaded from the CRM system to the CDB:

Category Object name Description
Condition CRM_CND_ACCSEQ Condition Customizing.
Access Sequence
CRM_CND_APPLIC Condition Customizing.
Application
CRM_CND_CNDTAB Condition Customizing.
Condition tables
CRM_CND_CNDTYP Condition Customizing.
Condition types
CRM_CND_CONFIG Condition Customizing.
Configuration
CRM_CND_CONFIGC Condition Customizing.
ConfigurationC
CRM_CND_GROUP Condition Customizing.
Condition groups
CRM_CND_USAGE Condition Customizing.
Usage
CRM_FGD_PROC Free Goods Customizing.
Procedures
CRM_PRC_CNDLMT Pricing Customizing.
Condition limit
CRM_PRC_CNDTYP Pricing Customizing.
Condition types
CRM_PRC_DEST Pricing Customizing. Target
Fields
CRM_PRC_EXCGRP Pricing Customizing.
Exclusion Groups
CRM_PRC_PROC Pricing Customizing.
Procedures

2.5.1 Initial load of Customers

To load the customer data to the CRM system there are two different types of customer
master data according to the OLTP systems. One is ‘Business partner’ master data for
Industry solution (e.g.: Automotive, Pharmaceutical, Media, High Tech, Aerospace…) R/3
system, and the other ‘Customer’ master data for standard R/3 system. The former is called
‘BUPA_MAIN’ and the latter is called ‘CUSTOMER_MAIN’ in the CRM system.
So please make sure you load one of those objects depending on your relevant OLTP system
environment. Perform phase [Link] with your standard R/3 system and execute phase
[Link] with your Industry solution R/3 system.

SAP AG page 65
SAP CRM Setup and Load Guide

x The following figure shows you the direction of flow for data loading and the load
object name for the business partner for each flow.

Business partner master data Customer master data

Industry solution Standard SAP

of SAP system system

BUPA_MAIN
BUPA_MAIN
BUPA_MAIN CUSTOMER_MAIN

CRM

BUPA_MAIN BUPA_MAIN

BUPA_MAIN BUPA_MAIN

External Systems CDB

Please note that CUSTOMER_MAIN is only designed for the load from the OLTP to the
CRM system.

[Link] Initial load of customers from R/3 customer master data

(Standard R/3 system)
[Link].1 Initial load of the reference customers

Please refer to the notes 339787 and 455289 in case you face problem with the
download of this object.
The reference customers are created by grouping the same data - sales organization,
shipping information, pricing procedure and so forth - for the consumers in the R/3 system.
The consumer master data can be linked to the reference customer to obtain the above data
when orders are placed for the consumers.

The load of the reference customer is only relevant to the R/3 system release 4.5 or higher.
The consumers mean that you have consumers in your R/3 customer master data that have
sales area dependent data from a reference customer.

x Before you load the consumers, you need to load the reference customer in advance.

Please start the load of the reference customer as below:

x Choose “Middleware o Data Exchange o Initial Load o Start” of the SAP Easy
Access Menu of the CRM System. Please select “DNL_REFCUSTOMER” as the
Load Object and execute.

When the load is successfully completed,

SAP AG page 66
SAP CRM Setup and Load Guide

1. Choose “Master Data o Business Partner o Maintain Reference BP for Consumers” of

the SAP Easy Access Menu of the CRM System.
2. Check the Field “Reference Bus. Partner” is filled.
3. Note the number of the Reference Business Partner, choose transaction
“CRMM_BUPA_MAP”, put the reference business partner number into the field “Business
Partner” and execute it.
4. See whether the field “Customer” contains the number of the Reference Customer in R/3.
5. Copy the GUID of the Reference Business Partner displayed in the field “Business
partner GUID”.
6. Go to your related R/3 System, choose transaction SE16, choose the table name
“CRMKUNNR” and press F7, paste the copied GUID of the CRM reference business
partner in the field “PARTN_GUID” in the selection screen and execute it.
7. Check for an identical entry for this selection and see if the field “CUSTOME_NO”
contains the number of the Reference Customer in R/3. When all these checks are done
you can start the load of the customers.

[Link].2 Initial load of Business Partners

There are some prerequisite customizing objects before you load business partners. Make
sure the necessary customizing objects are loaded successfully. The essential 12
customizing objects are the following: DNL_CUST_BNKA, DNL_CUST_ADDR,
DNL_CUST_TVPV, DNL_CUST_TVLS, DNL_CUST_TVIP, DNL_CUST_TVGF,
DNL_CUST_TVFS, DNL_CUST_TVAST, DNL_CUST_TSAB, DNL_CUST_TPFK,
DNL_CUST_T502T, DNL_CUST_TBRC.
Perform the following steps
1. Choose Middleware o Data Exchange o Initial load o Start.
2. Choose the Load Object: CUSTOMER_MAIN.
3. Choose execute (F8).
4. Check the load by using transaction SE16 (data browser): The table
CRMM_BUT_CUSTNO must have the same number of entries as the table KNA1 in the
OLTP. Please check also the error messages in the FLOW TRACE (Transaction
/nSMW01). In the event of errors, all inbound and outbound queues on CRM-side and on
R/3-side referring to the entries of the CUSTOMER-object and the relevant destination
(check with transactions SMQ1 and SMQ2) have to be emptied. Afterwards the initial load
of business partners has to be started again as described above. The customer master in
the OLTP is identified by the customer number (KUNNR), table KNA1 in particular
contains the customer number (KUNNR). The business partner master in CRM is
identified by the business partner number or its corresponding business partner GUID.
Customer number and business partner number for the same customer are not
necessarily identical; this depends on the mapping of account groups and classification
for business partners and the corresponding number assignment. The mapping between
the customer number and the business partner GUID is stored in table
CRMM_BUT_CUSTNO, whereas the mapping between business partner number and
business partner GUID is stored in table BUT000 in the CRM, which is the header table of
business partners in CRM.

Please note that you can also use table CRMV_BUPA_CUSTNO (Mapping Business
Partner Number - Customer) to control the result of your download.

SAP AG page 67
SAP CRM Setup and Load Guide

[Link].3 Initial load of Contact Persons (Relations)

As a prerequisite for starting this load, the customer load ‘CUSTOMER_MAIN’ should be
completed.

1. Choose Middleware -> Data Exchange o Initial load o Start

2. Choose the Load Object (S_OBJECT if logon language is German): ‘CUSTOMER_REL’
3. Choose execute (F8)
4. Check the load with transaction SE16 (data browser):
The table CRMM_BUT_CONTNO needs to have the same number of entries as table
KNVK in the OLTP, but as of R/3 release 4.5A and higher reduced by the number of
customers in the special account group for consumers (standard delivery uses account
group 0170). Please note in addition that all contact persons for whom the corresponding
business partner is not available in CRM are automatically omitted (without an error
message). Please also check the error messages in the FLOW TRACE (Transaction
SMO8FT). In the event of an error, all inbound and outbound queues on CRM-side and on
R/3-side referring the entries of the CONTACT-object and the relevant destination (check
with transactions SMQ1 and SMQ2) have to be emptied. Afterwards the initial load of
business partners has to be started again as described above.

Please note that you can also use table CRMV_BUPA_CONTNO (Mapping the Person's
Partner Number - Contact Person) to control the result of your download.

[Link] Initial load of business partner from R/3 business partner master
data (IBU R/3 system)

Please note that the following objects (BUPA_MAIN, BUPA_REL, BUAG_MAIN) have
been developed for Industry solutions R/3 systems with basis release 4.6C or higher
and therefore should not downloaded with older releases.

To avoid any problems with the number range assignment we recommend you use an
internal number assignment.

[Link].1 Initial load of Business partner

If you do not wish to load all of your business partners, you may set a filter on (refer to the
relevant middleware documentation using SAP online help for SAP Customer Relationship
Management \ Basis Technology \ CRM Middleware \ Adapter And Site Types \
Adapters \ The Adapter Framework \ Configuring the System \ Object Management \
Managing Objects \ Defining Filters for Objects) and only on the table BUT000.
To load the business partner,
1. Choose Middleware Æ Data Exchange Æ Initial load Æ Start from the SAP Easy Access
Menu of CRM system.
2. Select object ‘BUPA_MAIN’

SAP AG page 68
SAP CRM Setup and Load Guide

3. Enter and execute it.

For further details about load behaviors and how the system reacts if errors occur, refer to
middleware documentation.
After the successful completion of the load compare table ‘BUT000’ in both systems. Please
take into account that entries in table “BUT000” in CRM and table “BUT000” in R/3 do not
have to have the same number of entries, since the uploading activities of organizational units
or employees which are distributed via ALE are also considered as business partners and
remain as entries in the table “BUT000” in the CRM but not in the R/3 system.
If you use an external number range assignment, the Business Partner Numbers and
Business Partner GUID’s are the same for the both systems, but if you use an internal
number range assignment, only the Business partner GUID’s are same.

[Link].2 Initial load of Contact Persons (Relations)

As a prerequisite for starting this load, the customer load, ‘BUPA_MAIN’, should be
completed.
If you do not wish to load all of your business partners, you may set a filter on (refer to
relevant middleware documentation using SAP online help for SAP Customer Relationship
Management \ Basis Technology \ CRM Middleware \ Adapter And Site Types \
Adapters \ The Adapter Framework \ Configuring the System \ Object Management \
Managing Objects \ Defining Filters for Objects) and only on the table ‘BUT050’.

1. Choose Middleware -> Data Exchange o Initial load o Start

2. Choose Load Object: ‘BUPA_REL’
3. Choose execute (F8)
4. Check the load with transaction SE16 (data browser):
5. Compare the table‘BUT050’ for the OLTP and CRM system.

2.5.2 Customer hierarchy and business partner group

You have to perform this load step after business partner load is completed.

x You can match the customer hierarchy in OLTP system to the business partner group
in CRM system.
x The table for Customer hierarchy in OLTP system is ‘KNVH’.
x Two business objects have to be maintained on the CRM side: ‘DNL_BUPA_KNVH’
in initial load object and ‘BUPA_KNVH’ in delta load object.
x Once the customer hierarchy in OLTP system has been transferred to CRM system, it
is located in the ‘CRM_KNVH_TEMP’ table, which is not perfectly matched with the
Business partner group in CRM system.

To match this you need to follow the steps below in CRM system:

SAP AG page 69
SAP CRM Setup and Load Guide

1. Load business object DNL_BUPA_KNVH. You should load this business object after
business partner load is complete.
2. Go to transaction /nBPH_DNL

3. Execute it or F8. After this work, the system automatically matches the customer
hierarchy from OLTP system to the business partner group in CRM system.

4. In IMG, CRM o Master data o Business partner o Business partner group hierarchy
o Activate delta load. This activity allows you to have identical hierarchy in CRM
system with OLTP system.

SAP AG page 70
SAP CRM Setup and Load Guide

2.5.3 Initial load of Plants

Calling up the ATP functionality of APO and connecting the proper plants information from
APO to CRM, you need to load plant information from OLTP system. The Plants in CRM are
also considered as Business partners.
You can manually maintain the mapping table used by the BBP system administrator or load
the object.
It is recommended to load the plants data after the customer master data have been
completely loaded.

[Link] Manual maintenance of the mapping table in CRM system

Maintain the mapping table manually in CRM system as follows:
1. Transaction code: /ncrm_locmap
2. Manually type the business partner and plant to map one another.

SAP AG page 71
SAP CRM Setup and Load Guide

[Link] Automatic transfer of the location data from the R/3 to the CRM
system
Transfer of the location data from the R/3 to the CRM system automatically is described
below:
1. Check whether the table is maintained for DNL_PLANT object.
Middleware o Data Exchange o Object management o Business object o
DNL_PLANT

SAP AG page 72
SAP CRM Setup and Load Guide

2. The plant table T001W from R/3 is read, and the address fields of this table are used to
create a new business partner in CRM. The mapping between plant and business partner
is saved in table CRMM_LOCMAP (which can be viewed by transaction /nCRM_LOCMAP).
Middleware o Data Exchange o Initial load o Start

3. Execute it (F8)
4. Check your object by using transaction code SLG1

SAP AG page 73
SAP CRM Setup and Load Guide

SAP AG page 74
SAP CRM Setup and Load Guide

2.5.4 Initial load of Materials and Services

Please read and consider note number 418886, which contains essential information
before you proceed with the load of Materials and Services.
x The following figure shows you the direction of flow for data loading and the load
object name for the business partner for each flow.
(The Data loading flow and object names from the OLTP to the CRM and the
CRM to the CDB)

OLTP master data

x Materials
x Services
x Structured Articles for retail customers

Standard SAP
system

x Materials (MATERIAL)
x Services (SERVICE_MASTER)
x Structured Articles for retail customers (BOM)

CRM master data

x Hierarchies

CRM x Materials
x Services
x Inter-linkages (Materials, Services)

x Hierarchies (HIERARCHY_PROD)
x Material (PRODUCT_MAT)
x Services (PRODUCT_SRV)
x Inter-linkages (Materials: PRODUCT_IL_MAT,
Services: PRODUCT_IL_SRV)

CDB

SAP AG page 75
SAP CRM Setup and Load Guide

x When you want to load data from the CRM to the CDB, it is recommended the objects
be loaded in a sequence as follows:
1. Hierarchies (HIERARCHY_PROD).
2. The father objects: Materials (PRODUCT_MAT) and/or Services
(PRODUCT_SRV)
3. The child objects: Inter-linkages: (Materials (PRODUCT_IL_MAT) and/or
Services (PRODUCT_IL_SRV))
x Inter-linkages object names, for example, PRODUCT_IL_MAT and
PRODUCT_IL_SRV, are only used for initial data load; PRODUCT_MAT and
PRODUCT_SRV are used for delta data load instead.

(The Data loading flow and object names from the CRM to the OLTP and the
CDB to the CRM)

OLTP master data

x Materials
x Services
x Finance products
x Structured Articles for retail customers

Standard SAP
system

x No Bdocs, No load objects are used

x RFC technology is used

CRM

x Not available

CDB

SAP AG page 76
SAP CRM Setup and Load Guide

x When you want to load product relevant data from the CRM to the OLTP for the first
time, create the master data in the CRM system, and then choose the function for
‘upload’ to the OLTP system manually. In the event of master data changes in the
CRM system, it uploads to the OLTP system automatically.

Structured articles for the retail customers, load business object name ‘BOM’, are now
available to be loaded from the OLTP to the CRM system. Please refer to the relevant release
note.

x Make sure that the number range object IB_SYM_ID for configurable product loading
is maintained correctly. Otherwise you need to create the number range as follows by
using the transaction /nSNRO:
Number From number To number
01 000000000001 000999999999

x Check the correct definition of the item category groups:

IMG path on the OLTP R/3 IMG path on the CRM server
Sales and Distribution Æ Sales Æ Sales Customer Relationship Management
Documents Æ Sales Document ItemÆ Define Æ Transactions Æ Basic Settings Æ
Item Category Groups Define Item Category Group
The item category groups have to be created in the same way in the OLTP R/3.
Please ignore warning messages that might appear.

Additionally, the customizing objects ‘DNL_CUST_PROD*’ and ‘DNL_CUST_ACGRPP’

for material load and ‘DNL_CUST_SRVMAS’ for ‘SERVICE_MASTER’ load must have
already been received in the CRM system.
Specify which materials are supposed to be transferred. You do this by modifying the
filter for the object MATERIAL in transaction R3AC1
The filter settings have to have a format which is suitable for the corresponding fields in
your backend system. Especially numerical material numbers have to have 18 digits
(leading blanks have to be specified unless you chose lexicographical sorting)
‰ Perform the following steps in the CRM system:
1. Choose Middleware -> Data Exchange o Initial load o Start.
2. Load Object [S_OBJECT]: choose ”MATERIAL” or “SERVICE_MASTER” and execute
(F8).
3. Use transaction /nr3am1 to monitor the load.
4. Use transaction /nsmw01 to check the load (especially for a detailed analysis in case of
errors).
In the event of an error, all inbound and outbound queues on CRM-side and on R/3-side
referring the entries of the MATERIAL object and the relevant destination (check with
transactions SMQ1 and SMQ2) have to be emptied.

SAP AG page 77
SAP CRM Setup and Load Guide

Afterwards the initial load of business partners has to be started again as described
above.
5. In case you are using pricing products, execute transaction /NCRMM_PRPROD after a
successful initial load of the MATERIAL object to check whether problems occurred
during the assignment of pricing products and to determine the pricing reference
products.

You should also download the “SCE” (Product Configuration) object, especially in order to use
the Internet Pricing and Configurator (IPC).

Additional note for loading taxes of materials

1. If you want to load the materials from R/3 to CRM initially without correcting the tax
determination in advance in CRM,

a. Call up the transaction R3AC1 (or Middleware -> Data exchange -> object
Management -> Business Objects)
b. Switch into change mode.
c. Select the Business Object 'Material' and press 'table' icon.
d. Set the table "MLAN” as Inactive mode by choosing the column named 'Table
inactive' and save it.
e. Start initial load of product master.

2. However, from the selling viewpoint, at any rate, you need to determine taxes and also
which tax mapping is necessary for tax allocation from R/3 to the CRM.

To do this,
Carry out transaction code: CRMC_TAX_MAP or
choose IMG -> Customer Relationship Management -> Basic Functions ->Taxes ->
Define Assignment of Tax Data from R/3 to CRM

3. After correcting the determination of taxes and the mapping from R/3 system to CRM,

a. Call up the transaction R3AC1 (or Middleware -> Data exchange -> Object
Management -> Business Objects).
b. Switch into change mode
c. Select the Business Object 'Material' and press 'table' icon.
d. Set the table "MLAN” as active mode by deselecting the column named 'Table
inactive' and save it.
e. Start initial load, again.

The Changes for the materials in R/3 will be delta loaded.

Only changes made in CRM will not be influenced by this load.

SAP AG page 78
SAP CRM Setup and Load Guide

2.5.5 Initial load of Conditions

The load of condition records has to be performed in four steps that should be followed in
order:
1. Load the configuration of conditions and price determination
2. Run correction and generation report
3. Providing the infrastructure to distribute condition master data to the CDB and Mobile
Client
4. Load the condition master data

Please refer to OSS Note 314542, which contains useful information regarding error
messages that may occur during theses steps.
[Link] Load the configuration of conditions and price determination
The configuration definitions for conditions and price determination should already have been
loaded with the other configuration settings. If they are not there or if they are corrupt the load
can be redone using the following procedure:
a. Choose Middleware Æ Data Exchange Æ Initial load Æ Start.
b. Load Object [S_OBJECT]:
There are four objects to be loaded. They are DNL_CUST_CNDALL, DNL_CUST_CND
for condition technique, DNL_CUST_PRC for Pricing information and DNL_CUST_FGD
for free goods.
The difference between theses objects is:
x DNL_CUST_CNDALL includes all data including client independent and client
dependent tables and all these tables are in active mode
x DNL_CUST_CND also includes client independent and client dependent tables
but only client dependent tables are in active mode
x DNL_CUST_PRC and DNL_CUST_FGD only include client dependent tables
and they are in active mode.
SAP recommends you load DNL_CUST_CNDALL into only one specific client for one
system and other clients should individually load DNL_CUST_CND, DNL_CUST_PRC,
and DNL_CUST_FGD instead of DNL_CUST_CNDALL. Object DNL_CUST_CNDALL in
other clients should be deleted.
c. Check the application log for configuration load by using Transaction
CND_MAP_LOG_DISPLAY:
You need to enter the main object ‘COND_EXCHANGE’ and sub-object
’CUSTOMIZING’.

SAP AG page 79
SAP CRM Setup and Load Guide

[Link] Run correction and generation report

Please refer to OSS Note 398078 for useful information regarding report
/SAPCND/RV12N001.

After completion of the configuration load the following report for correction and
generation has to be started.
Please note that if you have a CRM system with multiple clients then you only need to run
this report once, just after you performed the download of DNL_CUST_CNDALL object.
Call the transaction /nse38 and type the report /SAPCND/RV12N001. This report corrects
entries in the configuration tables and generates the tables for the condition records.

SAP AG page 80
SAP CRM Setup and Load Guide

1. The correction is applied to the application (CRM, TAX, BBP and so forth) and the
usage (PR: Pricing, FG: Free goods and so forth)
2. For generation it is either empty or the same setting as you made for the
correction.

Make sure that you have the following authorization in order to run the
report/SAPCND/RV12N001: Authorization object “/SAPCND/CO” (Processing
Condition Technique Objects) with activity 64 (Generate) and 65 (Reorganize).

[Link] Providing the infrastructure to distribute condition master data

to the CDB and Mobile Client

SAP AG page 81
SAP CRM Setup and Load Guide

Before distributing condition master data to the mobile client the corresponding infrastructure
has to be created. That means CDB-Tables and synchronisation BDOCs have to be created.
The information needs to be replicated to the mobile client and the replication and
realignment mechanism needs to get arranged.

[Link].1 Preliminary Remarks

1. For CRM Rel 3.0 the Flow of condition master data was changed compared to former
Releases. The CDB tables are now filled by the CRM Online system. Also Data which
is passed from R/3 will first have to be stored in the CRM Online tables before being
replicated to the CDB tables
2. The data model in the CDB and correspondingly on the mobile client was changed for
condition master data to a model almost identical to the CRM Online model.
3. As messaging BDOC, CND_MAST_DEEP_SUP is always used (shortname
CND_M_SUP). Make sure the mobile bridge is activated for this mBDOC.
With Rel. 3.0 CDB tables and synchronisation BDOCs can be generated and do not need to
be modelled manually.

[Link].2 Naming conventions

The names for CDB tables for condition master data consist of the prefix CMB followed by a
name, which always follows the new naming convention for condition tables. The name of the
corresponding sBDOCs starts with the prefix CNB followed by a string according to the new
naming convention for condition tables.

For example the Online DB table CNCCRMPRSAP004 corresponds to the CDB table
CMBCCPSAP004. The sBDOC is named CNBCCPSAP004. For Online table
/1CN/CCFSAP010 the CDB table is named CMBCCFSAP010 while the sBDOC has
the name CNBCCFSAP010.

[Link].3 Generation of CDB condition tables and Synchronization BDOCs

You can generate CDB tables and sBDOCs using the Report
CND_MAST_GEN_TRANSFER_OBJECTS.

SAP AG page 82
SAP CRM Setup and Load Guide

Specify the CDB-tables or sBDocs by choosing the appropriate Application, Usage and Table
Number. (For scale tables you need only Application and Usage.)
While generating an sBDOC, create also a secondary index for the mobile client. The index is
needed for the access to the condition tables during business process on the mobile client.
You can review the sBDOCs in the BDOC Modeler (Transaction SBDM)

The CDB tables will already get generated if you generate the corresponding condition
table in the online DB using the IMG. Or, you also generate the CDB tables while
generating tables for the online tables using the report /SAPCND/RV12N001 with the
option ‘Additional Objects’ marked. The synchronisation BDOCs can only get
generated with the report CND_MAST_GEN_TRANSFER_OBJECTS.

[Link].4 Transfer to the mobile client and generation on the mobile client
After the generation is successfully completed, you need to extract the table scripts and the
stored procedure using the ClientConsole. In addition you need to run the scripts on the
mobile clients to generate the corresponding tables. For details please see the online
documentation for the mobile client. You can find this under
SAP Help Portal: [Link] o [Link] Cross-Industry Solutions o
mySAP Customer Relationship Management o SAP Customer Relationship Management
(CRM Online Documentation) o Basis Technology o CRM Middleware o Mobile Clients o
Client Console

[Link].5 Enter settings in the Admin Console

SAP AG page 83
SAP CRM Setup and Load Guide

Once the tables are present on the mobile clients you have to create Replication objects,
Publications and Subscriptions using the AdminConsole. Assign the appropriate Sites to the
subscriptions.

[Link].6 Initial Load from CRM Online DB to the CDB

You can fill the CDB tables from the CRM Online database by doing an initial load. Please
create an appropriate download object using transaction R3AC5. You can copy the settings
from Download object CRM_CCPSAP004. Please change the table to the one you want to
download. Afterwards start the download using transaction R3AS.

[Link].7 Remarks
Some of the sBDocs are delivered from SAP. It is for those conditions, which are delivered in
CRM (respectively the structure as for i.e. CNCCRMPRSAP004). In addition these tables
need to be relevant for processes affecting the mobile client. Anyhow there were no
replication objects delivered with the sBDOCs. You need to create them using the Admin
Console based on your individual needs. In addition publications and subscriptions have to be
created manually.
For condition tables, which originate from an R/3 system or customer owned condition tables
you need to generated CDB tables as well as sBDOCs from scratch.
CDB tables usually get generated in the background for all the Online database condition
tables. Generate sBDOCs only for tables for which you want to transfer data to the mobile
client.

For more information see the Online help and also note 432267.

[Link] Load condition master data

After you load all configuration data and generate the table for conditions, all prerequisites
are fulfilled to start the load of the condition records. If prices or conditions depend on the
material or customer, the corresponding master records must already exist (usually from the
previous load).
In the initial load, each condition table is loaded separately:

For example, the load of OLTP table A005 using the object DNL_COND_A005
Example for table A005:
1. Choose Middleware -> Data Exchange Æ Initial load Æ Start.
2. Load Object [S_OBJECT]: select ”DNL_COND_A005”.
3. Choose execute (F8).
4. Repeat the steps for all other relevant condition tables (DNL_COND*).
5. Check the application log for configuration load by using Transaction
CND_MAP_LOG_DISPLAY:
You need to enter the main object ‘COND_EXCHANGE’ and sub-object ’Conditions’.

SAP AG page 84
SAP CRM Setup and Load Guide

2.5.6 Initial load of further objects

In order to complete data transfer from CRM Online tables to CDB tables for Mobile client
Replication etc. you will need to enable the flow for PRODUCT_MAT & BUPA_MAIN.
Starting the data exchange is initially done through transaction R3AS, specifying the load
object and destinations, which are from CRM to CDB.

Check table ‘SMOFINICON’ (/nSE16) to see the objects via source site CRM, and target
site CDB.
x After Initial load is complete, subscriptions have to be defined in Administration
Console for all clients (sites).
x All projects are provided with the standard CG (consumer goods (SMOHPARIND;
INDUSTRY_TEMPLATE = "CG")) template. This also includes standard publications.
x For subscription input, refer to Administration Console documentation,
AdministrationÆ the ÆSubscription WizardÆ Adding/Editing a subscription. In the
Subscription Wizard it is possible to assign previously defined sites to subscriptions.
x The industry parameter value should not be changed if the customer has
subscriptions.

3 Delta load of Master Data

3.1 MW Server Job-Scheduling
3.1.1 Overview
The Middleware Server needs some jobs for automatically processing messages that are
stored in internal queues and one more for handling the statistic updates properly. Follow the
instructions to create the required system events and schedule the jobs.

SAP AG page 85
SAP CRM Setup and Load Guide

3.1.2 Statistics
This job makes some preparations for the updating of statistics. It should always run 1 day
before the updating of statistics is scheduled.

The updating of these statistics applies only to the oracle database environment.
(See OSS note number 162956).

You do not need to do this job if you use a database other than oracle.

Name: MW_STATISTICS
Steps: ABAP-Program
Name smo6_maint_statistic
Variant (No variant)
Start-Date: Approx. 1 day before the updating of statistics is scheduled
Date/Time <choose>

3.1.3 Activate Delta Events

The initial load of an object normally performs the activation of delta events automatically.
You have to activate the delta events manually only if you need the delta events but have not
performed the initial load of an object (e.g. BUPA). This is as follows:
1. Choose Middleware o Data Exchange o Delta load from OLTP R/3 o Set Up Delta load
2. Choose Display->Change Button in order to switch to change mode
3. Choose Button “New Entries”, then Object Class BUPA, Destination CRM_AX5_100 (i.e.
the RFC destination of the OLTP System)
4. Save the Entries. Now the message “Table TBE31 has been adjusted in OLTP system”
confirms the action if it was successful.

SAP AG page 86
SAP CRM Setup and Load Guide

3.1.4 Replication & Realignment Queues

All realignment functions are asynchronously processed with any corresponding messages in
the flow. Therefore the Replication & Realignment module works with 5 internal queues
(Three for extraction, one for realignment and one for subscription checking).
For processing the entries in these queues the Queue Demon has to run in the background. It
is client-independent and calls the required function modules via RFC destinations that have
been created during configuration in the IMG. Also the necessary intervals of the
corresponding number range objects have to be maintained (see Chapter “Configuring the
CRM server for message processing”, paragraph “Creating RFC destinations for Replication
& Realignment Queues”)
To display information on the status of the Queue Demon and contents of the replication and
realignment queues in the clients defined in your CRM Middleware System, choose
Middleware o Monitoring o Queues o Monitor R&R Queues in your SAP user menu. It is
the same function as in Middleware -> Replication and Realignment Queues -> Monitor R&R
Queues.

With this function the following five replication- and realignment queues are displayed for
each client:
x AC_EXTRACT – contains extract jobs created by the Administration Console [Extern].
x EXTRACTBLK - contains bulk extract jobs (these jobs are created by the subscription
checker).
x EXTRACT – contains extract jobs broken down by BDocs (the jobs are created by
realignment).
x REALIGN – contains realignment jobs for individual BDocs whose responsibilities must
be checked.
x SUBCHECK – contains subscription checker jobs (these should be generated in the
administration console, if the assignments between sites and subscriptions are changed).

SAP AG page 87
SAP CRM Setup and Load Guide

The following information is displayed:

Column Contents
Client Client in your CRM Middleware System
Name Name of queue
Status Status of queue
No. entries Current number of entries (messages) in the queue
Symbols Following symbols may appear:
to delete the entire contents of a queue

to display the current error message in an error situation

To update the information displayed choose Refresh.

The status of the Queue Demon is also displayed. You can start or stop the queue demon by
choosing appropriate buttons in the application tool bar.
By clicking on the status icon in the status column you can:
x Release queues for processing by setting their status to Released (yellow light)
x Reset released queues to Hold (red light)
x Interrupt queue processing (Status Running – green light) by setting the status to
Hold.
If you interrupt queue processing, processing of the current entry is completed and then the
queue is set to status Hold. The Queue demon automatically sets it to hold if an error occurs
during processing. The error symbol appears in the last column (see above). You can select
this to display the error message. When you release the queue again, the error status is
reset.
If you release a queue after the Queue demon has started, the status of the queue changes
to Running, provided it contains entries for processing. If all entries have been processed
(number of entries is zero), the status changes to Released again.
If a queue contains entries you can display details of the individual entries (e.g. the number of
sites affected) by clicking on the number of entries. You can delete individual entries in this
display, by selecting the checkbox in the first column of the record and choosing Delete. To
update the information choose Refresh.
If you double-click on a record, information about the site is displayed.

3.2 Reduction of Log-Levels

During generation and initial load full trace recording is recommended (trace level 3 with
ENV=G and ENV=I).
After these steps have been successfully finished, it is also recommended to reduce logging
for performance reasons. Trace level 1 is recommended.

SAP AG page 88
SAP CRM Setup and Load Guide

SMOFPARSFA Setting 2
Key CRMGENERAL
Paramname TRACE-LEVEL
Paramname2 ENV=
Paramname3 CMP=*
Paramval LEVEL=1

SAP AG page 89
SAP CRM Setup and Load Guide

4 Appendix
4.1 Mapping Business Partner number ranges in R3 and CRM
4.1.1 Business Partner Concepts in R/3 and CRM
The business partner concepts of the R/3 system and the CRM system are different.
Therefore, you have to define a mapping when exchanging business partners from R/3 to
CRM and vice versa.
a) R/3 System
x Every business partner has to be assigned to an account group that determines the
properties of business partners, especially:
x Master data fields
x Number range
x Specific functionality for sales and distribution
x There are more than 20 different account groups available in the standard delivery.
b) CRM System
x Business partners in the CRM system are grouped by using classifications which
determine:
x Master data fields
x Specific functionality
x The number ranges are not directly assigned to the classification. The number range
is determined by the so-called grouping. When creating a business partner you can
assign a grouping to the business partner. If you do not assign a grouping, the
system uses the specified standard grouping for internal or external number
assignment.
x There are only 5 different classifications
x Consumer: Organization
x Consumer: Person
x Customer
x Prospective customer
x Competitor
Note:
You can assign more than one classification when creating a business partner.
The classifications obey the following hierarchy.
Consumer > Customer > Prospective Customer > Competitor
For example, if you assign the classifications Consumer and Customer to a
business partner the leading classification in the mapping process to account
groups in R/3 is the classification Consumer.
You have to define the mapping of business partner for both directions: from the R/3 system
to the CRM system and vice versa. Thereby you have to:
x Map account groups to classifications and make sure that the required fields in both
systems are identical
x Map the number ranges

SAP AG page 90
SAP CRM Setup and Load Guide

4.1.2 Defining Number Assignment Strategy for Business

Partners
There are two alternatives for mapping the business partner numbers from the R/3 Backend
system to the CRM Server and vice versa.

[Link] Choosing different number ranges

[Link].1 Description
The business partner IDs of R/3 and CRM business partners are not identical.
There is always an internal assignment table that maps the R/3 business partner ID to the
corresponding CRM business partner to ensure a consistent data exchange.

[Link].1.1 Advantages
x The mapping procedure is easy
x No problems with duplicate business partner IDs

[Link].1.2 Disadvantages
x Identification of the same business partner in the R/3 Backend system and the CRM
Server application is difficult.
The R/3 ID is only available for searching and is not displayed in the master data record.

[Link].2 Procedure
When mapping R/3 account groups to CRM business partner groupings and vice versa you
choose always internal number assignment in the receiving system, i.e. a business partner
that is created in R/3 Backend system gets automatically a new ID during the replication to
the CRM Server and vice versa. You can choose the same or different number ranges for the
mapping of account group to classification. To avoid misunderstandings, i.e. customers with
the same ID are not identical, it is recommended to use different number ranges.

[Link].2.1 Example for mapping:

CRM Server R/3 Backend System
Classification From number to number Replication Account From number to number
direction group
Customer 1000-1999 Internal R/3 Backend 0001 1-999 Internal
number range to CRM number range
Server
Customer 1000-1999 Internal CRM Server 0001 1-999 Internal
number range to R/3 number range
Backend
The first customer created in the R/3 Backend system gets ID 1 in the R/3 Backend system
and ID 1000 in the CRM System.
If the next customer is created in the CRM system he will get the ID 1001 in the CRM system
and ID 2 in the R/3 Backend system.

[Link] Choosing identical number ranges

[Link].1 Description
The business partner IDs of R/3 and CRM business partners are identical.
There is always an internal assignment table that maps the R/3 business partner ID to the
corresponding CRM business partner to ensure a consistent data exchange.

[Link].1.1.1 Advantages

SAP AG page 91
SAP CRM Setup and Load Guide

x Identification of the same business partner in OLTP R/3 and CRM system is easy
possible because of using the same ID.

[Link].1.1.2 Disadvantages
x The mapping procedure is complicated.
x Duplicate business partner IDs may occur if the mapping is not defined correctly.

[Link].2 Procedure
There are two ways to guarantee identical number ranges.

[Link].2.1 Leading system approach

Define a leading system for business partner maintenance, i.e. business partners belonging
to the same account group or classification are only maintained in the OLTP R/3 or in the
CRM system exclusively.

[Link].2.2 Example
Customers (account group 0001) are only maintained in the OLTP R/3, consumers
(account group 0170) are only maintained in the CRM system. The account group and
the mapped classification must have the same number range. For the receiving system
external number assignment is required. You have to make sure that business partner
creation in the receiving system is prohibited.

[Link].2.3 Example for mapping:

CRM System OLTP R/3
Classification From number to number Replication Account From number to number
direction group
Customer 1-999 External ß 0001 1 -999 Internal
number range number range
(leading)
Consumer 1000-ZZZ Internal à 0170 1000-ZZZ External
number range number range
(leading)

[Link].2.4 Separate account group approach

If the leading system approach is not feasible you can ensure identical number ranges by
using different account groups.

[Link].2.5 Example
Customers have to be maintained in the R/3 Backend system and in the CRM system in
parallel. Define one account group (e.g. 0001) for customers that are created in the R/3
Backend system and have to be replicated in the CRM system. Define an additional
account group (e.g. Z001) for customers that are created in the CRM system and have to
be replicated to the R/3 Backend system. Use different number ranges for these account
groups and define external number assignment in the receiving system.

[Link].2.5.1 Note
This approach is not applicable for consumers because there can only be one unique account
group for consumers in the R/3 Backend system. Therefore you have to choose the leading
system approach to ensure identical numbers for consumers in both systems.

CRM System OLTP R/3

SAP AG page 92
SAP CRM Setup and Load Guide

Classification From number to number Replication Account From number to number

direction group
Customer 1-999 External ß 0001 1 -999 Internal
number range number range
(leading)
Customer 1000-1999 Internal à Z001 1000-1999 External
number range number range
(leading)
Note:
In the following only the required activities for implementing the separate account group
approach for customers and the leading system approach for consumers are described, i.e.
the CRM system is the leading system for the creation of consumers after the initial
replication from the R/3 Backend system.

4.1.3 Mapping Business Partner Master Data from R/3 to CRM

In order to map the business partner master data from R/3 Backend system to CRM Server
you have to run the following activities:
1. Identifying relevant R/3 account groups.
2. Defining number ranges for CRM business partners.
3. Defining CRM business partner groupings.
4. Mapping R/3 account group to CRM classification
The following table describes all relevant elements that have to be maintained for the
mapping of R/3 account groups to CRM classifications. It is also mentioned at which activity
the element is maintained. It is recommend to maintain this table to keep the overview when
running the following activities.
R/3 CRM
Step 4 Step 4 Step 3 Step 2 Step 2 Step 2
Accou Numb Interval Number Classificati Groupi Numb Interval Number
nt er assignm on ng er assignm
group range ent range ent
0001 01 000010000 Internal Customer R001 R1 000010000 External
0- or 0-
000099999 External 000099999
9 9

For the above example, the mapping runs as follows:

1. A business partner for account group 0001 (sold-to party) is created in the R/3
system.
2. The account group has the number range assignment 01 and internal number
assignment, i.e. a number is automatically created from the interval 0000100000-
0000999999 for this business partner, e.g. 100001.
3. The business partner is replicated to the CRM system.
4. The account group is assigned to the classification Customer with grouping R001.
Grouping R001 is assigned to number range R1 that is identical to the R/3 number
range 01. The R/3 customer that is replicated to the CRM system automatically is
created with classification Customer and gets the same number because external
number assignment is chosen for the CRM number range.

SAP AG page 93
SAP CRM Setup and Load Guide

4.1.4 Identifying Relevant R/3 Account Groups

[Link] Use
In the OLTP R/3 analyze the relevant account groups and their assigned number ranges.
Identify the account groups that you are using when creating business partners in the OLTP
R/3. For these account groups a mapping have to be defined in the following activities.

[Link] Procedure
R/3 Identifying Relevant R/3 Account Groups
Transaction code OVT0
IMG Path Logistics General o Business partners o Customers o Control o
Define account groups and field selection for customer
1. Select your relevant customer groups.
2. Choose Details (F2).
3. An overview table of the number ranges appears.
Select the field Number range and choose F4 to get the interval for this number range.
In this table, the External field indicates whether the number range is internal or external.
4. Note down the account group information in the table described in the activity Mapping
Business Master Data from R/3 to CRM. It will be used in the following activities.

4.1.5 Defining Number Ranges for CRM Business Partners

(Part 1)
[Link] Use
For each number ranges of the selected account groups of the OLTP R/3 you have to create
a number range in the CRM system.

[Link] Procedure
CRM Defining Number Ranges for CRM Business Partners (I)
Transaction code BUCF
IMG Path Cross Application Components o SAP Business PartneroBusiness
PartneroBasic SettingsoNumber Ranges and Groupings o Define
Number Ranges
1. Choose Change Intervals.
For each different number range identified in the activity Identifying Relevant R/3 Account
Groups create a new number range.
2. Choose Insert Interval and enter the number range according to the R/3 number range.
3. Choose the Ext. flag for the number range.
4. Save your entries.

4.1.6 Defining CRM Business Partners Groupings (Part 1)

[Link] Use
For each number range created in the activity “Defining Number Ranges for CRM Business
Partners (I)” you have to create a grouping. The business partner gets a number from the
number range that is assigned to the grouping. This grouping is only used for defining number
ranges for business partners that are replicated from R/3 to CRM.
Attention:

SAP AG page 94
SAP CRM Setup and Load Guide

These groupings should not be used for creating business partners in the CRM system,
because business partners belonging to these groupings are not replicated to the OLTP R/3.

[Link] Procedure
CRM Defining CRM Business Partners Groupings (I)
Transaction code SPRO
IMG Path Cross Application Components o SAP Business Partner o Business
Partner o Basic Settings o Number Ranges and GroupingsoDefine
Grouping and Assign Number Ranges
1. Choose New Entries.
Create a grouping for each number range interval created in the activity Defining Number
Ranges for CRM Business Partners.
2. Enter the following values:
Field Value Remarks

Grouping <ID> Choose a grouping with a leading character

that indicates that this grouping should not be
used when creating business partners in the
CRM system, e.g. ‘R’
Short name <Short name>, e.g. R/3 Choose a name indicating that this grouping is
Customer used for the corresponding R/3 account group
Description <Description>, e.g. R/3
Customer
Number range <Number range> Choose one of the number ranges you have
created before.
External Selected External number assignment is required.

3. Choose Enter.
[Link] Deselected This field has to be set only for the grouping
that is used for the classification Consumer:
Person
[Link] Deselected

4. Save your entries

4.1.7 Creating R/3 Reference Customer

[Link] Use
Attention:
This activity is not valid
x for R/3 releases less than 4.6
x if a reference customer for consumer is already created

Business partners with the classification Consumer: Persons are distributed as business
partner master data for consumers to the R/3 system (as of release 4.6). The sales area data
copied from the reference business partner to the business partner master records for
consumers in the CRM is not distributed to the customer master records in the R/3 system.

SAP AG page 95
SAP CRM Setup and Load Guide

The sales area data for consumers in the R/3 system is determined from the R/3 reference
customer. For these data use an existing account group you created as customer master
records for consumers in the R/3 system, e.g. account group 0170.
You have to create a customer master record that can be used as reference customer. This
customer must have consistent sales area data for all sales areas that can be assigned to a
consumer, which is created in the CRM system.
Attention:
Do not choose an existing customer as reference business partner.
The reference customer does not have to be a consumer himself. Create the reference
customer as Sold-To-Party.

[Link] Procedure
R/3 Creating R/3 Reference Customer
Transaction code XD01
SAP Menu Logistics o Logistics Execution o Master Data o Partner o Customer
o Create o Total
1. Create a new customer master record and maintain all relevant data.
You can also copy this business partner from an existing business partner where typical
sales area data is already maintained.

4.1.8 Assigning Consumer to Reference Customer

[Link] Use
Attention:
This activity is not valid
x for R/3 releases less than 4.6
x if a reference customer for consumer is already created

There is only one reference customer in an R/3 client. This reference customer is implicitly
assigned to the account group for consumers.

[Link] Procedure
R/3 Assigning Consumer – Reference Customer
Transaction code VD07
SAP Menu Logistics o Sales and Distribution o Master Data o Business Partners
o Customer o Assign Consumer – ref. Customer
1. In the field Ref. customer enter the business partner you have created in the activity
Creating Business Partner for Reference Customer.
2. Choose Enter.
3. Save your entries.

4.1.9 Creating Account Group for CRM Consumers

[Link] Use
Attention:
This activity is only valid for R/3 system releases less than 4.6.

SAP AG page 96
SAP CRM Setup and Load Guide

You have to create a new account group for the mapping of business partner classifications
Consumer: Organizations and Consumer: Persons. The mapping is described in the following
activity.

[Link] Procedure
R/3 Creating Account Group for Consumers
Transaction code OVT0
IMG Path Logistics General o Logistics Basic Data: Business partners o
Customers o Control o Define account groups and field selection for
customer
1. Create a new account groups by copying account group 0001.
2. Select account group 0001 and choose Copy as.
3. Enter the following values:
Field Value Remarks
Account Group (ID) <ID> Choose an ID beginning with ‘Z’ , e.g. Z0170.
Account Group (Name) <Short name> Choose a name indicating that this account
group is used for the mapping of CRM
consumers, e.g. CRM Consumers.
Number range <Number range ID> Choose a number range corresponding to the
number range for the classification Consumer
in the CRM system.
4. Save your entries.

4.1.10 Mapping R/3 Account Groups to CRM

Classifications
[Link] Use
For each of the OLTP R/3 account groups you have to define a mapping to a CRM business
partner classification and grouping. In the CRM system, the following business partner
classifications exist:
x Customer
x Consumer: Organization
x Consumer: Person
x Sales Prospect
x Competitor

[Link] Procedure
R/3 Mapping R/3 Account Groups to CRM Classifications
Transaction code PIDE
For each account group you have to specify the classification (for example Consumer) and
the grouping (that is, number ranges).
1. In the dialog structure choose R/3 Æ CRM: Assign Account Grp to BP Classification.
2. Choose New entries.

SAP AG page 97
SAP CRM Setup and Load Guide

3. Enter the following values:

Field Value Remarks

Account Group <Account Group ID> Create an entry for every R/3 account group
even if no mapping should be defined for this
account group
Name <Short name of account Determined automatically
group>
Classification <ID of the CRM business Choose the relevant classification to which the
partner classification> account group should be assigned. Leave this
field empty if no assignment is necessary, i.e.
business partners of this account group don’t
have to be replicated to the CRM system.
The account group for consumers (e.g. 0170)
have to be assigned to the classification
Consumer: Person.
Grouping <Grouping of the CRM Choose the grouping that was created for this
system> classification.
External Selected External number assignment is required to
make sure that the business partner numbers
are identical in R/3 and CRM.

[Link] Example
Account Group Name Classification Grouping External

0001 Sold-to party Customer R001 Selected

0002 Goods recipient Customer R001 Selected

0005 Prospective customer Sales Prospect R001 Selected

0006 Competitor Competitors R001 Selected

0170 Consumer Consumer: Person R002 Selected

... ... ...

4.1.11 Mapping Business Partner Master Data from CRM

to R/3
In order to map the business partner master data from CRM to R/3, you have to run the
following activities:
1. Defining number ranges for CRM business partners.
2. Defining CRM business partner groupings.
3. Creating R/3 business partner number ranges.
4. Creating R/3 account groups.
5. Mapping CRM classifications to R/3 account groups.
The following table describes all relevant elements that have to be maintained for the
mapping of CRM classifications to R/3 account groups. It is also mentioned at which activity

SAP AG page 98
SAP CRM Setup and Load Guide

the element is maintained. It is recommend to maintain this table to keep the overview when
running the following activities.
CRM R/3
Classificati Groupi Numb Interval Number Accou Numb Interval Number
on ng er assignm nt er assignm
range ent group range ent
Step 5 Step 2 Step 1 Step 1 Step 1 Step Step 3 Step 3 Step 3
4/5
Customer C001 C1 000010000 Internal Z001 C1 000010000 External
0- or 0-
000099999 External 000099999
9 9
....
For the example above the mapping runs as follows:
1. A business partner with classification Customer and grouping C001 is created in the
CRM system.
2. The grouping C001 has the number range assignment C1 and internal number
assignment, i.e. a number is automatically created from the interval 0000100000-
0000999999 for this business partner, e.g. 100002.
3. The business partner is replicated to the R/3 system.
4. The classification is assigned to the account group Z001 (sold-to party). The number
range C1 with the same interval as R/3 number range C1 is assigned to account
group Z001. The CRM business partner that is replicated from the CRM system to the
R/3 system gets the CRM number because external number assignment is chosen
for the R/3 number range.

4.1.12 Defining Number Ranges for CRM Business

Partners (Part 2)
[Link] Use
For the business partners created in the CRM system you have to define number ranges. You
can define one number range for all classifications or define for example a separate number
range for each classification.

[Link] Procedure
CRM Defining Number Ranges for CRM Business Partners (II)
Transaction code BUCF
IMG Path Cross Application Components o SAP Business Partner o Business
Partner o Basic Settings o Number Ranges and Groupings Æ Define
Number Ranges
1. Choose Change Intervals.
2. Choose Insert Interval and enter the new number range. Make sure that this interval is
not used in the R/3 system for business partners.
3. It is recommended to use internal number assignment. Therefore the Ext. flag should not
be selected.
4. Save your entries.

SAP AG page 99
SAP CRM Setup and Load Guide

4.1.13 Defining CRM Business Partners Groupings (Part

2)
[Link] Use
For each number range created in the activity “Defining Number Ranges for CRM Business
Partners (II)” you have to create a grouping. This grouping has to be assigned manually or
automatically when creating a business partner. The business partner gets a number from the
number range that is assigned to the grouping.

[Link] Procedure
CRM Defining CRM Business Partners Groupings (II)
Transaction code SPRO
IMG Path Cross Application Components Æ SAP Business Partner Æ Business
Partner o Basic Settings Æ Number Ranges and Groupings Æ Define
Grouping and Assign Number Ranges
1. Choose New Entries.
Create a grouping for each number range interval created in the activity Defining Number
Ranges for CRM Business Partners.
2. Enter the following values:
Field Value Remarks

Grouping <ID> Choose a grouping with a leading character

that indicates that this grouping should be used
when creating business partners in the CRM
system, e.g. ‘C’
Short name <Short name>, e.g. CRM Choose a name indicating that this grouping is
Customer used for the corresponding R/3 account group
Description <Description>, e.g. CRN
Customer
Number range <Number range> Choose one of the number ranges you have
created before.
External <Flag for external number Set automatically according to the selected
assignment> number range
3. Choose Enter.
[Link] Deselected

[Link] Deselected

4. Save your entries

4.1.14 Creating R/3 Business Partner Number Ranges

[Link] Use
For all number ranges created in the CRM system as described in “Defining Number Ranges
for CRM Business Partners (II)”, you have to define a corresponding number range in the R/3
Backend system. This is necessary to ensure that a business partners created in the CRM
system get the same ID when they are replicated to the R/3 Backend system.

[Link] Procedure

SAP AG page 100

SAP CRM Setup and Load Guide

R/3 Defining R/3 Business Partner Number Ranges

Transaction code OVZC
IMG Path Logistics - GeneraloBusiness Partner o Customers o ControloDefine
and assign customer number ranges
1. Choose Define Number Ranges for Customer Master.
2. Choose Change Intervals.
3. Choose Insert Interval and enter the number range according to the CRM number range
created in the activity Defining CRM Business Partner Number Ranges II.
4. The Ext. flag has to be selected.
5. Save your entries.

4.1.15 Creating R/3 Account Groups

[Link] Use
In order to map the CRM business partner classifications to R/3 account groups for the
replication of business partners from the CRM system to the OLTP R/3 you have to define a
separate account group for each classification (exception: Consumer: Person)
You can’t use the same account groups that you have chosen for the replication from the
OLTP R/3 into the CRM system, because this would cause inconsistencies. For example:
Account group 0001 is mapped to classification Customer for both replication directions R/3
Æ CRM and CRM Æ R/3. When two different customers are created at the same time in R/3
and CRM it is possible that they get the same number. In this case the replication would not
work because the customer number that have to be created in the receiving system is already
blocked.
Attention:
These account groups should not be used for creating business partners in the R/3 system,
because business partners belonging to these account groups are not replicated to the CRM
system.

[Link] Procedure
R/3 Creating R/3 Account Groups
Transaction code OVT0
IMG Path Logistics General o Business Partner o Customers o Control o Define
Account Groups and Field Selection for Customer
1. Create account groups for each CRM classification according to the following
recommendation:
CRM Classification R/3 Account Group
Customer Copy of 0001
Consumer: Organization Copy of 0001
Consumer: Person No copy!
Competitor Copy of 0006
Prospective Customer Copy of 0005
2. Create the new account groups by copying from the original account group. Select the
account group and choose Copy as.
3. Enter the following values:

SAP AG page 101

SAP CRM Setup and Load Guide

Field Value Remarks

Account Group (ID) <ID> Choose an ID beginning with ‘Z’ , e.g. Z001 for
the copy of account group 0001.
Account Group (Name) <Short name> Choose a name indicating that this account
group is used for the mapping of CRM
classifications, e.g. CRM Customer for the
copy of account group 0001.
Number range <Number range ID> Choose the number range you have created in
the activity Creating R/3 business partner
number ranges for the classification the
account group is defined for.
4. Save your entries.
After creating the new account groups you have to define the allowed partner functions for
this account group.
R/3 Define Partner Functions
Transaction code VOPA
IMG Path Sales and Distribution Æ Basic Functions Æ Partner Determination Æ
Define Partner Functions
1. Select partner object Customer Master.
2. Choose Partner Functions
3. Choose Environment Æ Acct grp assignment.
4. Overwrite an existing line with the following data.
The overwritten data will not be deleted.
Field Value

Funct SP

Acct group <Account Group>

5. Repeat this step with the values (SH, <Account Group>), (BP, <Account Group>) and
(PY, <Account Group>)
6. Save your entries.

4.1.16 Mapping CRM Classifications to R/3 Account

Groups
[Link] Use
For each of the CRM business partner classifications you have to define a mapping to a R/3
account group. Use the R/3 account groups you have created in “Creating R/3 Account
Groups”.

[Link] Procedure
R/3 Mapping CRM Classifications to R/3 Account Groups
Transaction code PIDE
For each account group you have to specify the classification (for example Consumer) and
the grouping (that is, number ranges).

SAP AG page 102

SAP CRM Setup and Load Guide

1. In the dialog structure choose CRM Æ R/3: Assign BP Classification to Account Grp.
2. Choose New entries.
3. Enter the mapping according to the following recommendation:

[Link].1.1 Recommendation for Consumer:

The business partner data that you create in CRM as consumers, it is important to know
whether the business partners are organizations or persons.
x Organizations are distributed to the R/3 system as business partner master
data for customers, and not for consumers. Thus, the sales area data that
was copied from the reference business partner to business partner master
records for consumers in CRM is distributed to customer master records in
the R/3 system. Create an account group in the R/3 system specifically for
business partner master records with the classification Consumer:
Organization of the CRM system. Do not use an existing account group that
you created in the R/3 system for customer master records for consumers.
x Persons are distributed as business partner master data for consumers to the
R/3 system (as of release 4.6). The sales area data copied from the
reference business partner to the business partner master records for
consumers in the CRM is not distributed to the customer master records in
the R/3 system. The sales area data for consumers in the R/3 system is
determined from the reference customer. For these data use an existing
account group you created as customer master records for consumers in the
R/3 system.

[Link].1.2 Recommendation for Customer

Assign the account group that is relevant in the R/3 system for customers. This is also
assigned when the business partner is additionally classified as a prospective customer and a
competitor in the CRM system.

[Link].1.3 Recommendation for Prospective Customer

Assign the account group that is relevant in the R/3 system for prospective customers. This is
also assigned when the business partner is additionally classified as a competitor in CRM.

[Link].1.4 Recommendation for Competitor

Assign the account group that is relevant as competitors in the R/3 system.
Attention:
If you have maintained neither an account group for consumers, nor a reference customer in
the R/3 system or in case that the release of your R/3 system is earlier than 4.6, do not assign
an account group for these data but use the new account group for both situations:
organizations or persons.

[Link] Example
CRM Classification R/3 Account Group
Customer Copy of 0001 (sold-to party)
Consumer: Organization Copy of 0001 (sold-to party) or
Z170 for R/3 < 4.6
Consumer: Person 0170 or
Z170 for R/3 < 4.6
Competitor Copy of 0006 (competitor)
Prospective Customer Copy of 0005 (prospective customer

SAP AG page 103

SAP CRM Setup and Load Guide

5 Checklist
This checklist was developed to provide you with a list of sequential
tasks for setting up the CRM 3.0 Server after the installation.

5.1 Setup activities directly after an installation or an upgrade

of the CRM 3.0 Server
After the installation of CRM 3.0, see Note 369963 first
After the Upgrade to CRM 3.0, see Note 369960 first
Set up logical Systems (page 8)
Create RFC Users (page 9)
Define RFC destinations (see page 9)
Define logical system name for Mobile Clients (page 9)
Define BW communication (page 9)
BW customer fact sheet (page 9)
Define APO communication (page 6)
Generat Industry-Specific Runtime Objects (page 11)
Regenerate Filter Objects After Client Copy (page 12)

5.2 Site IDs and Subscription setting

Define the R/3 Site (page 12)
Define Mobile Clients (page 14)
Create Subscriptions (page 15)

5.3 Preparing for Initial load

Oracle Database: Optimizing the OLTP load time
(note 114716, page 17)
Oracle Database: Starting Initial load (note 162956)
MS SQL Server: Adding a Startup Parameter
Setting up the Middleware for Master Data transfer
Configuring the CRM server for message processing (page 19)
Workflow Customizing (page 23)
Error Handler Setup (page 24)

5.4 The flows of the objects loading

Customizing Objects (page 27)

SAP AG page 104

SAP CRM Setup and Load Guide

Business Application objects (page 34)

5.5 Configuration & Customizing initial loa

Manual definition of the product hierarchy structure (page 36)
Definition of the product key (length, display, save) in
CRM (page 40)
Definition of the plant (page 40)
Initial Customizing load (page 40)
Mapping Account group and classification for business
partners (page 42)
Address title (page 49)
Setup Taxes (page 49)
Define Assignment of Tax Data for products from R/3 to CRM
(page 52)
Define Assignment of Tax Data for Tax Condition Records
from R/3 to CRM (page 54)

5.6 Setting up the Organizational Management

Analysis of the relevant sales areas in OLTP (page 58)
Definition of the replace division in CRM (page 58)
Definition of the Distribution Channel in CRM (page 59)
Maintain Organizational Model (Root definition) (page 59)
Creating sales organizations (page 60)

5.7 Application Data (initial)

Initial load of customers from R/3 customer master data
(Standard R/3 system) (page 65)
Initial load of Business Partners (page 67)
Initial load of Contact Persons (Relations) (page 68)
Initial load of business partner from R/3 business partner
master data (IBU R/3 system) (page 68)
Initial load of Business partner IBU R/3 (page 68)
Initial load of Contact Persons (Relations) IBU R/3 (page 69)
Customer hierarchy and business partner group (page 69)
Initial load of Plants (page 71)
Initial load of Materials and Services (page 75)

SAP AG page 105

SAP CRM Setup and Load Guide

Initial load of Conditions (page 79)

Load the configuration of conditions and price
determination (page 79)
Run correction and generation report (page 80 see also
note 314542)
Providing the infrastructure to distribute condition master
data to the CDB and Mobile Client (page 81)
Load condition master data (page 84)
Initial load of further objects (page 85)

5.8 Delta load of Master Data

MW Server Job-Scheduling (page 85)
Statistics (page 86)
Activate delta events (page 86)
Replication & Realignment Queues (page 87)

SAP AG page 106

SAP CRM Setup and Load Guide

6 Contact

For questions about this Setup and Load guide, You may contact:

Joerg Blattner CRM Production Management

Email : [Link]@[Link]
Address: SAP AG
Neurottstrasse 16
D-69190 Walldorf/Baden
Germany

SAP AG page 107