b66_bpc075_bb_configguide_en_de.doc

EHP4 for SAP ERP 6.0

September 2011

English

BW Setting of BPC NW (B66)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

Building Block Configuration Guide

© SAP AG of 166

SAP Best Practices BW Setting of BPC NW (B66): Configuration Guide

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 changed 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 Corporation.

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 Enterprise 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, WebSphere, 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 Technology.

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, ByDesign, Clear Enterprise, SAP BusinessObjects Explorer, 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 SAP France in the United States and in other countries.

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 respect 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 AG of 166


Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

External Process

Business Process Alternative/Decision Choice

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 AG of 166


Contents

1 Purpose........................................................................................................................................ 6

2 BW Configuration......................................................................................................................... 6

2.1 BW Connectivity.................................................................................................................... 6

2.1.1 Transferring Application Component Hierarchy..............................................................6

2.1.2 Transferring Business Content DataSource into Active Version....................................6

2.1.3 Enhancing Business Content DataSource.....................................................................7

2.1.4 Setting Application Active Indicator..............................................................................11

2.1.5 Defining Logical Systems – SAP ECC/SAP BW..........................................................11

2.1.6 Assigning Logical System to Client – SAP ECC/SAP BW............................................12

2.1.7 Creating RFC User – SAP ECC/SAP BW....................................................................13

2.1.8 Creating RFC Destinations – SAP ECC/SAP BI..........................................................15

2.2 General Settings for BW Integration....................................................................................16

2.2.1 Opening the Data Warehousing Workbench................................................................16

2.2.2 Activating ICF Services – SAP BW..............................................................................16

2.2.3 Defining the RFC USER as default..............................................................................17

2.2.4 Maintaining proposal for users in the source system...................................................17

2.2.5 Creating Source System..............................................................................................17

2.2.6 Transfer Global Settings...............................................................................................18

2.2.7 Transferring Exchange Rates.......................................................................................19

2.2.8 Maintenance of Source System IDs.............................................................................19

2.2.9 Logistics Extraction Structures Customizing Cockpit...................................................19

2.2.10 Deleting the Content of the Setup Table......................................................................20

2.2.11 Performing Setup - SD Billing Documents....................................................................21

2.3 Activating Business Content................................................................................................22

2.3.1 Assigning Source System for Activation.......................................................................22

2.3.2 Activating Business Content: InfoObject Catalogs.......................................................23

2.3.3 Replicating DataSources..............................................................................................23

2.3.4 Creating InfoArea and InfoObjects of BPC Planning....................................................25

2.3.5 Activating Business Contents:InfoCube.......................................................................31

2.3.6 Creating DataStore Object of FI-GL.............................................................................32

2.3.7 Creating InfoCube of FI-GL..........................................................................................32

2.3.8 Creating InfoCube of SD Transaction Data..................................................................33

2.3.9 Creating InfoCube of BPC PL Staging Cube................................................................35

2.3.10 Creating InfoCube of BPC Sales Staging Cube...........................................................36

© SAP AG of 166


2.3.11 Creating Transformation and DTP of SD......................................................................38

2.3.12 Creating Transformation and DTP of FI-GL.................................................................43

2.4 Loading Data.......................................................................................................................48

2.4.1 Maintaining permitted extra characters........................................................................48

2.4.2 Loading FI-GL Transaction Data.................................................................................48

2.4.3 Loading SD Transaction Data.....................................................................................51

3 BPC Configuration...................................................................................................................... 53

3.1 Uploading Conversion File..................................................................................................53

3.2 Uploading Transformation File............................................................................................54

3.3 Uploading Data Into BPC....................................................................................................55

3.4 Creating process chain........................................................................................................56

© SAP AG of 166


BW Setting of BPC NW

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

2 BW Configuration

2.1 BW Connectivity2.1.1 Transferring Application Component Hierarchy

Carry out the following steps in SAP R/3.

Procedure1. Access the activity using one of the following navigation options:

Transaction code RSA9

IMG menu Integration with Other mySAP.com Components Data Transfer to the SAP Business Information Warehouse Business Content DataSources Transfer Application Component Hierarchy

© SAP AG of 166


2. Choose Yes and then input the package name and request number. If you don’t know which package should be used, please ask the help from your system administrator.

