B09 Customizeing Replication

CRM Replication

CRM 5.0

March 2001July 2006

English

REF DokSprache \* MERGEFORMAT English

CRM Customizing Replication (B09)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyBuilding Block Configuration Guide

Copyright

Copyright 2006 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP 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, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

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

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

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

Icons

IconMeaning

Caution

Example

Note

Recommendation

Syntax

Typographic Conventions

Type StyleDescription

Example textWords or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation.

Example textEmphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXTNames of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example textScreen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.

EXAMPLE TEXTKeys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Example textExact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

Contents6Configuration Guide

61Purpose

62Preparation

62.1Prerequisites

62.2SAP Notes

83Configuration

83.1Preliminary Activities for Replication

83.1.1Registering Queues

93.1.2Starting Queue Demon and Queues

93.1.3Setting Up Error Handler (SAP CRM)

103.2Configuration Replication ECC -> CRM

103.2.1Checking ISO Codes (SAP ECC)

103.2.2Defining Product Hierarchy Structure

103.2.2.1Checking Product Hierarchy Structure in OLTP (SAP ECC)

113.2.2.2Defining Product Hierarchy Structure (SAP CRM)

113.2.3Defining Product ID Settings (SAP CRM)

123.2.4Replicating Customizing Objects (SAP CRM)

123.2.4.1Replicating Customizing Objects from ECC OLTP to CRM System

143.2.4.2Monitoring Replication Status (SAP CRM)

143.2.5Replicating Condition Customizing

143.2.5.1Selecting Condition Customizing for Replication (SAP CRM)

163.2.5.2Replicating Condition Customizing (SAP CRM)

173.2.5.3Monitoring Replication Status

173.2.5.4Correcting Condition Customizing

173.2.5.4.1Checking the Condition Customizing Download

193.2.5.4.2Mapping Customer-Specific Condition Tables

193.2.5.4.3Creating ECC Adapter Objects (SAP CRM)

203.2.5.4.4Replicating Single Condition Tables (SAP CRM)

213.2.6Setting Up Taxes

223.2.6.1Defining Tax Types

223.2.6.2Defining Business Partner Tax Groups

253.2.6.3Defining BP Tax Classification Assignment Settings

273.2.6.4Replicating Tax Customizing (SAP CRM)

273.2.6.5Monitoring Replication Status (SAP CRM)

273.2.6.6Defining Tax Type and Group

283.2.6.7Defining Assignment of Product Tax Data from ECC to CRM

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

313.3Setting Up the Organization Model

313.4Replicating Master Data and Transaction Data

323.5Tips and Tricks for the Replication Process

323.5.1Object Management

323.5.1.1Changing Block Size

323.5.1.2Defining Filters for Objects

343.5.2Improving Performance During Replication

343.5.3Monitoring and Error Analysis for Replication

343.5.3.1Monitoring Download Status

353.5.3.2General Analysis Steps

353.5.3.3Monitoring Outbound Queue

363.5.3.4Monitoring Inbound Queue

363.5.3.5Analyzing BDOC Messages

373.5.3.6Checking Transactional RFC Requests

373.5.3.7Analyzing ABAP Dumps

373.5.4Restart Replication

383.5.4.1Canceling Download of Objects

393.5.4.2Deleting Outbound Queue

393.5.4.3Deleting Inbound Queue

393.6Checking Delta Replication Events

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 NoteAreaTitle

ECC System

CRM System

432339CRM-MD-PRO-IF-CATErrors during Customizing download DNL_CUST_PROD1

435598CRM-BF-TAXInitial download of object DNL_CUST_TAX

490932CRM-BTX-BF-IFData exchange of sales transactions CRM R/3(see chapter Queue processing during the upload/delta download)

729669CRM-MW-ADPFilters are not used

756567CRM-BFDownload 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 codeSMQR

