• No results found

SAP CRM Configuration Guide

N/A
N/A
Protected

Academic year: 2021

Share "SAP CRM Configuration Guide"

Copied!
66
0
0

Loading.... (view fulltext now)

Full text

(1)

[

ARYA ACHALAM

],

Version 1.0 January 9, 2012

Project Parivartan

SAP IMPLEMENTATION PROJECT

Customer Relationship

Management

Configuration Guide

Client Input – Asset

Accounting

(2)

Table of contents

1 Configuration Settings for Organization Model...4

Organizational Model Overview...4

1.1 Organizational Model Synchronization ERP <-> CRM...5

1.1.1 Checking Sales Organization (SAP ERP)...5

1.1.2 Checking Distribution Channels (SAP ERP)...5

1.1.3 Checking Divisions (SAP ERP)...6

1.1.4 Checking Sales Areas (SAP ERP)...6

1.1.5 Checking Assignment of Sales Offices to Sales Areas (SAP ERP)...7

1.1.6 Checking Assignment Company Code -> Sales Organization (SAP ERP)...7

1.1.7 Checking Assignment Distribution Channel -> Sales Org. (SAP ERP)...7

1.1.8 Checking Assignment Division → Sales Organization (SAP ERP)...8

1.1.9 Defining Divisions ... 8

1.1.10 Performing Division Settings (SAP CRM)...8

1.1.11 Defining Distribution Channels...9

1.1.12 Defining Combination of Distribution Channel and Division...9

1.1.13 Set Up Integration Business Partner – Organizational Management...10

1.1.14 Defining Number Range for Org. Business Partners (SAP CRM)...10

1.1.15 Defining Grouping for Org. Business Partners (SAP CRM)...11

1.1.16 Setting Up Integration... 12

1.1.17 Executing Report for Changeover Classification...12

1.2 Maintaining Organizational Units...13

1.2.1 Creating an Organizational Model (SAP CRM)...13

1.2.2 Creating and Assigning Organizational Units...14

1.2.3 Assigning Attributes to Organizational Unit...14

1.2.4 Matching Sales Organization...16

1.2.5 Maintain Holder for Positions...16

1.2.6 Assigning Employees to Positions...17

1.2.7 Integration of System Users and Employees ERP <-> CRM...18

1.2.8 Set Up Buffering for Sales Scenario...18

2 Configuration settings of Master Data Replication ERP -> CRM...19

2.1 Replicating Business Partners...19

2.1.1 Defining Sources for Business Partner Creation...19

2.1.2 Business Partner Concept ERP <-> CRM...20

2.1.3 Defining Number Assignment Strategy for Business Partners...21

2.1.4 Mapping Business Partner Master Data from ERP to CRM...21

2.1.5 Identifying Relevant ERP Account Groups (SAP ERP)...22

2.1.6 Defining Number Ranges for CRM Business Partners (I) (SAP CRM)...23

2.1.7 Defining CRM Business Partners Groupings (SAP CRM)...23

2.1.8 Mapping ERP Account Groups to CRM Classifications (SAP ERP)...24

2.1.9 Mapping Business Partner Master Data from CRM to ERP...24

2.1.10 Defining Number Ranges for CRM Business Partners (SAP CRM)...25

2.1.11 Defining CRM Business Partners Groupings (SAP CRM)...25

2.1.12 Mapping CRM Classifications to ERP Account Groups (SAP ERP) ...26

2.1.13 Synchronizing Field Settings for Business Partners (SAP ERP)...26

2.1.14 Selecting Customers for Replication (SAP CRM)...27

2.1.15 Replicating Customers (SAP CRM)...27

2.1.16 Monitoring Replication Status (SAP CRM)...28

2.1.17 Checking Business Partners (SAP CRM)...28

2.1.18 Monitoring Replication Status (SAP CRM)...28

2.1.19 Checking Completeness of Replication (SAP CRM)...29

2.2 Replicating Materials...29

2.2.1 Checking Material (SAP ERP)...29

2.2.2 Defining Item Category Groups...30

2.2.3 Checking Item Category Groups (SAP ERP)...30

2.2.4 Copying Item Category Groups (SAP CRM)...30

(3)

2.2.6 Replicating Materials (SAP CRM)...31

2.2.7 Monitoring Replication Status (SAP CRM)...31

2.2.8 Checking Materials (SAP CRM)...32

2.3 Replicating Conditions...32

2.3.1 Creating Pricing Procedures...32

2.3.2 Replicating Conditions (SAP CRM)...33

2.3.3 Checking Data Integrity of Replication...37

2.3.4 Object Management... 38

3 Configuration settings for Marketing master Data...45

3.1 Defining Objectives...45

3.2 Defining Tactics...45

3.3 Defining Campaign Types/Objectives/Tactics...46

3.4 Maintaining Sender Addresses for E-Mail...47

3.5 Defining Types for Marketing Plan...48

3.6 Marketing Calendar...48

3.6.1 Assigning Graphic Profile for Marketing Calendar...49

3.7 Campaign Execution...49

3.7.1 External List Management... 49

4 Configuration settings for CRM Lead Management...51

4.1 General Settings for Leads...51

4.1.1 Defining Lead Origins... 51

4.1.2 Maintaining Organizational Data Profile...51

4.1.3 Defining Transaction Type for Lead...52

4.1.4 Defining Number Range for Leads...53

4.1.5 Assigning New Number Range...54

4.1.6 Defining Item Category Determination...54

4.1.7 Defining Questionnaires... 55

4.1.8 Defining your individual questionnaire:...55

4.1.9 Assigning Qualification Levels to Questionnaires...56

4.1.10 Defining Determination for Questionnaires...56

4.1.11 Defining Copy Control from Lead to Opportunity...57

5 Configuration settings for Basic Sales...57

5.1 Maintaining Organizational Data Profile...58

6 Configuration settings for Activity Management...59

6.1 Settings for Basic Functions for Activity Management...59

6.1.1 Defining Partner Functions... 59

6.1.2 Defining Partner Determination Procedure...60

6.1.3 Defining Transaction Types... 61

6.2 Actions... 62

6.2.1 Defining Action Profiles and Actions...62

6.2.2 Defining Conditions... 62

6.2.3 Assigning Organizational Data Profile to Transaction Types...63

6.2.4 Assigning Partner Determination Procedure to Transaction Types...64

