B84_BB_ConfigGuide_EN_HR

7/31/2019 B84_BB_ConfigGuide_EN_HR

http://slidepdf.com/reader/full/b84bbconfigguideenhr 1/11

SAP BW 7.0

July 2007

English

B84: BI Connectivity

SAP AGDietmar-Hopp-Allee 1669190 Walldorf Germany

Building Block Configuration Guide



SAP Best Practices BI Connectivity: Configuration Guide

Copyright

© Copyright 2006 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without theexpress 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 softwarecomponents of other software vendors.

Microsoft, Windows, 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, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli,and Informix are trademarks or registered trademarks of IBM Corporation.

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 trademarksor registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide WebConsortium, 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 technologyinvented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and servicesmentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AGin Germany and in several other countries all over the world. All other product and service namesmentioned are the trademarks of their respective companies. Data contained in this document servesinformational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and itsaffiliated companies ("SAP Group") for informational purposes only, without representation or warrantyof any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. Theonly warranties for SAP Group products and services are those that are set forth in the express warrantystatements accompanying such products and services, if any. Nothing herein should be construed asconstituting an additional warranty.

© SAP AG of 11




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 fieldnames, screen titles, pushbuttons as well as menu names, paths andoptions.

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, programnames, transaction codes, table names, and individual key words of aprogramming 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 asnames 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 thesystem exactly as they appear in the documentation.

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

© SAP AG of 11




Content

BI Connectivity ........................................................................................................................... 5

1 Local Settings ..................................................................................................................... 5

.1.1 Defining Client Administration ..................................................................................... 5

.1.2 Defining a Logical System .......................................................................................... 5

.1.3 Assigning Logical System to Client.............................................................................. 6

.1.4 Creating an RFC User ................................................................................................ 7

.1.5 Opening Data Warehousing Workbench (only SAP BI system) .................................... 7

.1.6 Defining RFC-USER as default (only SAP BI and SCM system) .................................. 8

2 Cross Connectivity .............................................................................................................. 8

.2.1 Connecting SAP BI with SAP ERP, SAP CRM, SAP SRM ........................................... 8

.2.2 SAP SCM with SAP BI................................................................................................. 9

2.2.1 Connecting SAP SCM to the SAP BI system .......................................................... 9

2.2.2 Connecting SAP BI to the SAP SCM System .......................................................10

.2.3 Connectivity File System in SAP BI ........................................................................... 10

© SAP AG of 11




BI Connectivity

1 Local Settings

This chapter describes all local settings that are necessary for each component like SAP ERP,SAP SCM, SAP BI, SAP CRM or SAP SRM. Please perform the following steps in all relevantsystems.

.1.1 Defining Client Administration

Use

This activity allows you to change Customizing settings.

Prerequisites

You have logged on to the system in English in order to start with the installation of the Best

Practices Scenario.

Procedure

Run the following activity:

Transaction Code SCC4

SAP Menu Tools Administration Administration Client Administration

Client Maintenance

Then carry out the following steps:

1. Choose Display → Change.

2. Confirm the warning 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 allowed

• eCATT and CATT allowed.

5. Save.

6. Go back to the SAP Easy Access menu.

.1.2 Defining a Logical System

Use

The purpose of this activity is to create a logical system for your systems. To enablecommunication between systems within your system landscape, you must

1. Define the systems as logical systems.

2. Assign the logical system to your client.

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

Logical systems are defined cross-client.

© SAP AG of 11




Procedure

Carry out the following steps:

1. Access the transaction using:

Transaction Code SPRO

SAP

IMG Menu

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 system that you want to create.

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

Log. System Name

<Logical system 2>, for example DS7CLNT723 Your 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



Transaction Code SCC4

SAP R/3 Menu Tools Administration Administration Client Administration

Client Maintenance

2. Choose Display → Change.

3. Confirm the warning message The table is cross client .

4. Select your ERP 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.

© SAP AG of 11




.1.4 Creating an RFC User

Use

To enable communication between the SAP systems, you have to create an RFC user.

The RFC user in the application client enables multiple RFC connections. Skip this activity if anRFC User has already been created.

Procedure



Transaction Code SU01

SAP R/3 Menu Tools Administration User Maintenance Users

2. In the User field, enter RFCUSER .

3. Choose the Create.4. On the Maintain User screen, enter the following data on the Tab entry screens:

Address

Last Name RFCUSER

Function

Logon data

User type System

Password welcome

Profile

Profiles SAP_ALL

SAP_NEW

S_BI-WX_RFC

For the BI System: S_BI-WHM_RFC

