General Settings for BI Integration[1]

8/2/2019 General Settings for BI Integration[1]

http://slidepdf.com/reader/full/general-settings-for-bi-integration1 1/12

SAP BW 7.0

July 2006

English

B03: General Settings for BI

Integration

SAP AGDietmar-Hopp-Allee 1669190 Walldorf Germany

Building Block Configuration Guide



SAP Best Practice General Settings for BI Integration: 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 withoutthe 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 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, Informix, i5/OS, POWER, POWER5, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registeredtrademarks 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 aretrademarks or 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 andservices mentioned herein as well as their respective logos are trademarks or registeredtrademarks 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. Datacontained in this document serves informational purposes only. National product specifications mayvary.

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 representationor warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect tothe materials. The only warranties for SAP Group products and services are those that are set forthin the express warranty statements accompanying such products and services, if any. Nothingherein should be construed as constituting an additional warranty.

© SAP AG Page 2 of 12




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 asF2) 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 these

words and characters with appropriate entries.





Content

General Settings for BI Integration ............................................................................................... .... 5

1 Configuration ............................................................................................................................. 5

.1.1 General Settings in SAP ERP ........................................................................................... . 5

1.1.1 Transferring Application Component Hierarchy ............................................ .............. . 5

.1.2 General Settings in SAP SCM ............................................................................... ..... ....... 5

1.2.1 Transferring Application Component Hierarchy (SAP SCM) ....................... .............. .... 6

.1.3 General Settings in SAP CRM ......................................................................... .............. .... 6

1.3.1 Transferring Application Component Hierarchy (SAP CRM) .................................. ....... 6

1.3.2 BI Adapter: Version Management: Metadata .................................................... ..... ....... 6

.1.4 General Settings in SAP BI................................................................................................ 7

1.4.1 Activating ICF Services ................................................................................. .............. . 7

1.4.2 Maintaining Profiles .................................................................................................. .... 81.4.3 Settings for Material Number Conversion .............................................................. ....... 8

1.4.4 Transferring Global Settings from Source Systems .................................. ..... .............. . 9

1.4.5 Maintaining Source System IDs .................................................................................... 9

1.4.6 Activating Business Content: InfoObject Catalogs ......................................... ............. 10

1.4.7 Activating Business Content: Currency Translation Type ............................................ 11





General Settings for BI Integration

Use

This section describes all activities that must be performed for BI Integration for each systeminvolved regardless of the analysis that is going to be performed

Prerequisites

Connectivity between BI and all other involved systems must be set up.Refer to the relevant sections of BI Connectivity building block.

1 Configuration

.1.1 General Settings in SAP ERP

UseThis section describes the general settings necessary for BI Integration in ERP.If ERP is not involved in your scenario skip this section.

1.1.1 Transferring Application Component Hierarchy

Procedure

This step has to be carried out in the SAP ERP 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 development class,. enter adevelopment class in the customer’s namespace and chooseSave or Local object .

.1.2 General Settings in SAP SCM

Use

This section describes the general settings necessary for the BI Integration in SCMIf SCM is not involved in your scenario skip this section.





1.2.1 Transferring Application Component Hierarchy (SAPSCM)

Procedure

This step has to be carried out in the SCM 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 development class, enter adevelopment class in the customers namespace and chooseSave or choose Local object .

If no error message is sent the application component hierarchy has been transferredsuccessfully.

.1.3 General Settings in SAP CRM

Use

This section describes the general settings necessary for BI Integration in CRM.If CRM is not involved in your scenario skip this section.

1.3.1 Transferring Application Component Hierarchy (SAPCRM)

Procedure

This step has to be carried out in the CRM system.


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 development class, enter adevelopment class in the customers namespace and chooseSave or choose Local object .

If no error message is sent the application component hierarchy has been transferredsuccessfully.

1.3.2 BI Adapter: Version Management: Metadata

Procedure

Transaction code BWA5

Carry out the following steps:

1. On the BW Adapter: Version Management: Metadataview choose Select Delta.





2. Choose Copy DataSources.

.1.4 General Settings in SAP BI

1.4.1 Activating ICF Services

UseThe ICF services required by SAP BI are delivered preconfigured but for

security reasons inactive. All the services needed by SAP BI require activation.

Procedure

Transaction code SICF

1. On the Maintain Services screen enter Hierarchy Type Service and choose Execute.

2. On the Maintain service screen expand default_host -> sap.

3. Right click on the ‘bw’ entry.4. From the context menu choose ‘Activate service’ .

5. In the confirmation dialog box, select the option to activateall sub-nodes below the ‘bw’node in the hierarchy.

6. Choose Back .

You may be asked for a transport to record the change.





1.4.2 Maintaining Profiles

Transaction code RZ10

1. On the Edit Profiles view make the following entries:

Field Entry

Profile DEFAULT (enter via matchcode)

Version is filled automatically

Extended Maintenance X

2. Choose Change.

3. On the Maintain R/3 Profile ‘DEFAULT’ Version ‘XXXXXX’ view look for the followingparameters. If a parameter doesn’t exist create it. Make sure that all parameters have the

value as specified in the table belowParameter name Parameter value

login/system_client BW client you’re working in

login/create_sso2_ticket 1