6.2.5 Assigning Action Profile to Transaction Types...64

6.2.6 Assigning Text Determination Procedure to Transaction Types...65

7 Configuration settings for CRM Opportunity Management...65

(4)

1 Configuration Settings for Organization Model

Purpose

This configuration guide provides the information you need to set up the configuration.

Organizational Model Overview

Organizational Management in CRM offers you a flexible tool for handling your company’s

task-related, functional organizational structure as a current organizational model. You can maintain the company structure including the positions and employees in an application and assign specific data (attributes) to the organizational units.

The organization model will be especially used for organizational data determination within the CRM scenarios for marketing, sales and service.

Compared to ERP the organizational model in CRM is more comprehensive, flexible and dynamic.

A synchronization of the organizational structure for sales and service in ERP and CRM is possible via mapping of organizational units. This is a prerequisite for a master data and transactional data integration between ERP and CRM.

In the following a sample organizational structure will be defined. It consists of separate

organizational units for marketing, sales and service. Positions will be assigned to the different organizational units in order to implement the functional task distribution of individual items and their reporting structure in the organizational model. Employees are assigned to these positions as holders.

These sample organizational structure is essential for all SAP Best Practices scenarios

because organizational data determination, partner determinations and evaluations are based on this structure.

If you use ERP as a back-end system in CRM, you need the sales structure from the SAP ERP system in order to transfer or create master data (for example, business partner, products, and conditions) in CRM.

The organizational model can be initially created automatically based on the sales organizational structure in ERP.

But this functionality will not be used for the following reasons:

• SAP Best Practices for CRM can also be used without an ERP system as a back end if only scenarios without ERP integration are implemented, such as Activity Management, Opportunity Management

• An automatic transfer of the ERP sales structure is only possible once. Errors may occur in organizational data determination if there are already organizational units in the system.

(5)

Further changes in the organizational model have to be maintained manually in the CRM system anyway.

1.1

Organizational Model Synchronization ERP <-> CRM

The ERP system is closely linked to the CRM system. The two systems have to be synchronized in some configuration areas, such as the organizational model.

Decide which sales areas you need to have in the CRM system, and check them in the ERP system.

A sales area consists of:

• a sales organization

• distribution channels

• divisions

The sales areas and related data are downloaded from ERP to CRM.

1.1.1

Checking Sales Organization (SAP ERP)

Procedure

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

Transaction code OVX5

SAP ERP IMG menu Enterprise Structure Definition Sales and Distribution Define, copy, delete, check sales organization Sales Organizatio n Sales Organization Description 4003 Sales Org.- PPL

1.1.2

Checking Distribution Channels (SAP ERP)

Procedure

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

Transaction code OVXI

SAP ERP IMG menu Enterprise Structure Definition Sales and Distribution Define, copy, delete, check distribution channel Disc. Chan nel Distribution Channel Description 41 Direct Sales 42 Broker Sale

(6)

43 Referral Sale

1.1.3

Checking Divisions (SAP ERP)

Procedure

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

Transaction code OVXB

SAP ERP IMG menu Enterprise Structure Definition Logistics -

General Define, copy, delete, check division

Division Division Description 11 Residential 12 Commercial 13 I.T

1.1.4

Checking Sales Areas (SAP ERP)

Procedure

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

Transaction code OVXG

SAP ERP IMG menu Enterprise Structure Assignment Sales and Distribution Set up sales area

Sales Org Dis Channel

4003 41

4003 42

4003 43

The above combination of Sales Org. and Disc Channel has been identified in combination of divisions as below

11 Residential

12 Commercial

(7)

1.1.5

Checking Assignment of Sales Offices to Sales Areas (SAP ERP)

Procedure

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

Transaction code SPRO

SAP ERP IMG menu Enterprise Structure Assignment Sales and Distribution Assign sales office to sales area

All the sales areas identified above are assigned to following sales offices:

403

1 Site Office-Est.Rng

1.1.6

Checking Assignment Company Code -> Sales Organization

(SAP ERP)

Procedure

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

Transaction code OVX3

SAP ERP IMG menu Enterprise Structure Assignment Sales and

Distribution Assign sales organization to company

code Sale s Org Description Company Code Co. Code Description

4003 Sales Org.- PPL 2003 Phadnis Properties Ltd.

1.1.7

Checking Assignment Distribution Channel -> Sales Org. (SAP

ERP)

Procedure

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

Transaction code OVXK

SAP ERP IMG menu Enterprise Structure Assignment Sales and

Distribution Assign distribution channel to sales

organization

Sale s

Org Distribution Channel Description

4003 41 Direct Sales

4003 42 Broker

(8)

1.1.8

Checking Assignment Division

Sales Organization (SAP ERP)

Procedure

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

Transaction code OVXA

SAP ERP IMG menu Enterprise Structure Assignment Sales and

Distribution Assign division to sales organization

Sales

Org. Division Description

4003 00 Common 4003 11 Residential 4003 12 Commercial 4003 13 I.T.

1.1.9

Defining Divisions

Use

In this step, you can define divisions for CRM.

Procedure

1. Access the activity using the following navigation options:

Transaction code SPRO

SAP CRM IMG menu Customer Relationship Management Master Data

Organizational Management Division Settings à

Define Divisions

2. Choose New Entries (F5).

Division Description

00 Common

11 Residential 12 Commercial

13 I.T

1.1.10

Performing Division Settings (SAP CRM)

Use

You can specify whether or not you work with divisions in the CRM system.

If you use CRM together with an ERP system, you must always maintain a dummy division in ERP, in order that you can exchange data (master data and documents) between systems, if you are not using a header division in CRM.

(9)

If you use a header division in CRM you do not need to use a dummy division for data transfer between the ERP and CRM systems.

Procedure

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

Transaction code SPRO

SAP CRM IMG menu Customer Relationship Management Master Data

Organizational Management Division Settings à

Define Use of Division and Dummy Division

2. Deselect the checkbox Division not act.

3. Select the indicator Header Div. Act. to use divisions at header level in business transactions in CRM Enterprise.

4. Enter an R/3 dummy division from the list of SAP ERP divisions identified in step Checking

Divisions (SAP ERP).

1.1.11

Defining Distribution Channels

Use

In this step, you can define distribution channels for CRM.

Procedure

