BB Installation Guide

backdamagedInternet and Web Development

Jul 30, 2012 (4 years and 10 months ago)

367 views



SAP BW 7.0
2

Dec
ember 2011

English














B
W
3
:
BW

Connectivity

for
the
SAP
CRM

System










SAP AG

Dietmar
-
Hopp
-
Allee

16

69190 Walldorf

Germany

Build
ing Block Configuration Guide


SAP Best Practices

BW Connectivity for SAP
CRM
: Configuration Guide

© SAP AG

Page
2

of
9

Copyright


© 2011 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 c
hanged 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 Corpo
ration.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z,
System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390,
OS/390, OS/400, AS/400, S/390 Parallel Enterpris
e Server, PowerVM, Power Architecture, POWER6+,
POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System
Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA,
AIX, Intelligent Miner, WebSpher
e, Netfinity, Tivoli and Informix are trademarks or registered trademarks
of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

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 Tec
hnology.

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.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesig
n, SAP BusinessObjects Explorer,
StreamWork, 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 other countries.

Business Objects and the Business Objects

logo, BusinessObjects, Crystal Reports, Crystal Decisions,
Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well
as their respective logos are trademarks or registered trademarks of
Business Objects Software

Ltd.
Business Objects is an SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and
services mentioned herein as well as their respective logos are trademarks or registered trademarks of
Sybase, Inc. Syb
ase is an SAP company.

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 res
pect 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 Best Practices

BW Connectivity for SAP
CRM
: Configuration Guide

© SAP AG

Page
3

of
9

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 nam
es,
Transaction Code
s, 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 cod
e, 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 t
hat 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 Best Practices

BW Connectivity for SAP
CRM
: Configuration Guide

© SAP AG

Page
4

of
9

Content


1

Local Settings in your SAP CRM system to be connected to BW

................................
.....

5

1.1

Defining Client Administration

................................
................................
..................

5

1.2

Definin
g Logical Systems

................................
................................
.........................

5

1.3

Assigning Logical System to Client

................................
................................
..........

6

1.4

Creating an RFC User

................................
................................
..............................

6

2

Cross Connectivity

................................
................................
................................
.............

7

2.1

Defining a Logical System (SAP BW)

................................
................................
......

7

2.2

Connecting SAP BW with your Source S
ystem (SAP BW)

................................
.....

8

2.3

Transferring Application Component Hierarchy (SAP CRM)

................................
...

9

SAP Best Practices

BW Connectivity for SAP
CRM
: Configuration Guide

© SAP AG

Page
5

of
9

BW Connectivity for SAP CRM
: C
onfiguration
Guide

1

Local Settings

in
your SAP
CRM

s
ystem to be
connected

to BW

1.1

Defining

Client Administration

Use

This activity allows you to change Customizing settings.

Procedure

Run the following activity:

Transaction Code

SCC4

Then carry out the following steps:

1.

Choose
Display



Change
.

2.

Confirm the w
arning message
Caution: The table is cross client
.

3.

Select your
client and choose
Details
.

4.

In the
Change View Clients:

Details

screen, activate the following settings:



Automatic recording of changes



Changes to Repository and cross
-
client Customizing allow
ed



eCATT and CATT allowed.

5.

Save
.

6.

Go back to the
SAP Easy Access

menu.

1.2

Defining Logical System
s


Use

The purpose of this activity is to create logical system
s

for your
systems

t
o enable
communication between systems within your system landscape
.


If
a
logic
al system

for the
CRM

and

the BW system

ha
ve

already been created

in your
CRM

system
, skip this activity.


Logical systems are defined cross
-
client.

Procedure

1.

Access the transaction using:

Transaction Code

SALE

2.

Choose
IDoc Interface / Application Link En
abling (ALE)


Basic Settings


Logical

systems



Define

Logical

System


SAP Best Practices

BW Connectivity for SAP
CRM
: Configuration Guide

© SAP AG

Page
6

of
9

3.

Choose
New entries
.

4.

Enter the following values:

Log. System

Name

<Logical system ID for
the client of
your
SAP
CRM

system>, for example
DS7CLNT723

A description for the logical syste
m

of
your
CRM

system

<Logical system

ID for your BW system
>

A

description
for
the logical system

of
your BW system


To designate logical systems, apply the naming convention

<
XXX
>CLNT<
NNN
>

where

XXX

is the system name

and

NNN

is the client.

5.

Save your
entries.

A transport request for
Workbench
appears.

6.

Select an existing request or create a new request, if necessary.

A transport request for
Customizing

appears.

7.

Select an existing request or create a new request, if necessary.

1.3

Assigning Logical System
to Client

Use

The purpose of this activity is to make an assignment for the logical system.

Skip this activity if a logical system is already assigned to your client.

Procedure

1.