2.1.2 Transferring Business Content DataSource into Active Version

PrerequisitesCarry out the following steps in SAP R/3.

UseIf you need to transfer data from a source system into SAP BW using a Business Content DataSource, you have to first transfer the DataSource in the source system from the D version into the active version (A version).


SAP ECC menu Integration with Other mySAP.com Components Data Transfer to the SAP Business Information Warehouse Business Content DataSources Transfer Business Content DataSources


© SAP AG of 166


2. In the Installation of DataSource from Business Content view, expand the node SAP-R/3 (SAP Application Components), select the relevant DataSources or the

complete nodes (refer to the table below) and choose (Select Sub-tree +/-).

3. Once you have selected all required DataSources and nodes from the application toolbar, choose Activate DataSources.

4. If a dialog box appears requesting the user to enter a development class, enter the appropriate development class and choose Save.

5. Choose Back.

Active the following Datasources;

Path Relevant DataSource

SAP-R/3 SD 2LIS_13_VDITM

SAP-R/3 FI FI-GL 0FI_GL_12

© SAP AG of 166


You should note that some of the Business Content DataSources may have already been activated before. If you reactivate it, you must replicate the DataSource and activate the relevant Transfer Rule again in BW system, since the timestamp is changed in your reactivation. One way to avoid this is to check if the DataSource has not been activated before you activate it. You can mark one DataSource and then choose Version Comparison from the Application Toolbar. If version A is different from version D, that means this DataSource hasn’t been activated yet, thus you can activate it. Otherwise, do not activate this DataSource again.

2.1.3 Enhancing Business Content DataSource

2.1.3.1 Enhancing Business Content DataSource StructureCarry out the following steps in SAP R/3.

UseIn this step, you can enhance Business Content DataSource by appending structure of Extractor.


SAP ECC menu Integration with Other mySAP.com Components Data Transfer to the SAP Business Information Warehouse Postprocessing of Business Content DataSources Edit DataSources and Application Component Hierarchy


2. In the postprocess DataSource and Hierarchy screen, expand the node SAP-R/3 (SAP Application Components), select the relevant DataSources or the complete

nodes (refer to the table below) and choose (Select Sub-tree +/-).

3. Double-click the following DataSource:



4. In DataSource: Customer version Display screen, Double-click ExtractStruct.: MC13VD0ITM.

5. In Dictionary: Display Structure screen, choose Append Structure....

6. On popup screen, choose Continue.

7. On popup screen, make the following input:

Field name Description User action and values Note

Append Name ZBWSD

8. Choose Enter.

9. In Dictionary: Maintain Append Structure screen, Input the Short Description as the following:

© SAP AG of 166



Short Description BPC NW 1.75 SD DataSource Enhancement

10. Choose Components tab, Choose Component Type, input:

Component RType Component Type Note

ZZPRCTR PRCTR

11. Choose Save.


13. Choose Activate.

14. Ignore the warning messages.

15. Choose Back.

2.1.3.2 Modifying DataSource Structure FieldsCarry out the following steps in SAP R/3.

UseIn this step, you can modify the status of DataSource structure fields.

© SAP AG of 166



SAP ECC menu Integration with Other mySAP.com Components Data Transfer to the SAP Business Information Warehouse Postprocessing of Business Content DataSources Edit DataSources and Application Component Hierarchy


2. In the postprocess DataSource and Hierarchy screen, expand the node SAP-R/3 (SAP Application Components), select the relevant DataSources or the complete

nodes (refer to the table below) and choose (Select Sub-tree +/-).

3. Choose the following DataSource, choose Change DataSource:



4. On DataSource: Customer version Edit screen, modify the following attributes for field ZZPRCTR (Profit Center) :

Field Name Short Text Hide field Field only

ZZPRCTR Profit Center Not click Click

5. Choose Save.

2.1.3.3 Creating Customer Enhancement Project

UseCollective management of SAP Enhancements

Procedure1. Access the activity choosing one of the following navigation options:

SAP ECC menu Tool ABAP Workbench Utilities Enhancements Project Management

Transaction code CMOD

2. On the Project Management of SAP Enhancement screen, make the following input


Project ZBPC

Subobjects Attributes

3. Choose Create, on the dialog box screen, make the following input:


