2 03 organisational management[1] 22

8/8/2019 2 03 Organisational Management[1] 22

1/19

SAP AG 2001

Partner DeterminationOverview

Business Partner

Text DeterminationOrganizational Management

Output DeterminationProduct Master

CRM BillingOpportunity Management

Conclusion & Appendix:CRM Best PracticesActivity Management

Sales Transactions

Organizational Management
http://www.clicktoconvert.com/


2/19

SAP AG 2001

l The CRM Organization model and its advantages

l Elements of the organization model

l Scenarios and attributes

l Determining the responsible organizational unit

l Automatic generation of the organization model

l Describe the CRM organization model, its functions andcharacteristics

l Explain the differences between the organization models ofCRM and R/3

l Depict the determination of the responsible organizational unit

Contents/Objectives

Contents

Objectives

At the end of this unit, you will be able to:


3/19

SAP AG 2001

l You are responsible for mapping the organizationalstructure of your enterprise in CRM Organizationmodel.

l Alongside the initial data creation of the organization

model you have to depict parts of the organizationalstructure of the existing Backend R/3 system in theCRM system.

l To allow your sales and service processes to run asautomated as possible, set up automatic organizational

determination.

Business Scenario


4/19

SAP AG 2001

l High flexibility when modeling the organizational structurewithin the CRM system

l One organization model for sales, service and EBP

l Validities (time stamp) for each organizational unit forplanning organizational alterations

l Organizational units are created automatically as business

partners

l Flexible determination of the responsible organizationalunits in business transactions

Advantages of the Organization Model


5/19

SAP AG 2001

IDES Inc.

IDES US Bus. Part.IDES US

Campaign Mana.

Sales US

IDES US Vend.

Sales US West

Marketing Mana.

Org. Unit

Org. Unit

Position

Purch. West IDES US Cust.Prod. West

Org. Unit

Sales Org.

Sales US East

Sales Office Office Internet Sales Off. Denver

Organizational Model: Example

Off. San Diego

Org. Unit


6/19

SAP AG 2001

You can maintain the following object types:

l Organizational Unit

l Positions

l

Holder (Central Person, System User)

Organizational Units are mandatory in CRM,Positions and Holders are optional

Organizational Unit

Position

Central Person System User

Elements of the Org. Structure: Object Types


7/19

SAP AG 2001

l Org. Units (e.g. Sales Office North)

l Position (e.g. Sales Manager North, Purchaser)

l Holder

Employee (Business Partner)

User (User-ID)

Basic data Address Type Attribute

Various data is available according to object type

Organizational Structure - Object Types


8/19

SAP AG 2001

Object Type Organizational Unit - Data Parts

Address

Type

Basic data

Attributes

Identifier, description, validity period

Example: Office 1, Boston office 01.01.01-31.120.9999

Address data (first and secondary address)

Example: 1 High St., 87654 Boston, Tel, Fax, E-mail, ...

Choice of scenarioExample: sales, service

R/3 mapping informationExample: organizational unit is sales org. and conforms

to R/3 sales org. 3020

Object attributes

Example: US country key, reference currency USD,

distribution channel 10, division 00, ...

Set the object as active/inactive (influence over

organizational determination and alteration ofattributes)


9/19

SAP AG 2001

Organizational unit: O 50001243 Boston office

Scenario: Sales

Org. Attributes: Sales office

General Attributes: Distr. chnl: 10Country: US

Zip code: 80000 to 89999

Scenario: Service

Org. Attributes: Service Organization

General Attributes: Country: US and CAN

Zip code: -

Scenarios and Attributes


10/19

SAP AG 2001

Sales organization Sales US

BostonSales office

Group 1 Group 2 Group 1 Group 2Salesgroup

Attribute 1: country = US

Attribute 2: ZIP code = 80000 to 89999

Attribute 3: ZIP code = 00000 to 10000

Inherited attribute 1: country = US

Denver

Inherited attribute 2: ZIP code = 80000 to 90000

Inherited attribute 3: ZIP code = 00000 to 10000

Inherited attribute 1: country = US

