Sei sulla pagina 1di 24

EHP3 for SAP CRM 7.

0
April 2016
English

CRM Organizational Model


Standalone (C02)
Building Block Configuration Guide

SAP SE
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
SAP Best Practices CRM Organizational Model Standalone (C02): Configuration Guide

Copyright

2016 SAP SE or an SAP affiliate company. 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 SE or an SAP affiliate company.

SAP and other SAP products and services mentioned herein as well as their respective logos are
trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other
countries. Please see http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark for
additional trademark information and notices.

Some software products marketed by SAP SE and its distributors contain proprietary software
components of other software vendors.

National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only,
without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable
for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate
company 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.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business
outlined in this document or any related presentation, or to develop or release any functionality
mentioned therein. This document, or any related presentation, and SAP SEs or its affiliated
companies strategy and possible future developments, products, and/or platform directions and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any
time for any reason without notice. The information in this document is not a commitment, promise, or
legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject
to various risks and uncertainties that could cause actual results to differ materially from expectations.
Readers are cautioned not to place undue reliance on these forward-looking statements, which speak
only as of their dates, and they should not be relied upon in making purchasing decisions.

SAP SE Page 2 of 24
SAP Best Practices CRM Organizational Model Standalone (C02): Configuration Guide

Revision Change Date Description

SAP SE Page 3 of 24
SAP Best Practices CRM Organizational Model Standalone (C02): 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 SE Page 4 of 24
SAP Best Practices CRM Organizational Model Standalone (C02): Configuration Guide

Contents
1 Purpose........................................................................................................................... 6
2 Preparation ..................................................................................................................... 6
2.1 Prerequisites ............................................................................................................ 6
3 Configuration .................................................................................................................. 6
3.1 Organizational Data Maintenance ............................................................................ 6
3.1.1 Performing Division Settings ........................................................................... 6
3.1.2 Defining Divisions ............................................................................................ 7
3.1.3 Defining Distribution Channels ........................................................................ 7
3.1.4 Defining Combination of Distribution Channel and Division ............................ 8
3.2 Set Up Integration Business Partner Organizational Management ...................... 9
3.2.1 Defining Number Range for Org Business Partners ....................................... 9
3.2.2 Defining Grouping for Org. Business Partners .............................................. 10
3.2.3 Setting Up Integration .................................................................................... 11
3.2.4 Executing Report for Changeover Classification ........................................... 12
3.3 Organizational Units ............................................................................................... 12
3.3.1 Creating an Organizational Model ................................................................. 13
3.3.2 Creating and Assigning Organizational Units ................................................ 14
3.3.3 Assigning Attributes to Organizational Unit ................................................... 15
3.4 Holder for Positions ................................................................................................ 17
3.4.1 Defining Number Ranges for Employees ...................................................... 17
3.4.2 Defining Grouping for Employees ................................................................. 18
3.5 Organizational Model Translation .......................................................................... 19
3.5.1 Translating Organizational Units ................................................................... 19
3.6 Organizational Structure Check ............................................................................. 20
3.6.1 Updating List of Organizational Units ............................................................ 20
3.6.2 Checking Settings for Attribute Maintenance ................................................ 20
3.6.3 Checking Organizational Data Settings ......................................................... 20
3.7 Organizational Units Assignment ........................................................................... 21
3.7.1 Creating a Billing Unit .................................................................................... 21
3.7.2 Assigning Billing Unit to Sales Organization ................................................. 22
3.7.3 Assigning Billing Unit to Service and Sales Organization ............................. 22
4 Pre-Assembled Deployment ......................................................................................... 23

SAP SE Page 5 of 24
SAP Best Practices CRM Organizational Model Standalone (C02): Configuration Guide

CRM Organizational Model Standalone


1 Purpose
This configuration guide provides the information you need to set up the configuration of this
building block manually.

2 Preparation
2.1 Prerequisites
Before starting with the installation of this building block, please see the document Quick
Guide to Implementing SAP Best Practices for CRM.