Short text BPC NW 1.75 DataSource Enhancement

4. Choose Enhancement assignments, choose Yes on the dialog box,

© SAP AG of 166



6. On the SAP Enhancements in Enhancement Project ZBPC screen, make the following input:

Field name Description User action and values

Note

Enhancement RSAP0001 Customer function calls in the service API

7. Choose Enter, and then choose Save.

8. Choose Back and then choose Activate.

ResultCustomer Enhancement Project is created, exit in the customer enhancement project is activated, and the developer can add code in the corresponding exit.

2.1.3.4 Creating Include Program of the Exit

UseActivate the system pre-defined include program, and tranfer the data from BW system to ERP system.




2. On the Project Management of SAP Enhancement screen, make the following input:


Project ZBPC


3. Choose Display.

4. On the Attributes of Enhancement Project ZBPC screen, choose components, then double-click EXIT_SAPLRSAP_001

5. On the Function Builder: Display EXIT_SAPLRSAP_001 double-click ZXRSAU01, Choose Enter.

6. Choose Yes on the popup dialog box to Create Object,


8. Choose Activate.

9. Choose from menu: Utilities More Utilities Upload/Download Upload, choose file: ...\Misc\BPC NW\ERP Enhancement\ZXRSAU01.txt

10. Choose Save and then choose Activate.

© SAP AG of 166


ResultProgram ZXRSAU01 is created.

2.1.3.5 Activating Enhancement

UseActivate Enhancement.




2. On the Project Management of SAP Enhancement screen, make the following input:


Project ZBPC


3. Choose Activate Project.

ResultEnhancement ZBPC is activated.

2.1.4 Setting Application Active Indicator This step has to be carried out in SAP R/3.

Procedure1. This is a cross-client operation. If it has been done for the same system before, just skip this

section

Transaction code BF11

2. Mark the checkbox on the BW application line

3. Save the change.

2.1.5 Defining Logical Systems – SAP ECC/SAP BW

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

1. Define the systems as logical systems.

© SAP AG of 166


2. Assign the logical system to your client.

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

You have to maintain this step both in SAP ECC and SAP BW

Logical systems are defined cross-client.


Transaction code SPRO

IMG menu SAP NetWeaver Application Server IDoc Interface / Application Link Enabling (ALE) Basic Settings Logical systems Define Logical System

© SAP AG of 166


2. Confirm the warning message Caution: The table is cross client.

3. Choose New entries.

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

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

Log. System Name

<Logical system>, for example EH4CLNT100 Your System

© SAP AG of 166


To designate logical systems, apply the naming convention

<XXX>CLNT<NNN>

where XXX is the system name

and NNN is the client.

6. Choose Save.

7. A transport request for Workbench appears.

8. Select an existing request or create a new request, if necessary. A transport request for Customizing appears. Select an existing request or create a new request, if necessary.

2.1.6 Assigning Logical System to Client – SAP ECC/SAP BW

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

You have to maintain /check this step both in SAP BI and SAP ECC.

Procedure1. Execute in BW system

2. Access the activity using the following navigation:

SAP ECC menu Tools Administration Administration Client Administration Client Maintenance

Transaction code SCC4

© SAP AG of 166


3. Follow the menu path Display Change.

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

5. Select your BW client.

6. Choose Details.

7. Enter the name of the logical system of your client.

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

9. Choose Back twice.

10. Execute in ECC system

SAP ECC menu Tools Administration Administration Client Administration Client Maintenance

Transaction code SCC4

© SAP AG of 166


11. Follow the menu path Display Change.

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

13. Select your ECC client.

14. Choose Details.

15. Enter the name of the logical system of your client.

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

17. Choose Back twice.

2.1.7 Creating RFC User – SAP ECC/SAP BW

UseTo 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 an RFC User has already been created.

You have to maintain /check this step in SAP BI and SAP ECC.

Procedure1. Execute the following steps in BW system.

2. Access the activity using one of the following navigation options:

SAP BW menu Tools Administration User Maintenance Users

Transaction code SU01

© SAP AG of 166


2. On the User Maintenance: Initial screen, enter the following data:

Field name Description User action and values Comment

User RFCUSER

© SAP AG of 166


3. Choose Create.