Defaults

Logon Language EN

5. Save your entries.

.1.5 Opening Data Warehousing Workbench (only SAP BIsystem)

Procedure

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

SAP BW Modeling Data Warehousing Workbench: Modeling

Transaction Code RSA1

1. In the Replicate Metadata dialog box, choose Only Activate.

© SAP AG of 11




2. If a message appears that you are only authorized to work in client ... (Brain 009) refer toSAP Note 316923 (do not import the support package, but use the description under section Workaround ).

.1.6 Defining RFC-USER as default (only SAP BI and SCMsystem)

Procedure

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

Transaction Code RSA1

SAP BW Menu Modeling Data Warehousing Workbench: Modeling

1. On the Data Warehousing Workbench: Modeling screen choose Settings Global Settings.

2. In the Global Settings/Customizing dialog box choose Glob. Settings.

3. On the Display View “RSADMINA Maintenance View”: Details screen:

a. Choose Display Change.

b. Enter RFCUSER in the BW User ALE field.

c. Choose Save.

Leave the transaction in order to activate the entries you have made.

2 Cross Connectivity

This chapter describes all settings that are necessary to connect the components of the

SAP.system landscape with each other. The settings for each combination of two componentsto be connected are described in a separate structure node. The separate section headingsmake it possible to identify the activities required to connect certain components with eachother. The section headings for components that are not part of the installation can be skipped.

.2.1 Connecting SAP BI with SAP ERP, SAP CRM, SAP SRM

Procedure

To carry out the activity, choose one of the following navigation options in the SAP BI system:

Transaction code RSA1

SAP BW MenuModeling

Data Warehousing Workbench: Modeling

1. Choose Modeling.

2. Choose Source Systems.

3. Select SAP in the window on the right.

4. Choose the Context menu (right mouse click).

5. Choose Create.

6. Make the following entries:

Field Entry

Target computer (server) Server of the SAP R/3, SAP CRM or SAP SRM

system

System ID System ID of the SAP R/3, SAP CRM or SAP

© SAP AG of 11




SRM system

System number System number of the SAP R/3, SAP CRM or SAP SRM system

Background user in sourcesystem

RFCUSER

Password for source system welcome

Background user in BW RFCUSER (can not be changed in this activity)

Password for BW user welcome

9. On the dialog box Please log on as an administrator in the following screen chooseContinue.

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

11. On the dialog box New Source System Connection choose Continue.

12. On the Replicate Metadata dialog box, choose Only Activate.

.2.2 SAP SCM with SAP BI

2.2.1 Connecting SAP SCM to the SAP BI system

Procedure

To carry out the activity, choose the following navigation option in the SAP BI system:

SAP BW Role Menu Connecting SAP APO to the SAP BI system



Then carry out the following steps:

1. Choose Modeling.


3. Select Source Systems in the window on the right.


5. Choose Create.

6. Select SAP Business Information Warehouse.


Field Entry

Target computer (server) Server of the SAP SCM system

System ID System ID of the SAP SCM system

System number System number of the SAP SCM system


RFCUSER




8. In the dialog box Please log on as an administrator in the following screen chooseContinue.

© SAP AG of 11





10. On the dialog box New Source System Connection choose Continue.

11. On the Replicate Metadata dialog box, choose Only Activate.

2.2.2 Connecting SAP BI to the SAP SCM System

Procedure

Carry out the activity in the SAP SCM system.

SAP BW Modeling Data Warehousing Workbench: Modeling


1. Choose Modeling.

2. Choose Source systems.

3. Select Source systems in the window on the right.


5. Choose Create.

6. Select SAP Business Information Warehouse.


Field Entry

Available destination Destination of your SAP BI system


RFCUSER




8. On the dialog box Please log on as an administrator in the following screen chooseContinue.


10. On the dialog box Check RFC destination choose Use.

.2.3 Connectivity File System in SAP BI

This section describes all settings that are necessary for the connectivity for an external system- PC files on the Workstation (for example Excel files) or files on the application server in SAP

BI.

Procedure

1. From the SAP Menu in the BI system, choose:



2. Choose Modeling .


4. In the right-hand window mark the entry File below Source Systems.

© SAP AG of 11




5. Choose the context menu (right mouse click).

6. Choose Create.

7. In the Create Source System dialog box, enter the following data:

Field name User action and values

Logical source system FILE

Source system name FILE

8. Choose Enter.

9. Choose Back.

© SAP AG of 11

B84_BB_ConfigGuide_EN_HR

Documents

Transcript of B84_BB_ConfigGuide_EN_HR