Important Steps to perform CRM-ECC integration – Middleware steps

Amit Aggarwal

Contents

Purpose...................................................................................................................3

1 Business Requirement.................................................................................3

2 Detailed Design...............................................................................................3

PurposeThis document describes

1) What are the different steps which needs to be performed to integrate CRM with ECC using CRM Middleware

2) The replication of the different objects from CRM to the ERP

1 Business Requirement

This main purpose of this document is to showcase the replication of data of ERP to CRM and Vice Versa through CRM middleware.

2 Detailed Design For CRM – ECC integration the following activities need to be performed:

1. Basic Connectivity between CRM and ECC a. Both in CRM and ECC –

i. Maintain Client specific parameters

ii. create logical destination for the system and client and assign it to client

iii. Create RFC users – ‘communication type’ which will communicate between CRM and ECC

b. Cross – connectivity:

i. In CRM,

1. Create valid RFC destination for ECC.

2. Create logical destination for ECC

3. maintain CRMCONSUM table entries

4. Create R/3 site in admin console and assign the RFC destination in the site attributes.

5. Create subscriptions in admin console and assign to the R/3 site (the assignment needs to be decided with business based on the data which needs to be uploaded to ECC)

ii. In ECC,

1. Create valid RFC destination for CRM.

2. Create logical destination for CRM

3. maintain CRMCONSUM table entries for CRM consumer

4. maintain CRMPAROLTP entry for CRM release

5. maintain CRMRFCPAR entry for the type of loads allowed and objects to be downloaded for R/3 (the table entry needs to be decided with business based on the data which needs to be uploaded to ECC)

c. In CRM, Register the inbound queues and outbound destinations

In inbound scheduler, register CSA*, R3A* queues

In outbound scheduler register the ECC destination

d. In ECC, in outbound scheduler - register the outbound destination for CRM.

With the above steps CRM-ECC will have basic integration working.

2. Generate runtime objects such as function module definitions for interfaces and services. Choose industry and specify applications and generate.

CRM CRM Middleware and Related Components Generating Industry-Specific Objects and Services Select Your Industry

3. Specify CRM applications which needs to be implemented

CRM -> CRM Middleware and Related Components -> Generating Industry-Specific Objects and Services -> Select Applications

4. Check if SMOGLASTLOG shows the initial generation has already happened for

a. BDoc types

b. Replication objects

c. Publication objects

Generally for a fresh implementation these objects will be generation during installation itself. If SMOGLASTLOG does not show any initial generation entry, then run the generate using trx SMOGTOTAL.

Check if generation is complete and green using trx GENSTATUS. choose Show Generation Jobs and check if MW_GENERATE job is successfully completed.

5. If the industry has been changed then industry specific replication objects and publications needs to be generated. Use trx. SMOGIND for this. It may take upto 1 hr. Check the generation status using trx GENSTATUS.

6. All filter modules have to be regenerated, if the CRM server is used in a client copy (i.e. not with client 000). This can be done using trx GNRWB.

1. Select the generator group R3ADP R/3 Adapter.

2. In the left-hand frame select all the adapter objects and in the right-hand frame select R3ADP_FILTER.

3. Choose Generate.

After the basic integration is set up, following customizing/master and business data needs to be transferred from ECC -> CRM (in sequence):

( Refer the best practices guides for the download). For downloading the master/customizing/business data always consult functional cons and first seek their advice. They will know which customizing is done in ERP and needs to replicate in CRM. They will also know what customizing needs to be maintained in CRM to

support the business scenario. They will also know what data they need in CRM which is available in ECC.

As a MW cons never change the customizing as we would never know why the current customizing is done and what needs to be change.

a. Customizing data (*refer to SAP best practice guide CRM Customizing Replication (B09))

a. Configuration replication ERP  ->  CRM:These are activities that are necessary to replicate the customizing data from the ERP to the CRM system in order to ensure the synchronization of customizing settings (for example, pricing) and to reduce the effort for parallel maintenance.

The following are the main customizing objects which are relevant to the initial download (trx R3AS) from ERP OLTP to the CRM system:

Object Name Description

DNL_CUST_ACGRPB Accounting Group Business Partner

DNL_CUST_ACGRPP Account Group Product

DNL_CUST_ADDR Regional structure

DNL_CUST_BASIS Basis CRM online

DNL_CUST_BASIS2 Basis CRM online

DNL_CUST_BASIS3 Basis CRM online

DNL_CUST_BASIS5 Basis CRM online

DNL_CUST_BASIS6 Basis CRM online

DNL_CUST_BNKA Banking Master

DNL_CUST_KTOKD Business Partner: Acc. Group

DNL_CUST_PAYPL Payplan

DNL_CUST_PRICE Sales pricing and pricing item

DNL_CUST_PROD0 Material number conversions

DNL_CUST_PROD1 Product: categories

DNL_CUST_PROD3 Material: ERP sales status

DNL_CUST_SALES Sales

DNL_CUST_SCE SCE varcond

DNL_CUST_SHIP Sales shipping

DNL_CUST_SPROD Sales product item

DNL_CUST_T502T Business Partner: T502T

DNL_CUST_TBRC Business Partner: Industries

DNL_CUST_TKUKL Business Partner: TKUKL, TKUKT

DNL_CUST_TNLS Business Partner: TNLS, TNLST

DNL_CUST_TPFK Business Partner: TPFK, TPFKT

DNL_CUST_TSAB Business Partner: TSAB, TSABT

DNL_CUST_TVAST Sales Document Blocking Reason

DNL_CUST_TVFS Sales Document Billing: Block

DNL_CUST_TVGF Business Partner: TVGF, TVGFT

DNL_CUST_TVIP Business Partner: TVIP, TVIPT

DNL_CUST_TVKN Business Partner: Attributes

DNL_CUST_TVLS Deliveries: Blocking Reasons/C

Object Name Description

DNL_CUST_TVPV Business Partner: TVPV, TVPVT

DNL_PLANT Plant

b. Tax replication ERP  ->  CRM:For tax replication please refer to section ‘SETTING UP TAXES’ of the best practice guide B09 mentioned above.

b. Organization Model –a. SD (* refer to best practice guide CRM Organizational Model (C01))

b. HR (* refer to best practice guide CRM Organizational Model with ERP HR Integration (C05))

c. CRM master data and Transactional data (*refer to best practice guide CRM Master and Transaction Data Replication (C03))-

a. Business partner replication:  ERP  -> CRM , customizing the number ranges/groupings in CRM and PIDE settings in ECC for account group and classification mapping.

Adapter object to download is CUSTOMER_MAIN

b. Contact person replication  ERP  ->  CRM , object CUSTOMER_RELc. Customer hierarchy ERP -> CRM,

i. Download of customer hierarchy in the ERP back end to the business partner group in CRM using adapter Object DNL_CUST_THIT

ii. Mapping of ERP customer hierarchy categories with CRM account hierarchies.

iii. Download customer hierarchy KNVH table to CRM using object DNL_BUPA_KNVH

iv. The SAP CRM account hierarchy has to be created based on the downloaded SAP ERP customer hierarchy. Use trx BPH_DNL

d. Product replication  ERP  ->  CRM, configuring Item groups in CRM as defined in ECC. Download object Material

e. Condition replication  ERP  ->  CRM. To download all the customizing data i.e. pricing procedures use adapter object DNL_CUST_CNDALL else download individual condition objects. (** make sure we refer to SAP best practices guide to download the conditions)

d. CRM Service data ( if CRM service is implemented ) – a. Installed Base Management b. Service and Response Profiles c. Service Products d. Warranties

e. Qualifications f. Problems and Solutions (Solution Database)