4. On the Maintain User screen, enter the following data:

Address

Last Name RFCUSER

Logon data

User type System

Password welcome1

Defaults

Logon Language EN

Profiles

Profiles S_BI-WHM_RFC

S_BI-WX_RFC

© SAP AG of 166


5. Choose Save.

6. Execute the following steps in ECC system.

SAP ECC menu Tools Administration User Maintenance Users

Transaction code SU01

© SAP AG of 166


7. On the User Maintenance: Initial screen, enter the following data:


User RFCUSER

© SAP AG of 166


8. Choose the Button Create.

9. On the Maintain User screen, enter the following data:

Address

Last Name RFCUSER

Logon data

User type SYSTEM

Password welcome1

Defaults

Logon Language EN

Profiles

Profiles S_BI-WX_RFC

© SAP AG of 166


If the RFC Destination is created in both system, please note the profiles to assign to the RFC user.

2.1.8 Creating RFC Destinations – SAP ECC/SAP BI

UseYou must maintain an RFC connection to your ECC system in the BI system.

You must maintain an RFC connection to your BI in the ECC system.


SAP ECC menu SAP NetWeaver Application Server IDoc Interface /

Application Link Enabling (ALE) Communication Create RFC

Connections

Transaction code SM59

© SAP AG of 166


2. Choose Create on the Configuration of RFC Connections screen.

3. On the upcoming screen, enter the following data:

Field name Value

RFC Destination XXX<CLNT>YYY

Connection Type 3

Description For example: ERP SYSTEM; BW SYSTEM

© SAP AG of 166


4. Choose the Enter.

5. The system changes automatically to the Technical Settings tab.

6. On this tab enter the following data:

Field name Value

Target Host Host name of your BI system or ECC system

System number the system number of your BI system or ECC system

© SAP AG of 166


7. Choose theEnter.

8. On the Logon & Security tab, enter the following data:

Field name Value

Trusted System No

Authorization for Destination Empty

Client The client number of your ECC client or BI client System

User For ECC:RFCUSER

For BW: RFCUSER

Password welcome1

© SAP AG of 166


9. Choose the Enter.

10. Confirm the information message User can be used for remote logon in target system.

11. On the MDMP & Unicode tab, choose Unicode.

12. Choose Save.

13. Choose the Button Remote Logon. you will logon to destination system and client.

14. Choose Back.

15. Choose Remote Logon.

16. Confirm the information message User can be used for remote logon in target system.

17. Choose Save.

2.2 General Settings for BW Integration2.2.1 Opening the Data Warehousing Workbench

This activity is only relevant for the SAP BW system.

Procedure1. Access the transaction using one of the following navigation options:

SAP BW menu Modeling Data Warehousing Workbench: Modeling


© SAP AG of 166


2. Mark the slection Do Not Show This Question Again and Chosse Yes to confirm the warning message.

2.2.2 Activating ICF Services – SAP BW

UseThe ICF services required by SAP BI are delivered preconfigured but for security reasons inactive. All the services needed by SAP BI require activation.


Transaction code SICF

IMG menu Tools Administration Administration Network HTTP Service Hierarchy Maintenance

© SAP AG of 166


2. On the Maintain Services screen, enter the data:


Hierarchy Type SERVICE

© SAP AG of 166


3. Choose Execute.

4. On the Maintain Service screen, expand the hierarchy of Default_host..

5. Expand SAP.

6. Right click the BW entry.

7. From the context menu choose ‘Activate service.’

8. In the confirmation dialog box, choose the Button Yes to activate all sub-nodes below the BW node in the hierarchy.

9. Choose Back.

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

2.2.3 Defining the RFC USER as default This activity has to be carried out in SAP BW

Procedure1. To Global Settings, choose:

SAP BW menu Information Systems Business Information Warehouse Modeling Data Warehousing Workbench: Modeling


© SAP AG of 166


2. On the Data Warehousing Workbench: Modeling screen:

Choose menu Setting Global Setting .

You could also run transaction code RSCUSTA to define the RFC user.

3. Choose Change ,enter the BW User ALE value:RFCUSER

4. Choose Save and Exit .

2.2.4 Maintaining proposal for users in the source system This activity has to be carried out in SAP BW

