4 crm customizing replicationapi.ning.com/.../crmcustomizingreplication.pdfcrm customizing...

CRM Customizing Replication

Contents

Configuration Guide................................................................................................................... 2

1 Purpose........................................................................................................................... 2

2 Preparation ..................................................................................................................... 3

2.1 Prerequisites ............................................................................................................ 3

2.2 SAP Notes................................................................................................................ 3

3 Configuration .................................................................................................................. 3

3.1 Preliminary Activities for Replication........................................................................ 3

3.1.1 Registering Queues............................................................................................ 3

3.1.2 Starting Queue Demon and Queues .................................................................. 4

3.1.3 Setting Up Error Handler (SAP CRM) ................................................................ 4

3.2 Configuration Replication ECC -> CRM................................................................... 5

3.2.1 Checking ISO Codes (SAP ECC)....................................................................... 5

3.2.2 Defining Product Hierarchy Structure................................................................. 6

3.2.2.1 Checking Product Hierarchy Structure in OLTP (SAP ECC)...................... 6

3.2.2.2 Defining Product Hierarchy Structure (SAP CRM) ..................................... 6

3.2.3 Defining Product ID Settings (SAP CRM) .......................................................... 7

3.2.4 Replicating Customizing Objects (SAP CRM).................................................... 8

3.2.4.1 Replicating Customizing Objects from ECC OLTP to CRM System .......... 8

3.2.4.2 Monitoring Replication Status (SAP CRM) ................................................. 9

3.2.5 Replicating Condition Customizing................................................................... 10

3.2.5.1 Selecting Condition Customizing for Replication (SAP CRM).................. 10

3.2.5.2 Replicating Condition Customizing (SAP CRM) ....................................... 12

3.2.5.3 Monitoring Replication Status ................................................................... 12

3.2.5.4 Correcting Condition Customizing ............................................................ 13 3.2.5.4.1 Checking the Condition Customizing Download............................... 13 3.2.5.4.2 Mapping Customer-Specific Condition Tables.................................. 14 3.2.5.4.3 Creating ECC Adapter Objects (SAP CRM) ..................................... 14 3.2.5.4.4 Replicating Single Condition Tables (SAP CRM) ............................. 16

3.2.6 Setting Up Taxes .............................................................................................. 16

3.2.6.1 Defining Tax Types................................................................................... 17

3.2.6.2 Defining Business Partner Tax Groups .................................................... 18

3.2.6.3 Defining BP Tax Classification Assignment Settings................................ 19

3.2.6.4 Replicating Tax Customizing (SAP CRM) ................................................ 21

3.2.6.5 Monitoring Replication Status (SAP CRM) ............................................... 21

3.2.6.6 Defining Tax Type and Group................................................................... 21

3.2.6.7 Defining Assignment of Product Tax Data from ECC to CRM ................. 22

3.2.6.8 Checking Customizing of Data Transfer for Taxes (SAP CRM)............... 24

3.3 Setting Up the Organization Model ........................................................................ 25

3.4 Replicating Master Data and Transaction Data ..................................................... 25

3.5 Tips and Tricks for the Replication Process........................................................... 25

3.5.1 Object Management ......................................................................................... 25

3.5.1.1 Changing Block Size................................................................................. 25

3.5.1.2 Defining Filters for Objects ....................................................................... 26

3.5.2 Improving Performance During Replication...................................................... 27

3.5.3 Monitoring and Error Analysis for Replication .................................................. 27

3.5.3.1 Monitoring Download Status..................................................................... 28

3.5.3.2 General Analysis Steps ............................................................................ 29

3.5.3.3 Monitoring Outbound Queue .................................................................... 29

3.5.3.4 Monitoring Inbound Queue ....................................................................... 29

3.5.3.5 Analyzing BDOC Messages ..................................................................... 30

3.5.3.6 Checking Transactional RFC Requests ................................................... 30

3.5.3.7 Analyzing ABAP Dumps ........................................................................... 31

3.5.4 Restart Replication ........................................................................................... 31

3.5.4.1 Canceling Download of Objects................................................................ 32

3.5.4.2 Deleting Outbound Queue ........................................................................ 32

3.5.4.3 Deleting Inbound Queue........................................................................... 32

3.6 Checking Delta Replication Events........................................................................ 33

Configuration Guide

1 Purpose This building block (Configuration Guide) describes the necessary activities to replicate data from the ECC system to the CRM system and vice versa. This building block is the prerequisite for the installation of all CRM scenarios delivered by SAP Best Practices. This building block is not required if you run the CRM in a stand-alone mode, that is without an OLTP back-end system.

CRM requires data from the ECC system in the following areas:

• Customizing

• Master data

− Business partners

− Contact persons

− Materials

− Conditions

− Sales documents

The purpose of this document is to describe the general configuration steps required to manually set up the configuration within the system landscape that has already been installed using the corresponding installation or configuration guides for installation.

The Configuration Guide describes how to set up the configuration of a building block manually.

2 Preparation

2.1 Prerequisites

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

2.2 SAP Notes

Before you begin the installation and configuration, read the relevant SAP Notes. These SAP Notes contain important information for installation and configuration, and also corrections concerning this building block.