SAP CRM IMG menuCRM CRM Middleware and Related Components Queue Setup ( Register CSA Queues

2. Choose Registration.

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

Field nameUser action and values

Queue nameCSA*

EXEMODED

MAXTIME60

USERDEST

NRETRY30

TDELAY300

4. Register an additional queue:

Field nameUser action and values

Queue nameR3A*

EXEMODED

MAXTIME60

USERDEST

NRETRY30

TDELAY300

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 codeSMOHQUEUE

SAP CRM IMG menuArchitecture 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 codeSPRO

SAP CRM IMG menuCustomer 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 nameValue

E-Mail Address of Receivers of the user that is logged on

E-Mail TypeB

7. Choose Save.

8. Choose Execute (F8).

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

ResultAn 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 codeSE16

SAP ECC menuTools ( ABAP Workbench ( Overview ( Data Browser

2. In the table name field enter T002.

3. Choose Table Contents (Enter).4. Choose Execute (F8).

5. Check the column LAISO for duplicate entries.

6. Repeat these steps for the other tables.

If duplicate ISO codes are detected, they have to be replaced by new ISO codes. The final result has to be that all tables mentioned hold unique ISO code entries. Multiple entries with empty ISO codes are possible.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 menuTools ( 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 menuCross Application Components ( SAP Product ( Product Category ( Define Category Numbering Schemes

2. Choose New entries.

3. Make the following entries:

Field name Entry

Number SchemeR3PRODHIER

Scheme Description (EN)Numbering Scheme R/3

Scheme Description (DE)R/3 Numbering schema

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):LevelNumber of Digits

15

25

38

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 codeCOMCPRFORMAT

SAP CRM IMG menuCross-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.

FieldValue

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

Template for IDValue of field Material Number Template in the ECC system

Display Leading ZerosValue of field Leading Zeros in the ECC system

Save LexicographicallyValue 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 NameDescription

DNL_CUST_ACGRPBAccounting Group Business Partner

DNL_CUST_ACGRPPAccount Group Product

DNL_CUST_ADDRRegional structure

DNL_CUST_BASISBasis CRM online

DNL_CUST_BASIS2Basis CRM online




DNL_CUST_BNKABanking Master

DNL_CUST_KTOKDBusiness Partner: Acc. Group

DNL_CUST_PAYPLPayplan

DNL_CUST_PRICESales pricing and pricing item

DNL_CUST_PROD0Material number conversions

DNL_CUST_PROD1Product: categories

DNL_CUST_PROD3Material: R/3 sales status

DNL_CUST_S_AREAOrganizational Unit: Divisions

DNL_CUST_SALESSales

DNL_CUST_SCESCE varcond

DNL_CUST_SHIPSales shipping

DNL_CUST_SPRODSales product item

DNL_CUST_T502TBusiness Partner: T502T

DNL_CUST_TBRCBusiness Partner: Industries

DNL_CUST_TKUKLBusiness Partner: TKUKL, TKUKT

DNL_CUST_TNLSBusiness Partner: TNLS, TNLST

DNL_CUST_TPFKBusiness Partner: TPFK, TPFKT

DNL_CUST_TSABBusiness Partner: TSAB, TSABT

DNL_CUST_TVASTSales Document Blocking Reason

DNL_CUST_TVFSSales Document Billing: Block

DNL_CUST_TVGFBusiness Partner: TVGF, TVGFT

DNL_CUST_TVIPBusiness Partner: TVIP, TVIPT

DNL_CUST_TVKNBusiness Partner: Attributes

DNL_CUST_TVLSDeliveries: Blocking Reasons/C

DNL_CUST_TVPVBusiness Partner: TVPV, TVPVT

DNL_PLANTPlant

Procedure


Transaction codeR3AS

SAP CRM menuArchitecture 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 codeR3AM1

SAP CRM menuArchitecture 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.

ResultThe 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 codeR3AC5

SAP CRM menuArchitecture 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.

TableFilter settings

MNTCNTNot needed.

T681Using 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.

T681TUsing 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.

T681EUsing 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, T682ZUsing 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.

T682VIt 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, T683TSet 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, T684SSpecify 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, T685ZUsing 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, T686FYou can leave these tables without filter settings.

TMC1Using 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.

TMC1DYou can leave these tables without filter settings.

3.2.5.2 Replicating Condition Customizing (SAP CRM)

PrerequisitesCheck 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.

UseThere 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



SAP CRM menuArchitecture and Technology Middleware Data Exchange Initial Load ( Start

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



SAP CRM menuArchitecture 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.

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.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 codeSLG1

2. Enter the following data:

Field nameValue

ObjectCOND_EXCHANGE

SubobjectCUSTOMIZING

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 nameR3TABNAMEInactive

DNL_COND_A002A002

DNL_COND_A005A005

3.2.5.4.2 Mapping Customer-Specific Condition TablesUse

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 menuArchitecture and Technology ( Middleware ( Data Exchange ( Object Management ( Condition Objects

2. Choose Display ( Change.3. Choose Create Object (F6).

4. Enter the following data:

FieldEntry

Object nameID of the adapter object, e.g. ZDNL_COND_A999

5. Choose Enter.

FieldEntry

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

Linked BDocCND_MAST_DEEP_SUP

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

Block Size1000

Inactive Objectnot selected

FunctionNo entry

Initial Flow Contexts

Source Site TypeR/3

Tables and Structures

Table (Source Site), for ex. A999KONHKONMKONPKONWTMC1K

Mapping Modules

Module nameCND_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 menuMiddleware 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 SystemCRM System

Tax TypesTSTLTB070

BP Tax GroupsTB071_CMTB071

Mapping of business partner relevant information of Condition recordsTB072_CMCRMC_TAX_MAP_BP

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 codePITC

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 codePITC

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:7. Choose New Entries.8. Enter the Country.

Enter the Region, if required.

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

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 codePITM

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

3. Enter the Country.

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

6. Enter the CRM Tax Type.

7. Enter the CRM Tax Group.

8. Enter the 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



SAP CRM menuArchitecture and Technology Middleware Data Exchange Initial Load Start

2. In the Load Object field, enter DNL_CUST_TAX.

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

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

3.2.6.5 Monitoring Replication Status (SAP CRM)

Procedure



SAP CRM menuArchitecture and Technology Middleware ( Data Exchange ( Initial Load ( Monitor Objects

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

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

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

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 menuCustomer 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 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 menuCustomer 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).

5. Choose New Entries.

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

Example:

ECC Table TSKM

TATYPTAXKM

CTX10

CTX11

CTX20

CTX21

CTX30

CTX31

Table TSTL

CountryLFDNRTATYP

CA1CTX1

CA2CTX2

CA3CTX3

CRM

Table CRMC_TAX_MAP (assignment)CountryRegionTax TypeTax GroupTax Seq.Tax Class.

CACTX1NON10

CACTX1FULL11

CACTX2NON20

CACTX2FULL21

CACTX3NON30

CACTX3FULL31

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 codeCRM_TAXCUST_VALIDATE

SAP CRM IMG menuCustomer 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

Please check the Delta Guide.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 menuMiddleware 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


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 menuMiddleware 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:

FieldProcedure

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).

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

FieldUse the input help to select a field.

OP (Operator)Select an operator.

LOWSpecify 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.

HIGHSpecify 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.

InactiveSet 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


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

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

3.5.3.1 Monitoring Download Status


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

Procedure



SAP CRM menuMiddleware 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.

FieldValue

CheckboxSet the indicator to select a transfer object for further processing.

StatusThe 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.

DateDate 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.

AttemptThis field shows the number of attempted transfers.

Source SiteSpecification of the RFC OLTP destination.

DestinationSpecification 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

Please check the Delta Guide.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

Please check the Delta Guide.Procedure


Transaction codeSMQ1

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


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


SAP CRM menuMiddleware 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


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

Procedure


Transaction codeSMW01

SAP CRM menuMiddleware 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



Transaction codeSM58

SAP CRM menuMiddleware 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



Transaction codeST22

SAP CRM menuMiddleware 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


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




SAP CRM menuMiddleware 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




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




SAP CRM menuMiddleware 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


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 menuBasis Tools ( ABAP Workbench ( Overview ( Data Browser

2. In the table name field enter TBE31.

3. Choose Table Contents (Enter).4. Choose Execute (F8).5. Check the column FUNCT for the relevant entries. For sales documents the relevant entry is:

APPLKFUNCT

BC-MIDCRS_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 menuMiddleware ( Data Exchange ( Delta Load from R/3 Back-End ( Set Up Delta Load

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

2. Choose New Entries.

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!

EMBED Excel.Sheet.8

EMBED Excel.Sheet.8

EMBED Excel.Sheet.8

EMBED Excel.Sheet.8

_1131966536.xlsMapping Condition R3->CRM

R/3 ConditionMappingCRM Condition

CntryTaxCategoryTAXM1CntryTaxCategoryProduct Tax GroupR/3 ContentCntryTax CategoryProduct Tax Group...Rate

DEMWST1DEMWSTFULL1DEMWSTFULL7%

GBMWST0GBMWSTNON0GBMWSTNON0%

ESMWST1ESMWSTFULL1ESMWSTFULL16%

ESMWES1ESMWESFULL1ESMWESFULL4%

ESMWST2ESMWSTHALF2ESMWSTHALF7%

ESMWES2ESMWESHALF2ESMWESHALF1%

R/3 ConditionMappingMappingCRM Conditions

CntryTaxCategoryTAXM1TAXK1RateCntryTaxCategoryProduct Tax GroupR/3 ContentCntryTax CategoryBP Tax GroupR/3 ContentCntryTax CategoryProduct Tax GroupBP Tax Group...Rate

DEMWST217%DEMWSTHALF2DEMWSTFULL1DEMWSTHALFFULL7%

GBMWST010%GBMWSTNON0GBMWSTFULL1GBMWSTNONFULL0%

ESMWST1116%ESMWSTFULL1ESMWSTFULL1ESMWSTFULLFULL16%

ESMWES114%ESMWESFULL1ESMWESFULL1ESMWESFULLFULL4%

ESMWST217%ESMWSTHALF2ESMWSTFULL1ESMWSTHALFHALF7%

ESMWES211%ESMWESHALF2ESMWESFULL1ESMWESHALFHALF1%

R/3 ConditionMapping ProductMapping BPCRM Conditions

CntryRegionTaxCategoryTAXM1TAXK1RateCntryTaxCategoryProduct Tax GroupR/3 ContentCntryTax CategoryBP Tax GroupR/3 ContentCntryRegionTax CategoryProduct Tax GroupBP Tax Group...Rate

CABCCTX1000%CACTX1NON0CACTX1EXEMPT0CABCCTX1NONEXEMPT0%

BCCTX1100%FULL1FULL1BCCTX1FULLEXEMPT0%

BCCTX1010%GST&PST(Ont & West2BCCTX1NONFULL0%

BCCTX1117%GST&PST (Que &Mar)3BCCTX1FULLFULL7%

BCCTX1020%BCCTX1NONGST&PST(Ont & West0%

BCCTX1127%BCCTX1FULLGST&PST(Ont & West7%

MBCTX2000%CTX2NON0CTX2EXEMPT0MBCTX2NONEXEMPT0%

MBCTX2100%FULL1FULL1MBCTX2FULLEXEMPT0%

MBCTX2020%GST&PST(Ont & West2MBCTX2NONGST&PST(Ont & West0%

MBCTX2127%GST&PST (Que &Mar)3MBCTX2FULLGST&PST(Ont & West7%

PICTX3000%CTX3NON0CTX3EXEMPT0PICTX3NONEXEMPT0%

PICTX3100%FULL1FULL1PICTX3FULLEXEMPT0%

PICTX3030%GST&PST(Ont & West2PICTX3NONGST&PST (Que &Mar)0%

PICTX31310%GST&PST (Que &Mar)3PICTX3FULLGST&PST (Que &Mar)10%

&A

Seite &P von &N

Mapping DE CRM->R3

CRM Tax CategoriesR/3 Table TSTL

CntryTax CategoryCntrySequenceTax Type

DEDE1MWST

CA1CTX1

CA2CTX2

CA3CTX3

CRM Product Tax GroupsR/3 Table TSKM

CntryTax GroupTax CategoryTax ClassificationText

DEBOOKSMWST0No tax

GOODSMWST1Full tax

SERVICEMWST2Half tax

MWST3Low tax rate

CRM BP Tax GroupsR/3 Table TSKD


DECOMPANYMWST0Tax Exempt

HOSPITALMWST1Liable for Taxes

PRIVAT PERSON

MILITARY

Mapping

CntryTax CategoryProduct Tax GroupR/3 ContentSequence

DEBOOKS21

SERVICE11

GOODS11

CEROSINE01

HELTH SERVICE01

Mapping

CntryTax CategoryBP Tax GroupR/3 ContentSequence

DECOMPANY11

HOSPITAL01

PRIVAT PERSON11

MILITARY01

CRM ProductR/3 Product

ProductCntryRegionTax CategoryProduct Tax GroupProductCntryTax CategoryTAXM1

P1DEGOODSP1DEMWST1

P2DEBOOKSP2DEMWST1

CRM CustomerR/3 Customer

CustomerCntryRegionTax CategoryProduct Tax GroupCustomerCntryTax CategoryTAXK1

C1DECOMPANYC1DEMWST1

C2DEHOSPITALC2DEMWST0

CRM ConditionsR/3 Condition

CntryTax CategoryProduct Tax GroupBP Tax Group...RateCntryTax CategoryTAXM1TAXK1Rate

DEBOOKSPRIVAT PERSON7%DEMWST217%

BOOKSCOMPANY7%

GOODSCOMPANY16%MWST1116%

HELTH SERVICEPRIVAT PERSON0%MWST010%

CEROSINECOMPANY16%MWST010%

N : 1 Possible -> Only for TTE Scenarios. Not in Combination with R/3

&CMapping Example Germany

&A&RSeite &P

Customizing

R/3 Table TSTLCRM Tax Categories

CntrySequenceTaxCategoryCntryTax Category

CA1CTX1CACTX1

CA2CTX2CACTX2

CA3CTX3CACTX3

DE1MWSTDEMWST

ES1MWSTESMWST

ES2MWESESMWES

FR1MWSTFRMWST

FR2LCFRFRLCFR

GB1MWSTGBMWST

IT1MWSTITMWST

IT2LCITITLCIT

R/3 Table TSKMCRM Product Tax Groups

Tax CategoryTax ClassificationTextCntryTax Group

CTX10No taxCANON

CTX11Full taxFULL

CTX20No taxDENON

CTX21Full taxFULL

CTX30No taxHALF

CTX31Full taxLOW

MWST0No taxESNON

MWST1Full taxFULL

MWST2Half taxHALF

MWST3Low tax rateLOW

MWES0No taxFRNON

MWES1Full taxFULL

MWES2Half taxHALF

MWES3Low tax rateLOW

LCFRALicense group AGBNON

LCFRBLicense group BFULL

LCIT0DummyHALF

LOW

R/3 Table TSKDCRM BP Tax Groups


CTX10Tax ExemptCAEXEMPT

CTX11GSTFULL

CTX12GST & PST(Ont & WestGST & PST(Ont & West

CTX13GST & PST (Que &Mar)GST & PST (Que &Mar)

CTX20Tax ExemptDEEXEMPT

CTX22GST & PST(Ont & WestFULL

CTX30Tax ExemptESEXEMPT

CTX33GST & PST(Que & Mar)FULL

MWST0Tax ExemptFREXEMPT

MWST1Liable for TaxesFULL

MWES0Tax ExemptGBEXEMPT

MWES1Liable for TaxesFULL

LCFR0Do not check license

LCFR1Check license

LCIT0Do not check license

LCIT1Check license

TTE Exemption Handlingno Product Tax Group




Mapping ES R3-CRM



ES1MWSTESMWST

ES2MWESESMWES



MWST0No taxESNON

MWST1Full taxFULL

MWST2Half taxHALF


MWES0No tax

MWES1Full tax

MWES2Half tax

MWES3Low tax rate



MWST0Tax ExemptESEXEMPT


MWES0Tax Exempt

MWES1Liable for Taxes

MappingMapping

CntryTaxCategoryProduct Tax GroupR/3 ContentCntryTax CategoryBP Tax GroupR/3 Content

ESMWSTNON0ESMWSTEXEMPT0

ESMWESNON0ESMWESFULL1

ESMWSTFULL1ESMWSTEXEMPT0

ESMWESFULL1ESMWESFULL1

ESMWSTHALF2ESMWSTEXEMPT0

ESMWESHALF2ESMWESFULL1

R/3 ProductCRM Product

ProductCntryTax CategoryTAXM1ProductCntryRegionTax CategoryProduct Tax Group

P1ESMWST1P1DEGOODS

MWES1P2DEBOOKS

P2ESMWST0

MWES0

R/3 CustomerCRM Customer

CustomerCntryTax CategoryTAXK1CustomerCntryRegionTax CategoryProduct Tax Group

C1DEMWST1C1DECOMPANY

C2DEMWST0C2DEHOSPITAL

Mapping CRM -> R3

CRM Product

CntryRegionTax CategoryProduct Tax GroupTax Tarif Code

CACTX1FULL

CTX2FULL

CTX3FULL

CABCCTX1FULL

BCCTX2FULL

BCCTX3FULL

MBCTX1FULL

MBCTX2FULL

MBCTX3FULL

CRM BP

CntryRegionTax CategoryBP Tax Group

CACTX1FULL

CTX2FULL

CTX3FULL

CABCCTX1FULL

BCCTX2FULL

BCCTX3FULL

MBCTX1FULL

MBCTX2FULL

MBCTX3FULL

CRM Conditions

CntryRegionTax CategoryProduct Tax GroupBP Tax Group...Rate

CABCCTX1NONEXEMPT0%

BCCTX1FULLEXEMPT0%

BCCTX1NONFULL0%

BCCTX1FULLFULL7%

BCCTX1NONGST&PST(Ont & West0%

BCCTX1FULLGST&PST(Ont & West7%

MBCTX2NONEXEMPT0%

MBCTX2FULLEXEMPT0%

MBCTX2NONGST&PST(Ont & West0%

MBCTX2FULLGST&PST(Ont & West7%

PICTX3NONEXEMPT0%

PICTX3FULLEXEMPT0%

PICTX3NONGST&PST (Que &Mar)0%

PICTX3FULLGST&PST (Que &Mar)10%


































&A

Seite &P von &N

Mapping DE CRM->R3

CRM Tax TypesR/3 Table TSTL

CntryTax TypeTax SeqCntrySequenceTaxCategory

DEMWST1DE1MWST

CACTX11

CACTX22

CACTX33



DEBOOKSMWST0No tax

GOODSMWST1Full tax


MWST3Low tax rate





PRIVAT PERSON

MILITARY

Mapping


DEBOOKS21

SERVICE11

GOODS11

CEROSINE01

HELTH SERVICE01

Mapping


DECOMPANY11

HOSPITAL01

PRIVAT PERSON11

MILITARY01



P1DEGOODSP1DEMWST1

P2DEBOOKSP2DEMWST1








BOOKSCOMPANY7%






&A&RSeite &P

Customizing



CA1CTX1CACTX1

CA2CTX2CACTX2

CA3CTX3CACTX3

DE1MWSTDEMWST

ES1MWSTESMWST

ES2MWESESMWES

FR1MWSTFRMWST

FR2LCFRFRLCFR

GB1MWSTGBMWST

IT1MWSTITMWST

IT2LCITITLCIT



CTX10No taxCANON

CTX11Full taxFULL

CTX20No taxDENON

CTX21Full taxFULL

CTX30No taxHALF

CTX31Full taxLOW

MWST0No taxESNON

MWST1Full taxFULL

MWST2Half taxHALF


MWES0No taxFRNON

MWES1Full taxFULL

MWES2Half taxHALF




LCIT0DummyHALF

LOW




CTX11GSTFULL












LCFR1Check license


LCIT1Check license





Mapping ES R3-CRM



ES1MWSTESMWST

ES2MWESESMWES



MWST0No taxESNON

MWST1Full taxFULL

MWST2Half taxHALF


MWES0No tax

MWES1Full tax

MWES2Half tax

MWES3Low tax rate





MWES0Tax Exempt


MappingMapping










P1ESMWST1P1DEGOODS

MWES1P2DEBOOKS

P2ESMWST0

MWES0





Mapping CRM -> R3

CRM Product


CACTX1FULL

CTX2FULL

CTX3FULL

CABCCTX1FULL

BCCTX2FULL

BCCTX3FULL

MBCTX1FULL

MBCTX2FULL

MBCTX3FULL

CRM BP


CACTX1FULL

CTX2FULL

CTX3FULL

CABCCTX1FULL

BCCTX2FULL

BCCTX3FULL

MBCTX1FULL

MBCTX2FULL

MBCTX3FULL

CRM Conditions


CABCCTX1NONEXEMPT0%

BCCTX1FULLEXEMPT0%

BCCTX1NONFULL0%

BCCTX1FULLFULL7%



MBCTX2NONEXEMPT0%

MBCTX2FULLEXEMPT0%



PICTX3NONEXEMPT0%

PICTX3FULLEXEMPT0%




































&A

Seite &P von &N

Mapping DE CRM->R3


CntryTax TypeCntrySequenceTaxType

DEDE1MWST


CntryTax GroupTax TypeTax ClassificationText

DEBOOKSMWST0No tax

GOODSMWST1Full tax


MWST3Low tax rate


CntryTax GroupTax TypeTax ClassificationText



PRIVAT PERSON

MILITARY

Product Tax Group

CntryRegTax TypeProduct Tax GroupR/3 ContentSequence

DEMWSTFULL21

DEMWSTHALF11

DEMWSTNONE11

CACTX1FULL

CACTX1NONE

CACTX2FULL

CACTX2NONE

CACTX3FULL01

CACTX3NONE01

Mapping

CntryTax TypeBP Tax GroupR/3 ContentSequence

DECOMPANY11

HOSPITAL01

PRIVAT PERSON11

MILITARY01


ProductCntryRegionTax TypeProduct Tax GroupProductCntryTax TypeTAXM1

P1DEGOODSP1DEMWST1

P2DEBOOKSP2DEMWST1


CustomerCntryRegionTax TypeProduct Tax GroupCustomerCntryTax TypeTAXK1




CntryTax TypeProduct Tax GroupBP Tax Group...RateCntryTax TypeTAXM1TAXK1Rate


BOOKSCOMPANY7%






&A&RSeite &P

Customizing



CA1CTX1CACTX1

CA2CTX2CACTX2

CA3CTX3CACTX3

DE1MWSTDEMWST

ES1MWSTESMWST

ES2MWESESMWES

FR1MWSTFRMWST

FR2LCFRFRLCFR

GB1MWSTGBMWST

IT1MWSTITMWST

IT2LCITITLCIT



CTX10No taxCANON

CTX11Full taxFULL

CTX20No taxDENON

CTX21Full taxFULL

CTX30No taxHALF

CTX31Full taxLOW

MWST0No taxESNON

MWST1Full taxFULL

MWST2Half taxHALF


MWES0No taxFRNON

MWES1Full taxFULL

MWES2Half taxHALF




LCIT0DummyHALF

LOW




CTX11GSTFULL












LCFR1Check license


LCIT1Check license





Mapping ES R3-CRM



ES1MWSTESMWST

ES2MWESESMWES



MWST0No taxESNON

MWST1Full taxFULL

MWST2Half taxHALF


MWES0No tax

MWES1Full tax

MWES2Half tax

MWES3Low tax rate





MWES0Tax Exempt


MappingMapping










P1ESMWST1P1DEGOODS

MWES1P2DEBOOKS

P2ESMWST0

MWES0





Mapping CRM -> R3

CRM Product


CACTX1FULL

CTX2FULL

CTX3FULL

CABCCTX1FULL

BCCTX2FULL

BCCTX3FULL

MBCTX1FULL

MBCTX2FULL

MBCTX3FULL

CRM BP


CACTX1FULL

CTX2FULL

CTX3FULL

CABCCTX1FULL

BCCTX2FULL

BCCTX3FULL

MBCTX1FULL

MBCTX2FULL

MBCTX3FULL

CRM Conditions


CABCCTX1NONEXEMPT0%

BCCTX1FULLEXEMPT0%

BCCTX1NONFULL0%

BCCTX1FULLFULL7%



MBCTX2NONEXEMPT0%

MBCTX2FULLEXEMPT0%



PICTX3NONEXEMPT0%

PICTX3FULLEXEMPT0%




































&A

Seite &P von &N

Mapping DE CRM->R3


CntryTax CategoryCntrySequenceTaxCategory

DEDE1MWST



DEBOOKSMWST0No tax

GOODSMWST1Full tax


CTX10No tax

CTX11Full tax

CTX20No tax

CTX21Full tax

CTX30No tax

CTX31Full tax





PRIVAT PERSON

MILITARY

Mapping


DEBOOKS21

SERVICE11

GOODS11

CEROSINE01

HELTH SERVICE01

Mapping


DECOMPANY11

HOSPITAL01

PRIVAT PERSON11

MILITARY01



P1DEGOODSP1DEMWST1

P2DEBOOKSP2DEMWST1








BOOKSCOMPANY7%






&A&RSeite &P

Customizing



CA1CTX1CACTX1

CA2CTX2CACTX2

CA3CTX3CACTX3

DE1MWSTDEMWST

ES1MWSTESMWST

ES2MWESESMWES

FR1MWSTFRMWST

FR2LCFRFRLCFR

GB1MWSTGBMWST

IT1MWSTITMWST

IT2LCITITLCIT



CTX10No taxCANON

CTX11Full taxFULL

CTX20No taxDENON

CTX21Full taxFULL

CTX30No taxHALF

CTX31Full taxLOW

MWST0No taxESNON

MWST1Full taxFULL

MWST2Half taxHALF


MWES0No taxFRNON

MWES1Full taxFULL

MWES2Half taxHALF




LCIT0DummyHALF

LOW




CTX11GSTFULL












LCFR1Check license


LCIT1Check license





Mapping ES R3-CRM



ES1MWSTESMWST

ES2MWESESMWES



MWST0No taxESNON

MWST1Full taxFULL

MWST2Half taxHALF


MWES0No tax

MWES1Full tax

MWES2Half tax

MWES3Low tax rate





MWES0Tax Exempt


MappingMapping










P1ESMWST1P1DEGOODS

MWES1P2DEBOOKS

P2ESMWST0

MWES0





Mapping CRM -> R3

CRM Product


CACTX1FULL

CTX2FULL

CTX3FULL

CABCCTX1FULL

BCCTX2FULL

BCCTX3FULL

MBCTX1FULL

MBCTX2FULL

MBCTX3FULL

CRM BP


CACTX1FULL

CTX2FULL

CTX3FULL

CABCCTX1FULL

BCCTX2FULL

BCCTX3FULL

MBCTX1FULL

MBCTX2FULL

MBCTX3FULL

CRM Conditions


CABCCTX1NONEXEMPT0%

BCCTX1FULLEXEMPT0%

BCCTX1NONFULL0%

BCCTX1FULLFULL7%



MBCTX2NONEXEMPT0%

MBCTX2FULLEXEMPT0%



PICTX3NONEXEMPT0%

PICTX3FULLEXEMPT0%



_1118226115.bin

Documents

B09 Customizeing Replication