You are on page 1of 40

SAP CRM 2007

March 2009
English

CRM Organizational Model
(C01)
Building Block Configuration Guide

SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany

SAP Best Practices

CRM Organizational Model (C01): Configuration Guide

Copyright
© Copyright 2009 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, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft
Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390,
OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x,
System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS,
POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of
IBM Corporation.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks
of Adobe Systems Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks
or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web
Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology
invented and implemented by Netscape.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, and other SAP
products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP AG in Germany and in several other countries all over the world. All other product
and service names mentioned are the trademarks of their respective companies. Data contained in this
document serves informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its
affiliated companies ("SAP Group") for informational purposes only, without representation or warranty
of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The
only warranties for SAP Group products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as
constituting an additional warranty.

© SAP AG

Page 2 of 40

SAP Best Practices

CRM Organizational Model (C01): Configuration Guide

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.

© SAP AG

Page 3 of 40

SAP Best Practices

CRM Organizational Model (C01): Configuration Guide

Contents
Configuration Guide.................................................................................................................. 6
1

Purpose.......................................................................................................................... 6

2

Preparation..................................................................................................................... 6

3

2.1

Prerequisites............................................................................................................ 6

2.2

SAP Notes............................................................................................................... 6

Configuration.................................................................................................................. 7
3.1

Organizational Model Overview...............................................................................7

3.2

Organizational Model Synchronization ERP <-> CRM.............................................8

3.2.1

Checking Sales Organization (SAP ERP).......................................................8

3.2.2

Checking Distribution Channels (SAP ERP)...................................................9

3.2.3

Checking Divisions (SAP ERP).......................................................................9

3.2.4

Checking Sales Areas (SAP ERP)..................................................................9

3.2.5

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

3.2.6

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

3.2.7

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

3.2.8

Checking Assignment Division  Sales Organization (SAP ERP)................10

3.3

Maintain Organizational Data for Marketing and Sales Scenarios.........................11

3.3.1

Performing Division Settings (SAP CRM)......................................................11

3.3.2

Defining Divisions..........................................................................................11

3.3.3

Defining Distribution Channels......................................................................12

3.3.4

Defining Combination of Distribution Channel and Division..........................13

3.4

Set Up Integration Business Partner – Organizational Management.....................13

3.4.1

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

3.4.2

Defining Grouping for Org Business Partners (SAP CRM)............................14

3.4.3

Setting Up Integration...................................................................................15

3.4.4

Executing Report for Changeover Classification...........................................16

3.5

Maintaining Organizational Units...........................................................................16

3.5.1

Creating an Organizational Model (SAP CRM).............................................17

3.5.2

Creating Organizational Units.......................................................................18

3.5.3

Assigning Attributes to Organizational Unit...................................................19

3.5.4

Matching Sales Organization........................................................................21

3.5.5

Matching Sales Offices..................................................................................22

3.5.6

Matching Service Organization.....................................................................22

3.6

Maintaining Positions for the Organizational Units................................................23

3.7

Maintain Holder for Positions.................................................................................24

3.7.1

Defining Number Ranges for Employees......................................................24

3.7.2

Defining Grouping for Employees.................................................................25

3.7.3

Creating Employees (SAP CRM)..................................................................25

© SAP AG

Page 4 of 40

.............38 3.................................4 Assigning Company Code to Billing Unit......27 Translate Organizational Model.1 © SAP AG CRM WebClient UI Settings.9................39 Assigning Business Roles to Positions.........35 3.......... 30 3............6 Assigning Plant and Storage Location to Service Organization...............................5 Assigning Business Area to Service and Sales Organization.....................11.............................12...........................................11..........................................................................12..............13...29 3...................................SAP Best Practices 3..39 3.................................................11 Set Up Buffering for Sales Scenario..........12.8 CRM Organizational Model (C01): Configuration Guide Assigning Employees to Positions...................................................1 Creating System Users (SAP ERP)..2 Translate Positions...........37 3.........36 3...........12 Organizational Units Assignment..............................10...35 3.........10..........................1 Enable Buffering for Sales Scenario..13 3................................................31 3......7..............10.................39 Page 5 of 40 ................12.............1 Creating a Billing Unit..2 Checking Settings for Attribute Maintenance..................................................................................32 3.......................36 3.........................................34 3..33 3.........................................29 3..................4 3..............................31 3..................................................................3 Checking Organizational Data Settings..8.................................2 Assigning Billing Unit to Sales Organization.................9....................................................1 Translate Organizational Units..8..........34 3..33 3.....................2 Assigning Role to System Users (SAP ERP)....3 Assigning Billing Unit to Service and Sales Organization...............1 Updating List of Organizational Units........12..................................................................33 3.......................9 Integration of System Users and Employees ERP <-> CRM.................................................12.............................34 3............33 3.................10 Checking Organizational Structure.......................2 Update Buffers for Sales Scenario......