Procedure1. To Maintain proposal for users in the source system,choose.

SAP BW menu SAP Customizing Implementation Guide SAP NetWeaver Business Intelligence Links to Other Source Systems Connection Between SAP Systems and BW Maintain proposal for users in the source system (ALE communication)

Transaction code RSCUSTV3

© SAP AG of 166


2. Enter the SS user ALE field : RFCSYSUSER

3. Choose Save and EXIT.

2.2.5 Creating Source SystemThis activity has to be carried out in SAP BW system. If your ERP system and BW system use the same client, this step can be skipped.

Procedure1. To create source system, choose:

SAP BW menu Information Systems Business Information Warehouse Modeling Data Warehousing Workbench Modeling


© SAP AG of 166


2. On the Workbench: Modeling screen,Choose Source Systems, Right -click SAP in the right hand window and choose Create.

3. On the Create SAP Source System screen, Enter the following enteries:

Field name Value

Available destination ( RFC Destination such as: ERPCLNT102)

Background user in source system

RFCUSER

Password for source system user welcome1

Background user in BW RFCUSER

Password for BW user welcome1

© SAP AG of 166


4. If the logon screen popup, logon the SAP ERP client with a dialog user. Confirm all warning messages.

5. Dialog text Replicate Metadata pop-up, choose Active only. If you choose the Replicate as well, this step will take 1 hour, don’t stop the transaction.

6. Choose continue.

7. Choose Exit.

2.2.6 Transfer Global SettingsThis activity has to be carried out in SAP BW. If your ERP system and BW system used same client, this step skip.

Procedure1. To Transfer Global Settings, choose:



© SAP AG of 166


2. On the Data Warehousing Workbench: Modeling screen:

a. Choose Source Systems.

b. In the right hand window, select the ERP source system.

c. From the context menu, choose Transfer global settings.

3. In the Transfer global table contents frame of the Transfer global settings: Selection screen, select the checkboxes for the settings you want to transfer from your ERP source system:

a. Currencies, to transfer the currency keys

b. Units of measurement, to transfer units of measurement

c. Fiscal year variants, to transfer fiscal year variants

4. In the Mode frame, choose Update Tables.

5. Choose Execute.

6. Go Back twice.

2.2.7 Transferring Exchange RatesThis activity has to be carried out in SAP BW. If your ERP system and BW system used same client, this step skip.

Procedure1. To Transfer Exchange Rates, choose:



© SAP AG of 166


2. On the Data Warehousing Workbench: Modeling screen, Choose Source Systems. Right -click your R/3-Source System in the right hand window and choose Transfer Exchange Rates

3. On the Tranfer Exchange Rates；Selection. Choose Update exchange rates, Choose Exctue.

4. Choose Exit twice.

2.2.8 Maintenance of Source System IDsThis activity has to be carried out in SAP BW

Procedure1. To Maintenance of Source System IDs:



2. On the Data Warehousing Workbench: Modeling screen, choose Tools Asgnment of Srce Syst. To Srce Syst. ID from the menu.

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

4. Choose Enter.

5. Enter a text description for the ERP systems.

6. Choose Save.

7. If the Empty source system IDs are not saved dialog box appears, choose Enter.

8. Go Back.

2.2.9 Logistics Extraction Structures Customizing Cockpit

ProcedureThis activity must be performed out in the SAP ERP system.

1. Access the transaction using one of the following navigation options:

IMG menu Integration with Other mySAP.com Components Data Transfer to the SAP Business Information Warehouse Settings for Application-Specific DataSources (PI) Logistics Managing Extract Structures Logistics Extraction Structures Customizing Cockpit

Transaction code LBWE

2. Expand the following nodes:

Logistics applications 13:SD Billing BW Extract structures

3. For node MC13VD0ITM: Extraction SD Billing Document BW: Document Item, click Inactive in the Update column of the line containing the extract structure.

4. In the Notifications MCEX 146 dialog box, choose Continue. The entry changes from Inactive to Active.

© SAP AG of 166


If the system prompts you for a customizing request, enter the appropriate customizing request or create a new one.In the Update Mode column of the line containing the logistics applications (13 – SD Billing BW), the entry should be Queued Delta. To change the entry click it. In the Select Update Mode dialog box, select Queued Delta and choose Continue.