1. Access the activity using the following navigation options:

Transaction code SPRO

SAP CRM IMG menu Customer Relationship Management Master Data

Organizational Management Organizational Data for

Sales Scenario à Define Distribution Channels

2. Choose New Entries (F5). 41 Direct Sales

42 Broker Sales 43 Referral Sale 3. Save your entries.

1.1.12

Defining Combination of Distribution Channel and Division

Use

In this step, you can define combinations of distribution channels and divisions that can be assigned as attributes to the sales organization to define a sales area.

Procedure

1. Access the activity using the following navigation options:

Transaction code SPRO

SAP CRM IMG menu Customer Relationship Management à Master Data à Organizational Management à Organizational Data for Sales Scenario à Define Combination of Distribution Channel and Division

(10)

2. Choose New Entries (F5).

Distribution

ChannelDescription DivisionDescription

41Direct Sales 11Residential 41Direct Sales 12Commercial 41Direct Sales 13I.T

42Broker Sales 11Residential 42Broker Sales 12Commercial 42Broker Sales 13I.T

43Referral Sale 11Residential 43Referral Sale 12Commercial 43Referral Sale 13I.T

3. Save your entries.

1.1.13

Set Up Integration Business Partner – Organizational

Management

Use

For you to use your existing organizational units in orders, the system must create business partners from these organizational units. The system uses the Organizational Unit role for the business partners it creates from organizational units.

1.1.14

Defining Number Range for Org. Business Partners (SAP CRM)

Use

For each organizational unit created in the organizational model a business partner is generated automatically. For this business partners a number range has to be created. If you don’t define a number range the created business partner will get a number that belongs to other business partner types, e.g. consumers.

Procedure

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

Transaction code BUCF

SAP CRM IMG menu Cross-Application Components à SAP Business Partner à Business Partner à Basic Settings à Number Ranges and Groupings à Define Number Ranges

4. In the next steps you define the number range for Org business partners. 5. Choose Insert interval (Shift+F1).

(11)

Field Value Remarks

No. Y4 Choose an ID with leading ‘Y’

From number 0004000000 If you use numeric values make sure you add leading zeroes to the value until the full length of the field is reached.

To number 0004000999 If you use numeric values make sure you add leading zeroes to the value until the full length of the field is reached.

Current number

Ext Internal number assignment is required. 7. Choose Insert (Enter).

8. Choose Save (Ctrl+S).

1.1.15

Defining Grouping for Org. Business Partners (SAP CRM)

Use

For each organizational unit created in the organizational model a business partner is generated automatically. This grouping can be used for selecting the number range when creating a business partner.

Procedure

1. Access the activity using the following navigation options:

Transaction code SPRO

SAP CRM IMG menu Cross-Application Components à SAP Business Partner

à Business Partner à Basic Settings à Number

Ranges and Groupings à Define Groupings and Assign Number Ranges

2. Choose New Entries (F5). 3. Enter the following values:

Field Value Remarks

Grouping Y4 The grouping must have the same ID as the assigned number range

Short name CRM Organizational Units

Description (EN) Business Partner for Org Units

Number range Y4 The number range you have created for Org Business Partners.

External Internal number assignment is required.

4. Choose Enter.

Int.Std.Grping Selected Ext.Std Grping Deselected 5. Choose Save (Ctrl+S).

(12)

1.1.16

Setting Up Integration

Use

Activate the integration of organizational units and business partners and assign the number range defined in the preceding sections.

Procedure

1. Access the activity using the following navigation options:

Transaction code SPRO

SAP CRM IMG menu Customer Relationship Management à Master Data à Business Partner à Integration Business Partner-Organization Management à Set Up Integration with Organizational Management

2. Enter the following values for the existing combination of Group and Sem.abbr.:

Group Sem.abbr. Value abbr Description

HRALX HRAC X Activate HR Integration HRALX OBPON ON Integration O-BP Activated HRALX ONUMB 2 Business Partner Number

Assignment (Org. Unit) HRALX OSUBG Y4 Business Partner Subgroup

(Organizational Unit) 3. Choose Save (Ctrl+S).

1.1.17

Executing Report for Changeover Classification

Use

A report has to be executed to changeover the customer classification from former CRM releases.

This report has to be executed once even in case of a new installed CRM system. Otherwise error messages during business partner processing will occur.

It has to be executed at this time because otherwise the business partners which are related to the organizational units are not created correctly.

Procedure

1. To run the report, use the following navigation option:

Transaction code

SA38

2. Enter the report CRM_MKTBP_ZCACL_UPDATE_30 and choose Execute (F8). 3. Keep the default values and choose Execute (F8).

4. In case of the status message Class Type BUP: No Suitable Classes Found no further actions are required.

5. In case of other messages, read the documentation of the report and run the report with deactivated flag for Test mode.

(13)

1.2

Maintaining Organizational Units

Use

Organizational units are functional units of a company. Depending on how task distribution is organized in a company, these can be, for example, departments, groups or project teams. Separate organizational units for marketing, sales and service will be defined.

The organizational unit in sales and distribution structures the company according to SD requirements. Sales transactions are prepared and implemented in a sales organization. Several sales offices or sales groups or other freely definable organizational units can be assigned at lower level than the sales organization. It is not possible, however, for other sales organizations to be subordinate to a sales organization. You can assign attributes to a sales organization in organizational plan maintenance. The sales organization is then responsible for these attributes; for example, one or more divisions and distribution channels, a language, or a postal code.

In addition there are organizational unit in the service area in which services are planned and

1.2.1

Creating an Organizational Model (SAP CRM)

Use

An organization model is created initially together with a root organizational unit which builds the basic node for all other organizational units.

Procedure

1. Access the Organizational Model using the following navigation:

SAP CRM WebClient menu Master Data Organization Model 2. Create a root organizational unit by choosing Root Organizational Unit. 3. Choose Continue.

4. Maintain the following values for this organizational unit::

Field name Value

General data

Code PPL_COMP

Description Phadnis Properties Ltd. Address

Address Suppl Phadnis Properties Ltd. Street/House No. Kalpavriksha, 2nd Floor

New 100 Ft. D.P.Road, Karvenagar

City Mumbai Postal Code 400063 Country IN Region MH Telephone no. 02067243000 Fax Number 02067243200 Attributes Country IN

