B08 Varaint Configuration in CRM

CRM 4.0

June 2004

English

CRM Cross-Topic Functions

SAP AGNeurottstr. 1669190 WalldorfGermany

Building Block Configuration Guide

SAP Best Practices CRM Cross-Topic Functions: Configuration Guide

Copyright

© Copyright 2004 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®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® 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 and Informix® Dynamic Server™ are trademarks of IBM Corporation in USA 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®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.

HTML, DHTML, XML, XHTML 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.

MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, 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 information purposes only. National product specifications may vary.

© SAP AG Page 2 of 48


Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Typographic Conventions

Type Style Description

Example text Words 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 text Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT Names 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 text Screen 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 TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

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

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



ContentConfiguration Guide........................................................................................................................7

1 Purpose .................................................................................................................................... 7

2 Preparation ............................................................................................................................... 7

.2.1 Prerequisites ..................................................................................................................... 7

.2.2 Uploading the Configuration Role ..................................................................................... 7

3 Configuration ............................................................................................................................ 8

.3.1 SAP Business Workflow ................................................................................................... 8

3.1.1 Defining Basic Settings for Workflow ........................................................................... 8

.3.2 Availability Check .............................................................................................................. 9

3.2.1 R/3 Configuration ...................................................................................................... 11

.3.2.1.1 Activating Availability Check from CRM .......................................................... 11

.3.2.1.2 Defining Entries for Availability Check ............................................................ 11

.3.2.1.3 Assigning Process Function Modules ............................................................. 12

3.2.2 CRM Configuration .................................................................................................... 12

.3.2.2.1 Setting Up Middleware Parameters ................................................................ 12

.3.2.2.2 Creating ATP Profile ....................................................................................... 13

.3.2.2.3 Assigning ATP Profile to Item Category .......................................................... 14

.3.2.2.4 Scenario-Specific Settings .............................................................................. 14

.3.3 Credit Limit Check ........................................................................................................... 15


.3.3.1.1 Defining Destination for Credit Check ............................................................. 15

.3.3.1.2 Defining Credit Group ..................................................................................... 16

.3.3.1.3 Assigning Credit Group to Item Category ....................................................... 16

.3.3.1.4 Activating the Credit Check ............................................................................. 17

.3.3.1.5 Business Workflow for Credit Management .................................................... 18

.3.3.1.5.1 Maintaining Employees in the Organizational Structure .......................... 19

.3.3.1.5.2 Specifying the Supervisor as Agent for the Workflow Tasks .................... 19

.3.3.1.5.3 Activating Event Linkage ......................................................................... 20

3.3.2 R/3 Configuration ...................................................................................................... 20

.3.3.2.1 Checking Definition of Credit Group for Sales Orders ..................................... 20

.3.3.2.2 Checking Assignment of Credit Group to Order Type ..................................... 21

.3.3.2.3 Checking Definition of Credit Control Area .................................................... 21

.3.3.2.4 Checking Assignment of Company Code to the Credit Control Area .............. 22

.3.3.2.5 Checking Assignment of Sales Area to the Credit Control Area ..................... 22

.3.3.2.6 Checking Definition of Risk Category for Customer ........................................ 23



.3.3.2.7 Checking Credit Limit Definition for Customer and Risk Category Assignment ..................................................................................................................................... 23

.3.3.2.8 Checking Definition of Automatic Credit Control ............................................. 24

.3.4 Payment Cards ............................................................................................................... 25

3.4.1 Determining Organizational Unit for Clearing (SAP CRM) ........................................ 26

3.4.2 Defining Blocking Reason ......................................................................................... 27

3.4.3 Defining Merchant IDs ............................................................................................... 27

3.4.4 Assigning Merchant IDs ............................................................................................ 28

3.4.5 Determining Authorization Module ............................................................................ 29

3.4.6 Maintaining the Card Numbers for the Business Partner .......................................... 29

.3.5 Free Goods ..................................................................................................................... 30

3.5.1 Checking the Customizing Download (SAP CRM) .................................................... 31

3.5.2 Assigning the Procedure for Free Goods .................................................................. 31

3.5.3 Defining Item Category Determination for Free Goods (SAP CRM) .......................... 32

3.5.4 Maintaining Condition Records for Free Goods (SAP R/3) ....................................... 33

3.5.5 Checking Condition Records in SAP CRM ................................................................ 33

.3.6 Product Determination .................................................................................................... 34

3.6.1 Checking the Customizing Download (SAP CRM) .................................................... 34

3.6.2 Assigning the Procedure for Product Determination (SAP CRM) .............................. 35

3.6.3 Checking the Substitution Reasons ........................................................................... 36

3.6.4 Maintaining Condition Records .................................................................................. 36

3.6.5 Checking Condition Records in SAP CRM ................................................................ 37

.3.7 Variant Configuration ...................................................................................................... 37

3.7.1 R/3 Configuration ...................................................................................................... 38

.3.7.1.1 Creating Knowledge-Base Objects in R/3 ....................................................... 38

.3.7.1.2 Creating Runtime Versions in R/3 ................................................................... 39

<date> ................................................................................................................................... 40

1 ............................................................................................................................................ 40

<numeric key for your plant> ................................................................................................ 40

<key for the application for selecting your BOM> ................................................................. 40

<blank> ................................................................................................................................. 40


.3.7.2.1 Maintaining Number Ranges for Configurable Products ................................ 41

000000000001 ...................................................................................................................... 41

.3.7.2.2 Replicating Customizing Objects ................................................................... 41

.3.7.2.3 Selecting Knowledge-Base Objects for Replication ........................................ 43

OLTP .................................................................................................................................... 43



SCEKB .................................................................................................................................. 43

KBOBJNAME ........................................................................................................................ 43

<name of your knowledge-base object> ............................................................................... 43

<name of your knowledge-base object> ............................................................................... 43

.3.7.2.4 Replicating Knowledge-Base Objects ............................................................ 44

.3.7.2.5 Replicating Configurable Products .................................................................. 44

.3.7.2.6 Replicating Single Condition Tables .............................................................. 45

.3.8 US Taxes ........................................................................................................................ 45

3.8.1 U.S.: Methods of Determining US and Canadian Taxes in R/3 ................................. 46

3.8.2 U.S.: Why External Taxes Are Needed for Tax Determination in CRM ..................... 46

3.8.3 U.S.: Tax Determination Using Third-Party Software by Vertex ................................ 46

3.8.4 U.S.: Connecting and Activating External Tax Software ............................................ 47

.3.8.4.1 U.S.: Connecting CRM to Vertex .................................................................... 47

.3.8.4.1.1 U.S.: Defining Physical Destination ........................................................ 47

3.8.5 U.S.: Assigning Pricing Procedure to US Sales Organization ................................... 48



Configuration Guide