5. Go Back.

ResultYou have activated the update of the extract structures. Transaction data can be written into the extract structures from now on.

2.2.10 Deleting the Content of the Setup Table

UseTo upload existing transaction data to your BW you call up selected data records of sales and trigger the statistical update for the BW extraction structures for sales orders. To ensure that there is no existing data in the relevant tables, you delete the content of the respective tables before you trigger the statistical update for sales orders data.

ProcedureThis activity must be performed in the SAP ERP system.


IMG menu Integration with Other mySAP.com Components Data Transfer to the SAP Business Information Warehouse Settings for Application-Specific DataSources (PI) Logistics Managing Extract Structures Initialization Delete the Contents of the Setup Tables

Transaction code LBWG

2. In the Delete setup data view, enter 13 in the Application field.

3. Choose Execute.

4. Confirm the warning with Yes.

5. Go Back.

ResultYou have deleted the content of the setup tables for billing documents. This ensures that duplicate data will not be used during the data update.

2.2.11 Performing Setup - SD Billing Documents

UseTo upload existing deliveries data to your BW you call up selected invoices and trigger the statistical update for the BW extraction structures for existing invoices.

© SAP AG of 166


Completing setup tables is a critical action that should be performed with caution. For large data amounts, this can take longer than one overnight period and may need to be performed over a weekend. You can also split up the setup into several parts.

ProcedureThis activity must be performed in the SAP ERP system.


IMG menu Integration with Other mySAP.com Components Data Transfer to the SAP Business Information Warehouse Settings for Application-Specific DataSources (PI) Logistics Managing Extract Structures Initialization Filling in the Setup Table Application-Specific Setup of Statistical Data SD-Billing Documents - Perform Setup

Transaction code OLI9BW

2. On the Statistical Setup from Old Documents: Billing Docs screen, make the following entries:

Field Entry

Name of run <Any name>

New run X

Date of Termination <A date in the future> For example, tomorrow's date.

Time of termination <A time in the future>

No. tolerated faulty documents

<Any number> For example, 99.

3. Choose Execute.

4. In the Information dialog box, confirm the message with Continue.

If you want to continue with the next activity, do not leave the transaction.

ResultYou have triggered the statistical update for the BW extraction structures for existing invoices. The data is available to be uploaded to BW. The statistical update used here corresponds to the method you chose in the Logistics Extraction Structures Customizing Cockpit.

2.3 Activating Business Content2.3.1 Assigning Source System for Activation

UseWhen you activate Business Content, DataSources from source systems are assigned to InfoSources in BW. If you do not select a source system, all source systems are automatically assigned. If you have several source systems, this may take a lot of time because also transfer rules have to be activated for each DataSource from each source system.

© SAP AG of 166


However, an assignment of a DataSource to an InfoSource may not be necessary for all existing source systems.

Assign only the source systems you need to load data from for the Business Content Objects that you are going to activate.

You can subsequently change the selection you made.

The assignment of source systems is only relevant for transfer rules, DataSources and InfoPackages. If there is more than one source system, only those objects assigned to the specified source system are collected for the transfer. Objects that have not been assigned to the specified source systems are ignored.

Procedure1. Access the activity using the following navigation:

SAP BW menu Information SystemsBusiness Information WarehouseModeling Data Warehousing Workbench: Business Content

Transaction code RSORBCT

2. In the Data Warehousing Workbench: Business Content view choose Edit Source System Assignment.

3. In the Select Source System dialog box select the checkbox in the column Selected in the row containing the source systems you need to load data from, and deselect other source systems which you do not need if necessary.

4. Choose Continue.


ResultBy assigning the source systems, you limit the assignment to the DataSources from the assigned source systems only. This reduces the time for activation.

© SAP AG of 166


2.3.2 Activating Business Content: InfoObject Catalogs

UseSome activities in this chapter are also required for other building blocks, such as Plant Maintenance Data. If you have performed them already, you don’t need do it again. In that case you can skip certain activities in this chapter.

Carry out the following steps in SAP BW.

Procedure1. Access the activity using the following navigation:

SAP BW menu Information SystemsBusiness Information WarehouseModeling Data Warehousing Workbench: Business Content


© SAP AG of 166