Ref. currency for document IN Correspondence Language IN

5. Choose Save. An ID will be automatically created for the root organization. To display this ID, choose the button ‘Personalize’, move ‘ID from the Available Columns to the

(14)

1.2.2

Creating and Assigning Organizational Units

Prerequisites

The root node PPL_COMP has already been created as described in the preceding section.

Procedure

1. Access the activity using one the following navigation:

SAP CRM WebClient

menu Master Data Organization Model

2. Enter the description of the organizational unit, that has been created in the preceding section Oberoi Company and choose Search.

3. In the view area Result List, select the link of the root organizational unit PPL_COMP. This object has already been created in the preceding section.

4. In the assignment block Organizational Unit select the root organization PPL_COMP and choose the button Organizational Unit to create a new organizational unit on the level below.

5. In the assignment block Organization Unit Details and the view area General Data enter the Code and a Description for the new organizational unit.

6. Run the following steps to create the following SAP Best Practices organizational structure as an example to work with:

Description Hierarchy

Level Code

Phadnis Properties Ltd. 0 OB_COMP

PPL Sales Organization 1 PPL S Org

GM-Sales 2 GM-Sales

GM-Marketing 2 GM-Marketing

7. Save your entries using the Save button.

Result

The necessary organizational units for the marketing, sales and service scenarios have been created.

1.2.3

Assigning Attributes to Organizational Unit

Use

You can use general attribute maintenance to attribute data (attributes) to organizational units, when creating your sales and distribution or service structure. You always maintain these attributes specifically for a scenario (Sales or Service).

CRM distinguishes between organizational and business attributes:

 Organizational attributes define the type of organizational unit, for example, whether it is a sales organization or a service group.

 Business attributes define the responsibility of an organizational unit, for example, for which distribution channels or product groups an organizational unit is responsible. Attributes can have one or more values. For some attributes, you can also enter areas (for example, partner numbers 001 to 300).

(15)

The following organizational units are available in CRM for which you can enter the corresponding organizational unit in the ERP system.

Scenario Organizational attribute Corresponds in ERP with

Sales Sales organization Sales organization Sales Sales office Sales office

Sales Sales group Sales group

Service Service Organization Maintenance planning plant

Procedure

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

SAP CRM WebClient

menu Master Data à Organization Model

2. Enter the description Oberoi Company and choose Search.

3. In the view area Result List, select the link of the root organizational unit Oberoi Company. 4. In the assignment block Organizational Unit select the organizational unit, that you want to

maintain

5. In the view Allow Org. Unit to be Determined of the assignment block Organizational Unit

Details, select field if necessary. Otherwise this organizational unit will not be taken into

consideration for the organizational data determination.

Organizational Unit Details Organizational

Unit ID

Functions Allow Org. Unit to be Determined

BP_COMP

OCPL S Org Sales Organization Sales 1010 S Off Sales Office Sales 101 S Group Sales Group Sales 102 S Group Sales Group Sales 103 S Group Sales Group Sales 104 S Group Sales Group Sales 105 S Group Sales Group Sales 106 S Group Sales Group Sales 1011 S Off Sales Office Sales 111 S Group Sales Group Sales 112 S Group Sales Group Sales 1012 S Off Sales Office Sales 121 S Group Sales Group Sales 122 S Group Sales Group Sales 1015 S Off Sales Office Sales 151 S Group Sales Group Sales ORL S Org Sales Organization Sales 1110 Off Sales Office Sales 101 S Group Sales Group Sales 102 S Group Sales Group Sales

1. In order to maintain the attributes select the created organizational units one after another and choose Edit List in the assignment block Attributes.

2. Maintain all required attributes for all three scenarios (Marketing, Sales and Service) of an organizational unit if necessary.

(16)

Most of the values cannot be pre-defined because they are depending on the country or on the individual organizational structure.

Organizational

Unit ID Scenario Attribute

Value Value to

PPL_COMP Sales

Country IN

Ref. currency for document INR

Correspondence Language EN PPL S Org Sales

Only inherited attribute values GM-Sales Sales

Only inherited attribute values

3. In the assignment block Attributes, choose the button Check Consistency for the consistency. Examine the messages for the check results.

4. Choose Save.

1.2.4

Matching Sales Organization

Procedure

1. Access the activity using the following navigation options:

Transaction code SPRO SAP CRM IMG

menu Customer Relationship Management à Master Data à Organizational Management à Assignment of Organizational Units from SAP ECC à Assign SAP CRM Sales Organizations to SAP ECC Sales Organizations

2. Choose New Entries (F5).

3. Maintain the following data using the input help:

Sales Organization ID Field

Name R/3SlsOrg Entry

O 50000002 1031 4. Choose Save (Ctrl+S).

1.2.5

Maintain Holder for Positions

Use

You assign employees or users to positions; in doing this, you also determine the tasks assigned to them.

1.2.5.1

Defining Number Ranges for Employees

Use

You want to create employees with separate external number ranges in CRM.

Procedure

(17)

Transaction code BUCF SAP CRM IMG

menu

Cross-Application Components à SAP Business Partner

à Business Partner à Basic Settings à Number Ranges

and Groupings à Define Number Ranges

2. Choose Change intervals.

3. Choose Insert interval (Shift+F1). 4. Enter the following values:

No. From number To number Ext

Y1 0000001501 0000001530 5. Choose Save (Ctrl+S).

1.2.5.2

Defining Grouping for Employees

Use

You want to create employees with the external number ranges in CRM. You have to define the grouping and assign the number range to this grouping.

Procedure

1. Access the activity using the following navigation options:

Transaction code SPRO

SAP CRM IMG menu

Cross-Application Components à SAP Business Partner à Business Partner à Basic Settings à Number Ranges and Groupings à Define Groupings and Assign Number

Ranges

2. Choose New Entries (F5). 3. Enter the following values:

Grouping Short name Description Number range External Ext. Std. Grping Int Std. Grping Y1 CRM Employees CRM Employees Y1 Deselecte d Selected 4. Choose Save (Ctrl+S).

1.2.6

Assigning Employees to Positions

Prerequisites

You have maintained the organization units and the positions. Employees and users have been created.

Procedure

1. Log on to the CRM GUI screen.

2. Access the activity using the transaction code PPOMA_CRM: 3. In the search criteria area choose Find by Organizational Unit. 4. Choose Search.