1 PurposeThe Building Block CRM Cross-Topic Functions contains the steps to implement those functions in a CRM system which are an optional enlargement within the context of a CRM sales scenario, like for example Internet Sales: Business-to-Business.

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, without the support of automated configuration tools. If you want to use BC Sets and CATT procedures for an automated installation process, refer to the Installation Guide of the Building Block CRM Cross-Topic Functions.

2 Preparation

.2.1 PrerequisitesBefore starting with the installation of this Building Block, please see the Scenario Installation Guide of the SAP Best Practices CRM scenario that you want to install.

.2.2 Uploading the Configuration Role

UseBefore you start with the configuration according to the manual procedures described in this Configuration Guide, you need to upload the configuration role and assign it to your user.

With the Building Block CRM Cross-Topic Functions a configuration role is provided to access all transactions relevant for the installation:

Technical name Description

File name for upload

B08_01C B08 - CRM Cross-Topic Functions Configuration Role (SAP R/3) B08_01C.SAP

B08_04C B08 - CRM Cross-Topic Functions Configuration Role (SAP CRM) B08_04C.SAP

ProcedureFor details on how to upload the configuration roles to the system and how to work with the roles please refer to Building Block Essential Information.



3 Configuration

.3.1 SAP Business Workflow

3.1.1 Defining Basic Settings for Workflow

UseWith this activity, you maintain the standard settings for the SAP Business Workflow with the help of the Auto Customizing.

You can execute checks in order to make sure that customizing for the SAP Business Workflow is complete regarding further important settings. You can start a verification workflow . The automatic customizing does not contain task-specific customizing (assigning tasks and possible processors).

Scenario-specific settings for the workflow are provided with the scenario configuration guides.

Procedure1. To carry out the activity, choose one of the following navigation options:

SAP CRM Role Menu Defining Basic Settings for Workflow

Transaction code SWU3

IMG Path CRM Basic Functions SAP Business Workflow Maintain standard settings for SAP Business Workflow

2. From the menu choose Auto-Customizing Execute.

3. The system will automatically maintain a minimum of required data.

4. Choose the activity Maintain Definition Environment Maintain Prefix Numbers.

5. Choose Execute.

6. Choose Display <-> Change.

7. Choose Create.

8. Enter the following data:

Field name Value

Prefix number <New prefix>

SAP System ID <System-ID CRM system>

Client number <Client number CRM system>

Package <Dev. Class>

9. Choose Save.

10. Choose the activity Maintain Additional Settings and Services Maintain Standard Domain for Internet Mail.

11. Choose Execute.



The information about the relevant standard domain can be provided by your IT department.

For detailed information concerning configuring e-mail service see note 455140.

12. Enter the domain.

13. Save your entries.

14. To change the default RFC destination for the Workflow choose the entry Maintain Runtime Environment Configure RFC Destination and press Execute (F8).The system attempts to logon with the standard user WF-BATCH for the RFC destination WORKFLOW_LOCAL_xxx (xxx = CRM client). By overwriting the default values for user and password you create a new user and password for this RFC destination.

15. Start a verification workflow by choosing Menu Extras Start Verification Workflow (F5).Follow the instructions on the screen. Make sure that you can execute these as described.

16. Go to the Business Workplace (Transaction SBWP).Under Inbox Workflow you will find a user decision work item.

17. Execute this work item.You receive two mails. These are the notifications of completion for this user decision and the subsequent background step.

The system user WF-BATCH is created. All automatically created users have the profiles SAP_ALL and SAP_NEW assigned to them, which gives them full authorization rights. If this authorization is not applicable to your project you can restrict the rights of these users according to SAP Note 0338537.

.3.2 Availability Check

PurposeAvailability check (ATP check) is used to check whether a product can be confirmed in a sales order, based on the fact that enough stock is available or can be produced or purchased on time.

For the availability check in the CRM system three methods are offered:

1. Availability information using the R/3 system

2. Availability check using the R/3 system

3. Availability check using the APO system

The choice of the methods depends on the used SAP components and the complexity of the required availability check.



MethodRequired SAP Comp.

FunctionalityRestrictions

1 R/3

simple availability check for initial sales processes, e.g. quotation

no product reservation

no transfer of ATP requirements to production or purchasing

reservation and requirement transfer take place after order creation in the R/3 system

2 R/3

availability check with reservation and transfer of requirements to production or purchasing

Not supported:

• Batch processing

• Assembly production

• Third-party processing

• Rescheduling

• Individual purchase order

• Material determination and product selection

• Free goods (that is, the inclusive bonus quantity)

• Material listing and exclusion

• Delivery groups

3 APO

Support of further strategies for checking the availability of products to the ATP check strategy supported in SAP R/3, e.g. rule-based ATP check.

This document contains all activities required for setting up the availability check using the R/3 system (method 2).

PrerequisitesThe R/3 release must be at the lowest 4.6B and the Plugin Version (PI) must be 2002.2 or higher

You have checked the time zones of both systems. Both have to be in the same time zone because no time conversion takes place.

RestrictionsFor further information on restrictions, see also the following SAP Note:

Release SAP Note Title

CRM 4.0 624992 CRM 4.0: CRM-ATP based on R/3-ATP (local ATP)



3.2.1 R/3 Configuration

.3.2.1.1 Activating Availability Check from CRM

UseIn SAP R/3 you must activate the functionality for the Availability Check Using SAP R/3.


SAP R/3 Role Menu Activate Availability Check from CRM

Transaction Code FIBF

2. Choose Settings → Identification → SAP applications.

3. Select New Entries.

4. Create the following table entry.

Field name Values

Appl. CRMATP

Active X

Text R/3 ATP check called by CRM


.3.2.1.2 Defining Entries for Availability Check

UseIn SAP R/3 you have to define the events that trigger the data exchange required for the availability check.


SAP R/3 Role Menu Defining Events for Availability Check

Transaction Code FIBF

2. Choose Settings → P/S function modules → …of an SAP appl.



Event Ctr. Appl. function module

01000820 BC-MID SD_CRM_GET_DOC_SCENERIO

01000821 BC-MID VBAK_LOGSYSB_GET




.3.2.1.3 Assigning Process Function Modules

UseIn SAP R/3 you have to define the process function modules for the availability check.


SAP R/3 Role Menu Assign process function modules

Transaction code FIBF

2. Choose Settings → Process function modules → …of SAP appli.




Event Ctr. Appl. Function module

01000820 CRMATP PERS_ENQ_ATP_ENTRIES_SELECT

01000821 CRMATP PERS_ENQ_ATP_ENTRIES_INSERT


3.2.2 CRM Configuration

.3.2.2.1 Setting Up Middleware Parameters

UseIn addition to the RFC connections, some parameter settings are necessary to specify the communication between the SAP CRM system and the SAP R/3 system. Therefore you have to implement a new entry in table SMOFPARSFA that specifies the R/3 system to which the availability request is supposed to be addressed.

PrerequisitesThe connectivity to your R/3 system must have been set up.


SAP CRM Role Menu Setting Up Middleware Parameters