read the relevant SAP Notes. SAP Note Area Title CRM System There are no additional SAP Notes relevant for this building block.1 Prerequisites Before starting with the installation of this building block. © SAP AG Page 6 of 40 . These SAP Notes contain important information for installation and configuration.SAP Best Practices CRM Organizational Model (C01): Configuration Guide Configuration Guide 1 Purpose This configuration guide provides the information you need to set up the configuration of this building block manually. Make sure that you have the most up-to-date version of SAP Notes.2 SAP Notes Before you begin the installation and configuration.2.com/notes). . please see the document Quick Guide to Installing SAP Best Practices for CRM.2.sap. and also corrections concerning this building block. 2 Preparation . You can find the SAP Notes on the SAP Service Marketplace (http://service.

You can maintain the company structure including the positions and employees in an application and assign specific data (attributes) to the organizational units. Employees are assigned to these positions as holders. A synchronization of the organizational structure for sales and service in ERP and CRM is possible via mapping of organizational units.SAP Best Practices 3 CRM Organizational Model (C01): Configuration Guide Configuration . The organizational model can be initially created automatically based on the sales organizational structure in ERP. and conditions) in CRM. If you use ERP as a back-end system in CRM. © SAP AG Page 7 of 40 . partner determinations and evaluations are based on this structure. It consists of separate organizational units for marketing. you need the sales structure from the SAP ERP system in order to transfer or create master data (for example.3. In the following a sample organizational structure will be defined. These sample organizational structure is essential for all SAP Best Practices scenarios because organizational data determination. functional organizational structure as a current organizational model. This is a prerequisite for a master data and transactional data integration between ERP and CRM. 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.1 Organizational Model Overview Organizational Management in CRM offers you a flexible tool for handling your company’s task-related. The organization model will be especially used for organizational data determination within the CRM scenarios for marketing. Compared to ERP the organizational model in CRM is more comprehensive. For details about setting up an organizational structure please see the CRM standard documentation. sales and service. sales and service. business partner. products. flexible and dynamic.

Errors may occur in organizational data determination if there are already organizational units in the system.1 Checking Sales Organization (SAP ERP) Please check the Delta Guide. in case of deviations from this sample model all pre-defined setting for organizational data determination etc. © SAP AG Page 8 of 40 . i.3. A sales area consists of:  a sales organization  distribution channels  divisions The sales areas and related data are downloaded from ERP to CRM. Decide which sales areas you need to have in the CRM system. and check them in the ERP system. Identify your required Sales Organizations. check sales organization 2. such as Activity Management.2 Organizational Model Synchronization ERP <-> CRM Please check the Delta Guide. SAP Best Practices customizing settings are based on the sample organizational model. delete. copy. Further changes in the organizational model have to be maintained manually in the CRM system anyway. Access the activity using one of the following navigation options: Transaction code OVX5 SAP ERP IMG menu Enterprise Structure  Definition  Sales and Distribution  Define. Please skip these sections if you use CRM as a standalone system. Procedure 1. such as the organizational model. The two systems have to be synchronized in some configuration areas.e.SAP Best Practices CRM Organizational Model (C01): Configuration Guide 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. Opportunity Management  An automatic transfer of the ERP sales structure is only possible once.2. 3. Use The ERP system is closely linked to the CRM system. . will not work.

Identify the required Distribution Channels.2. delete. Procedure 1.SAP Best Practices 3.General  Define.5 Checking Assignment of Sales Offices to Sales Areas (SAP ERP) Please check the Delta Guide. delete. check division 2. Identify your required Divisions. 3. Procedure 1. 3.2.2 CRM Organizational Model (C01): Configuration Guide Checking Distribution Channels (SAP ERP) Please check the Delta Guide.2.2. Procedure 1. Access the activity using one of the following navigation options: Transaction code OVXB SAP ERP IMG menu Enterprise Structure  Definition  Logistics . copy. Procedure 1.3 Checking Divisions (SAP ERP) Please check the Delta Guide. Identify your required Sales Areas. Access the activity using one of the following navigation options: Transaction code OVXI SAP ERP IMG menu Enterprise Structure  Definition  Sales and Distribution  Define. 3. check distribution channel 2.4 Checking Sales Areas (SAP ERP) Please check the Delta Guide. copy. Access the activity using one of the following navigation options: © SAP AG Page 9 of 40 . 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 2.

7 Checking Assignment Distribution Channel -> Sales Org. Procedure 1.2. (SAP ERP) Please check the Delta Guide. 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 2.8 Checking Assignment Division  Sales Organization (SAP ERP) Please check the Delta Guide. Identify your required assignments for CRM. 3. 3.SAP Best Practices CRM Organizational Model (C01): Configuration Guide Transaction code SPRO SAP ERP IMG menu Enterprise Structure  Assignment  Sales and Distribution  Assign sales office to sales area 2. 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 2. Access the activity using one of the following navigation options: Transaction code OVXA SAP ERP IMG menu Enterprise Structure  Assignment  Sales and Distribution © SAP AG Page 10 of 40 .2.2. Procedure 1.6 Checking Assignment Company Code -> Sales Organization (SAP ERP) Please check the Delta Guide. Identify your required assignments for CRM. Identify your required Sales Offices for the selected sales area. 3.

Enter an R/3 dummy division for the list of SAP ERP divisions identified in step Checking Divisions (SAP ERP).SAP Best Practices CRM Organizational Model (C01): Configuration Guide  Assign division to sales organization 2. If you use CRM together with an ERP system. if you are not using a header division in CRM. you can define divisions for CRM in addition to those copied from the ERP system. 3.3 Maintain Organizational Data for Marketing and Sales Scenarios 3. Deselect the checkbox Division not act. Use You can specify whether or not you work with divisions in the CRM system.3. Use In this step.2 Defining Divisions Please check the Delta Guide. Identify your required assignments for CRM. 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. in order that you can exchange data (master data and documents) between systems. if you wish to use divisions at header level in business transactions in CRM Enterprise. © SAP AG Page 11 of 40 . Act. 3. 4. you must always maintain a dummy division in ERP. Select the indicator Header Div.3. .3.1 Performing Division Settings (SAP CRM) Please check the Delta Guide. 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.

where no ERP integration is implemented. Enter 1 – 3 distribution channels with ID and description according to the distribution channels in your ERP system. Use In this step. 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.3 Defining Distribution Channels Please check the Delta Guide. 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. 3. Choose New Entries (F5).3. Save your entries. but for the SAP Best Practices scenarios only the first entry will be used. 3.3. © SAP AG Page 12 of 40 . You can enter additional divisions. Choose New Entries (F5). 3. Otherwise the divisions have been copied automatically from ERP into CRM via the initial data replication. Enter the ID and description of your central ERP division in case the division has not been replicated from the ERP. you can define distribution channels for CRM. Procedure 1. Procedure 1. 5.4 Defining Combination of Distribution Channel and Division Please check the Delta Guide. 4. 4. 3. Save your entries.SAP Best Practices CRM Organizational Model (C01): Configuration Guide You normally have to maintain divisions manually only if you use a CRM standalone system.

The system uses the Organizational Unit role for the business partners it creates from organizational units. Otherwise problems may occur when replicating business partners from the ERP into the CRM system. Choose New Entries (F5). the system must create business partners from these organizational units. . 3. Enter possible combinations of distribution channels and divisions according to your sales areas in the ERP system and your settings in the preceding activities. Procedure 1. For this business partners a number range has to be created. Save your entries.3. 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 2.g. Make sure that this number range is not used in the ERP for business partners. If you don’t define a number range the created business partner will get a number that belongs to other business partner types.4 Set Up Integration Business Partner – Organizational Management Use For you to use your existing organizational units in orders. Procedure 1. 3. 4. e. you can define combinations of distribution channels and divisions that can be assigned as attributes to the sales organization to define a sales area.1 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. 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 © SAP AG Page 13 of 40 . consumers.4.SAP Best Practices CRM Organizational Model (C01): Configuration Guide Use In this step.

a.2 Defining Grouping for Org Business Partners (SAP CRM) Use For each organizational unit created in the organizational model a business partner is generated automatically. Business partners are already created for a number range. Current number Ext Internal number assignment is required. 9. Confirm the information window Transport number range intervals with Continue (Enter). This grouping can be used for selecting the number range when creating a business partner. In the next steps you define the number range for Org business partners. Choose Change intervals.SAP Best Practices CRM Organizational Model (C01): Configuration Guide 2. b. 3. Choose Insert (Enter). 4. 3. 5.4. © SAP AG Page 14 of 40 . Enter the following values: Field Value Remarks No. Before creating new number range intervals you have to delete the SAP default number ranges. No business partners have been created for the number range. The number range that was created in the section Defining Number Range for Org Business Partners (SAP CRM) has to be assigned to a grouping. Choose Insert interval (Shift+F1). 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. Procedure 1. 8. 6. To number 0004999999 If you use numeric values make sure you add leading zeroes to the value until the full length of the field is reached. Choose Save (Ctrl+S). 7. Choose New Entries (F5). 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. In this case the value of field Current number is higher than 0 and a deletion of the number range is not possible. Set the upper limit of the number range (field To number) to the value of field Current number. In this case select the number range and choose Delete interval (Shift+F2).

Procedure 1. 6.Std.abbr. Choose Enter. 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.Std Grping Deselected Please make sure that the ID of the grouping is identical with the ID of the assigned number range.3 Setting Up Integration Use Activate the integration of organizational units and business partners and assign the number range defined in the preceding sections. Choose Save (Ctrl+S). Int. 3. Enter the following values: Field Value Remarks Grouping Y4 The grouping must have the same ID as the assigned number range Short name Org BP Description (EN) Business Partner for Org Units Description (DE) Geschäftspartner für Org Einheiten Number range Y4 External The number range you have created for Org Business Partners.SAP Best Practices CRM Organizational Model (C01): Configuration Guide 3.Grping Selected Ext.: © SAP AG Page 15 of 40 . 4. Internal number assignment is required. 5.4. Select a customizing request. Enter the following values for the existing combination of Group and Sem.

5. Value abbr Description HRALX HRAC X Activate HR Integration HRALX OBPON ON Integration O-BP Activated HRALX ONUMB 2 Business Partner Number Assignment (Org. Keep the default values and choose Execute (F8). You can assign attributes to a sales © SAP AG Page 16 of 40 . read the documentation of the report and run the report with deactivated flag for Testmode.4. Depending on how task distribution is organized in a company.abbr. This report has to be executed once even in case of a new installed CRM system.3. sales and service will be defined. It is not possible. To run the report. Sales transactions are prepared and implemented in a sales organization. The organizational unit in sales and distribution structures the company according to SD requirements. Enter the report CRM_MKTBP_ZCACL_UPDATE_30 and choose Execute (F8). . In case of the status message Class Type BUP: No Suitable Classes Found no further actions are required. 3. Choose Save (Ctrl+S). use the following navigation option: Transaction code SA38 2. Procedure 1. Separate organizational units for marketing. It has to be executed at this time because otherwise the business partners which are related to the organizational units are not created correctly.SAP Best Practices CRM Organizational Model (C01): Configuration Guide Group Sem. Several sales offices or sales groups or other freely definable organizational units can be assigned at lower level than the sales organization.4 Executing Report for Changeover Classification Use A report has to be executed to changeover the customer classification from former CRM releases. these can be. however. for other sales organizations to be subordinate to a sales organization. Otherwise error messages during business partner processing will occur.5 Maintaining Organizational Units Use Organizational units are functional units of a company. groups or project teams. departments. for example. In case of other messages. 3. 4. Unit) HRALX OSUBG Y4 Business Partner Subgroup (Organizational Unit)  Number Range 3.

By inheriting the attribute Service organization. Access the Organizational Model using the following navigation: SAP CRM WebClient menu Master Data  Organization Model 2. for example. the responsible service organizations.1 Creating an Organizational Model (SAP CRM) Please check the Delta Guide. Log on to the CRM WebClient with the user POWER_USER. 3. to which you can assign subordinate organizational units. Maintain the following values for this organizational unit:: Field name Value General data Code BP_COMP Description BP Company Address Street/House No. Procedure 1. 4. This attribute flags an organizational unit as a responsible organizational unit in the service area. Use An organization model is created initially together with a root organizational unit which builds the basic node for all other organizational units. the system identifies the subordinate organizational units implicitly as organizational units for the service area. Enter values City Enter values Postal Code Enter values Country <Country> Attributes Country © SAP AG <Country> Page 17 of 40 . For CRM service there is the attribute Service organization. In addition there are organizational unit in the service area in which services are planned and prepared. or a postal code. The sales organization is then responsible for these attributes. a language. Choose Continue. report to the service organization. which you set in organizational model maintenance on the Function tab page. Create a root organizational unit by choosing Root Organizational Unit. one or more divisions and distribution channels.5. 3.SAP Best Practices CRM Organizational Model (C01): Configuration Guide organization in organizational plan maintenance. This means that the organizational unit is flagged as a superordinate organizational unit in the service area. Subordinate organizational units.

Access the activity using one the following navigation: SAP CRM WebClient menu Master Data  Organization Model 2. Enter the description of the organizational unit. In the view area Result List. select the link of the root organizational unit BP Company. 3. 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. choose the button ‘Personalize’.2 Creating Organizational Units Please check the Delta Guide. To display this ID. Choose Save. Run the following steps to create the following SAP Best Practices organizational structure as an example to work with: Description Hierarchy Code Level SAP Best Practice Company 0 BP_COMP BP Marketing Organization 1 BP_MARKET Marketing Organization BP Sales Organization 1 BP_SALES Sales Organization 2 BP_SLS 3 BP_SO_CENTER BP Sales Call Center 2 BP_IC_SAL BP Service Organization 1 BP_SERVICE BP Service Back Office 2 BP_SRV BP Service Technicians Group 2 BP_TECH BP Service Call Center 2 BP_IC_SRV BP Service IC Support 2 BP_IC_SUP BP Direct Sales BP Sales Office Central © SAP AG Functions Sales Office Service Organization Service Team Page 18 of 40 . In the assignment block Organizational Unit select the root organization BP Company and choose the button Organizational Unit to create a new organizational unit on the level below. Procedure 1. 5.SAP Best Practices CRM Organizational Model (C01): Configuration Guide Please use ID BP_COMP and do not change this ID until the complete organizational model has been maintained. An ID will be automatically created for the root organization. Prerequisites The root node BP_COMP has already been created as described in the preceding section. move ‘ID’ from the Available Columns to the Displayed Columns and Save. 3. that has been created in the preceding section (BP Company) and choose Search. 6. This object has already been created in the preceding section. 4.5.

when creating your sales and distribution or service structure. you can also enter areas (for example. for example. You always maintain these attributes specifically for a scenario (Sales or Service). Otherwise problems may occur during the organizational data determination. In view area Functions check the corresponding function (for example.5. The following organizational units are available in CRM for which you can enter the corresponding organizational unit in the ERP system. for example. Procedure 1. in particular. Choose Back twice. 10. Access the activity using one of the following navigation options: © SAP AG Page 19 of 40 . Use You can use general attribute maintenance to attribute data (attributes) to organizational units.  business attributes define the responsibility of an organizational unit. 3. 9. 8. the system may not be able to identify organizational units. Check the delta guide for details. enter an address for the organizational unit. whether it is a sales organization or a service group. 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 For SAP Best Practices the sample organizational structure is prepared for the assignment of one single ERP Sales Organization and one single Planning Plant. sales and service scenarios have been created. Result The necessary organizational units for the marketing. Save your entries using the Save button. partner numbers 001 to 300).SAP Best Practices CRM Organizational Model (C01): Configuration Guide The code of organizational units must not contain numbers. BP Sales Organization). Attributes can have one or more values. 7. CRM distinguishes between organizational and business attributes:  organizational attributes define the type of organizational unit.3 Assigning Attributes to Organizational Unit Please check the Delta Guide. Sales Organization) for each organizational unit (for example. In view area Address. for which distribution channels or product groups an organizational unit is responsible. For some attributes.

Organizational Unit Details Organizational Unit ID Functions Allow Org. For the SAP Best Practices organizational model maintain the following attributes. select the link of the root organizational unit BP Company. In the assignment block Organizational Unit select the organizational unit. Most of the values can not be pre-defined because they are depending on the country or on the individual organizational structure. currency for document <PV> Correspondence Language <PV> Country <PV> Correspondence Language <PV> Sales Service BP_MARKET © SAP AG All Value Value to Only inherited attribute values Page 20 of 40 . 3. Unit to be Determined of the assignment block Organizational Unit Details. select field if necessary. Unit to be Determined BP_COMP BP_MARKET Marketing Organization BP_SALES Sales Organization BP_SLS BP_SO_CENTER Marketing Sales Sales Office Sales Service Organization Service BP_IC_SAL BP_SERVICE BP_SRV BP_TECH Service Service Team BP_IC_SRV BP_IC_SUP 1. Organizational Unit ID Scenario Attribute BP_COMP Marketing Country <PV> Ref. The entry <PV> indicates that the value has to be personalized according to the project situation. 2. Sales and Service) of an organizational unit if necessary. In order to maintain the attributes select the created organizational units one after another and choose Edit List in the assignment block Attributes. currency for document <PV> Country <PV> Ref. Enter the description BP Company and choose Search.SAP Best Practices CRM Organizational Model (C01): Configuration Guide SAP CRM WebClient menu Master Data  Organization Model 2. In the view Allow Org. Otherwise this organizational unit will not be taken into consideration for the organizational data determination. that you want to maintain 5. 4. Maintain all required attributes for all three scenarios (Marketing. In the view area Result List.

SAP Best Practices CRM Organizational Model (C01): Configuration Guide Organizational Unit ID Scenario Attribute Value BP_SALES Sales Division <PV> Distribution Channel <PV> Postal Code 00000 Tupel (…) <PV> Value to 99999 BP_SLS All Only inherited attribute values BP_SO_CENTER Sales Region BP_IC_SAL All Only inherited attribute values BP_SERVICE Sales Region <PV> Tupel (…) <PV> Division <PV> Distribution Channel <PV> Postal Code 00000 99999 Service Postal Code 00000 99999 BP_SRV All Only inherited attribute values BP_TECH All Only inherited attribute values BP_IC_SRV All Only inherited attribute values BP_IC_SUP All Only inherited attribute values <PV> <PV> 3. Choose Save (Ctrl+S). Maintain the following data using the input help: Field Name Entry Sales Organization ID <ID of CRM Sales Organization> R/3SlsOrg <corresponding ERP Sales Organization> (e. In the assignment block Attributes. 3. 4. Examine the messages for the check results. 1000) 4.4 Matching Sales Organization Procedure 1.5. choose the button Check Consistency for the consistency. 3. Choose Save.. © SAP AG Page 21 of 40 . 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).g.

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 Offices to SAP ECC Sales Offices 2. 3. .6 Maintaining Positions for the Organizational Units Use © SAP AG Page 22 of 40 . 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 Service Organizations to SAP ECC Maintenance Planning Plants 2. Repeat this step for every CRM Sales Office. Choose Save (Ctrl+S). 3. 3. Maintain the following data using the input help: Field Name Entry Sales Office <ID of CRM Sales Office> R/3SlsOffc <corresponding ERP Sales Office> 4.6 Matching Service Organization Procedure 1.5.5 CRM Organizational Model (C01): Configuration Guide Matching Sales Offices Use In case you are using sales offices in SAP ERP and in SAP CRM.5. you have to map these sales offices. Maintain the following data using the input help: Field Name Entry Service Organization <ID of CRM Service Organization> MnPlngPlnt <corresponding ERP Maintenance Planning Plant> 4. Choose New Entries (F5).3. 5.SAP Best Practices 3. Procedure 1. Choose New Entries (F5). Choose Save (Ctrl+S).