5. In the view area Result List, select the link of root organizational unit, Phadnis Properties Ltd.

(18)

6. In the Organizational Unit view expand the tree to the position you want to assign an employee to.

7. Mark the Position. 8. Click on Employee.

9. Search the employee by criteria (last name, user ID). 10. Select the business partner.

11. Choose Save. 12. Choose Back.

1.2.7

Integration of System Users and Employees ERP <-> CRM

1.2.7.1

Creating System Users (SAP ERP)

Use

If not already done, you need to create some additional system users in the ERP system.

Procedure

1. To create a new system user, choose one of the following navigation options:

Transaction code SU01

SAP ERP GUI menu Tools à Administration à User Maintenance à Users

2. In the User field, enter the system user name. 3. Choose Create (F8).

4. Enter the following data:

Field name Value

Address tab page

Last name PANDIT First name MRINAL

Logon data tab page

Initial password Initial Repeat password Initial User Type Dialog

Profiles tab page

Profile Leave empty. Will be assigned in the next activity 5. Choose Save (Ctrl+S).

6. Repeat these steps for the following system all other users:

Result

Additional system users were created in the CRM system.

1.2.8

Set Up Buffering for Sales Scenario

Some processes of CRM need to have the sales areas. The sales areas are represented in the organizational model that you can maintain with the transaction PPOMA_CRM, this means they are not physically stored, but they are the result of the different combinations of sales organizations, sales offices, sales groups, channels and divisions maintained in the

(19)

Whenever a CRM transaction or a business partner needs the sales areas, they are

calculated, and this is an expensive process. To speed up this process, the sales areas are buffered.

Report HRBCI_ATTRIBUTES_BUFFER_UPDATE is used to buffer the attributes of organizational management objects. To enable buffering you have to maintain view T77OMATTR.

1.2.8.1

Enable Buffering for Sales Scenario

Procedure

1. Access the activity using the following navigation option:

Transaction code OOATTRCUST

2. Select the structure node Scenarios.

3. Flag the field in the column Buffering for the scenario SALE. 4. Mark scenario SALE.

5. Choose Attributes/Scenarios in the Dialog Structure

6. Adapt the values for the following combination of Scenario/Attribute::

Scenario Attribute Inherit Type Invisible Seq SALE IS_SA_GRP No inheritance Selected 00 SALE IS_SA_OFF No inheritance Selected 00 SALES IS_SA_ORG No inheritance Selected 00 7. Choose Save (Ctrl+S).

8. Log off and log on again to the CRM system in order to make the effect of these settings visible to your user.

2 Configuration settings of Master Data Replication

ERP -> CRM

2.1

Replicating Business Partners

2.1.1

Defining Sources for Business Partner Creation

Use

A business partner can be created and maintained in different classifications and in different systems depending on the business scenario. The following table describes the business partner usage in the Best Practices scenarios. An entry in the column CRM or ERP indicates that this business partner classification is mandatory in this system for a complete walk-through of the scenario.

(20)

Area Sales Marketing Service Classification

Required for CRM ERP CRM ERP CRM ERP

Customer X X X X X X

Prospective customer

X X

Competitor X

2.1.2

Business Partner Concept ERP <-> CRM

Use

The business partner concepts of the ERP system and the CRM system are different. Therefore you have to define a mapping when exchanging business partners from ERP to CRM and vice versa.

a) ERP System

• Every business partner has to be assigned to an account group that determines the properties of business partners, especially:

− Master data fields

− Number range

− Specific functionality for sales and distribution

• There are more than 20 different account groups available in the standard delivery.

b) CRM System

• Business partners in the CRM system are grouped by using classifications which determine:

− Master data fields

− Specific functionality

• The number ranges are not directly assigned to the classification. The number range is determined by the so-called grouping. This grouping has to be assigned manually or automatically when creating a business partner.

• There are only 5 different classifications

− Consumer: Organization

− Consumer: Person

− Customer

− Prospective customer

− Competitor

The mapping of business partners has to be defined for both directions: from the ERP system to the CRM system and vice versa. Thereby you have to:

• Map account groups to classifications and make sure that the required fields in both systems are identical

(21)

2.1.3

Defining Number Assignment Strategy for Business Partners

Use

1. Choosing identical number ranges

• Description

• The business partner IDs of ERP and CRM business partners are identical.

• There is always an internal assignment table that maps the ERP business partner ID to the corresponding CRM business partner to ensure a consistent data

exchange.

• Procedure

• There are two ways to guarantee identical number ranges. a) Leading system approach

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

For example: Customers (account group 0001) are only maintained in the OLTP ERP, consumers (account group 0170) are only maintained in the CRM system.

The account group and the mapped classification must have the same number range.

For the receiving system external number assignment is required.

You have to make sure that business partner creation in the receiving system is prohibited.

Mapping Example

CRM System OLTP ERP

Classificatio n From number to number Replicatio n direction Accoun t group From number to number Customer 1-999 External number range  0001 1 -999 Internal number range (leading) Consumer 1000 -ZZZ Internal number range (leading ) à 0170 1000 -ZZZ External number range

2.1.4

Mapping Business Partner Master Data from ERP to CRM

Use

This step is for the business partner exchange only from ERP to CRM. In the following section you perform all necessary steps to get the business partners from the ERP into the CRM system.

In order to map the business partner master data from ERP to CRM you have to run the following activities:

(22)

3. Defining CRM business partner groupings.

4. Mapping ERP account group to CRM classification

The following table describes all relevant elements that have to be maintained for the mapping of ERP account groups to CRM classifications. It is also mentioned at which activity the

element is maintained. It is recommended to maintain this table to keep the overview when running the following activities.

The mapping runs as follows:

1. A business partner for account group 0001 (sold-to party) is created in the ERP system. 2. The account group has the number range assignment 01 and internal number assignment,

i.e. a number is automatically created from the interval 0000100000-0000999999 for this business partner, e.g. 100001.

3. The business partner is replicated to the CRM system.

4. The account group is assigned to the classification Customer with grouping R001.

Grouping R001 is assigned to number range R1 that is identical to the ERP number range

01. The ERP customer that is replicated to the CRM system automatically is created with

classification Customer and gets the same number because external number assignment is chosen for the CRM number range.

2.1.5