Transaction code R3AC6

SAP Menu Architecture and Technology Middleware → Administration → Define Middleware Parameters





Field name User action and values Comment

Key field R3A_COMMON

Paramname CRM_DEFAULT_DESTINATION

Paramname2 CRM_R3MATERIAL_AVAIL

Name

Paramval <Name of your R/3 Backend Destination>

Paramval2 X=R/3<x.yz> <x.yz> stands for the SAP R/3 release, e.g. 4.70

If you omit the X in the Control Information field, SAP R/3 is not activated


Although a transport request is provided for this activity it is not recommended to transport this entry because it contains a RFC destination that is different in the target system.

.3.2.2.2 Creating ATP Profile

ProcedureTo carry out the activity, choose one of the following navigation options:

SAP CRM Role Menu Define ATP Profile

Transaction code SPRO

IMG path CRM Basic Functions → Availability Check → Availability Check Using SAP R/3 → Define ATP Profile

1. Make a new entry with the following data:

Field name User action and values

ATP Prof. 200

Description Availability Check in the SAP R/3 System




.3.2.2.3 Assigning ATP Profile to Item Category

Please check the Delta Guide.

Use

To call the availability information by the CRM Online Application and then carry it out in the SAP R/3 System, you have to leave the field for the ATP profile assignment empty.


SAP CRM Assigning ATP Profile to Item Category


IMG path CRM Basic Functions Availability Check → Availability Check Using SAP R/3 Assign ATP Profile to Item Category

1. Select the required item category for the ATP check in SAP R/3 system, e.g. TAN, and choose Detail.

2. Enter or check the following data


ATP Prof. 200 Availability Check in SAP R/3 System

3. Change your data if required.


.3.2.2.4 Scenario-Specific SettingsFor the following CRM scenarios additional settings are required:

• Internet Sales B2B

• Internet Sales B2C

• Telesales Inbound

• Telesales Outbound

For detailed information refer to the scenario-relevant configuration guide.



.3.3 Credit Limit Check

UseCredit management limits financial risks for your organization by allowing you to carry out credit checks in transaction processing, and by forwarding documents, blocked for credit reasons, directly to the employees responsible for reviewing them.

1. You trigger the credit check either when you save a document, or when you choose the Credit Check icon at the top of the item screen area.

2. CRM then gets ready to do the check, which may actually consist of a series of checks, one for each item category in the document. CRM therefore first groups the items by item category, and, for each group, totals the open values of the requested quantity of error-free items, including tax. If the document contains items belonging to one item category, CRM only does one check.

3. CRM calls up the automatic credit check and sends the information on open values to R/3, along with data on the credit group, sales organization, currency, payer and other business partners.

4. R/3 uses this information to determine the R/3 credit group, credit control area, credit management account of the payer, and the risk category of the account.

5. R/3 checks the payer's credit standing.

6. It then sends the results of the credit check back to CRM.

7. CRM enters the overall credit status for the document on the Status tab page in the document header, and enters credit status for each item on the Status tab pages at item level. CRM also enters messages, describing the results of the check, in the application log.


.3.3.1.1 Defining Destination for Credit Check

UseTo carry out a credit check, CRM uses a Remote Function Call (RFC) to contact the R/3 system where you do financial accounting.

The RFC destination to your R/3 system has already been defined in the chapter. You only have to specify this destination for the credit check.


SAP CRM Role Menu Defining Destination for Credit Check


IMG path CRM CRM Middleware and Related Components Communication Setup Middleware Parameters Define Middleware Parameters

1. In Choose Activity, choose OLTP R/3 credit check.



2. Enter the following data:


Key CRMCREDCHE

Parameter 1 CRMCREDCHE

Paramval <R/3 RFC connection>e.g. ES7CLNT03

3. Save your data.

.3.3.1.2 Defining Credit Group

UseHere you define credit groups and specify which rule the system uses for a particular credit group when it does credit checks.

The system includes credit group 01, for which it uses rule 01. Rule 01 calls up the automatic credit check in SAP R/3.


SAP CRM Role Menu Defining Credit Group


IMG path CRM Basic Functions Credit Management Maintain Credit Group

1. Check whether the following entries does already exist:


CredUpdate deselected

Credit Grp. 01

Description Standard order

Check Rule 01

Description Automatic Credit Check, SAP Standard

2. If it exists, you can simply leave the transaction. If the table is still empty or doesn’t contain this record, create the entry and save your settings.

.3.3.1.3 Assigning Credit Group to Item Category




UseThis activity has the following three levels:

1. On the first level, Item Categories, define a new item category or choose an existing one to which you want to assign a credit group.

2. On the second level, Assignment Application Area, choose the relevant transaction category, such as sales or service.

3. On the third level, Customizing at Item Level, in the Billing data group box, choose a credit group.

You assign a credit group to an item category on the third level.

Then when you create a transaction that includes items of this category, the system groups them, totals their open values, and does a credit check using the rule you specified for this credit group.

The system determines open values for item categories according to what item object types they are assigned. It determines open values for item object types as follows:

• For CRM Sales Items that are replicated and invoiced in SAP R/3, it adds together the net value and the tax of confirmed, open (still to be delivered), items. If no items are confirmed, it uses the requested quantity.

• For CRM Customer Financing Items it calculates the amount to be financed.

• For CRM Quantity and Value Contract Items it calculates the target value.

• For all other item object types, it adds together the net value and the tax.

To determine open values differently, you must create your own method of determining open values. To do so in Customizing, choose Customer Relationship Management → Basic Functions → System Enhancements → Credit Management → Determine Open Values.


SAP CRM Role Menu Assigning Credit Group to Item Category


IMG path CRM → Basic Functions → Credit Management → Assign Credit Group to Item Category

1. Select the item category used for your sales order transaction, e.g. TAN (Standard Sales Item) and choose Assignment of Business Transaction Categories from the structure tree.

2. Select transaction category Sales and choose Customizing Item from the structure tree.

3. Assign a credit group, for example, 01 Standard order.

4. Save your data.

.3.3.1.4 Activating the Credit Check




UseThis activity has the following three levels:

1. On the first level, Transaction Types, define a new transaction type or choose an existing one for which you plan to do credit checks.

2. On the second level, Assignment of Business Transaction Categories, choose the appropriate category.

3. On the third level, Customizing at Header Level, in the General group box, select the Credit check field.

You activate the credit check for a transaction type on the third level.

Then when you create and save a transaction of this type, the system carries out a credit check. Also, the toolbar at the top of the item area in these transactions contains a Credit check button, with which you can trigger a check at any time in a transaction.


SAP CRM Role Menu Activating Credit Check


IMG path CRM Basic Functions Credit Management Activate Credit Check in Transaction

1. Select Transaction type used for your sales orders, e.g. TA and choose Assignment of Business Transaction Categories from the structure tree.

2. Select Transaction category Sales and choose Customizing header.