3 Configuration
With this building block a root organizational structure will be defined containing a sales
organization and a service organization to be used as root units when setting up a detailed
organizational structure for the respective application areas.
Organizational Management in CRM offers you a flexible tool for handling your companys
task-related, functional organizational structure as a current organizational model.
You can maintain the company structure including the positions and employees in an
application and assign specific data (attributes) to the organizational units.
The organization model will be especially used for organizational data determination within
the CRM scenarios.

For details about setting up an organizational structure please see the CRM
standard documentation.
These sample organizational structure is essential for all SAP Best Practices scenarios
because organizational data determination, partner determinations and evaluations are based
on this structure.

SAP Best Practices customizing settings are based on the sample organizational
model, that is in case of deviations from this sample model all pre-defined setting
for organizational data determination and so on will not work.

3.1 Organizational Data Maintenance


3.1.1 Performing Division Settings

Use
You can specify whether or not you work with divisions in the CRM system.
If you use a header division in CRM you do not need to use a dummy division.

SAP SE Page 6 of 24
SAP Best Practices CRM Organizational Model Standalone (C02): Configuration Guide

Procedure
1. Access the activity using the following navigation options:
Transaction code SPRO
SAP CRM IMG menu Customer Relationship Management Master Data
Organizational Management Division Settings Define Use
of Division and Dummy Division
2. Deselect the checkbox Division not act.
3. Select the indicator Header Div. Act., if you wish to use divisions at header level in
business transactions in CRM Enterprise (select for SAP Best Practices for CRM).

Result
The division settings have been successfully performed.

3.1.2 Defining Divisions

Use
In this step, you can define divisions for CRM.

Procedure
1. Access the activity using the following navigation options:
Transaction code SPRO
SAP CRM IMG menu Customer Relationship Management Master Data
Organizational Management Division Settings Define
Divisions
2. Choose New Entries.
3. Enter the following values:
Division Description
10 for example Product Division 10
4. You can enter additional divisions, but for the SAP Best Practices scenarios only division
10 will be used.
5. Save your entries.

Result
You have successfully defined divisions for CRM.

3.1.3 Defining Distribution Channels

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

Procedure
1. Access the activity using the following navigation options:

SAP SE Page 7 of 24
SAP Best Practices CRM Organizational Model Standalone (C02): Configuration Guide

Transaction code SPRO


SAP CRM IMG menu Customer Relationship Management Master Data
Organizational Management Organizational Data for Sales
Scenarios Define Distribution Channels
2. Choose New Entries.
3. Enter the following values:
Dis. Chan. Description
10 for example Direct Sales
20 for example Wholesale
30 for example Other Sales
4. You can enter additional distribution channels, but for the SAP Best Practices scenarios
only channels 10, 20, and 30 will be used.
5. Save your entries.

Result
Distribution channels for CRM have been successfully defined.

3.1.4 Defining Combination of Distribution Channel and


Division

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

Procedure
1. Access the activity using the following navigation options:
Transaction code SPRO
SAP CRM IMG menu Customer Relationship Management Master Data
Organizational Management Organizational Data for Sales
Scenarios Define Combination of Distribution Channel and
Division
2. Choose New Entries.
3. Enter the following values:
Distribution Channel Division
10 10
4. You can enter additional combinations but for the SAP Best Practices scenarios only the
combination listed in the table above will be used.
5. Save your entries.

Result
Combination of distribution channel and division has been successfully defined.

SAP SE Page 8 of 24
SAP Best Practices CRM Organizational Model Standalone (C02): Configuration Guide

3.2 Set Up Integration Business Partner Organizational


Management

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

3.2.1 Defining Number Range for Org Business Partners


Use
For each organizational unit created in the organizational model a business partner is
generated automatically. For this business partners a number range has to be created.
If you dont define a number range the created business partner will get a number that
belongs to other business partner types, for example consumers.

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

Transaction code BUCF