Identifying Relevant ERP Account Groups (SAP ERP)

Use

In the ERP system, analyze the relevant account groups and their assigned number ranges. Identify the account groups that you are using when creating business partners in the ERP system. For these account groups a mapping has to be defined in the following activities.

Procedure

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

Transaction code OVT0

SAP ERP IMG menu Logistics - General à Business Partner à Customers

à Control à Define Account Groups and Field Selection for Customers

2. Select your relevant customer groups. 3. Choose Details (F2).

4. An overview table of the number ranges appears.

Select the field Number range and choose F4 to get the interval for this number range. In this table, the External field indicates whether the number range is internal or external.

A/c Grp A/c Grp Description No. Range Int/Ext

3110

Ph- PPL Dir domestic

customer V1 Ext

(23)

2.1.6

Defining Number Ranges for CRM Business Partners (I) (SAP

CRM)

Use

For each number range of the selected account groups of the ERP system you have to create a number range in the CRM system.

Procedure

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

Transaction code BUCF

SAP CRM IMG menu Cross-Application Components à SAP Business Partner à Business Partner à Basic Settings à Number Ranges and Groupings à Define Number Ranges

2. Choose Change intervals.

For each different number range identified in the activity Identifying Relevant ERP Account

Groups create a new number range.

3. Choose Insert interval (Shift+F1) and enter the number range according to the ERP number range.

4. Choose the Ext flag for the number range.

Number

Range Int/Ext

V1 Ext

5. Choose Save (Ctrl+S).

2.1.7

Defining CRM Business Partners Groupings (SAP CRM)

Use

For each number range created in the activity Defining Number Ranges for CRM Business

Partners you have to create a grouping. The business partner gets a number from the number

range that is assigned to the grouping. This grouping is only used for defining number ranges for business partners that are replicated from ERP to CRM.

Procedure

1. Access the activity using the following navigation options:

Transaction code SPRO

SAP CRM IMG menu Cross-Application Components à SAP Business Partner à Business Partner à Basic Settings à Number Ranges and Groupings à Define Grouping and Assign Number Ranges

2. Choose New Entries (F5).

Create a grouping for each number range interval created in the activity Defining Number Ranges for CRM Business Partners.

3. Enter the following values:

Grouping Description Number Range Int/Ext

3110

3 Direct Customers -

(24)

4. Choose Save (Ctrl+S).

2.1.8

Mapping ERP Account Groups to CRM Classifications (SAP ERP)

Use

For each of the ERP account groups you have to define a mapping to a CRM business partner classification and grouping. In the CRM system, the following business partner classifications exist: • Customer • Consumer: Organization • Consumer: Person • Sales Prospect • Competitor

Procedure

1. Access the activity using the following navigation option:

SAP ERP Transaction

code PIDE

For each account group you have to specify the classification (for example Consumer) and the grouping (that is, number ranges).

2. In the dialog structure choose R/3CRM: Assign Account Grp. to BP Classification.

3. Choose New Entries (F5). 4. Enter the following values:

Account

Group Account Group Description Classification Grouping Int/Ext

3110

Ph- PPL Dir domestic

customer B 3110 Int

5. Choose Save (Ctrl+S).

2.1.9

Mapping Business Partner Master Data from CRM to ERP

Use

This step is for the business partner exchange only from CRM to ERP. In the following section you perform all necessary steps to get the business partners from the CRM into the ERP system.

In order to map the business partner master data from CRM to ERP you have to run the following activities:

1. Defining number ranges for CRM business partners. 2. Defining CRM business partner groupings.

(25)

2.1.10

Defining Number Ranges for CRM Business Partners (SAP CRM)

Use

For the business partners created in the CRM system you have to define number ranges. You can define one number range for all classifications or define for example a separate number range for each classification.

Procedure

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

Transaction code BUCF

SAP CRM IMG menu Cross-Application Components SAP Business

Partner Business Partner Basic Settings

Number Ranges and Groupings Define Number

Ranges

2. Choose Change intervals.

No.

Range Interval (from) Interval (from)

V1 0031100001 0031109999

3. Choose Save (Ctrl+S).

2.1.11

Defining CRM Business Partners Groupings (SAP CRM)

Use

The grouping was created earlier. This grouping has to be assigned manually or automatically when creating a business partner. The business partner gets a number from the number range that is assigned to the grouping.

Procedure

1. Access the activity using the following navigation options:

Transaction code SPRO

SAP CRM IMG menu Cross-Application Components SAP Business Partner

Business Partner Basic Settings Number Ranges and

Groupings Define Grouping and Assign Number Ranges 2. Choose New Entries (F5).

Create a grouping for each number range interval created in the activity Defining Number

Ranges for CRM Business Partners.

3. Enter the following values:

Grouping Description 3110 Ph- PPL Dir domestic customer 4. Choose Save (Ctrl+S).

(26)

2.1.12

Mapping CRM Classifications to ERP Account Groups (SAP ERP)

Use

For each of the CRM business partner classifications you have to define a mapping to an ERP account group. Use the ERP account groups you have created in the activity Creating ERP

Account Groups.

Procedure

1. Access the activity using the following navigation option:

SAP ERP Transaction code

PIDE

2. In the dialog structure choose CRMR/3: Assign BP Classification to Account Grp.

3. Choose New entries (F5). 4. Enter the mapping according:

a) Customer

Assign the account group that is relevant in the ERP system for customers. This is also assigned when the business partner is additionally classified as a prospective

customer and a competitor in the CRM system.

CRM Classification ERP Account Group

Customer (B) 3110 (Ph- PPL Dir domestic customer) 5. Choose Save (Ctrl+S).

2.1.13

Synchronizing Field Settings for Business Partners (SAP ERP)

Use

In order to replicate business partners from the ERP to the CRM system and vice versa you have to synchronize the field settings for business partner, i.e. if a master data record field in the receiving system has the setting Required Entry an upload is only successful if this field maintained in the master data record of the sending system.

To avoid replicating problems the required entries of the master data records have to be identical.

Procedure

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

Transaction code OVT0

SAP ERP IMG menu Logistics - General > Business Partners > Customers > Control > Define Account Groups and Field

Selection for Customer

2. Choose an account group that is relevant for the mapping. 3. Choose Details (F2).

4. Double-click on the text General data in the screen area Field status.