3. Under General, set the flag for Credit Check.

4. Save your data.

.3.3.1.5 Business Workflow for Credit Management

UseThis workflow supports credit management in CRM by automatically forwarding transactions that are blocked as the result of a credit check to the employee responsible for reviewing them.

This workflow is triggered when a credit check for a transaction results in the status Credit Check not OK. Using the organizational data model, the system determines the supervisor of the employee who created the transaction, and sends a workflow task to his inbox.

From the inbox, the supervisor can call up and view the transaction document. On the Status tab page in the header, he can release or reject the whole transaction, or on the Status tab page at item level, release or reject individual items.

If he rejects the whole transaction, he enters a reason for the rejection. If he processes individual items, the transaction stays in the workflow until all blocked items are either released or rejected.



PrerequisitesYou have maintained the standard settings for the SAP Business Workflow. See section Basic Settings for Workflow of this guide.

.3.3.1.5.1 Maintaining Employees in the Organizational Structure

UseYou have to create the positions for the employee of the sales organization and his or her supervisor in the organizational structure. For example, the positions Sales Manager and Sales Assistant have to be maintained.

If you are a U.S. customer, ensure that you create an employee position for your U.S. sales organization


SAP CRM Maintaining Employees in the Organizational Structure

Transaction code PPOMA_CRM

SAP Menu Master Data Organizational Model PPOMA_CRM - Maintain Organizational Model

1. For the Manager, set the flag Head of own organizational unit on the Basic data tab page.

2. Save your data.

3. You have to assign the users to the positions via transaction PPOMA_CRM (the users are created via transaction SU01).

4. Save your data.

If you are a U.S. customer, ensure that you create an employee position for your U.S. sales organization.

.3.3.1.5.2 Specifying the Supervisor as Agent for the Workflow Tasks


SAP CRM Role Menu Specifying the Supervisor as Agent for the Workflow Tasks



Transaction code OOCU

SAP Menu CRM Basic Functions SAP Business Workflow Perform Task-Specific Customizing

1. Go to the Application Component Abbreviation CRM-BF-CM and choose Assign Agents.

2. Mark CRM: Approve Blocked Transactions and choose Create Agent Assignment.

3. Select a position for example and assign it to the task.

.3.3.1.5.3 Activating Event Linkage

UseYou have to activate the linkage for the event Credit Check To Be Processed for Workflow WS 10000246.


SAP CRM Role Menu Activating Event Linkage

Transaction code OOCU

SAP Menu CRM Basic Functions SAP Business Workflow Perform Task-Specific Customizing

1. Go to the Application Component Abbreviation CRM-BF-CM .

2. Choose Activate event linking.

3. Activate the workflow WS10000246 by pressing choosing Deactivated. The button will switch to Status Activated.

4. Repeat these steps for the workflows WS10000225 (component CRM-BTX-SLO) and WS10000279 (component CRM-BTX-SLO-QUT).


.3.3.2.1 Checking Definition of Credit Group for Sales Orders


SAP R/3 Role Menu Checking Definition of Credit Group for Sales Orders




IMG path Sales and Distribution Basic Functions Credit Management/Risk Management Credit Management Define Credit Groups

Check if the following data has been maintained. If not, you have to create them.

Field name User action or value

CG 01

Document credit grp Credit Group for Sales Order

.3.3.2.2 Checking Assignment of Credit Group to Order Type


UseCheck if the order type you use is maintained in the credit check.


SAP R/3 Role Menu Checking Assignment of Credit Group to Order Type

Transaction code OVAK

IMG path Sales and Distribution Basic Functions Credit Management/Risk Management Credit Management Assign Sales Documents And Delivery Documents

1. Choose Credit limit check for order types.

2. Select the order type and assign the credit group.

3. In the field Check credit enter D for the automatic credit control.


SaTy e.g. OR

Check credit D

Credit group 01

.3.3.2.3 Checking Definition of Credit Control Area



SAP R/3 Role Menu Checking Definition of Credit Control Area



1. Choose Maintain controlling area.

2. Check if the data for the credit control area has been maintained.

Example


COAR 0001

Name Controlling area 0001

.3.3.2.4 Checking Assignment of Company Code to the Credit Control Area



SAP R/3 Role Menu Checking Assignment of Company Code to the Credit Control Area


IMG path Financial Accounting Accounts receivable and Accounts Payable Credit Management Credit Control Account Assign permitted Credit Control Areas to Company Code

The company code to which the customer belongs must be assigned to the credit control area you use.

Example


Company Code 0001

Credit Control Area 0001

.3.3.2.5 Checking Assignment of Sales Area to the Credit Control Area



SAP R/3 Role Menu Checking Assignment of Sales Area to the Credit Control Area


IMG path Enterprise Structure Assignment Sales and Distribution Assign Sales Area to Credit Control Area



Check if the distribution area is assigned to the credit control area.

Example

SO DChl Dv CCAr

0001 01 01 0001

.3.3.2.6 Checking Definition of Risk Category for Customer



SAP R/3 Role Menu Checking Definition of Risk Category for Customer


IMG path Financial Accounting Accounts receivable and Accounts Payable Credit Management Credit Control Account Define Risk Categories

Check the risk category that you have assigned to your customer.

Example


Risk Category 001

CCAr 0001

.3.3.2.7 Checking Credit Limit Definition for Customer and Risk Category Assignment



SAP R/3 Checking Credit Limit Definition for Customer and Risk Category Assignment

Transaction code FD32

SAP Menu Logistics Sales and Distribution Credit Management Master Data Change



1. Choose the PAYER of the customer and the credit control area, set the flags for Overview, Central data and Status, and press enter.

2. On the Overview screen, check if the risk category has been maintained (for example, Risk category 001). It is shown in the bottom right-hand area under Control.

3. On the Central Data screen, under Current credit limit assigned and Maximum permitted credit limits, check if the credit limit has been maintained.

Example

Field name Value

Current credit limit assignedTotal amount e.g. 1.000.000,00

Largest indiv. limit e.g. 1.000.000,00

(Cred.contr.area) e.g. 0001

Maximum permitted credit limitsTotal amount e.g. 1.000.000,00

Individual limit e.g. 1.000.000,00

Currency Choose currency of credit control area

4. On the Status screen, check if the credit limit has been maintained in the Credit limit data.

5. Save your data.

.3.3.2.8 Checking Definition of Automatic Credit Control


UseThe automatic credit check can target certain aspects during a check and run at different times during order processing. In this menu option, you can define your own credit checks to correspond to your requirements in the area of Credit Management.

You can determine an automatic credit check for any combination of the following:

• Credit control area

• Risk class (classifying attribute for your customers from the viewpoint of credit risk which is maintained in FI Customizing)

• Credit group

It is possible to define a system response for each credit check (for example, warning message). In the case of a warning message, a block can be set in the credit status of a document.




SAP R/3 Role Menu Checking Definition of Automatic Credit Control

Transaction code OVA8