Access the transaction using:

Transaction Code

SCC4

2.

Choose
Display



Change
.

3.

Confirm the warning message
The table is cross client
.

4.

Select your client and choose
Details
.

5.

Enter the name of the logical system of your client.

6.

Save and confirm the warning message
Be careful when changing the logical system
.

7.

Choose
Back

twice.

1.4

Creatin
g an RFC User

Use

To enable communication between the SAP
system
s,

you have to create an RFC user
.

Skip this activity if an RFC User has already been created.

SAP Best Practices

BW Connectivity for SAP
CRM
: Configuration Guide

© SAP AG

Page
7

of
9

Procedure

1.

Access the transaction using:

Transaction Code

SU01

2.

In the
User

field, enter
RFCUSER
.

3.

Choose

Create
.

4.

On the
Maintain User

screen, enter the following data on the Tab entry screens:

Address


Last Name

RFCUSER

Function

User for remote connections

Logon data

User type

System

Password

welcome

Defaults

Logon Language

EN

Roles

Role

SAP_
BC_USR_CUA_CLIENT

SAP_BC_USR_CUA_SETUP_CLIENT

Profiles

Profile

SAP_A
LL

S_BI
-
WX_RFC

5.

Save your entries.


2

C
ross Connectivity

2.1

Defining a Logical System

(SAP BW)


Use

The purpose of this activity is to create a logical system for your system

to be connected

in
the BW system.

This enables the system to recognize the target system as an RFC destination. If the logical
system has already been created, skip this activity.


Logical systems are defined cross
-
client.

Procedure

1.

Access the transaction using:

SAP Best Practices

BW Connectivity for SAP
CRM
: Configuration Guide

© SAP AG

Page
8

of
9

Transac
tion Code

SPRO

IMG Menu in
BW

SAP NetWeaver



Application Server


IDoc Interface /
Application Link Enabling (ALE)


Basic Settings


Logical

systems



Define

Logical

System

2.

Choose
New entries
.

3.

In the column
Log System
, enter a name for the logical sys
tem that you want to create.

4.

In the column
Name
, enter a description of the logical system.

Log. System

Name

<Logical system

for your
CRM

system to be
connected
>, for example
DS7CLNT723

A description for the logical system of
your
CRM

system to be connect
ed


To designate logical systems, apply the naming convention

<
XXX
>CLNT<
NNN
>

where

XXX

is the system name

and

NNN

is the client.

5.

Save your entries.

A transport request for
Workbench
appears.

6.

Select an existing request or create a new request, if necess
ary.

A transport request for
Customizing

appears.

7.

Select an existing request or create a new request, if necessary.

2.2

Connecting SAP BW with your Source System

(SAP BW)


Use

This chapter describes all settings that are necessary to connect the components
of the SAP
system landscape with each other.

Please perform the following steps for
your SAP
CRM

system

to be connected to BW
.

Procedure

To carry out the activity, choose one of the following navigation options in t
he SAP
BW

system:

Transaction Code

RSA1

SAP
BW

Menu

Modeling


Data Warehousing Workbench
:
Modeling

1.

Choose
Modeling.

2.

Choose
Source Systems.

3.

Double click on the entry

SAP

in the window on the right
.

4.

Choose the
Context menu
(right mouse click).

5.

Choose
Create.

6.

Make the following entries:

SAP Best Practices

BW Connectivity for SAP
CRM
: Configuration Guide

© SAP AG

Page
9

of
9

Field

En
try

Target computer (server)

Server of the SAP
CRM

system

to be
connected

System ID

(system name)

System ID of the SAP
CRM

system to be
connected

System number

System number of the
SAP

CRM

system

to be
connected

Background user i
n source
system

RFCUSER

Password for source system

user

w
elcome

Repeat password

w
elcome

Background user in
B
W

RFCUSER (can not be changed in this activity)

Password for
B
W

user

w
elcome

Repeat password

w
elcome

7.

Choose
Transfer
.

8.

On the dialog box
Pleas
e log on as an administrator in the following screen

choose
Continue
.

9.

Log on to the Source System with your user. Choose the correct client.

10.

On the dialog box
New Source System Connection

choose
Continue
.

11.

On the
Replicate Metadata
dialog box, choose
Only A
ctivate
.

Result

The system connection is defined and RFC connection was created with <
XXX
>CLNT<
NNN
>
where
XXX

is the system name and
NNN

is the client.


2.3

Transferring Application Component Hierarchy

(SAP
CRM
)


Procedure

This step has to be carried out in y
our SAP
CRM

system.

Transaction code

RSA9

Confirm the security check:
Do you want the content application Transfer Component
Hierarchy?

with
YES
.


If a dialog box appears requesting the user to enter a package, enter a package
in customer namespace and
choose
Save

or choose
Local object
.