2. In the Data Warehousing Workbench: BI Content screen:

At the top of the right frame, choose Grouping and select only necessar.

At the top of the right frame, choose Collection Mode and select Collect Automatically.

In the left frame, select Object Types.

In the middle frame, expand InfoObject Catalog and double-click Select Objects.

3. On the Input help for Metadata dialog box.Select the following InfoObject catalogs:

Info-object Description

0CHANOTASSIGNED Unassigned characteristics

© SAP AG of 166


4. For multiple selection use the Ctrl-Key.Choose Transfer Selections.If a dialog box Exceeded Runtime when collecting objects appears choose Continue.

5. At the top of the right frame, choose Install and select Install in background..

6. If a new screen appears choose Transfer all without dialog.

7. A monitor section appears. Choose Back.


ResultYou have started a background job in order to activate the Business Content. Check the status of the background job using transaction SM37.

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

2.3.3 Replicating DataSources

UseMetadata (that is data describing the structure of data from an SAP source system) is read in the source system using the function Replicate DataSources and replicated or created in the SAP Business Information Warehouse. The properties of a DataSource that are required for communication or data transfer are replicated in BI by a metadata upload.

PrerequisitesThe SAP source system has been created. All required Business Content DataSources have been activated in the source system.

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

Procedure 1. Access the activity using the following navigation:



© SAP AG of 166


2. On the Data Warehousing Workbench: Modeling screen carry out the following steps:

a. In the left frame choose Source Systems.

b. Expand the node SAP and Select your ERP source system in the right-hand window.

c. From the context menu, choose Display DataSource Tree.3. On the right frame, expand the Metadata tree of SAP - SAP Application Components -Financial

Accounting - Financial Accounting: General Ledger

If you only see Unassigned Nodes here, you have to replicate Tree Metedata via right clicking DataSources for XXXCLNTXXX.

4. Right click Financial Accounting: General Ledger, choose Replicate DataSources from context menu.

5. If the Unknown DataSource dialog box occurs, choose This and the following <…>as DataSource(RSDS).

6. Double-click your new DataSources.

7. In the Change DataSource XXX_XX_XX Screen click Display/Change DataSource butoon to enter the change mode.

8. Save your new DataSources and Active it.

9. Repeat steps 1 to 8 to activate the metadata tree of SAP-SAP Application Components-Sales and Distribution.

10. Choose Back.

ResultMetadata about all active DataSources is now available in SAP BW.

© SAP AG of 166


2.3.4 Creating InfoArea and InfoObjects of BPC Planning

UseThis activity provider you the processing steps on how to create InfoObjects which will be used in BPC planning.

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



© SAP AG of 166


Then carry out the following steps:

1. On the Data Warehousing Workbench: Modeling screen choose InfoObjects.

2. Right click InfoObjects in the right-hand frame and choose Create InfoArea.

3. In the Create InfoArea dialog box:

a. Make the following entries:

Field Entry

InfoArea ZBPC

Long description BPC NW 1.75

© SAP AG of 166


b. Choose Enter.

4. On the Data Warehousing Workbench: Modeling screen, right click the InfoArea ZBPC and choose Create InfoObject Catalog.

5. In the Edit InfoObject Catalog dialog screen, make the following entries and create:

Field Entry

InfoObjCat ZBPC_CHAR

Long description ZBPC_CHAR

InfoObject Type Char.

© SAP AG of 166


6. On the Data Warehousing Workbench: Modeling screen, right click ZBPC_CHAR and choose Create InfoObject…

7. In the Create Characteristic screen, make the following entries:

Field Entry

Char. ZBPC_ACC

Long description Acconut

© SAP AG of 166


8. Save it and go to the next screen, make the following entries:

In the General tab:

Field Entry

Data Type CHAR

Length 20

Attribute Only

Characteristic Is Document Property

Transfer routine exists

© SAP AG of 166


In the Master data/texts tab:

Field Entry

With master data X

With texts X

Long text exists X

Texts language dependent X

InfoArea /CPMB/XX_XX_XX (Your appplication set)

© SAP AG of 166


9. Save and Active it.

10. Right click ZBP_CHAR and choose Create InfoObject…


Field Entry

Char. ZBPC_CUST

Long description Customer

© SAP AG of 166