IMG path Sales and Distribution Basic Functions Credit Management/Risk Management Credit Management Define Automatic Credit Control

1. Choose the credit control of the sales orders and go to the details.

2. Make sure that the credit limit check is set according to your requirements.

Example


CCAr 0001

Risk Cat. 001

CG 01

.3.4 Payment Cards

UseThis section shows all the steps necessary to set up the payment card functionality.

Payment card processing allows you to work with payment cards, such as credit cards, which frequently replace other payment methods, and are therefore necessary for many merchants, consumers and banks. They offer merchants a form of risk management because an authorized transaction is a guarantee of payment.

Payment card processing in Customer Relationship Management (CRM) is designed especially for merchants, rather than for consumers or banks.

To process payment cards you must arrange with a clearing house or bank for authorization and settlement services. Depending on your arrangements, and particularly if you work with Internet transactions, a third party may relay the electronic messages between you and the clearing house or bank. In Customizing for payment cards you define how this electronic communication takes place.

Complete processing of payment card transactions created in CRM also involves an online transaction processing (OLTP) system, such as SAP R/3. You create, authorize and change the transactions in CRM, but handle shipping, billing, accounting, and settlement with the clearing house in the OLTP system.


http://help.sap.com/verity_cgi_crm31/35/26c70fafab52b9e10000009b38f974/content.htm


3.4.1 Determining Organizational Unit for Clearing (SAP CRM)

UseAssign the appropriate organizational unit for Clearing (rule 10000153). A combination of this assignment and other factors allows organizational units to process payment card transactions.


SAP CRM Role Menu Determining Organizational Unit for Clearing


IMG path CRM → Basic Functions → Payment Cards → Settings for Authorizations → Determine Organizational Unit for Clearing

1. To maintain the Clearing rule, in the Rule Name field, enter 10000153.

2. Choose Change.

3. Under the Responsibility tab, choose Create Responsibility.

4. In the Create Responsibility dialog box:

• In Object Abbreviation, enter Clearing.

• In Name, enter Clearing.



5. In the Of field, enter the appropriate sales organization.

6. Save your entries, then go back.

7. Select Clearing and select the Insert agent assignment icon.

8. Select Organizational Unit.

9. In the Choose Org. dialog box, choose Enter to pull up a list of available organizational units.

10. Select the appropriate organizational unit and choose Enter.

11. On the Create Relationship dialog box, choose Copy.

12. Save your entries and fill out the appropriate details in the transport request dialog box.

3.4.2 Defining Blocking Reason


SAP CRM role Menu Defining Blocking Reason


IMG path CRM → Basic Functions → Payment Cards →Basic Settings → Maintain Payment Card Blocks

1. Select New entries.

2. Set up one or more blocking reasons.

Field Value

Lock Assign a number to the blocking reason, for example 02.

Description Enter a description of the blocking reason.


3.4.3 Defining Merchant IDs

UseA unique number is issued to a merchant by a clearinghouse. This number identifies the merchant in payment card transactions.

With this function, you define merchant IDs by entering the merchant ID and a short description; such as to which clearing house or card type this ID corresponds.




SAP CRM Role Menu Defining Merchant IDs


IMG path CRM → Basic Functions → Payment Cards → Settings for Authorization → Define Merchant ID

1. Enter a merchant ID and a description for your respective merchants.

Example

Field Value

Merchant ID Y_BP_Sales

Description BP Sales


3.4.4 Assigning Merchant IDs


UseAssign a Merchant ID to Organizational Units and Payment Card types.


SAP CRM Assigning Merchant IDs


IMG path CRM → Basic Functions → Payment Cards → Settings for Authorization → Assign Merchant ID

1. Assign Org Object and Card type to the appropriate merchants.

Field Value

OrgObject Your OrgObject

Card Type For example: MC





The transport request must not be transported because it contains an organizational unit. The Id of this unit may differ in the target system and will cause inconsistencies in this case.

3.4.5 Determining Authorization Module

UseWith this function, you assign a Remote Call Function (RCF) function module and a Remote Function Call (RFC) destination to each merchant ID in the system.

ProcedureTo process payment cards in the CRM system, you must transport the authorization module you use in R/3 into CRM. You may acquire this module from your clearinghouse and modify it for R/3 and CRM, or develop it yourself.

The CRM system includes the function module CCARD_AUTH_SIMULATION. You can use this module to test the authorization process before installing your own authorization module in the CRM system. CCARD_AUTH_SIMULATION is delivered by SAP for authorization testing purposes only.

To carry out the activity, choose one of the following navigation options:

SAP CRM Role Menu Determining Authorization Module


IMG path CRM → Basic Functions → Payment Cards → Settings for Authorization → Determine Authorization Module

1. Enter the authorization module used by your company in the authorization function fields for all merchant IDs.



Authorization Function Your Authorization Function. You can enter the CCARD_AUTH_SIMULATION, which is a simulation used for testing purposes only.

2. Save your entries and fill out the details in the transport request dialog box.

3.4.6 Maintaining the Card Numbers for the Business Partner

UseBefore you can simulate the authorization check during the process of the payment card processing, you have to maintain the card number for the business partner. For the simulation,



there are some example numbers which you can take from the note 513449. In addition, the note explains how the simulation of the payment card check works.


SAP CRM Role Menu Maintaining the card numbers for Business Partner

Transaction code BP

SAP Menu path Master Data → Business Partners → Maintain Business Partner

1. Search the business partner for maintaining the card numbers.

2. Change to the tab Payment Transactions and in the sub screen Payment Card you can maintain the card number for the selected business partner.

The following cards are always authorized:

ID Type Description Card Number

000001 VISA Visa 4111111111111111

000002 MC MasterCard 5100000000000008

The following cards are always rejected:

ID Type Description Card Number

000003 VISA Visa 4200000000000000

000004 MC MasterCard 5200000000000007

3. Save the data.

.3.5 Free Goods

UseIn many sectors of industry it is normal practice to offer free goods upon the sale of a certain amount of a product. This encourages the customer to order large quantities.

The following types of free goods exist:

1. Inclusive bonus quantity: The customer only pays for part of the goods he has ordered. The rest is free. For example, a customer orders ten bottles of champagne, but must only pay for nine bottles.

2. Exclusive bonus quantity: The customer pays for the goods he requires and also receives more goods for free. The materials delivered as free goods do not have to be the same as the goods ordered. For example, a customer orders four coffee machines and receives a free package of coffee.



PrerequisitesIf you need the R/3 condition type (e.g. NA00) for free good in CRM, you have to carry out the initial down of the customizing and check these.

You have to assign the determination procedure for Free Goods.

You have to maintain the condition records in R/3.

3.5.1 Checking the Customizing Download (SAP CRM)


SAP CRM Role Menu Checking the customizing download


IMG path CRM → Basic Functions → Free Goods → Set up Free Goods Procedure

1. Choose Procedure and check whether the following entry exists:

Proc. NR Procedure Src. System

NA0001 Free Goods (SD) A Source: R/3

You can open the procedure and see what kind of condition types contains, for example NA00.

2. Choose Condition Types and check whether the following entry exists:

Condition Type Description Access Sequence

NA00 Free Goods SD NA00

3. Choose Access Sequence and check whether the following entry exists:

Access Sequence Description Source

NA00 Free Goods (SD) A Source: R/3

You can mark the access sequence and choose the folder Access to see the condition table.

4. If these three entries do not exist, the customizing download is not correct. You have to carry this out with the customizing object DNL_CUST_CND_FG and DNL_CUST_FGD.For details see Configuration Guide CRM Replication, section Replication Customizing Objects.

3.5.2 Assigning the Procedure for Free Goods




UseYou activate free goods determination when you assign the using procedure to the sales organization, distribution channel and so on.


SAP CRM Role Menu Assign the procedure for free goods


IMG path CRM → Basic Functions → Free Goods → Set up Free Goods → Assign Procedure

1. If the entry with the using sales organization exits, you only need to assign the procedure in the last field Free Good Determination. If the entry doesn’t exist, you choose the button New Entries and enter for example following data:

Sales Org. Dis. Chan. Div. Doc. Pric. Proc.

Cust. Proc. Free Good Determination

O 50000001 01 01 A NA0001

O 50000001 01 01 A 1 NA0001


3.5.3 Defining Item Category Determination for Free Goods (SAP CRM)


UseFor Free Goods you need the item category TANN. You have to define the Item Category Determination for the used transaction type (for example, TA).


SAP CRM Role Menu Define Item Category Determination for Free Goods


IMG path CRM → Transactions → Basic Settings → Define Item Category Determination

1. Choose New Entries and maintain for example following data:



Trans. Typ Item Cat. Group

Item cat. usage

Main item cat.

Item Catagory

TA NORM (Sales Item)

FREE (Free Goods)

TAN TANN


3.5.4 Maintaining Condition Records for Free Goods (SAP R/3)



SAP R/3 Role Menu Maintaining condition records for free goods

Transaction code VBN1

SAP Menu path Logistics → Sales and Distribution → Master Data → Conditions → Free Goods → Create

1. Enter the condition type, for example NA00 and choose Enter.

2. Enter the relevant condition data for organizational data, customer and material.

Example

Sales Org. Dis. Chan. Customer Valid on Valid to

0001 01 C6100 Today 1 year

Material Name Min Qty From UnitFG Are free good

AddUnitFG Free Goods

CR10010 Amarettini 5 1000 PC 10 PC 1

3. Save the data.

3.5.5 Checking Condition Records in SAP CRM

UseThe condition records maintained in the R/3 system are only automatically replicated into the CRM system if an initial download has been executed before.




SAP CRM Role Menu Checking Condition Records in SAP CRM

Transaction code SE16

1. Enter the table name /1CN/CCFSAP010 and choose Enter.

2. Enter NA00 in field KSCHL_SUPP and choose Execute.

3. If no entries are available the condition records have to be replicated from the R/3 system as described in section Replicating Specific Conditions of the Building Block Configuration Guide CRM Replication.

ResultIf you create a sales order with the business partner, product and the quantities X PC, you will get an item with X-Y PC and a free item with Y PC.

.3.6 Product Determination

UseWithin the framework of order entry, it is possible for you on the one hand to enter a user-defined product description (alternative product ID), and on the other, to automatically replace a product by another (product substitution). This makes entering products faster and more efficient, and you can, for example, support sales promotions.

Prerequisites1. You have set up product determination (or material determination) in SAP R/3, and

downloaded this to CRM.

2. You have assigned the product determination procedure to a transaction type in Customizing.

3.6.1 Checking the Customizing Download (SAP CRM)


SAP CRM Role Menu Checking the customizing download


IMG path CRM → Basic Functions → Product Determination → Set up Product Substitution



1. Choose Procedure and enter Application CRM and Usage PD.

2. Check whether the following entry exists:

List Activation Status Src. System Short Text

A00001 Entry was activated A Source: R/3 Material Determination

You can open the procedure and see what kind of condition types contains, for example A001.

3. Choose Condition Types and check whether the following entry exists:

Condition Type Description Access Sequence

A001 Material Entered A001

4. Choose Access Sequence and check whether the following entry exists:

Access Sequence Description Source

A001 Material Entered A Source: R/3

You can mark the access sequence and choose the folder Access to see the condition table.

5. If these three entries do not exist, the customizing download is not correct. You have to carry this out with the customizing object DNL_CUST_CND_PD and DNL_CUST_PDD.For details see Configuration Guide CRM Replication, section Replication Customizing Objects.

3.6.2 Assigning the Procedure for Product Determination (SAP CRM)


UseIn order to link product substitution to the required business transactions, you have to assign the determination procedure to a transaction type, for example TA.


SAP CRM Role Menu Assign the procedure for Product Determination


IMG path CRM → Transactions → Basics Settings → Define Transaction Types



1. Choose Position and search for the transaction type, for example TA.

2. Choose Details.

3. On the subscreen Product Determination, you have to assign the field Product Substitution Procedure, for example A00001


3.6.3 Checking the Substitution Reasons

UseIn this activity, you check the initial download from SAP R/3 of the substitution reason and you can maintain this.


SAP CRM Role Menu Checking the substitution reasons


IMG path CRM → Basic Functions → Product Determination → Maintain the Substitution Reasons

1. Check the substitution reasons from SAP R/3.R/3 IMG path: Sales and Distribution Basic Functions Material Determination Define Substitution Reasons.

2. If you want to display the substitute product at the header level of the sales transaction, you have to set the flag in the column Display Subst. Prod..

3. Save you entries.

3.6.4 Maintaining Condition Records

UseHere, you have to define which product to replace with the other product. This step you have to carry out with the maintenance of condition records for product substitution in SAP R/3.


SAP R/3 Role Menu Maintaining condition records

Transaction code VB11

SAP Menu path Logistics → Sales and Distribution → Master Data → Products → Material Determination → Create



1. Enter the condition type, for example A001 and choose Enter.

2. Enter the validity data and the condition info:

Example

Valid on Valid to Proposed reason

Today 1 year e0002

MatEntered Name Material Description Reason

C10010 Mini-Cookies CR10010 Amarettini 0002

3. Save the data.

ResultIf you create the sales order with the product (Entered Product), the system replaces this with the other one (Replaced product).

3.6.5 Checking Condition Records in SAP CRM

UseThe condition records maintained in the R/3 system are only automatically replicated into the CRM system if an initial download has been executed before.


SAP CRM Role Menu Checking Condition Records in SAP CRM

Transaction code SE16

1. Enter the table name /1CN/CCRSAP001 and choose Enter.

2. Enter A001 in field KSCHL_SUPP and choose Execute.