SAP CRM IMG menu Cross-Application Components SAP Business Partner
Business Partner Basic Settings Number Ranges and
Groupings Define Number Ranges
2. Before creating new number range intervals you have to delete the SAP default number
ranges.
3. Choose Change Intervals.
a. Business partners are already created for a number range.
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.
b. No business partners have been created for the number range.
In this case select the number range and choose Delete Line (F7).
4. In the next steps you define the number range for Org business partners.
5. Choose Insert Line (F6).
6. Enter the following values:
Field Value Remarks
No. Y4 Choose an ID with leading Y
From No. 0004000000 If you use numeric values make sure you add
leading zeroes to the value until the full length of
the field is reached.
To number 0004999999 If you use numeric values make sure you add
leading zeroes to the value until the full length of
the field is reached.
NR Status
Ext Internal number assignment is required.

SAP SE Page 9 of 24
SAP Best Practices CRM Organizational Model Standalone (C02): Configuration Guide

7. Choose Insert.
8. Choose Save.
9. Confirm the information window Transport number range intervals with Continue.

Result
You have successfully defined number range for Org. business partners.

3.2.2 Defining Grouping for Org. Business Partners

Use
For each organizational unit created in the organizational model a business partner is
generated automatically. 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. This
grouping can be used for selecting the number range when creating a business partner.

Procedure
1. Access the activity using the following navigation options:
Transaction code SPRO

SAP CRM IMG menu Cross-Application Components SAP Business Partner


Business Partner Basic Settings Number Ranges and
Groupings Define Groupings and Assign Number Ranges
2. Choose New Entries (F5).
3. Enter the following values:
Field Value Remarks
Grouping Y4 The grouping must have the same ID
as the assigned number range
Short name Org BP
Description (EN) Business Partner
(Organizational Unit)
Number range Y4 The number range you have created
for Org Business Partners.
External Internal number assignment is
required.

4. Choose Enter.
Int.Std.Grping Selected
Ext.Std Grping Deselected

Make sure that the ID of the grouping is identical with the ID of the assigned
number range.
5. Choose Save.
6. Select a customizing request.

SAP SE Page 10 of 24
SAP Best Practices CRM Organizational Model Standalone (C02): Configuration Guide

To maintain additional languages highlight the new grouping and choose Goto
Translation.
Select the relevant languages and maintain the translations.
Language Short Name Description
EN Org BP Business Partner (Organizational Unit)
DE Org BP Geschftspartner (Organisationseinheit)
ES Org BP Interlocutor comercial (unidad organizativa)
PT Org BP Parceiro de negcios (unidade organizacional)

ZH Org BP

FR Org BP Partenaire (unit organisationnelle)

JA BP ()