login/accept_sso2_ticket 1

4. Choose Back .

5. In the dialog box chooseYes.

6. On the Edit Profiles view save the profile.

7. In the Activate profile dialog box choose Yes.

8. Confirm the Dialog box.

9. In the Information dialog box choose Continue.

10. In the Caution! dialog box choose Continue.

The effect of activating a profile is simply that the profile is stored at operating systemlevel. For the profile to take effect for a particular application server, you have to restartthe application server.

1.4.3 Settings for Material Number Conversion

ProcedureTransaction code OMSL

1. On the Change View "Material Number Formats": Detailsview make the same entries as in theSAP ERP source system. Look up the same transaction in the source system.

2. Choose Save. If the system prompts you for a transport request enter the relevant requestnumber or create a new request.

3. Choose Back twice.





1.4.4 Transferring Global Settings from Source Systems

Use

In this activity you transfer fiscal year variants, units of measures and currency units from your source system.

If you do not use the settings from your source systems you will have to maintain the settings in BICustomizing.In this case skip this step.

Prerequisites

In your ERP/CRM/SCM source system fiscal year variants, units of measures and currency unitshave been maintained.

Procedure

This activity has to be carried out in the BI system. Perform this activity for every ERP/CRM/SCMsource system that you will use in SAP BI.

To transfer global settings from a source system choose:

SAP Menu Modeling Data Warehousing Workbench: Modeling


Then carry out the following steps:

1. On the Data Warehousing Workbench: Modeling screen:

a. Choose Source Systems.

b. In the right hand window select the source system from which you would like totransfer the global settings.

c. From the context menu choose Transfer global settings.

2. On the Transfer global settings: Selection view in the frame Transfer global table contentsselect the checkboxes for the settings you want to use from your ERP source system:

a. Currencies to transfer the currency keys from the source system.

b. Units of measurement to transfer units of measurement from the source system.

c. Fiscal year variants to transfer fiscal year variants

3. In the frame Mode choose Update Tables.

4. Choose Execute.

5. Choose Back twice.

1.4.5 Maintaining Source System IDs

Procedure

This activity has to be carried out in the SAP BI system.

To maintain the Source System IDs, carry out the following steps:

1. On the SAP Easy Access SAP Business Information Warehousescreen, choose:

SAP Menu Modeling Data Warehousing Workbench: Modeling






2. Choose Asgnmt of Srce Syst. to Srce Syst. ID from the Menu Tools.

3. Enter a unique 2 digit Source System ID for all of your source systems.

4. Choose Enter .

5. Enter a text/ description for the source systems.

6. Choose Save.

7. If dialog box with the informationEmpty source system IDs are not saved comes up chooseEnter .

8. Choose Back .

These entries cannot be changed.

1.4.6 Activating Business Content: InfoObject Catalogs

ProcedureThis activity has to be carried out in the BI system:

SAP Menu Modeling Data Warehousing Workbench: BusinessContent

Transaction code RSORBCT

Then carry out the following steps:

1. On the Data Warehousing Workbench: Business Content screen:

a. At the top of the right hand frame, chooseGrouping and select In Data Flow Before.

b. At the top of the right hand frame, chooseCollection mode and select collect

automatically .

c. In the left hand frame, selectObject Types.

d. In the middle frame, expand InfoObject Catalog and make a double-click onSelect Objects.

2. In the Input help for Metadata dialog box.

a. Select the following InfoObject catalog:

InfoObject Catalog

(technical name)

InfoObject Catalog

(description)

0CHANOTASSIGNED Unassigned characteristics

b. Choose Transfer Selections.

c. If a dialog box appears Exceeded runtime when collecting objectschoose Continue.

3. At the top of the right frame, choose Install and select Install in Background .

4. In the Install Business Content in the Background dialog box choose Yes.


6. Choose Exit .





Result

You have started a background job in order to activate the Business Content. Check the status of the background job using transactionSM37.

Make sure that the current job has finished successfully before you proceed with theactivation of further objects.

1.4.7 Activating Business Content: Currency Translation Type

Procedure

This activity has to be carried out in the BI system:

SAP Menu Modeling Data Warehousing Workbench: BusinessContent

Transaction code RSORBCT

Then carry out the following steps:2. On the Data Warehousing Workbench: Business Content screen:

a. At the top of the right hand frame, chooseGrouping and select Only Necessary Objects.

b. At the top of the right hand frame, chooseCollection mode and select collect automatically .

c. In the left hand frame, selectObject Types.

d. In the middle frame, expand Currency Translation Type and make a double-click onSelect Objects.

7. In the Input help for Metadata dialog box.

a. Select the following Object:

Object name

(technical name)

Long Description

0HRFIXCUR Fixed target currency, current date

b. Choose Transfer Selections.

c. If a dialog box appears Exceeded runtime when collecting objectschoose Continue.

8. At the top of the right frame, choose Install and select Install in Background .

9. In the Install Business Content in the Background dialog box choose Yes.


11. Choose Exit .

Result

You have started a background job in order to activate the Business Content. Check the status of the background job using transactionSM37.





Make sure that the current job has finished successfully before you proceed with theactivation of further objects.


Documents

General Settings for BI Integration[1]