3. If no entries are available, the condition records have to be replicated from the R/3 system as described in section Replicating Specific Conditions of the Building Block Configuration Guide CRM Replication.

.3.7 Variant Configuration

UseThis section describes how to get Variant Configuration running in a CRM system.

For further information about Variant Configuration check the help.sap.com documentation.

Functional Documentation for SCE:



Help Portal (help.sap.com): mySAP Business Suite --> mySAP CRM --> Application Services --> Application Engines --> Product Configuration

Comparison of SCE (Sales Configuration Engine ) in CRM and Variant Configuration in R/3:

Help Portal (help.sap.com): mySAP Business Suite --> mySAP CRM --> Application Services --> Application Engines --> Product Configuration --> Master Data for Product Configuration --> Using SAP R/3 Master Data --> Comparison of SCE and R/3 Variant Configuration


UseTo be able to use your R/3 master data in the product configuration with the IPC, you must prepare it in the R/3 system in a way that it can be used by the IPC. You combine the entire master data knowledge required for the sales configuration into one unit – a knowledge base.

To do this, you must create knowledge-base objects and knowledge-base runtime versions for your master data in your R/3 system.

.3.7.1.1 Creating Knowledge-Base Objects in R/3


UseA knowledge-base object is a Container for distributing configuration-relevant master data from the R/3 System to the IPC sales configurator knowledge base.

A knowledge-base object determines which objects are downloaded for produce configuration with IPC. Different runtime versions support versioning of the R/3 database for the knowledge base.

A knowledge base object in the R/3 System contains:

• Basic data, such as name, description, and status

• Language-dependent descriptions

• One or more knowledge-base profiles


R/3 Creating Knowledge Base Objects

Transaction code CU31

SAP Menu Logistics -> Central Functions -> Variant Configuration -> Knowledge Base -> Knowledge Base Object -> Create

1. Enter a name in the Knowledge-base object field, for example KB_BEST_PRACTICES.

2. Choose Enter.

3. On the Create Knowledge Base Object screen, enter a description and a status.



You can only replicate a runtime version that has status Released.

3. Choose Profiles.

4. Choose Create and enter for example KB_PROFILE_BP as KB profile and KB Profile Best Practices as description.

5. Choose Enter.

6. Enter the material or class from which you want to start configuration as the OO class, and enter the variant class type.

7. If you do not enter a user interface, the SCE appears with its standard interface and groups characteristics according to the interface design settings defined in R/3.

The User interface field is a reference point for interfacing to customer-specific programs. You can refer to this field in your program to link a customer-specific user interface to a knowledge base.

6. Choose Save.

Result

The knowledge base object is now defined. Before you can download the knowledge base, you must create a runtime version.

.3.7.1.2 Creating Runtime Versions in R/3


Use

The runtime version is a replicable copy of all the configuration-relevant master data of a knowledge-base object that is valid on a specified date. The runtime version thus fulfills a versioning function.

It ensures that each object is downloaded only once, even if:

• It occurs in different places in the configuration model

• You have defined more than one knowledge-base profile


R/3 Creating Runtime Versions

Transaction code CU34

SAP Menu Logistics → Central Functions → Variant Configuration → Knowledge Base → Runtime Versions → Create

1. In the knowledge-base object field enter the name of your knowledge-base object

2. In the Version field enter the name for your runtime version and confirm.

3. On the Create Runtime Version: Basic Data screen, enter the following data:



Fieldname value description

Valid from <date> default is today's date

Status 1 Released

Plant <numeric key for your plant>

BOM application

<key for the application for selecting your BOM>

Language key <blank> We advise you to leave the Language key blank.

Incl. Actions (converted to procedures)

If you use actions for either configuration profiles or BOM items in the SCE, select Incl. actions (converted to procedures).

You can only download a runtime version that has status Released.

If you leave the field Language key blank, descriptions are downloaded in all languages. Missing descriptions can cause errors!

Only actions for configuration profiles and BOM items are converted to procedures Actions for characteristics and characteristic values are ignored!

4. Choose Save.

5. Generate the runtime version

Result

The program collects and compiles all the relevant objects, checks the class network for consistency, and saves the runtime version. The runtime version is now ready to download

For detailed information about the generation of a runtime version, display the R/3 application log. To do this, start transaction SLG1, then enter log object PPVA and sub-object KBMT.




.3.7.2.1 Maintaining Number Ranges for Configurable Products

UseYou have to maintain the number ranges for the configurable products before you replicate the configuration relevant master data.

ProcedureTo carry out the activity, choose the following navigation option:

CRM Maintaining Number Ranges

Transaction code SNRO

1. In the Object field enter or select the value IB_SYM_ID.

2. Choose Change.

3. On the Number Range objects: Change screen choose Number Ranges.

4. In the IB Numerical identifier for a symbol screen choose Change intervals.

5. Choose Insert interval.

6. Maintain the following values.

Number From number To number

01 000000000001

000009999999

7. Choose Save.

Through this activity SAP Note 204346 Short dump NESTED_PERFORM_ON_COMMIT when saving is covered.

ResultYou have maintained the number ranges for the configurable products.

.3.7.2.2 Replicating Customizing Objects

UseThe following objects are relevant to the download from R/3 OLTP to the CRM system.

Object Name Description

DNL_CUST_SCE SCE varcond

DNL_CUST_TAX Customizing: Taxes

DNL_CUST_PROD* Complete Product Customizing




SAP CRM Replicating Customizing Objects

Transaction code R3AS

SAP Menu Architecture and Technology Middleware Data Exchange Initial Load Start

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

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

4. Choose Execute.

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

Go to the Replication Guide section Monitoring Replication Status, if problems occur.



.3.7.2.3 Selecting Knowledge-Base Objects for Replication

UseYou can specify a filter for the knowledge-base objects to be downloaded from R/3 to SAP CRM System. If you don’t specify a filter for your knowledge-base objects all in SAP R/3 available knowledge-base objects are downloaded to the SAP CRM System.


CRM Selecting Knowledge-Base Objects for Replication

Transaction code R3AC1

SAP Menu Middleware → Data Exchange → Object Management → Business Objects

1. Ensure that you are in change mode. Choose Display <->Change (Ctrl+F1).

2. Set the filter for the business object SCE by clicking on the filter symbol.

3. In the screen enter data as described in the following table:


Source side O The side name configured in the previous installation process

Table/structure S

Field K You can either choose KBOBJNAME or KBID. KBID is the internal number for the knowledge-base object, which is difficult to find out. We recommend to work with KBOBJNAME, which is identical to the Name of your knowledge-base object name in your SAP R/3 System

OP Possible entries, to filter the business objects:

Equality (= Low)Inequality (<> Low)Between low and high value (Low <= x <= High)Less than lower or bigger than higher boundContains PatternDoesn't contain patternLess than (< Low)Less or equal than (<= Low)Greater than (> Low)Greater or equal than (>=Low)

Low < Specify your entry in dependency to the selected operator