Example: attribute maintenance for organizational units in a

sales scenario

Attribute Inheritance


11/19

SAP AG 2001

R/3 CRM

?

l Analysis of the R/3 organizational structure (which sales orservice organizations are required in the CRM system?)

l Structure of the organizational model in CRM

l Mapping of CRM organizational units with those in R/3

l Assignment of attributes to organizational units

l Definition and assignment of positions and holders

From an R/3 Org. Model to the CRM Org. Structure

This watermark does not appear in the registered version - http://www.clicktoconvert.com


12/19

SAP AG 2001

l To speed up creation of theinitial CRM Org. Model you canhave the R/3 organizationalmodel automatically generatedin CRM

l Prerequisite for the automatic generation is that no organizationmodel exists in CRM, as existing organization models could beoverwritten

l The generation program can only be executed once and afterwardsno delta download is carried out

l Only the organization models from the "sales" scenario can becreated, the scenarios "purchasing" and "service" are notsupported

Automatic Generation of the Organizational Model


13/19

SAP AG 2001

Company code

Division

Distribution

channel

Sales-

organization1000

10

01 02 0201

1020

2000 1000

OU 3OU 2

2000

OU 1OU 120/0110/01

10/02

Root node

10/02

Sales structure in R/3 Organization model in CRM

OU = Organizational unit

Automatic Generation of the Organization Model
http://www.clicktoconvert.com/http://www.clicktoconvert.com/


14/19

SAP AG 2001

All other organizational units derive from the responsibleorganizational unit!

Example: responsible organizational unit = Group IS1

Sales group Group IS1 (Details Type)

Sales office Office 2 (Details Type)

Distr. chnl. 30 (Details Attributes)

Sales organization Sales US (Details Type)

l No automatic determination of the responsible organizationalunit (= manual maintenance in the documents)

l Automatic determination of the responsible organizational unitvia determination rules of the type Responsibilities

l Automatic determination of the responsible organizational unit

via determination rules of the type Organization model

Determining the Responsible Organizational Unit


15/19

SAP AG 2001

Container elements

Transaction type

State,region

Org.data profile

Determination rule

Search criteria

Evaluated attributes(fill container)

State: USRegion: MA

Organization model

potential organizational

units are searchedfor in the Organization

model

Customer order

Business Partner

(e.g. Mr J. Smith

from Boston, MAUnited States)

Responsibilities

direct fixing of theresponsible

organizational unit

o r

The

org.unitfo

undi

s

updated

Determining the Responsible Organizational Unit


16/19

SAP AG 2001

Standard Order

Org.data

Sales Org. 50001200

Distrib. Ch. 12

Sales Office 50001205

Transaction Type: Standard Order (TA)

Header:

Organizational Data Log

l Indicates how the systemhas determined theorganizational data

Organizational Data Profile withDetermination Rule(s):

l Specifies how the systemdetermines organizational data

l Specifies which organizationaldata is required

Organizational Data Determination at Header Level


17/19

SAP AG 2001

Organizational data on item level may not differ from that in the

header (except division)

No individual data determination on item level

l Org. data is copied from the

header.

l Division is derived from the

product.

l There is no organizational

data on item level.

Assign org. data profile withoutdetermination rule to item

category

No org. data profile is assigned

to the item category

Organizational Data Determination at Header Level


18/19

SAP AG 2001

Transaction Type

Organizational Data Profile

Determination Rules

Rule typeResponsibilities

Rule typeOrganizational Model

Responsibilities can be

assigned directly

Determination according

to the attributes of the

org. units

Only org. units necessary,

no attributes,no organizational plan

necessary

Organizational plan has to

be defined;Attributes have to be

maintained

System

Customizing Settings

Organizational Data Determination Overview

Wizard for creating

determination rules

Wizard for creatingand assigning org.

data profiles


19/19

SAP AG 2001

l Describe the CRM organization model, its functions andcharacteristics

l Explain the differences between the organization models of CRMand R/3

l Depict the determination of the responsible organizational unit

You are now able to

Summary

2 03 organisational management[1] 22

Documents