Access the activity using the following navigation option: SAP CRM WebClient menu Master Data  Organization Model 2. Choose Save. Examine the messages for the check results. Procedure 1. 4. You can define a head position within an organizational unit. 10. select the link of the root organizational unit BP Company. 11. If you want to create further positions. 7. you have to repeat the steps 3-10. 3. Choose the button Position. Choose the button Edit List and choose Check Consistency. POS_MKT_MGT). 9. to which all other positions in the organizational unit report. Choose Save. Campaign Manager) of the position and the Code (for example.SAP Best Practices CRM Organizational Model (C01): Configuration Guide You assign positions to organizational units. Maintain the following positions: © SAP AG Page 23 of 40 . Enter the description BP Company and choose Search. in doing this. 5. 6. you also determine the tasks assigned to them. if this position is a head of an organizational unit. In the assignment block Organizational Unit select the organizational unit. In the view area Result List. In the assignment block Position Details and the view General Data enter the Description (for example. 8. for which you want to add a Position. Also activate the checkbox. In the area Attributes you will see the inherited Attributes from the organization unit.

7. unit .1 Defining Number Ranges for Employees Use You want to create employees with separate external number ranges in CRM. 3. © SAP AG Page 24 of 40 .3.7 Maintain Holder for Positions Use You assign employees or users to positions. you also determine the tasks assigned to them. in doing this.SAP Best Practices CRM Organizational Model (C01): Configuration Guide Description Code Hierarchy Level Object Type BP Company BP_COMP 0 Org Unit BP_MARKET 1 Org Unit Marketing Manager POS_MKT_MGT 2 Position Marketing Employee POS_MKT_EMP 2 Position BP_SALES 1 Org Unit BP_SLS 2 Org Unit Director of Sales POS_SLS_DIR 3 Position BP Sales Office Central BP_SO_CENTER 3 Org Unit Sales Manager POS_SLS_MAN 4 Position Sales Employee POS_SLS_EMP 4 Position BP_IC_SAL 2 Org Unit IC Manager POS_ICM_SAL 3 Position IC Agent Marketing POS_IC_MKT 3 Position IC Agent Sales POS_IC_SAL 3 Position BP_SERVICE 1 Org Unit Service Manager POS_SRV_MAN 3 Position BP Service Back Office BP_SRV 2 Org Unit POS_SRV_EMP 3 Position BP_TECH 2 Org Unit POS_SRV_TECH 3 Position BP_IC_SRV 2 Org Unit IC Manager POS_ICM_SRV 3 Position IC Agent Service POS_IC_SRV 3 Position BP_IC_SUP 2 Org Unit POS_IC_SUP 3 Position BP Marketing Organization BP Sales Organization BP Direct Sales BP Call Center Sales BP Service Organization Service Employee BP Service Technicians Group Service Technician BP Call Center Service BP IC Support IC Agent Support Head of org.

2 Defining Grouping for Employees Use You want to create employees with the external number ranges in CRM. 4. Choose Save (Ctrl+S). each employee (for example. From number To number Ext Y7 0000010000 0000099999 X 5. sales manager) that will be assigned to an organizational unit at a later stage.7. needs to be created as an Employee. Enter the following values: No. Choose Change intervals. Choose New Entries (F5). 3. 3. 3. Choose Insert interval (Shift+F1). Choose Save (Ctrl+S). 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.3 Creating Employees (SAP CRM) Use As next step.SAP Best Practices CRM Organizational Model (C01): Configuration Guide Procedure 1.7. You have to define the grouping and assign the number range to this grouping. Prerequisites © SAP AG Page 25 of 40 . Grping Int Std. 3. 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. Std. Procedure 1. Grping Deselected Deselected 4. Enter the following values: Grouping Short name Description Number range Y7 CRM Employees CRM Employees Y7 External Ext.

SAP Best Practices CRM Organizational Model (C01): Configuration Guide For each business partner being created here a corresponding system user has already been created in the CRM system (transaction SU01). . Repeat these steps for the following users: ID Employee/Name User 10000 Jennifer Stone SALES_MAN 10010 Michael Curtis SALES_EMPL 10030 Peter Seller SALES_DIR 10100 Angela Lucata IC_MAN 10110 Ann Anderson IC_AGENT_SRV 10120 Peter Best IC_AGENT_SUP 10130 Michelle Dean IC_AGENT_MKT © SAP AG Page 26 of 40 . 4. In assignment block Users choose Add. If assignment block Users is not visible. Procedure 1. Enter the User Name or search by the Input Help and choose Ok. Open the assignment block Users and choose Add. Choose Save. This is described in the Building Block C04 CRM WebClient User Interface in section Adapting Entry Screen for Employees The CRM system users which have to be assigned to the CRM employees have been created in Building Block CRM WebClient User Interface. To create a business partner. Choose Save. choose button Personalize on the top level and move this view from table Available Assignment Blocks to Displayed Assignment Blocks. 6. 5. choose the following navigation option: SAP CRM WebClient menu Master Data  Create: Employee 2. 7. The database field Grouping in the view Employee has to be added in the view as this field is hidden in the SAP CRM standard entry screen. Enter at least the following data in General Data: Field Name Entry General Data ID <business partner number> (see list below) First Name <first name of employee> Last Name <last name of employee> Grouping CRM Employees Nationality <country key for employee’s> 3.

Employees and users have been created. 5. 3.g. Procedure 1. e. 2. In the view area Result List. Mark the Position. Choose Back. Choose Search. Access the activity using the following navigation: SAP CRM WebClient menu Master Data  Organization Model  Search Criteria  Organizational Unit 3. select the link of root organizational unit. 6. In the search criteria area choose Find by Organizational Unit. Search the employee by criteria (last name. 10.7.SAP Best Practices CRM Organizational Model (C01): Configuration Guide ID Employee/Name User 10140 Judie Coltman IC_AGENT_SLS 10200 Ryan Reval SERV_MAN 10210 Barbara Lee SERV_EMPL 10230 Matthew Carter SERV_TECH 10300 Melanie Richard MKT_MAN 10400 Richard Lion MKT_EMPL Result Each employee is created as a business partner with role Employee in the CRM system. Assign the following employees to the positions by performing steps 2 to 8 again: Organizational Unit Position Employee User BP Marketing Organization Marketing Manager Melanie Richard MKT_MAN Marketing Employee Richard Lion MKT_EMPL BP Sales Organization Director of Sales Peter Seller SALES_DIR BP Sales Office Central Sales Manager Jennifer Stone SALES_MAN © SAP AG Page 27 of 40 . Click on Employee.4 Assigning Employees to Positions Prerequisites You have maintained the organization units and the positions (see the two previous sections). Select the business partner. 9. BP Company. 11. 8. In the Organizational Unit view expand the tree to the position you want to assign an employee to. Log on to the CRM WebClient with user power_user and password welcome. Choose Save. 4. 7. user ID).

SAP Best Practices Organizational Unit CRM Organizational Model (C01): Configuration Guide Position Employee User Sales Employee Michael Curtis SALES_EMPL BP Service Organization Service Manager Ryan Reval SERV_MAN BP Sales Call Center IC Manager Angela Lucata IC_MAN IC Agent Marketing Michelle Dean IC_AGENT_MKT IC Agent Sales Judie Coltman IC_AGENT_SLS BP Service Back Office Service Employee Barbara Lee SERV_EMPL BP Service Technicians Group Service Technician Matthew Carter SERV_TECH BP Service Call Center IC Manager Angela Lucata IC_MAN IC Agent Service Ann Anderson IC_AGENT_SRV IC Agent Support Peter Best IC_AGENT_SUP BP IC Support Result: Description Hierarchy Level Object Type SAP Best Practice Company 0 Org Unit BP_COMP BP Marketing Organization 1 Org Unit BP_MARKET Marketing Manager 2 Position POS_MKT_MGT Melanie Richard 3 Holder Marketing Employee 2 Position 3 Holder 1 Org Unit BP_SALES 2 Org Unit BP_SLS Director of Sales 3 Position POS_SLS_DIR Peter Seller 4 Holder 3 Org Unit BP_SO_CENTER 4 Position POS_SLS_MAN Jennifer Stone 5 Holder Sales Employee 4 Position Michael Curtis 5 Holder 2 Org Unit BP_IC_SAL 3 Position POS_ICM_SAL 4 Holder 3 Position 4 Holder 3 Position 4 Holder Richard Lion BP Sales Organization BP Direct Sales BP Sales Office Central Sales Manager BP Sales Call Center IC Manager Angela Lucata IC Agent Marketing Michelle Dean IC Agent Sales Judie Coltman © SAP AG Code POS_MKT_EMP POS_SLS_EMP POS_IC_MKT POS_IC_SAL Page 28 of 40 .

SAP Best Practices CRM Organizational Model (C01): Configuration Guide Hierarchy Level Object Type 1 Org Unit BP_SERVICE 2 Position POS_SRV_MAN 3 Holder BP Service Back Office 2 Org Unit BP_SRV Service Employee 3 Position POS_SRV_EMP 4 Holder 2 Org Unit BP_TECH Service Technician 3 Position POS_SRV_TECH Matthew Carter 4 Holder 2 Org Unit BP_IC_SRV 3 Position POS_ICM_SRV 4 Holder 3 Position 4 Holder 2 Org Unit BP_IC_SUP IC Agent Support 3 Position POS_IC_SUP Peter Best 4 Holder Description BP Service Organization Service Manager Ryan Reval Barbara Lee BP Service Technicians Group BP Service Call Center IC Manager Angela Lucata IC Agent Service Ann Anderson BP IC Support Code POS_IC_SRV . Use the following procedure to translate the texts of the organizational units into other languages.1 Translate Organizational Units Procedure 1. Enter the following values and leave all other fields empty: Field name Value Organizational Unit selected Object ID Select the relevant organizational unit or leave the field empty in case the all org units have to be translated Reporting Period All Evaluation Path ORGEH © SAP AG Page 29 of 40 .8 Translate Organizational Model Use Initially. 3.3. Access the activity using one of the following navigation options: Transaction code CRMD_TRANS_OM SAP CRM GUI menu Master Data  Organizational Model  Translate Short Text for Organizational Units 2.8. the organizational units are maintained only in English.

On the Translate Language-Dependent Records screen maintain a translation for the objects names in the target language.2 Translate Positions Procedure 1. Access the activity using one of the following navigation options: Transaction code CRMD_TRANS_OM SAP CRM GUI menu Master Data  Organizational Model  Translate Short Text for Organizational Units 2. 5. Choose Save.SAP Best Practices CRM Organizational Model (C01): Configuration Guide Field name Value Source Language EN Target Language Select your target language 3. Do not translate the field Object abbr.3. . Choose Save.1 Creating System Users (SAP ERP) Use © SAP AG Page 30 of 40 . 4. Choose Execute. Enter the following values and leave all other fields empty: Field name Value Position selected Object ID Select the relevant positions or leave the field empty in case the all positions have to be translated Reporting Period All Source Language EN Target Language Select your target language 3. On the Translate Language-Dependent Records screen maintain a translation for the objects names in the target language.8. 4.9 Integration of System Users and Employees ERP <-> CRM 3.9. 3. Do not translate the field Object abbr.

enter the system user name SALES_MAN. Enter the following data: Field name Value Address tab page Last name Stone First name Jennifer Function Sales Manager E-Mail <E-mail address> (optional) Logon data tab page Initial password initial Repeat password initial User Type Dialog Profiles tab page Profile Leave empty. These users are required to perform the ERP steps of the business process procedures of the SAP Best Practices scenarios. Procedure 1. To create a new system user. Will be assigned in the next activity 5. you need to create some additional system users in the ERP system. Choose Create (F8). Repeat these steps for the following system user SERV_EMPL: Field name Value Address tab page Last name Lee First name Barbara Function Service Employee E-Mail <E-mail address> (optional) © SAP AG Page 31 of 40 . 3. choose one of the following navigation options: Transaction code SU01 SAP ERP GUI menu Tools  Administration  User Maintenance  Users 2. 6.SAP Best Practices CRM Organizational Model (C01): Configuration Guide If not already done. Choose Save (Ctrl+S). In the User field. 4. Repeat these steps for the following system user SALES_EMPL: Field name Value Address tab page Last name Curtis First name Michael Function Sales Employee E-Mail <E-mail address> (optional) 7.

Enter user SALES_MAN and SALES_EMPL in field User ID. 13. Choose Generate. Choose User Comparison. In order to avoid that these users will be able to access additional transactions. 7.9. Choose tab User. The predefined authorization roles are provided as attachment BP_CRM_ROLES. 10. 9. 12. Choose Change. Adapt authorizations if required. Choose Back. Choose Save. 2. Choose Role  Upload and upload the following roles from your local directory: Make sure that you choose the value (Default . Role ID Name BP_CRM_SALES_MANAGER BP CRM Sales Manager 4. 6. 11. 5. Choose Change Authorization Data. 16. 8.UTF8 für UnicodeSysteme) of field Codierung on the role selection screen Open. Access the activity using one of the following navigation options: Transaction code PFCG SAP ERP menu Tools  Administration  User Maintenance  Role Administration  Roles 3. 15.SAP Best Practices CRM Organizational Model (C01): Configuration Guide Result Additional system users were created in the ERP system. Download and unzip the roles to your local directory. Procedure 1. Choose Save. Choose Complete Comparison.ZIP to the general SAP note for this SAP Best Practices version.2 Assigning Role to System Users (SAP ERP) Use The users created in the preceding activity will be used in order to access specific ERP transactions from the CRM system. 3. 14. Repeat steps 3-15 with the following data: Role ID Name System User ID BP_CRM_SERVICE_EMPLOYEE BP CRM Service Employee SERV_EMPL © SAP AG Page 32 of 40 . Choose tab Authorizations. a PFCG role has to be assigned to the users to limit the authorizations.

3 Checking Organizational Data Settings Use See documentation of the IMG activity for details about this check Procedure 1. Procedure 1. Access the activity using one of the following navigation options: Transaction code CRM_ORG_PROUVE SAP CRM IMG menu Customer Relationship Management  Master Data  Organizational Management  Tools  Organizational Data Settings Check 2.SAP Best Practices CRM Organizational Model (C01): Configuration Guide .3. Procedure 1. Execute (F8) the update for object types O (Organizational unit) and S (Position). © SAP AG Page 33 of 40 .10. Access the activity using one of the following navigation options: Transaction code CRMD_INDEX_OM SAP CRM IMG menu Customer Relationship Management  Master Data  Organizational Management  Tools  Update List of Organizational Objects 2.1 Updating List of Organizational Units Use Run this activity to make changes to the organizational model visible for applications working on the model. Execute (F8) the check. 3. Execute (F8) the check. Access the activity using one of the following navigation options: Transaction code COM_OM_ATTRIBUTECHK SAP CRM IMG menu Customer Relationship Management  Master Data  Organizational Management  Tools Check Settings for Attribute Maintenance 2.2 Checking Settings for Attribute Maintenance Use Check the consistency of the attribute assignments to the organizational units.10 Checking Organizational Structure 3. Normally changes are not visible until the following day. 3.10.10.

To speed up this process. 4.11. Whenever a CRM transaction or a business partner needs the sales areas. 3. Access the activity using the following navigation option: Transaction code SA38 2. they are calculated.3. 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. Mark scenario SALE. channels and divisions maintained in the organizational model. 5. The sales areas are represented in the organizational model that you can maintain with the transaction PPOMA_CRM. Select the report HRBCI_ATTRIBUTES_BUFFER_UPDATE.11. To enable buffering you have to maintain view T77OMATTR. sales groups. © SAP AG Page 34 of 40 . Choose Attributes/Scenarios in the Dialog Structure 6. 8.1 Enable Buffering for Sales Scenario Procedure 1. Choose Save (Ctrl+S). 3.2 Update Buffers for Sales Scenario Procedure 1. Access the activity using the following navigation option: Transaction code OOATTRCUST 2. Flag the field in the column Buffering for the scenario SALE.11 Set Up Buffering for Sales Scenario Some processes of CRM need to have the sales areas.SAP Best Practices CRM Organizational Model (C01): Configuration Guide . 3. this means they are not physically stored. Log off and log on again to the CRM system in order to make the effect of these settings visible to your user. the sales areas are buffered. and this is an expensive process. sales offices. Report HRBCI_ATTRIBUTES_BUFFER_UPDATE is used to buffer the attributes of organizational management objects. Select the structure node Scenarios. 4. 3. Flag the fields Delete All Buffers and Restructure Buffer on (Date). but they are the result of the different combinations of sales organizations. Choose Execute (F8).

Procedure 1.12 Organizational Units Assignment 3. 5.. In the assignment block Roles choose Edit List and select the Role Billing Unit from the drop down list.g. Access the activity using the following navigation option: SAP CRM WebClient menu Master Data  Create: Corporate Account 2. DE) 3. BP Billing Unit) Main Address and Communication Data Country <relevant country> (e.2 Assigning Billing Unit to Sales Organization Use In this activity you define which billing unit is determined from the sales organization. Note you can also schedule a job in transaction SM36 to run this report regularly. .3. This applies to sales transactions in CRM Online that are billed in CRM Online and then posted as billing documents in SAP ERP Financial Accounting (FI). In the assignment block Account Details enter at least the following data: Field Name Field Entry General Data Name 1 <description of the billing unit> (e. © SAP AG Page 35 of 40 . Press Enter. Save your entries and take a note of the number of the newly created Billing Unit: BP ID:_______________________________ Result A billing organization unit has been created.12. Prerequisites You are logged on to the CRM WebClient with user power_user and password welcome.g.1 Creating a Billing Unit Use The purpose of this activity is to create the billing unit(s) being assigned to sales orders via the respective sales organization when performing sales transactions.. 4.12.SAP Best Practices CRM Organizational Model (C01): Configuration Guide In Note 737315 further details regarding this topic are described. 3.

Result A billing unit has been assigned to each relevant sales organization. Procedure 1. <ID of BP_SALES> SOrg. Choose New Entries (F5) and enter the following data: Field Name Field Entry Sales Org. Procedure 1. Access the activity using the following navigation options: Transaction code SPRO SAP CRM IMG menu Customer Relationship Management  Master Data  Organizational Management  Cross-System Assignment of Organizational Units  Assign Billing Units to Service/Sales Organizations 2.12. Prerequisites The respective service and sales organizations and billing units are already defined in the system. Choose New Entries (F5) and enter the following data: Field Name Field Entry ServiceOrg <ID of BP_SERVICE> © SAP AG Page 36 of 40 . BP_SALES Bill. Unit <ID of BP Billing Unit> 3. 3. Choose Save (Ctrl+S).3 Assigning Billing Unit to Service and Sales Organization Use The purpose of this activity is to define for service and sales transactions which billing units are found from the appropriate service/sales organizations. Access the activity using the following navigation options Transaction code SPRO SAP CRM IMG menu Customer Relationship Management  Master Data  Organizational Management  Cross-System Assignment of Organizational Units  Assign Billing Units to Sales Organizations 2.SAP Best Practices CRM Organizational Model (C01): Configuration Guide Prerequisites The respective sales organizations and billing units are already defined in the system.

Choose Save (Ctrl+S). 3. 3.SAP Best Practices CRM Organizational Model (C01): Configuration Guide Field Name Field Entry ServiceOrg BP_SERVICE Sales Org. Unit <ID of BP Billing Unit> CoCode <your company code> (e.4 Assigning Company Code to Billing Unit Use The purpose of this activity is to define which company code is determined from the respective billing unit. 3. Procedure 1. Prerequisites Company Code 1000 has been replicated and a new billing unit has been created. and posted as billing documents in SAP ERP Financial Accounting (FI).g. Result A billing unit has been assigned to each relevant service and sales organization. Unit <ID of BP Billing Unit> 3..12. BP_SALES Bill. Access the activity using the following navigation options: Transaction code SPRO SAP CRM IMG menu Customer Relationship Management  Master Data  Organizational Management  Cross-System Assignment of Organizational Units  Assign Company Codes to Billing Units 2. <ID of BP_SALES> SOrg. Choose New Entries (F5) and select the following values (using the input help): Field Name Field Entry Bill. This applies to sales transactions and service transactions in CRM Online that are invoiced via CRM Online. 1000) You are able to choose 1000 as company code if you have installed SAP Best Practices for Baseline in your ERP backend system.12. Choose Save (Ctrl+S).5 Assigning Business Area to Service and Sales Organization Use © SAP AG Page 37 of 40 .

This applies to CRM service transactions that are invoiced via CRM Online and posted as invoices in ERP FI. and division combinations. sales organization. The input help for business areas offers the business areas in the ERP system that is assigned to the CRM Online application.. BP_SALES DChan <your distribution channel> (e. 3. 3. Choose New Entries (F5) and enter the following data: Field Name Field Entry ServiceOrg <ID of BP_SERVICE> ServiceOrg BP_SERVICE Sales Org. Prerequisites The respective service and sales organizations and billing units are already defined in the system. 0001) You are able to select 10 as distribution channel and 0001 as business area if you have installed SAP Best Practices for Baseline in your ERP backend system.6 Assigning Plant and Storage Location to Service Organization Use The assignment applies to service processes in SAP CRM and is used to determine the correct plant and storage location when withdrawing or reserving spare part items.SAP Best Practices CRM Organizational Model (C01): Configuration Guide In this activity you define which business areas are determined from which service organization. distribution channel.g. 10) Division * Bus. © SAP AG Page 38 of 40 .12.g. Result A billing unit has been assigned to each relevant service and sales organization.. Access the activity using the following navigation options: Transaction code SPRO SAP CRM IMG menu Customer Relationship Management  Master Data  Organizational Management  Cross-System Assignment of Organizational Units  Assign Business Areas to Service/Sales Organizational Units 2. <ID of BP_SALES> SOrg. Procedure 1. If you have the SAP system number displayed bottom right in your SAP window you see the number of the SAP system there when you use the input help for business areas. Choose Save (Ctrl+S). area <your business area> (e.

4. Procedure 1. Loc. Result A plant and storage location has been assigned to each relevant service organization. Procedure 1. In the view Search Criteria enter BP Company in field Description and Organizational unit in field Find by.13 CRM WebClient UI Settings 3. <your storage location (e. 2. Choose Search.3. Access the activity using the following navigation options: SAP CRM WebClient menu Master Data  Search: Organization Model 3. 0001) You are able to select 1000 as plant and 0001 as storage location if you have installed SAP Best Practices for Baseline in your ERP back-end system.g.g. © SAP AG Page 39 of 40 . 3... SAP users and employees assigned to a position within the organizational model are also assigned to the corresponding business role. Thus. Access the activity using the following navigation options: Transaction code SPRO SAP CRM IMG menu Customer Relationship Management  Master Data  Organizational Management  Cross-System Assignment of Organizational Units  Assign Plant and Storage Location to Service Organizational Units 2. Choose Save (Ctrl+S).1 Assigning Business Roles to Positions Use The purpose of this activity is to assign business roles to positions in the organizational model. Choose New Entries (F5) and enter the following data: Field Name Field Entry Service Organization <ID of BP_SERVICE> Service Team * Service Employee * Plant <your plant> (e.13. 1000) Stor. . Log on to the SAP CRM WebClient with the user POWER_USER.SAP Best Practices CRM Organizational Model (C01): Configuration Guide Prerequisites The respective service organizations units are already defined in the system.

7. Select the according position. © SAP AG Page 40 of 40 .SAP Best Practices CRM Organizational Model (C01): Configuration Guide 5. Marketing Manager. 10. e. select the proper role from the dropdown list. 8. 11. 9. 6. In the view Result List click on the Organizational Unit ‘BP Company’ you searched for. BP_MKT_MAN BP Company  BP Marketing Organization  Marketing Employee. In the view Role Assignment. Perform steps 6-10 for the following positions and business roles: Position Business Role BP Company  BP Marketing Organization  Marketing Manager.g. Open the assignment block Position Details and choose Edit. Users are then linked to a role by assigning them to a position. Choose Save. BP_MKT_EMPL BP Company  BP Sales Organization  BP Direct Sales  BP Sales Office Central  Sales Manager BP_SLS_MAN BP Company  BP Sales Organization  BP Direct Sales  BP Sales Office Central  Sales Employee BP_SLS_EMPL BP Company  BP Sales Organization  Director of Sales BP_SLS_MAN BP Company  BP Sales Organization  BP Sales Call Center  IC Manager BP_IC_MAN BP Company  BP Sales Organization  BP Sales Call Center  IC Agent Marketing BP_ICA_MKT BP Company  BP Sales Organization  BP Sales Call Center  IC Agent Sales BP_ICA_SLS BP Company  BP Service Organization  Service Manager BP_SRV_MAN BP Company  BP Service Organization  BP Service Back Office  Service Employee BP_SRV_EMPL BP Company  BP Service Organization  BP Service Technicians Group  Service Technician BP_SRV_TECH BP Company  BP Service Organization  BP Service Call Center  IC Manager BP_IC_MAN BP Company  BP Service Organization  BP Service Call Center  IC Agent Service BP_ICA_SRV BP Company  BP Service Organization  BP IC Support  IC Agent Support BP_ICA_SRV Result Roles are not directly assigned to users but to positions in the organizational model. In the assignment block Organizational Unit navigate to the according position as indicated in the table below.