RU BP ( )
AR Org BP ) (

Result
A grouping has been created and the number ranges have been assigned.

3.2.3 Setting Up Integration


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

Procedure
1. Access the activity using the following navigation options:
Transaction code SPRO
SAP CRM IMG menu Customer Relationship Management Master Data Business
Partner Integration Business Partner Organizational
Management Set Up Integration with Organizational
Management

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

Group Sem. Abbr. Value abbr. Description


HRALX HRAC X Activate HR Integration
HRALX OBPON ON Integration O-BP Activated
HRALX ONUMB 2 Business Partner Number Assignment
(Org. Unit)
HRALX OSUBG Y4 Business Partner Subgroup
(Organizational Unit)
Number Range

3. Save your entries.

SAP SE Page 11 of 24
SAP Best Practices CRM Organizational Model Standalone (C02): Configuration Guide

Result
You have successfully activated the integration of organizational units and business partners.

3.2.4 Executing Report for Changeover Classification

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

This report has to be executed once even in case of a new installed CRM system.
Otherwise error messages during business partner processing will occur.
It has to be executed at this time because otherwise the business partners which
are related to the organizational units are not created correctly.

Procedure
1. To run the report, use the following navigation option:
Transaction code SA38
2. Enter the report CRM_MKTBP_ZCACL_UPDATE_30 and choose Execute (F8).
3. Keep the default values and choose Execute (F8).
4. In case of the status message Class type BUP: no suitable classes found no further
actions are required.
5. In case of other messages, read the documentation of the report and run the report with
deactivated flag for Test mode.

Result
You have successfully executed the report for changeover classification.

3.3 Organizational Units


Use
Organizational units are functional units of a company. Depending on how task distribution is
organized in a company, these can be, for example, departments, groups or project teams.
The organizational unit in sales and distribution structures the company according to SD
requirements. Sales transactions are prepared and implemented in a sales organization.
Several sales offices or sales groups or other freely definable organizational units can be
assigned at lower level than the sales organization. It is not possible, however, for other sales
organizations to be subordinate to a sales organization. You can assign attributes to a sales
organization in organizational plan maintenance. The sales organization is then responsible
for these attributes; for example, one or more divisions and distribution channels, a language,
or a postal code.
In addition there are organizational unit in the service area in which services are planned and
prepared.
For CRM service there is the attribute Service organization, which you set in organizational
model maintenance on the Function tab page. This attribute flags an organizational unit as a

SAP SE Page 12 of 24
SAP Best Practices CRM Organizational Model Standalone (C02): Configuration Guide

responsible organizational unit in the service area. This means that the organizational unit is
flagged as a superordinate organizational unit in the service area, to which you can assign
subordinate organizational units.
Subordinate organizational units, the responsible service organizations, report to the service
organization. By inheriting the attribute Service organization, the system identifies the
subordinate organizational units implicitly as organizational units for the service area.

3.3.1 Creating an Organizational Model

Please check the Delta Guide (C01_CRM70x_BB_DeltaGuide_EN_XX.doc)

Use
An organization model is created initially together with a root organizational unit which builds
the basic node for all other organizational units.
Log on to the CRM WebClient with user POWER_USER and password welcome. If
necessary select business role YBP_POWER_USER from the list of business roles.

Procedure
1. Access the Organizational Model using the following navigation:
SAP CRM WebClient menu Master Data Search: Organization Model
2. Create a root organizational unit by choosing Root Organizational Unit.
3. Choose Continue.
4. Maintain the following values for this organizational unit:
Field name Value
General Data
Code BP_COMP
Description Global Company
Address
Street/House No. Enter values
City Enter values
Postal Code Enter values
Country <Country>
Attributes
Country <Country>

Please use ID BP_COMP and do not change this ID until the complete
organizational model has been maintained.
5. Choose Save. An ID will be automatically created for the root organization.

In order to display this ID, choose the button Personalize, move ID from the
Available Columns to the Displayed Columns and Save.

SAP SE Page 13 of 24
SAP Best Practices CRM Organizational Model Standalone (C02): Configuration Guide

Result
A new organizational model has been successfully created.

3.3.2 Creating and Assigning Organizational Units

Please check the Delta Guide (C01_CRM70x_BB_DeltaGuide_EN_XX.doc)

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

Use
Organizational units are functional units of a company. Depending on how task distribution is
organized in a company, these can be, for example, departments, groups or project teams.
With this activity you will create and assign organizational units to the organizational model
that has been created in the preceding section.

Procedure
1. Access the activity using the following navigation option:
SAP CRM WebClient menu Master Data Search: Organization Model
2. Enter the description of the organizational unit, that has been created in the preceding
section (Global Company) and choose Search.
3. In the view area Result List, select the link of the root organizational unit Global
Company. This object has already been created in the preceding section.
4. In the assignment block Organizational Unit select the root organizational unit Global
Company and choose the button Organizational Unit to create a new organizational unit
Headquarters on the level below.
On the level below organizational unit Headquarters you create new organizational units
Sales and Service (as shown in the table below).
5. In the assignment block Organization Unit Details and the view area General Data enter
the Code and a Description for the new organizational unit (as shown in the table below).
6. Run the following steps to create the following SAP Best Practices organizational
structure as an example to work with:
Description Hierarchy Code Functions
Level
Global Company 0 BP_COMP
Headquarters 1 BP_HQS
Sales 2 BP_SALES Sales Organization
Service 2 BP_SERVICE Service Organization

The code of organizational units must not contain numbers. Otherwise problems
may occur during the organizational data determination; in particular, the system
may not be able to identify organizational units.
7. In view area Address, enter an address for the organizational unit.
Check the Delta Guide for details.

SAP SE Page 14 of 24
SAP Best Practices CRM Organizational Model Standalone (C02): Configuration Guide

8. In view area Functions check the corresponding function (for example, Sales
Organization) for each organizational unit (for example, Sales).
9. Choose Back twice.
10. Save your entries.

Result
New basic organizational units for Headquarters, Sales and Service have been created.

3.3.3 Assigning Attributes to Organizational Unit

Please check the Delta Guide (C01_CRM70x_BB_DeltaGuide_EN_XX.doc)

Use
You can use general attribute maintenance to attribute data (attributes) to organizational
units, when creating your sales and distribution or service structure. You always maintain
these attributes specifically for a scenario (Sales or Service).
CRM distinguishes between organizational and business attributes:
organizational attributes define the type of organizational unit, for example, whether it
is a sales organization or a service group.
business attributes define the responsibility of an organizational unit, for example, for
which distribution channels or product groups an organizational unit is responsible.
Attributes can have one or more values. For some attributes, you can also enter areas (for
example, partner numbers 001 to 300).

Procedure
1. Access the activity using the following navigation option:
SAP CRM WebClient menu Master Data Search: Organization Model
2. Enter the description Global Company and choose Search.
3. In the view area Result List, select the link of the root organizational unit Global
Company.
4. In assignment block Organizational Unit select the organizational unit that you want to
maintain.
5. In the view Allow Org. Unit to be Determined of the assignment block Organizational Unit
Details, select field if necessary. Otherwise this organizational unit will not be taken
into consideration for the organizational data determination.
Organizational Unit Details
Organizational Functions Allow Org. Unit to be Determined
Unit ID
BP_COMP
BP_HQS
BP_SALES Sales Organization
BP_SERVICE Service Organization Service

SAP SE Page 15 of 24
SAP Best Practices CRM Organizational Model Standalone (C02): Configuration Guide

6. In order to maintain the attributes select the created organizational units one after another
and choose Edit List in the assignment block Attributes.
7. Maintain all required attributes for all three scenarios (Marketing, Sales and Service) of an
organizational unit if necessary.
For the SAP Best Practices organizational model maintain the following attributes.
Most of the values cannot be pre-defined because they are depending on the country or
on the individual organizational structure. The entry <PV> indicates that the value has to
be personalized according to the project situation (in parenthesis an example value is
indicated that can be used for demo purposes).
Organizational Value Value to
Scenario Attribute
Unit ID
BP_COMP Marketing <PV> (that is
Country
US)
Ref. currency for <PV> (that is
document USD)
Sales <PV> (that is
Country
US)
Ref. currency for <PV> (that is
document USD)
Correspondence <PV> (that is
Language EN)
Service <PV> (that is
Country
US)
Correspondence <PV> (that is
Language EN)
BP_HQS Marketing <PV> (that is
Country
(values inherited US)
from BP_COMP)
Ref. currency for <PV> (that is
document USD)
Sales <PV> (that is
Country
US)
Ref. currency for <PV> (that is
document USD)
Correspondence <PV> (that is
Language EN)
Service <PV> (that is
Country
US)
Correspondence <PV> (that is
Language EN)
BP_SALES Sales Division <PV> (that is 10)
Distribution Channel <PV> (that is 10)
<PV> (that is <PV> (that is
Postal Code
00000) 99999)
<PV> (that is
Tupel ()
1010)
BP_SERVICE Sales Region <PV>
Tupel () <PV>

SAP SE Page 16 of 24
SAP Best Practices CRM Organizational Model Standalone (C02): Configuration Guide

Organizational Value Value to


Scenario Attribute
Unit ID
Division <PV>
Distribution Channel <PV>
<PV> (that is <PV> (that is
Postal Code
00000) 99999)
<PV> (that is <PV> (that is
Service Postal Code
00000) 99999)
8. In assignment block Attributes choose the button Check Consistency for the consistency.
Examine the messages for the check results.
9. Choose Save.

Result
You have successfully assigned attributes to the organizational units.

3.4 Holder for Positions

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

3.4.1 Defining Number Ranges for Employees


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

Procedure
1. Access the activity using one of the following navigation options:
Transaction code BUCF
SAP CRM IMG menu Cross-Application Components SAP Business Partner
Business Partner Basic Settings Number Ranges and
Groupings Define Number Ranges
2. Choose Change Intervals.
3. Choose Insert Line (F6).
4. Enter the following values:
No From No. To number External
Y7 0000010000 0000099999 X

5. Choose Save (Ctrl+S).

Result
You have created separate external number ranges in CRM for employees.

SAP SE Page 17 of 24
SAP Best Practices CRM Organizational Model Standalone (C02): Configuration Guide

3.4.2 Defining Grouping for Employees


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

Procedure
1. Access the activity using the following navigation options:
Transaction code SPRO
SAP CRM IMG menu Cross-Application Components SAP Business Partner Business
Partner Basic Settings Number Ranges and Groupings
Define Groupings and Assign Number Ranges

2. Choose New Entries.


3. Enter the following values:
Grouping Short name Description Number External Ext. Std. Int Std.
range Grping Grping
Y7 CRM CRM Y7 X Deselected Deselected
Employees Employees

To maintain additional languages highlight the new grouping and choose Goto
Translation.
Select the relevant languages and maintain the translations:
Language Short Name Description
EN CRM Employees CRM Employees
DE CRM Mitarbeiter CRM Mitarbeiter
ES CRM Empleados CRM Empleados
PT CRM Empregados CRM Empregados
ZH CRM CRM

FR CRM Salaris CRM Salaris


JA CRM CRM
RU CRM CRM
AR CRM CRM

4. Choose Save.

Result
You have defined the grouping for the created employee and assign the number range to this
grouping

SAP SE Page 18 of 24
SAP Best Practices CRM Organizational Model Standalone (C02): Configuration Guide

3.5 Organizational Model Translation


Use
Initially, the organizational units are maintained only in English. Use the following procedure
to translate the texts of the organizational units into other languages.

3.5.1 Translating Organizational Units


Use
Initially, the language used is English. The texts of the organizational units have to be
translated into other languages.

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. 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
Source Language EN
Target Language(s) Select your target language

3. Choose Execute.
4. On the Translate Language-Dependent Records screen, maintain a translation for the
objects names in the target language.

Do not translate the field Object abbr.


5. Choose Save.

Result
You have successfully translated the texts of the organizational units.

SAP SE Page 19 of 24
SAP Best Practices CRM Organizational Model Standalone (C02): Configuration Guide

3.6 Organizational Structure Check


3.6.1 Updating List of Organizational Units

Use
Run this activity to make changes to the organizational model visible for applications working
on the model. Normally changes are not visible until the following day.

Procedure
1. Access the activity using 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. Choose Execute to update object type O (Organizational unit).

Result
You have updated the list of organizational objects.

3.6.2 Checking Settings for Attribute Maintenance

Use
Check the consistency of the attribute assignments to the organizational units.

Procedure
1. Access the activity using the following navigation options:

Transaction code SPRO


SAP CRM IMG menu Customer Relationship Management Master Data
Organizational Management Tools Check Settings for
Attribute Maintenance

2. Execute the check.

Result
The settings for attribute maintenance have been checked.

3.6.3 Checking Organizational Data Settings


Use
See the documentation of the IMG activity for details about this check.

Procedure
1. Access the activity using the following navigation options:

SAP SE Page 20 of 24
SAP Best Practices CRM Organizational Model Standalone (C02): Configuration Guide

Transaction code SPRO


SAP CRM IMG menu Customer Relationship Management Master Data
Organizational Management Tools Organizational Data
Settings Check

2. Maintain the following values:


Field name Field Entry
Transaction Type (* = All) *

3. Execute the check (F8).

Result
The organizational data settings have been checked.

3.7 Organizational Units Assignment


Use
With the following chapters a necessary mapping of organizational units is maintained for the
sales and service areas in combination with billing, which needs to be done in any case.

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

Prerequisites
You are logged on to the CRM WebClient with user power_user and password welcome. If
necessary, select the business role YBP_POWER_USER from the list of business roles.

Procedure
1. Access the activity using the following navigation option:
SAP CRM WebClient menu Master Data Create: Corporate Account

2. In the assignment block Account Details enter at least the following data:
Field name Field Entry
General Data
Grouping Business Partner (Organizational Unit)
Name 1 <description of the billing unit> (for example, BP Billing Unit)
Main Address and Communication Data
Country <relevant country> (for example, US)

3. Press Enter.
4. In the assignment block Roles select the Role Billing Unit from the drop down list.

SAP SE Page 21 of 24
SAP Best Practices CRM Organizational Model Standalone (C02): Configuration Guide

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

3.7.2 Assigning Billing Unit to Sales Organization

Use
In this activity you define which billing unit is determined from the sales organization. This
applies to sales transactions in CRM Online that are billed in CRM Online.

Prerequisites
The respective sales organizations and billing units are already defined in the system.

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 Sales
Organizations

2. Choose New Entries (F5) and enter the following data:


Field name Field Entry
Sales Org. <ID of BP_SALES>
SOrg. BP_SALES
Bill. Unit <ID of BP Billing Unit>

3. Choose Save (Ctrl+S).

Result
A billing unit has been assigned to each relevant sales organization.

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

Prerequisites
The respective service and sales organizations and billing units are already defined in the
system.

SAP SE Page 22 of 24
SAP Best Practices CRM Organizational Model Standalone (C02): Configuration Guide

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. Choose New Entries (F5) and enter the following data:


Field name Field Entry
ServiceOrg <ID of BP_SRVC>
ServiceOrg BP_SERVICE
Sales Org. <ID of BP_SALES>
SOrg. BP_SALES
Bill. Unit <ID of BP Billing Unit>

3. Choose Save (Ctrl+S).

Result
A billing unit has been assigned to each relevant service and sales organization.

4 Pre-Assembled Deployment
Use
If you follow the pre-assembled deployment approach, some parts of the SAP Best
Practices for CRM content are already activated, whereas others still need to be activated.
Therefore, all configuration tasks are classified into one of the following categories:

Pre-Assembly (Pre): Configuration tasks classified as Pre-Assembly have already


been executed and do not need to be re-activated during an implementation project.
Post-Processing (Post): Post-Processing configuration tasks still need to be
performed in the target system landscape.
Some tasks can be classified as both Pre-Assembly and Post-Processing; this
means that these tasks have been pre-assembled, but need to be checked and
potentially modified during the post-assembly phase.

ERP CRM
Configuration Task Integrated Standalone System
Pre Post Pre Post
3.1.1 Performing Division Settings n.a. n.a. X CRM
3.1.2 Defining Divisions n.a. n.a. X CRM
3.1.3 Defining Distribution Channels n.a. n.a. X CRM
3.1.4 Defining Combination of Distribution n.a. n.a. X CRM
Channel and Division
3.2.1 Defining Number Range for Org n.a. n.a. X CRM

SAP SE Page 23 of 24
SAP Best Practices CRM Organizational Model Standalone (C02): Configuration Guide

Business Partners
3.2.2 Defining Grouping for Org. Business n.a. n.a. X CRM
Partners
3.2.3 Setting Up Integration n.a. n.a. X CRM
3.2.4 Executing Report for Changeover n.a. n.a. X CRM
Classification
3.3.1 Creating an Organizational Model n.a. n.a. X CRM
3.3.2 Creating and Assigning n.a. n.a. X CRM
Organizational Units
3.3.3 Assigning Attributes to Organizational n.a. n.a. X CRM
Unit
3.4.1 Defining Number Ranges for n.a. n.a. X CRM
Employees
3.4.2 Defining Grouping for Employees n.a. n.a. X CRM
3.5.1 Translating Organizational Units n.a. n.a. X CRM
3.6.1 Updating List of Organizational Units n.a. n.a. X CRM
3.6.2 Checking Settings for Attribute n.a. n.a. X CRM
Maintenance
3.6.3 Checking Organizational Data n.a. n.a. X CRM
Settings
3.7.1 Creating a Billing Unit n.a. n.a. X CRM
3.7.2 Assigning Billing Unit to Sales n.a. n.a. X CRM
Organization
3.7.3 Assigning Billing Unit to Service and n.a. n.a. X CRM
Sales Organization

SAP SE Page 24 of 24