5. Double-click on each of the different entries in the Select Group area, for example,

Address. The corresponding field list is displayed.

6. Repeat these steps for all field status areas (Company code data, Sales data).

(27)

General Data Name 1/last name

Postal code, city

Sales data Pricing Procedure Shipping Conditions/POD

relevance

7. Save your changes.

2.1.14

Selecting Customers for Replication (SAP CRM)

Procedure

1. This step is optional, and has to be performed in case there are any business partner (relevant for CRM) available in ERP. This activity was not needed in current case, but documented for future reference.

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

Transaction code R3AC1 SAP CRM GUI

menu

Architecture and Technology à Middleware à Data Exchange à Object Management à Business Objects

3. To set the filter for the business object CUSTOMER_MAIN, click on the filter symbol. 4. Go to the tab Filter Settings.

5. In the field Source Site Name, choose the site source of your data (normally OLTP). 6. Make sure that you are in change mode. Choose Display <-> Change (Ctrl+F1).

7. Choose the relevant data for your filter settings, for example you can specify the customer numbers for replication.

8. Enter the following data:

Table/Stru cture

Field OP Low High Incl./Excl.

KNA1 KUNNR BT <put number of customer as in KNA1 table> <put number of customer as in KNA1 table> Inclusive defined set/array 9. Choose Save (Ctrl+S)

10. Choose No to all on the first dialog box.

11. Choose Continue (Enter) on the second dialog box..

2.1.15

Replicating Customers (SAP CRM)

Procedure

1. This step is optional, and has to be performed in case there are any business partner (relevant for CRM) available in ERP. This activity was not needed in current case, but documented for future reference.

(28)

2. To replicate the customers, either as specified in the filter or all customers, into the CRM system, access the activity using one of the following navigation options:

Transaction code R3AS

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

3. In the Load Object field, enter CUSTOMER_MAIN.

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

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

6. Confirm the next screen message by choosing Continue (Enter).

2.1.16

Monitoring Replication Status (SAP CRM)

Procedure

1. This step is optional, and has to be performed in case there are any business partner (relevant for CRM) available in ERP. This activity was not needed in current case, but documented for future reference.

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

Transaction code R3AM1

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

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

4. Choose Execute (F8).

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

2.1.17

Checking Business Partners (SAP CRM)

Prerequisites

In the business partner maintenance of the CRM system, make sure that the business partner has a corresponding entry in the Sales Area of the sales, distribution, and invoicing data.

Procedure

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

SAP CRM WebClient menu Master Data à Accounts

2. Enter the Account ID of your business partner in the Search Criteria field Account ID is. 3. In Search Criteria field Role, choose the Role Sold-to.

4. In the area view Result List double-click on the business partner Name.

5. Then scroll down to the view area Sales Area Data. This view area might be hidden. It can be added by choosing Personalize in this Account View.

2.1.18

Monitoring Replication Status (SAP CRM)

Procedure

(29)

Transaction code R3AM1

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

2. In the Object Name field, enter CUSTOMER_REL 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.

2.1.19

Checking Completeness of Replication (SAP CRM)

Procedure

To check the completeness of the contact person replication, carry out these steps: 1. Access the activity using one of the following navigation options:

Transaction code SE16

SAP CRM GUI menu Architecture and Technology à ABAP Workbench à

Overview à Data Browser

2. Enter BUT050 in the field Table Name. 3. Choose Table Contents (Enter).

4. Compare the number of entries with the Relationship Category value BUR001 Contact

Person Rel.ship with the number of entries in the ERP table KNVK.

The number of entries should be identical. Please note that all contact persons for which the corresponding business partner isn’t available in the CRM system are not replicated, i.e. you have to set a filter in the tables which is identical with the filter used for the download of customers.

2.2

Replicating Materials

Use

The following activities are required to replicate the product settings to the CRM system:

• Checking Material

• Defining Item Category Groups

• Selecting Materials for Replication

• Replicating Materials

• Monitoring Replication Status

2.2.1

Checking Material (SAP ERP)

Use

In this step you check whether the material master that you want to sell in your CRM system is in the corresponding sales area in the ERP system.

Procedure

(30)

Transaction code MM03 SAP ERP GUI

menu

Logistics à Materials Management à Material Master

à Material à Display à Display Current

2.2.2

Defining Item Category Groups

Use

The item categories of the ERP back end have to be created in the same way in the CRM system.

2.2.3

Checking Item Category Groups (SAP ERP)

Procedure

1. Access the activity using the following navigation options:

Transaction code SPRO

SAP ERP IMG menu Sales and Distribution à Sales à Sales Documents

à Sales Document Item à Define Item Category Groups

2. All the item category groups are to be copied which are there in ERP.

2.2.4

Copying Item Category Groups (SAP CRM)

Procedure

To create the item category groups in the CRM system, carry out these steps: 1. Access the activity using the following navigation options:

Transaction code SPRO

SAP CRM IMG menu Customer Relationship Management à Transactions

à Basic Settings à Define Item Category Group

2. On the Item Category Group screen choose New Entries (F5). 3. Paste the relevant item category groups of the ERP back end. 4. Choose Save (Ctrl+S).

2.2.5

Selecting Materials for Replication (SAP CRM)

Procedure

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

Transaction code R3AC1

SAP CRM GUI menu Architecture and Technology à Middleware à Data Exchange à Object Management à Business Objects

2. Set the filter for the business object MATERIAL by clicking on the filter symbol. 3. Make sure that you are in change mode. Choose Display <-> Change (Ctrl+F1). 4. In the field Source Site Name choose OLTP.

5. Specify the material numbers for replication, for example by selecting table MARA and field MATNR.

(31)

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

MARA MATNR EQ <Low number>

Inclusive defined set/array

7. Choose Save (Ctrl+S).

8. Choose No to all on the first dialog box.

9. Choose Continue (Enter) on the second dialog box. 10. Choose Filter Sync.

11. Choose Continue (Enter) on the dialog box.

If you specify filter criteria and enter values into numeric fields to narrow the range of objects to be downloaded, make sure you add leading zeros to the value until the full length of the ERP database table field is reached.

Material number MARA.MATNR requires 18 digits (000000000010000040). The material number must have the same format as in the ERP system, check database entries with transaction code SE17.

2.2.6

Replicating Materials (SAP CRM)

Procedure

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