High < Specify your entry in dependency to the selected operator

Incl./Excl. Possible entries

Inclusive defined set/arrayExclusive defined set/array




Inactive Do not select to set your filter

4. Choose Generate General Filter.

5. Choose Save.

.3.7.2.4 Replicating Knowledge-Base Objects

PrerequisitesThe knowledge-base objects and the runtime version for your knowledge-base objects have been created and successfully generated.

ProcedureTo replicate the knowledge base objects for replication into the CRM System, run the activity:

CRM Replicating Knowledge-Base Objects


SAP Menu Middleware Data Exchange Initial Load Start

1. In the Load Object field enter SCE.

2. In the Name of Source Site (Sender) field specify the site for your R/3 Backend System.

3. To run the replication choose Execute.

Result The knowledge-base object has been downloaded and is available for further processing. Now you can process your configurable products like other products in your CRM. For example you can use them in your product catalog for your Web Shop.

Please make sure that the condition records for the object DNL_COND_A057 have been downloaded successfully. If you haven’t done the download yet, please refer to the relevant chapter of your Installation Guide to load the conditions from your SAP R/3 System to your SAP CRM System

For information concerning further processing of products, please refer to the relevant section in your Installation Guide.

.3.7.2.5 Replicating Configurable Products


SAP CRM Replicating Configurable Products


SAP Menu Architecture and Technology Middleware Data Exchange Initial Load Start



2. In the Load Object field, enter MATERIAL.

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

4. Choose Execute (F8).

.3.7.2.6 Replicating Single Condition Tables

UseThe condition tables for the configurable products must be downloaded. Identify the condition tables which you use for your configurable products.

Object Name (for example) Description

DNL_COND_A304

DNL_COND_A305

DNL_COND_A057


SAP CRM Replicating Single Condition Tables


SAP Menu Middleware Data Exchange Initial Load Start

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

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

4. Choose Execute.

5. Repeat this step for other required objects.

.3.8 US TaxesIn the United States, tax on sales and purchases is known as sales and use tax. Sales and use tax is levied on the sale of tangible personal property and is imposed by tax authorities on transactions.

Most states in the United States impose a sales tax on sales of goods. As a general rule, the consumer bears the tax and the vendor merely acts as a collector for the jurisdiction. Most jurisdictions that impose sales tax also impose a complimentary use on the use or consumption of goods originating from another state. Transactions are generally subject to sales or use tax, but not both, and payment is generally self-imposed by the buyer or seller.

Sales tax is levied on the sale of taxable goods and is imposed by the tax authorities on transactions that occur within a state. No sales tax is imposed for transactions originating outside the state when the seller is not present in that state. If you are a seller in an intrastate transaction, you must collect and remit sales tax to the tax authorities. If you are a purchaser in



an intrastate transaction, the vendor must collect sales tax from you and remit it to the tax authorities.

Use tax is a tax imposed on the purchaser of sales originating from another state. The purchaser, not the seller, is liable to accrue and pay the use tax in the jurisdiction where the goods and services are consumed. Generally, there is an exemption from use tax for goods purchased for resale or production materials. If you purchase and consume goods from another state, the vendor does not charge tax on the invoice. Therefore, you are required to remit use tax to your local tax authority. If you sell goods to a purchaser in another state, you do not charge sales tax. The purchaser is liable to remit use tax to the tax authority where the goods are consumed.

3.8.1 U.S.: Methods of Determining US and Canadian Taxes in R/3

SAP offers the following standard methods of determining US & Canadian Sales & Use Taxes in the R/3 backend:

• Internal Tax calculation is performed in R/3 and tax rates are based on jurisdiction codes defined by the R/3 user. That means that these codes actually have to be entered and maintained manually for all the jurisdictions.

• External Standard SAP Sales & Use Tax Interface System to 3rd party tax packages. Tax calculation and reporting is performed by an external system. The 3rd party system calculates the taxes based on its own jurisdiction codes and then communicates the percentages back to the R/3 system.

3.8.2 U.S.: Why External Taxes Are Needed for Tax Determination in CRM

Internal Tax Determination does not work in the CRM system because the settings residing in the R/3 FI tables that are required to determine jurisdiction codes in R/3 are not available in the CRM system. Only the SD condition types are downloaded to the CRM system.

3.8.3 U.S.: Tax Determination Using Third-Party Software by Vertex

Quantum and eQuantum by Vertex are third-party products, external to mySAP.com, that calculate and report taxes on sales and purchases. If you are in the United States, you need to install an external tax package to be able to determine taxes in CRM Internet Sales and CRM Field Sales.

There are two products that Quantum by Vertex delivers:

• Quantam

• EQSUT (eQuantum)

Quantum is the traditional product to determine taxes in an ABAP based environment such as R/3 or CRM. R/3 has a sales tax application-programming interface (API), which defines how to communicate with an external tax system. The Translink application needs to be installed on each application server to properly communicate via RFC calls.

The external tax-interface is called through the API:



• During address maintenance to retrieve the appropriate tax jurisdiction code for customer, vendor, cost center, plant, and company code address.

• During order and invoice processing out of SD to retrieve tax amounts and/or determine exemptions

• During the execution of the SAP update utility program, which updates Quantum by Vertex’s audit files with the appropriate tax information.

EQSUT (eQuantum) is used to determine taxes in a Java environment such as the IPC (Internet Pricing Configurator) and needs to be installed on the same machine as the IPC and the mobile sales clients. Delivered with EQSUT is a software component called Quantum SAP CRM Integration (QSCI) that integrates the QSUT with the SAP Markets Internet Sales and the mySAP CRM Mobile Sales application.

3.8.4 U.S.: Connecting and Activating External Tax Software

.3.8.4.1 U.S.: Connecting CRM to Vertex

.3.8.4.1.1 U.S.: Defining Physical Destination

ProcedureSAP CRM Defining Physical Destination

Transaction code SM59

IMG Path CRM → Basic Functions → Taxes → External Tax Calculation

1. Choose Create.

2. In RFC destination, enter transaction VERTEX_MAXTAX

3. In Connection Type, enter T.

4. In description, enter a description.

5. Choose Enter.

6. In Program, enter the exact location of the file verrfc on the Quantum by Vertex server.

7. Select start on Explicit host.

8. In Target Host, enter the Quantum by Vertex server name.

9. In Gateway host, enter the qualified name of the Quantum by Vertex server or the ip address.

10. In Gateway Service, enter the appropriate gateway service.

11. Choose Save on the initial screen (not shown here) and then choose Test Connection (still on initial screen and not shown).

12. A successful test is expected.



3.8.5 U.S.: Assigning Pricing Procedure to US Sales Organization

ProcedureSAP CRM Determine Pricing Procedures


IMG Path CRM → Basic Functions → Pricing → Pricing in the Business Transaction → Determine Pricing Procedure

Ensure that your US Sales Organization is assigned to your pricing procedure.