Make sure that you have the most up-to-date version of SAP Notes. You can find the SAP Notes on the SAP Service Marketplace (http://service.sap.com/notes) or in SAPNet.

SAP Note Area Title

ECC System

CRM System

432339 CRM-MD-PRO-IF-CAT Errors during Customizing download DNL_CUST_PROD1

435598 CRM-BF-TAX Initial download of object DNL_CUST_TAX

490932 CRM-BTX-BF-IF Data exchange of sales transactions CRM – R/3 (see chapter “Queue processing during the upload/delta download”)

729669 CRM-MW-ADP Filters are not used

756567 CRM-BF Download Customizing Basis from OLTP 640

3 Configuration

3.1 Preliminary Activities for Replication

3.1.1 Registering Queues

Use

All replication and realignment queues for the data exchange between the ECC system and the CRM system are registered automatically when starting the replication.

The CSA queues have to be registered manually.

Procedure

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

Transaction code SMQR

SAP CRM IMG menu CRM � CRM Middleware and Related Components � Queue Setup � Register CSA Queues

2. Choose Registration.

3. On the Queue Registration screen, make the following entries:

Field name User action and values

Queue name CSA*

EXEMODE D

MAXTIME 60

USERDEST

NRETRY 30

TDELAY 300

4. Register an additional queue:

Field name User action and values

Queue name R3A*

EXEMODE D

MAXTIME 60

USERDEST

NRETRY 30

TDELAY 300

5. Choose Continue.

Result

The CSA* queue is registered and will be displayed in the queue list.

3.1.2 Starting Queue Demon and Queues

Procedure


Transaction code SMOHQUEUE

SAP CRM IMG menu Architecture and Technology � Middleware � Monitoring � Queues � Monitor R&R Queues

2. Choose Start Queue Demon.

3. Release all queues by choosing Release Queue.

3.1.3 Setting Up Error Handler (SAP CRM)

Use

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

Procedure

1. Access the activity using the following navigation options:

Transaction code SPRO

SAP CRM IMG menu Customer Relationship Management � CRM Middleware and Related Components � Message Flow Setup � Assign Error Actions to Messages

2. Select Default Error Action.

3. Choose Execute (F8).

4. Select Maintain Configuration (F9)

5. Select Mail as Error Action.

6. Enter the following data as Mail Parameters.

Field name Value

E-Mail Address of Receivers

<USER ID> of the user that is logged on

E-Mail Type B

7. Choose Save.


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

Result

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

3.2 Configuration Replication ECC -> CRM

3.2.1 Checking ISO Codes (SAP ECC)

Use

Before starting the Customizing replication, verify that entries for the ISO codes are unique in the following ECC tables:

• Language keys (T002 field LAISO)

• Currency codes (TCURC field ISOCD)

• Countries (T005 field INTCA).

Although SAP delivers these tables in a consistent state, duplicate ISO entries can occur because this is not a key field in those tables (especially if own entries have been set up with copy functions).

Procedure


Transaction code SE16

SAP ECC menu Tools � ABAP Workbench � Overview � Data Browser

2. In the table name field enter T002.

3. Choose Table Contents (Enter).


5. Check the column LAISO for duplicate entries.

6. Repeat these steps for the other tables.

If duplicate ISO codes are detected, they have to be replaced by new ISO codes. The final result has to be that all tables mentioned hold unique ISO code entries. Multiple entries with empty ISO codes are possible. Duplicate entries cannot be deleted directly in transaction SE16. If you want to delete database records please get advice from experienced consultants or enter an SAP message.

3.2.2 Defining Product Hierarchy Structure

Please check the Delta Guide.

3.2.2.1 Checking Product Hierarchy Structure in OLTP (SAP ECC)

Procedure



SAP ECC menu Tools � ABAP Workbench � Development � ABAP Dictionary

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

3. Choose Display.

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

3.2.2.2 Defining Product Hierarchy Structure (SAP CRM)

Procedure



SAP CRM IMG menu Cross Application Components → SAP Product →

Product Category → Define Category Numbering Schemes

2. Choose New entries.

3. Make the following entries:

Field name Entry

Number Scheme R3PRODHIER

Scheme Description (EN) Numbering Scheme R/3

Scheme Description (DE) R/3 Nummerierungschema

Ignore the warning message.

4. Mark number scheme R3PRODHIER and double-click on folder Define Numbering Scheme Levels.

5. Choose New entries and enter the matching levels and number of digits for each level. They need to be exactly the same as in the OLTP system.

Example (SAP standard delivery):

Level Number of Digits

1 5

2 5

3 8

3.2.3 Defining Product ID Settings (SAP CRM)

Use

The output format and storage form of product IDs have to be defined.

If you intend to replicate product data to an ECC System, the number of characters you specify will determine whether you can use the product ID as the material number.

This activity describes how to synchronize the product IDs in the CRM system and the ECC system.

Procedure


Transaction code COMCPRFORMAT

SAP CRM IMG menu Cross-Application Components → SAP Product → Basic

Settings → Define Output Format and Storage Format of Product Ids

2. Check the product ID settings in the ECC system by calling transaction OMSL in the ECC system.

3. Enter the following values on the Material Number Format screen in the CRM system. Choose New Entries if no number format exists.

Field Value

Prod. ID Length Value of field Material No. Length in the ECC system (OMSL)

Template for ID Value of field Material Number Template in the ECC system

Display Leading Zeros Value of field Leading Zeros in the ECC system

Save Lexicographically Value of field Lexicographical in the ECC system

For more information, see SAP Note 545824.

3.2.4 Replicating Customizing Objects (SAP CRM)

3.2.4.1 Replicating Customizing Objects from ECC OLTP to CRM System

Prerequisites

If you have any problems while downloading the object DNL_CUST_S_AREA, please refer to SAP Note 437477. Step 6 is still valid and you have to add the table (Source Site) CRMC_DIVISION_T with the Mapped Structure (Target Site) SMOTSPAT.

Use

The following objects are relevant to the download from ECC OLTP to the CRM system.

Object Name Description

DNL_CUST_ACGRPB Accounting Group Business Partner

DNL_CUST_ACGRPP Account Group Product

DNL_CUST_ADDR Regional structure

DNL_CUST_BASIS Basis CRM online

DNL_CUST_BASIS2 Basis CRM online




DNL_CUST_BNKA Banking Master

DNL_CUST_KTOKD Business Partner: Acc. Group

DNL_CUST_PAYPL Payplan

DNL_CUST_PRICE Sales pricing and pricing item

DNL_CUST_PROD0 Material number conversions

DNL_CUST_PROD1 Product: categories

DNL_CUST_PROD3 Material: R/3 sales status

DNL_CUST_S_AREA Organizational Unit: Divisions

DNL_CUST_SALES Sales

DNL_CUST_SCE SCE varcond

DNL_CUST_SHIP Sales shipping

DNL_CUST_SPROD Sales product item

DNL_CUST_T502T Business Partner: T502T

DNL_CUST_TBRC Business Partner: Industries

DNL_CUST_TKUKL Business Partner: TKUKL, TKUKT

DNL_CUST_TNLS Business Partner: TNLS, TNLST

DNL_CUST_TPFK Business Partner: TPFK, TPFKT

DNL_CUST_TSAB Business Partner: TSAB, TSABT

Object Name Description

DNL_CUST_TVAST Sales Document Blocking Reason

DNL_CUST_TVFS Sales Document Billing: Block

DNL_CUST_TVGF Business Partner: TVGF, TVGFT

DNL_CUST_TVIP Business Partner: TVIP, TVIPT

DNL_CUST_TVKN Business Partner: Attributes

DNL_CUST_TVLS Deliveries: Blocking Reasons/C

DNL_CUST_TVPV Business Partner: TVPV, TVPVT

DNL_PLANT Plant

Procedure


Transaction code R3AS

SAP CRM menu Architecture and Technology � Middleware � Data Exchange � Initial Load � Start

2. In the Load Object field, enter an object from the table above.

3. In the Source Site (Sender) field enter OLTP and in the Destination Site (Receiver) field,

enter CRM.

4. To run the replication, choose Execute.

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

3.2.4.2 Monitoring Replication Status (SAP CRM)

Procedure


Transaction code R3AM1

SAP CRM menu Architecture and Technology � Middleware � Data Exchange � Initial Load � Monitor Objects

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

3. Choose Execute.

Result

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

In case of problems during replication refer to section Tips and Tricks for Replication of this guide.

3.2.5 Replicating Condition Customizing


3.2.5.1 Selecting Condition Customizing for Replication (SAP CRM)

Use

An important prerequisite to the successful initial download of condition customizing is that all the necessary filter settings are in place. Without using a filter all customizing objects, i.e. pricing procedures etc. are replicated.

For that reason it would be a good option not to use object DNL_CUST_CNDALL for the download of condition customizing but to create another object (for example YDNL_CUST_CNDALL) and to set up the filters according your business needs.

When creating a new condition customizing download object (e.g., YDNL_CUST_CNDALL) you should work together with an SD consultant with profound pricing knowledge to define the tables and filter settings being used. Otherwise use object DNL_CUST_CNDALL to download all customizing objects.

In order get the gross value displayed in crm sales documents please see SAP note 340099.

Procedure


Transaction code R3AC5

SAP CRM menu Architecture and Technology � Middleware → Data

Exchange → Object Management → Condition Objects

2. On the Object Overview screen choose Display->Change to make sure that you are in change mode.

3. If you want to create a new condition customizing download object (e.g., YDNL_CUST_CNDALL) choose Create Object. Make sure that you enter exactly the same information for the new object as you have for DNL_CUST_CNDALL.

4. Save your entries.

5. The following table can be used as an orientation for defining table filter settings within the newly created download object. According to your specific data some settings may have to be adapted.

Table Filter settings

MNTCNT Not needed.

T681 Using field KOTAB enter only those condition

tables accessed by condition types from the pricing procedures that you are going to download to the CRM system.

T681T Using field KOTABNR enter only those

condition tables accessed by condition types from the pricing procedures that you are

going to download to the CRM system.

Also restrict the Language key to E using field

SPRAS and the Usage of the condition table to A using field KVEWE.

T681E Using fields KOTABNR enter only those

condition tables accessed by condition types from the pricing procedures that you are going to download to the CRM system.

Also restrict the Usage of the condition table to A using field KVEWE.

T682, T682I, T682T, T682Z Using field KOZGF enter only those access

sequences used by condition types from the pricing procedures that you are going to download to the CRM system.

T682V It is recommended that you set filters on fields KVEWE and KAPPL, restricting download only to Usage A Pricing and Applications V Sales/Distribution.

T683, T683S, T683U, T683T Set a filter on the field KALSM, specifying only those pricing procedures you want to use in the CRM system.

It is recommended that you also set filters on fields KVEWE and KAPPL, restricting download only to Usage A Pricing and Applications V Sales/Distribution

T684, T684G, T684T, T684S Specify filter settings only if you use condition exclusion groups in your pricing precedures that you are downloading to the CRM stystem. Otherwise, deactivate these tables.

T68 5, T685A, T685T, T685Z Using field KSCHL enter only those condition

types which you use in the pricing procedures that you are going to download to the CRM system.

It is recommended that you also set filters on fields KVEWE and KAPPL, restricting download only to Usage A Pricing and Applications V Sales/Distribution

T686E, T686F You can leave these tables without filter settings.

TMC1 Using field GSTRU only enter those condition

tables, which are accessed by condition types from the pricing procedures that you are going to download to the CRM system.

TMC1D You can leave these tables without filter settings.

3.2.5.2 Replicating Condition Customizing (SAP CRM)

Prerequisites

Check the pricing procedure you are using. If you want to show a gross value in your documents you must assign the subtotal 9 to the Gross Value. This is mandatory for E-Commerce Sales scenarios.

Use

There are four objects to be loaded. These are:

• DNL_CUST_CNDALL (or YDNL_CUST_CNDALL if created in the section above) and DNL_CUST_CND for condition technique

• DNL_CUST_PRC for Pricing information

• DNL_CUST_FGD for free goods

The differences between the above objects are that DNL_CUST_CNDALL includes all data including client independent and dependent tables and all those tables are in active mode. DNL_CUST_CND also includes client independent and dependent tables but only client dependent tables are in active mode, and DNL_CUST_PRC and DNL_CUST_FGD only includes client dependent tables and they are in active mode.

SAP recommends you to 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.

For more information about the Customizing download of the condition technique, see SAP Help Portal under mySAP Customer Relationship Management -> Components and Functions -> Master Data -> Condition Technique -> Data Exchange for Conditions.

Procedure




2. In the Load Object field, enter an object according to the recommendation above.

3. In the Source Site field enter OLTP and in the Destination Site field enter CRM.

4. To run the replication, choose Execute (F8)

5. Repeat this step for other required objects.

3.2.5.3 Monitoring Replication Status

Procedure




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

Result


In case of problems during replication refer to section Tips and Tricks for Replication of this guide.

3.2.5.4 Correcting Condition Customizing

Use

In this activity you have to analyze and correct the condition customizing that has been replicated from the ECC system into the CRM system.

3.2.5.4.1 Checking the Condition Customizing Download

Use

In this activity you check whether all condition tables of your pricing procedure are replicated and generated correctly.

Procedure

1. Access the activity using the following navigation option:

Transaction code SLG1

2. Enter the following data:

Field name Value

Object COND_EXCHANGE

Subobject CUSTOMIZING

From (date/time) e.g. 01.10.2003

To (date/time) e.g. Current date

The other fields are default.

3. Choose Execute (F8)

4. On the next screen you will see the display logs with the results of the condition exchange of customizing. You see the date/time/user and a list of messages, for example:

5. You have to check the red status with the problem class important what kind of errors is occurred. You have to click double on the message and the details with message text appear in screen below. You have to check whether all errors are with your used condition tables in the pricing process. You can choose the icon long text to see more details.

Check SAP Note 314542 for a general problem solving procedure.

6. For condition tables you also have to check whether a corresponding ECC adapter object is available.

7. Start the transaction SE16.

8. In the field Table name enter SMOFTABLES and choose Table contents (Enter).

9. In the OBJNAME field enter DNL_COND_A* and choose Execute (F8).

Note the status of the adapter object in your analysis table below.

Object name R3TABNAME Inactive

DNL_COND_A002 A002 <empty>

DNL_COND_A005 A005 <empty>

3.2.5.4.2 Mapping Customer-Specific Condition Tables

Use

You created a condition table in ECC OLTP and you want to create the corresponding table in CRM, but in CRM at least one of the fields of the condition table is not supported in the standard.

Procedure

In the activity Checking and Comparing the Customizing Download you have got a message like "The condition table XXX has a field with initial name", where XXX is a concatenated string of application, usage and table number of the condition table.

In this case please apply SAP Note 514952 (Download of customer-specific tables) to create your customer-specific table fields in the CRM system.

3.2.5.4.3 Creating ECC Adapter Objects (SAP CRM)

Use

Run this activity only if you have detected missing ECC adapter object in the activity Checking the Condition Customizing Download.

The procedure described below is valid for every condition object. The only variable part is the ECC table that has to be mapped.

Prerequisites

Before running this activity please check if the condition table in ECC OLTP you want to create has a corresponding table in CRM.

Please refer to note 514952.

Procedure



SAP CRM menu Architecture and Technology � Middleware � Data Exchange � Object Management � Condition Objects

2. Choose Display � Change.

3. Choose Create Object (F6).

4. Enter the following data:

Field Entry

Object name ID of the adapter object, e.g. ZDNL_COND_A999

5. Choose Enter.

Field Entry

Object name Description of the adapter object, e.g. Condition table A999

Linked BDoc CND_MAST_DEEP_SUP

Enter the data for this field using the input help. Otherwise it will not be saved.

Block Size 1000

Inactive Object

not selected

Function No entry

Initial Flow Contexts

Source Site Type

R/3

Tables and Structures

Table (Source Site)

<R/3 condition table>, for ex. A999 KONH KONM KONP KONW TMC1K

Mapping Modules

Module name

CND_MAP_MAST_EXCHANGE_MAIN_MBD


3.2.5.4.4 Replicating Single Condition Tables (SAP CRM)

Use

The condition tables for which a new adapter object was created in the step Creating ECC Adapter Objects have to be downloaded again.

Prerequisites

This activity can be omitted for the initial download because the condition replication is

described in section Replicating Master Data ECC → CRM. It is only required when changing and replicating condition customizing with additional adapter objects after the initial download.

Procedure



SAP CRM menu Middleware � Data Exchange � Initial Load � Start

2. In the Load Object field, enter the condition object that has to be downloaded again with the newly created adapter object.

3. In the Source Site field enter OLTP and in the Destination Site field enter CRM.

4. To run the replication, choose Execute (F8).

5. Repeat this step for other required objects.

3.2.6 Setting Up Taxes


In CRM standard, there is no automatic generating and transferring function for all of the configuration about taxes from OLTP to CRM yet. To transfer it from OLTP to CRM, it is necessary to maintain a mapping table in the CRM system.

The new mapping allows you to have more complex tax determination combined with easier setup. The determination is based on the combinations of: country + region + tax type + tax group. The tax group of a certain tax type determines, for example, if a product is fully or partly taxed or exempted from this tax.

This information is also used by a third party program that finally determines the applicable tax rate.

How does the transfer logic from ECC OLTP to CRM work?

• Products: All existing tax data which is material based (table MLAN) is transferred. To function correctly the mapping of tax setup needs to be consistent on both sides. Otherwise the data transfer stops.

• Business Partners: The mapping of the tax classification is already done in ECC. The new configuration objects also have to be maintained in the ECC system since the business partner mapping is done in ECC system. The Configuration load imports data from the following tables of the ECC System into the following tables of the CRM System:

ECC System CRM System

Tax Types TSTL TB070

BP Tax Groups TB071_CM TB071

Mapping of business partner TB072_CM CRMC_TAX_MAP_BP

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

• Condition Records: The data transfer of Condition records for tax calculation requires the mapping for Products and Business Partners.

3.2.6.1 Defining Tax Types

Procedure


Transaction code PITC Then carry out the following steps:

2. Check tables TSTL (Tax categories by countries).

3. For every relevant combination of country and tax category in table TSTL a corresponding entry has to be available in table TB070_CM.

4. Choose the transaction PITC. You branch to the Define Tax Types screen.

5. Check if entries for the relevant countries and tax types exist. If not proceed as follows:

6. Choose Define Tax Types.

7. Choose New Entries.

8. Enter the Country.

9. Enter the Tax Type.

10. Indicate, via the checkboxes, if the tax type is relevant for the Business Partner, Product, or both.

11. Choose Save.

Example of correct mapping

3.2.6.2 Defining Business Partner Tax Groups

Procedure


Transaction code PITC

2. Check tables TSTL and TSKD in the ECC system.

3. For every relevant country and tax category in table TSTL determine the tax classifications in table TSKD. For each combination of country, tax category and tax classification an entry in table TB071_CM consisting of country, tax type and tax group has to exist.

4. Choose transaction PITC.

5. Select a Tax Type.

6. Choose Assign BP Tax Group. Check if an entry according to table TSKD exists. If not proceed as follows:



Enter the Region, if required.

If you calculate tax via the jurisdiction method, you must maintain a region. If this field contains no value, the settings made apply to all regions defined for the country.

9. Enter the Tax Type.

10. Enter the Tax Group.

11. Choose Save.

Example of correct mapping

Result

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

3.2.6.3 Defining BP Tax Classification Assignment Settings

Use

With this activity you replicate ECC tax categories and tax classifications to the CRM system.

You have to map the newly created CRM tax types and tax categories created in the preceding activities to the corresponding ECC tax categories and tax classifications.

Procedure


Transaction code PITM

2. On the screen Tax Classification: Mapping ECC to CRM, choose New Entries.


4. Enter the Region.

5. If you calculate tax via the jurisdiction method, you must maintain a region.

6. Enter the CRM Tax Type.

7. Enter the CRM Tax Group.

8. Enter the R/3 Tax Category.

9. Enter the R/3 Tax Classification.

10. Choose Save.

Example of a correct mapping

3.2.6.4 Replicating Tax Customizing (SAP CRM)

Procedure




2. In the Load Object field, enter DNL_CUST_TAX.

3. In the Source Site (Sender) field enter OLTP and in the Destination Site (Receiver) field

enter CRM.

4. To run the replication, choose Execute (F8).

3.2.6.5 Monitoring Replication Status (SAP CRM)

Procedure




2. In the Object Name field, enter the downloaded object to get the download status of this object. You can also make no entry to get the status of all downloaded objects.

Result


In case of problems during replication, call transaction SMWP (Middleware Portal) and search for error states in the area Runtime Information.

For a detailed error handling see section Tips and Tricks for the Replication Process at the end of this guide.

3.2.6.6 Defining Tax Type and Group

Use

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

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

Procedure



SAP CRM IMG menu Customer Relationship Management → Basic Functions →

Taxes → Basic Settings � Tax Types and Tax Groups � Define Tax Types and Tax Groups

2. Check ECC tables TSTL and TSKM using transaction SE16.

3. Choose the IMG activity Define Tax Types and Tax Groups in the CRM system.

4. Select the countries tax types for which you have to maintain product taxes and choose Assign Product Tax Groups.

5. Choose New entries.

6. For each combination of Country, Tax Category and Tax Classification in the ECC system (tables TSTL and TSKM) create a corresponding entry of Country, Tax Type and Product Tax Group.

Example of a correct mapping

3.2.6.7 Defining Assignment of Product Tax Data from ECC to CRM

Use

In this activity, you can assign the ECC material tax classification (TAXMx) to the combination of country, region (optional), tax type, and tax group defined in the CRM System in the activity Defining Assignment of Tax Data for Products from ECC to CRM.

When data is imported from an ECC System to a CRM System, all existing tax data in the ECC System (table MLAN) is transferred to the CRM System for each material. This requires

Cntry Sequence Tax Type

DE 1 MWST

CA 1 CTX1

CA 2 CTX2

CA 3 CTX3

R/3 Table TSTL

Tax Category Tax

Classification

Text

MWST 0 No tax

MWST 1 Full tax

MWST 2 Half tax

CTX1 0 No tax

CTX1 1 Full tax

CTX2 0 No tax

CTX2 1 Full tax

CTX3 0 No tax

CTX3 1 Full tax

R/3 Table TSKM

Cntry Tax Type Tax Seq

DE MWST 1

CA CTX1 1

CA CTX2 2

CA CTX3 3

CRM Tax Types

Cntry Reg Tax

Type

Product Tax

Group

DE MWST FULL

DE MWST HALF

DE MWST NONE

CA CTX1 FULL

CA CTX1 NONE

CA CTX2 FULL

CA CTX2 NONE

CA CTX3 FULL

CA CTX3 NONE

Product Tax Group

the tax settings to be assigned from the ECC System to the CRM System correctly. If this is not the case, the data transfer process stops.

Procedure



SAP CRM IMG menu Customer Relationship Management → Basic Functions →

Taxes → Basic Settings � Tax Types and Tax Groups � Assign Tax Groups to SAP ECC Tax Classifications (Product)

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

3. For each combination of country, tax category and tax classification in the tables TSTL and TSKM you have to create an entry in the table CRMC_TAX_MAP in the CRM system as follows:

4. Run IMG activity Assign Tax Groups to SAP R/3 Tax Classifications (Product).


6. Enter values for country, tax type, product tax group, tax sequence and tax classification.

Example:

• ECC

• Table TSKM

TATYP TAXKM

CTX1 0

CTX1 1

CTX2 0

CTX2 1

CTX3 0

CTX3 1

• Table TSTL

Country LFDNR TATYP

CA 1 CTX1

CA 2 CTX2

CA 3 CTX3

• CRM

o Table CRMC_TAX_MAP (assignment)

Country Region Tax Type Tax Group Tax Seq. Tax Class.

CA CTX1 NON 1 0

CA CTX1 FULL 1 1

CA CTX2 NON 2 0

CA CTX2 FULL 2 1

CA CTX3 NON 3 0

CA CTX3 FULL 3 1

Result

The product tax data is maintained in the CRM system and synchronized with the ECC system.

The tax information in the product master data will be downloaded in the following way:

3.2.6.8 Checking Customizing of Data Transfer for Taxes (SAP CRM)

Procedure


Transaction code CRM_TAXCUST_VALIDATE

SAP CRM IMG menu Customer Relationship Management → Basic Functions

→ Taxes → Basic Settings → Tax Types and Tax Groups

→ Check Data Transfer Customizing Settings

2. The Check Results screen is displayed.

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

3.3 Setting Up the Organization Model

Please see configuration guide for the Building Block C01 CRM Organization Model for defining the CRM Organizational structure.

The setup of the organizational model is the prerequisite for replicating the master data from the ECC System to the CRM System.

3.4 Replicating Master Data and Transaction Data

Please see configuration guide for the Building Block C03 CRM Master and Transaction Data Replication for this topic.

3.5 Tips and Tricks for the Replication Process

Please see SAP Note 430980 for the latest error analysis procedure.

3.5.1 Object Management

3.5.1.1 Changing Block Size


Use

The block size specifies the number of object instances that will be selected and forwarded in a single operation. The block size is set by the system. The default value only has to be changed if there are problems (for example, memory overflow when making selection in the ECC system).

Procedure



SAP CRM menu Middleware � Data Exchange � Object Management � Business Objects

2. In the Object Overview screen choose Display � Change.

3. Select the object for which the block size should be changed and select the button Filters.

4. Change the entry in the field Block Size.

3.5.1.2 Defining Filters for Objects


Use

Under Filter Settings you can set filters for a business object. For Customizing and condition objects the filters can be defined only using tables/structures and the table-related filter symbol. If you use more than one filter entry per object, filters to the same table field are linked with an OR. Filters to different table fields are linked by AND.

The filter condition VKORG = 0001, VKORG = 0002 results in a set that contains both the first and second sales organization.

The filter condition VKORG = 0001, VTWEG = 01 results in objects that fulfill both conditions at the same time.

Procedure



SAP CRM menu Middleware � Data Exchange � Object Management � Business Objects

2. Mark a business object and choose Details.

3. Choose Filter Settings.

4. Enter the data for the following fields:

Field Procedure

Source site Use the input help to select the site you want to set the filter criteria for. For example, for an initial data transfer from SAP ECC, this is the ECC system from which the data is to be transferred.

Note: The selection is dependent on the allowed flow contexts (SMOFINICON).

Table Use the input help to select a table, for example, KNA1 for customer master.

Field Use the input help to select a field.

OP (Operator) Select an operator.

LOW Specify the lower limit for the filter condition. If the field you selected is a date field, enter the date with the format YYYYMMDD. Leading zeros should be used as values for

example, for customer and material numbers.

HIGH Specify the upper limit.

Incl./Excl. Specify whether the stated value/interval range should be included or not.

Inclusive: the resulting set lies within the range.

Exclusive: The resulting set lies outside the range.

Inactive Set your filter conditions to active.


The Generate Filter pushbutton located below the menu is only used for regenerating filter modules for selected objects, and should only be used in exceptional cases.

• The fields for filtering are available predefined for the objects. You will find the values allowed for each object when you make your selection.

• Some objects are delivered with predefined filters. SAP recommends that you do not change or delete. If necessary, you should define new filters. The purpose of filters is to reduce the size of the dataset transferred. You can find the predefined filters in the change functions of the Adapter Framework and in table SMOFFILTAB.

• Filters from CRM to CDB are currently not supported; only filters from ECC OLTP to CRM are supported.

• Filter conditions are only stored locally and are not contained in the transport of adapter objects. In this way filters are not transported from the development system to the production system. This is because filter conditions are site-specific and are defined differently in the development system to the production system. New filter settings have to be defined in each system.

3.5.2 Improving Performance During Replication


Use

The initial download of objects such as the material master data can lead to performance problems.

Procedure

In order to improve performance, apply SAP Note 0350176.

3.5.3 Monitoring and Error Analysis for Replication


Several tools for monitoring can be used to check the status of the replication.

3.5.3.1 Monitoring Download Status


Use

The list Monitor Objects shows the current download status (Running, Wait, Done) for previously selected objects.

Procedure



SAP CRM menu Middleware� Monitoring � Data Exchange � Monitor Objects

2. Enter either an object name or an object name area or use the F4 input help. Leave the selection empty if you want to display all objects.

3. Under Additional Selection Criteria you can select by the current status: Abort, Waiting, Running or Done.

4. Choose Execute.

5. On the Monitor Download Objects screen you get the following information that gives you hints about the correctness of the download for each object.

Field Value

Checkbox Set the indicator to select a transfer object for further processing.

Status The following values are possible:

• Red (waiting) i.e. not yet started or aborted

• Yellow (Running)

• Green (Done)

Object name

P (Parent) If this indicator is set, there is a superordinate object in the transfer.

Date Date of the last transfer block.

Time Start time of the last transfer block.

Block No. The block number indicates how many blocks have already been downloaded.

If, for example, the block size has been set to 100, then block number 15 means that 1,500 objects have already been posted on the CRM Server database.

Attempt This field shows the number of attempted transfers.

Source Site Specification of the RFC OLTP destination.

Destination Specification of the CRM system or CDB

6. If an object will not start (red light and status = Waiting), check if the object is dependent (field Subobject). Only if the parent object has been loaded successfully, can dependent objects be started, e.g. Material can only be downloaded once Customer has been downloaded, since there are materials dependent on customers.

7. If an object has not changed in the Monitor for a long time, (e.g. no increase in block numbers for the last five minutes), ascertain the reason first and then try to download the object again. In this case you should run the following activities to detect the error.

3.5.3.2 General Analysis Steps


Carry out the following steps:

1. Make sure the highest available Plug-In (PI) Support Packages plus Core Support Packages are installed in the OLTP in the same way as on the CRM/EBP server.

2. Check the setting for ECC table CRMRFCPAR (see chapter Maintaining Table CRMRFCPAR).

3. Check the RFC connections from CRM to ECC and vice versa.

3.5.3.3 Monitoring Outbound Queue


Procedure


Transaction code SMQ1

2. To display a list of the queues, enter the client, queue name (for example *) and the queue destination (for example *).

3. Choose Execute.

4. To display the status, select the queue and choose Display selection (F7).

5. Call a specific outbound queue, select it and choose Display Selection (F7).

6. To display details on a queue, double-click the field Queue name.

7. If the queue was stopped because of capacity overload, use F6 to restart the queue.

8. If a second start of the queue is not successful, call the short dump analysis in the CRM system.

3.5.3.4 Monitoring Inbound Queue


Procedure

1. To view the inbound queues in the CRM system and their status, choose one of the following navigation options:


SAP CRM menu Middleware � Monitoring � Queues � Display Inbound RFC Queues

2. Enter the client and the queue name (for example *).

3. Choose Execute.

4. To display the status, select the queue and choose Display selection (F7).

5. When you double-click the field Status, additional detailed information is generated.

6. To display details on a queue, double-click the Queue name field.

7. On the queue details screen, a red entry in the field Status indicates an error.

8. If the queue has status STOP, this is a Customizing problem in the CRM application.

9. When you double-click on the status field entry detailed information is displayed.

3.5.3.5 Analyzing BDOC Messages


Use

By analyzing the BDOC messages you get information about incorrect settings in the CRM system that influence the replication.

Procedure


Transaction code SMW01

SAP CRM menu Middleware � Monitoring � Message Flow � Display BDOC Messages

2. Specify date and time of the relevant period of time.

3. Choose Execute.

4. BDOC messages with status beginning with E (red traffic light) need manual correction and retry.

5. Select the message and choose Errors.

6. Here you find notes regarding CRM setting problems.

3.5.3.6 Checking Transactional RFC Requests


Procedure


Transaction code SM58

SAP CRM menu Middleware � Monitoring � Transactional RFC � Display Transactional RFC Requests

2. On the initial screen Transactional RFC, specify dates for the display period.

3. Fill in the remaining fields. Alternatively, enter *.

4. Choose Execute.

5. To display further details, drill down in the log.

3.5.3.7 Analyzing ABAP Dumps


Procedure


Transaction code ST22

SAP CRM menu Middleware � Monitoring � Performance � Exceptions/Users � Exceptions � Dump Analysis

2. Specify the period (today, yesterday).

3. Choose Display list (F8).

4. To display the ABAP short dump description, select one of the short dumps and choose Dump analysis (F2).

3.5.4 Restart Replication


Use

After detecting and solving the replication error you have to restart the replication.

While there are no restrictions for repeating data transfers from ECC to CRM, data transfers from CRM to CDB are more serious, because in this case the data has to be distributed. To avoid inconsistencies between the CDB and mobile application databases, a repeated initial data transfer from CRM to CDB is prevented. If you are sure that no mobile clients have been supplied with data or that no data can be extracted again, then a repeated initial data transfer from CRM to CDB can be carried out. To do this, you have to change an entry in table SMOFINICUS.

The table contains the following fields:

• ObjName: Name of object (corresponds to the object name from table SMOFOBJECT)

• BDoc Name: Name of the BDoc

• Data Dist.: determines whether data is distributed (selected) or only written to the CDB (empty)

• User Name: Name of changer.

Table SMOFINICUS is delivered empty. With initial data transfers from CRM to CDB data distribution is automatically selected. If you are sure that mobile clients have still not been supplied with data, then the selection for data distribution can be unselected for the required object using the view maintenance for table SMOFINICUS (transaction code SM30). Then a new initial data transfer can be started for this object.

Table SMOFINICUS replaces parameter CRM_USE_BULK_DURING_INIT of the configuration file SMOFPARSFA.

Procedure

In order to restart the replication you have to run the following steps:

1. Canceling download of objects

2. Deleting outbound queue

3. Deleting inbound queue

4. Restart download

3.5.4.1 Canceling Download of Objects


Procedure



SAP CRM menu Middleware� Monitoring � Data Exchange � Monitor Objects

2. Enter either an object name or an object name area or use the F4 input help. Leave the selection empty if you want to display all objects.

3. Under Additional Selection Criteria you can select the status: Waiting and Running.

4. Choose Execute.

5. On the Monitor Download Objects screen select the objects you want to cancel for download.

6. Choose the Cancel symbol.

3.5.4.2 Deleting Outbound Queue


Procedure



2. To display a list of the queues, enter the client, queue name (for example *) and the queue destination (for example *).

3. Choose Execute.

4. To delete an outbound queue, select the queue and choose Delete selected objects.

3.5.4.3 Deleting Inbound Queue


Procedure



SAP CRM menu Middleware � Monitoring � Queues � Display Inbound RFC Queues

2. To display a list of the queues, enter a queue name (for example *).

3. Choose Execute.

4. To delete an inbound queue, select the queue and choose Delete selected objects.

3.6 Checking Delta Replication Events


Use

For all master data objects an automatic delta replication will be activated during the initial download, i.e. each modification of a master data object is automatically transferred from the ECC into the CRM system. Customizing data is not automatically replicated. You have to run the delta replication manually or run a background job periodically.

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, for example for sales documents. If all relevant objects that will be used in the scenarios have been downloaded successfully, you can skip this activity.

Procedure



SAP ECC menu Basis Tools � ABAP Workbench � Overview � Data Browser

2. In the table name field enter TBE31.

3. Choose Table Contents (Enter).


5. Check the column FUNCT for the relevant entries. For sales documents the relevant entry is:

APPLK FUNCT

BC-MID CRS_SALES_COLLECT_DATA

If this entry is in the table, the delta replication for sales documents is switched on.

In case you need to activate the delta events manually, run the following activity in the CRM system:


SAP CRM menu Middleware � Data Exchange � Delta Load from R/3 Back-End � Set Up Delta Load

1. Choose Display � Change in order to switch to change mode.


3. Enter the relevant object class in field Object Class and the RFC destination to the ECC system in the field Destination.


This transaction also maintains database table TBE31 in the ECC system!

4 crm customizing replicationapi.ning.com/.../crmcustomizingreplication.pdfcrm customizing...

Documents