Transaction code R3AS SAP CRM GUI

menu

Architecture and Technology à Middleware à Data Exchange à Initial Load à Start

2. In the Load Object field, enter MATERIAL.

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

2.2.7

Monitoring Replication Status (SAP CRM)

Procedure

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

Transaction code R3AM1 SAP CRM GUI

menu

Architecture and Technology à Middleware à Data Exchange à Initial Load à Monitor Objects

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

(32)

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

2.2.8

Checking Materials (SAP CRM)

Prerequisites

In the product maintenance of the CRM system, make sure that the product has entries for Sales and Distribution.

Procedure

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

SAP CRM WebClient menu Master Data à Products

2. Enter the Product ID of one of your replicated products from ERP to CRM.

3. Choose a product in the Result List view area and check the fields in the view areas

Product Details, Categories for completeness.

2.3

Replicating Conditions

This chapter describes the Initial Load of Condition Customizing Data and Condition Master Data for specific pricing procedures.

When using SAP Best Practices for CRM the sales order processing (quotation, sales order) takes place in the ERP system only.

2.3.1

Creating Pricing Procedures

Use

In order to replicate condition customizing data and condition master data you have to make sure that the following activities, creating two new customer pricing procedures, have been executed in ERP.

Procedure

1. Access the activity using the following navigation options:

Transaction code SPRO

SAP ERP IMG menu Sales and Distribution à Basic Functions à Pricing à Pricing Control à Define And Assign Pricing

Procedures

2. Choose Maintain pricing procedures.

3. Choose New Entries (F5) and create the new pricing procedure ZOCLPR CRM Pricing

Procedure PPL.

4. Choose Enter.

5. Select the newly created pricing procedure and choose Control data in the left-hand Dialog Structure.

6. Choose New entries (F5) and create pricing procedure as below:

Lev el Co un Usa ge Con. Type Fro m To Manu al Subto tal Calculat ion Formul Base Form ula Cond.

(33)

a 30 0 PR ZPPL X 2 45 0 PR ZCAR 30 X 2 100 0 PR ZAGV 30 45 102 0 PR ZPSD X 2 104 0 PR ZPRC X 2 106 0 PR ZPEC X 2 108 0 PR ZOPV 100 X 2 110 0 PR ZPCH X 2 112 0 PR ZPMC X 2 900 0 PR YEST 30 X 10 920 0 PR YES1 900 X 950 0 PR YES2 900 X 140 0 PR ZBRO 2 7. Choose Save (Ctrl+S).

8. Save your entries and select a customizing request if required.

Result

Pricing procedure ZOCLPR will be used for the scenario Opportunity Management.

2.3.2

Replicating Conditions (SAP CRM)

Use

The initial load of the condition customizing object is performed before the initial load of the condition master data objects and after the initial load of business partner master data and material master data has been performed.

Please see SAP note 484073 for information about cross-client and client-specific customizing tables.

2.3.2.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. This activity was performed using download object DNL_CUST_CNDALL. For future maintenance create own download object as described in steps below, which is given as example.

In case you would like to run another condition customizing download in an additional CRM client it is recommended to use (copies of) the download objects DNL_CUST_PRC and DNL_CUST_CND_PR with filters instead of DNL_CUST_CNDALL because

DNL_CUST_CND_ALL comprises client independent and client dependent customizing whereas the other two objects are restricted to client specific customizing.

(34)

Procedure

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

Transaction code R3AC5

SAP CRM menu Architecture and Technology Middleware Data

Exchange Object Management Condition

Objects

2. Choose Create in the 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 procedures that you are downloading to the CRM system. Otherwise, deactivate these tables. T68 5, T685A, T685T, T685Z Using field KSCHL enter only those condition

(35)

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.

6. For the SAP Best Practices scenarios only two pricing procedures have to be replicated from the ERP system to the CRM system: a simplified pricing procedure for CRM Opportunity Management (Y00001) and a pricing procedure for Service Order

Management <PP Sales> identified in section Determine ERP Sales Pricing Procedure. In order to restrict the download at least on the level of pricing procedures you can add the following filters to the T683 tables in the new download object YDNL_CUST_CNDALL and keep all other filters unchanged:

Table Field Operator Value

T683 KALSM EQ Equality (= Low) Y00001 T683 KALSM EQ Equality (= Low) <PP Sales> T683S KALSM EQ Equality (= Low) Y00001 T683S KALSM EQ Equality (= Low) <PP Sales> T683T KALSM EQ Equality (= Low) Y00001 T683T KALSM EQ Equality (= Low) <PP Sales> T683U KALSM EQ Equality (= Low) Y00001 T683U KALSM EQ Equality (= Low) <PP Sales> 7. Choose Save (Ctrl+S).

2.3.2.2

Replication of Condition Objects

Use

The purpose of this task is to replicate the condition customizing and the condition master data from the ERP back-end system to the CRM system.

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

Transaction code R3AS

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

2. Select the new download object YDNL_CUST_CNDALL (if created new) (or the objects

DNL_CUST_PRC and DNL_CUST_CND_PR) or DNL_CUST_CNDALL for the condition

customizing data.

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

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

References

Related documents

• Speed of weaning: induction requires care, but is relatively quick; subsequent taper is slow • Monitoring: Urinary drug screen, pain behaviors, drug use and seeking,

Protein analysis was performed in human prostate cancer cell lines LNCaP, LNCaP-abl, PC-3 and DU145 to compare expression levels in hormone- dependent

Non-Convex Problem (1) (NP-hard in general) Randomness Geometric Analysis Construction of Dual Certificate Reduction to Low-Rank Approximation Strong Duality Exact

Online community: A group of people using social media tools and sites on the Internet OpenID: Is a single sign-on system that allows Internet users to log on to many different.

UC-Paid Life Insurance: Appointed 50% or more for a year or more and participating in a university retirement plan. UC-Paid Disability Insurance: Appointed 50% or more for a year

96 This analytical framework is a more effective method to address the “multifaceted nature of inequality.” 97 It is a way to “assess and assist in modifying laws, policies

Quality: We measure quality (Q in our formal model) by observing the average number of citations received by a scientist for all the papers he or she published in a given

To test this concept, 48 hours in vitro (hiv) hippocampal neurons were treated for different time periods with freshly prepared myelin extracts, and the levels of membrane Gal-4