$gplqlvwudwru :runehqfk - knowsap€¦ · create molap cube.....158 ods object ... types of data...

$GPLQLVWUDWRU�:RUNEHQFK

��

��

��

�

5 H O H D V H �� $

SAP Online Help Business Information Warehouse

Administrator Workbench 30A 2

&RS\ULJKW

© Copyright 2001 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 priornotice.

Some software products marketed by SAP AG and its distributors contain proprietary softwarecomponents of other software vendors.

Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registeredtrademarks ofMicrosoft Corporation.

IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®, AS/400®,OS/390®, and OS/400® are registered trademarks of IBM Corporation.

ORACLE® is a registered trademark of ORACLE Corporation.

INFORMIX®-OnLine for SAP and Informix® Dynamic ServerTM

are registered trademarks of InformixSoftware Incorporated.

UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.

HTML, DHTML, XML, XHTML 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.

SAP, SAP Logo, R/2, RIVA, R/3, ABAP, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAPEarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over theworld. All other products mentioned are trademarks or registered trademarks of their respectivecompanies.



,FRQV

,FRQ 0HDQLQJ

Caution

Example

Note

Recommendation

Syntax



Administrator Workbench ...................................................................................................................... 12

Metadata Repository .......................................................................................................................... 14

Searching for Metadata .................................................................................................................. 15

Displaying Graphics........................................................................................................................ 16

Exchange of Metadata in XML Format According to CWM............................................................ 17

Business Content (Versions).............................................................................................................. 19

Installing Business Content ............................................................................................................ 21

Installing BW Statistics (Technical Content)................................................................................... 25

Modeling............................................................................................................................................. 27

InfoObject ....................................................................................................................................... 28

InfoObject Catalog ...................................................................................................................... 29

Creating InfoObject Catalogs .................................................................................................. 30

Additional InfoObject Catalog Functions ................................................................................. 31

InfoObject Naming Conventions ................................................................................................. 32

Creating InfoObjects: Characteristics ......................................................................................... 33

Tabstrip: General..................................................................................................................... 34

Tabstrip: Business Explorer .................................................................................................... 36

Mapping Geo-Relevant Characteristics............................................................................... 38

Static and Dynamic Geo-Characteristics ......................................................................... 40

Shapefiles..................................................................................................................... 42

Delivered Geo-Characteristics ..................................................................................... 44

Maintaining the SAPBWKEY for Static Geo-Characteristics ........................................... 45

Creating a Local Copy of the Shapefile........................................................................ 47

Downloading BW Master Data into a dBase File ......................................................... 48

Maintaining the SAPBWKEY Column .......................................................................... 49

Uploading Edited Shapefiles into BW .......................................................................... 50

Geocoding........................................................................................................................ 51

Downloading BW Master Data into a dBase File ......................................................... 52

Geocoding Using ArcView GIS .................................................................................... 53

Converting dBase Files into CSV Files ........................................................................ 55

Tabstrip: Master Data/Texts .................................................................................................... 56

Tabstrip: Hierarchy .................................................................................................................. 58

Tabstrip: Attributes .................................................................................................................. 59

Tabstrip: Compounding ........................................................................................................... 61

Navigation Attribute ................................................................................................................. 63

Creating Navigation Attributes............................................................................................. 64

Transitive Attributes as Navigation Attributes...................................................................... 65

Creating InfoObjects: Key Figures.............................................................................................. 69

Tabstrip: Type/Unit .................................................................................................................. 70



Tabstrip: Aggregation .............................................................................................................. 72

Non-Cumulatives..................................................................................................................... 73

Non-Cumulative Key Figures............................................................................................... 75

Time Reference Characteristic ............................................................................................ 76

Validity Period...................................................................................................................... 78

Maintaining the Validity Period......................................................................................... 80

Transferring Non-Cumulative Data into BW ........................................................................ 81

Aggregational Behavior of Non-Cumulative Values ............................................................ 82

Procedure for Evaluating Non-Cumulative Values .............................................................. 85

Tabstrip: Additional Properties ................................................................................................ 88

Editing InfoObjects...................................................................................................................... 89

Additional Functions in the InfoObject Maintenance .................................................................. 90

Data Targets ................................................................................................................................... 92

Use of Master Data and Master Data-Bearing Characteristics................................................... 93

Master Data Types: Attributes, Texts, and Hierarchies .......................................................... 94

Master Data Maintenance ....................................................................................................... 95

Creating and Changing Master Data ................................................................................... 96

Maintaining Time-Dependent Master Data ...................................................................... 97

Time-Dependent Master Data from Different Systems.................................................... 99

Deleting Master Data at Single Record Level.................................................................... 100

Deleting Master Data and Texts for a Characteristic ............................................................ 101

Activating Master Data and Texts ......................................................................................... 102

Simulate Loading of Master Data.......................................................................................... 103

Master Data Lock .................................................................................................................. 104

InfoCube.................................................................................................................................... 105

BasicCubes ........................................................................................................................... 106

Transactional InfoCubes ....................................................................................................... 108

Creating InfoCubes ............................................................................................................... 110

Dimension.............................................................................................................................. 113

Line Item Dimension.............................................................................................................. 114

Additional Functions in InfoCube Maintenance..................................................................... 115

Checking the Data Loaded in the BasicCube.................................................................... 117

Checking the Data Consistency of an InfoCube................................................................ 118

Non-Cumulative Value Parameter Maintenance ............................................................... 119

DB Memory Parameters .................................................................................................... 120

Partitioning......................................................................................................................... 121

Partitioning InfoCubes using the Characteristic 0FISCPER .......................................... 123

Deleting the InfoCube and InfoCube Content ....................................................................... 124

Overview of Loadable InfoSources for an InfoCube ............................................................. 125

Aggregates ............................................................................................................................ 126

Aggregation Levels ............................................................................................................ 127



Aggregation Level .......................................................................................................... 128



Editing Aggregates ............................................................................................................ 133

Creating the First Aggregate for an InfoCube................................................................ 137

Displaying Aggregates and their Components .............................................................. 138

Activating and Filling Aggregates ...................................................................................... 141

Rolling up Data into an Aggregate..................................................................................... 144

Efficiently Loading Data into Aggregates........................................................................... 146

Further Editing Functions for Aggregates.......................................................................... 147

Automatically Selecting and Optimizing Aggregates......................................................... 149

Proposals from Queries ................................................................................................. 150

Proposals from BW Statistics......................................................................................... 151

Optimizing Proposed Aggregates .................................................................................. 152

MOLAP Store ........................................................................................................................ 153

MOLAP Aggregate............................................................................................................. 155

MOLAP Cube (Root Aggregate)........................................................................................ 157

Create MOLAP Cube......................................................................................................... 158

ODS Object ............................................................................................................................... 160

Scenario for ODS Objects ..................................................................................................... 164

Example for Updating Data in an ODS Object ...................................................................... 166

Creating ODS Objects........................................................................................................... 167

Transactional ODS object ..................................................................................................... 169

ODS Object Performance...................................................................................................... 171

Further Processing of ODS Objects...................................................................................... 172

Deleting from the Change Log .............................................................................................. 174

Status Overview of ODS Objects .......................................................................................... 175

ODS Data and External Applications .................................................................................... 176

Hierarchies ................................................................................................................................ 177

Hierarchy Nodes.................................................................................................................... 179

Link Nodes......................................................................................................................... 180

Loading Hierarchies .............................................................................................................. 181

Loading Subtree Hierarchies. ............................................................................................ 182

Creating Hierarchies.............................................................................................................. 184

Options for the Combination of Nodes and Leaves........................................................... 186

Reporting-relevant Hierarchy Settings............................................................................... 187

Editing Hierarchies ................................................................................................................ 189

Copying Hierarchies .............................................................................................................. 190

Activating Hierarchies............................................................................................................ 191

Node Attributes...................................................................................................................... 192

Hierarchy Versions ............................................................................................................ 193



Maintaining Hierarchy Versions ..................................................................................... 194

Time-dependent Hierarchies ............................................................................................. 195

Loading Time-dependent Hierarchies............................................................................ 197

Hierarchy Intervals............................................................................................................. 198

Reversing the Sign ............................................................................................................ 199

Hierarchy Modeling Options.................................................................................................. 200

Update Rules ............................................................................................................................ 201

Update Options ..................................................................................................................... 202

Update Process..................................................................................................................... 204

Creating Update Rules for Data Targets............................................................................... 206

Creating a Start Routine .................................................................................................... 207

Update Types .................................................................................................................... 208

Update Methods ................................................................................................................ 210

Automatic Time Conversion........................................................................................... 212

Time Distribution ............................................................................................................ 213

Splitting Key Figure Values............................................................................................ 215

Different Rules for Different Key Figures of a Characteristic ......................................... 216

Toolbox and Formula Editor........................................................................................... 217

Update Routines ................................................................................................................ 219

Creating Update Routines.............................................................................................. 221

Changing Update Rules ........................................................................................................ 223

Transferring Update Rules from a Template......................................................................... 224

Currency Translation in the Update ...................................................................................... 225

Additional Functions in Update Rule Maintenance ............................................................... 227

Source System ............................................................................................................................. 228

Connection between Source Systems and BW ........................................................................ 229

Creating an SAP Source System.............................................................................................. 230

Creating an SAP Source System Automatically.................................................................... 232

Creating an SAP Source System Manually........................................................................... 233

Creating External Systems ....................................................................................................... 235

Creating File Systems............................................................................................................... 236

Data Extraction from SAP Source Systems.............................................................................. 237

DataSource............................................................................................................................ 238

Transferring Business Content DataSources into Active Version ..................................... 240

Maintaining DataSources .................................................................................................. 241

Assigning DataSources to InfoSources and Fields to InfoObjects.................................... 242

Extract Structure.................................................................................................................... 243

Transfer Structure ................................................................................................................. 244

Delta Process ........................................................................................................................ 245

Transferring Data in XML Format ............................................................................................. 246

XML DataSource (BW DataSource with SOAP Connection)................................................ 248



Creating an XML DataSource............................................................................................ 250

Loading XML Data................................................................................................................. 252

The Structure of an XML Document...................................................................................... 255

Metadata Upload for SAP Systems .......................................................................................... 257

Updating Metadata for Flat Files or External Systems ............................................................. 259

Check Source System .............................................................................................................. 260

Data Mart Interface ................................................................................................................... 261

Data Mart Interface Between Several Systems .................................................................... 262

Using the Data Mart Interface............................................................................................ 264

Generating the InfoCube Export DataSource.................................................................... 266

Generating the Master Data Export DataSource............................................................... 267

Transferring Transaction Data for the Data Mart Interface................................................ 268

Transferring Texts and Hierarchies for the Data Mart Interface........................................ 269

Data Mart Interface in the Myself System ............................................................................. 270

InfoSource{} .................................................................................................................................. 271

InfoSource Types...................................................................................................................... 273

Scenarios for Flexible Updating................................................................................................ 275

Creating InfoSources (R/3 Source System).............................................................................. 277

Communication Structure...................................................................................................... 278

Maintaining Communications Structures with Flexible Updating....................................... 279

Maintaining Communications Structures for an InfoSource with Direct Updating............. 281

Check for Referential Integrity ........................................................................................... 282

Transfer Structure ................................................................................................................. 283

Maintaining Transfer Structures ........................................................................................ 284

Processing Transfer Rules .................................................................................................... 285

Start Routine in Transfer Rules ......................................................................................... 287

Creating Transfer Routines ............................................................................................... 288

Maintaining InfoSources (Flat Files) ......................................................................................... 289

Uploading Transaction Data from Flat Files.......................................................................... 290

Maintaining Transaction Data InfoSources using Flat Files .............................................. 292

Uploading Master Data from Flat Files.................................................................................. 294

Uploading Hierarchies from Flat Files ................................................................................... 296

Structuring a Flat Hierarchy File ........................................................................................ 298

Preview and Simulation of Loading Data from Flat Files ...................................................... 302

Maintaining InfoSources (External System).............................................................................. 303

Info Providers ............................................................................................................................... 304

InfoSet....................................................................................................................................... 306

Creating InfoSets................................................................................................................... 308

Editing InfoSets ..................................................................................................................... 309

Variants: Editing InfoSets ...................................................................................................... 310

Screen Layout: Changing InfoSets ....................................................................................... 313



Join Control ........................................................................................................................... 315

Defining Join Conditions........................................................................................................ 319

Temporal Join........................................................................................................................ 321

Classic InfoSet ...................................................................................................................... 324

Setting-up a Role for the InfoSet Query ............................................................................ 325

Processing Classic InfoSets and Assigning Roles ............................................................ 326

InfoSet Query..................................................................................................................... 328

Creating InfoSet Queries ................................................................................................... 329

SAP RemoteCube..................................................................................................................... 331

Creating a SAP RemoteCube ............................................................................................... 332

RemoteCube............................................................................................................................. 333

Virtual InfoCubes with Services ................................................................................................ 335

MultiProviders ........................................................................................................................... 338

Staging Scenarios ........................................................................................................................ 340

Data Storage Properties ........................................................................................................... 341

Staging Scenarios with Persistent Data Storage...................................................................... 344

Staging Scenarios without Persistent Data Storage................................................................. 347

Administration................................................................................................................................... 349

Scheduler...................................................................................................................................... 350

Maintaining InfoPackages......................................................................................................... 351

Procedure for SAP Systems ................................................................................................. 352

Procedure for Flat Files ......................................................................................................... 353

Procedure for External Systems with BAPI Functions .......................................................... 354

Scheduling InfoPackages ......................................................................................................... 355

Tabstrip: Select Data ................................................................................................................ 357

Variable Selection Change in Background Processing......................................................... 359

Tabstrip: Select Hierarchy......................................................................................................... 361

Tabstrip: Processing ................................................................................................................. 363

Tabstrip: Data Targets .............................................................................................................. 366

Automatic Request Deletion from the InfoCube when Loading ............................................ 367

Tabstrip: Update Parameters.................................................................................................... 368

Tabstrip: External Data ............................................................................................................. 370

Variants ..................................................................................................................................... 372

Maintaining Data Transfer Control Parameters for DataSources ............................................. 373

Handling Double Data Records ................................................................................................ 374

Treating Data Records with Errors ........................................................................................... 375

Monitoring ..................................................................................................................................... 377

Monitor ...................................................................................................................................... 378

Selection Screen ................................................................................................................... 380

Request Overview ................................................................................................................. 381

Detail Screen......................................................................................................................... 382



Traffic Lights .......................................................................................................................... 385

Wizard ................................................................................................................................... 386

Persistent Staging Area ............................................................................................................ 387

Types of Data Update with PSA............................................................................................ 389

Checking and Changing Data ............................................................................................... 391

Checking and Changing Data Using PSA-APIs .................................................................... 392

Versioning.............................................................................................................................. 394

Deleting Requests from the PSA .......................................................................................... 395

InfoPackage Group ................................................................................................................... 396

Maintaining InfoPackage Groups .......................................................................................... 397

Scheduling an InfoPackage Group ....................................................................................... 398

Adjusting Changes to Hierarchies and Attributes ..................................................................... 399

Status Overview of ODS Objects.............................................................................................. 401

Managing Data Targets ................................................................................................................ 402

Managing InfoCubes................................................................................................................. 403

InfoCube Content .................................................................................................................. 405

Transferring InfoCube Contents ........................................................................................ 408

Selective Deletion .............................................................................................................. 409

InfoCube Performance .......................................................................................................... 410

Compressing InfoCubes........................................................................................................ 412

Requests in the InfoCube...................................................................................................... 413

Automatic Further Processing............................................................................................... 415

Restructuring InfoCubes........................................................................................................ 416

Managing ODS Objects ............................................................................................................ 417

Contents of an ODS Object................................................................................................... 418

Requests in an ODS object ................................................................................................... 419

Reconstructing an ODS object .............................................................................................. 421

Managing InfoObjects ............................................................................................................... 422

Process Control ............................................................................................................................ 423

Process Chains......................................................................................................................... 424

Processes.............................................................................................................................. 427

Start Process ..................................................................................................................... 428

Application Processes ....................................................................................................... 429

Remote Process Chain .................................................................................................. 431

ABAP Programs............................................................................................................. 432

Implementing Your Own Process Type ......................................................................... 434

Collection Process ............................................................................................................. 437

Process Chain Maintenance ................................................................................................. 438

Creating a Process Chain.................................................................................................. 440

Process Chain Attributes ................................................................................................... 444

Process Chain Log ............................................................................................................ 446



Subsequent Processing ............................................................................................................ 448

Event Collector.......................................................................................................................... 449

Creating an Event Collector .................................................................................................. 450

Scheduling the Event Collector ............................................................................................. 451

Editing an Event Collector ..................................................................................................... 452

Reporting Agent ............................................................................................................................... 453

Defining Exceptions Setting.......................................................................................................... 454

Tabstrip: Exception Reporting................................................................................................... 456

Edit Follow-Up Action: Send Message ..................................................................................... 457

Editing the Follow-Up Action: Alert Monitor Entry..................................................................... 460

Defining the Print Setting.............................................................................................................. 461

Tabstrip: Print Settings.............................................................................................................. 463

Defining the Print Layout........................................................................................................... 465

Defining a Web Templates Setting............................................................................................... 469

Parameter DATA_MODE.......................................................................................................... 472

Control Query for Pre-calculating Web Templates ................................................................... 474

Defining the Value Set Setting...................................................................................................... 475

Processing the Scheduling Package............................................................................................ 476

Documents ....................................................................................................................................... 479

Hyperlinks to Documents.............................................................................................................. 482

Searches in Documents ............................................................................................................... 483

Document Management in BW .................................................................................................... 485

Tabstrip: Content Repository .................................................................................................... 486

Tabstrip: Indexes for Searches................................................................................................. 488

Tabstrip: Generic Properties ..................................................................................................... 491

Processing Documents in the AWB Documents View ................................................................. 492

Documents for Metadata........................................................................................................... 494

Documents as Online Documentation................................................................................... 495

Documents for Master Data ...................................................................................................... 497

Documents for Transaction Data .............................................................................................. 498

Processing Documents in the Documents Screen....................................................................... 499

Creating Documents..................................................................................................................... 502

Importing Documents ................................................................................................................... 504

Exporting Documents ................................................................................................................... 505

Translating a Text for BW Objects ................................................................................................... 507

Step-By-Step Instructions ................................................................................................................ 509



$GPLQLVWUDWRU�:RUNEHQFK

3XUSRVH

The Administrator Workbench is the tool for controlling, monitoring and maintaining all of theprocesses connected with data staging and processing in the Business Information Warehouse.

,QWHJUDWLRQ

The data for the SAP Business Information Warehouse that has been staged with the help of theAdministrator Workbench can be evaluated and presented with the Business Explorer reporting tool.

)XQFWLRQV

The Administrator Workbench encompasses the following functional areas:

• Metadata Repository [Seite 14]

• Installing Business Content [Seite 21]

• Modeling [Seite 27]

• Administration [Seite 349]

• Reporting Agent [Seite 453]

• Documents [Seite 479]

• Translating Texts for BW Objects [Seite 507]

From BW systems you can get to the Administrator Workbench by choosing %:�$GPLQLVWUDWLRQ�→$GPLQLVWUDWRU�:RUNEHQFK.

When you call the Administrator Workbench, a navigation menu appears on the left of the screen. Youcan use the pushbuttons to open the individual areas of the Administrator Workbench, and in turndisplay the views and functions you can use in these areas. With one click you can call up the viewsand functions on the right of the screen.

The pushbutton toolbar of the Administrator Workbench includes a pushbutton for hiding thenavigation menu, pushbuttons for frequently used functions and pushbuttons that are relevant for the



individual areas. Pushbuttons, which refer to certain views or functions, are displayed on the right ofthe screen.

The Administrator Workbench also contains a jump to the transport system. You can find additionalinformation in the System Administration section of the BW documentation under Transport System[Extern].



0HWDGDWD�5HSRVLWRU\

8VH

With the HTML-based BW Metadata Repository, you can access the information onBW Metadata as well as the most important properties of the objects and the links toother objects. You can search and exchange Metadata, export HTML pages anddisplay the graphics of the objects.

)XQFWLRQV

In the Metadata Repository, you can display active objects in the system ($FWLYDWHG2EMHFWV) and objects delivered by SAP (%XVLQHVV�&RQWHQW). The object typesavailable in the respective systems are presented in the right-hand window.Hyperlinks on the object types bring you to a list of all objects for that object type.From this object list you can navigate directly to the individual object information.

Use the pushbuttons 3UHYLRXV�3DJH and 1H[W�3DJH in the function toolbar tonavigate in the Metadata repository. The pushbutton 0DLQ�3DJH brings you back tothe initial page whenever you want.

6HDUFK�LQ�WKH�0HWDGDWD�5HSRVLWRU\

This searches for the technical name, the short and long texts and the delivered SAPdocumentation of the objects in the Metadata Repository.

0HWDGDWD�([FKDQJH

You can export Metadata to another system, import it from another system, orinterchange it between two systems. When you exchange data, general informationand dependences are integrated for display.

+70/�([SRUW

Active objects can be exported as HTML pages, as can SAP delivered objects.

*UDSKLFV

Metadata can be displayed by XML-based vector graphics formats for documentsand the Internet as VML graphics and SVG graphics.

6HH�DOVR�

Searching for Metadata [Seite 15]

Displaying Graphics [Seite 16]



6HDUFKLQJ�IRU�0HWDGDWD

3URFHGXUH

1. In the Metadata Repository choose 6HDUFK�LQ�0HWDGDWD�5HSRVLWRU\.

If you are using the search function for the first time, you must first set up the search index.For this, choose ([WUDV�Å 0HWDGDWD�6HDUFK�Å 6WUXFWXUH�6HDUFK�,QGH[� The search index isstructured in the background.

2. Enter the search term you want.

You can search by the object’s title or technical name. Only a full text search, not a genericsearch, is possible.

The system searches all the objects in the search index. You can restrict the search toInfoObjects, InfoCubes or queries.

5HVXOW

A list appears with the objects found, separated according to active objects in the system (activatedobjects) and SAP delivery objects in the system (Business Content). The hit lists are sorted by objecttype/symbol, number and technical name.

You can navigate directly to the individual object information via the hyperlinks of the short text andlong text fields as well as the technical name hyperlinks.



'LVSOD\LQJ�*UDSKLFV1. In the Metadata Repository choose ([WUDV�Å *UDSKLFV�

2. Choose either 90/��9HFWRU�0DUNXS�/DQJXDJH��,(�) or 69*��6FDODEOH�9HFWRU�*UDSKLFV) as thegraphics format.

The display in VML format is only be possible as of MS Internet Explorer 5.

Graphics in SVG format can be displayed using a Browser Plug-In, with MS InternetExplorer 4 and Netscape Navigator 4, for example.

3. In the Metadata Repository, look for the object you want displayed graphically and navigate via thehyperlink to the information on this object.

4. If it is possible to display the graphics for an object, it will be in the object information under*UDSKLFDO�'LVSOD\ as a hyperlink.

For roles, workbooks and InfoSources, you can display the 1HWZRUN�'LVSOD\�LQ�WKH�'DWD�)ORZ.

With InfoCubes you have the additional option of a schematic display as well as a compactdisplay.

With queries, you can display a query preview next to the network display.

5. Navigate via the hyperlink to the graphics display that you want.

You can navigate from the graphic via hyperlinks into the object information of the displayedobjects.

If you want to change the size of a graphic, choose the pushbutton &KDQJH�6L]H�RI�*UDSKLFand enlarge or reduce the value set in the dialog box that follows. The default setting is 1.00.

You can print the graphic on display by choosing the pushbutton 3ULQW.

Furthermore, you can use the context menu of the installed Browser in the graphicswindow.



([FKDQJH�RI�0HWDGDWD�LQ�;0/�)RUPDW�$FFRUGLQJ�WR�&:0

8VH

In order to exchange metadata (BW objects) between different systems, you can use the XML formatin the Administrator Workbench functional area 7UDQVSRUW�&RQQHFWLRQ. In doing so, one of the modelsderived according to the CWM (Common Warehouse Metamodel) standard is used.

You can find additional information about the CWM standard on the OMG (ObjectManagement Group) homepage: www.omg.org.

You can find additional information about the Administrator Workbench function area7UDQVSRUW�&RQQHFWLRQ under Transport Systems [Extern].

,QWHJUDWLRQ

You can export or import the XML files ('RZQORDG or 8SORDG for PC) by using the AdministratorWorkbench.

Furthermore, an +773�VHUYLFH is available under 6$3�%:�;0/�&:0. You can request thismetadata in the way that you would like from a Web server by using this HTTP service. In order torequest metadata for an object, use the following URL:

http://<Server>:Port/SAP/BW/XML/CWM?/CLASSID=<Klasse>&ID=<Name>&DETAIL=X&OBJECTVERSION=A

You have the following expressions for substitution:

7HUP ,QIRUPDWLRQ

<Server>:Port Specify the name of the VHUYHU and the SRUW for the BW system you want.

http://LS0027.WDF.SAP-AG.DE:1080/

SAP/BW/XML/CWM?...

<Class> Specify the name of the FODVV for the BW object you want.

As an example for the class ,QIR&XEH:CLASSID=COM.SAP.BW.CWM.OLAP.INFOCUBE

You get the BW model in XML format by using the followingURL:

http://<Server>:Port/SAP/BW/XML/CWM?

CLASSID=METAMODEL

<Name> Specify the technical name for the %:�REMHFW you want.

• You get an 2YHUYLHZ�RI�$OO�2EMHFWV by using the following:


CLASSID=LIST&ID=&DETAIL=&OBJECTVERSION=A

• You get an 2YHUYLHZ�RI�$OO�%XVLQHVV�&RQWHQW�2EMHFWV�by usingthe parameter &OBJECTVERSION=D, namely




CLASSID=LIST&ID=&DETAIL=&OBJECTVERSION=A

• You get an Overview of All Objects of a Specific Type by usingthe ID specifications in the URL.

For example, you specify the following for InfoCubes:


CLASSID=LIST&ID=COM.SAP.BW.CWM.OLAP.INFOCUBE

&DETAIL=&OBJECTVERSION=A

)XQFWLRQV

The exchange of metadata includes:

�,PSRUW from another system

�([SRUW into another system

The objects that also exist for BAPIs (%XVLQHVV�$SSOLFDWLRQ�3URJUDPPLQJ�,QWHUIDFHV) aresupported with details. You can only import these objects after you have changed them.You are still unable to import non-BW objects.

You can export the current BW model according to the XMI (XML Metadata Interchange) standard.This is possible by using the SAP report RSO_REPOSITORY_EXCHANGE_XML.

You can find additional information about the XMI standard on the OMG homepage:www.omg.org.



%XVLQHVV�&RQWHQW��9HUVLRQV�

'HILQLWLRQ

SAP delivers Business Content in the SAP Delivery Version (D version).

8VH

You need to transfer the Business Content objects in the active version (A version) in order to be ableto work with them.

6WUXFWXUH

In the Business Information Warehouse a differentiation is made between the following objectversions:

9HUVLRQ 0HDQLQJ

'�HOLYHU\� SAP delivery version

$�FWLYH� Active version

0�RGLILHG� Modified version

,QWHJUDWLRQ

The following diagram displays the Business Content versions

$�FWLYH�

'�HOLYHU\�

0�RGLILHG�

Version

11 11 11

11 11 11 22

11 11 22 22 22

22 22

11

SAP-Delivery 2. SAP-Delivery

BCT-Installation 2. BCT Installation(Adjustment)

The black arrows represent how the versions are used in the delivery process:

1. SAP delivery

− SAP delivers the Business Content objects in the '�9HUVLRQ.

− Changes are saved in the 0�YHUVLRQ�

− Active Business Content is saved in the $�YHUVLRQ�

Only those objects that were stored in the A version are exported from the developmentsystem. When importing into the target system, these objects, dependent on object type,are either imported directly into the active version or in a modified version.



Here are some examples of objects imported into the active version:

• Currency Translation Type

• InfoObject Catalog

Here are some examples for object types that are firstly imported into a modified versionand activated after being imported.

• InfoObject

• InfoCube

2. SAP Delivery (Business Content upgrade)

− SAP delivers the Business Content objects in a new '�9HUVLRQ.

− The customer can compare the new Business Content with his/her active customer version,and either adopt the new version or merge it with his/her version.

• $GRSW��The customer version is deleted and replaced by the new Business Contentversion.

• 0HUJH��The “total” is made from both objects and saved as a new customer version.

The characteristics merger, for example, is the same as the construction of theattribute union.. The customer must select which ones they want to adopt for certainproperties in dialog mode. Not all objects support merging.

In the $GRSW�%XVLQHVV�&RQWHQW�function area in the Administrator Workbench, you can collect andtransfer the Business Content delivered by SAP. In this way, all additional necessary objects are takeninto account automatically, along with the sequence activation. You can choose whether you want tocopy, compare, or not transfer the Business Content objects.

When activating Business Content, the SAP delivery version is adopted and the activecustomer versions are overwritten if you do not execute a match-up

6HH�DOVR�

Installing Business Content [Seite 21]



,QVWDOOLQJ�%XVLQHVV�&RQWHQW

8VH

You need to transfer the Business Content objects from the SAP delivery version ( D version) into theactive version (A version) in order to be able to work with them. You can find further information underBusiness Content (Versions) [Seite 19].

3URFHGXUH

1. In the main menu of the SAP Business Information Warehouse select %:�$GPLQLVWUDWLRQ ->$GPLQLVWUDWRU�:RUNEHQFK�

2. Select the %XVLQHVV�&RQWHQW�function area using the corresponding pushbutton in the left-handnavigation window or by -XPS��!�,QVWDOO�%XVLQHVV�&RQWHQW

With the pushbutton 1DYLJDWLRQ�:LQGRZ�2Q�2II on the application toolbar in theAdministrator Workbench, you can show or hide the left-hand navigation window. Weassume that the navigation window remains hidden in the following section.

3. If you want to assign source systems, select $VVLJQPHQW�6RXUFH�6\VWHP. The 6HOHFW�6RXUFH6\VWHP�DV�'HIDXOW�dialog window appears.

Select one or more source systems by setting the corresponding indicators in the 'HIDXOW$VVLJQPHQW�column.

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

If you do not select a source system, DOO source systems are automatically assigned.

You can subsequently change the selection you made using 6RXUFH�6\VWHP�$VVLJQPHQW .

4. Change the required settings in the following selection list:

*URXSLQJ

Choose the objects that you want the system to consider. The groupings summarize all theobjects of an area.

*URXSLQJ ,QIRUPDWLRQ

Only necessary objects (standard setting) Only those objects that are really necessaryfor the action, that is, the transport of theselected objects, are taken into account(minimal selection).

,Q�GDWD�IORZ�EHIRUH All objects are collected that submit data to acollected object.

,Q�GDWD�IORZ�DIWHU All objects are collected that obtain data froma collected object.

,Q�GDWD�IORZ�EHIRUH�DQG�DIWHU All objects are collected that both submit andcollect data.

If you change the default setting ( RQO\�QHFHVVDU\�REMHFWV��the new setting will be used asa standard for the user.



&ROOHFWLRQ�0RGH

Select how you want to collect the objects:

&ROOHFWLRQ�0RGH ,QIRUPDWLRQ

DXWRPDWLF�FROOHFWLRQ��standard setting). The data is collected directly when theobjects are selected.

6WDUW�PDQXDO�FROOHFWLRQ The data is only collected when you select &ROOHFW�GHSHQGHQW�REMHFWV.

5. Select an 2EMHFW�7\SH�you want to transfer.

You have various selection options in the navigation window in the %XVLQHVV�&RQWHQW�functionarea of the Administrator Workbench.

When you select an object type, the arrangement and selection of the existing objects aredisplayed in the tree structure of the central screen area as below:

2EMHFW�7\SH�LQ�WKH�$GPLQLVWUDWRU:RUNEHQFK�1DYLJDWLRQ�:LQGRZ�

'LVSOD\�REMHFWV�LQ�WKH�WUHH�VWUXFWXUH�LQ�WKHFHQWUDO�VFUHHQ�DUHD�

'DWD�WDUJHWV�E\�,QIR$UHDV List of InfoCubes and ODS objects byInfoAreas.

,QIR2EMHFWV�E\�DSSOLFDWLRQ�FRPSRQHQWV� List of objects by InfoObject catalog and byInfoAreas

,QIR6RXUFHV�E\�DSSOLFDWLRQ�FRPSRQHQWV� List of InfoSources for master data andtransaction data.

5ROHV List of the standard and branch roles.

2EMHFW�7\SHV List of objects by type (InfoArea, application,InfoObject catalog, role, workbook, queryelement, InfoSet query, Crystal Reportstemplate, Web template, Web item, savedquery view, MultiProvider, InfoCube,InfoObject, InfoSet, Classic InfoSet, ODSobject, update rules, InfoSource transactiondata, transfer rules, source system,InfoPackage group, InfoPackage, processchain, Reporting Agent, report/reportinterface, currency conversion type

2EMHFWV�LQ�%:�3DWFK List of installed BW patches including list ofobjects newly delivered or re-delivered withthe respective patch.

3DFNDJH List of packages in which there are SAPobjects.

6. Select the object(s) you want to transfer in the central screen area and transfer them into the right-hand &ROOHFWHG�2EMHFWV�screen area by drag and drop.

Using 6HDUFK�IRU�2EMHFW, you can also search for objects by a string (for example,0CUST) or by pattern (for example, 0CUST_*B).

You can display a value help for every object type: By double clicking on 6HOHFW2EMHFWV in the tree structure of the corresponding object type, the screen 9DOXH�+HOS�IRU

0HWDGDWD appears. Select the required objects. Choose 7UDQVIHU�VHOHFWLRQV�



You can only use Business Content DataSources of a source system for transferring datain BW, when you have transferred these in their active forms and then copied them intothe BW system.

The system displays the selected object(s) and all dependent objects in the &ROOHFWHG�2EMHFWVscreen area. To reduce the time taken to access the objects when wanting to use them again,the collected objects are stored by default in the Repository Cache [Extern].

When transferring the objects to the &ROOHFWHG�2EMHFWV screen area, the objects are addedat the same time to the tree structure of the corresponding object type in the centralscreen area and are saved for the respective user. This SHUVRQDO�REMHFW�OLVW�is availableevery time the program is restarted.

To remove objects from the personal list, select the object in question and choose5HPRYH�2EMHFW�IURP�'LVSOD\ via the context menu or via .

Objects that are listed in several tree structures are only displayed as changeable the first timethey appear. Each time they are listed again, they are highlighted in gray and are not ready forinput.

7. Check the following columns in the &ROOHFWHG�2EMHFWV screen area:

The following Business Content objects are highlighted in the�7UDQVIHU column by default:

• Objects transferred for the first time

• Objects delivered again in a new version from Business Content.

When the SAP delivery version and the active version can be compared, a check box is shown inthe column &RPSDUH��;��RU�&RS\�

There is a check mark in this checkbox by default. In this case, your version is comparedwith the new SAP delivery version and complimented.

If you remove the indicator then the new SAP delivery version is copied in its entirety.

• Date symbol: The object is already available in an active version. However, the activeversion belongs to an older Content Release. We recommend that you adopt the newversion

• Gray Selection : There is an active version in the system, but the object status is givenas inactive. The object has to be subsequently edited.

In the $FWLYH�9HUVLRQ�$YDLODEOH column, there are the following display options:

,QGLFDWRU 0HDQLQJ

No Indicator The object is not available in an activeversion.

The object is available in an active version.You can decide whether to retain this versionor adopt again.

8. Change the required settings in the following selection list :

7UDQVIHU�7\SH ,QIRUPDWLRQ

6LPXODWH�WUDQVIHU A test is made to see if errors are likely tooccur during the transfer. The most importantobjects can be checked in the simulation.However, this does not include all dependentobjects Therefore, only use the simulation asan orientation help to be able to recognizeerrors and remove them.



7UDQVIHU The selected objects are transferredimmediately.

7UDQVIHU�LQ�EDFNJURXQG The selected objects are transferred in thebackground.

7UDQVIHU�DQG�WUDQVSRUW The selected objects are transferredimmediately and then written to a transportrequest in the connection.

We recommend 7UDQVIHU�LQ�WKH�%DFNJURXQG��because transferring a large number ofobjects and especially changing already active objects can take up a lot of time.

9. You can find out if errors have occurred during the installation of Business Content from a log,which you can request using the /RJ pushbutton. Repair the errors in the respectivemaintenance transaction. Try to transfer the Business Content again.

6HH�DOVR�

Transferring Business Content DataSources into the Active Version [Seite 240]



,QVWDOOLQJ�%:�6WDWLVWLFV��7HFKQLFDO�&RQWHQW�

8VH

BW statistics are delivered as part of technical content. The 7HFKQLFDO�&RQWHQW role contains all of theobjects that you need to install BW statistics, in particular the BW statistics MultiProvider (previouslycalled the BW statistics MultiCube). You install the technical content in the same way that you installBusiness Content in the ,QVWDOO�%XVLQHVV�&RQWHQW�functional area of the Administrator Workbench. SeeTransferring Business Content [Seite 21]

The version of BW statistics that is delivered with BW2.0B contains InfoObjects that have changed to such anextent that they are no longer compatible with theInfoCube 0BWTC_C01 that is delivered with BW 1.2B.

If you want to continue working with this InfoCube you can choose QRW to install the newInfoCubes, changed InfoCubes, and so on, from the BW statistics.

We recommend that you use the version of BW statistics that isdelivered with BW 2.0B. Install RQO\ the new InfoCubes.

3UHUHTXLVLWHV

We recommend that you make or check the following settings before you install the technical content.

1. Choose the 6RXUFH�6\VWHP�$VVLJQPHQW function. Check that the BW system is highlighted inthe list of source systems. If the BW system is not highlighted, the system is not able to collectDataSources and InfoPackages, for example.

2. In the BW system, call transaction RSA5 ,QVWDOO�%XVLQHVV�&RQWHQW to install the DataSources fromthe application components TCT (0BWTC* and 0TCT*). Although the DataSources are in thesame system, they are not made available automatically.

3. In the 0RGHOLQJ functional area of the Administrator Workbench under 6RXUFH�6\VWHPV, replicatethe DataSources for the BW system.

Since standard InfoSources are prepared for BW statistics, the usual data staging procedure is usedto load information into the InfoCubes in the BW statistics.

3URFHGXUH

1. In the %XVLQHVV�&RQWHQW functional area of the Administrator Workbench you can install theInfoCubes under either the %:�6WDWLVWLFV�InfoArea�or the %:�7HFKQLFDO�&RQWHQW�role:

,QVWDOOLQJ�WKH�,QIR&XEHV�XQGHU�WKH�7HFKQLFDO�&RQWHQW�,QIR$UHD��!%:�6WDWLVWLFV

a. From the context menu (right mouse-click) of the %:�6WDWLVWLFV InfoArea, choose the ,QVHUW2EMHFWV�IRU�&ROOHFWLRQ function.

b. First, choose the grouping function for QHFHVVDU\�REMHFWV�RQO\� Choose ,QVWDOO�

c. When the installation is complete, choose the grouping function LQ�GDWD�IORZ�EHIRUH�and�LQGDWD�IORZ�DIWHUZDUGV for the same InfoCubes. This includes in the collection the queries andInfoSources that are also delivered. Choose ,QVWDOO�

,QVWDOOLQJ�WKH�%:�7HFKQLFDO�&RQWHQW�UROH

a. From the context menu (right mouse-click) of the %:�7HFKQLFDO�&RQWHQW�role, choose the,QVHUW�2EMHFWV�IRU�&ROOHFWLRQ function.

b. Choose the grouping GDWD�IORZ�. Choose ,QVWDOO� The system installs the new InfoCubesand InfoSources automatically.



2. InfoPackages and the InfoPackage groups are not collected using the procedurementioned above.

a. Choose REMHFW�W\SHV in the navigation window of the Administrator Workbench.

b. From the InfoPackage group , choose %:�6WDWLVWLFV

Additional InfoPackage groups are listed here.

Master data / texts

Master data

Transaction data

Initialization of the delta process

Delta process

For more information see Delta Process [Seite 245]

When you have installed the Business Content, the %:�6WDWLVWLFV InfoPackage groupappears under the 1RW DVVLJQHG node.



0RGHOLQJ

3XUSRVH

In modeling, you can create and edit all the objects and rules of the Administrator Workbench that areneeded for data transport, update and analysis. You can also execute functions related to these.

The objects are displayed in modeling in a tree structure. The objects are sorted here according tohierarchical criteria. You can select the corresponding maintenance dialog or carry out the relevantfunctions from the context menu (right mouse click). Double clicking on an object brings you to thecorresponding maintenance dialog.

3URFHVV

The basic information stores in BW are InfoObjects [Seite 28] Using InfoObjects, Information ismapped in a structured form. This is required for constructing data targets [Seite 92] Data istransferred from specified source systems [Seite 228] into BW. By applying transfer rules, InfoObjectsthat logically belong together are group into InfoSources [Seite 271] The data is then updated intodata targets, if necessary using update rules. The data is finally made available to the InfoProvider[Seite 304] so that it can be evaluated in queries.

6HH�DOVR�

You can find information on the different VHWWLQJV�in AWB modeling in the Settings in the AdministratorWorkbench [Extern] section.

You can find information on the possibility of displaying the data flow for BW objects in the Data FlowDisplay [Extern].



,QIR2EMHFW

'HILQLWLRQ

Business evaluation objects (customers. sales revenues,...) are known in BW as InfoObjects. They aredivided into characteristics, key figures, units, time characteristics and technical characteristics (forexample, request number).

InfoObjects with attributes or texts can be either a pure data target [Seite 92] or an InfoProvider [Seite304] (if it is being reported).

8VH

InfoObjects are the basic information providers of BW. They structure the information needed to createdata targets.

6WUXFWXUH

The FKDUDFWHULVWLFV of an InfoObject are reference objects (keys) with dimensions that are related (forexample, ‘region’ and ‘land’ are the geographical dimensions of ‘customer’. 7LPH�FKDUDFWHULVWLFV arecharacteristics that are assigned to the dimension of time. Their dependencies are therefore alreadyknown, since the time is predefined. The NH\�ILJXUHV of an InfoObject form the data part. That is, theydeliver the values that you want to report on. Key figures can be quantities, amounts or number ofitems. These values must have XQLWV to give them meaning. The WHFKQLFDO�FKDUDFWHULVWLFV�of anInfoObject are only of structural use within BW. An example is the request number, which is takenwhen you load a request and helps you find the request at a later date.

InfoObjects are structured by attributes and/or hierarchies. The company location can be an attributeof ‘customer’, for example. You can use these to form customer groups, for example, for a specificregion. You can also define a hierarchy to make the structure of the characteristic ‘customer’ moreclear in its overview.

,QWHJUDWLRQ

�� &RPSRQHQW�RI�DQ�,QIR6RXUFH

An InfoSource is always a quantity of InfoObjects that logically belong together.

�� ,QIR6RXUFHV�ZLWK�)OH[LEOH�8SGDWLQJ

An InfoSource with flexible updating can be updated in any data targets (with the exception ofhierarchies). Update rules are created for this InfoSource.

InfoObjects can be used in as many InfoSources and InfoCubes/ODS objects as youwant.

�� ,QIR6RXUFHV�ZLWK�'LUHFW�8SGDWLQJ

Master data (characteristics with attributes, texts or hierarchies) of an InfoObject can bewritten directly (without update rules) to the master data table with an InfoSource with directupdating.

�� &UHDWLQJ�D�'DWD�7DUJHW�,QIR3URYLGHU

An InfoCube/ODS object consists of a number of InfoObjects.

− The characteristics, units and time characteristics are essentially the key fields/data fields ofthe InfoCube/ODS object.

− The key figures are the data fields (or facts) or values of the InfoCube/ODS object.



,QIR2EMHFW�&DWDORJ

'HILQLWLRQ

An InfoObject catalog is a collection of InfoObjects grouped according to application-specific criteria.There are two types of InfoObject catalogs: &KDUDFWHULVWLF�and .H\�ILJXUH�

8VH

An InfoObject catalog is assigned to an InfoArea.

It is also purely an organizational aid, and is not for intended for reporting purposes.

For example, all the InfoObjects that are used for reporting in the area of “Sales and Distribution”, canbe grouped together in one InfoObject catalog. This makes it much easier for you to handle what mightturn out to be a very large number of InfoObjects for any given context.

An InfoObject can be included in several InfoObject catalogs.

You can choose an InfoObject catalog to use as a filter for the template when you are defining anInfoCube or an ODS object.



&UHDWLQJ�,QIR2EMHFW�&DWDORJV

3UHUHTXLVLWHV

• Ensure that all the InfoObjects that you want to transfer into the InfoObject catalog are active.

• Create and activate any InfoObjects that are not available already [Seite 33].

• If you want to define an InfoObject catalog in the same way as an InfoSource, then thecommunication structure [Seite 279] for the InfoSource has to be available and active.

3URFHGXUH

1. Create an InfoArea, to which you want to assign the new InfoObject catalog. This function is onthe first level of the hierarchy in the Administrator Workbench under InfoObjects.

2. Use the right mouse button to create an InfoObject catalog in the InfoArea. If you want to make acopy of an existing InfoObject catalog, specify a reference InfoObject catalog.

3. Choose either &KDUDFWHULVWLF or .H\�)LJXUH for the InfoObject type, and choose &UHDWH.

4. A list of all InfoObjects is displayed. Use the pushbuttons to filter this list according to InfoSource,ODS object, InfoCube, or InfoObject catalog.

5. Use the arrow buttons to transfer the InfoObjects you want to use into the InfoObject catalog.

6. Activate the InfoObject catalog.



$GGLWLRQDO�,QIR2EMHFW�&DWDORJ�)XQFWLRQV

,QIR�)XQFWLRQV

There are various info-functions on the status of the InfoCube Catalog:

• the log display for activation and deletion runs of the InfoObject Catalog,

• the current system settings, the object catalog entry.

6SHFLDO�)XQFWLRQV

• 1DYLJDWLRQ�IRU�,QIR2EMHFW�PDLQWHQDQFH� Pushbuttons allow you to FUHDWH��GLVSOD\ and FKDQJHindividual InfoObjects. Note that changes to InfoObjects apply to all the places where theInfoObjects are used!

• 'LVSOD\�DFWLYH��6$3�YHUVLRQ� When you are editing the InfoObject Catalog, you can display itsactive version, or the version delivered by SAP (if available).

• 7UDQVIHU�6$3�YHUVLRQ��Using this function, the “D” version of the InfoObject Catalog delivered bySAP is transferred to the saved “A” version.

InfoObject Catalogs are only available in the “A” or “D” version, meaning either actively oras an SAP delivery object. In order to keep things simple, the saved version “M” does notapply. An InfoObject Catalog is therefore activated directly, but not saved.

• 'HOHWH�,QIR2EMHFW�&DWDORJ��This function deletes the complete InfoObject Catalog in its definition.



,QIR2EMHFW�1DPLQJ�&RQYHQWLRQV

8VH

As is the case for other objects in BW, the customer namespace A-Z is also reservedfor InfoObjects.

When you create an InfoObject, the name you give it has to begin with a letter.Business Content InfoObjects start with the number 0.

,QWHJUDWLRQ

If you change an InfoObject that is in the SAP namespace, your changes are notoverwritten immediately when you install a new release, and your changes remain inplace.

Business Content InfoObjects are initially delivered in the D version. An InfoObject isactivated after you have installed it from Business Content (see Installing BusinessContent [Seite 21]). If you change the activated InfoObject, a new M version isgenerated. When this M version is activated, it overwrites the previous active version.

$FWLYLWLHV

Note, when you are determining naming conventions for InfoObjects, that the lengthof an InfoObject is restricted to 9 characters.



&UHDWLQJ�,QIR2EMHFWV��&KDUDFWHULVWLFV

3UHUHTXLVLWHV

If you want to assign your InfoObject to an InfoObject catalog for characteristics, you have to firstcreate the InfoObject. You do not have to assign the InfoObject to an InfoObject catalog immediately,you can do it at a later date if you want to.

Instead of creating a new InfoObject, you can choose an InfoObject from those delivered by SAP withBusiness Content (see Installing Business Content [Seite 21].

3URFHGXUH

1. Using the context menu, select &UHDWH�,QIR2EMHFW from your InfoObject catalog for characteristics.

2. Enter a name and a description.

3. If necessary, define a template InfoObject.

4. Confirm your entries.

5. Maintain the Tabstrip: General [Seite 34]. You must enter at least the description, data type, anddata length. All the following settings and tabstrips are optional.

6. Maintain the Tabstrip: Business Explorer [Seite 36]

7. Maintain the Tabstrip: Master Data/Texts [Seite 56]

8. Maintain the Tabstrip: Hierarchy [Seite 58]

9. Maintain the Tabstrip: Attributes [Seite 59]

10. Maintain the Tabstrip: Compounding [Seite 61]

11. 6DYH and DFWLYDWH the characteristic you have created.

Characteristics have to be DFWLYDWHG before they can be used.

6DYH means, that all changed characteristics are created, and that the table entries aresaved. Currently, they can not, however, be used for reporting in InfoCubes. For the timebeing, if it already exist, the DFWLYDWHG� older version remains here unaltered.

Only once you have DFWLYDWHG� are the relevant objects created in the data dictionary (dataelements, domains, text table and master data table, programs). Only now do theInfoCubes work with the activated, new version.

In the InfoObject maintenance, you can switch, at any time, between any D, M, and Aversions that exist for an InfoObject.



7DEVWULS��*HQHUDO

8VH

In this tabstrip, you determine the basic properties of the characteristic.

6WUXFWXUH

'LFWLRQDU\

Specify the GDWD�W\SH and the GDWD�OHQJWK. The system provides you with a list to choose from in the F4Help.

The following data types are supported for characteristics:

Char: Numbers and letters Character length 1 -60

Numc: Numbers only Character length 1 -60

Dats: Date Character length 8

Tims: Time Character length 6

For authorizations, only the first 32 characters are interpreted.

0LVFHOODQHRXV

/RZHUFDVH�OHWWHUV�DOORZHG��QRW�DOORZHG

If this indicator is set, the system differentiates between lowercase letters and capital letters when youuse a screen template to input values. If this indicator is not set, the system converts all the letters intocapital letters when you use a screen template to input values.

If you choose to allow the use of lowercase letters, you must be aware of what happenswhen you input variables:

If you want to use the characteristic in variables, the system is only able to find the valuesfor the characteristic if the lowercase letters and the capital letters are typed in accuratelyon the input screen for variables. If, on the other hand, you do not allow the use oflowercase letters, any characters that you type onto the input screen, are convertedautomatically into capital letters.

([FOXVLYH�DWWULEXWHV

If you select H[FOXVLYH�DWWULEXWH, the created characteristic can be used only as a display attribute foranother characteristic, and not as an independent characteristic or navigation attribute in theInfoCube/ODS object. You can choose the /RZHUFDVH /HWWHUV option as a characteristic value for theCHAR field type.

If you use lowercase letters in an attribute, the system is unable to create a master datatable. An attribute cannot have any hierarchies, nor can it be used as a navigationattribute.

&KDUDFWHULVWLF�LV�D�SURSHUW\�RI�D�GRFXPHQW

You can specify that a characteristic be used as a document property. This enables you to assign acomment (this can be any document) to a combination of characteristic values and a key figure. Seealso Documents [Seite 479].



Since it does not make sense to use this comment function for all characteristics, youneed to identify explicitly the characteristics that you want to appear in the comments.

If you use this property, the system generates a property (attribute) for this characteristic in themetamodel of the document management system. For technical reasons, this property (attribute) hasto be written to a (dummy) transport request (the appropriate dialog box appears) but it is not actuallytransported.

&RQVWDQWV

By assigning a FRQVWDQW to a characteristic, you give the characteristic a fixed value. This means thatthe characteristic is available on the database (for verifications, for example) but is no longer relevantto reporting (no aggregation / drilldown is possible for this characteristic). Assigning a constant is mostuseful with compounded characteristics.

The VWRUDJH�ORFDWLRQ characteristic is compounded with the SODQW�characteristic. If only oneplant is ever run within the application, a constant can be assigned to the plant. Theverification for the storage-location master table runs correctly with this value for the plant.In the query, however, only the storage location appears as a characteristic.

6SHFLDO�&DVH�

If you want to assign the SPACE constant (type CHAR) or 00..0 (type NUMC) to thecharacteristic, type # in the first position.

7UDQVIHU�5RXWLQH

When you create a transfer routine, it is valid globally for the characteristic, and is included in all thetransfer rules. If, for example, you upload data from various source systems, you need to maintain thetransfer routine only once. On the other hand, when you maintain the transfer rules between thetransfer structure and the communication structure, you have the option of assigning a local transferroutine to a characteristic.

If you have created a local and a global transfer routine, both are used (the local transferroutine first, and then the global transfer routine).



7DEVWULS��%XVLQHVV�([SORUHU

8VH

In this tabstrip, you determine for the characteristics the properties that are required for reportingpurposes in the Business Explorer.

6WUXFWXUH

*HQHUDO�6HWWLQJV

/D\RXW

The layout describes the contents of the leading column for this characteristic in the BusinessExplorer. There are various display options to choose from: QR�GLVSOD\��WH[W��NH\��WH[W�DQG�NH\��ORQJWH[W��or PHGLXP�WH[W. Choose a display option.

7H[W�6HOHFWLRQ

In this field, you set which text appears for this characteristic in the Business Explorer. Choosebetween the long and short descriptions of the characteristic.

6HOHFWLRQ

The selection describes if and how the characteristic values have to be restricted in queries. If youchoose the XQLTXH IRU�HYHU\�FHOO�option, the characteristic must be restricted to one value in everycolumn and in every structure of all the queries. You are not able to use this characteristic inaggregates. Typical examples of this kind of characteristic are 3ODQ�DFWXDO�,', or 9DOXH�W\SH.

,QSXW�+HOS�LQ�WKH�4XHU\�'HILQLWLRQ

This field tells you from which database table the values for the input help in the query definition aretaken.

Usually, the values in the input help are taken from the master data table. With characteristics that donot have master data tables, the values are taken from the SID table instead. In many cases it makesmore sense to display only those values that are also contained in the dimension of an InfoCube.

,QSXW�+HOS�LQ�WKH�4XHU\�([HFXWLRQ

This field tells you how the values for the input help are determined when a query is executed.

Usually, when queries are executed, the values in the input help are determined by the data that isselected by the query. This means that only the values for which data has been selected in the currentnavigation status are displayed.

In many cases, however, it can makes sense to include additional values. This is why the 8VLQJ'LPHQVLRQV and 8VLQJ�0DVWHU�'DWD�7DEOH settings are also active.

&XUUHQF\�$WWULEXWHV

You can choose a FXUUHQF\ type unit-InfoObject that you have created as an attribute for thecharacteristic. This currency is used as the default target currency for the currency translation in theBusiness Explorer [Extern] .

$XWKRUL]DWLRQ�5HOHYDQFH

With characteristics, you decide whether a particular characteristic is included in the authorizationcheck whenever you are working with the query.

Flag a characteristic as DXWKRUL]DWLRQ�UHOHYDQW if you want to create authorizations that restrict theselection conditions for this characteristic to single characteristic values.

Only flag the characteristic as QRW�DXWKRUL]DWLRQ�UHOHYDQW, if it is no longer being used as a field for theauthorization object.

6HH�DOVR�



Authorizations for Working with a Query [Extern]

%([�0DS

*HRJUDSKLFDO�7\SH

For each geo-relevant characteristic [Seite 40] you have to specify a geographical type. There are fouroptions to choose from.

1. 6WDWLF�JHR�FKDUDFWHULVWLF: For this type, you can use shape files (country borders, for example), todisplay the characteristic on a map in the Business Explorer.

2. '\QDPLF�JHR�FKDUDFWHULVWLF: For this type of geo-characteristic, the system generates geo-attributes that make it possible, for example, to display customers on a map.

3. '\QDPLF�JHR�FKDUDFWHULVWLF�ZLWK�DWWULEXWH�YDOXHV: For this type of geo-characteristic, the geo-attributes of a type 2 geo-characteristic (that is an attribute) are used.

4. 6WDWLF�JHR�FKDUDFWHULVWLF�ZLWK�JHR�DWWULEXWHV: Just like static geo-characteristics, with the addition ofgenerated geo-attributes.

See also Static and Dynamic Geo-Characteristics [Seite 40].

If you choose the 1RW�D�*HR�&KDUDFWHULVWLF option, this characteristic cannot be used as a geo-characteristic for displaying information on the BEx Map. Geographical attributes (such as0LONGITUDE, 0ALTITUDE) are deleted for the InfoObject.

*HRJUDSKLFDO�$WWULEXWH

If you have selected the geographical type G\QDPLF�JHR�FKDUDFWHULVWLF�ZLWK�DWWULEXWH�YDOXHV for thecharacteristic, specify here the characteristic attribute, whose geo-attributes you want to use.

8SORDGLQJ�6KDSH�)LOHV

Use this function to upload the geo-information files that are assigned to the characteristic. These filesare stored in the BDS as files that belong logically to the characteristic.

See also Shapefiles [Seite 42].

'RZQORDGLQJ�*HR�'DWD

You use this function to load the master data for a characteristic to your PC, where you are able to useyour GIS tool to geocode the data. Finally, you use a flat file to load the data into the relevant BWmaster data table.



0DSSLQJ�*HR�5HOHYDQW�&KDUDFWHULVWLFV

'HILQLWLRQ

In order to display BW data geographically, a link between this data and the respective geographicalcharacteristic must be created. This process is called 0DSSLQJ�*HR�5HOHYDQW�&KDUDFWHULVWLFV�

6WUXFWXUH

The geographical information about geographical boundaries of areas that are displayed using staticgeo-characteristics is stored in shapefiles [Seite 42] In the shapefile, a BW-specific attribute called theSAPBWKEY connects an area on the map with the corresponding characteristic value in BW. Thisattribute matches the object key in the corresponding BW master data table. This process is called6$3%:.(<�0DLQWHQDQFH�IRU�6WDWLF�*HR�&KDUDFWHULVWLFV� See Maintaining the SAPBWKEY for StaticGeo-Characteristics [Seite 45]

You can use $UF9LHZ�*,6�or other software that has functions for editing dBase files tocarry out the SAPBWKEY maintenance (MS Excel, for example).

With data in point form that is displayed using dynamic geo-characteristics, geographical data is addedto BW master data. The process of assigning geographical data for entries in the master data table iscalled JHRFRGLQJ. See Geocoding [Seite 51]

The software $UF9LHZ�*,6 from ESRI (Environmental Systems Research Institute)geocodes the InfoObjects.

Shapefiles (.shp, .dbf, .shx)Static Geometric Information

SAPBWKEY AttributeSAPBWKEY Attribute

BW Master Data Table

• Static Geo Characteristics

• Dyn. Geo Characteristics

SAPBWKEY Attribute SAPBWKEY Attribute

Additional Geographical AttributeAdditional Geographical Attribute

Geographical Data Display

Combination of Data During Runtime

• Geocoding for Dyn. Geo-Characteristics

• SAPBWKEY Maint. for Stat. Geo-Characteristics

��

ArcView GIS from ESRIArcView GIS from ESRI

SAP BW ServerSAP BW Server

Shapefile Upload toBusiness Document Service (BDS)

Upload of master data with additional geographicalattributes (longitude, latitiude)into the master data table

,QWHJUDWLRQ

You geocode using the ArcView GIS software from ESRI. Over and above geocoding, ArcView offersa large scope of functions for special, geographical problems that are not covered by the BusinessInformation Warehouse solution. ArcView enables you to create your own maps, for example, a mapof your sales regions. For more detailed information, see the ArcView documentation.

When you buy the 6$3�%XVLQHVV�,QIRUPDWLRQ�:DUHKRXVH��you receive a voucher that you can use toorder $UF9LHZ�*,6�from ESRI.



The installation package also contains a CD developed specially by SAP and ESRI. The CD containsa range of maps covering the whole world in various levels of detail. All maps on this data CD areoptimized already for use with the Business Information Warehouse. The .dbf files for the mapscontain the SAPBWKEY column, which is filled with default values. For example, the world map(cntry200) contains the usual values from the SAP system for countries in the SAPBWKEY column.Therefore, you can use the map immediately to evaluate your data geographically. You do not have tomaintain the SAPBWKEY.

You can get additional, more detailed maps in the ESRI shapefile from ESRI.



6WDWLF�DQG�'\QDPLF�*HR�&KDUDFWHULVWLFV

'HILQLWLRQ

Static and dynamic characteristics describe data with a geographical reference (for example,characteristics such as customer, sales region, country). Maps are used to display and evaluate thisgeo-relevant data.

6WUXFWXUH

There are four different types of geo-characteristic:

�� 6WDWLF�JHR�FKDUDFWHULVWLFV

A static geo-characteristic is a characteristic that describes a surface (polygon), whosegeographical coordinates rarely change. Country and region are examples of static geo-characteristics.

Data from areas or polygons are stored in Shapefiles [Seite 42] that define the geometry andthe attributes of the geo-characteristics.

�� '\QDPLF�JHR�FKDUDFWHULVWLFV

A dynamic geo-characteristic is a characteristic that describes a location (information in pointform), whose geographical coordinates can change more frequently. Customer and plant areexamples of dynamic geo-characteristics because they are rooted to one geographical “point”that can be described by an address, and the address data of these characteristics can oftenchange.

BW adds a range of standard attributes to this geo-characteristic. These standard attributesstore the geographical coordinates of the corresponding object for each row in the master datatable. There are the following geo-attributes:

7HFKQLFDO�1DPH 'HVFULSWLRQ 'DWD�7\SH /HQJWK

LONGITUDE longitude of thelocation

DEC 15

LATITUDE latitude of the location DEC 15

ALTITUDE altitude of the location(height above sealevel)

DEC 17

PRECISID identifies how precisethe data is

NUMC 4

SRCID ID for the data source CHAR 4

At present, only the LONGITUDE and LATITUDE attributes are used. ALTITUDE,PRECISID and SRCID are reserved for future use.

If you reset the geographical type of a characteristic to 1RW�D�*HR�&KDUDFWHULVWLF, theseattributes are deleted in the InfoObject maintenance.

�� '\QDPLF�JHR�FKDUDFWHULVWLFV�ZLWK�YDOXHV�IURP�DWWULEXWHV

To save you having to geocode each dynamic geo-characteristic individually, a dynamic geo-characteristic can get its geo-attributes (longitude, latitude, altitude) from another dynamiccharacteristic that has been geocoded already (postal code, for example). Customers andplants are examples of this type of G\QDPLF�JHR�FKDUDFWHULVWLFV�ZLWK�YDOXHV�IURP�DWWULEXWHV(type 3).

The system treats this geo-characteristic as a regular dynamic geo-characteristic thatdescribes a location (geographical information as a point on map). The geo-attributes



described above are not added to the master data table on the database level. Instead, thegeo-coordinates are stored in the master data table of a regular attribute of the characteristic.

You want to define a dynamic geo-characteristic for 3ODQW with the postal code as anattribute. The geo-coordinates are generated from the postal code master data tableduring the runtime.

This method prevents redundant entries from appearing in the master data table.

�� 6WDWLF�JHR�FKDUDFWHULVWLFV�ZLWK�JHR�DWWULEXWHV

A static geo-characteristic that includes geo-attributes (longitude, latitude, altitude) which geo-characteristics of type 3 are able to refer to. The postal code, for example, can be used as aVWDWLF�JHR�FKDUDFWHULVWLF�ZLWK�JHR�DWWULEXWHV.

0POSTCD_GIS (postal code) is used as an attribute in the dynamic geo-characteristic0BPARTNER (business partner) that gets its geo-coordinates from this attribute. In thisway, the location information for the business partner is stored on the level of detail of thepostal code areas.

6HH�DOVR�

Delivered Geo-Characteristics [Seite 44]



6KDSHILOHV

'HILQLWLRQ

ArcView GIS software files from ESRI that contain digital map material of areas or polygons (that is,shapes). Shapefiles define the geometry and attributes of static geo-characteristics.

8VH

Shapefiles form the basis of the display of BW data in the area of Web Reporting.

6WUXFWXUH

)RUPDW

The format of ArcView Shapefiles uses the following files with special file enhancements:

�GEI – dBase file that saves the attributes or values of the characteristic

�VKS – saves the current geometry of the characteristic

�VK[ – saves an index for the geometry

These three files are saved for each static geo-characteristic in the Business Document Service (BDS)and loaded to the local computer from BDS when you use BEx Map.

6KDSHILOH�'DWD�IURP�WKH�(65,�%:�0DSSLQJ�'DWD�&'

The map data from the ESRI BW mapping data CD was selected as the basic reference data level toprovide you with a detailed map display and also with thematic mapping material on the levels of worldmaps, continents and individual countries. The reference data levels involve country boundaries, stateboundaries, towns, streets, railways, lakes and rivers. The mapping data is subdivided into data for 21separate maps.

There is mapping data for:

• a world map

• seven maps on continent level, for example, Asia, Europe, Africa, North America, South America.

• 13 maps on country level: The data for countries may vary. Most of the country boundaries arefrom 1960-1988, some countries have been updated to their position in 1995.

The names of the Shapefiles on the ESRI BW mapping data CD follow a three-part namingconvention.

• The first part consists of an abbreviation of the thematic content of the Shapefile, for example,FQWU\�stands for a Shapefile with country boundaries.

• The second part of the name indicates the level of detail. There are, for example, three Shapefileswith country boundary information at different levels of detail. The least detailed Shapefile beginswith FQWU\�, whereas the most detailed Shapefile begins with FQWU\�.

• The third part of the name indicates the version number of the Shapefile, based on the last twodigits of the year beginning with the year 2000. Therefore, the full name of the Shapefile with themost detailed country boundary information is FQWU\��

All Shapefiles on the ESRI BW mapping data CD already contain the SAPBWKEY column. Forcountries, the two-figure SAP country key is entered in the SAPBWKEY column.

The file 5HDGPH�W[W�on the ESRI BW mapping data CD contains further, detailedinformation on the delivered Shapefiles, the file name conventions used, the mapping datadescriptions and specifications, data sources, and how up-to-date the data is.



,QWHJUDWLRQ

At run time, the Shapefiles are downloaded from the BW to the IGS (Internet Graphic Server). Thefiles are copied into the �GDWD�VKDSHILOHV�index. If a specific Shapefile is already in this directory, it isnot copied again. If the Shapefile has been changed in the Business Document Service (BDS) in themeantime, the latest version is copied automatically into the local directory.

Depending on the level of detail, Shapefiles can be quite large. The Shapefile cntry200.shp with thecountry boundaries for the entire world is around 2.2 megabytes. For small organizational units, suchas federal states, the geometric information is saved in several Shapefiles. That is, you can assign acharacteristic to several Shapefiles (for example, states in Germany and in France.).



'HOLYHUHG�*HR�&KDUDFWHULVWLFV

'HILQLWLRQ

With Business Content, SAP BW delivers a range of geo-characteristics.

6WUXFWXUH

The following are the most important delivered geo-characteristics:

6WDWLF�JHR�FKDUDFWHULVWLFV

7HFKQLFDO�1DPH 'HVFULSWLRQ

0COUNTRY Country key

0DATE_ZONE Time zone

0REGION Region (federal state, province)

'\QDPLF�JHR�FKDUDFWHULVWLFV


0APO_LOCNO Location number

0TV_P_LOCID IATA location

'\QDPLF�JHR�FKDUDFWHULVWLFV�ZLWK�YDOXHV�IURP�DWWULEXWHV

7HFKQLFDO�1DPH $WWULEXWHV 'HVFULSWLRQ

0BPARTNER 0POSTCD_GIS Business partner

0CONSUMER 0POSTCD_GIS Consumer

0CUSTOMER 0POSTCD_GIS Customer number

0PLANT 0POSTCD_GIS Plant

0VENDOR 0POSTCD_GIS Vendor

6WDWLF�JHR�FKDUDFWHULVWLFV�ZLWK�JHR�DWWULEXWHV


0CITYP_CODE Coding for regional area for location and streetdata.

0CITY_CODE Location coding for location and street data

0POSTALCODE Postal code

0POSTCD_GIS Postal code (geo-relevant)



0DLQWDLQLQJ�WKH�6$3%:.(<�IRU�6WDWLF�*HR�&KDUDFWHULVWLFV

3XUSRVH

During runtime, BW data is combined with a corresponding shapefile [Seite 42]. This enables the BWdata to be displayed in geographical form (country, region, and so on) using color shading, bar charts,or pie charts. The SAPBWKEY ensures that the BW data is assigned to the appropriate shapefile.

��

��

��

��

%DOWLPRUH

'HQYHU%RVWRQ

��

��

��

��

��

>�[ � ��\ � ��[ � ��\ � �@>�[ � ��\ � ��[ � ��\ � �@>�[ � ��\ � ��[ � ��\ � �@

��

�

��

��

Region �� !�"# $ % !�&('�!�) $50.00#(* +�, "(- , & $20.00#(. + �� -0/�1 , )0! $150.00232�2 232�2 2�232Result 4 *(*(# 2 #(#

%([�4XHU\�'DWD 6KDSHILOH�$WWULEXWH�7DEOH 6KDSHILOH�*HRPHWU\

6$3%:.(<

'DW

D

*HRP

HWU\

In the standard shapefiles delivered with the ESRI BW map CD, the SAPBWKEY columnis already filled with the two-character SAP country keys (DE, EN, and so on). You canuse these shapefiles without having to maintain the SAPBWKEY beforehand.

3UHUHTXLVLWHV

You have marked the geo-relevant characteristic as geo-relevant in the InfoObject maintenance.

Before you are able to follow the example that explains how you maintain the SAPBWKEYfor static geo-characteristics, you have to make sure that the SAP DemoContent is activein your BW system.

You can use the ArcView GIS from ESRI to maintain the SAPBWKEY, or you can useother software (MS Excel or FoxPro, for example) that has functions for displaying andediting dBase files.

3URFHVV

For static geo-characteristics (such as &RXQWU\ or 5HJLRQ� that represent the geographical drilldowndata for a country or a region, you have to maintain the SAPBWKEY for the individual country orregion in the attribute table of the shapefile. The attribute table is a database table stored in dBaseformat. Once you have maintained the SAPBWKEY, you load the shapefiles (.shp, .dbf, .shx) into BW.The shapefiles are stored in the Business Document Service (BDS), a component of the BW server.



The following section uses the example of the 0D_COUNTRY characteristic to describe how youmaintain the SAPBWKEY for static geo-characteristics. You use the CNTRY200 shapefile from theESRI BW map data CD. The CD contains the borders of all the countries in the world. Themaintenance of the SAPBWKEY for static geo-characteristics consists of the following steps.

1. Creating a local copy of the shapefile from the BW data CD (.shp,.shx,.dbf) [Seite 47].

2. Downloading BW master data into a dBase (.dbf) file [Seite 48].

3. Opening the dBase attributes table for the shapefile (.dbf) in Excel, and maintaining theSAPBWKEY column [Seite 49].

4. Uploading the edited shapefile into BW [Seite 50].

In this example scenario using the 0D_COUNTRY characteristic, the SAPBWKEY columnis already maintained in the attribute table and corresponds with the SAP country keys inthe master data table. If you maintain a shapefile where the SAPBWKEY has not beenmaintained, or where the SAPBWKEY is filled with values that do not correspond to BWmaster data, proceed as described in the steps above.

5HVXOW

You are now able to use the characteristic as a static geo-characteristic in the BEx Web Publisher.Every user that works with a query containing this static geo-characteristic, is able to attach a map tothe query and analyze the data directly on the map.



&UHDWLQJ�D�/RFDO�&RS\�RI�WKH�6KDSHILOH

8VH

You need a local copy of the Shapefile before you are able to maintain the SAPBWKEY column in theattributes table of the Shapefile.

3URFHGXUH

1. Use your file manager (Windows Explorer, for example) to localize the three files FQWU\��VKS,FQWU\��VK[ and FQWU\��GEI on the ESRI BW map data CD, and copy the files to theC:\SAPWorkDir directory, for example.

2. You must deactivate the :ULWH�3URWHFWHG option before you are able to edit the files. (Select thefiles and choose the 3URSHUWLHV option from the context menu (right mouse-click). Under $WWULEXWHV,deactivate the :ULWH�3URWHFWHG�option).

If you do not have access to the ESRI BW map data CD, proceed as follows:

The files are already maintained in the BW Business Document Service (BDS). Thefollowing example explains how, for the characteristic 0D_COUNTRY in InfoCube0D_SD_C0, you download these files from the BDS to your local directory.

1. Log on to the BW system and go to the InfoObject maintenance screen (transaction 56'�). Thistakes you to the (GLW�,QIR2EMHFWV��,QLWLDO�VFUHHQ.

2. In the InfoObject field, enter 0D_COUNTRY and choose 'LVSOD\� You reach the 'LVSOD\&KDUDFWHULVWLF��'B&28175<��'HWDLO�screen.

3. Choose the %XVLQHVV�([SORUHU tabstrip. In the %([�0DS�area, 0D_COUNTRY is shown as a staticgeo-characteristic.

4. Choose 'LVSOD\�6KDSHILOHV. This takes you to the %XVLQHVV�'RFXPHQW�1DYLJDWRU that alreadyassociates three Shapefiles with this characteristic.

5. Open up the Shapefiles completely in the %:�0HWDREMHFWV tree.

6. Select the .dbf file BW_GIS_DBF and choose ([SRUW�'RFXPHQW. This loads all the files to yourlocal SAPWorkDirectory. (The system proposes the C:\SAPWorkDir directory as yourSAPWorkDirectory).

7. Repeat the last step for the .shp (BW_GIS_SHP) and .shx (BW_GIS_SHX) files.



'RZQORDGLQJ�%:�0DVWHU�'DWD�LQWR�D�G%DVH�)LOH

8VH

The first step in the SAPBWKEY maintenance for dynamic geo-characteristics and their geo-coding isto download the BW master data table into a dBase file.

3URFHGXUH


2. In the InfoObject field, specify the name of the G\QDPLF�geo-characteristic that you want togeocode (in this example: 0D_SOLD_TO.

3. Choose 'LVSOD\� You reach the 'LVSOD\�&KDUDFWHULVWLF��'B62/'B72��'HWDLO�screen.

�� Choose the %XVLQHVV�([SORUHU tabstrip. In the %([�0DS�area 0SOLD_TO is shown as a G\QDPLFJHR�FKDUDFWHULVWLF�

5. Choose *HR�'DWD�'RZQORDG��(YHU\WKLQJ��

If you only want to maintain those entries that have been changed since the last attributemaster data upload, choose *HR�'DWD�'RZQORDG��'HOWD�� The geo-data has to bedownloaded in the delta version before you execute the realignment run for theInfoObject. Otherwise the delta information is lost.

6. The system asks you to select a geo-attribute that you want to include in the dBase file. Thesystem only displays those attributes that we defined as geo-relevant. In this case, select bothattributes: 0D_COUNTRY and 0D_REGION.

7. Choose 7UDQVIHU�6HOHFWLRQV�

8. Accept the file name proposed by the system by choosing 7UDQVIHU�

The proposed file name is made up of the technical name of the characteristic and the.dbf extension. You can change the file name and create a directory. If you do not specifya path, the file is save automatically in the SAP work directory.

5HVXOW

The status bar contains information on how much data has been transferred.



0DLQWDLQLQJ�WKH�6$3%:.(<�&ROXPQ

3UHUHTXLVLWHV

You have completed the following steps:

Created a local copy of the Shapefile [Seite 47]

Downloaded BW master data into a dBase file [Seite 48]

,QWHJUDWLRQ

The SAPBWKEY is maintained in the dBase file with the suffix �GEI. This file contains the attributetable.

3URFHGXUH

1. Launch Microsoft Excel and choose )LOH�→ 2SHQ�

2. From the dropdown box in the )LOHV�RI�7\SH field, choose G%DVH�)LOHV�� GEI��

3. From the &�?6$3:RUN'LU directory, open the FQWU\��GEI file. The attributes table from theshapefile is displayed in an Excel worksheet.

4. Repeat this procedure for the �'B&28175<�'%) file that you created in the step DownloadingBW Master Data into the dBase File [Seite 48]. This file shows you which values from theSAPBWKEY are used for which countries.

5. In the �'B&28175<�'%) file, use the short description (�7;76+ column) to compare the twotables.

ESRI delivers an ESRI BW map data CD. This CD contains the SAPBWKEY(corresponding to the SAP country key) for the characteristic 0D_COUNTRY. This is whythe 6$3%:.(< column in the FQWU\��GEI file is already filled with the correct values.

You have to copy the SAPBWKEY manually to the attributes table in the shapefile:

− If you are using a different country key

− If you are working with characteristics for which the 6$3%:.(< column has not beendefined, or is filled with invalid values

If you are working with compounded characteristics, copy the complete SAPBWKEY, forexample, for region �� compounded with country '( copy the complete value '(��.

'R�QRW�XQGHU�DQ\�FLUFXPVWDQFHV�FKDQJH�WKH�VHTXHQFH�RI�WKH�HQWULHV�LQ�WKHDWWULEXWHV�WDEOH��IRU�H[DPSOH��E\�VRUWLQJ�RU�GHOHWLQJ�URZV�� If you were to change thesequence of the entries, the attribute table would no longer agree with the index and thegeometric files.

6. When you have finished maintaining the SAPBWKEY column, save the attributes table in theshapefile, in this example, FQWU\��.GEI.



8SORDGLQJ�(GLWHG�6KDSHILOHV�LQWR�%:

3UHUHTXLVLWHV


Created a local copy of the Shapefile [Seite 47]


Maintained the SAPBWKEY column [Seite 49]

3URFHGXUH

The last step is to attach the Shapefile set (.shp, .shx, .dbf) to the InfoObject, by uploading it into theBusiness Document Service (BDS) on the BW server.


2. In the InfoObject field, specify 0D_COUNTRY and choose 0DLQWDLQ� This takes you to the &KDQJH&KDUDFWHULVWLF��'B&28175<��'HWDLO�screen.

3. In the %XVLQHVV�([SORUHU tabstrip, choose 8SORDG�6KDSH�)LOHV� The %XVLQHVV�'RFXPHQW�6HUYLFH�)LOH�6HOHFWLRQ dialog box appears.

4. Select the FQWU\��VKS file and choose 2SHQ The Business Document Service suggests entriesfor the file name, description, and so on, and allows you to enter key words that will make it easierfor you to find the file in the BDS at a later date.

5. Choose 1H[W.

6. The system automatically asks you to upload the FQWU\��GEI�and FQWU\��VK[�files for theShapefile.

5HVXOW

You have uploaded the edited Shapefile into BW. You can now use the characteristic in the Webreport. Every user that works with a query that contains the 0D_COUNTRY InfoObject, can now attacha map to the query and analyze the data on the map.



*HRFRGLQJ

3XUSRVH

To display dynamic geo-characteristics as points on a map, you have to determine the geographic co-ordinates for each master data object.

The master data table for dynamic geo-characteristics is therefore extended with anumber of standard geo-attributes such as LONGITUDE and LATITUDE (see Static andDynamic Geo-Characteristics [Seite 40]).

3UHUHTXLVLWHV

You have marked the geo-relevant characteristic as geo-relevant in the InfoObject maintenance. See:Tabstrip: Business Explorer [Seite 36]

Before you can to follow the example that explains the geocoding process, you have toensure that SAP DemoContent is active in your BW system.

3URFHVV

You geocode using the ArcView GIS software from ESRI. ArcView GIS determines the geographicalcoordinates of BW data, by identifying a column with geo-relevant characteristics in a referenceshapefile. To carry out this process, you have to load the BW master data table into a dBase file. Thegeographical coordinates are determined for every master data object. After you have done this,convert the dBase file with the determined geo-attributes into a CSV file (Fomma-Veparated Yalue file),which you can use for a master data upload into the BW master data table.

The following steps explain the process of geocoding dynamic geo-characteristics using the0D_SOLD_TO characteristic (sold-to party) from the 0D_SD_C03 6DOHV�2YHUYLHZ�'HPR�&RQWHQW,QIR&XEH�

1. Downloading BW master data into a dBase (.dbf) file [Seite 52]

2. Geocoding using ArcView GIS [Seite 53].

3. Converting dBase Files into CSV Files [Seite 55].

4. Scheduling a master data upload for the CSV file.

The system administrator is responsible for the master data upload.

5HVXOW

You can now use the characteristic as a dynamic geo-characteristic in the BW Business Explorer.Each user who works with a query that contains this dynamic geo-characteristic can now analyze datafrom a chart.



'RZQORDGLQJ�%:�0DVWHU�'DWD�LQWR�D�G%DVH�)LOH

8VH

To be able to maintain the SAPBWKEY column in the Shapefile attribute table, you have to specify thecorresponding SAP BW country key for every row in the attribute table. Since this information iscontained in the BW master data table, you have to download it into a local dBase file to compare itwith the entries in the attribute table and to be able to maintain the SAPBWKEY.

3UHUHTXLVLWHV

You have created a local working copy of the Shapefile [Seite 47].

3URFHGXUH


2. In the InfoObject field, enter 0D_COUNTRY and choose 'LVSOD\� You reach the 'LVSOD\&KDUDFWHULVWLF��'B&28175<��'HWDLO�screen.

3. Choose the %XVLQHVV�([SORUHU tabstrip. In the %([�0DS�area, 0D_COUNTRY is shown as a staticgeo-characteristic.

4. Choose *HR�'DWD�'RZQORDG��(YHU\WKLQJ��

5. Accept the file name proposed by the system by choosing 7UDQVIHU�

The proposed file name is made up of the technical name of the characteristic and the.dbf extension, therefore, in this case the file is called 0D_COUNTRY.DBF.

If the *HR�'DWD�'RZQORDG��(YHU\WKLQJ��pushbutton is deactivated (gray), there is nomaster data for the InfoObject. If this is the case, download the texts for the InfoObjectmanually to get to the SAPBWKEY.

See also: Creating InfoObjects: Characteristics [Seite 33] Tabstrips: Master Data/Texts[Seite 56]

5HVXOW

The status bar contains information on how much data has been transferred.

If you have not specified a directory for the file name, the file is saved in the local SAPwork directory.



*HRFRGLQJ�8VLQJ�$UF9LHZ�*,6

3UHUHTXLVLWHV

• You have installed the ESRI ArcView software on your system and requested the geographicaldata you need from ESRI, if this is not already on the data CD delivered with the software.

• You have carried out the following step:

Downloading BW master data into a dBase file [Seite 52]

8VH

Using geocoding, you enhance dynamic geo-characteristics from BW master data with thegeographical attributes degrees of longitude and latitude.

3URFHGXUH

The following procedure is an example procedure that you can reconstruct using thedemo contents. For further details on geocoding and on the ArcView functions, refer toArcView documentation.

In ArcView GIS you can execute many commands easily from the context menu. To openthe context menu, mark an item and click on it with the right mouse button.

1. Open $UF&DWDORJ using 3URJUDPV�→ $UF*,6.

2. Under *HRFRGLQJ�6HUYLFHV��double-click on the entry 1HZ�*HRFRGLQJ�6HUYLFH�

3. In the &UHDWH�1HZ�*HRFRGLQJ�6HUYLFH�window, select the entry 6LQJOH�)LHOG��)LOH� and click on OK.

4. In the 1HZ�6LQJOH�)LHOG��)LOH��*HRFRGLQJ�6HUYLFHV window, enter the name of the service and thedescription, for example, *HRFRGLQJ�6HUYLFH�6ROG7R� Under 5HIHUHQFH�'DWD, enter the path for thereference shapefile, for example, JBVWDW��VKS and from the )LHOGV dropdown menu, select themost appropriate entry, in this case, 6$3%:.(<� Under 2XWSXW�)LHOGV, activate the control box ;DQG�<�&RRUGLQDWHV�

In the navigation menu, the new service is displayed under *HRFRGLQJ�6HUYLFHV�

5. Open $UF0DS�using 3URJUDPV�→ $UF*LV�and start the initial dialog box with D�QHZ��HPSW\�PDS�Click 2..

6. In the standard toolbar, click on the $GG�'DWD�symbol and add the corresponding dBase file, forexample, 6ROG7R�GEI as a new table.

7. Click with the right mouse button in the main tree on the entry for the table that you created andchoose *HRFRGH�$GGUHVVHV�

The window 6HOHFW�*HRFRGLQJ�6HUYLFH�is opened. This window displays all available services.

8. Click on $GG� and, in the window $GG�*HRFRGLQJ�6HUYLFH��under 6HDUFK�LQ��choose the entry*HRFRGLQJ�6HUYLFHV� Select the service that you created in step 4, in this example, *HRFRGLQJ6HUYLFH�6ROG7R, and click on $GG�

9. In the 6HOHFW�D�*HRFRGLQJ�6HUYLFH�window, select the service again, and click 2.�

The *HRFRGH�$GGUHVVHV�window is opened.

10. Under $GGUHVV�,QSXW�)LHOGV��choose the appropriate entry, for example, �B�'B5HJLR. This is thefield that tallies with the reference data. Under 2XWSXW��2XWSXW�6KDSHILOH�RU�)HDWXUH�&ODVV� enterthe path under which the result of the geocoding is to be stored. Click 2..

The data is geocoded.

11. After you have checked the statistics in the 5HYLHZ�5HPDWFK�$GGUHVVHV�window, click 'RQH�



5HVXOW

The dynamic geo-characteristics for your master data have now been enhanced with additional geo-information in the form of the columns ;�(longitude) and < (latitude). In the ArcMap, this information isdisplayed by points in the right-hand section of the working area.

To check whether the result appears as you had planned, you can place the points on the relevantmap. Proceed as follows:

1. Click on the tabstrip on the symbol .

2. Select the reference shapefile that you used in step 4, for example, JBVWDW��VKS�

3. Click $GG.

The map is displayed in the work area in a layer beneath the points.



&RQYHUWLQJ�G%DVH�)LOHV�LQWR�&69�)LOHV

3UHUHTXLVLWHV



Geocoded using ArcView GIS [Seite 53]

,QWHJUDWLRQ

The result of the geocoding is the dBase file *HRFRGLHUXQJB5HVXOW�GEI. This file contains the BWmaster data enhanced with columns ; and <. Since the attribute table is stored in dBase file format,you must convert it into CSV (Fomma Veparate Yalue) format, which is executed by the BW StagingEngine. You can convert the table in Microsoft Excel.

3URFHGXUH

1. Launch Microsoft Excel and choose )LOH�→ 2SHQ�

2. From the dropdown box in the )LOHV�RI�7\SH field, choose G%DVH�)LOHV�� GEI��

3. Open the file *HRFRGLQJB5HVXOW�GEI. The attribute table with the geo-attributes is displayed inExcel.

4. Choose )LOH�→�6DYH�$V��

5. From the 6DYH�DV�7\SH selection list, choose &69��&RPPD�'HOLPLWHG��

6. Save the table.

5HVXOW

You have converted the dBase file to a CSV file with the geo-attributes of the dynamic geo-characteristic 0D_SOLD_TO. You system administrator can now schedule a master data upload.

When you upload the CSV file you must map the values in column X to the attribute0LONGITUDE and the values in column Y to the attribute 0LATITUDE.



7DEVWULS��0DVWHU�'DWD�7H[WV

8VH

In this tabstrip, you determine whether the characteristic has access to master data and/or texts.

6WUXFWXUH

:LWK�0DVWHU�'DWD

Determine here whether the characteristic has master data. You have to create a master data table fora characteristic if you want the characteristic to have attributes.

When you select this option, the system generates a master data table. Using the maintain masterdata [Seite 96] function, you branch to the corresponding maintenance dialog.

The master data table has a time-dependent and a time-independent part. Determine in attributemaintenance whether an attribute is time-dependent or not.

You cannot use time-dependent navigation attributes in aggregates.

:LWK�7H[WV

Here, you determine whether the characteristic has texts.

If you do want the characteristic to have texts, you must select at least one text. The short text (20characters) option is active by default, but you can also choose medium texts (40 characters) or longtexts (60 characters).

/DQJXDJH�'HSHQGHQW�7H[WV

You can choose whether or not you want the texts in the text table to be language-dependent or not. Ifyou decide that you want the texts to be language-dependent, the language becomes a key field in thetext table. If you decide that you do not want the texts to be language-dependent, the text table doesnot get a language field.

Some Business Content characteristics, for example, customer (0CUSTOMER), do notneed to be language-dependent.

7LPH�'HSHQGHQW�7H[WV

If you want the texts to be time-dependent, meaning that you want the date to be included in the key ofthe text table, you make the appropriate settings here. See also: Using Master Data and Master Data-Bearing Characteristics [Seite 93]

0DLQWDLQLQJ�0DVWHU�'DWD�ZLWK�$XWKRUL]DWLRQ�&KHFNV

If you set this indicator, you are able to use authorizations to protect the master data and texts for thischaracteristic from being maintained illegally on the single records level. If this option is activated,characteristic variables can be entered, for which the user has authorization. You can do this in theprofile generator (transaction: PFCG) using the authorization object S_TABU_LIN for each key field ofthe master data table. For example, you can authorize user A to maintain the values 1000 – 1999, anduser B to maintain the values 2000- -2999.

If you do not set this indicator, you have the option of allowing or blocking the maintenance of masterdata as a whole (for all characteristic values).

2'6�2EMHFW�IRU�&KHFNLQJ�&KDUDFWHULVWLF�9DOXHV

If you create an ODS object for checking the characteristic values in a characteristic, in the updaterules and in the transfer rules, the valid values for the characteristic are determined from the ODS



object and not from the master data. The characteristic itself and all the fields in the compound mustbe included as key fields in the ODS object.

Also refer to Check for Referential Integrity [Seite 282].

&KDUDFWHULVWLF�LV��

DQ�,QIR6RXUFH�

If you want to turn a characteristic into an InfoSource with direct updating, you have to assign anapplication component to the characteristic. The characteristic is subsequently displayed in theInfoSource tree in the Administrator Workbench. You are able to assign DataSources and sourcesystems to the characteristic from here. You are also able to load master data, texts, and hierarchiesfor the characteristic.

In the following cases you are not able to turn an InfoObject into an InfoSource with direct updating:

• The characteristic that you want to modify is characteristic 0SOURSYSTEM (source systemID).

• The characteristic has no master data, no texts, and no hierarchies – there is no point inloading data for this kind of characteristic.

• The characteristic that you want to modify turns out to be a unit or a key figure.

If you want to generate an export-DataSource for a characteristic, the characteristic has to be anInfoSource with direct updating – meaning that it has to be assigned to an application component.

D�'DWD�7DUJHW��,QIR3URYLGHU�

This indicator shows you whether the characteristic is a data target or an InfoProvider.

If you want to turn a characteristic into a data target, you have to assign an InfoArea to thecharacteristic. The characteristic is subsequently displayed in the InfoProvider tree in the AdministratorWorkbench. You can determine update rules for the characteristic, and use them to load master dataand texts to the characteristic.

You can turn a characteristic into a data target only if the characteristic contains texts or master data.At the present time, it is not possible to use update rules to load hierarchies.

A characteristic that has master data and is assigned to an InfoArea is also an InfoProvider. Thismeans that you are able to define queries for the characteristic, or rather for the master data of thecharacteristic. In this case, on the $WWULEXWHV tabstrip, you are able to switch-on dual-level navigationattributes (navigation attributes for navigation attributes) for this characteristic in its role asInfoProvider.

DQ�([SRUW�'DWD6RXUFH�

If this indicator is set, you are able to extract into other BW systems the master data, texts, andhierarchies that are in the characteristic. See also Data Mart Interface [Seite 261].



7DEVWULS��+LHUDUFK\

8VH

If you want to create a hierarchy or upload an existing hierarchy from a source system, you have to setthe WLWK +LHUDUFK\ indicator. The system generates a hierarchy table with hierarchical relationships forthe characteristic.

You can determine the following properties for the hierarchy:

• Whether or not you want to create hierarchy versions [Seite 193] for a hierarchy.

• Whether you want the entire hierarchy or just the hierarchy structure to be time-dependent [Seite195].

• Whether you want to allow the use of hierarchy intervals [Seite 198].

• Whether you want to activate the reverse signs +/- function for nodes. If you do activate thereverse signs +/- function for hierarchies, you are able to specify, for every hierarchy node that isdisplayed in the query, whether or not you want to reverse the +/- sign for the transaction databooked to each of the nodes.

• Which characteristics are allowed to appear in the hierarchy nodes.

6HH�DOVR�

Hierarchies [Seite 177]

Using Master Data and Master Data-Bearing Characteristics [Seite 93]



7DEVWULS��$WWULEXWHV

8VH

On this tabstrip, you determine whether or not the characteristic has attributes or navigation attributes,and if so, which properties they have.

6WUXFWXUH

Attributes are InfoObjects that exist already, and that are assigned logically to the new characteristic.There are the following ways to maintain attributes for a characteristic:

• Choose attributes from the $WWULEXWHV�RI�WKH�$VVLJQHG�'DWD6RXUFHV list.

• Use F4 Help for the fields that are ready for input in the $WWULEXWHV�RI�WKH�&KDUDFWHULVWLF�list, todisplay all the InfoObjects. Choose the attributes that you need.

• In the $WWULEXWHV�list, specify directly in the fields that are ready for input the name of an InfoObjectthat you want to use as an attribute� If the InfoObject that you want to use does not yet exist, youhave the option of creating a new InfoObject at this point. Any new InfoObjects that you create areinactive. They are activated when the existing InfoObject is activated.

3URSHUWLHV

Choose 'HWDLO��1DYLJDWLRQ�$WWULEXWH to get to the detailed view. In the detail view, you set the following:

7LPH�'HSHQGHQF\

You can decide for each attribute individually, whether it is time-dependent or not. If only one attributeis time-dependent, the master data table is also time-dependent. However, there can still be attributesfor this characteristic that are not time-dependent.

All the time-dependent attributes are in one table, meaning that they all have the same time-dependency. All the time-constant attributes are also in one table.

Characteristic: Business process

Table PABCPROCESS - for time-constant attributes

&KDUDFWHULVWLF��%XVLQHVVSURFHVV

$WWULEXWH��&RVW�FHQWHU�UHVSRQVLEOH

Characteristic value: 1010 Attribute value: Jones

Table QABCPROCESS - for time-dependent attributes

%XVLQHVV�SURFHVV 9DOLG�IURP 9DOLG�WR &RPSDQ\�FRGH

Characteristic value:1010

01.01.2000 01.06.2000 Attribute value: A

02.06.2000 01.10.2000 Attribute value: B

A view, MABCPROCESS, connects these two tables:

%XVLQHVVSURFHVV

9DOLG�IURP 9DOLG�WR &RPSDQ\�FRGH &RVW�FHQWHUUHVSRQVLEOH

1010 01.01.2000 01.06.2000 A Jones

02.06.2000 01.10.2000 B Jones

In master data updates, you can either load time-dependent and time-constant dataindividually, or together.



Time-dependent attributes that are used as navigation attributes in an InfoCube,cannot be used in aggregates.

6HTXHQFH�RI�$WWULEXWHV�LQ�,QSXW�+HOS

You can determine the sequence in which the attributes for a characteristic are displayed in the inputhelp. There are the following values for this setting:

• ��The attribute is not displayed in the input help

• ��The attribute appears in the first position (far left) in the input help

• ��The attribute appears in the second position in the input help.

• ��......

1DYLJDWLRQ�$WWULEXWH

You can switch navigation attributes on and off, and specify their descriptions and short texts. Thesetexts for navigation attributes can also be supplied by the attribute. If the text of the characteristicchanges, the texts for the navigation attribute are adjusted automatically. This process requires verylittle maintenance and translation resources..

When you are defining and executing queries, it is not possible to use the texts todistinguish between navigation attributes and characteristics.

As soon as a characteristic appears in duplicate (as a characteristic and as a navigationattribute) in an InfoProvider, you must give the navigation attribute a different name. Forexample, you could call the characteristic &RVW�&HQWHU, and call the navigation attribute3HUVRQ�5HVSRQVLEOH�IRU�WKH�&RVW�&HQWHU.

You use the 1DYLJDWLRQ�$WWULEXWHV�,QIR3URYLGHU function to maintain dual-level navigation attributes(navigation attributes for navigation attributes). This is possible only if the characteristic is anInfoProvider (meaning that it has master data and an InfoArea assigned to it).



7DEVWULS��&RPSRXQGLQJ

8VH

In this tabstrip, you determine whether you want to compound the characteristic to other InfoObjects.You sometimes need to compound InfoObjects in order to map the data model. Some InfoObjectscannot be defined uniquely without compounding.

For example, you can only evaluate the characteristic ‘storage location’ in connection with‘plant’, if storage location A for plant B is not the same as storage location A for plant C. Inthis case, define a compounding characteristic ‘storage location’ to ‘plant’, so it is clearwhat the characteristic is.

One exception in compounding, is the option of compounding characteristics to the source system ID[Extern]. You can do this by setting the 0DVWHU�GDWD�LV�YDOLG�ORFDOO\�IRU�WKH�VRXUFH�V\VWHP indicator. Youmay need to do this if there are identical characteristic values for the same characteristic in differentsource systems, but these values indicate different objects.

The extensive use of compounded InfoObjects, particularly if you add a lot of InfoObjectsto a compounding, can influence performance. Do not try to display hierarchical linksthrough compounding. Use hierarchies [Seite 177] instead.

5HIHUHQFH�,QIR2EMHFWV

If an InfoObject has a reference InfoObject, it has its technical properties.

• For characteristics these are the data type and length as well as the master data (attributes, textsand hierarchies). The characteristic itself also has the business semantics.

• For key figures these are the key figure type, data type and the definition of the currency and unitof measure. The referencing key figure can have another aggregation.

These characteristics can only be maintained with the reference InfoObject.

Several InfoObjects can use the same reference InfoObject. Such InfoObjects automatically have thesame technical properties and master data.

The business semantics, that is the properties, such as description, display, text selection, relevanceto authorization, person responsible, constant, and exclusively attribute, are also maintained withcharacteristics that are based on one reference characteristic.

The characteristic VROG�WR�SDUW\ is based on the reference characteristic FXVWRPHU andtherefore has the same values, attributes, and texts.

More than one characteristic can have the same reference characteristic: Thecharacteristics VHQGLQJ�FRVW�FHQWHU and UHFHLYLQJ�FRVW�FHQWHU both have the referencecharacteristic FRVW�FHQWHU.

&KDUDFWHULVWLF�&RQVWDQWV

A fixed value is assigned to a characteristic when you assign a constant. This means that thecharacteristic is available on the database (for verifications, for example) but is no longer relevant toreporting (no aggregation / drilldown is possible for this characteristic).

You must enter the internal value of the characteristic, which can be determined using the value help.

Assigning a constant is most useful with compounded characteristics.

The VWRUDJH�ORFDWLRQ characteristic is compounded with the SODQW�characteristic. If only oneplant is ever run within the application, a constant can be assigned to the plant. The



verification for the storage-location master table runs correctly with this value for the plant.In the report, however, only the storage location appears as a characteristic.

Special case:If you want to assign the SPACE constant (type CHAR) or 00..0 (type NUMC) to thecharacteristic, type # in the first position.



1DYLJDWLRQ�$WWULEXWH

8VH

Characteristic attributes can be converted into navigation attributes. They can beselected in the query in exactly the same way as the characteristics for an InfoCube.In this case, a new edge/dimension is added to the InfoCube. During the dataselection for the query, the data manager connects the InfoCube and the master datatable (‘join’) in order to fill the Query.

Costs of the cost center drilled down by person responsible:

You use the attribute ‘Cost Center Manager’ for the characteristic ‘Cost Center’. If youwant to navigate in the query using the cost center manager, you have to create theattribute ‘Cost Center Manager’ as a navigation attribute, and flag it as a navigationcharacteristic in the InfoCube.

When executing the query there is no difference between navigation attributes andthe characteristics for an InfoCube. All navigation functions in the OLAP processorare also possible for navigation attributes.

Extensive use of navigation attributes leads to a large number of tables in the connection(‘join’) during selection and can impede performance.



&UHDWLQJ�1DYLJDWLRQ�$WWULEXWHV

3UHUHTXLVLWHV

You are in InfoObject characteristic maintenance and have selected the tab page‘Attributes’.

3URFHGXUH

1. Choose 'HWDLOV�1DYLJDWLRQ�$WWULEXWHV.

2. Specify the technical name of the characteristic that you want to use as a navigation attribute, orcreate a new attribute by choosing µ&UHDWH¶. You can also directly transfer proposed attributes ofthe InfoSource.

So that you can use the characteristic as a navigation attribute, make sure the InfoObject isassigned as an attribute first, and that the option ‘Attribute only’ is not activated for thecharacteristic on the tabstrip ‘General’.

3. Choose the button ‘Details/Navigation attributes’. By clicking on the symbol ‘Navigation attributeon/off’ in the relevant column, you can define an attribute as a navigation attribute.

4. Click on the symbol and enter a name in the navigation attribute description field.

If you turn a characteristic attribute into a navigation attribute, assign a text to the navigationattribute, so that it can tell it apart from a normal characteristic in reporting.

5HVXOW

You have created a characteristic as a navigation attribute for your superiorcharacteristic.

)XUWKHU�6WHSV�WR�7DNH

You must activate the created navigation attributes in the InfoCube. The default isinitially set to “off” so as not to implicitly include more attributes than are necessary inthe InfoCube.

Note that you can subsequently create or activate navigation attributes in theInfoCube at any time. Once an attribute has been activated, you can only deactivateit if it not used in aggregates [Seite 126].

In addition, you must record navigation attributes in queries, so that they are takeninto account in reporting.



7UDQVLWLYH�$WWULEXWHV�DV�1DYLJDWLRQ�$WWULEXWHV

8VH

If a characteristic was included in an InfoCube as a navigation attribute, it can be used for navigationin queries. This characteristic can itself have further navigation attributes, called transitive attributes.These attributes are not automatically available for navigation in the query. As described in thisprocedure, they must be switched on.

An InfoCube contains InfoObject 0COSTCENTER (cost center). This InfoObject hasnavigation attribute 0COMP_CODE (company code). This characteristic in turn hasnavigation attribute 0COMPANY (company for the company code). In this case0COMPANY would be a transitive attribute that one could switch on as navigationattribute.

,QIR&XEH�,&

Characteristic

Navigation attributesNavigation attribute2nd level

0COSTCENTER0COSTCENTER

0BUS_AREA

0COMP_CODE

0PROFIT_CTR

0BUS_AREA

0COMP_CODE

0PROFIT_CTR

0COMPANY0COMPANY

3URFHGXUH

In the following procedure, we assume a simple scenario with InfoCube IC containing characteristic A,with navigation attribute B and transitive navigation attribute T2, which does not exist in InfoCube ICas a characteristic. Navigation attribute T2 should be displayed in the query.

,QIR&XEH�,&

Characteristics Navigation attributesNavigation attribute2nd level

B

T2

B

T2

T2T2A

dA

A

dA



�� &UHDWLQJ�&KDUDFWHULVWLFV

Create a new characteristic dA (denormalized A) which has the transitive attributes requestedin the query as navigation attributes (for example T2) and which has the same technicalsettings for the key field as characteristic A.

After creating and saving characteristic dA, go to Transaction SE16, select the entry for thischaracteristic from table RSDCHA (CHANM = <characteristicname> and OBJVERS = ’M’) andset field CHANAV to �. This makes characteristic dA invisible in queries. This is not necessarytechnically, but improves the readability in the query definition since the characteristic doesnot appear here.

Start Transaction RSD1 (InfoObject maintenance) again and activate the characteristic.

�� ,QFOXGLQJ�&KDUDFWHULVWLFV�LQ�WKH�,QIR&XEH

Include characteristic dA in InfoCube IC. Switch on its navigation attribute T2. The transitivenavigation attributes T2 are now available in the query.

�� $GMXVWLQJ�8SGDWH�5XOHV

Now adjust the update rules to the InfoSources for InfoCube IC so that the newly includedcharacteristic dA is computed in exactly the same way as the existing characteristic A. Thevalues of A and dA in the InfoCube must be identical.

InfoSource ISInfoSource IS

InfoCube IC

Characteristics

A dA A dA

AA

Characteristic

�� &UHDWLQJ�,QIR6RXUFHV

Create a new InfoSource with flexible updating. Assign it the DataSource of characteristic A.

Since a DataSource can only be assigned to one InfoSource at a time, you must cancelthe existing assignment of the DataSource of characteristic A to the InfoSource (withdirect updating).

�� /RDGLQJ�'DWD

7HFKQLFDO�H[SODQDWLRQ�RI�WKH�ORDG�SURFHVV�

The DataSource of characteristic A must define the master data table of characteristic A aswell as of characteristic dA. In this example the DataSource delivers key field A and attributeB. A and B must be updated in the master data table of characteristic A.

A is also updated in the master data table of dA (namely in field dA) and B is only used todetermine transitive attribute T2, which is read from the updated master data table ofcharacteristic B and written into the master data table of characteristic dA.

Since the values of attribute T2 are copied to the master data table of characteristic dA, thisresults in the following dependency, which must be taken into consideration during modeling:



If a record of characteristic A changes, it is transferred from the source system when it isuploaded into the BW. If a record of characteristic B changes, it is also transferred from thesource system when it is uploaded into the BW. However, since attribute T2 of characteristic Bis read and copied when characteristic A is uploaded, a data record of characteristic A mightnot be transferred to the BW during a delta upload of characteristic A because it has notchanged. But the transitive dependent attribute T2 might have changed just for this record andthe attribute would not be updated for dA.

The structure of a scenario for loading data depends on whether or not the extractor ofDataSource A is delta-enabled.

/RDG�3URFHVV�

1. Scenario for non-delta-enabled extractor

If the extractor for DataSource A is not delta-enabled, the data is updated in the two differentdata targets (master data table of characteristics A and dA) using a flexible InfoSource andtwo different update rules.

DataSource A DataSource A

InfoCube ICInfoCube IC

InfoSource (flexible)InfoSource (flexible)

Transfer rules

Update rules

A B ... A B ...

A B ... A B ...

A B ... A B ...

dA T2 dA T2

Routine “Read T2“

2. Scenario for delta-enabled extractor

If it is a delta-enabled extractor, an ODS object from which you can always execute a fullupdate in the master data table of characteristic dA is used. With this solution, the data is alsoupdated in two different data targets (master data table of characteristic A and new ODSobject which has the same structure as characteristic A) with a new (flexible) InfoSource andtwo different update rules using a delta update. Update rules from the ODS are also used towrite the master data table of characteristic dA with a full update.



DataSource A DataSource A

InfoCube ICInfoCube IC

InfoSource (flexible)InfoSource (flexible)

Transfer rules

Update rules

Routine “Read T2“

Full update

Delta update

A B ... A B ...

A B ... A B ...

A B ... A B ...

dA T2 dA T2

2'6�REMHFW

For both solutions, the update rules in the data target master data table of characteristic dAmust cause attribute T2 to be read. Since this can be very complicated, especially if thescenario is complicated an one has to read several levels, function modules will be provided inthe future that offer you this service.

It is better for the coding for reading the transitive attributes (in the update rules) if youinclude the attributes to be read in the InfoSource right from the beginning. This meansthat you only have update rules that perform a one-to-one mapping. The additionalattributes that are included in the InfoSource are not filled in the transfer rules. They areonly computed in the update rules in a start routine that must be created. The advantageof this is that the coding for reading the attributes (which can be quite complex) is storedin one place in the update rules.

In both cases the order at load time must be adhered to and must be implemented eitherorganizationally (load times in the scheduler) or by process chain. It is essential that themaster data to be read (in our case the master data of characteristic B) already exist in themaster data tables in the system when the data providing the DataSource of characteristic A isloaded.



&UHDWLQJ�,QIR2EMHFWV��.H\�)LJXUHV

3UHUHTXLVLWHV

If you want to assign your InfoObject to an InfoObject catalog for key figures, you have to first createthe InfoObject. You do not have to assign the InfoObject to an InfoObject catalog immediately, you cando it at a later date if you want to.

Instead of creating a new InfoObject, you can choose an InfoObject from those delivered by SAP withBusiness Content (see Installing Business Content [Seite 21].

3URFHGXUH

1. Using the context menu, select &KDQJH�,QIR2EMHFW from your InfoObject catalog for key figures.

2. Specify the key figure and a description. You can also specify a template. Choose &RQWLQXH. Youget to the InfoObject maintenance for key figures.

3. Specify a long text and a short text.

4. Edit the Tabstrip: Type/Unit [Seite 70].

5. Edit the Tabstrip: Aggregation [Seite 72].

6. Edit the Tabstrip: Further Properties [Seite 88].

7. Save, and activate the key figure you have created.

Key figures have to be DFWLYDWHG before they can be used.

6DYH means, that all changed key figures in the InfoObject catalog are created, and thatthe table entries are saved. Currently, they can not, however, be used for reporting inInfoCubes. For the time being, the DFWLYDWHG� older version remains here unaltered.

The objects (data elements, domains, programs) are not created in the data dictionaryuntil after you have DFWLYDWHG. Only now do the InfoCubes work with the activated, newversion.



7DEVWULS��7\SH�8QLW

)XQFWLRQV

.H\�)LJXUH�7\SH

Specify the W\SH. Amounts and quantities need unit fields.

'DWD�7\SH

Specify the GDWD�W\SH. For the amount, quantity, and number, you can choosebetween the decimal number and the floating point number, which guarantees moreaccuracy. For the key figures date and time, you can choose the decimal display toapply to the fields.

The following combinations of key figure and data type are possible:

Key Figure Type Data Type

AMO Amount CURR: Currency field, created asDEC

FLTP: Floating point number with 8byte precision

QUA Quantity QUAN: Quantity field, created asDEC


NUM Number DEC: Calculation or amount field withcomma and +/- sign.


INT integer INT4: 4 byte integer, whole numberwith +/- sign

DAT Date DATS: Date field (YYYYMMDD),created as char(8)

DEC: Calculation or amount field withcomma and +/- sign.

TIM Time TIMS: Time field (hhmmss), createdas char(8)

DEC: Calculation or amount field withcomma and +/- sign.

&XUUHQF\�4XDQWLW\�8QLW

You can assign a IL[HG�FXUUHQF\ to the key figure. If this field is filled, the key figurebears this currency throughout BW.



You can also assign a variable currency to the key figure. In the field XQLW�FXUUHQF\,determine which InfoObject bears the key figure unit. For quantities or amount keyfigures, either this field must be filled, or you must enter a fixed currency or amountunit.



7DEVWULS��$JJUHJDWLRQ

)XQFWLRQV

$JJUHJDWLRQ�

There are three aggregation options:

1. Minimum

2. Maximum

3. Sum

([FHSWLRQ�$JJUHJDWLRQ

This field determines how the key figure is aggregated in the Business Explorer in relation to theexception characteristic. In general, this refers to time.

The key figure ‘Number of Employees’ would, for example, be summed using thecharacteristic ‘Cost Center’, and not a time characteristic. Here you would determine atime characteristic as an exception characteristic with, for example, the aggregation ‘ODVWYDOXH’.

5HIHUHQFHG�FKDUDFWHULVWLF�IRU�H[FHSWLRQ�DJJUHJDWLRQ

In this field, select the characteristic in relation to which the key figure is to be aggregated with theexception aggregation. In general this is a time characteristic. However, you can use any characteristicyou wish.

&XPXODWLYH�DQG�1RQ�FXPXODWLYH�9DOXH

You can select the key figure as a FXPXODWLYH�YDOXH. Values for this key figure have to be posted ineach time unit, for which values for this key figure are to be reported.

1RQ�&XPXODWLYH�ZLWK�1RQ�&XPXODWLYH�&KDQJH

The key figure is a non-cumulative. You have to enter a key figure that represents the non-cumulativechange of the non-cumulative value. There do not have to be values for this key figure in every timeunit.

1RQ�&XPXODWLYH�ZLWK�LQIORZ�DQG�RXWIORZ

The key figure is a non-cumulative. You have to specify two key figures that represent the inflow andoutflow of a non-cumulative value.

For non-cumulatives with non-cumulative change, or inflow and outflow, the two keyfigures themselves are not allowed to be non-cumulative values, but must representcumulative values. They must be the same type (for example, amount, quantity) as thenon-cumulative value.

6HH�DOVR�

Non-Cumulatives [Seite 73]



1RQ�&XPXODWLYHV

'HILQLWLRQ

Non-cumulatives are evaluated by non-cumulative values. Non-cumulative values are special keyfigures that are different from other key figures (cumulative values) in data transfers and saving, aswell as in aggregational behavior.

1RQ�FXPXODWLYH�YDOXHV are those key figures that are measured in relation to a period in time; that isto say, they cannot be meaningfully cumulated over time. Non-cumulative values are summarized overtime using exception aggregation. See also: Aggregational Behavior of Non-Cumulative Values [Seite82]

Non-cumulative values such as ‘number of employees’, are cumulated usingcharacteristics such as ‘cost center’. It does not make any sense, however, to cumulatethe number of employees using different periods. With periods, for example, you can forman average.

&XPXODWLYH�YDOXHV�are those key figures that can be cumulated using all characteristics, thus alsousing time.

With the cumulative value ‘sales revenue’, for example, it makes sense to cumulate theindividual sales revenues using different periods, and using characteristics such as‘products’ and ‘customers’.

Example of the difference between non-cumulative and cumulative values:

Sales volume (cumulative value):

Sales volume 01.20 + sales volume 01.21 + sales volume 01.23 gives the total salesvolume for these three days.

Warehouse stock (non-cumulative value):

Stock 01.20 + stock 01.21 + stock 01.23 does QRW�give the total stock for these threedays.

8VH

The target of the special folder for non-cumulative values is to optimize the data transport into BW,and the data retention as well as the database access when evaluating for reporting in BW. The datatransfer from the OLTP system is minimized and only the meaningful data is saved and processed.

It is recommended that you use non-cumulative values for areas in which non-cumulatives do notregularly change completely, so, for example, for warehouse stock (retail), or for the number ofemployees.

6WUXFWXUH

0RGHO�RI�1RQ�&XPXODWLYH�9DOXHV

Non-cumulatives are modeled in BW using a non-cumulative value with the fields belonging to it forchanging the non-cumulative or for receipts or issues.

The technical storage of non-cumulatives takes place using a PDUNHU�for the current time (current non-cumulative) and the storage of non-cumulative changes, or inflows and outflows. The current, validend non-cumulative (to 31.12.9999) is stored in the marker. You can determine the current non-cumulative, or the non-cumulative at a particular point in time from the current end non-cumulative andthe non-cumulative changes or the inflows and outflows.



Queries for the current non-cumulative can be answered very swiftly, since the current non-cumulativeis created as a directly accessible value. There is only one marker that is always updated when thenon-cumulative InfoCube is compressed. So that access to queries is as quick as possible, compressthe non-cumulative InfoCubes regularly to keep the marker as up to date as possible (seeCompressing InfoCubes [Seite 412]).

For example, in month 03 the marker is read with three non-cumulative changes for aquery. In month 04, the marker is updated so that the current marker has to be read withonly one non-cumulative change for a query in month five. If the marker is not updated, itstill has four non-cumulative changes to read.

The non-cumulative changes or the inflows and outflows are cumulative values in themselves and canbe used separately as key figures or in query structures.

'DWD�7UDQVIHU�RU�6WRUDJH��DQG�$JJUHJDWLRQ�IRU�1RQ�&XPXODWLYH�9DOXHV

To optimize the data transport and data retention for non-cumulative values in BW, non-cumulativevalues are treated differently to cumulative values in both technical data transfer and storage, as wellas in aggregation:

• )HDWXUHV�RI�1RQ�&XPXODWLYH�9DOXHV��7UDQVIHUULQJ�DQG�6DYLQJ�'DWD�

− Non-cumulative values are mapped using one key figure for non-cumulative changes or twokey figures for inflows and outflows.

See also: Non-Cumulative Key Figures [Seite 75]

− A non-cumulative InfoCube has to contain a time reference characteristic. This means that thesystem has to be able to divert all time characteristics of the non-cumulative InfoCube beautomatically from this time characteristic.

See also: Time Reference Characteristics [Seite 76]

− If you use a user-specific validity table, the table is adjusted when you load it.

See also: Validity Period [Seite 78].

− Non-cumulatives are transferred in an initialization run and the change runs that follow(initialization can also be omitted here).

See also Transferring Non-Cumulative Data into BW [Seite 81]

• $JJUHJDWLRQDO�%HKDYLRU�1RQ�&XPXODWLYH�9DOXHV

A non-cumulative value always has a time-related exception aggregation.

See also: Aggregational Behavior of Non-Cumulative Values [Seite 82]

,QWHJUDWLRQ

In query definition and navigation, there is no difference in the way cumulative and non-cumulativevalues are dealt. Cumulative and non-cumulative values can be analyzed at the same time in a query.

You can also define MultiCubes that consist of non-cumulative InfoCubes (InfoCube with at least onenon-cumulative key figure) and InfoCubes.

See also: Procedure for evaluating non-cumulative values [Seite 85]



1RQ�&XPXODWLYH�.H\�)LJXUHVThere are two different ways to define non-cumulative key figures:

• 1RQ�FXPXODWLYH�NH\�ILJXUH�ZLWK�QRQ�FXPXODWLYH�FKDQJHV�

Before you can define the non-cumulative value, an additional cumulative key figurecontaining the non-cumulative change must exist as an InfoObject.

• 1RQ�FXPXODWLYH�NH\�ILJXUH�ZLWK�LQIORZV�DQG�RXWIORZV

There has to be two additional cumulative key figures as InfoObjects for non-cumulativevalues - one for inflows and one for outflows. The cumulative key figures have to have thesame technical properties as the non-cumulative key figure, and the aggregation andexception aggregation have to be SUM.

You can evaluate separately the non-cumulative changes on their own, or also the inflow and outflow,according to the type of chosen non-cumulative key figure in addition to the non-cumulative.

For aggregation, see Aggregational Behavior of Non-Cumulative Values [Seite 82]



7LPH�5HIHUHQFH�&KDUDFWHULVWLF

8VH

If the InfoCube contains a non-cumulative value, then a time-based reference characteristic for theexception aggregation of the non-cumulative value must be available. There can be several timecharacteristics per InfoCube, but only one time reference characteristic. This means that the time-based reference characteristic is the same for all the non-cumulative values of an InfoCube.

,QWHJUDWLRQ

The time reference characteristic for an InfoCube when there are several time characteristics in theInfoCube is always the “most refined”, since all other times in the InfoCube are derived from this.

An InfoCube contains warehouse key figures that should be evaluated for the calendarmonth and calendar year. In this case, the calendar month is the most refined commontime reference characteristic.

There is a difference between complete and incomplete time characteristics:

The complete time characteristics are the 6$3�WLPH�FKDUDFWHULVWLFV calendar day (0CALDAY),calendar week (0CALWEEK), calendar month (0CALMONTH), calendar quarter (0CALQUARTER),calendar year (0CALYEAR), fiscal year (0FISCYEAR), and fiscal period (0FISCPER). They are clearlyassigned to a point in time. Only these SAP time characteristics can be used as time referencecharacteristics, since you must be able to derive time characteristics automatically from the mostdetailed time characteristic must be possible with the non-cumulative folder.

Incomplete time characteristics, such as 0CALMONTH2, 0CALQUART1, 0HALFYEAR1,0WEEKDAY1, or 0FISCPER3, can be used in a non-cumulative InfoCube but cannot be a timereference characteristic, since they are not assigned to a specific point in time.

The following graphic gives an overview of the KLHUDUFK\�IRU�6$3�WLPH�FKDUDFWHULVWLFV:��

��

�� "!#��

�� $��%��

��&�'(�)!+*

�� & , -�%/.��

��01��2

�� 304��5��

��6��87

�� 6�� 9�

:�;=<�> ��?�� ; '�

��:�@�A �B?/�/��

:�;C<�> ��D�E��

��:�@�A �F�9��

If you have a non-cumulative for a week and for a month in the same InfoCube at thesame time, the roughest common time characteristic is calendar day. The timecharacteristic calendar day must be included in the InfoCube, so that it can function as areference characteristic for time-based aggregation.



9DOLGLW\�3HULRG

8VH

Only the currently valid end non-cumulative and the non-cumulative change are stored on thedatabase. To be able to evaluate the non-cumulative (for example, to calculate mean values or toexecute a drilldown according to period), it is necessary that you know for which time interval you cancalculate the non-cumulative. Otherwise, a non-cumulative from 01.01.0000 to 31.12.9999 isdisplayed.

)XQFWLRQV

9DOLGLW\�SHULRG: The differing time-based validity of non-cumulatives is mapped using a YDOLGLW\SHULRG. The validity period describes in which time period non-cumulatives have been managed.

Usually, this time interval is valid for all records in an InfoCube, for example, for all cost centers ormaterials. If data is loaded into the InfoCube from different source systems at different times, it can bebeneficial to keep the different validity periods for each subarea.

Source system 1: Delivers values for the current month

Source system 2: Delivers values for the previous month

If the source systems deliver values at different times, aggregation can be affected and can containinaccurate values over a period of time. For example, the calculated monthly average is too high (seeexample at the end of this section).

All validity periods for a non-cumulative InfoCube are stored in validity tables. The validity tableautomatically contains the most detailed, selected time characteristic of the InfoCube, the time-reference characteristic.

9DOLGLW\�'HWHUPLQLQJ�&KDUDFWHULVWLFV��Characteristics that determine the temporal validity period ofthe non-cumulative in an InfoCube.

Validity-determining characteristics are, for example, characteristics that specify which source systemthe non-cumulative belongs to, or characteristics, such as YDOXH�W\SH�(plan/actual) that are in adifferent time period. In the InfoCube maintenance, there is always an indicator that thesecharacteristics cannot be aggregated. See also: Non-Cumulative Parameter Maintenance [Seite 119]

The totals line for queries that aggregate using validity-determining characteristics isgenerally not defined. That is, the result is dependent on the drilldown situation andchanges according to the query read mode or the aggregates used. Validity-determiningcharacteristics are to be taken for evaluation in reporting into the query drilldown, or as asingle value in the filter. That is, they are not to be aggregated.

SAP recommends that when you create a non-cumulative InfoCube, you use validity-determining characteristics only in the specified cases. If you have too many validity-determining characteristics or a validity-determining characteristic with a lot ofcharacteristic values, performance decreases considerably.

If you decide later that you require more validity-determining characteristics, you canmodify the selection using the report RSDG_CUBE_VALT_MODIFY. You change the non-cumulative InfoCube using this report by selecting the new validity determiningcharacteristics and reconstructing the validity table. The structure of the non-cumulativeInfoCube remains the same. You do not have to reload the transaction data for it.

For each combination of characteristic values for the validity-determining characteristics, the validityperiod is, by default, the interval between initialization (or the first change in non-cumulative) and thelast posted non-cumulative change for this combination. That is, the validity period is created from theposting data from when the data was loaded.



When evaluating in reporting, the final non-cumulative for the requested period is evaluated using thecurrent non-cumulative and the corresponding non-cumulative changes (meaning that the non-cumulative is defined at every moment within the validity period). In this way, the non-cumulatives fortime periods, for which no change was posted, are also identified.

Assuming that every plant delivers its data separately at different times, the characteristicSODQW has to be validity determining. If you also assume that the characteristic values are%RVWRQ�3ODQW��'DOODV�3ODQW�and 6DQ�)UDQFLVFR�3ODQW, the validity interval appears asfollows:

��

��

� �� ! ��

"��#�$�%�%�% ��&�'�#�$�%�%�% ()��*#+$�%�%�%

#�#�# #�#�# #�#�# #�#�#

For the Dallas plant and the San Francisco plant, the validity table is maintained asfollows:

3ODQW )URP�IL[HG�

7R�IL[HG�

Dallas 001.2000 003.2000

San Francisco 001.2000 002.2000

The following data is then displayed in the query:

3ODQW -DQXDU\

)HEUXDU\

0DUFK

5HVXOW &RPPHQWV

Dallas: Material Stock 700 700 900 766.66 (∅ per month)

Dallas: Goods Receipts 200 0 200 400 (SUM)

San Francisco: Material Stock 200 300 (300) 250 (Not 266.66!)

San Francisco: Goods Receipts 50 100 (0) 150 (SUM)

In the query, the average amount from January and February is given as the result for theSan Francisco plant since only these time periods have been defined as valid. If you donot define a validity area, the average given that is too high (266.66).

6HH�DOVR�

Maintaining the Validity Area [Seite 80]



0DLQWDLQLQJ�WKH�9DOLGLW\�3HULRG

3UHUHTXLVLWHV

The user-specific change to the validity table can be carried out only after the corresponding InfoCubehas been activated with a Release status of 2.0B (or higher).

3URFHGXUH

The minimum and maximum loaded values of the time reference characteristic (for every feature of thevalidity table) are used as standard as a threshold for the validity period toolbar. You can change thevalidity of the individual characteristic values independently of the data loaded.

1. Call transaction RSDV

2. You get to the window 5HSRUW�RQ�9DOLGLW\�6OLFH�0DLQWHQDQFH. Specify the InfoCube here, for whichyou want to maintain the validity area, and select ([HFXWH.

3. In the window (GLWLQJ�WKH�9DOLGLW\�6OLFH�IRU�1RQ�FXPXODWLYH�,QIR&XEHV� select 'LVSOD\�&KDQJH.

4. You can now determine, for each individual feature, the update method for the lower (‘from’ mode)and upper (‘to’ mode) limits of the validity area. You have the following selection options:

• Feature " "

This mode corresponds to the standard setting, meaning that for every feature, theminimum or maximum (time-related) loaded value is taken.

The current, valid value is displayed in the )URP��)L[HG��(for the start value) or 7R��)L[HG�(for the end value). You cannot change these values.

• Feature "F"

Here you can specify a fixed start or end date. Enter the values you want in the fields IURPIL[HG (for the start value) or WR�IL[HG (for the end date).

The input format must be adjusted to the corresponding time characteristic.

If 0CALDAY is the time-reference characteristic, then the input format has tocorrespond to the date format day, month, year as specified in the global setting, forexample, 01.01.2000 or 2000/01/01. If 0CALMONTH is the time-referencecharacteristic, then the input format must contain month and year correspondingly.

• Feature "R"

Here you can specify the interval thresholds relative to the current time. Enter, as wholenumbers (positive or negative), the values you want in the field IURP�UHO� (for the startvalue) and WR�UHO� (for the end value). The specified values describe movement in unitswith time reference characteristics with reference to the current time.

If the number ‘+1’ is entered in the field UHO��WR��for time-reference characteristic0CALDAY, this means that the validity period threshold is the current next day.However, if 0CALMONTH is the time-reference characteristic, then the threshold forthe validity period is the next current month.

5. Save your entries.

5HVXOW

The modified validity table is taken into account in reporting.



7UDQVIHUULQJ�1RQ�&XPXODWLYH�'DWD�LQWR�%:

)XQFWLRQV

A first inclusion of a non-cumulative can take place as an initialization or by loading a non-cumulativechange. With initialization, you can only post and initial non-cumulative for each combination ofInfoCube characteristics. 1RQ�FXPXODWLYH�FKDQJHV�subsequently take place. There is one InfoSourcefor the initial non-cumulative and one for non-cumulative changes.

,QIR6RXUFH�IRU�LQLWLDO�QRQ�FXPXODWLYH��Transfers the current non-cumulatives once from the sourcesystem to SAP BW. This is necessary, for example, if you want to connect a system to a BW systemlater. By doing this, you can ensure that the non-cumulative situation in BW is the same as thesituation in the source system.

,QIR6RXUFH�IRU�QRQ�FXPXODWLYH�FKDQJHV��Transfers current transactions, goods receipts, goodsissues, and so on.

If an initial non-cumulative is to be loaded for a characteristic value combination, then this occurs inthe ILUVW load procedure with the InfoSource for the initial non-cumulative. If a non-cumulative changeis posted first, then no further initial non-cumulative can be posted for this characteristic valuecombination. The initial non-cumulative is then equal to zero. In the query, the first delta, whichactually contains the initial value, appears to be especially high.

For other combinations of characteristics, initialization is permitted. If you load an initialization in anInfoCube that already has data, a warning appears. However, you can continue with the initialization.Both initializations are added to the query. However, you can no longer compress the request. Beforecompression, you have to delete the request with the second initialization from the InfoCube.

When loading the data, the validity period is determined and updated correspondingly, for everycombination of validity-defining characteristic and per request.

An initial non-cumulative is firstly loaded for plant A. Non-cumulative changes are thenposted for this plant. Subsequently, a non-cumulative change is posted in the InfoCube forplant B. Data for plant C is then posted in the InfoCube with an initial non-cumulative atfirst and then with non-cumulative changes.

Only non-cumulative changes, not initial non-cumulatives, can now be posted for all threeplants.



$JJUHJDWLRQDO�%HKDYLRU�RI�1RQ�&XPXODWLYH�9DOXHVThe aggregational behavior determines whether, and how, key figure values are aggregated in reportsusing the different characteristics or characteristic values. The aggregational behavior depends onwhether you are aggregating using time characteristics or other characteristics.

If you total cumulative values such as “sales revenue” using all characteristics (that is, timecharacteristics as well), the average or the last value is often taken as the non-cumulative valuerelating to the time characteristic.

There are two possible kinds of aggregational behavior for non-cumulative values:

• 6WDQGDUG�DJJUHJDWLRQ�specifies how a key figure is compressed using all characteristics (but nottime characteristics).

• ([FHSWLRQ�DJJUHJDWLRQ specifies how a key figure is compressed using all time characteristics.

For non-cumulative values such as warehouse stock, you often want to calculate the sum of thewarehouse stock using different articles and different stock. However, you want to use the fiscal yearand calendar periods to calculate the mean value. Exception aggregation therefore is used for non-cumulative values with regard to time.

([FHSWLRQ�$JJUHJDWLRQV�ZLWK�5HJDUG�WR�7LPH

Every key figure has a standard aggregation and an exception aggregation. Non-cumulative valuesalways have summation as their standard aggregation and for time characteristics, an exceptionaggregation of unequal to summation.

The non-cumulative value ‘warehouse stock’ is aggregated using ‘summation’ forcharacteristics that are not time-related such as ‘articles’ or ‘stock’. For timecharacteristics such as “calendar month”, however, the non-cumulative value ‘warehousestock’ has the exception aggregation ‘mean’.

Meaningful aggregations for non-cumulative values are primarily “mean weighted according tocalendar days” (AV1) and “last value” (LAS). Additional exception aggregations for non-cumulativevalues are listed in the following table.

([FHSWLRQ�$JJUHJDWLRQV�IRU�1RQ�&XPXODWLYH�9DOXHV


$9� Mean value (weighted with the number of calendar days)

AV2 Mean value (weighted with the number of working days according tothe factory calendar with the ID 01)

FIR First value

/$6 Last value

MAX Maximum

MIN Minimum

The time at which non-cumulative values were posted for different materials is displayedin the following graphic. The evaluation results for the non-cumulative value for ‘material1’, for exception aggregation “mean”, and the exception aggregation “last value”, are listedin the following tables, where they are displayed once by calendar month, and once bycalendar day.



��

�! #"%$! #"$#�#�#�

�� "%��$�"%$#�#�#� �! #"%�#&#$#��

�! #"' � �"$#��

��$�"( �)!"$#�#�#�

�#&!"%�#)!"$#�#�#�

*!�!��#��+-, .��/�+0��!+-, 12��+43!�

5��!��(��67�#�8�

9#� : 9 : � : ��

��$#�:#; � 12��4�!+0��

12��4��+0��$

�$�"%&� �" �9�9�9

�#&!"( ��!"$#�#�#�

�$#�

�<#�

&#� : $�� $��)#�

In this example, we assume that validity-determining characteristics are not necessary.Therefore, the resulting validity interval is determined from the minimum and maximumpostings.

This means that the validity area here is the time interval from 12.31.1999 to 03.10.2000,since the first posting was made on the 12.31.1999 and the last non-cumulative changefor one of the materials (material 2) was posed on the 03.10.2000.

'ULOOGRZQ�RQ�WKH�1RQ�&XPXODWLYH�9DOXH�IRU�0DWHULDO��E\�&DOHQGDU�0RQWK

0HDQ�9DOXH��&DOHQGDU�'D\� /DVW�9DOXH

January 100 110

February 140 160

March 150 140

'ULOOGRZQ�RQ�WKH�1RQ�&XPXODWLYH�9DOXH�IRU�0DWHULDO��E\�&DOHQGDU�'D\

0HDQ�9DOXH��&DOHQGDU�'D\� /DVW�9DOXH

01.01.2000 90 90

02.01.2000 90 90

03.01.2000 90 90

04.01.2000 90 90

... ... ...

09.01.2000 90 90

10.01.2000 90 90

11.1.2000 99 99

... ... ...

*Note that non-cumulatives that are evaluated by calendar day, both for the mean and forthe last value, always produce the same result. The reason for this is that FDOHQGDU�GD\ is



the smallest unit of time to which the data is transferred. This always occurs when youdrilldown on the most detailed time characteristic.



3URFHGXUH�IRU�(YDOXDWLQJ�1RQ�&XPXODWLYH�9DOXHVFor evaluating on non-cumulative values, you can usually use the corresponding %XVLQHVV�&RQWHQWSee also: Transferring Business Content [Seite 21]

The following InfoSources are delivered:

• 2LIS_40_S278: Transfers the current non-cumulative from the source system to SAP BW once.

• 2LIS_03_BF: Transfers current transactions (goods receipts, goods issues, and so on).

These InfoSources are not specific to retail, even though the choice of name may suggest this. Theyare standard extractors for initial non-cumulatives in the Logistics area (Retail, Consumer Products,AFS, Beverage, and so on).

1RQ�FXPXODWLYH�,QIR&XEHV�are also delivered with Business Content, for example:

• 0RT_C36: Most current article stock (that is the last time stock was evaluated) on a weekly basis.

• 0RT_C37: Most current article stock (that is the last time stock was evaluated) on a monthly basis.

• 0RT_C41: MultiCube containing the non-cumulative InfoCube 0RT_C37

If you want to model your own objects, proceed as follows:

�� 6RXUFH�6\VWHP

There are two extraction modes for non-cumulatives in the source system. The DataSourcesfor non-cumulatives have to support one of these extraction modes.

�� 0RGHOLQJ�

Determine in which way you wish to evaluate the non-cumulative value. If you only wish toevaluate the non-cumulative, or the non-cumulative changes as well as the non-cumulativeusing a particular time period, choose modeling as a non-cumulative value with non-cumulative changes. If you also want to evaluate the inflows and outflows separately, thenchoose modeling as a non-cumulative key figure with inflows and outflows.

�� .H\�)LJXUH�'HILQLWLRQ�

The non-cumulative change, or inflows and outflows, which you require for the definition of thenon-cumulative value, must already be created as InfoObjects if the non-cumulative value iscreated. Therefore, firstly define either the non-cumulative change, or the in- and outflows asnormal cumulative values where necessary. These key figures must correspond to the non-cumulative values, which still have to be defined, in the type definition. The non-cumulativechanges, or inflows and outflows, must have ‘summation’ as aggregation and as exceptionaggregation.

Define the non-cumulative value by assigning to it the previously defined non-cumulativechange, or in- and outflows.

Choose the exception aggregation you want to use. Standard aggregation always equals“summation”.

�� ,QIR&XEH�'HILQLWLRQ�

D�� %DVLF&XEH

If you transfer the non-cumulative value into the InfoCube, then the respective cumulativevalues (non-cumulative change, or in- and outflows) are automatically included in theInfoCube definition.

Take all of the time characteristics into the InfoCube definition, with which you wish toevaluate the InfoCube data.

You can also choose one or more characteristics via ([WUDV →�0DLQWDLQ�1RQ�&XPXODWLYH9DOXHV, which further specify the validity of the non-cumulative. These characteristics areadditionally listed in the validity table of the non-cumulative right down to the most detailedtime-reference characteristic.



Refer to the notes for defining validity tables. You do not usually have to include additionalvalidity-determining characteristics in the validity table.

Activate the InfoCube.

E�� 0XOWL&XEH

In a MultiCube in which one or several BasicCubes with non-cumulative key figures areincluded, the following peculiarity occurs.

The time dimension has to be identical in all of these non-cumulative InfoCubes (that is, matchin all InfoObjects) and the MultiCube also has to contain this time dimension, which meansthat the time characteristic of the MultiCube is predefined.

A MultiCube is defined from non-cumulative InfoCube BC1 and InfoCube IC1 The timecharacteristic 0CALMONTH for the MultiCubes comes from BC1 and IC1, whereas thetime characteristic 0CALYEAR only comes from BC1. Any further non-cumulativeInfoCubes have to contain the same time characteristics as BC1.

Non-Cummul.Cube BC1

InfoCube IC1

0CALMONTH

0CALYEAR

0CALMONTH

0CALDAY

0CALQUARTER

MultiCube

0CALMONTH

0CALYEAR

from BC1 and IC1

from BC1

�� ,QIR6RXUFH�'HILQLWLRQ�

Create the InfoSource(s). If you wish to load an initial non-cumulative, note that you mustcreate two differing InfoSources for posting the initial non-cumulative and for posting the non-cumulative changes. However, initialization is not absolutely necessary.

Only non-cumulatives, therefore no non-cumulative changes, inflows and outflows, or othercumulative values can be loaded with the InfoSource for the initialization.

When using the InfoSource for non-cumulative changes, only the changes, or in- and outflows,and not the non-cumulative itself, are updated.

You assign this InfoSource in the maintenance using DataSource transfer rules.

�� /RDGLQJ�'DWD�

If you want to load an initial non-cumulative, load this ILUVW, followed by the non-cumulativechanges.

If a non-cumulative change is updated when loading data for the first time, then no furtherinitial non-cumulative can be loaded for this characteristic value.

When loading data, the validity areas for the individual validity-defining characteristicvalues are automatically updated.

�� 4XHU\�'HILQLWLRQ�



Both the non-cumulative value and the non-cumulative change, or in- and outflows, areavailable for selection for the query definition in the InfoCube.

With evaluations in reporting, there is no difference in the way cumulative and non-cumulativevalues are dealt. Cumulative and non-cumulative values can be evaluated at the same time ina query, since the key figures are automatically aggregated correctly.



7DEVWULS��$GGLWLRQDO�3URSHUWLHV

)XQFWLRQV

%XVLQHVV�([SORUHU

'HFLPDO�3ODFHV

You can determine how many decimal places the field has by default in the BusinessExplorer. This layout can be overwritten in queries.

/D\RXW

This field describes with which scaling the field in the Business Explorer is displayedby default. This layout can be overwritten in queries.

([FOXVLYHO\�$WWULEXWH�

If you choose H[FOXVLYHO\�DWWULEXWH, then the created key figure can only be used asan attribute for another characteristic, but cannot be used as a dedicated key figure inthe InfoCube.



(GLWLQJ�,QIR2EMHFWV

3UHUHTXLVLWHV

You have already created an InfoObject.

6HH�DOVR�

Creating InfoObjects: Characteristics [Seite 33]

Creating InfoObjects: Key Figures [Seite 69]

3URFHGXUH

Select the InfoObject you want to maintain, and, using the context menu, choose&KDQJH. Alternatively, select the InfoObject you want to maintain, and choose the0DLQWDLQ�,QIR2EMHFWV icon from the menu toolbar. You get to the InfoObjectmaintenance.

You are not able to delete any characteristics that are still being used in an InfoCube, anODS object, an InfoSource, compounding, or as attributes. It is a good idea, therefore, toexecute a where-used list, whenever you want to delete a characteristic. If thecharacteristic is being used, you have to first delete the InfoCube or the InfoObject fromthe InfoCube. If errors occur, or applications exist, an error log appears automatically.

&KDQJH�2SWLRQV

It is usually possible to change the meaning and the text of an InfoObject. However,only limited changes can be made to certain properties, in case the InfoObject isused in InfoCubes or ODS objects.

With key figures, for example, you cannot change the property type, the data type, orthe aggregation, if the key figure is still being used in an InfoCube/ODS object. Usethe &KHFN function to get hints on incompatible changes.

With characteristics, you can change compounding and data type, but only if no datahas yet been loaded.



$GGLWLRQDO�)XQFWLRQV�LQ�WKH�,QIR2EMHFW�0DLQWHQDQFH

8VH

There are other functions available in addition to those of creating, changing, anddeleting InfoObjects.

)XQFWLRQV

,QVHUWLQJ�'RFXPHQWV

Use this function to add documents to InfoObjects in different formats (for example,MS Word, PowerPoint, PDF, BMP, HTML).

6HH�DOVR��&UHDWLQJ�%:�'RFXPHQWDWLRQ�>([WHUQ@

7UHH�'LVSOD\

Use this function to display, in a clear tree structure, all the settings for an InfoObjectthat have been made in the tabstrips of the InfoObject maintenance.

9HUVLRQ�&RPSDULVRQ

This function compares the following InfoObject versions:

• the active and revised versions of an InfoObject

• the active and Content versions of an InfoObject

• the revised and Content versions of an InfoObject

This enables you to compare all the settings made in the tabstrips of the InfoObjectmaintenance.

7UDQVSRUW�&RQQHFWLRQ

You can choose and transport InfoObjects. All those BW Objects that are needed toensure a consistent status in the target system, are collected automatically.

:KHUH�8VHG�/LVW

You determine which other objects in BW also use a specific InfoObject.

You determine the consequences of a particular change to an InfoObject, andwhether this change is permitted at the moment or not.

5HSRVLWRU\�%URZVHU

Use this function to see how the different BW Objects relate to one another.

For example:

• Structural dependencies such as InfoObjects, for example, from which an InfoCube is structured.

• Connections between BW objects, such as the data flow from a source systemacross an InfoCube to a query.

The dependencies can be displayed and exported in HTML format.

+\SHUOLQNV

Technical objects, such as data elements or attributes, are often underlined in blue inthe InfoObject maintenance. In this case, use the context menu (right mouse click) tocall up a selection of possible functions, for example, jumping to the detail view



(dictionary), table contents, table type, and so on. Double-click to get to the detaildisplay.

$FWLYDWLQJ�LQ�WKH�%DFNJURXQG

In some cases (for example when converting large amounts of data), activating anInfoObject can take a very long time. The activation process terminates after aspecified amount of time. In these cases, you can activate InfoObjects in thebackground with the help of a background job. In the InfoObject maintenance,choose &KDUDFWHULVWLF�→�$FWLYDWH�LQ�%DFNJURXQG.



'DWD�7DUJHWV

'HILQLWLRQ

A data target is an object into which data is loaded. Data targets are the physical objects that arerelevant during data modeling and when loading the data.

6WUXFWXUH

Data targets are:

• InfoCubes [Seite 105]

• ODS objects [Seite 160]

• InfoObjects [Seite 93] (characteristics with attributes, texts or hierarchies).

There are differences between:

• Pure data targets for which no queries can be created or executed. An InfoCube might only beused as a data source for another InfoCube. This is also possible for ODS objects andInfoObjects.

If you want a characteristic to appear in the InfoProvider tree, you have to assign an InfoAreato it. You can define update rules for the characteristic in the InfoProvider tree, and use themto load attributes and texts.

You can turn a characteristic into a data target only if the characteristic contains texts orattributes. It is not possible to use update rules to load hierarchies.

• Data targets for which queries can be defined. These are called InfoProviders.

See also InfoProviders [Seite 304].



8VH�RI�0DVWHU�'DWD�DQG�0DVWHU�'DWD�%HDULQJ&KDUDFWHULVWLFV

'HILQLWLRQ

0DVWHU�GDWD is data that remains unchanged over a long period of time. It contains information that isalways needed in the same way. Characteristics [Seite 28] can bear master data in BW. With masterdata you are dealing with attributes, texts or hierarchies.

If characteristics have attributes, texts, or hierarchies at their disposal then we speak of PDVWHU�GDWD�EHDULQJ�FKDUDFWHULVWLFV.

The master data of a cost center contains the name, the person responsible, the relevanthierarchy area, and so on.

The master data of a supplier contains the name, address, and bank details.

The master data of a user in the SAP system contains his/her access authorizations to thesystem, the standard printer, start transaction, and so on.

8VH

When you create a characteristic InfoObject, it is possible to assign attributes, texts, hierarchies, or acombination of this master data to the characteristic. If a characteristic bears master data, you can editit in BW in master data maintenance.

See also Creating InfoObjects: Characteristics [Seite 33]

Master data for a characteristic is uploaded into BW using an InfoSource with direct updating.

See also InfoSources with Direct Updating [Seite 273].

You can also update characteristics with master data flexibly. In this case the InfoObject becomes thedata target or InfoProvider. However, you must explicitly declare the InfoObject in the InfoObjectmaintenance to be the InfoProvider.

See also InfoSources with Flexible Updating [Seite 273].



0DVWHU�'DWD�7\SHV��$WWULEXWHV��7H[WV��DQG�+LHUDUFKLHV

8VH

There are three different types of master data in BW:

�� $WWULEXWHV

Attributes are InfoObjects that are logically subordinate to a characteristic and cannot be selected inthe query.

You can assign the attributes 3HUVRQ�5HVSRQVLEOH�IRU�WKH�&RVW�&HQWHU, and 7HOHSKRQH1XPEHU�RI�WKH�3HUVRQ�5HVSRQVLEOH�IRU�WKH�&RVW�&HQWHU (characteristics as attributes), aswell as 6L]H�RI�WKH�&RVW�&HQWHU�LQ�6TXDUH�0HWHUV�(Key figures as attributes), to a &RVW&HQWHU.

�� 7H[WV

You can create or load text descriptions for master data in BW. Texts are stored in a text table.

The 1DPH�RI�WKH�3HUVRQ�5HVSRQVLEOH�IRU�WKH�&RVW�&HQWHU is assigned to the master data3HUVRQ�5HVSRQVLEOH�IRU�WKH�&RVW�&HQWHU in the text table.

�� +LHUDUFKLHV

A hierarchy forms a summarization and grouping for a characteristic according to individual evaluationcriteria. See Hierarchies [Seite 177] for a comprehensive description.

)XQFWLRQV

7LPH�GHSHQGHQW�DWWULEXWHV

If the characteristic has at least 1 time-dependent attribute, a time interval is specified for this attribute.$V�PDVWHU�GDWD�PXVW�H[LVW�EHWZHHQ�WKH�SHULRG�RI��DQG��LQ�WKH�GDWDEDVH��WKHJDSV�DUH�ILOOHG�DXWRPDWLFDOO\��VHH�0DLQWDLQLQJ�7LPH�'HSHQGHQW�0DVWHU�'DWD�>6HLWH��@��

7LPH�GHSHQGHQW�WH[WV

If you create time-dependent texts, the text for the key date is always displayed in the query.

7LPH�GHSHQGHQW�WH[WV�DQG�DWWULEXWHV

If the texts and the attributes are time-dependent, the time intervals do not have to agree.

/DQJXDJH�GHSHQGHQW�WH[WV

In the Characteristic InfoObject Maintenance [Seite 33], you can determine whether the texts arelanguage-specific (for example, with product names: German → Auto, English → car), or not (forexample, customer names). Only the texts in the selected language are displayed.

If they are language-dependent, you have to upload all texts with a language indicator.

,I�RQO\�WH[WV�H[LVW�

You can also just create texts for a characteristic, without maintaining attributes. When you are loadingtexts, the entries in the SID table are retrieved automatically.



0DVWHU�'DWD�0DLQWHQDQFH

8VH

You can run master data maintenance in two different sessions:

• Creating or Changing Master Data [Seite 96]

• Deleting Master Data at Single Record Level [Seite 100]

,QWHJUDWLRQ

You cannot run the two sessions at the same time, meaning that

• if you choose &KDQJH in the master data maintenance, the deletion function is deactivated, and isonly reactivated once you have saved your changes.

• if you select a master data record in the master data maintenance and choose 'HOHWH, the createand change function is deactivated, and is only reactivated once you have finished the deletionprocess by choosing 6DYH.

)XQFWLRQV

&UHDWLQJ�RU�&KDQJLQJ�0DVWHU�'DWD�

You can add new data records for master data for a characteristic, change single data records formaster data or else select several data records for master data and assign global changes to them.

'HOHWLQJ�0DVWHU�'DWD�DW�6LQJOH�5HFRUG�/HYHO�

You can delete single records or else select and delete several records.

You can only delete data records for master data if the master data you want to delete stillhas no transaction data, is not used as an InfoObject attribute and has no hierarchies.



&UHDWLQJ�DQG�&KDQJLQJ�0DVWHU�'DWD

3UHUHTXLVLWHV

If master data is maintained for a master data-bearing characteristic, you can change it in BW orcreate additional master data records.

3URFHGXUH

1. You get to the master data maintenance via

,QIR2EMHFW 7UHH → ,QIR2EMHFW�→�&RQWH[W�0HQX (ULJKW�PRXVH�EXWWRQ� → 0DLQWDLQ 0DVWHU�'DWD�

or

,QIR6RXUFH�7UHH�→�$SSOLFDWLRQ�&RPSRQHQW�→�0DVWHU�'DWD�,QIR6RXUFH�→�&RQWH[W�0HQX��ULJKW

PRXVH�EXWWRQ��→�0DLQWDLQ�0DVWHU�'DWD�

or in the InfoObject maintenance by choosing 0DLQWDLQ�0DVWHU�'DWD

A selection screen that you might want to edit appears for restricting the master data.

2. Taking into account the options from F4 Help, select the relevant data.

You get to the list header for the selection. The list header is also displayed if no hits havebeen found for your selection, so that you can enter new master records for particular criteria.

3. Make your changes with the help of the relevant maintenance function.

&UHDWLQJ�QHZ�PDVWHU�UHFRUGV

Choose &UHDWH�to add new master records. New records are tagged onto the end of the list.

&KDQJLQJ�VLQJOH�UHFRUGV

A double-click on a data record takes you to the individual maintenance. Make the relevantchanges in the following change dialog box.

0DVV�FKDQJHV

Select several records, and choose &KDQJH� A change dialog box appears in which theattributes and also texts are offered. Enter the relevant entries that are then transferred to allthe selected records.

4. Choose 6DYH�

If a newly created record already exists in the database but does not appear in theprocessing list (because you have not selected it in the selection screen) there is nocheck. Instead, the old records are overwritten.

If you change master data in BW, you must adjust the respective source systemaccordingly. Otherwise the changes will be overwritten in BW the next time you uploaddata.

Master data, which you have created in BW, remains even after you have uploaded datafrom the source system.

Note the exception for time-dependent master data [Seite 97].



0DLQWDLQLQJ�7LPH�'HSHQGHQW�0DVWHU�'DWD

8VH

The maintenance of the master data is more complex with time-dependent master data, as the validityperiod of a text is not necessarily in concordance with that of an attribute master record.

The InfoObject 8VHU�PDVWHU�UHFRUG has the time-dependent attribute 3HUVRQQHOQXPEHU, and the time-dependent text 8VHU�QDPH. If the user name changes (aftermarriage, for example), the personal number still remains the same.

3UHUHTXLVLWHV

In the InfoObject Maintenance [Seite 33], make sure that the relevant InfoObject is flagged as ‘time-dependent’.

3URFHGXUH

To maintain texts with time-dependent master data, proceed as follows:

1. Select the master data that want, and select one of the three text pushbuttons.

If you choose 'LVSOD\�WH[W, a list appears containing all the texts for this characteristic value.By double clicking, you can select a text. A dialog box appears with the selected text for thecharacteristic value.

If you choose &KDQJH�WH[W, a list appears containing all the texts for this characteristic value.By double clicking, you can select a text. A dialog box appears with the selected text for thecharacteristic value, which you can then edit.

If you choose &UHDWH�WH[W, a dialog box appears in which you can enter a new text for thecharacteristic value.

The texts always refer to the selected characteristic value.

2. Choose 6DYH�

When you select time-dependent master data with attributes, the list displays the texts thatare valid until the end of the validity period of the characteristic value. When you changeand enter new texts, the lists are updated.

Master data must exist between the period of 01.01.1000 and 12.31.1000 in the database.When you create data, gaps are automatically filled. When you change or initially createmaster data, in some cases, you must adjust the validity periods of the adjoining recordsaccordingly.

If a newly created record already exists in the database but does not appear in theprocessing list (because you have not selected it in the selection screen) there is nocheck. Instead, the old records are overwritten.

If you change master data in BW, you must adjust the respective source systemaccordingly. Otherwise the changes will be overwritten in BW the next time you uploaddata.

Master data, which you have created in BW, remains even after you have uploaded datafrom the source system.



7LPH�'HSHQGHQW�0DVWHU�'DWD�IURP�'LIIHUHQW�6\VWHPV

8VH

You have the option of uploading time-dependent characteristic attributes from different systems, evenif the time intervals of the attributes are different.

)XQFWLRQV

If you load time-dependent characteristic attributes from different source systems, these are written inthe master data table, even if the time intervals are different.

From source system 1, load attribute A with the values 10, 20, 30 and 40. From sourcesystem B, load attribute B with the values 15, 25, 35 and 45. The time intervals of the lasttwo values are different.

MrsSteward

MrMajor

MrCalf

MrsSmith

Vehicles Accessories Light bulbs Pumps

Source system 1

Person responsible

Source system 1

Person responsible

Source system 2

Cost center

Source system 2

Cost center

Time

Time

��

MrsSteward/Vehicles

MrCalf/Light

bulbs

MrsSmith/Pumps

Mr Major/

AccessoriesMaster datatable in BWMaster datatable in BW

8SORDG �� "! � �#��$��

�� %� �� &�%��"! � �#��$��

Mrs Smith/Light bulbs

The system inserts another row into the master data table:

GDWHWR GDWHIURP 3HUVRQ5HVSRQVLEOH

&RVW�&HQWHU

01.01.1999 28.02.1999 Mrs Steward Vehicles

01.03.1999 31.05.1999 Mr Major Accessories

01.06.1999 31.08.1999 Mr Calf Light bulbs

01.09.1999 10.09.1999 Mrs Smith Light bulbs

11.09.1999 30.09.1999 Mrs Smith Pumps



'HOHWLQJ�0DVWHU�'DWD�DW�6LQJOH�5HFRUG�/HYHO

8VH

Besides creating and changing master data you can also use a deletion mode at single record level.

3URFHGXUH

5. You get to the deletion mode from the master data maintenance by choosing

,QIR2EMHFW 7UHH → ,QIR2EMHFW�→�&RQWH[W�0HQX (ULJKW�PRXVH�EXWWRQ� → 0DLQWDLQ 0DVWHU�'DWD�

or

,QIR6RXUFH�7UHH�→�$SSOLFDWLRQ�&RPSRQHQW�→�0DVWHU�'DWD�,QIR6RXUFH�→�&RQWH[W�0HQX��ULJKW

PRXVH�EXWWRQ��→�0DLQWDLQ�0DVWHU�'DWD�

or from the InfoObject maintenance by choosing 0DLQWDLQ�0DVWHU�'DWD�

A selection screen that you might want to edit appears for restricting the master data.

6. Taking into account the options from F4 Help, select the relevant data.

3. You get to the list overview for the selection and have 2 options:

a. In the list select the master data records to be deleted, choose GHOHWH and VDYH your entries.

b. Select additional master data using GDWD�VHOHFWLRQ, select the master data records that are to bedeleted, and choose GHOHWH. Repeat the selection on demand where necessary and choose 6DYHto finish.

The records marked for deletion are first written into the deletion buffer. If you choose 6DYH,the system generates a where-used list for the records marked for deletion. Master data,which is not used any more in transaction data, is deleted.



'HOHWLQJ�0DVWHU�'DWD�DQG�7H[WV�IRU�D�&KDUDFWHULVWLF

8VH

You can delete master data and texts directly from the master data table in BW. Contrary to deleting atsingle record level you can use this function to delete all the existing master data and texts for acharacteristic in one action.

3UHUHTXLVLWHV

To be able to delete master data, no transaction data may exist in BW for the affected master data, itmust not be used as an attribute for InfoObjects, and no hierarchies may exist for this master data.

)XQFWLRQV

You get to the function 'HOHWH�PDVWHU�GDWD via:

,QIR2EMHFW 7UHH → ,QIR2EMHFW�→�&RQWH[W�0HQX (ULJKW�PRXVH�EXWWRQ� → 'HOHWH 0DVWHU�'DWD�

or

,QIR6RXUFH�7UHH�→�$SSOLFDWLRQ�&RPSRQHQW�→�0DVWHU�'DWD�,QIR6RXUFH�→�&RQWH[W�0HQX��ULJKW�PRXVH

EXWWRQ��→�'HOHWH�0DVWHU�'DWD�

If you choose the function 'HOHWH�PDVWHU�GDWD, the program checks the entries in the affected masterdata table, one after the other. You can only delete master data that has no transaction data, that isnot used as an InfoObject attribute and that has no hierarchies.



$FWLYDWLQJ�0DVWHU�'DWD�DQG�7H[WV

3UHUHTXLVLWHV

The Scheduler [Seite 350] has already imported master data and texts into BW.

3URFHGXUH

$FWLYDWLQJ�PDVWHU�GDWD

When you update master data, it is imported from an R/3 system in an inactive state.So that reporting can access the new master data, you should activate it first.

Choose ,QIR2EMHFW�7UHH�→ &RUUHVSRQGLQJ�&KDUDFWHULVWLF�→ �Right mouse button�→$FWLYDWH�

When you DFWLYDWH, there are two scenarios:

�� 7KH�UHOHYDQW�PDVWHU�GDWD�LV�DOUHDG\�EHLQJ�XVHG�LQ�DJJUHJDWHV�

If you are already using the existing master data in aggregates in the InfoCube, youcannot activate the master data individually.�In this case, proceed as follows:

a. In the menu bar, choose 7RROV�→�&KDQJH�6WUXFWXUH�→�,QIR2EMHFW�/LVW

A list is displayed containing all characteristics that are affected by changes to masterdata.

b. Select the corresponding characteristic and choose 3HUIRUP�VWUXFWXUH�FKDQJH�

The system now automatically restructures and activates the master data and itsaggregates.

Please note that this process can take several hours if the volume of data is relativelyhigh. You should therefore activate all characteristics that are affected by master datachanges, at the same time and at regular intervals.

�� 7KH�UHOHYDQW�PDVWHU�GDWD�LV�QRW�XVHG�LQ�DJJUHJDWHV�

Choose ,QIR2EMHFW�7UHH�→�&RUUHVSRQGLQJ�&KDUDFWHULVWLF�→ Right mouse button�→$FWLYDWH�

The system now automatically activates the master data and can be used directly inreporting.

$FWLYDWLQJ�WH[WV

The texts are automatically set to active and can be used directly in reporting. You do not need toDFWLYDWH�manually.



6LPXODWH�/RDGLQJ�RI�0DVWHU�'DWD

8VH

This function allows you to simulate the loading of a master data packet before loading the data intoBW. This means you can be aware of errors in the data loading early on and remove problems inadvance.

,QWHJUDWLRQ

You can get to the function from the 0RQLWRU�'HWDLOHG�6FUHHQ → Tabstrip 8SGDWHG�'DWD or $OO�,'RFV�

)HDWXUHV

,Q�WKH�FDVH�RI�GDWD�ZLWKRXW�HUURUV, the loading simulation provides you with a detailed description ofthe processes that are run during loading. The left-hand frame structures the various master datatypes that can be loaded in a tree. Either:

• Time-dependent texts and/or time-constant texts, or

• Time-dependent master data attributes and/or time-constant texts

On the level below the master data types, you will see the different database operations that arecarried out during loading. (For example, modifying, inserting, deleting)

By clicking on a master data type or on a database operation, or by using drag-and-drop on theseobjects in the right-hand frame, you can obtain a detailed view of the respective uploaded data.

,Q�WKH�FDVH�RI�LQFRUUHFW�GDWD, only the master data types, and not the database operations, aredisplayed in the left-hand frame.

The corresponding error log appears in the lower frame.



0DVWHU�'DWD�/RFN

8VH

During the master data load procedure, the master data tables concerned are locked so that, forexample, data cannot be loaded at the same time from different source systems, which would bringabout inconsistencies.

In certain cases, for example if a program termination occurs during the load process, then the locksare not automatically removed after the load process.

You then have to manually delete the master data locks.

$FWLYLWLHV

You get to the master data lock overview via the padlock symbol. Using the context menu (rightmouse button), choose the corresponding master data symbol, and delete the master data lock.



,QIR&XEH

'HILQLWLRQ

InfoCubes are data targets. An InfoCube describes (from a reporting point of view) a self-containeddataset of a business-orientated area. It can also be an InfoProvider if it is used to execute reports andanalyses in BW.

%:

�

6

(

59

(

5

%

(

[

SAP BW Architecture

��

��

�� ! ��"��#�$�� # �� ! �%"��#�$�� %�#

&('*)&('*)

+�,.-�/10324#5�6 2(7

+�,8-�/10324#5�6 297

+�,.-�/10324#5�6 2(7

+�,8-�/10324#5�6 2(7

+%,.-�/10324#5�6 2(7

+�,8-�/10324#5�6 2(7

+%,.-�/10324#5�6 2(7

+�,8-�/10324#5�6 297

: � � !��;# %�<� � " ��: � � !��;# %�� " �� : � � !��;# %��=� " ��: � � !��;# ��<� � " ��

8VH

An InfoCube is assigned to an InfoArea.

InfoCubes are supplied with data from one or more InfoSources or ODS objects (BasicCube) or froman external system (RemoteCube).

6WUXFWXUH

There are various types of InfoCubes:

1. Physical data storage: BasisCube [Seite 106]

2. Virtual data storage:

− RemoteCube [Seite 333]

− SAP RemoteCube [Seite 331]

− Virtual InfoCube with Services [Seite 335]

Only BasicCubes physically contain data on the database. Virtual InfoCubes simply display logicalviews of a dataset. The InfoCube type is not important as far as reporting is concerned.

,QWHJUDWLRQ

You can access the characteristics and key figures defined for an InfoCube in the Query definition[Extern] in the Web or in BEx.



%DVLF&XEHV

The following unit relates to the administrative view of BasicCubes. From a reporting pointof view, meaning for the reporting end user, there is no difference between the InfoCubeand the BasicCube. For reporting, the BasicCube properties described here also apply toInfoCubes.

'HILQLWLRQ

“Data containers”, on which reports and analyses in BW are based, are called BasicCubes. You obtaintwo types of data; key figures and characteristics. A single BasicCube contains (from an evaluationpoint of view) a self-contained dataset, for example, from a business area.

A BasicCube is a collection of relational tables arranged according to the star schema: A large facttable in the center, surrounded by several dimension tables.

8VH

A BasicCube is assigned to an InfoArea.

BasicCubes are supplied with data from one or several InfoSources.

6WUXFWXUH

A BasicCube consists of several InfoObjects and is structured according to the star schema, thismeans there is a (large) fact table that contains the key figures for the BasicCube surrounded byseveral (smaller) dimension tables, in which the characteristics of the BasicCube are stored.

In contrast to the ODS object, the data fields in the BasicCube fact table cannot contain characterfields as key figures. Character fields are interpreted as keys.

The fact table and dimensions [Seite 113] are linked to one another using identifying, abstractnumbers (IDs), which are in the key part of the particular database table. As a result, the key figures ofthe BasicCube are related to the characteristics of the dimension. The characteristics determine thelevel of detail in which the key figures are managed in the BasicCube.

Characteristics that logically belong together (district and area, for example, belong to the regionaldimension) are grouped together in a dimension. By adhering to this design criterion, dimensions areto a large extent independent of each other, and dimension tables remain small as regards datavolume, which is desirable for performance reasons.

The fact table and dimension tables are both relational database tables.

6WDU�6FKHPD



Customer Dimension

K BranchChain

Sales OrganizationK Sales Rev.

Cust. No.

��

T

��

��

P

Product Description

NameCust No.

Customer Master Data

Loc.Industry Key

LanguageProduct No.

Product No. ABC Key Figures�� !�"�$#%�&� ��&�'�(��")!�

��* !�"�$#%�&� ��!��&�'�

Product Number

Product Group

Brand Merchandise Category

Time Period Fiscal Year

Head Office

P Z Reduction Sales Overheads Non-cumulative Values

Characteristics point to the master data, with their attributes and text descriptions. All InfoObjects(meaning characteristics with their master data as well as key figures) are available across allBasicCubes, contrary to dimensions, which represent the special organizational form of characteristicsin a BasicCube.

The master data in BW is transferred from the source system by an upload, but it can also beenhanced with other data from external systems.

Similarly, the extractor program provides the BasicCubes with data from the prestored sourcesystems. Alternatively, you can also transfer external non-SAP data.

,QWHJUDWLRQ

The BasicCube is filled using the Scheduler, provided that the update rules [Seite 201] are maintained.

For higher-performance access, you can maintain aggregates for the BasicCube [Seite 133], in whichInfoCube data is stored redundantly, and in an aggregated form.

You can either use a BasicCube directly as an InfoCube for reporting, or you can use it together withother data targets as a basis for a MultiProvider.

6HH�DOVR�

SAP Demo Cubes [Extern]

Checking the Data Loaded in the BasicCube [Seite 117]



7UDQVDFWLRQDO�,QIR&XEHV

'HILQLWLRQ

Transactional InfoCubes differ from standard InfoCubes in that the former have an increased writeaccess performance level. Standard InfoCubes are technically optimized for read-only access and fora comparatively small number of simultaneous accesses.

The transactional InfoCube was developed to meet the demands of SAP Strategic EnterpriseManagement (SEM).

8VH

Transactional InfoCubes are used only in conjunction with SEM. The data from this kind of InfoCube isaccessed transactionally, meaning data is written to the InfoCube (possibly by several users at thesame time) and reread as soon as possible. Standard BasisCubes are not suitable for this. You shoulduse standard BasisCubes for read-only access (for example, reading reference data).

6WUXFWXUH

Transactional InfoCubes can be filled with data using two different methods: Loading planned data viaSEM or via BW Staging, where no planned data can be loaded. You have the option to convert atransactional Info Cube Select Convert Transactional InfoCube using the context menu in yourtransactional InfoCube in the�InfoProvider tree. By default, the 7UDQVDFWLRQDO�&XEH�&DQ�%H�3ODQQHG�/RDGLQJ�RI�'DWD�1RW�3HUPLWWHG�is selected. The system then fills the cube using the SEM functions.Switch this setting to 7UDQVDFWLRQDO�&XEH�&DQ�%H�/RDGHG�:LWK�'DWD��3ODQQLQJ�1RW�3HUPLWWHG��if youwant to fill the cube with data via BW Staging.

Using the SEM process, data is written to a transactional InfoCube data request. As soon as thenumber of records in a data request exceeds a threshold value, the request is closed and a rollup iscarried out for this request in defined aggregates (asynchronously). You can still rollup and defineaggregates, collapse, and so on, as before.

According to the database on which they are based, transactional InfoCubes differ from standardBasis Cubes in the way they are indexed and partitioned. For an Oracle DBMS this means, forexample, no Bitmap indices for the fact table and no partitioning (initiated by BW) of the fact tableaccording to the package dimensions.

Reduced read-only performance is accepted as a drawback of transactional InfoCubes, in the face ofthe parallel (transactional) writing option and improved write performance.

&UHDWLQJ�D�7UDQVDFWLRQDO�,QIR&XEH

Select the 7UDQVDFWLRQDO�indicator when creating a new (Basis) InfoCube in the AdministratorWorkbench.

&RQYHUWLQJ�D�6WDQGDUG�,QIR&XEH�LQWR�D�7UDQVDFWLRQDO�,QIR&XEH

,QIR&XEH�&RQYHUVLRQ��5HPRYLQJ�7UDQVDFWLRQ�'DWD

If the standard InfoCube already contains transaction data that you no longer need (for example, testdata from the implementation phase of the system), proceed as follows:

1. In the InfoCube maintenance in the Administrator Workbench choose, from the main menu,,QIR&XEH�→ 'HOHWH�'DWD�&RQWHQW� The transaction data is deleted and the InfoCube is set to“inactive”.

2. Continue with the same procedure as with &UHDWLQJ�D�7UDQVDFWLRQDO�,QIR&XEH.

,QIR&XEH�&RQYHUVLRQ��5HWDLQLQJ�7UDQVDFWLRQ�'DWD

If the standard InfoCube already contains transaction data from the production operation you stillneed, proceed as follows:



Execute the SAP_CONVERT_TO_TRANSACTIONAL ABAP report under the name of thecorresponding InfoCube. You should schedule this report as a background job for InfoCubes withmore than 10,000 data records. This is to avoid a potentially long run-time.

,QWHJUDWLRQ

The following typical scenarios demonstrate the connection between BW and SEM and the use oftransactional InfoCubes:

��6FHQDULR�

Actual data (read-only access) and planned data (read-only and write access) have to be held indifferent InfoCubes. Therefore, use a BasisCube for actual data and a transactional InfoCube forplanned data. Data integration is achieved using an SEM multi-planning area, which contains theareas that are assigned to the InfoCubes. Access to the two different InfoCubes is controlled here bythe characteristic “Planning area”, which is added automatically.

��6FHQDULR�

In this scenario, the planned and actual data have to be together in one InfoCube. This is the case, forexample, with special rolling forecast variants. Here you have to use a transactional InfoCube, sinceboth read-only and write accesses take place. You can no longer load data directly that has alreadyarrived in the InfoCube by means of an upload or import source. To be able to load data nevertheless,you have to make a copy of the transactional InfoCube that is identified as a BasisCube and not astransactional. Data is loaded as usual here and subsequently updated to the transactional InfoCube.



&UHDWLQJ�,QIR&XEHV

3UHUHTXLVLWHV

Ensure that all InfoObjects that you wish to transfer into the InfoCube are actively available. Createany required InfoObjects that do not exist already, and activate them.

If you want to define an InfoCube in the same way as an InfoSource, then thecommunication structure [Seite 278] for the InfoSource should be available in an activeform.

Instead of creating a new InfoCube, you can transfer an InfoCube from SAP’s Business Content [Seite21].

3URFHGXUH

Create an InfoArea, to which the new InfoCube should be assigned.

For this, choose 0RGHOLQJ�→�,QIR3URYLGHU.

Using the context menu for the InfoArea, choose &UHDWH�,QIR&XEH.

Select the type of InfoCube:

− BasicCube [Seite 106]

− Transactional InfoCube [Seite 108]

− Virtual InfoCubes:

• SAP RemoteCube [Seite 331]

• General RemoteCube [Seite 333]

• Virtual InfoCube with Services [Seite 335] (only for special cases)

Choose &UHDWH�

If you want to create a copy of an existing InfoCube, you can enter an InfoCube as a template.

You go to the InfoCube maintenance.

7UDQVIHUULQJ�,QIR2EMHFWV�

The InfoObjects that are to be added to the InfoCube are divided into the categoriescharacteristic, time characteristic and key figure. You have to transfer at least one InfoObjectfrom each category. You select the category from the tabstrip.

Transfer the FKDUDFWHULVWLFV, by selecting the relevant characteristics and assigning them to theInfoCube with the aid of the arrow keys. Compound or referenced characteristics are automaticallytransferred over.

Editing (making revisions to the sequence in the InfoCube) functions are available.

7HPSODWH�6HOHFWLRQ

You can choose different templates. The default setting is always “All InfoObjects”. By settinga template filter, you achieve greater clarity with regard to a particular task (fewer InfoObjectsfor selection).

You can select an InfoSource (still only the InfoObjects for the communication structure of theInfoSource are displayed), an InfoCube, an ODS Object, or an InfoObject catalog as atemplate. A simple way of constructing an InfoCube, that is identical to the communicationstructure of an InfoSource, is by VHWWLQJ�WKH�WHPSODWH��VHOHFWLQJ�DOO�ILHOGV�DQG�WUDQVIHUULQJ�LQWRWKH�,QIR&XEH.

Setting a template can affect either all InfoObject types or just the current one.

'HWDLO�9LHZ�RI�)XQFWLRQV



• A double-click on an InfoObject takes you to the detail display of this InfoObject. You canalso get to the detail display using the pushbutton 'LVSOD\�,QIR2EMHFW�V� (at the bottom ofthe tab page).

• In addition to the text for the InfoObjects, the pushbutton 'HWDLO�9LHZ displays additionalattributes/properties.

$VVLJQLQJ�WKH�&KDUDFWHULVWLFV�WR�'LPHQVLRQV

You get to the definition and assignment screen for dimensions using the pushbutton 'LPHQVLRQV (F8).

Define the required dimensions. You can also read more about dimensions [Seite 113].

If no dimensions exist yet, then you define them using the &UHDWH�function��Enter descriptionsfor all dimensions�

Flag the dimensions in certain cases as line items. You can find further information underLine Item Dimension [Seite 114].

Additionally, you have the option of giving dimensions the indicator +LJK�&DUGLQDOLW\. Thisfunction needs to be switched on if the dimension is larger than ten percent of the fact table.Then you can create B tree indexes instead of Bitmap indexes.

Choose the tabstrip $VVLJQ��select the characteristics to be dimensioned, position the cursor on thedimensions to be assigned to this characteristic, and choose $VVLJQ�(or double click on theassigned dimension).

You can also assign JUDSKLFDOO\�the characteristics that are not assigned (pushbutton). Youcan select and assign the unassigned characteristics on the tree-like display of the dimensionsand characteristics. Note that for graphical assignments, QR�FKDQJHV are permitted to theassignment of a dimension, rather only to an assignment of characteristics that are still free.

The arrow keys can be used for scrolling through the dimensions.

If the InfoCube has been activated once, then individual characteristics or key figures canno longer be deleted. You can only insert additional characteristics or key figures.

Exception: After the function ,QIR&XEH → 'HOHWH�'DWD��the InfoObjects are released again.

Transfer WLPH�FKDUDFWHULVWLFV�

Maintenance of time characteristics follows in the same way as for characteristics. You do notneed to maintain any dimensions, as all time characteristics are assigned with the dimension‘time’ implicit in them.

Transfer the NH\�ILJXUHV

This step is carried out in a similar way to the characteristics. The unit InfoObjects in theInfoCube, which you can display for inspection, result implicitly from the list of transferred keyfigures.

6DYH or $FWLYDWH the InfoCube.

Only an activated InfoCube can be supplied with data and used for reporting.

1H[W�6WHS

Creating Update Rules [Seite 206]

Creating Aggregates [Seite 133]

6HH�DOVR�

SAP Demo Cube [Extern]



'LPHQVLRQ

'HILQLWLRQ

The grouping of classification groups (characteristics) that logically belong together as regardscontent, under one generic term. If the dimension contains a characteristic whose value alreadyuniquely determines the values of all other characteristics from a business-orientated viewpoint, thenthe dimension is named after this characteristic.

The customer dimension could, for example, be made up of the customer number, thecustomer group and the levels of the customer hierarchy.

The sales dimension could contain the characteristics ‘sales person’, ‘sales group’ and‘sales office’.

The time dimension could be given using the characteristics ‘day’ (in the formYYYYMMDD), ‘week’ (in the form YYYY.WW), ‘month’ (in the form YYYY.MM), ‘year’ (inthe form YYYY) and ‘period’ (in the form YYYY.PPP).

8VH

'HILQLWLRQ�LQ�WKH�6WDU�6FKHPD

When defining an InfoCube, characteristics for dimensions are grouped together to store them in atable of the star schema (dimension table). The afore-mentioned business-orientated grouping can bethe basis for this. With the aid of a simple foreign key dependency, dimensions are linked to one of thekey fields of the fact table.

6WUXFWXUH

From a technical viewpoint, several characteristic values are mapped to an abstract dimension key(DIM ID), to which the values in the fact table refer. The characteristics chosen for an InfoCube aredivided up among InfoCube-specific dimensions when creating the InfoCube.



/LQH�,WHP�'LPHQVLRQ

8VH

A line item is an InfoObject, which has a small number of facts listed on itscharacteristic values in the fact table of the InfoCube. The dimension table of a lineitem InfoObject would become almost as large as the fact table. By indicating adimension as a line item, you can prevent performance problems that would comeabout from the size of the dimension table. The document number is a goodexample.

We do recommend that you use ODS objects, where possible, instead of InfoCubesfor line items. See Creating ODS Objects [Seite 167].

$FWLYLWLHV

When creating the dimensions in the InfoCube maintenance, flag the relevantdimension as a /LQH�,WHP. You can assign this dimension to exactly one InfoObject.No database table is created when you activate the InfoCube. Instead, a field iswritten for this dimension to the fact table. The field is a direct link to the SID table ofthe InfoObject. The data is requested directly from the InfoObject.

From the Star Schema diagram:

,QIR&XEH�→�'LPHQVLRQ�→�,QIR2EMHFW

we now have (for this line item InfoObject):

,QIR&XEH�→�,QIR2EMHFW



$GGLWLRQDO�)XQFWLRQV�LQ�,QIR&XEH�0DLQWHQDQFH

,QVHUWLQJ�'RFXPHQWV

Using this function you can add documents to InfoCubes in different formats (for example, MS Word,PowerPoint, PDF, BMP, HTML).

6HH�DOVR� Adding Documents to BW Objects [Extern]

7UHH�'LVSOD\

Use this function to display all the settings for an InfoCube that have been made in the InfoCubemaintenance in a clear tree structure. The InfoCube is output in a KLHUDUFKLFDO�WUHH�GLVSOD\�with itsdimensions and InfoObjects.

9HUVLRQ�&RPSDULVRQ

Use this function to compare the following InfoCube versions:

• the active and modified versions of an InfoCube

• the active and content versions of an InfoCube

• the modified and content versions of an InfoCube

This enables you to compare all the settings made in the tabstrips of the InfoCube maintenance.


You can choose and transport InfoCubes. All those BW objects that are needed to ensure a consistentstatus in the target system are collected automatically.

:KHUH�XVHG�OLVW

You can determine which other objects in BW can use a specific InfoCube.

You can also determine the consequences of making a particular change to an InfoCube and whetherthe change is permitted at the moment.

%XVLQHVV�&RQWHQW

Use this function to see how the different BW objects relate to one another.

For example:

• Structural dependencies

• Connections between BW objects, such as the data flow from a source system across anInfoCube to a query.

The dependencies can be displayed and exported in HTML format.

1DYLJDWLRQ�$WWULEXWHV

A navigation attribute [Seite 63] that has been created in the InfoObject maintenance for acharacteristic can be switched on in the InfoCube. The default is initially set to “off” so as not toimplicitly include more attributes than are necessary in the cube.

Note that you can subsequently create or activate navigation attributes in the InfoCube at any time.However, once you have activated an attribute, you are no longer able to deactivate it (because of anyaggregates or selection variables that may have been defined).

8QLWV

By clicking a pushbutton on the key figures screen, you can display the units contained in theInfoCube. Units are not defined, but result from data from the transferred key figures.

3URSHUWLHV�6SHFLILF�WR�WKH�,QIR&XEH

You can assign InfoObjects specific properties that are valid only in the InfoCube you are currentlyprocessing.



An example with characteristics is the selection of a particular fiscal year variant for thefield 0FISCVARNT.

An example with key figures is the setting-up of a particular display (for example “in 1000”)for a certain key figure.

The corresponding function is found in the menu under ([WUDV.

,QIR�IXQFWLRQV

Various information functions are available referring to the status of the InfoCube:

• The log display for the save, activation and deletion runs of the InfoCube,

• The InfoCube status in the ABAP/4 Dictionary and on the database,

• A function for the raw display (Browser) of data saved in the InfoCube [Seite 117]

• The current system settings,

• The permitted limits in the InfoCube,

• The object catalog entry.

• Analysis of the data consistency of the InfoCube [Seite 118]

6SHFLDO�)XQFWLRQV

1DYLJDWLRQ�IRU�,QIR2EMHFW�PDLQWHQDQFH� Pushbuttons allow you to FUHDWH��GLVSOD\ and FKDQJHindividual InfoObjects. Note that changes to InfoObjects apply to all the places where the InfoObject isused (that means also in other InfoCubes)!

8QGR�FKDQJH��This function resets the InfoCube to the active version, meaning that the changes thatwere made the last time data was saved, are undone.

'LVSOD\�DFWLYH��6$3�YHUVLRQ� When you are editing the InfoCube, you can display its active version,or the version delivered by SAP (if it exists).

3HUIRUPDQFH�6HWWLQJV�

• Database Memory Parameters [Seite 120]

• Partitioning [Seite 121]

• Non-cumulative Value Parameters [Seite 119]

$VVLJQLQJ�D�)XQFWLRQ�0RGXOH

You load data from external sources by assigning a function module to an InfoCube. The functionmodule is called when the data is loaded. It supplies the data temporarily. The function can be calledfrom the context menu with $GGLWLRQDO�&KDUDFWHULVWLFV.



&KHFNLQJ�WKH�'DWD�/RDGHG�LQ�WKH�%DVLF&XEH

3UHUHTXLVLWHV

You have loaded your data into the InfoCube, and checked the data request in the Monitor [Seite 378].

3URFHGXUH

7UDQVDFWLRQ�'DWD�

1. Choose�,QIR&XEH�0DLQWHQDQFH�→ (GLW�→ ,QIR&XEH�'DWD�'LVSOD\��and specify whether you want toinclude the SIDs in the display as well.

2. Choose the characteristic values for which the output list is to be selected.

3. Choose ILHOG�VHOHFWLRQ�IRU�RXWSXW, and select the characteristics and key figures that are to beselected in the output list.

4. Choose ([HFXWH.

5. In the following window, choose ([HFXWH again.

See also: InfoCube Content [Seite 405]

0DVWHU�'DWD�

1. Choose ,QIR6RXUFH 7UHH�→ <RXU�,QIR$UHD → <RXU�0DVWHU�'DWD ,QIR6RXUFH → &RQWH[W�0HQX �ULJKW

PRXVH�EXWWRQ� → &KDQJH�$WWULEXWHV�

2. Select the 0DVWHU�'DWD�7H[WV folder.

3. Double click on the technical name of the master data table.

4. In the following window, choose 8WLOLWLHV�→�7DEOH�&RQWHQWV�→�'LVSOD\.



&KHFNLQJ�WKH�'DWD�&RQVLVWHQF\�RI�DQ�,QIR&XEH

8VH

Choose ,QIR&XEH�0DLQWHQDQFH → (GLW → $QDO\]H�,QIR&XEH and check the data consistency of anInfoCube according to various technical aspects.

3UHUHTXLVLWHV

To do this check, you need a detailed, technical understanding of the data structure in BW, preferably,you are an administrator.

You have created an InfoCube and would like to use it in reporting.

)XQFWLRQV

The screen provides you with a series of check options that are broken down in the followingcategories:

• Information about the InfoCube

• InfoCube definition

• InfoCube fact table, dimensions, SID table, master data table

• Tests with the entry of additional parameters

After executing one or several checks, you receive a status message by way of traffic light symbols(red, yellow, green).

)XQFWLRQV

([HFXWH� Using this function, you can start one or more checks that were previously chosen from thelist.

([HFXWH�LQ�WKH�%DFNJURXQG� Using this function, you can start one or several checks that werepreviously chosen from the list, and generate a print list. This is a particular advantage with largerInfoCubes especially, where a check can be very time consuming, and direct execution would result ina time-out.

5HVXOWV� Using this function, you can display the results of your checks.

• gray: Comment

• yellow: Warning

• red: Error

5HSDLU� If the system offers it, you can use this function to automatically repair errors that have arisen.

,QIRUPDWLRQ� Using this function, you can display additional information for a check that you previouslychose, by clicking with the mouse.



1RQ�&XPXODWLYH�9DOXH�3DUDPHWHU�0DLQWHQDQFH

8VH

The non-cumulative parameter maintenance is activated as soon as at least one non-cumulative valueexists in the InfoCube. In this case, you have to choose a �WLPH� UHIHUHQFH�FKDUDFWHULVWLF�IRU�WKHQRQ�FXPXODWLYH�YDOXHV of the InfoCube, which sets the granularity (the degree of precision) in whichthe non-cumulative values are managed. This (time) reference characteristic applies for all the non-cumulative values of the InfoCube and must be the “smallest” of the time characteristics present in theInfoCube.

The InfoCube contains warehouse stock key figures as well as the time characteristics‘calendar month’ and ‘calendar year’. In this case, define the InfoObject 0CALMONTH(calendar month) as a reference characteristic for the time-based aggregation.

For the non-cumulative values contained in the InfoCube, a YDOLGLW\�WDEOH is created, inwhich the time interval is stored, for which the non-cumulative values are valid. Apart fromthe reference characteristic for time-based aggregation, which is always implicitly insertedin the validity table, this table can contain additional characteristics. See also: ValidityPeriod [Seite 78].

Such characteristics are, for example:

− a 3ODQ�$FWXDO indicator, in case there are different time references for plan and actualvalues (plan values up until year end, actual values up until the current date).

− the characteristic 3ODQW, in case the non-cumulative key figure for each plant isreported at different times, for example from different OLTP (source) systems.

$FWLYLWLHV

Select all additional characteristics that are to be included in the validity table, by selecting. In theaforementioned example, the characteristics 3ODQ�$FWXDO and 3ODQW must be selected. The systemautomatically generates the validity table corresponding to the definition that was made. This table isupdated automatically when data is loaded.

6HH�DOVR�

Non-Cumulatives [Seite 73]



'%�0HPRU\�3DUDPHWHUV

8VH

Data type and size category of fact and dimension tables are defined as default values.

To increase the InfoCube performance you can enter other data types for the fact table anddimensions where necessary.

This means you can fill tables in other table spaces of the database, so you can access tables faster.



3DUWLWLRQLQJ

8VH

By using partitioning you can split up the whole dataset for an InfoCube into several, smaller,physically independent and redundancy-free units. Thanks to this separation, performance isincreased when reporting, or also when deleting data from the InfoCube.

Only certain database providers support this function (for example, ORACLE, INFORMIX).If you use a database that does not support this function, then this function is not providedby the BW system.

3UHUHTXLVLWHV

You can only partition a dataset using one of the two partitioning criteria ‘calendar month’(0CALMONTH) or ‘fiscal year/period (0FISCPER). At least one of the two InfoObjects must becontained in the InfoCube.

If you want to partition an InfoCube using the fiscal year/period (0FISCPER) characteristic,you have to set the fiscal year variant characteristic to constant.

Partitioning InfoCubes Using the Characteristic 0FISCPER [Seite 123]

)XQFWLRQV

When activating the InfoCube, the fact table is created on the database with one of the number ofpartitions corresponding to the value range. You can determine the value range yourself.

You choose the partitioning criterion 0CALMONTH and determine the value range

from 01.1998

to 12.2003

6 years * 12 months + 2 = 74 partitions are created (2 partitions for values that lay outsideof the range, meaning < 01.1998 or >12.2003).

You can also determine how many partitions are created as a maximum on the database for the facttable of the InfoCube.

You choose the partitioning criterion 0CALMONTH and determine the value range

from 01.1998

to 12.2003

You choose 30 as the maximum number of partitions.

Resulting from the value range: 6 years * 12 calendar months + 2 marginal partitions (upto 01.1998, from 12.2003) = 74 single values.

The system groups three months at a time together in a partition (meaning that a partitioncorresponds to exactly one quarter); In this way, 6 years * 4 partitions/year + 2 marginalpartitions = 26 partitions are created on the database.

$FWLYLWLHV

In the InfoCube maintenance choose ([WUDV�Å 3DUWLWLRQLQJ, and specify the value range. Wherenecessary, limit the maximum number of partitions. Note that the value range can only be changed ifthere is no data contained in the InfoCube.



3DUWLWLRQLQJ�,QIR&XEHV�XVLQJ�WKH�&KDUDFWHULVWLF��),6&3(5

8VH

You can partition InfoCubes using two characteristics – calendar month (0CALMONTH) and fiscalyear/period (0FISCPER). The special feature of the fiscal year/period characteristic (0FISCPER) beingcompounded with the fiscal year variant (0FISCVARNT) means that you have to use a specialprocedure when you partition an InfoCube using 0FISCPER.

3UHUHTXLVLWHV

When partitioning using 0FISCPER values, values are calculated within the partitioning interval thatyou specified in the InfoCube maintenance. To do this, the value for 0FISCVARNT must be known atthe time of partitioning, that is, it must be set to FRQVWDQW.

3URFHGXUH

1. Set the value for the 0FISCVARNT characteristic to constant. Carry out the following steps:

a. Call the InfoSet maintenance from $GPLQLVWUDWRU�:RUNEHQFK��0RGHOLQJ�by double clicking onthe InfoCube that you want to partition. You reach the (GLW�,QIR&XEH��&KDUDFWHULVWLFV�screen.

b. Choose the 7LPH�&KDUDFWHULVWLFV tabstrip.

c. Choose ([WUDV��!�,&�6SHFLILF�3URSHUWLHV�RI�,QIR2EMHFW��InfoObject Properties You get to the6WUXFWXUH�6SHFLILF�3URSHUWLHV dialog box.

d. Specify a constant for the characteristic 0FISCVARNT. Choose &RQWLQXH.

2. Choose ([WUDV��!�3DUWLWLRQLQJ� You get to the 'HWHUPLQH�3DUWLWLRQLQJ�&RQGLWLRQV dialog box. Youcan now select the 0FISCPER characteristic under 6OFWQ. Choose &RQWLQXH.

3. You get to the 9DOXH�5DQJH��3DUWLWLRQLQJ�&RQGLWLRQ��dialog box. Enter the required data. For moreinformation, see Partitioning [Seite 121]



'HOHWLQJ�WKH�,QIR&XEH�DQG�,QIR&XEH�&RQWHQW

'HOHWLQJ�WKH�,QIR&XEH

The whole InfoCube in its definition with all the data is deleted using this function. Dependent objectssuch as queries and update rules can be deleted with this if desired.

Note that this function results in the irrevocable loss of all data and definitions for the InfoCube.

InfoObjects that have been transferred to the InfoCube cannot be removed from theInfoCube once it has been activated. The only exception here is the state of an InfoCubedirectly after the function “Delete InfoCube Data” is executed, since all data base tablesare in their initial state following this function, that is, they do not contain any data.

This same is true when assigning characteristics to dimensions. These cannot be reversed againeither.

To delete the InfoCube select ,QIR3URYLGHU�7UHH → ,QIR&XEH��→�ULJKW�PRXVH�NH\��→�'HOHWH�,QIR&XEH�

'HOHWH�,QIR&XEH�&RQWHQW

By using this function, all the data that is contained in the InfoCube is deleted. You also have theoption here of deleting dependent objects such as queries and update rules.

To delete the InfoCube contents choose ,QIR3URYLGHU�7UHH → ,QIR&XEH��→�ULJKW�PRXVH�NH\��→�'HOHWH'DWD.



2YHUYLHZ�RI�/RDGDEOH�,QIR6RXUFHV�IRU�DQ�,QIR&XEH

8VDJH

In the InfoCube tree of the Administrator Workbench Modeling, you can display all InfoSources for anInfoCube to which it is possible to load data.

$FWLYLWLHV

1. Select the InfoCube and choose ,QIR6RXUFHV�2YHUYLHZ using the context menu (right mousebutton).

Information on the InfoSource as well as on the last loading process is displayed for you.

2. Using the status symbol of the last loading process you get to the Monitor and can check this datarequest.

3. Using the pushbutton ([SDQG you get to the InfoSource tree. From here you can schedule a datarequest for the InfoCube.



$JJUHJDWHV

'HILQLWLRQ

An aggregate is a materialized, aggregated view of the data in an InfoCube. In an aggregate, thedataset of an InfoCube is saved redundantly and persistently in a consolidated form into the database.

8VH

Aggregates make it possible to access InfoCube data quickly in Reporting. Aggregates serve, in asimilar way to database indexes, to improve performance.

We recommend that you create aggregates, especially in the following cases:

• The execution and navigation of query data leads to delays with a group of queries.

• You want to speed up the execution and navigation of a specific query.

• You often use attributes in queries.

• You want to speed up reporting with characteristic hierarchies by aggregating specific hierarchylevels.

$JJUHJDWH�6FUHHQ�,QIRUPDWLRQ

An aggregate is made up of characteristics and navigation attributes belonging to an InfoCube. Youcan group the data according to different aggregation levels [Seite 127]. In doing so, you can alsostore values for hierarchy levels belonging to an external hierarchy. Both time-dependent attributesand time-dependent hierarchies can be used in aggregates. Characteristics that are not used in theaggregate are brought together.

If you have created aggregates for an InfoCube and entered data for them, the OLAP processorautomatically accesses these aggregates. When navigating, the different results are consistent. Theaggregate is transparent for the end user.

New data is loaded at a defined time using logical data packages (requests) in an aggregate. After thistransaction, the new data is available for rolling up in reporting.

6HH�DOVR�

Creating InfoCubes [Seite 110]

Editing Aggregates [Seite 133]

Activating and Filling Aggregates [Seite 141]

Rolling up Data into an Aggregate [Seite 144]

Efficiently Loading Data into Aggregates [Seite 146]

Further Editing Functions for Aggregates [Seite 147]

Automatically Selecting and Optimizing Aggregates [Seite 149]

Adjusting Changes to Hierarchies and Attributes [Seite 399]

“3HUIRUPDQFH�7XQLQJ�IRU�4XHULHV�ZLWK�%:�$JJUHJDWHV” from the performance page for SAPBusiness Information Warehouse in SAP Service Market place

You can find additional information about MOLAP aggregates in MOLAP Store [Seite 153] .



$JJUHJDWLRQ�/HYHOV

'HILQLWLRQ

An aggregation level indicates the degree of detail to which the data of the underlying InfoCube iscompressed.

8VDJH

An aggregation level must be assigned to each component of an aggregate (characteristics andnavigation attributes). You can choose one of the following aggregation levels:

• All characteristic values ("*"): The data is grouped by all the values of the characteristic ornavigation attribute.

• Hierarchy level (“H”): The data is grouped by the hierarchy level node.

• Fixed value (‘F’): The data is filled according to a single value.

([DPSOH

Aggregation Level "All Characteristic Values" ('*') [Seite 128]

Aggregation Level "Hierarchy Level" ('H') [Seite 130]

Aggregation Level "Fixed Value" (‘F’) [Seite 132]



$JJUHJDWLRQ�/HYHO��$OO�&KDUDFWHULVWLF�9DOXHV�� The following examples assume a simplified InfoCube (sales figures), containing the characteristics’COUNTRY’ and ’CUSTOMER’ and the key figure ’SALES’.

([DPSOH��,QIR&XEH

&28175< &86720(5 6$/(6

USA Buggy Soft 10

Germany Ocean Networks 15

USA Funny Duds 5

Austria Ocean Networks 10

Austria Thor Industries 10

Germany Funny Duds 20

USA Buggy Soft 25

([DPSOH��$JJUHJDWH�&RXQWU\�

• Characteristic ’COUNTRY’ is used for grouping.

• Characteristic ’CUSTOMER’ is used for compressing.

&28175< 6$/(6

USA 40

Germany 35

Austria 20

The data for key figure ’SALES’ is listed for the sum of the sales for each country and not for individualcustomers.

The aggregate can be used

• In a query that determines the sales for each country or the total sales

• For evaluations using a navigation attribute for characteristic ’COUNTRY’ or using a hierarchy onthe countries

The aggregate cannot be used if you want to expand or select in a query using characteristic’CUSTOMER’ because it does not contain any information about the customers.

([DPSOH��$JJUHJDWH�,QGXVWU\�

In the second example for aggregation level ’All characteristic values’, the LQGXVWU\ is needed as aQDYLJDWLRQ�DWWULEXWH. The following master data table is used here:

0DVWHU�'DWD�7DEOH��&XVWRPHU

&86720(5 ,QGXVWU\

Buggy Soft Technology

Ocean Networks Technology

Funny Duds Consumption

Thor Industries Chemicals

• Navigation attribute ’INDUSTRY’ is used for grouping.

• Characteristic ’CUSTOMER’ is used for compressing.

,QGXVWU\�DJJUHJDWH



,1'8675< 6$/(6

Technology 60

Consumption 25

Chemicals 10

The aggregate can be used

• In a query that determines the sales for each industry or the total sales

• For evaluations by node values if there is a hierarchy for the industry

Detailed information cannot be obtained about characteristic ’CUSTOMER’ with the exception of theindustry to which the customer is assigned.

([DPSOH��$JJUHJDWH�6DOHV�3HUVRQ�

In the third example for aggregation level ’All characteristic values’, the WLPH�GHSHQGHQW�QDYLJDWLRQDWWULEXWH 6DOHV�SHUVRQ is needed. The following table is used here:

6DOHV�3HUVRQ�7DEOH

&28175< )520 72 6$/(6�3(5621

USA 01.01.2000 31.12.2000 Smith

USA 01.01.2000 31.12.2001 Miller

Germany 01.01.2000 31.03.2001 Meyer

Germany 01.04.2000 31.12.2001 Huber

Austria 01.01.2000 31.12.2001 Huber

• Navigation attribute ’SALES PERSON’ is used for grouping.

• Characteristic ’COUNTRY’ is used for compressing.

• Key Date: Sept. 01, 2001

6$/(6�3(5621 6$/(6

Miller 40

Huber 55

The aggregate can be used in a query that has the same key date as the aggregate.



$JJUHJDWLRQ�/HYHO��+LHUDUFK\�/HYHO��+��Assume

• the simplified InfoCube (sales figures) containing characteristics ‘COUNTRY’ and ‘CUSTOMER’as well as key figure ‘SALES' (see Aggregation Level "All Characteristic Values" (‘*’) [Seite 128]),

• The following external hierarchy for the countries:

World

Europe America

Austria USA

Level 1

Level 2

Level 3

External Hierarchy by Country

Germany

([DPSOH��$JJUHJDWH�&RXQWU\�+�/HYHO��

• Characteristic 'COUNTRY' is used to compress on level 2 of the country hierarchy (Europe,America).

• The characteristic ‘CUSTOMER’ is not contained in the aggregate.

+LHUDUFK\�OHYHO��

&28175< 6$/(6

America 40

Europe 55

This aggregate can be used in queries

• That need sales for a node of the hierarchy on level 2 or higher, including such queries that havethe country hierarchy as presentation hierarchy in the drill-down and are not expanded deeperthan level 2.

• That determine the total sum of the sales if

− The hierarchy does not have any multiple leaves, i.e. each variant of a characteristic onlyoccurs once in the hierarchy,

− Node "Remaining" is not suppressed

The aggregate cannot be used if the third hierarchy level (Austria, Germany, USA) is needed in aquery.



$JJUHJDWLRQ�/HYHO��)L[HG�9DOXH��µ)¶�The simplified InfoCube (sales figures) is given containing characteristics ‘COUNTRY’ and‘CUSTOMER’ as well as key figure ‘SALES' (see Aggregation Level "All Characteristic Values" (‘*’)[Seite 128]),

([DPSOH��$JJUHJDWH�&RXQWU\�)� �'(��&XVWRPHU�

The aggregate only contains data for characteristic value 'Germany'.

)L[HG�9DOXH��*HUPDQ\

&28175< &86720(5 6$/(6

Germany Ocean Networks 15

Germany Funny Duds 20

The aggregate can only be used in queries having the same filter value.

The aggregate cannot be used if other countries are needed in a query.

We recommend that you use filter values for aggregates if only one variant is needed for Reporting, forexample

• The plan/actual indicator

• The current fiscal year

• Certain versions



(GLWLQJ�$JJUHJDWHV

3UHUHTXLVLWHV

The InfoCube for which you want to create an aggregate has been saved and is active.

3URFHGXUH

How to create or change an aggregate for an InfoCube is described below.

1. You are in the 0RGHOLQJ function area of the Administrator Workbench. In the navigation windowchoose ,QIR3URYLGHU.

2. In the InfoProvider tree navigate to the InfoCube whose queries you want to optimize.

3. In the context menu of the InfoCube select 0DLQWDLQ�$JJUHJDWHV. This will bring you screen0DLQWDLQ�$JJUHJDWHV�

If an aggregate was already created for the selected InfoCube, you can also go to themaintenance screen by double-clicking on .

If you create the first aggregate for an InfoCube, you will first go to the 3URSRVDOV�IRU$JJUHJDWHV dialog box. You can define whether the system should propose aggregates orwhether you want to create them manually.

For more information see Creating the First Aggregate for an InfoCube [Seite 137].

4. The left side of the screen shows the dimensions, characteristics and navigation attributes of theselected InfoCube in a tree structure as 6HOHFWLRQ�2SWLRQV�IRU�$JJUHJDWHV.

Select one or more objects to be copied to the aggregate.

Define the JUDQXODULW\ you need for the data in the aggregate. Add all the characteristicsderived from these characteristics.

For example if you define an aggregate for the month, you should also include the TXDUWHUand \HDU�in the aggregate.

This enhancement does not increase the data set, but permits

• a year aggregate to be built from this aggregate,

• those who need the annual values can also use queries of this aggregate.

You can only include a characteristic and one of its attributes in an aggregate in expertmode (([WUDV -> 6ZLWFK�H[SHUW�PRGH�RQ�RII). Such an aggregate has the same granularityand size as an aggregate that was only built with the characteristic, but is affected by thehierarchy/attribute change run. Compared with the aggregate for the characteristic inwhich the attribute information is defined by a join with the master data table, theaggregate for the characteristic DQG the attribute only saves the database join.

We therefore recommend that you HLWKHU build an aggregate using with the characteristicRU you build a much smaller aggregate using the attribute.

5. You have different options for creating an aggregate:

• Pull the selected object(s) to the column $JJUHJDWHV on the right side of the screen usingDrag-and-drop.

• Select &UHDWH�QHZ�DJJUHJDWH.



The (QWHU�'HVFULSWLRQ�IRU�$JJUHJDWH dialog box appears.

6. Enter:

6KRUW�GHVFULSWLRQ

/RQJ�'HVFULSWLRQ

To change the text at a later time select &KDQJH�GHVFULSWLRQ�WH[W�from the context menu ofthe aggregate.

7. Choose 1H[W. You get to the 0DLQWDLQ�$JJUHJDWHV screen.

The system displays the aggregate at the upper right of the screen. The log is displayed in thelower part of the screen.

For more information see Displaying an Aggregate and its Components [Seite 138].

8. If an aggregate contains a time-dependent component, you must assign the aggregate a key date.

When you fill the aggregate, the key date behaves like the key date of a query: The time-dependent attributes and hierarchies are evaluated on this key date. For this reasonaggregates with a time-dependent component can only be used in a query if the key dateof the query is the same as the key date of the aggregate.

In the 6HOHFW�9DULDEOH�RU�)L[HG�'DWH dialog box select the following as key date:

• a variable that is also used in queries for the key date and can be automatically calculatedin the 6$3�([LW or &XVWRPHU�([LW processing types (see Using Variables [Extern]),

0CWD Current workday

0DAT Current calendar day

0P_KEYDT Key date of due date

0P_KEYD2 Key date of posting (from key date of due date)

0P_KEYD3 Key date of clearing (from key date of due date)

0P_KEYD4 Key date of posting (posting date)

0P_KEYD5 Key date of clearing (from key date of posting)

Aggregates with a variable key date must be updated regularly. This process must beincluded in a process chain [Seite 424] ()XUWKHU�%:�SURFHVVHV -> $GMXVW�WLPH�GHSHQGHQWDJJUHJDWHV).

• A certain calendar day

To enter a calendar day, select object CALENDAR in the 6HOHFW�9DULDEOH�RU�)L[HG�'DWH

dialog box (<Calendar>). Choose 7UDQVIHU�VHOHFWLRQV� This takes you to the &DOHQGDUdialog box. You can copy this date to the aggregate definition by double-clicking.

The system displays the technical name of the variable you chose or of the fixed calendardate in the aggregate tree under 3URSHUWLHV for node 9DULDEOHV�IRU�NH\�GDWH.

Once the aggregate has been activated and filled, the system copies the key date computedfrom the variable when the aggregate should be filled into the line .H\�GDWH.



9. You can change the structure of the aggregate by adding further components or deleting existingones. You can also change the key date.

,QVHUWLQJ�&RPSRQHQWV�LQWR�WKH�$JJUHJDWH

i. Select one or more objects in 6HOHFWLRQ�2SWLRQV�IRU�$JJUHJDWHV.

ii. Pull them to the aggregate to be changed at the right of the screen with drag-and-drop.

iii. If necessary, change the aggregation level [Seite 127] by using the context menu:

All characteristic values [Seite 128]

Hierarchy level [Seite 130]

Fixed value [Seite 132]

Aggregates containing fewer than 14 components are stored on the database in optimizedform (see Efficiently Loading Data into Aggregates [Seite 146]).

The characteristics that are defined in the InfoCube are also included in the aggregateand thus increase the number of components even though they are not visible on thesurface.

'HOHWLQJ�&RPSRQHQWV�IURP�WKH�$JJUHJDWH

i. In the aggregate tree navigate to the characteristic(s) or navigation attributes you want todelete.

ii. Select these components.

iii. To delete the components from the aggregate you can:

− Select 5HPRYH�FRPSRQHQWV from the context menu.

− Pull the components to the left part of the screen with drag-and-drop.

To delete a dimension from an aggregate, you have to delete all the characteristics andnavigation attributes of this dimension.

&KDQJLQJ�WKH�.H\�'DWH

i. In the aggregate tree under 3URSHUWLHV select node 9DULDEOH�IRU�NH\�GDWH andchoose &KDQJH from the context menu. You go to dialog box 6HOHFW�9DULDEOH�RU�)L[HG'DWH.

ii. Select and copy the required variable or calendar date.

The key date computed from a changed variable is only copied to line .H\�GDWH whenthe $GMXVW�WLPH�GHSHQGHQW�DJJUHJDWHV process has been executed.

10. To check the aggregate definition for inconsistencies choose &KHFN�GHILQLWLRQ.

11. Save the new or changed aggregate.

5HVXOW

You can activate the new or changed aggregate and fill it with data. It is then available for reporting.

6HH�DOVR�

Activating and Filling Aggregates [Seite 141]

Rolling Data up into an Aggregate [Seite 144]

Automatically Selecting and Optimizing Aggregates [Seite 149]




&UHDWLQJ�WKH�)LUVW�$JJUHJDWH�IRU�DQ�,QIR&XEH

3UHUHTXLVLWHV

The InfoCube for which you want to create an aggregate has been saved and is active. There are notyet any aggregates for the selected InfoCube.

Note the following requirements if you want to have the system propose aggregates:

• You must have created at least one query for the selected InfoCube or for a MultiCube that usesthe InfoCube. The necessary aggregates can be proposed when you start the queries andnavigate in them.

• Make sure that you have switched on BW statistics collection for the selected InfoCube in theOLAP area. For more information see Activating Data Transfers for BW Statistics [Extern].

3URFHGXUH

1. In the context menu of the InfoCube select 0DLQWDLQ�$JJUHJDWHV. The 3URSRVDOV�IRU�$JJUHJDWHVdialog box appears.

2. Specify if you want the system to propose aggregates.

)XQFWLRQ :KDW�\RX�QHHG�WR�NQRZ

Create proposals The system proposes suitable aggregates.

The 6SHFLI\�6WDWLVWLFV�'DWD�(YDOXDWLRQ�dialog boxappears. Type in the data that the system asksyou for. Choose &RQWLQXH.

This will bring you to screen 0DLQWDLQLQJ$JJUHJDWHV� The system displays the proposedaggregates in the right area of the $JJUHJDWHVscreen.

You can change these proposals byusing Drag & Drop to add or removedimensions, characteristics orattributes.

Create yourself This will bring you to screen 0DLQWDLQLQJ$JJUHJDWHV�

For more information see Editing Aggregates[Seite 133].

3. To check the aggregate definition for inconsistencies choose &KHFN�GHILQLWLRQ.

4. Save the aggregates.

5HVXOW

You can activate the aggregates you just created and fill them with data.



'LVSOD\LQJ�$JJUHJDWHV�DQG�WKHLU�&RPSRQHQWV

'HILQLWLRQ

The screen area of the $JJUHJDWH�0DLQWHQDQFH screen in which aggregates and their components aredisplayed in a logical tree.

8VH

You use this screen area to:

• Define aggregates

• Obtain information about the status of the individual aggregates

You can and should define a number of aggregates for an InfoCube. However, make sure thattheir usefulness balances out their disadvantages:

− Usefulness: Aggregates improve the performance of queries.

− Disadvantages: Aggregates increase the load time

• through data packages uploads;

• through the hierarchy/attribute change run after loading master data;

• through adjusting time-dependent aggregates.

To optimize an InfoCube, you should repeatedly check:

− Whether further aggregates are missing: Create new aggregates.

− Whether existing aggregates are no longer being used: Delete unnecessary aggregates.

The display of the aggregates in the $JJUHJDWH�0DLQWHQDQFH�screen helps you to evaluate theaggregates.

6WUXFWXUH

&ROXPQ ,QIRUPDWLRQ

Aggregates Aggregates with all transferred components in a treedisplay

Technical name

Save Marks new or changed aggregates

Proposed action The system proposes actions if necessary

Once the system has proposed a new aggregate, itrecommends that you activate this aggregate. This ismarked by a in this column.

Status Created

Changed (The modified aggregate definition is nolonger the same as the active aggregate definition)

Saved and active

Filled/switched off Not filled with data

Filled with data

Refers to individual components in the aggregate:

• Aggregation Levels [Seite 127]

By default the system aggregates by value of theselected objects:



• ’*’ All characteristic values

• ’H’ Hierarchy level

• ’F’ Fixed value

You can change this setting from the context menuof the displayed aggregation level.

• Hierarchy If necessary, name of the selected hierarchy

• Hierarchy level If necessary, selected level of the hierarchy

• Fixed value If necessary, selected fixed value

Evaluation Representation in a bar chart:

• The larger the number of minus signs, the worseis the evaluation of the aggregate:

"-----" means: The aggregate can possiblybe deleted.

• The larger the number of plus signs, the better isthe evaluation of the aggregate:

"+++++" means: The aggregate could makea lot of sense.

The evaluation is based on a number of criteria. Atthe moment the following is used in the evaluation:

• The compression of the data compared with theInfoCube: How much smaller is the aggregatecompared to the InfoCube?

• When was the aggregate last used? (see underODVW�XVHG).

Records Number of records in the filled aggregate.

This information tells you something about the sizeof the aggregate.

Records compressed (mean value) Number of records read on an average from thesource in order to create a record in the aggregate.

Given an aggregate with three records.For example if 10 records were read forthe first record in the aggregate, 15records were read for the second recordand 20 records for the third record, theaggregate has a mean of ��"recordscompressed".

This information tells you something about thequality of the aggregate.

• The larger the value, the greater is thecompression and the better the quality ofaggregate.

Since an aggregate should be 10 timessmaller than its source, the numbershould be larger than 10.

• If the value is "1", the aggregate is a copy of the



InfoCube. In this case, consider deleting theaggregate.

Use Number of uses (in queries).

How often was the aggregate used for Reporting

Last usage Date.

When was the aggregate last used for Reporting?

If an aggregate has not been used for a long time,deactivate or delete it.

Note that certain aggregates cannot beused at certain times (for exampleduring vacation).

Do not delete basic aggregates that youcreated to speed up thehierarchy/attribute change run.

Last roll-up Date.

When was the last time that data was entered for theaggregate?

Last roll-up by User name of the person who scheduled the roll-up.

Last changed on Date.

When was the aggregate definition last changed?

Last changed by User name of the person who made the last change.

,QWHJUDWLRQ

The log display is shown in the lower part of the screen when the aggregate is defined and after fillingit with data.

6WDWXV�2YHUYLHZ�RI�WKH�$JJUHJDWHV

You can find a status display for all the aggregates in the BW system in the functional area 0RQLWRULQJof the Administrator Workbench:

In the navigation window choose 6WDWXV�RYHUYLHZ��The screen area 6WDWXV�RI�WKH�$JJUHJDWHV�listsall the InfoCubes and all the existing aggregates under each InfoCube.

The structure of this screen area corresponds to the $JJUHJDWH screen area of the $JJUHJDWH0DLQWHQDQFH screen. Only the status and not the components of the aggregate are displayed.

By double-clicking on of a certain aggregate you go to the $JJUHJDWH�'LVSOD\�screen. Theaggregate is displayed here together with its components.



$FWLYDWLQJ�DQG�)LOOLQJ�$JJUHJDWHV

8VH

To use an aggregate for an InfoCube when executing a query, you must first activate it and then fill[Extern] it with data.

3UHUHTXLVLWHV

You created or changed an aggregate.

3URFHGXUH

1. Select the aggregate that you want to activate and fill.

2. Choose $FWLYDWH�DQG�)LOO. The system creates an active version of the aggregate.

6\VWHP�$FWLYLW\ 5HVXOW

The system creates the tables required by theaggregate definition on the database. Aggregatesare created according to the same schema asInfoCubes.

• An aggregate contains two fact tables and anumber of dimension tables.

• The table names are derived from thetechnical names of the aggregates.

If the aggregate was activated successfully, thestatus display in the 6WDWXV column changes from

for a newly create aggregate or for achanged aggregate to .

3. Once the aggregate was activated, you must trigger the action to fill the aggregate with data. The6XEVHTXHQWO\�$JJUHJDWH�,QIR&XEH�$JJUHJDWHV dialog box appears.

4. An active aggregate is selected and marked in column $FWLYH�,QDFWLYH�with .

If you do QRW want to fill an aggregate, you can deselect it.

5. Select )LOO�DJJUHJDWH. The 7LPH�RI�$JJUHJDWLRQ dialog box appears.

Since it can take a long time to build an aggregate from an InfoCube, all the aggregatesare filled in the background.

Note that an aggregate can also read data from a larger aggregate that is already filled.You can therefore assign data to very compressed aggregates quickly.

6. Define when you want to start the job to fill the aggregate:

− LPPHGLDWHO\

− ODWHU

This takes you to the 7LPH�RI�6XEVHTXHQW�$JJUHJDWLRQ dialog box. Enter the date and timefor the background processing.

7. In the 6XEVHTXHQWO\�$JJUHJDWH�,QIR&XEH�$JJUHJDWHV�dialog box choose� 5HIUHVK� The systemcopies the relevant data to the columns

− User who scheduled the aggregate for building,

− Date for scheduling the new version of the aggregate

− Time for scheduling the new version of the aggregate

− Name of the background job



In the column -RE�6WDWXV�you have the following display options:

shows that the job of filling the aggregate is currently running.

shows that the job of filling the aggregate is scheduled, but is not running yet.

shows that the job of filling the aggregate was canceled.

To find out about your background jobs for filling aggregates, choose -REV. You get to the6LPSOH�-RE�6HOHFWLRQ�screen.

To view the logs for filling your aggregates, choose /RJ. The $QDO\]H�$SSOLFDWLRQ�/RJdialog box appears.

By using the transaction SLG1, you can directly access the application log even if the jobis not canceled. The $QDO\]H�$SSOLFDWLRQ�/RJ dialog box appears.

Enter the required data in the following fields:

)LHOG�ODEHOV (QWU\

2EMHFW RSSM

(Scheduler; Monitor; Tree Callback)

6XEREMHFW MON

(Monitor)

([W��,GHQWLI� (External Identification) For displaying all logs:

*,QIR&XEH*

For filling new aggregates:

MON:PROTOCOLL_ACTION-AGGR2-,QIR&XEH

(For rolling up already existing aggregates:

MON:PROTOCOLL_ACTION-AGGR1-,QIR&XEH)

Instead of entering ,QIR&XEH, enter thetechnical name of the desired InfoCube.

8. Choose �

6\VWHP�$FWLYLW\ 5HVXOW

The system reports all the executed actions in thelower right part of the log display.

If you used a variable for the key date in anaggregate with time-dependent attributes orhierarchies, the system evaluates this variablewhen it fills it and builds the aggregate on thecomputed key date.

If the aggregate was filled successfully, the statusdisplay in the column )LOOHG�6ZLWFKHG�RII��changesfrom to .

To activate and fill a number of aggregates at the same time, select them and choose $FWLYDWH�DQG�ILOO.

The system chooses the optimum sequence for filling the aggregates.

i. The large, detailed aggregates are filled first.

ii. The smaller, very compressed aggregates are filled next.



The larger aggregates can therefore be used already when you are still building thesmaller ones.

5HVXOW

The active aggregate that is filled with data can be used for reporting. If the aggregate contains datathat is to be evaluated by a query, the query data is read automatically from the aggregate.

You can find more information about the number of records read and the use of an aggregate inqueries in Displaying Aggregates and their Components [Seite 138].

You can roll up new data packages (requests) into the aggregate. For more information see Rolling upData into an Aggregate [Seite 144].



5ROOLQJ�XS�'DWD�LQWR�DQ�$JJUHJDWH

8VH

If you load new data packages (requests) into the InfoCube, these are not available at first in reportingby using an aggregate. In order to supply the aggregate with the new InfoCube data, you first have toload these into the aggregate tables for a set time frame. This process is known as a roll up [Extern].

3UHUHTXLVLWHV

• New data packages (requests) were loaded into an InfoCube.

• Aggregates for this InfoCube are already activated and filled with data.

3URFHGXUH

In the InfoCube maintenance you can set for each InfoCube the way in which the rolling up of datapackages into the aggregates need to be run.

You are in the 0RGHOLQJ�function area in the Administrator Workbench. Choose 0DQDJH by using thecontext menu for the InfoCube you want. You arrive at the screen 0DQDJLQJ�WKH�'DWD�7DUJHWV. Thesystem transfers the InfoCube data into the list in the upper screen area.

([HFXWLRQ�7\SH 3URFHGXUH

,QFOXGLQJ�GDWD�SDFNDJH�LQWR�D�SURFHVV�FKDLQDV�D�SURFHVV

We recommend admission into aprocess chain

• with complex schedules

• with difficulties with automatisms andevent collectors

• for all new developments

1. Choose the tabstrip 5ROO�8S from the screen0DQDJLQJ�'DWD�7DUJHWV.

The system suggests the largestpossible value for 5ROO�8S�WR�5HTXHVW,'� However, you can overwrite this.

2. Choose 3URFHVV�&KDLQ�0DLQWHQDQFH.

By using the transaction RSPC, youarrive at the dialog box Selecting aProcess Chain with an overviewusing the existing process chains inthe BW system.

If there is no suitable process chain, youcan create a new process chain with theprocess of rolling up.

You can find additional information underCreating Process Chains [Seite 440] inthe section &UHDWLQJ�3URFHVV�&KDLQV�E\8VLQJ�D�0DLQWHQDQFH�'LDORJ�IRU�D3URFHVV�

Starting data package roll ups manually

Use this procedure especially whenthe data from several data packagescreate a logical unit, and theytherefore only need to be released.

Different plants deliver their data at

1. Choose the tabstrip 5ROO�8S from the screen0DQDJLQJ�'DWD�7DUJHWV.

2. Choose 6HOHFWLRQ. You get to the 6WDUW�'DWH9DOXHV dialog box.

3. Choose the start date. You have the followingoptions:

− Immediately

− Date/Time



different points in time. The dataneeds to be visible first, however, inthe InfoCube if all plants have loadedtheir data into the InfoCube.

− After job

− After event

− By operation mode

4. Set the respective indicators if you would likethe job to run periodically.

5. Save

The following procedures are also possible, but should not be used for new scenarios.

([HFXWLRQ�7\SH 3URFHGXUH

Subsequent processing [Seite 448] 1. Choose the tabstrip 5ROO�8S from the screen0DQDJLQJ�'DWD�7DUJHWV.

2. Choose 6XEVHTXHQW�3URFHVVLQJ. You arriveat the dialog box 0DLQWDLQ�(YHQWV�WR�5XQ$IWHU�3URFHVVLQJ.

You can find further information underProcess Control [Seite 423] and Creatingan Event Collector [Seite 450].

5ROOLQJ�XS�HDFK�GDWD�SDFNDJH�DXWRPDWLFDOO\LQWR�WKH�DJJUHJDWH

The InfoCube has to be ensured fortechnical correctness and quality.

Only use the automatic roll up whenyou load requests into the InfoCubeand there is no overlapping betweenprocesses for loading, for roll ups,and for other automatisms for theInfoCube.

You can find additional informationunder Automatic Further Processing[Seite 415].

1. Choose this from the screen 'DWD�7DUJHW$GPLQLVWUDWLRQ from the (QYLURQPHQW��!$XWRPDWLF�5HTXHVW�3URFHVV You get to the$XWRPDWLVP�0DLQWHQDQFH dialog box.

2. Set the indicator for 5ROO�8S�'DWD�LQWR�WKH$JJUHJDWH under the group heading$XWRPDWLF�3URFHVVLQJ.

3. Save.

3URJUDP 56''.B$**5(*$7(6B52//83 You can also run the roll up with the programRSDDK_AGGREGATES_ROLLUP (see RunningPrograms Directly - Reports [Extern]).

You can also schedule this programas a regular background job or use itin an event collector [Seite 449].

5HVXOW

The new data for these queries, that were started after the roll up, is taken into account in reporting.

6HH�DOVR�

Managing InfoCubes [Seite 403]



(IILFLHQWO\�/RDGLQJ�'DWD�LQWR�$JJUHJDWHV

Setting Automatic CompressionYou can set if the aggregate of each InfoCube should be compressed automatically when it is filledwith data or after being rolled up from data packages (requests).

1. You are in the 0RGHOLQJ function area of the Administrator Workbench. In the InfoProvider tree,navigate to the required InfoCube.

2. In the context menu of the InfoCube select $GPLQLVWUDWH. The 0DQDJH�'DWD�7DUJHWV dialog boxappears.

3. Select tabstrip 5ROO�8S in the lower part of the screen.

4. Set the corresponding indicator in field &RPSUHVV�DIWHU�UROO�XS under the group header$JJUHJDWHV.

,QGLFDWRU :KDW�\RX�QHHG�WR�NQRZ

QRW set (default):

Automatic compression switched on

The aggregates of an InfoCube are compressedautomatically when they are filled with data orafter being rolled up from data packages(requests).

If you want to delete a data package (request)from the InfoCube and the InfoCube was alreadyrolled up to the aggregate, you have to deactivatethe aggregate and build it again.

set:

Automatic compression switched off

The aggregates are only compressed togetherwith the InfoCube.

Use this setting if you have to delete requestsfrom the InfoCube frequently. A specific requestcan be deleted from the aggregates when it hasbeen deleted from the InfoCube.

Keep an eye on the performance becauseaggregates can become quite large if they are notcompressed automatically.

Reading the Data in BlocksIf the amount of data is very large during filling, the system reads the data in blocks and not all at onetime. This avoids problems with the temporary tablespace on the database if you have very largesources (InfoCubes or aggregates).

For more information about setting the block size see the implementation guide for the %XVLQHVV,QIRUPDWLRQ�:DUHKRXVH -> *HQHUDO�%:�6HWWLQJV -> 3DUDPHWHUV�IRU�$JJUHJDWHV.

Optimizing the Performance of Aggregates with Few CharacteristicsAggregates with fewer than 14 characteristics are created for all databases so that each characteristicis in a separate dimension and these dimensions are created as line item dimensions. Aggregates thatonly consist of line item dimensions are filled with pure database means. This improves theperformance during filling and when rolling up.

The logical tree display in the right part of the screen of the $JJUHJDWH�0DLQWHQDQFH screen is copiedfrom the left part of the 6HOHFWLRQ�2SWLRQV�IRU�$JJUHJDWHV screen and does not mirror this special formof storage on the database.



)XUWKHU�(GLWLQJ�)XQFWLRQV�IRU�$JJUHJDWHV

8VH

In order to work efficiently with aggregates, you must check the structure and use of the aggregates.You can save time during uploading by either deactivating or deleting the aggregates that you nolonger need for reporting.

)XQFWLRQV

)XQFWLRQ ,QIRUPDWLRQ

�5ROO�8S +LHUDUFK\ The 5ROO�8S�$JJUHJDWH�+LHUDUFK\ dialog boxappears.

The system shows how the aggregates of anInfoCube lie in relationship to one another, thatis which aggregate can be built from whichother aggregate.

With the help of the roll-up-hierarchy, you canidentify similar aggregates and manuallyoptimize the specific aggregates on this basis.

Choose the automatic optimization in the$JJUHJDWH�0DLQWHQDQFH�screen from 3URSRVH -> 2SWLPL]H. For further information aboutautomatic optimization, look underAutomatically Selecting and OptimizingAggregates [Seite 149]).

�6ZLWFK�2Q�2II You can temporarily switch off an aggregate tocheck if you need to use it. An aggregate thatis switched off is QRW used when a query isexecuted.

To do this select the relevant aggregate andchoose �6ZLWFK�2Q�2II. An aggregate that isswitched off is marked in column)LOOHG�6ZLWFKHG�RII�with .

Since aggregates that are switched off mustalso be consistent, you do not have to activatethe aggregate again or to fill it when you switchit back on.

Execute a query or trace that would use theaggregate that was switched off. Compare thetime that the database needs with the time thatthe query needs when using the aggregate. Ifthe query is not significantly slower without theaggregate, you can deactivate or delete theaggregate.

You can find more information about evaluatingand controlling the use of aggregates inDisplaying Aggregates and their Components[Seite 138].

'HDFWLYDWH The system deletes all the data and databasetables of an aggregate. The definition of theaggregate is not deleted.

To do this, select the required aggregate andchoose 'HDFWLYDWH�



The status display in the columns 6WDWXV and)LOOHG�VZLWFKHG�RII change back to .

If you want to, you can activate and fill theaggregate again later.

'HOHWH The system deactivates the aggregate anddeletes the definition of the aggregate.

To do this, select the aggregate to be deletedand select the delete function either with 'HOHWH or from the context menu of theaggregate.



$XWRPDWLFDOO\�6HOHFWLQJ�DQG�2SWLPL]LQJ�$JJUHJDWHV

8VH

Data for the BW statistics InfoCube and the created queries can be used as part ofthe automatic selection and optimizing of aggregates.

In this, the system makes an assessment based on the definition of particularlysuitable aggregates. Aggregates that appear to be suitable, are proposedautomatically. You can optimize the proposed aggregates and use them for furtherwork with the InfoCube.

3UHUHTXLVLWHV

An InfoCube in active version is available.

Obviously, queries have to be in the InfoCube already, in order for you to be able touse the query statistics.

These must be collected before BW statistical data can be analyzed. You must activate the collectionprocess for statistical data for the InfoCube ($GPLQLVWUDWRU�:RUNEHQFK�→7RROV�→%:�6WDWLVWLFV�IRU,QIR&XEHV) and you must have already executed queries.

)XQFWLRQV

You can display a proposal of aggregates by choosing 3URSRVDOV from the menu. Youhave the following options:

• Proposals from queries: The queries that are created for an InfoCube are taken into account.

• Proposals from the previous navigation: The last navigational step is evaluated, which you carriedout with a query.

• Proposals from BW Statistics (tables): BW statistical data is taken into account (database tables).

• Proposals from BW Statistics (InfoCube): Data which is contained in the BW Statistics InfoCube, istaken into account.

You can also subsequently process the aggregates and add or delete characteristics.

6HH�DOVR�

Proposals from Queries [Seite 150]

Proposals from BW Statistics [Seite 151]



3URSRVDOV�IURP�4XHULHV

8VH

By choosing 3URSRVDOV�→ 3URSRVDOV�IURP�4XHULHV, you can select created queries forthe selected InfoCube, and view proposals for a minimum as well as a maximumaggregate for each InfoCube. The name of the proposed aggregate is derived from‘MIN’ or ‘MAX’ and sequence number.

Use this function when you are optimizing an InfoCube for the first time. If you haveexecuted queries before, use the other options for optimizing, because the number oftimes a query has been executed, and individual navigational steps are also taken intoaccount here.

The PLQLPDO�DJJUHJDWH�µ0,1¶�corresponds to the smallest aggregate possible,which contains only the data that is needed for the first time you drilldown on a query.

For this reason, set the query to hierarchical reading or reading on demand.

The drilldown defined in the BEx Analyzer is accelerated by you activating theminimal aggregate.

The PD[LPXP�DJJUHJDWH�µ0$;¶ represents an aggregate that supports everynavigational step of a query. This comes from the theory that the relevant query isdrilled down over all characteristics (all free characteristics that is). Even if thishappens less often in practice, this aggregate can be used by all the possiblenavigational steps of this query. But you must still check whether this aggregatereally is of any use. These aggregates are often the same size as the InfoCube, asfar as volume is concerned. In this case, do not use the aggregates.

If the components, meaning the characteristics and attributes of a newly definedaggregate that are not summarized, are identical to an aggregate that is alreadyproposed, they will not be added to the list. Instead, the number of calls is increasedby one.

In general it is the case that the higher the number of calls of an aggregate, the moreuseful the aggregate is. This means that the higher the number of calls of anaggregate, the higher the number of queries in which it can be used.

You can modify or delete the proposed aggregates.

6HH�DOVR�

Proposals from BW Statistics [Seite 151]

Optimizing Proposed Aggregates [Seite 152]



3URSRVDOV�IURP�%:�6WDWLVWLFV

8VH

If you have activated the collection option for OLAP statistical data, everynavigational step that requests data from the database, is saved. This includes whatcharacteristics, navigation attributes and hierarchies were involved. This statisticaldata is saved in database tables at first. You can then load this data into the BWstatistics InfoCube for evaluation.

You can also use this data for optimizing aggregates. The advantage of havingproposals from BW statistics as opposed to proposals from queries, is that the actualuser capacity is taken into account here.

Use this function if there is already representative statistical data. Also, use the function atregular intervals to adjust the aggregates against the changes in user actions.

You can evaluate the saved data over the menu path 3URSRVDO��→�3URSRVDO�IURP�%:6WDWLVWLFV��WDEOHV��or�3URSRVDO�IURP�%:�6WDWLVWLFV��,QIR&XEH�. You can restrict theanalysis to a sub-quantity of the data, where an interval for the start-time or the run-time of the query is specified.

After the data has been read from BW statistics, the current ideal aggregate isdetermined for every navigation step, and a list of the different aggregates is made.

For aggregates that vary in one component only on the aggregation level, all those with anaggregation level hierarchy (‘H’), or fixed value (‘F’), are replaced with an aggregate (‘*’)grouped according to characteristic values, as long as this has already been proposed.

The list of proposed aggregates has the same structure as the Proposal from Queries[Seite 150]. However, the list is generally longer.

You can modify or delete the proposed aggregates.

6HH�DOVR�

Optimizing Proposed Aggregates [Seite 152]



2SWLPL]LQJ�3URSRVHG�$JJUHJDWHV

8VH

If the query analysis or BW statistics has come up with several proposals foraggregates, it is not necessarily advisable to activate all of them.

This reduces the run-times for queries, and optimizes the roll-up of aggregates in away that allows aggregates that are already rolled up and available to be used. But,as a rule, it takes up too much memory space, and it takes too long to fill theaggregates.

In addition to the runtime for the queries, complete optimization must also take intoaccount the dependencies of the aggregates, their memory requirement and the timetaken to roll up new data amongst other factors.

$FWLYLWLHV

A simplified optimization is available over the pushbutton 3URSRVDO�→ 2SWLPL]H�

For this optimization it is usually assumed (heuristics), that the number of aggregatesshould be reduced first. In addition, those aggregates are selected that have beencalled up least often and together account for 20% of all calls. These aggregates arechecked, one after the other, to see if there are aggregates with exactly one extracomponent.

If several aggregates with exactly one extra component are found, the one with themost number of calls is selected. These are taken into account with the aggregatesthat have been checked. The checked aggregate (from the 20% quantity) is thendeleted from the proposal list.

However, this only happens if the number of calls for the checked aggregate is not morethan double the calls for the aggregate with the extra components. This preventsaggregates from being replaced by others that are used relatively rarely.

You can continue to optimize until the point where the aggregate is small enough, oruntil no more aggregates can be brought together.

Because the optimizer has no information on the data structure, you should check theproposals again before filling with data. For example, a proposed aggregate can contain acharacteristic that is almost the same size as the InfoCube. When the aggregate is filled,therefore, practically a copy of the InfoCube is created, which is not normally advisable orof any use.

6HH�DOVR�




02/$3�6WRUH

'HILQLWLRQ

MOLAP (Multidimensional Online Analytical Processing) is a format conceived especially for storingmultidimensional data in a multidimensional database.

8VH

MOLAP is an alternative physical store to ROLAP (Relational Online Analytical Processing), which is astore for multidimensional data in a relational database.

You have the option in BW to create aggregates either on the basis of a ROLAP store or on the basisof a MOLAP store. Scenarios, where both store types appear, are not possible.

Nevertheless, you can toggle between MOLAP and ROLAP aggregates.

You can find additional information about using and maintaining MOLAP aggregates inMOLAP Aggregate [Seite 155].

5HVWULFWLRQV�ZKHQ�XVLQJ�WKH�02/$3�VWRUH

The BW MOLAP store is a platform-specific means of optimizing query performance. It uses MicrosoftAnalysis Services and, for this reason, it is only available for a Microsoft SQL server databaseplatform.

6WUXFWXUH

The multidimensional data are stored in arrays in a MOLAP store. These arrays are physically storedas compressed files on the Microsoft Analysis Server.

In a ROLAP store, however, the multidimensional data is stored in tables that are organized in a starschema in the database.

,QWHJUDWLRQ

The following overview illustrates how Microsoft Analysis Services is technically integrated in aBusiness Information Warehouse System.



06�$QDO\VLV�6HUYLFHV

'%�6HUYHU�

6$3�02/$3�%ULGJH

��

$SSOLFDWLRQ�6HUYHU

52/$3�$JJUHJDWHV

��

&OLHQW &OLHQW &OLHQW

02/$3�$JJUHJDWHV

The following services are also installed on the database server:

• Microsoft Analysis Services

• SAP MOLAP Bridge

The SAP MOLAP Bridge provides the interface used to access Microsoft AnalysisServices functions from the BW system.

6HH�DOVR�

%:�&XVWRPL]LQJ�,PSOHPHQWDWLRQ�*XLGH -> %XVLQHVV�,QIRUPDWLRQ�:DUHKRXVH -> &RQQHFWLRQV�WR�2WKHU6\VWHPV -> 0LFURVRIW�$QDO\VLV�,QWHJUDWLRQ ->

• &RQQHFWLRQ�EHWZHHQ�0LFURVRIW�$QDO\VLV�6HUYLFHV�DQG�%:

• &UHDWH�5)&�GHVWLQDWLRQV

• &UHDWH�02/$3�GDWDEDVH

MOLAP Aggregate [Seite 155]

MOLAP Cube (Root Aggregate) [Seite 157]

Create MOLAP Cube [Seite 158]



02/$3�$JJUHJDWH

'HILQLWLRQ

A MOLAP aggregate�is an aggregate of an InfoCube, whose data is physically stored in a MOLAPstore.

Contrasting model: ROLAP.

8VH

6LPLODULWLHV�EHWZHHQ�02/$3�DQG�52/$3�DJJUHJDWHV

MOLAP aggregates have significant properties in common with ROLAP aggregates.

• Aggregates improve performance when executing queries, but do not improve the reportingfunctions. A user who constructs a query in an InfoCube with aggregates sees functionally nodifference between MOLAP and ROLAP aggregates.

• Data is stored redundantly and persistently in the aggregates.

• The aggregates are used when a query is executed. The aggregates cannot be directly accessedin the BW system.

'LIIHUHQFHV�EHWZHHQ�02/$3�DQG�52/$3�DJJUHJDWHV

MOLAP aggregates differ from ROLAP aggregates with regard to the following features:

• MOLAP aggregates are stored in a MOLAP store. For more information, see MOLAP Store [Seite153]

• MOLAP aggregates do not allow for filter conditions for characteristics. The definition of a MOLAPaggregate only relates to the selection of characteristics, in which the system GRHV�QRWsummarize. (The system summarizes in characteristics that are not selected).

You can find additional information about special features of ROLAP aggregates inAggregation Levels [Seite 127].

5HFRPPHQGDWLRQV�IRU�XVLQJ�02/$3�DJJUHJDWHV�

Before making a decision about whether it is better to create MOLAP- or ROLAP aggregates for anInfoCube, you need to check the prerequisites for both options.

MOLAP uses numerous structural master data properties to improve efficiency. When changes aremade to master data, MOLAP objects must be reconstructed in parallel, either partially or completely:Changing a BW hierarchy has the effect that all MOLAP Cubes that contain this hierarchy are forcedto be reconstructed. On the other hand, changing attribute values requires less effort. Nevertheless,both lead to increased run time for the hierarchy- or attribute change run.

6WUXFWXUH

You can derive as many ROLAP aggregates as required directly from an InfoCube. However, thebasis structure in a MOLAP store has two stages.



SAP 6

,QIR&XEH

02/$3

$JJUHJDWHV

5HODWLRQDO'DWDEDVH

0DQDJHPHQW6\VWHP

02/$3�5RRW

$JJUHJDWH

02/$3

6WRUH

1. Exactly one MOLAP Cube (or a MOLAP root aggregate) is derived from an InfoCube. This usuallycontains the same information as the InfoCube.

Further information about a MOLAP Cube can be found at MOLAP Cube [Seite 157].

2. You can derive as many MOLAP aggregates from this MOLAP Cube (or MOLAP root aggregates)as required.

When you have created a MOLAP Cube, you can create, save and activate MOLAPaggregates in the same way as with ROLAP aggregates for any particular BW Cube.

You can find additional information about (ROLAP-) aggregates in Aggregate [Seite 126] .

The most crucial difference is that MOLAP aggregates are created on the Microsoft AnalysisServer. MOLAP aggregates can easily be converted to ROLAP aggregates, since theaggregate definition is, in contrast, stored in the BW.

,QWHJUDWLRQ

The relationship of an InfoCube in the store differs from that of an aggregate, as below:

$JJUHJDWHV %DVLV�,QIR&XEH

ROLAP ROLAP

MOLAP ROLAP

It is possible to toggle between ROLAP and MOLAP as a store for aggregates of one and the sameInfoCube.

If the system determined that ROLAP aggregates could be derived from a particularInfoCube, this can be converted to MOLAP aggregates. During this process, the systemdeletes the existing ROLAP aggregates and builds them in MOLAP.

You can change from ROLAP to MOLAP and vice versa.



02/$3�&XEH��5RRW�$JJUHJDWH�

'HILQLWLRQ

A 02/$3�&XEH�is a Basis Cube, whose data is physically stored in a MOLAP store.

The description 02/$3�5RRW�$JJUHJDWH�is used synonymously.� This description reflectsthe fact that a MOLAP aggregate is treated like an aggregate.

8VH

A MOLAP Cube is derived directly from an InfoCube (See MOLAP Aggregate [Seite 155]). Dataconsistency is secured when constructing additional aggregates and when requesting queries in thebase of a uniform MOLAP store. This is because a MOLAP Cube usually contains the same data asthe basis InfoCube.

6WUXFWXUH

A MOLAP Cube is constructed from a BW InfoCube using specific rules. Note the followingrestrictions: The BW InfoCube must not;

• contain any time-dependent characteristics

• contain any non-cumulative key figures

• be a transactional InfoCube

The total of all characteristics, navigation attributes and hierarchies must not be greater than 127.

6HH�DOVR�

Create MOLAP Cube [Seite 158]



&UHDWH�02/$3�&XEH

8VH

In order to work with MOLAP aggregates, you firstly need to create a MOLAP Cube.

(See MOLAP Cube (Root Aggregate) [Seite 157])

3UHUHTXLVLWHV

The BW system must be connected to a Microsoft Analysis server via the SAP MOLAP Bridge.

The InfoCube for which you want to create an aggregate has been saved and is active. There are notyet any aggregates for the selected InfoCube.

3URFHGXUH

1. You are in the 0RGHOLQJ function area of the Administrator Workbench. In the navigation windowchoose ,QIR3URYLGHU.

2. In the InfoProvider tree navigate to the InfoCube whose queries you want to optimize.

3. In the context menu of the InfoCube choose &KDQJH. The (GLW�,QIR&XEH�screen appears.

4. Choose 02/$3�6WRUH from ([WUDV� The 0XOWLGLPHQVLRQDO�&XEH dialog box appears.

5. Process the window areas from top to bottom. The system supports this process with traffic lightsand system messages.

02/$3�&XEH��6WUXFWXUH

Mapping possible? Traffic light display &KHFN

Does MOLAP Cube exist? Traffic light display

Refresh

&UHDWH

'HOHWH

02/$3�&XEH��'DWD

MOLAP Cube processed? Traffic light display &KHFN

Loading Data: • complete

• refresh

Execute

in the background

i. Check to see if Mapping is possible When the traffic light displays WR�FKHFN, choose &KHFN. You can find additional information about the structural properties of a MOLAP

Cube relevant here under MOLAP-Cube (Root Aggregate) [Seite 157].

ii. If Mapping is possible, you can create a MOLAP Cube on the Microsoft Analysis server.

This step is approximately the same as when activating an InfoCube in BW. Databaseviews, MOLAP dimensions, MOLAP Cube partitions and finally the MOLAP Cube arecreated.

iii. Finally, you can process the MOLAP Cube. In this step, the MOLAP Cube is filled withdata.

Choose the fill mode.

If the MOLAP Cube is to be filled with data for the first time, choose FRPSOHWH

If you want to load new data into the MOLAP Cube , choose UHIUHVK�

Choose how the system should carry out the processing.



When the basis BW InfoCube only contains a small amount of data, we recommend youimmediately start processing using ([HFXWH�in the dialog box. In this way, you canfollow the actions immediately.

When the basis BW InfoCube contains a large amount of data , we recommend that youschedule processing in the background.

5HVXOW

A MOLAP Cube is now available as the result of this procedure.



2'6�2EMHFW

'HILQLWLRQ

An ODS object acts as a storage location for consolidated and cleaned-up transaction data(transaction data or master data, for example) on the document (atomic) level.

It describes a consolidated dataset from one or more InfoSources. This dataset can be evaluatedusing a BEx query.

��

�!#"%$'&�(*),+.-0/21')43'5�),+6)�72+6/(6&

"8597:"%;=<>&@?,+*A

B CDE FGDDH CI GD

J (6)41�K�3L)4(�-M+�NO�1,+6&@P2(6)Q+R-S/21

O�1@T*/�UVK�;4&,A

W FX YZ[\]E YF^ __GDD

` a] Z\_]E YFRbc IG\FCd be Z\FDX YZ[\]E YF

B CDE FGDDH CI GD

f%)@A,+6&4(�59)Q+.)

An ODS object contains key fields (for example, document number/item) and data fields that can alsocontain character fields (for example, order status, customer) as key figures. The data from an ODSobject can be updated with a delta update into InfoCubes and/or other ODS objects or master datatables (attributes or texts) in the same system or across different systems.

Unlike multi-dimensional data storage using InfoCubes, the data in ODS objects is stored intransparent, flat database tables. Fact tables or dimension tables are not created.

8VH

The cumulative update of key figures is supported for ODS objects, just as it is with InfoCubes, butwith ODS objects it is also possible to overwrite data fields. This is particularly important withdocument-related structures, since changes made to documents in the source system do not applysolely to numeric fields such as order quantity, but also to non-numeric fields such as goods receiver,status, and delivery date. To map these changes in the BW ODS objects, the relevant fields in theODS objects must also be overwritten and set to the current value.

6WUXFWXUH

Every ODS object is represented on the database by three transparent tables:

$FWLYH�GDWD� A table containing the active data (A table)

$FWLYDWLRQ�TXHXH: For saving ODS data records that are to be updated but that have not yet beenactivated. The data is deleted after the records have been activated.

&KDQJH�ORJ: For updating delta from the ODS Object into other data targets, such as ODS Objects orInfoCubes for example.

An exception is the transactional ODS object, which is only made up of the active datatable.



� ��

� ��

�&�� O�5�O��)@?�� O 5�O�9&'?� ��9/

�&�� O�5�O��)@?�� O 5�O�9&'?� ��9/

� ��V�� 2

�� ! �� " ��9!#��

�� 9��$ ��2

��

59/�?� ��/�

The tables containing active data are constructed according to the ODS object definition, meaning thatkey fields and data fields are specified when the ODS object is defined. Activation queue and changelog are the same in the table’s structure. They have the request ID, package ID and the record numberas a key.

Data can be loaded from several source systems at the same time. The queuing mechanism allowsparallel insertion. The key allows records to be labeled consistently in the activation queue.

The data is loaded into the change log via the activation queue and reaches the active data tablewhen activated. From here, it is made available for reporting. During activation, the requests aresorted according to their logical keys. This makes sure that the data is updated in the active data tablein the correct request sequence.

See also the Example of Updating Data to an ODS Object [Seite 166]

,QWHJUDWLRQ

,QWHJUDWLRQ�ZLWK�GDWD�IORZ

The diagram below shows the data flow in BW, enhanced with ODS objects. The data flow consists ofthree steps:

1. Loading the data from the DataSource into the PSA.In this step, the data from a source system DataSource is loaded and stored in the transferstructure format. The PSA is the input storage location for BW. DataSources with the IDoc transfermethod are not supported with ODS objects.

2. Updating the data into the ODS object, and activating the data

− Updating the data into the ODS object using transfer and update rules.The transfer rules transform and clean up the data from the PSA. Generally, the update rulesare only used here for 1 to 1 transfer into the ODS object. This is because transformation hasalready taken place in the transfer rules.

− Activating the data in the ODS object.When you activate the data, the data necessary for a delta update is sent to the change log.

3. Updating the data from the ODS object

− Updating the data in the related data targets, such as InfoCubes or ODS objects, for example.In this step, the system uses the update rules to update the data that has not yet beenprocessed in the change log (the delta) into InfoCubes, other ODS objects or master datatables. Only update rules are used here, because the data is already available in a cleansedand consolidated format.



− Transferring the data from an ODS object into other BW systemsIn this step, it is possible to use the data mart interface to load data from one BW into anotherBW. In the BW source system, the corresponding ODS object acts as a DataSource that theBW target system recognizes as a DataSource replica, through the metadata comparison. TheBW target system is now able to request data from the source system, just as it does withevery other DataSource. The requested data is stored in the input storage PSA for furtherprocessing, such as updating into InfoCubes, for example.

ODS-ServerODS-Server %:�'DWD�0DUW%:�'DWD�0DUW

��

��

�� "!$#&%'�)(

*,+ �*,-/.1032�4*,+ �

*,-5.607284

2'6�2EMHFW

+:984;9 � <�=�> 2�0 ��

�$�&�� ?!�#&%@�A(B�CD�AE�(GFH��C$!�#&%'�)(

,QWHJUDWLRQ�ZLWK�WKH�$GPLQLVWUDWRU�:RUNEHQFK��0RGHOLQJ

0HWDGDWD

The ODS objects are fully integrated with BW metadata. They are transported just like InfoCubes, andinstalled from Business Content. The ODS objects are grouped with the InfoCubes in the InfoProviderview of the Administrator Workbench - Modeling, and are displayed in a tree. They also appear in thedata flow display.

8SGDWH

The update rules define the rules that are used to write to an ODS object. They are very similar to theupdate rules for InfoCubes. The most important difference is how the Data Fields Are Updated [Seite208]. When you update requests in an ODS object, you have an overwrite option as well as anaddition option.

The Delta Process [Seite 245] , which is defined for the DataSource, also influences the update. Whenyou are loading flat files [Seite 292], you have to select a suitable delta process from the transferstructure maintenance, this ensures that you use the correct type of update.

Unit fields and currency fields operate just like normal key figures, meaning that they must be explicitlyfilled using a rule.

6FKHGXOLQJ�DQG�0RQLWRULQJ

The processes for scheduling InfoPackages for updating into InfoCubes and ODS objects areidentical. Error handling is an exception here. It cannot be used with ODS objects.

It is also possible to schedule the activation of ODS object data and the update from the ODS objectinto the related InfoCubes or ODS objects.

The individual steps, including the ODS object processing, are logged in the Monitor. Logs detailingthe activation of the new records from the existing request in the ODS object, are also stored in theMonitor.



/RDGDEOH�'DWD6RXUFHV

In full-update mode, every transactional DataSource contained in an ODS object is updated. In delta-update mode, only those DataSources that are flagged as ODS-delta compatible are updated.



6FHQDULR�IRU�2'6�2EMHFWVThe diagram below shows how ODS objects are used in this example of updating order and deliveryinformation, and the status tracking of orders, meaning which orders are open, which are partially-delivered, and so on.

2'62'6

36$

��

,QIR&XEH

� ��

� � �� !� ��

� � ��#"� ��!� �� /HYHO��

/HYHO��

$�%��&('#�)��*��+�-,$�%.��&('#�)�#*��+�-, $�%.��&-'#�)�#*��/�0,$1%��&('#�)��*��/�-,

$�%.��&('#�)��*��+�-,$�%.��&-'#�)�#*��/�0,

$�%.��&('#�)��*��+�-,2�� &�3.,045�� #*��6�-,$�%.��&('#�)�#*��+�-,27� &�30,.4��8�#*��+�0,

There are three main steps to the entire data process:

1. Loading the data into BW and storing it in the PSA [Seite 387]

The data requested by BW is stored initially in the PSA. The PSA is a transparent databasetable, in which data is saved, per request, in the format of the transfer structure. A PSA iscreated for each DataSource and each source system. The PSA is the storage location forincoming data in BW. Requested data is saved, unchanged, to the source system.

2. Processing and storing the data in ODS Objects.

In the second step, the ODS Objects are used on two different levels.

a. On level 1, the data from an InfoSource from several source systems is stored in ODS objects.This allows data to be saved in a consolidated way in the technical format of BW. The transferrules cleanse the data from the source system-dependent data format of the PSA. On level 1,the data is stored on the document level (for example, orders and deliveries) and constitutesthe consolidated database for further processing in BW. Reporting is therefore not usuallycarried out on the ODS objects at this level.

b. On level 2, transfer rules subsequently combine the data from several ODS objects into asingle ODS object in accordance with business-related criteria. The data is very detailed, forexample, information such as the delivery quantity, the delivery delay in days, and the orderstatus, are calculated and stored per order item. Level 2 is used specifically for operativereporting issues, for example, which orders are still open from the last week. Unlike OLAPreporting, where very large quantities of data are selected, here data is displayed andanalyzed selectively.

3. Storing data in the InfoCube

In the final step, the data is aggregated from the ODS object on level 2 into an InfoCube,meaning in this scenario, that the InfoCube does not contain the order number, but saves thedata, for example, on the levels of customer, product, and month. OLAP reporting using theBEx Query is also run on this data. You can still display the detailed document data from theODS object whenever you need to. Use the report/report interface [Extern] from a BEx query.



In this way, you are able to analyze the aggregated data from the InfoCube, and target thespecific level of detail you want to access in the data.



([DPSOH�IRU�8SGDWLQJ�'DWD�LQ�DQ�2'6�2EMHFWThe graphic below shows how data is updated into an ODS object and the effect of the activation step.

�� ! �"#��%$� ��&��! �"#��'(�%$� ��&��!)��! �"#��!*�+�$

�-,/.10-�2��1��! �"#��3$�-,/.10�)4��1��! �"#��%+�$

546#798!:<;=?>�7@>

A 7@><B�8DC<BFEGC/B-8DC�;A 7@>/B-8DC/BHE-C<B-8IC/;

JLK >�C/B�;M<N�B

O?;/P�QR@O?;/P�S#T

O?;/P-U

546�798V:�>#7W8N-CXZY ; Y ;

546#798!:<>�7W8N�C

��#� � �� [�\L�/]#^�_ �"#��2�`�3$ �"#��2�1+�$

1. Request 1 with amount 10 and request 2 with amount 30 are loaded parallel into the ODS object.This takes you to the activation queue.

2. When you carry out the activation step, the new data is transferred into the table containing theactive data and immediately deleted from the activation queue. In the table containing the activedata, the amount 10 is replaced by 30 (since 2YHUZULWH is set as the update type).

3. When you activate the data, the change log is also notified: The old record from the active table issaved as a negative (-10) and the new record is stored as a positive (+30).

4. If all the records are activated, you can update the changes to the data records for the ODS objectin the related ODS objects and/or InfoCubes, in a separate step. The amount in this example isincreased in the related data targets by 20.



&UHDWLQJ�2'6�2EMHFWV

3UHUHTXLVLWHV

Make sure that all the InfoObjects that you want to transfer into the ODS object are active. Create anyrequired InfoObjects that do not exist already, and activate them.

As an alternative to creating a new ODS object, it is also possible to transfer an ODS object from SAPdelivered Business Content [Seite 21].

3URFHGXUH

1. Select the InfoArea that you want to assign the ODS object to, or create a new InfoArea. Choose0RGHOLQJ�→�,QIR�3URYLGHUV�→ &UHDWH�,QIR$UHD.

2. From the context menu for the InfoArea, choose &UHDWH�2'6�2EMHFW.

3. Give a name and a description for the ODS object, and choose &UHDWH.

If you want to create a copy of an existing ODS object, specify the ODS object that you wantto use as a template.

You get to the ODS object maintenance screen.

4. Transferring InfoObjects:

On the left side of the screen, there are various templates to choose from, which allow you toget a better overview in relation to a particular task. For performance reasons, the defaultsetting here is an empty template. Using the pushbuttons, select an InfoSource (only theInfoObjects for the communication structure of the InfoSource are displayed), an InfoCube, anODS object, or an InfoObject catalog.

Define the ODS object in the right half of the screen. Using the drag and drop function, assignthe InfoObjects in the key fields and in the data fields. It is possible to select severalInfoObjects at once. The system assigns navigation attributes automatically. These navigationattributes can be switched on for reporting in BEx.

There has to be at least one key field and one data field. Additional restrictions:

− You can create a maximum of 16 key fields

− You can create a maximum of 749 fields

− You can reserve 1962 bytes (minus 44 bytes for the change log)

− You cannot include key figures as key fields

5. Under 6HWWLQJV, you can:

• make the ODS object available for use in BEx reporting. It is possible to use an ODSobject in a BEx query only if you have set this option.

• select the ODS object type. You can choose between standard and transactional,whereby standard is pre-installed and transactional is only meant for special cases. Seealso Transactional ODS Object [Seite 169].

• to see the name of the InfoObject for which the ODS object is the check table, ifnecessary. This can be specified when creating an InfoObject. See also InfoObjectMaintenance [Seite 56].

• determine that the system automatically sets the quality status to OK after loading datainto the ODS object. As a rule, this function must be selected. Only deselect this indicatorif you want to check the data after it has been loaded.

• activate the ODS data automatically. Data that has been given the quality status OK istransferred from the $FWLYDWLRQ�4XHXH into the $FWLYH�GDWD table, and the change log isupdated accordingly. Activation is carried out by a new job that is started after loading into



an ODS object is complete. If the activation process terminates, there can be no automaticupdate.

• update the ODS data automatically. Once it has been activated, the data is updated in thedata targets. An init. update is carried out automatically with the first update. If theactivation process terminates, there can be no automatic update. The update is carriedout by a new job that is started once activation is complete.

�� You can create secondary indexes by using the context menu under ,QGH[HV in order to improvethe loading and query performance of the ODS object. Primary indexes are created automaticallyby the system.

If the values in the index uniquely identify each record in the table, select 8QLTXH�,QGH[ fromthe dialog box. The description of the indexes is specified by the system. To create a folderfor the indexes, choose &RQWLQXH from the dialog box. Now you can transfer the key fields thatyou want into the index folder by using Drag & Drop.

You can create a maximum of 16 secondary indexes.

For more information, see Indexes [Extern]

�� Additional functions:

• Using the InfoObject context menu, it is possible to set ODS object-specific properties forBEx reporting, such a text display and decimal points.

• Use &KHFN to make sure that the ODS object is consistent.

8. Save the ODS object, and activate it.

1H[W�6WHS�




7UDQVDFWLRQDO�2'6�REMHFW

'HILQLWLRQ

The transactional ODS object is different from the standard ODS object through its architecture andthe way in which it contains data. It fulfills the requirement for data to be immediately visible. This isnecessary, for example, for SAP Strategic Enterprise Management (SEM) or other externalapplications.

8VH

Transactional ODS objects allow data to be available quickly. The data from this kind of ODS object isaccessed transactionally, that is, data is written to the ODS object (possibly by several users at thesame time) and reread as soon as possible.

It offers no replacement for the standard ODS objeckt. Instead, an additional function displays thosethat can be used for special applications.

6WUXFWXUH

The transactional ODS object simply consists of a table for active data. The table gets the data fromexternal systems by using an Add / Overwrite API for inserting, updating, or deleting data. The loadingprocess is not supported by the BW system. The advantage to the way it is structured is that data iseasy to access. They are made available for reporting immediately after being loaded.

6RXUFH�6\VWHP

External System

%:�6\VWHP

ODS Object

Add / OverwriteAPI

&UHDWLQJ�D�WUDQVDFWLRQDO�2'6�REMHFW

When creating an ODS object, you can change the ODS object type under 6HWWLQJV�via the contextmenu. The default setting is 6WDQGDUG

,QWHJUDWLRQ

Since transactional ODS objects cannot be filled with BW data using staging (data is not supplied fromthe DataSources), they are not displayed in the Scheduler or in the Monitor. Transactional ODSobjects can therefore not be updated in the same way as standard ODS objects.

As no change log is generated, no delta update of data stored at the end of the process is possible.

You cannot set the indicator for BEx Reporting when creating a transactional ODS object.



You can download the data for that from your transactional ODS object by using the downloadfunction. You can find this function in the administration of the ODS objects, 7DEVWULS�&RQWHQWV →$FWLYH�'DWD�� Choose ([HFXWH to display the data. Using the main menu (GLW�→�'RZQORDG, you candownload the data in different formats.



2'6�2EMHFW�3HUIRUPDQFHTo ensure good loading performance for ODS objects, take account of the following:

1. Initialization, then deltas

To load data into an ODS object, initialize first and then load deltas. Also note that the table fornew data must not have more than one million data records. If necessary, carry out theinitialization in several steps, using selection criteria.

2. Avoid SIDs

Extracting SIDs takes a long time and can be avoided by:

− Not setting the indicator for BEx Reporting if you are using the ODS object only as a datastore. If you do not set this indicator, SIDs are extracted for all new characteristic values.

− If you use line items (for example, document number, time stamp) as characteristics in theODS object, flagging these in the characteristic maintenance as “Exclusively Attribute”.

3. DB partitioning in tables for active data (techn. A table)

By partitioning by database levels, you can delete data from the ODS object much morequickly. As a partitioning criterion, choose the characteristic by which you want to delete. Formore information on partitioning database tables, see the database documentation (DBMS-CD). Partitioning is supported by the following databases: Oracle, DB2/390, Informix.

4. Indexing

Use selection criteria for queries on ODS objects. If the key fields are specified, the existingprimary index is used. The frequently accessed characteristic should appear on the left-handside.

If you did not specify the key fields completely in the selection criteria (visible in SQL trace),you can create additional indexes to improve the run time of the query. You create thesesecondary indexes in the ODS object maintenance.



)XUWKHU�3URFHVVLQJ�RI�2'6�2EMHFWV

8VH

Before you can use an ODS object as a data source for another ODS object or InfoCube, you have tomake sure that the data is of good quality, and that it is active in the system. You can only activate thedata, and update it in the data target manually, if you have not switched on the option for the automaticprocessing of the request in the ODS Object Maintenance [Seite 167] or Administration [Seite 417]

If you want to use the ODS object as a data source in other BW systems, you have to generate anexport DataSource first.

)XQFWLRQV

$FWLYDWLQJ�WKH�2'6�2EMHFW�GDWD

If you have not switched on the option $XWRPDWLFDOO\�$FWLYDWH�2'6�2EMHFW�'DWD in the ODSmaintenance or ODS administration screen, you have to activate the data manually. Either choose$FWLYDWH�2'6�2EMHFW�'DWD�using the &RQWH[W�0HQX�LQ�WKH�2'6�2EMHFW�or choose in the 5HTXHVWVtab strip in Administration. The inactive requests are displayed, enabling you to activate them. Onlyactivated requests are updated in other data targets.

Here you have the following options:

• Do not compress requests in a request when activation takes place.

If you set this indicator, a request in the change log appears from each loaded request afterbeing activated. These are then updated individually to additional data targets. Otherwise, allrequests activated in this process are compressed into a change log request. Only thisrequest can be completely rolled back from the ODS object. This has been possible sincerelease BW 2.0B.

• Process requests in a batch process in serial when activation takes place:

When this indicator is set, the data is activated in an extracted background process in serial.Otherwise, data is activated in the separated dialog processes in parallel.

6LPXODWLQJ�WKH�8SGDWH�IURP�WKH�2'6�2EMHFW�LQWR�2WKHU�'DWD�7DUJHWV

You can also simulate updating into other data targets before carrying out the update. Do this by onlyloading the data into the PSA, and start the simulation from there.

Go to the InfoSource tree and map the InfoSource generated for your ODS object using 6HWWLQJV�in themain menu. You can find your InfoSource under the application component with the same name asyour ODS object, with the prefix 8. Create an InfoPackage for this InfoSource, and load it only into thePSA. Having loaded the data into the PSA, proceed as follows:

Types of Data Update with PSA [Seite 389]

8SGDWLQJ�WKH�2'6�2EMHFW�'DWD�LQ�'DWD�7DUJHWV

If you have not chosen the option 8SGDWH�'DWD�7DUJHWV�IURP�2'6�2EMHFW�in the ODS objectmaintenance or administration screens, you have to update the ODS object manually. Choose fromthe &RQWH[W�0HQX�IRU�WKH�2'6�2EMHFW → 8SGDWH�2'6�'DWD�LQ�'DWD�7DUJHWV� Choose between an init-update and a full-update. You reach the Scheduler, where you either schedule the data for loading, orstart the loading process immediately.

8SGDWLQJ�LQ�DQ�2'6�2EMHFW

If you want to carry out a full-update, proceed as described above. As a result, you get an ODS objectwith active data (A-table).

If you carry out a full-upload, you cannot load any more deltas.



If you want to load deltas, you have to transfer the init data first. Do this by choosing the 5HFRQVWUXFWtabstrip from the ODS object administration. After reconstruction is complete, you are able to load thedeltas into the new ODS object. Load the change log data for the ODS object first of all. You are thenable to load the new deltas.

Performance note:

When you are updating large quantities of data, it makes sense to create separateInfoPackages and write these into the PSA first. When you update generatedInfoPackages, you can select 'DWD�7DUJHWV�2QO\�when editing� Since the update takesplace in dialog processors, time-out errors can occur. You can avoid this by choosing theoption 36$�2QO\�and 8SGDWH�6XEVHTXHQWO\�LQ�'DWD�7DUJHWV� The update into PSA is quitefast, the update in data targets is carried out in the background.

Make sure when you choose this option that you cannot switch on the automatic update.

8SGDWLQJ�LQ�DQ�,QIR&XEH�

There must be no init. data already contained in any InfoCube that you want to load deltas into. If youwant to have the init. data in the InfoCube, either reconstruct the InfoCube using the 5HFRQVWUXFWtabstrip in the ODS object administration, or carry out a full-update of the ODS data in the InfoCube. Ifyou choose to carry out a full-update, make sure that all the deltas contained in the ODS object havealready been updated. This prevents the deltas being updated twice in the InfoCube.

*HQHUDWLQJ�H[SRUW�'DWD6RXUFHV

If you want to use an ODS object in BW as a data source for an InfoCube or ODS object, you do notneed to generate an export DataSource, because it is possible to use all the ODS objects within a BWsystem as data sources. You only need to generate an export DataSource from the context menu ifyou want to use the ODS object as a data source in a second BW system. The export DataSource isneeded to transfer data from a source BW into a target BW. Generating ODS object exportDataSources is basically the same as generating InfoCube export DataSources.

In the Administrator Workbench, choose 0RGHOLQJ�→ 'DWD�7DUJHWV�→ �<RXU�2'6�2EMHFW�→ &RQWH[W

0HQX (ULJKW�PRXVH�FOLFN) → *HQHUDWH�([SRUW�'DWD6RXUFH.



'HOHWLQJ�IURP�WKH�&KDQJH�/RJ

8VH

You can only delete data from the ODS object change log. This is recommended if you have alreadyloaded several requests into the ODS object when these requests are no longer necessary for thedelta update. The change log can become very large in certain circumstances, causing theperformance advantages to delete the requests.

3URFHGXUH

Since the change log is also stored as a PSA table, you can use the function for deleting data from thePSA to delete data from the change log.

1. Go to the PSA tree.

2. Use the main menu to choose 6HWWLQJV → 'LVSOD\�*HQHUDWHG�2EMHFWV, so that you can display theInfoSource for your ODS object. Your InfoSource has the same name as your ODS object, alongwith the prefix ‘8’.

3. Use the context menu to choose 'HOHWH�36$�'DWD.

4. Proceed further as in Deleting Requests from the PSA [Seite 395].

For different deletion options from the ODS object, see also:

Deleting Requests [Seite 419]

Deleting Selectively from Fields [Seite 418]



6WDWXV�2YHUYLHZ�RI�2'6�2EMHFWV

8VH

The status overview displays the loading, activation and update status of all the ODS Objects. You canget to the ODS Object display or administration screen directly from this overview.

)XQFWLRQV

The /RDGLQJ�6WDWXV column shows whether the data was loaded successfully in the ODS Object or iferrors occurred. If there are errors shown in the loading status (red traffic light), you can branchstraight to the function 0DQDJH�2'6�2EMHFW.

The $FWLYDWLRQ�6WDWXV column shows whether all data has been activated yet or not. If not, you canactivate it by choosing the pushbutton.

The column 8SGDWH�6WDWXV shows whether all the ODS Object data has updated in the data target yetor not. If not, you can update the data in the data target by choosing the pushbutton.

Moreover, it is possible to jump to the ODS Object display or maintenance screen from here. To dothis, select one or more ODS Objects and choose 'LVSOD\�(or double-click on the name) or 0DQDJH.

$FWLYLWLHV

Choose 0RQLWRULQJ → 6WDWXV�2YHUYLHZ�in the Administrator Workbench.



2'6�'DWD�DQG�([WHUQDO�$SSOLFDWLRQV

8VH

Various functions allow you to read data from ODS objects from external applications or to fill ODSobjects from external applications.

)XQFWLRQV

A BAPI for reading data enables you to make ODS data available to external systems.

An API for writing data enables you to fill ODS objects with data from external applications. You canfind this in the transactional ODS object application. See Transactional ODS Objects [Seite 169].

([WHUQDO�6\VWHP([WHUQDO�6\VWHP

&XVWRPHU

3URJUDP

%:�6\VWHP%:�6\VWHP

2'6�2EMHFW

5HDG�%$3,

:ULWH�$3,

You can also download form the ODS object. You can display the ODS table data from the ODSobject administration, and also download the data using the Data Browser so that you can use ordisplay it in other applications. See Contents of an ODS Object [Seite 418].



+LHUDUFKLHV

'HILQLWLRQ

A hierarchy is a method of displaying a characteristic structured and grouped according to individualevaluation criteria.

8VH

Hierarchies are used in two main ways:

• First, for the structured display of the characteristic values (tree display) in a presentationhierarchy [Extern].

• Secondly, to select a defined quantity of characteristic values as a selection of hierarchy nodes[Extern].

6WUXFWXUH

The components of a hierarchy are:

1RGHV

A hierarchy consists of nodes. Node relationships are defined vertically as in the following:

• The highest node is the root from which additional roots can come.

• Each node (except for the highest node) is directly superior to another node.

You differentiate between nodes that are postable and are not postable [Seite 179].

5RRW

A hierarchy can have several roots. These have no superior nodes.

+LHUDUFK\�OHYHO

All nodes on the same level of the hierarchy (nodes that are the same distance away from the root)form a hierarchy level. The root of a hierarchy creates level one. The level of a node indicates thedistance between the node and the root.

/HDYHV

The leaves of a hierarchy come from characteristic values for the basic characteristic and can,therefore, also have entries in the fact table. In contrast to postable nodes, a leaf cannot havesubnodes.

,QWHUYDOV

Intervals encompass groups of leaves that belong together and that are described by their higher andlower limits. You can create them if a node has several leaves. You can find additional informationunder Hierarchy Intervals [Seite 198].

%DVLF�FKDUDFWHULVWLF

Hierarchies can be created only for those characteristics that do not reference other characteristics.(See also: Creating InfoObjects: Characteristic [Seite 33]).

The characteristic &RVW�(OHPHQW can be structured according to cost element groups. Thesecond hierarchy level consists, for example, of personnel costs, material costs,administration costs, and so on. Personnel costs are divided up, for example, into the costelement groups pay, salaries, and personnel overhead costs. The cost element group‘pay’ contains the cost elements ‘individual pay costs’, ‘pay overhead costs’ and ‘other paycosts’.

Another typical example of a characteristic hierarchy is the grouping of the characteristic5HJLRQ into districts that are themselves sub-divided into areas.



6DOHV�+LHUDUFK\

��

�� !�" �� #� ��$� ��"�

%��'&(� )"*+� %��'&(� )"* %��&#��)"*��

, �.-��0/1��.�2�$�2�'3�4

3URSHUWLHV

A BW hierarchy has the following properties:

• Hiearchies are set for basic characteristics (those that are not referenced to other characteristics).An example for a basic characteristic is 0COSTCENTER.

• Hierarchies are stored in special master data tables. They are also similar to master data, and cantherefore be used and modified in all InfoCubes.

• You can define several hierarchies for a single characteristic.

• A hierarchy can have a maximum of 98 levels.

,QWHJUDWLRQ

You can

• ORDG�FKDUDFWHULVWLF�KLHUDUFKLHV�IURP�D�VRXUFH�V\VWHP

The source system can be an SAP system or an external system (BAPI, file). If you want toload a hierarchy from an external system, you have to first maintain the metadata for thishierarchy. You can load a hierarchy directly from an SAP system – the metadata is alreadydelivered with it.

See: Loading Hierarchies [Seite 181]

• /RDGLQJ�XVLQJ�WKH�'DWD�0DUW�,QWHUIDFH�LQ�RWKHU�%:�V\VWHPV

If you want to use hierarchies from a BW system in another BW system, you do not (andcannot) transport them, since it concerns data when using hierarchies (and they are notTLOGO objects). In order to load hierarchies from a BW system into another BW system, youcan use the Data Mart Interface.

See: Using the Data Mart Interface [Seite 264]

• &UHDWH�FKDUDFWHULVWLF�KLHUDUFKLHV�LQ�WKH�%XVLQHVV�,QIRUPDWLRQ�:DUHKRXVH

See: Creating Hierarchies [Seite 184]

If you are working with DJJUHJDWHV and are loading or creating new hierarchies, or changing existinghierarchies, you have to reconstruct the aggregates that are affected by the changes afterwards (see:Adjusting Changes to Hierarchy and Attribute [Seite 399]).

3UHUHTXLVLWHV

You have to determine in the InfoObject maintenance [Seite 33] whether or not you want thecharacteristics to have hierarchies. The properties of the allowed hierarchy (for example, the hierarchyversions [Seite 193], time-dependent hierarchy structure) are also defined here.



+LHUDUFK\�1RGHV

6WUXFWXUH

A characteristic hierarchy consists of nodes and leaves. There are two kinds of possible nodes: thosethat can and those that cannot be posted.

1RGHV�WKDW�FDQ�EH�SRVWHG

All nodes that refer to the characteristic (for which the hierarchy has been created) are nodes that youcan post to. Transaction data can only be dragged from the InfoCube for nodes that can be posted to.

Leaves are nodes that can be posted and that do not have any lower-level nodes. The leaves of ahierarchy are characteristic values or characteristic value intervals (if intervals are allowed in thehierarchy for the characteristic). In contrast to other nodes, they can occur twice.

1RGHV�WKDW�FDQQRW�EH�SRVWHG

Nodes that cannot be posted do not refer to the basic characteristic. They are either text nodes thatyou can include in the hierarchy, or they are external characteristic nodes.

7H[W�QRGHV function purely as headers, and they are there only to improve the structure of yourhierarchy. They are special characteristic nodes for characteristic 0HIER_NODE.

You can also post H[WHUQDO�FKDUDFWHULVWLF�QRGHV in addition to the basic characteristic on which thehierarchy is based. You can identify any nodes, including a set of leaves with the characteristic valueof any characteristic (InfoObject).

In the following example, the hierarchy is based on the InfoObject &XVWRPHU. In addition,characteristic values for the InfoObject 5HJLRQ have also been transferred over into thehierarchy. The nodes for the external InfoObject 5HJLRQ that can not be posted aredisplayed as yellow, while the nodes for the InfoObject &XVWRPHU that can be posted aredisplayed as green. Text nodes, such as the customer hierarchy here, are displayed as afile.

��

� ��

��

!#"%$��'&%&

( �� )��

*�+(

, �-��

. �%&'/��

0 �� 1��324�5��

Both the overall hierarchy and the structure of a hierarchy (each individual noderelationship) can be time-dependent [Seite 195].



/LQN�1RGHV

8VH

You can attach a subtree to a hierarchy several times with the link node.

6WUXFWXUH

A link node duplicates the subtree of the original node. The name, and InfoObject (where necessarythe fields of the from-to dates) of the nodes are identical. The link node is, however, only a link to theoriginal node, meaning that it inherits the properties and subtrees of this original node. The differencebetween link nodes and original nodes is the different parent and neighbor nodes and the link identifierthat is set for the link node.

To model the node &RVW�&HQWHU�0DQDJHU�% to hang under the node &RVW�&HQWHU�� and&RVW�&HQWHU��, you have to hang &RVW�&HQWHU�0DQDJHU�% under &RVW�&HQWHU�� and hang alink node &RVW�&HQWHU�0DQDJHU�% under &RVW�&HQWHU��

Cost center 1

Resp. person A

Cost center 2

/LQN�QRGHResp. person B

Employee Y Employee X Employee YEmployee X

2ULJLQDO�QRGH

Resp. person BResp. person C

Link nodes cannot have their own lower-level nodes. They take on the level-level nodes ofthe original node. These adopted lower-level nodes are not displayed in the hierarchymaintenance screen.

,QWHJUDWLRQ

When you upload link nodes, they have their own node ID and higher-level ID (formerly ‘parent’).Lower-level ID (formerly ‘child’) and next ID must be blank, and node name, InfoObject and, whereapplicable, time intervals, are the same as the values for the original node. The link identifier must beset for this node.



/RDGLQJ�+LHUDUFKLHV

3UHUHTXLVLWHV

In the InfoObject maintenance [Seite 33], the indicator ZLWK�KLHUDUFKLHV is set, meaning that thecharacteristic can have hierarchies.

A source system must be assigned to the InfoSource for master data.

If you want to load hierarchies from external systems, you must also edit the metadata in the transferstructure maintenance screen. See also Uploading Hierarchies from Flat Files [Seite 296]

3URFHGXUH

1. Select the InfoSource tree under 0RGHOLQJ in the $GPLQLVWUDWRU�:RUNEHQFK.

2. Select the master data InfoSource for the InfoObject, to which you want to load the hierarchy.

3. Choose $VVLJQ�'DWD6RXUFH�from the context menu, and select the source system, from which youwant to load the hierarchy.

4. Choose the function &UHDWH�,QIR3DFNDJH�from the context menu (6HH��Maintaining InfoPackages[Seite 351]).

5. Give the InfoPackage a description.

6. Choose the pushbutton +LHUDUFKLHV�from the possible data types. You get a list of all thehierarchies that are available in the source system for this InfoObject.

7. On the tabstrip +LHUDUFK\�6HOHFWLRQ, select the hierarchy that you want to load into the BusinessInformation Warehouse.

It is possible to create a hierarchy as a sub-tree, provided there is already a hierarchyunder the specified technical key, and this hierarchy contains the root nodes of thehierarchy that you want to load.

For update methods, see Tabstrip: Select Hierarchy [Seite 361].

8. Use the other tabstrips to determine the update parameters, and schedule the InfoPackage. SeeMaintaining InfoPackages [Seite 351] and Scheduling InfoPackages [Seite 355].

5HVXOW

The hierarchy structure and the node texts/intervals are loaded. The structure information and thehierarchy texts are stored in the Business Information Warehouse.

You are now able to edit the hierarchy. You must activate it so that it can be used in reporting.

When you upload hierarchies, the system carries out a consistency check, making surethat the hierarchy structure is correct. Error messages are logged in the Monitor [Seite378].

6HH�DOVR�

Uploading Hierarchies from Flat Files [Seite 296]



/RDGLQJ�6XEWUHH�+LHUDUFKLHV�

8VH

After loading, it is possible to create a hierarchy as a subtree, provided there is already a hierarchyunder the specified technical key in the BW system, and this WDUJHW�KLHUDUFK\ contains the root nodesof the VXEWUHH�KLHUDUFK\ that you want to load.

You can use subtree hierarchies to combine hierarchies from various BW source systems amongstother things.

3UHUHTXLVLWHV

1. Every subtree hierarchy must have the same technical name as the target hierarchy. If required,you renamed the subtree hiearchy after the loading process. (refer to Tabstrip: Select Hierarchy[Seite 361]).The loaded hierarchy is only saved as a subtree when a hierarchy for the hierarchy basischaracteristic already exists in BW under the specified key. (The key consists of a technicalhierarchy, a to-date and a hierarchy version name if required). The BW system knows that theloaded hierarchy is to be included in a target hierarchy with the same technical name by the usermarking the 6XEWUHH�,QVHUW�or the 6XEWUHH�8SGDWH option.

2. When a hierarchy is to be included in a target hierarchy as a subtree, the root node of the subtreehierarchy must be included as a node in the target hierarchy. It must also have the same technicalproperties as this target hierarchy node. In the target- and subtree hierarchy, this so-calledLQWHUIDFH�QRGH�relates to the same InfoObject. It has the same technical name in the target- andsubtree hierarchy and has the same to-date when variables are time dependent.

3. The target hierarchy must not contain an additional subtree hierarchy node, unless it satisfies thepre-requisites for a correct double node in the new complete hierarchy.

)XQFWLRQV

When you load a hierarchy and execute a VXEWUHH�LQVHUW, the hierarchy is included in an exisitinghierarchy as a subtree, without the system deleting target hierarchy nodes.

If a subtree is inserted for a second time, there will be two sets of each subtree hierarchynode amongst the interface nodes. The load process is terminated for this reason.

When you load a hierarchy and execute a 6XEWUHH�8SGDWH, the hierarchy is included in an existinghierarchy as a subtree, and the system replaces the old subtree with the new one if required.

If a subtree update is executed again, all nodes that are found amongst the interfacenodes are deleted from the target hierarchy, before the new subtree is inserted.

$FWLYLWLHV

Execute the following activities on the Select Hierarchy tab strip to store a hierarchy as a subtree inBW.

1. After loading, change the technical name of the subtree hierarchy to the technical name of thetarget hierarchy. Choose 5HQDPH�+LHUDUFK\�$IWHU�/RDGLQJ�and enter the technical name.

2. Choose the Subtree Insert update method , when the hierarchy is to be included in an existinghierarchy as a subtree without the system deleting nodes in the target hierarchy.

or

choose the Subtree Update update method, when the hierarchy is to be included in an existinghierarchy as a subtree and the system is to replace the old subtree with the new one ifrequired.



([DPSOH

([DPSOH��

This example is based on the fact that the hierarchies for the InfoObject OCUST_SALES have textnodes for root nodes, which are represented by the InfoObject 0HIER_NODE with the characteristicvalue ~ROOT. Otherwise the hierarchies only consist of nodes that can be posted from InfoObject0CUST_SALES

If the InfoObject OSOURCESYSTEM is attached to 0CUST_SALES, it is possible to combinehierarchies from various SAP systems into one BW hierarchy. If a hierarchy is uploaded, theInfoObject 0SOURCESYSTEM is automatically filled with the corresponding source system ID. Whenthe same nodes come from different source systems, the attachment to the 0SOURCESYSTEMprevents double nodes in the target hierarchy. The interface node is the root node from the0CUST_SALES hierarchy in this example.

The name of the hierarchy to be loaded is selected in the InfoPackage for the corresponding sourcesystem. In this example, the same technical name is always used in the various source systems andmade available for selection. You can use the Tab Strip: Select a Hierarchy [Seite 361] in theScheduler to ensure, if this is not always the case, that the uploaded hierarchies always receive thesame technical name in BW. You can also set the update method here.

If all additional hierarchies are stored as a subtree after the full update of one of these hierarchiesusing 6XEWUHH�,QVHUW, you get the following: A hierarchy with a root node, under which all those nodeshang, which used to hang under the root nodes of the hierarchies specific to the source system.

If you were to use the 6XEWUHH�8SGDWH� you would get a target hierarchy containing the subtree thatwas last loaded. This is because all nodes under the interface nodes would be deleted before thesubtree is added.

([DPSOH��

This example assumes that there are different SET hierarchies for the InfoObject 0COSTCENTER,such as for Europe, Mexico, USA. It is also assumed that the nodes of one hierarchy do not appear inany other hierarchy.

IN BW, a hierarchy WORLD is created with the help of hierarchy maintenance with three interfacenodes that belong to the SET hierarchies mentioned above. You can use the Tab Strip: SelectHierarchy [Seite 361] in the Scheduler to ensure that the three SET hierarchies are stored after theloading process as a subtree under the technical name of the WORLD hierarchy.

When a SET hierarchy is loaded, you get a hierarchy, under whose root nodes the three hierarchiesEurope, Mexico and USA hang.

If you use the 6XEWUHH�,QVHUW�in this example, the scenario must be created again when uploadingonce more. Otherwise, the hierarchies would be added in duplicate. You can create the scenario againby deleting the nodes and subtrees under the interface hierarchies before re-loading.

If you use the 6XEWUHH�8SGDWH, the individual hierarchies can be loaded again as many times as youwant, because the old subtree is deleted each time.



&UHDWLQJ�+LHUDUFKLHV

3UHUHTXLVLWHV

In the InfoObject maintenance, the indicator ZLWK�KLHUDUFKLHV is set for the relevant characteristic,meaning that the characteristic can have hierarchies.

3URFHGXUH

1. Select the InfoObject tree under 0RGHOLQJ in the $GPLQLVWUDWRU�:RUNEHQFK.

2. If you have assigned the characteristic to an InfoObject catalog, select the correspondingInfoObject catalog for an InfoArea.

If the characteristic does not belong to an InfoObject catalog, select the 1RW�$VVLJQHG�1RGHVInfoArea�and the 1RW�$VVLJQHG�&KDUDFWHULVWLFV InfoObject catalog.

3. Select the characteristic for which you want to create a hierarchy, choose the context menu withthe right mouse button, and then &UHDWH�KLHUDUFK\.

4. In the dialog box, enter the technical hierarchy name, or the hierarchy version if applicable, thetime-reference, and at least one short description of the hierarchy. Confirm your entries. You cometo the screen 0DLQWDLQ�KLHUDUFKLHV. You can now define your hierarchy here.

&UHDWLQJ�1RGHV�DQG�/HDYHV

5. Select the root and choose (GLW�→�&UHDWH�QRGHV. Give the node a technical name and at least oneshort description.

6. Select a node that does not represent a value interval, and create a child node for it, or choose(GLW�→�,QVHUW��,QIR2EMHFW�QDPH!. You now see a list of the characteristic values and can selectone single value or various single values.

These InfoObjects are�QRGHV�WKDW�FDQ�EH�SRVWHG. These are symbolized by the greenInfoObject icon.

Please note the Combination options of nodes and leaves [Seite 186].

7. If you want to include external characteristic nodes in the hierarchy, you can do this using ULJKWPRXVH�EXWWRQ�→�,QVHUW�QRGHV�IRU�FKDUDFWHULVWLF, or &KDUDFWHULVWLF in the menu toolbar.

These InfoObjects are�QRGHV�WKDW�FDQQRW�EH�SRVWHG. These are symbolized by the yellowInfoObject icon.

8. If during InfoObject maintenance you specified that the hierarchy may contain intervals [Seite 198]and you want to create an interval, choose the right mouse key�→�&UHDWH�LQWHUYDO�or�,QWHUYDO�in themenu bar.�Specify (for example, with input help), the value interval.

You can create intervals anywhere, even under nodes that can be posted.

A hierarchy node, which represents a value interval, is an end node and cannot have childnodes.

9. Repeat this step until the final hierarchy structure has been defined.

A hierarchy should not be unnecessarily large. It should not contain more than 50,000 -100,000 leaves. If your hierarchy is larger, you should insert a level that is used as anavigation attribute or preferably as a separate characteristic in the dimension table.

10. You can also make various settings that change the hierarchy display in Reporting. See alsoReporting-relevant Hierarchy Settings [Seite 187].



11. To display, change, or delete nodes or leaves from the hierarchy, place the cursor on thenode/leaf to be deleted, and choose (GLW�→�&KDQJH��'LVSOD\��'HOHWH�1RGHV.

��

��

� ��

� �� !

� �� #"

$%��'&��

6DYLQJ�DQG�$FWLYDWLQJ�+LHUDUFKLHV

12. Save the hierarchy.

13. With the right mouse button, choose $FWLYDWH�KLHUDUFK\. See also Activating Hierarchies [Seite191]

5HVXOW

The hierarchy is activated (the tree symbol is now green) and can be used in aggregates andreporting.



2SWLRQV�IRU�WKH�&RPELQDWLRQ�RI�1RGHV�DQG�/HDYHV

)XQFWLRQV

With the exception of intervals, you can combine different node types as you like. No further nodesmay be inserted beneath intervals.

A node may only occur more than once in a hierarchy under the following circumstances:

• The nodes that occur more than once with the same technical key are leaves (nodes withoutchildren that can be posted) and do not hang under the same higher-level node.

• With the exception of one node (the original node), all nodes having the same technical key arelink nodes [Seite 180].

• The hierarchy structure is time-dependent and the time intervals of none of the nodes that occurmore than once with the same technical key overlap.



5HSRUWLQJ�UHOHYDQW�+LHUDUFK\�6HWWLQJV

8VH

You can influence how hierarchies are displayed in reporting by using the following settings.

)XQFWLRQV

Go to hierarchy maintenance in the Administrator Workbench.

/HYHO�0DLQWHQDQFH

A level includes all nodes that are on the same drilldown level in a hierarchy.

With the /HYHO�0DLQWHQDQFH pushbutton you can determine names for the different levels of ahierarchy that are used in the context menu when navigating in the query.

You rename the level of a hierarchy with the names FRQWLQHQW��FRXQWU\ and UHJLRQ. If youuse the function ([SDQG�+LHUDUFKLHV in the context menu of BEx when navigating in thequery, then you have the following options:

([SDQG�E\

• Continent

• Country

• Region

are offered to you.

If you do not maintain any names for the levels then the non-mnemonic names OHYHO��OHYHO��...�OHYHO�Q are used.

+LHUDUFK\�$WWULEXWHV

With the +LHUDUFK\�$WWULEXWHV pushbutton you can set the parameters for displaying the hierarchy in thequery.

• Do not display leaves for inner nodes in the query

There are different ways to display an inner node that can be posted in the query, that is anode that can be posted and has lower-level children. Either a leaf is created for each innernode that is inserted directly below the inner node or these additional leaves are notdisplayed.

• Display behavior for leaves of inner nodes can be changed

You can set whether or not this display behavior can be changed in the query at runtime (seeabove). You have the following options:

’ ’ : Display behavior can QRW be changed in the query’X’: Display behavior can be changed in the query

• Suppressing the XQDVVLJQHG�node

You can make the setting here for suppressing the node, which contains all the values thatcan be posted to and do not appear in the hierarchy.

• Root�sum position

You can determine here

− whether in the query the root, and thereby the totals item for the hierarchy, aredisplayed at the end of the query, and whether the leaves appear at the top.

− whether the root, and thereby the totals item for the hierarchy, are displayed at thestart of the query, and whether the leaves appear at the bottom.



• Start Drilldown Level

You can determine here to what level the hierarchy in the query should be drilled down, whenit is first called up. This setting can be changed in the Query Builder.



(GLWLQJ�+LHUDUFKLHV

3UHUHTXLVLWHV

There is already a hierarchy for the InfoObject in BW.

3URFHGXUH

1. Select the InfoObject tree under 0RGHOLQJ in the $GPLQLVWUDWRU�:RUNEHQFK. You can also go to thestandard toolbar in the hierarchy maintenance directly with (GLW�+LHUDUFKLHV.

$FFHVV�ZLWK�WKH�,QIR2EMHFW�WUHH�

2. If you have assigned a characteristic to an InfoObject catalog, then select the relevant InfoObjectcatalog for an InfoArea.

If the characteristic does not belong to an InfoObject catalog, select the 1RW�$VVLJQHG�1RGHVInfoArea�and the 1RW�$VVLJQHG�&KDUDFWHULVWLFV InfoObject catalog.

3. Select the characteristic hierarchy that you want to edit, and choose the functions carried out inthe table with the right mouse button.


'LVSOD\LQJ�WKH�KLHUDUFK\

&RS\LQJ�WKH�KLHUDUFK\ Enter a new technical name and at least oneshort, medium, and long description. Thehierarchy is copied and can now be modified.

See: Copying Hierarchies [Seite 190]

&KDQJLQJ�WKH�KLHUDUFK\ You come to the screen 0DLQWDLQ�KLHUDUFK\ andcan change the hierarchy.

See: Creating Hierarchies [Seite 184]

'HOHWLQJ�WKH�KLHUDUFK\

$FWLYDWLQJ�WKH�KLHUDUFK\ See: Activating Hierarchies [Seite 191]

You can display the detailed information on the hierarchy, such as hierarchy name,description, object version, person responsible, last changed by, and changed on (date)/at(time), by choosing *RWR�→�+HDGHU�LQIRUPDWLRQ in hierarchy maintenance.

$FFHVV�ZLWK�WKH�+LHUDUFK\�SXVKEXWWRQ�

2. You get a list of all the hierarchies in the system. You can limit this list by selecting a basiccharacteristic. You can display the details about the hierarchy, such as the hierarchy name,description, object version, person responsible, last person to change and date and time ofchange by choosing 'HWDLOV.

3. All the functions listed in the above table can be used. Select the hierarchy to be edited. You go tothe hierarchy maintenance with &KDQJH�+LHUDUFK\. You can also create, delete, copy and activatethe hierarchies directly.



&RS\LQJ�+LHUDUFKLHV

3UHUHTXLVLWHV

You have to have already loaded a hierarchy, or created a hierarchy in BW.

You may have specified that the hierarchy is version and/or time-dependent in the InfoObjectcharacter maintenance [Seite 33].

3URFHGXUH

1. In the Administrator Workbench under 0RGHOLQJ choose ,QIR2EMHFW�7UHH → <RXU�,QIR2EMHFW →ULJKW�PRXVH�NH\ → &RS\�KLHUDUFK\�

2. Specify the hierarchy name and description.

3. If the hierarchy is version or time-dependent, then specify a hierarchy version or the validity date.

5HVXOW

You have created a copied version of the hierarchy, which is now ready for editing.



$FWLYDWLQJ�+LHUDUFKLHV

3UHUHTXLVLWHV

You have already loaded a hierarchy, or created a hierarchy in BW. The icon in the AdministratorWorkbench shows whether there is an inactive hierarchy or an active version available for anInfoObject. There may also be a modified version.

3URFHGXUH

1. Select the InfoObject tree under 0RGHOLQJ in the $GPLQLVWUDWRU�:RUNEHQFK.

2. If you have assigned the hierarchy characteristic to an Info Object catalog, select thecorresponding InfoObject catalog for an InfoArea.

If the hierarchy characteristic does not belong to an InfoObject catalog, select the 1RW$VVLJQHG�1RGHV�InfoArea�and the 1RW�$VVLJQHG�&KDUDFWHULVWLFV InfoObject catalog.

3. Select the characteristic hierarchy that you want to activate and, using the right mouse button,select $FWLYDWH�+LHUDUFK\�

The hierarchy is now activated. If this hierarchy already exists in an aggregate for anInfoCube, a dialog box appears which lets you activate it directly by deleting the aggregate ormarking the hierarchy for activation.

4. If the hierarchy was only marked for activation, you must execute the change run for thishierarchy. This updates all the aggregates contained in the hierarchy and activates the hierarchy.

5HVXOW

The hierarchy is activated (indicated by the green tree). The hierarchy data is written to thecorresponding OLAP tables and are now available for Reporting and for use in new aggregates.

6HH�DOVR�




1RGH�$WWULEXWHV

'HILQLWLRQ

A node attribute is an attribute on the node level. This means that each node of the hierarchy has thisattribute. Attributes that are assigned to the entire hierarchy are called hierarchy attributes.

6HH�DOVR�

Hierarchy Attributes [Seite 187]

6WUXFWXUH

If a node attribute is released for a characteristic in the InfoObject maintenance, the attribute can beused for all the nodes in all hierarchies for the characteristic.

SAP also delivers node attributes. The following node attributes are available:

• Version dependency [Seite 193]

• Time dependency [Seite 195]

• Intervals [Seite 198]

• Reversing the sign [Seite 199]



+LHUDUFK\�9HUVLRQV

5HTXLUHPHQWV

You have specified�in the InfoObject characteristic maintenance [Seite 33], that the correspondinghierarchy characteristic is KLHUDUFK\�YHUVLRQ�GHSHQGHQW.

8VH

Characteristic hierarchies can be used in different hierarchy versions.

Within the context of an area restructuring of your business, you can create differentversions of hierarchies for the characteristic 0DLQ�5HJLRQ��and compare them with oneanother in a query.

+LHUDUFK\�YHUVLRQ�3/$1 +LHUDUFK\�YHUVLRQ�$&78$/

0DLQ�$UHD�1257+ 0DLQ�$UHD�1257+

Region 1 Region 2

Region 2

0DLQ�$UHD�6287+ 0DLQ�$UHD�6287+

Region 3 Region 1

Region 4 Region 3

Region 4

,QWHJUDWLRQ

If there are different hierarchy versions in the source system, you can map these into BW. You canalso generate different versions for one and the same hierarchy from the source system.

)XQFWLRQV

You can create different hierarchy versions under the same technical name. You then compare thedifferent hierarchy versions in reporting.

You want to generate a plan version of the hierarchy ‘xyz’ to be able to make a plan/actualcomparison of both hierarchies in reporting. To do this, create a hierarchy version ‘plan’,and assign it to the copied hierarchy.

In reporting, you display the data with either the plan or actual version of the hierarchy Aplan/actual comparison is also possible across different columns. Variables can be usedto set parameters for the different versions.



0DLQWDLQLQJ�+LHUDUFK\�9HUVLRQV

3URFHGXUH

1. Select 7RROV → 0DLQWDLQ�+LHUDUFK\�9HUVLRQV in the main menu in the Administrator Workbench.

2. Select existing hierarchy versions and choose ([HFXWH�

3. You can now create a new hierarchy version or change existing versions.


5HVXOW

You have created a new hierarchy version including descriptive text or changed an existing version.This version can be used upon creating a hierarchy with versions.

The text for a hierarchy version does not depend on the InfoObject, that is if version 001 has text"Plan", each hierarchy version 001 has text "Plan", irrelevant of the basic characteristic the hierarchywas defined for.



7LPH�GHSHQGHQW�+LHUDUFKLHV

8VH

In the InfoObject characteristic maintenance you determine whether or not a hierarchy may be time-dependent. You define either that the entire hierarchy should be time-dependent or that the hierarchystructure (each individual node relationship) should be time-dependent.

If you only need the hierarchy each month, you should create the entire hierarchy as time-dependent.However, if you only need the current view on the hierarchy, you should not create it as time-dependent. Of course you can activate it as often as you like.

(QWLUH�+LHUDUFK\�7LPH�GHSHQGHQW

If an entire hierarchy is time-dependent, this means that there are versions of the hierarchy that arevalid for one time interval each. The system automatically uses the current valid version in this case.

You can make the hierarchy time-dependent, within the context of an area restructuring ofyour business, for the characteristic 0DLQ�5HJLRQ, in order to compare them with oneanother at different times in a query.

+LHUDUFK\�� +LHUDUFK\��

0DLQ�$UHD�1257+ 0DLQ�$UHD�1257+

Region 1 Region 2

Region 2

0DLQ�$UHD�6287+ 0DLQ�$UHD�6287+

Region 3 Region 1

Region 4 Region 3

Region 4

The hierarchy that is valid currently is uniquely identified by the technical name and the IURP�±�WR�GDWH.The time-dependent hierarchies that have been created, are displayed, along with the current µ7R�GDWH¶in the InfoObject tree under the InfoObject belonging to it. When a query is executed, the validhierarchy is found using the query key date.

You can also work in the individual columns of a report structure with fixed date values, for example to.Compare the "Main area North" in the hierarchy of 31.05.2000 with "Main area North" in the hierarchyof 01.06.2000 (simulation).

7LPH�GHSHQGHQW�+LHUDUFK\�6WUXFWXUHV

If the hierarchy structure is time-dependent, the hierarchy is set up on the current key date or on thekey date defined in the query.

You can assign an employee to different cost centers at different times within the contextof a restructuring.

In the hierarchy display (+LHUDUFK\�→�&RQWH[W�0HQX��ULJKW�PRXVH�EXWWRQ��→�'LVSOD\�KLHUDUFKLHV��everynode and every leaf is marked with a date symbol. All hierarchy nodes are displayed. Nodes that arehung according to time-dependency in different places in the structure can, therefore, appear morethan once. Double-clicking on the nodes displays the validity period of the node relationship.



By double-clicking on the node in this example, you would be able to see that ‘Jones’ is assigned tothe region USA from 01.01.99 to 31.05.99, and to the region Puerto Rico from 01.06.99 to 31.12.99.

��

��

� ��

�� !�"�

#$�� %&��'

(*)�#

+��,��'

-. "�"/��10

2�,��10 �43. �%��

+,��' 5,6,7�5�8�7!6�9�9,9;:�<�6�7!6�=,7"6&9�9�9

5�6�7�5�6�7"6>9�9�9;:�<�6�7�5�?�7"6>9,9�9

6HH�DOVR�

Maintaining Hierarchy Versions [Seite 194]



/RDGLQJ�7LPH�GHSHQGHQW�+LHUDUFKLHV

(QWLUH�+LHUDUFK\�7LPH�GHSHQGHQW

3UHUHTXLVLWHV

When loading time-dependent hierarchies, you proceed in the same way as for Loading NormalHierarchies [Seite 181]. Bear in mind the following special features when you are loading time-dependent hierarchies.

3URFHVV

When you load time-dependent hierarchies and hierarchies with the same technical name alreadyexist in the BW system, the new hierarchy dominates. This means that the time intervals of theexisting hierarchies are adjusted if the open hierarchy interval of the old hierarchy is not completelycovered.

• If the time interval of the new hierarchy overlaps with an old hierarchy, then the time interval of theold hierarchy is made shorter so that the time intervals run directly onto one another.

Exception: If the time interval of the new hierarchy is contained in the time interval of the oldhierarchy so that the "from" date of the new hierarchy is larger than the "from" date of the oldhierarchy and the "to" date of the new hierarchy is smaller than the "to" date of the oldhierarchy, you cannot load the new hierarchy. You first have to change the time interval for theold or new hierarchy, so that the interval for the new hierarchy is not contained in the intervalfor the existing hierarchy or the condition just described is not satisfied.

• If one or more time intervals of existing hierarchies are contained in the interval of the newhierarchy, then these hierarchies are deleted.

$SSOLFDWLRQ

If you do not wish to determine in advance, how long a hierarchy is valid for, set the current day as the)URP�WR�GDWH and the maximum date as 31.12.9999. Do the same for other hierarchies that you aregoing to load subsequently.

When loading each hierarchy, the system automatically sets the 'DWH�WR for the (up to now) mostcurrent hierarchy to the day before the 'DWH�IURP for the new hierarchy.

+LHUDUFK\�6WUXFWXUH�7LPH�GHSHQGHQW

The time intervals to be loaded are selected in the Scheduler.

Not all extractors support the loading of time-dependent structures. However it is supported forexample by 0CUST_SALES.



+LHUDUFK\�,QWHUYDOV

8VH

You have the option of hanging characteristics in the form of intervals under a hierarchy node. Insteadof hanging the cost types for 0DWHULDO�FRVWV individually under the node 0DWHULDO�FRVWV in a cost typehierarchy, you can specify the cost types in the form &RVW�W\SH��WR��.

You can create intervals for characteristic values, for which no master data yet exists, and save havingto expand the hierarchy every time new master data is added. New characteristic values are insertedautomatically.

InfoObject 0HIER_NODE or the basic characteristic of the hierarchy therefore must be specified for anode of type ,QWHUYDO. This node represents the interval. The entries for the interval are nodes that canbe updated and are entered in fields LEAFFROM and LEAFTO.

Each interval has a description that is stored as text for the interval node. The interval is triggered inthe query, that is all the nodes lying in the interval that have data in the fact table are displayed asleaves.

You create interval &RVW�W\SH��WR�� under node 0DWHULDO�FRVWV for characteristic&RVW�W\SH. Master data for this characteristic is available in BW, but only for the values��.

In the query only values �� for which there is transaction data are displayed undernode 0DWHULDO�FRVWV in the cost type hierarchy.

In the course of time some cost types will be added to the material costs and you createmaster data for the values ��. As soon as transaction data has been loaded, thenew cost types can be displayed automatically in the query, without you having to expandthe hierarchy manually.



5HYHUVLQJ�WKH�6LJQ

8VH

The display behavior of nodes in a query can be changed by reversing the sign. You can make thissetting in InfoObject maintenance. If you do activate the reverse signs +/- function for hierarchies, youare able to specify for every hierarchy node that is displayed in the query, whether or not you want toreverse the +/- sign for the transaction data booked to each of the nodes.

This function is used especially by SAP SEM (Strategic Enterprise Management).

Costs are stored as negative values in the database. To display these values with apositive sign in reporting, you can switch on sign reversal.



+LHUDUFK\�0RGHOLQJ�2SWLRQV

8VH

There are various ways to map hierarchies in SAP BW:

• As "normal" hierarchies (as already described)

• As hierarchies in the dimension

There is a hierarchy in the dimension of an InfoCube for example for the time dimension:InfoObjects 0CALDAY, 0CALMONTH and 0CALYEAR already create a hierarchy based ontheir definition. They are drilled down as hierarchy levels in the query. All the drill-downoptions of the query can be used, but the hierarchy can only be expanded level-by-level.

• Hierarchy in the attributes

There is a hierarchy in the attributes of an InfoCube for example for InfoObjects 0MATERIAL,0MATL_GROUP, 0MATL_TYPE and 0IND_SECTOR. These already form a hierarchy basedon their definition. The attributes must be defined as navigation attributes.

)XQFWLRQV

'LIIHUHQFHV�EHWZHHQ�WKH�GLIIHUHQW�KLHUDUFKLHV�

+LHUDUFK\ +LHUDUFK\�LQ�'LPHQVLRQ +LHUDUFK\�LQ�$WWULEXWHV

• ’As posted’ view is notpossible

• Different views (e.g.version, key date) on thedata possible

’As posted’ view is possible • ’As posted’ view is notpossible

• Different views on the datanot possible. Only view onkey date

Hierarchy for all InfoCubes Hierarchy only for oneInfoCube

Hierarchy structure modeled inthe master data and thereforefor all InfoCubes

Hierarchy can be changed Reorganization not possiblewithout reloading the InfoCube

Reorganization possible byselecting additional attributes

Fast analyses only possiblewith aggregates

Fast analyses possible Fast analyses only possiblewith aggregates

Drill-down path defined by thestructure

Drill-down path not defined bythe structure. Levels cantherefore be skipped.

Drill-down path not defined bythe structure. Levels cantherefore be skipped.

Non-leveled hierarchiespossible

Different attributes ofdimension correspond to thehierarchy levels, i.e. onlyleveled hierarchies possible

Different attributes ofdimension correspond to thehierarchy levels, i.e. onlyleveled hierarchies possible

Duplicate leaves alwaysdisplayed

Duplicate leaves only possiblein ’As posted’ view

Duplicate leaves not possible



8SGDWH�5XOHV

'HILQLWLRQ

The update rules specify how the data (key figures, time characteristics, characteristics) is updated inthe InfoProvider from the communication structure of an InfoSource. You are therefore connecting anInfoSource with an InfoProvider.

Data Providing

,QIR3URYLGHU

%XVLQHVV�,QIRUPDWLRQ

:DUHKRXVH�6HUYHU6WDJLQJ�(QJLQH

Source System 1 Source System 2

��

8SGDWH�5XOHV8SGDWH�5XOHV

,QIR6RXUFH

Communications StructureCommunications Structure

Extract StructureExtract Structure Extract StructureExtract Structure'DWD6RXUFH

'DWD6RXUFH

(Copy)Transfer StructureTransfer Structure

Transfer StructureTransfer Structure Transfer StructureTransfer Structure

Transfer StructureTransfer Structure

8VH

An update rule must be specified for each key figure and the corresponding characteristics of theInfoCube. For an ODS object it must be specified for the data and key fields, and for an InfoObject itmust be specified for the attribute and key fields.

There are the following types of updating:

1. No update

2. Addition, minimum or maximum

3. Overwriting (with ODS objects only)

A data target can be supplied with data from several InfoSources. A record of update rules must bemaintained for each of these InfoSources, describing how the data is written from the communicationstructure belonging to the InfoSource into the data target.

The InfoObjects of the communication structure belonging to the InfoSource are described in theupdate as source InfoObjects (meaning source key figure or source characteristic). The InfoObjects forthe InfoCube, on the other hand, are described as target InfoObjects (meaning target key figure ortarget characteristic). Similarly, the InfoObjects of an ODS object/InfoObject are called targetInfoObjects (therefore, target data field or target key field).

6WUXFWXUH

There is an update rule for each key figure of the InfoSource. This is put together from the rule for thekey figure itself and the current rules for characteristics, time characteristics, and units assigned to it.



8SGDWH�2SWLRQV

8VH

�� (DFK�FKDUDFWHULVWLF�RI�WKH�,QIR3URYLGHU�DOVR�H[LVWV�LQ�WKH�,QIR6RXUFH�

Data records 1 and 2 of the InfoSource have the same characteristic values (plant,storage location and month). The key figures of these two data records are transferredinto the Cube according to the relevant update rule. This example uses adding.

�� $�FKDUDFWHULVWLF�RI�WKH�,QIR3URYLGHU�GRHV�QRW�DSSHDU�LQ�WKH�,QIR6RXUFH�

If this situation should arise, you have two options open to you:

a. Assign a suitable characteristic for the InfoSource with the same type (characteristic, timecharacteristic or unit characteristic) to the characteristic for the InfoCube.



The characteristic /RFDWLRQ in data record 1 of the InfoSource is assigned to thecharacteristic of the same type 6WRUDJH�/RFDWLRQ in the InfoCube.

b. Write an update routine that calculates the corresponding characteristic of the InfoCube.

c. Enter a value (constant) that you want the characteristic of the InfoCube to have.

d. Fill the characteristic by reading the master data for another characteristic of thecommunication structure.

e. Do not enter anything for the characteristic and leave it blank.

�� $�FKDUDFWHULVWLF�H[LVWV�LQ�WKH�,QIR6RXUFH��EXW�GRHV�QRW�DSSHDU�LQ�WKH�,QIR3URYLGHU�

In this case, the corresponding characteristic is not updated.



8SGDWH�3URFHVV

3XUSRVH

In order to better understand the update rules maintenance, make yourself familiar with the underlyingupdate mechanism.

3URFHVV

You load a request into the InfoCube (or into any other InfoProvider). For each existing key figureloaded into the InfoCube, the update mechanism calculates the characteristic values and puts theresults into an intermediate buffer.

If more than one key figure is updated, each individual entry is then processed for a key figure,meaning that the value of the key figure is calculated initially and then all values of the characteristics.The values of other key figures are initially set to zero. All entries are thus processed specific to keyfigures one after another.

Entries that are identical in characteristic values, are aggregated for an entry in the buffer table. Withthe aid of the update routines, you do have the option, however, of using the function Splitting KeyFigures [Seite 215] and, thereby, generating more than one entry from a single entry.

The processed entries are updated in the data target by the internal table.

Step ...

Cust. No. Material no. Salesperson Calendar Day Profit Number

1001 3210 5001 19900412 345.00

5.00

1001 3210 5002 19900412 207.00

3.00

1002 3210 5004 19900415 483.00

7.00

1001 3210 19900412 345.00 0.00

1001 3210 19900412 345.00 5.00

1001 3210 19900412 552.00 8.00

1002 3210 19900415 483.00 7.00

Communication Structure

Internal Buffer Table

InfoCube

Step 1

Step 2

Step 3

Step 4

In the example graphic above, three records from the communication structure areupdated that are processed one after another. The characteristic VDOHV�SHUVRQ does notexist in the InfoCube and is, therefore, not updated.

The characteristic values for the first key figure (profit) of the first record is calculatedinitially. The key figure value of the second key figure (number) of the first record is firstset to zero.

In the next step, the characteristic values are calculated for the second key figure of thefirst record. Since the characteristic values for both key figures concur, they areaggregated.



The other records are processed in this way, one after the other. Since the characteristicVDOHV�SHUVRQ is not updated, the characteristic values for both key figures are the same inthe first two records. These are consequently aggregated up to one record.



&UHDWLQJ�8SGDWH�5XOHV�IRU�'DWD�7DUJHWV

3UHUHTXLVLWHV

In order to be able to maintain update rules, choose 0RGHOLQJ�→�,QIR3URYLGHU→�<RXU�,QIR3URYLGHU→&RQWH[W�0HQX��ULJKW�PRXVH�EXWWRQ�→ &UHDWH�8SGDWH�5XOHV in the Administrator Workbench.

3URFHGXUH

1. Select a data source. Choose between InfoSources, ODS objects and InfoCubes.

2. Choose 1H[W�VFUHHQ�

A default proposal for the update rule is generated from the InfoCube.

Alternatively, transfer an update rule from Business Content.

3. Select a key figure or a data field by double-clicking on it, or by choosing 'HWDLO.

4. Define the update type [Seite 208] for the displayed key figure or data field.

5. Select an update method [Seite 210].

6. Also select an update method for the characteristics and time reference or for the key fields.

7. Select the next key figure by double-clicking, or by selecting 'HWDLO� and repeat steps 4 to 6.

8. If you want to save the rules first, without an update taking place, choose 6DYH�

If you want the update to take place, select $FWLYDWH��An InfoProvider can only contain datawith an active update rule.

Check the status of the update rules.

It must be set to DFWLYH in order for the data records for your InfoSource to be updated. Ifthis is not the case, activate the rules.



&UHDWLQJ�D�6WDUW�5RXWLQH

8VH

You have the option of creating a start routine that is then carried out per data packet at the beginningof the update. You can, for example, use the start routine to generate internal tables that you can thenuse for key figure and characteristic routines.

In the update you want to credit a certain percentage of the sales turnover to the individualsalespersons of a sales office. For example, salesperson A 20% of the turnover of salesoffice A, salesperson B 30&, salesperson C 50%. The salespersons and their sales officesare listed in a master data table. The uploaded data contains the sales office and salesfigures as characteristics. To be able to assign the salespersons to the sales offices, youhave to read the data from the master data table on demand. If the master data table isnot comprehensive enough, then you can generate an internal table in the start routinethat contains the master data and that can access the subsequent key figure andcharacteristic routines.

You also have the option of changing data (for example, modifying or deleting it), by changing thetable DATA_PACKAGE with the help of ABAP code.

3URFHGXUH

1. Select $GPLQLVWUDWRU�:RUNEHQFK�→�,QIR3URYLGHU.

2. Select the required InfoProvider and choose &UHDWH�8SGDWH�5XOHV�or select the desired updaterules and choose &KDQJH�8SGDWH�5XOHV.

3. Enter the name of the InfoSource, whose update rules you wish to maintain. Choose 1H[W�6FUHHQ�

If the corresponding update rules have already been maintained, these will be displayed.

If you create new update rules, the system makes suggestions here.

4. Choose the pushbutton &UHDWH�6WDUW�5RXWLQH. You automatically get to the ABAP Editor forcreating the start routine.

6HH�DOVR�

Update Routines [Seite 219]



8SGDWH�7\SHV

8VH

With the update type, you control whether a key figure/data field is updated in the InfoProvider.

)XQFWLRQV

)RU�,QIR&XEHV�DQG�,QIR2EMHFWV�

• Depending on the aggregation type you entered in the Key Figure Maintenance [Seite 69] for thiskey figure, you are given the options $GGLWLRQ or 0D[LPXP or 0LQLPXP. If you choose one ofthese options, new values are updated in the InfoProvider.

The DJJUHJDWLRQ�W\SH (DGGLWLRQ��PLQLPXP��PD[LPXP) determines how key figuresare updated where primary keys are the same. Thus either the total, the minimum or themaximum for these values is formed for new values.

If you entered one of these aggregation types in the key figure definition, it is transferredfor the update. Otherwise, the aggregation type addition is automatically selected.

• If you choose QR�XSGDWH, the key figures are not updated in the InfoProvider, meaning that nodata records are written in the InfoProvider with the first data transfer, or that data records thatalready exist, will remain in place with subsequent transfers.

)RU�2'6�2EMHFWV�

1. Depending on the type of data and DataSource, you have the option to $GG or 2YHUZULWH� If youchoose one of these options, new values are updated in the ODS object.

For numerical data fields, you are given a proposal for the update type through thecharacteristic 0RECORDMODE. If only the after-image is delivered, the system proposes2YHUZULWH. However, it could make sense to change this: For example, with the meter datafield “# Changes”, which is filled with a constant 1 but still has to be updated through addition,although only an after-image is delivered.

Characteristic 0RECORDMODE is used to pass indicators of the DataSource (from SAPsystems) to the update.

You do not need characteristic 0RECORDMODE as long as you do not load deltarequests in the ODS object or only from file DataSources.

a. Adding:

Addition is not supported with the data types CHAR, DAT, TIMS, CUKY and UNIT. To beable to use the addition function, make sure the DataSource is compatible with an additivedelta.

b. Overwriting:

Whether adding or overwriting is supported or not, is determined by the delta-compatibilityof the DataSource.

In this example, the order quantity changes after it has been loaded into BW. With thesecond loading process the data is overwritten since it has the same primary key.

)LUVW�/RDGLQJ�3URFHVV

'RFXPHQW�1R�

'RFXPHQW,WHP

2UGHU�4XDQWLW\ 8QLW�RI0HDVXUH

100001 10 200 Pieces

100001 20 150 Pieces



100002 10 250 Kg

6HFRQG�/RDG�3URFHVV

'RFXPHQW�1R�

'RFXPHQW,WHP

2UGHU�4XDQWLW\ 8QLW�RI0HDVXUH

100001 10 180 Pieces

100001 20 165 Pieces

The system keeps to the time sequence of the data packets and requests when youupdate data. You have to decide the logical order of the update yourself. Meaning, forexample, orders must be requested before deliveries, otherwise the wrong results myappear when you overwrite the data.

c. If you choose QR�XSGDWH, the data fields are not updated in the ODS object, meaning that nodata records are written in the ODS object with the first data transfer, or that data records thatalready exist will remain in place with subsequent transfers.



8SGDWH�0HWKRGV

8VH

You use the calculation method to control whether and how a characteristic/key figure or a datafield/key field should be updated in the data target.

)XQFWLRQV

There are several options:

• 6RXUFH�,QIR2EMHFW: The field is filled directly from the selected source InfoObject of thecommunications structure.

If the system does not make any suggestions for a VRXUFH�,QIR2EMHFW, you can assign a VRXUFH,QIR2EMHFW�of the same type (amount, number, integer, quantity, float, time) or create a URXWLQH.

If you assign a source InfoObject RI�WKH�VDPH�W\SH, that has a different currency to the targetInfoObject, then you must translate the source currency using a currency translation in thetarget currency [Seite 225].

For source-time characteristics: The system offers automatic time conversion [Seite 212].

• &RQVWDQW: The field is not filled with the communication structure. It is filled directly with thespecified value.

• )RUPXOD: The key figure/data field/attribute is updated with a value determined with a formula[Seite 217].

• 0DVWHU�GDWD�DWWULEXWH�RI: The data field/attribute is updated by reading the master data table ofan InfoObject contained in the communications structure and containing the corresponding datafield/attribute as attribute.

In an InfoCube there is a characteristic (for example, FM area) that does not appear as acharacteristic in the communication structure. In the communication structure, however,there is a characteristic (for example, cost center) that has the characteristic )0�DUHD asan attribute.

You can read the attribute )0�DUHD from the master data on demand, and thereby fill thecharacteristic )0�DUHD in the InfoCube.

If the attribute is time-dependent, you also have to define when it should be read: at thecurrent date (sy-datum), at the beginning or end of a period (defined with a time characteristicof the InfoSource), or at a constant date that you enter directly. V\�GDWXP is used as a default.

• 5RXWLQH: The field is filled by an update routine [Seite 221] that you have written.

The system provides you with a selection option which lets you decide whether the routineshould be valid for all of the key figures /data field / attributes belonging to this characteristic oronly for the key figure / data field / attribute displayed.

Update rules generally only have one return value. If you select UHWXUQ�WDEOH, thecorresponding key figure routine then no longer has a return value, but a return table. You canthen generate as many key figures/data field values as you like from one data record. [Seite215]

With ODS objects/InfoObjects: You cannot use the return code in the routine for datafields that are updated by being overwritten. If you do not want to update specific records,you can delete these from the start routine.

If you generate different rules for different key figures/data fields for the same characteristic[Seite 216], a separate data record can be created from a data record of the InfoSource foreach key figure.



For InfoCubes: If you choose a routine, you can then also choose the indicator URXWLQH�ZLWKXQLW�FDOFXODWLRQ. In the routine you then also get the return parameter ‘UNIT’. In this respectyou can, for example, store the required unit of the key figure, such as ‘DEM’ or ‘ST’. You canuse this option, for example, to calculate the unit KG present in the communication structure intons in the InfoCube

If you fill the target key figure from an update routine for update rules, the currency translationhas to be carried out using the update routine. This means that an automatic calculation is notavailable.

• ,QLWLDO�YDOXH: The field is not filled. It remains empty.



$XWRPDWLF�7LPH�&RQYHUVLRQ

8VH

You can use automatic time conversion to update source time characteristics of the InfoSource intotarget time characteristics of the InfoCube in the update rule maintenance. This function does notapply to ODS objects, since time characteristics are treated like normal data fields.

3UHUHTXLVLWHV

You have already determined the rules for the corresponding key figure and the characteristics thatbelong to it in the update rule maintenance, and are in the time reference maintenance.

)XQFWLRQV

The system only presents you with the time characteristics, for which an automatic time conversionroutine exists.

For the target time characteristic &DOHQGDU�0RQWK� source time characteristic &DOHQGDU'D\ is presented. This means that a time conversion routine exists, that converts thesource time characteristic &DOHQGDU�'D\ into the target time characteristic CDOHQGDU0RQWK.



7LPH�'LVWULEXWLRQ

8VH

You can update time characteristics with time distribution when you update InfoCubes. All the keyfigures that can be added are distributed to the corresponding smaller time units.

You can choose time distribution if the InfoSource contains a time characteristic (such as0CALMONTH) that is more approximate than a time characteristic of the InfoCube (suchas 0CALWEEK):

For example, the calendar month 07.2001 would be divided into the weeks 26.2001,27.2001, 28.2001, 29.2001, 30.2001 and 31.2001. Each key figure that can be addedreceives 1/31 of the original value for week 200126, 7/31 for each of weeks 27,28,29 and30, and exactly 2/31 of it for week 31.

The example makes more sense if you compare it to the calendar:

)XQFWLRQV

You can define whether you want the time distribution to be based on the normal calendar or on acertain factory calendar.

Within an InfoCube you may only use one and the same characteristic and one calendar for timedistribution for different time characteristics. Otherwise it would not be clear how the different resultsare to be combined.

For example if 0CALQUARTER is used for distribution on 0CALWEEK and 0CALYEARfor distribution on 0CALMONTH, and 0CALQUARTER contains the value ’1.2000’ and0CALYEAR ’1999’, it would not be clear how the values for 0CALWEEK (01.2000,02.2000....) should be merged with the values for 0CALMONTH (01.1999, 02.1999...).Only 0CALQUARTER or 0CALMONTH can be chosen.

This function is not implemented for ODS objects.



6SOLWWLQJ�.H\�)LJXUH�9DOXHV

8VH

You can create several update rules for each key figure in the InfoCube/data field.

In an enterprise, an employee in Sales makes a particular sales revenue. In the InfoCube,90% of this sales revenue is to be assigned to the employee (routine 1), 10% to the directsuperiors of the employee (routine 2).

You can split the key figure values in two possible ways:

��&RS\�5XOHV

Create an update rule with the routine 1 (90% of the sales revenue are assigned tothe employee). Copy the update rule. Maintain the routine 2 (10& of the salesrevenue are assigned to the direct superiors of the employee) in the copied rule, andmake the necessary changes in the tabstrip of the characteristic calculation.

��5RXWLQH�ZLWK�5HWXUQ�7DEOH

Update rules generally only have one return value. However, you can create aroutine in the tabstrip key figure calculation, by choosing 5HWXUQ�WDEOH� Thecorresponding key figure routine then no longer has a return value, but a return table.You can then generate as many key figure values as you like from one data record.

In the routine editor, you will find the calculated characteristic values in the structureICUBE_VALUES. Change these values accordingly (in the above example:Employee), fill the field for the relevant key figure (in the above example: Salesrevenue), and use this to fill the return table RESULT_TABLE.



'LIIHUHQW�5XOHV�IRU�'LIIHUHQW�.H\�)LJXUHV�RI�D�&KDUDFWHULVWLFThere are three date characteristics in the InfoSource:

• Order date

• Delivery date

• Invoice date

The InfoProvider only contains a general date characteristic that should be filled from the different datecharacteristics of the InfoSource, depending on the key figure/data field.

Different rules can be created for the update rule for the date characteristic. Depending on the keyfigure/data field, the rule updates the order date, the delivery date, or the invoice date in theInfoProvider.

�� !�#"$�%��$��

��

& '��(*)

(,+

& �� -� '��!��

& �� -� ��.�/��0�1�

& �� -� � � �� !�2"��3��$��

��

4�5 �� & '��(�+

& '��(�6

(,6(�)

(,+ (,6(*)



7RROER[�DQG�)RUPXOD�(GLWRU

8VH

The Formula Editor with the Toolbox helps you maintain the transfer structure of an InfoSource andassists you with the update rules for a data target.

It simplifies the creation of formulas. The Formula Editor is an SAP Basis function and was enhancedin BW. The Toolbox still delivers predefined functions for converting fields/InfoObjects.

Do not use formulas for RemoteCubes, because inversion is not allowed. In this case youhave to use routines.

)XQFWLRQV

Together with the Toolbox, the Formula Editor simplifies the creation of formulas from a context-sensitive interface without ABAP coding.

The Toolbox provides you with the following functions:

• ,I: If the condition is satisfied, performs a calculation. If the condition is not satisfied, there is analternative calculation (e.g. standard value).

Parameter: ,I��FRQG!��DOW�!��DOW�!��

<cond>... Condition<alt1>... Calculation, if condition = TRUE<alt2>... Calculation, if condition = FALSE

• 'DWH�FRQYHUVLRQ: This function converts any date format into the SAP date format. Two types ofdate can be converted:

1. Day, month and year have a fixed format, i.e. they are always at the same position in a string(e.g. yyyy/dd/mm).

2. Day, month and year have different formats. In this case the day, month and year must have afixed order (e.g. 1.1.2001 and 31.12.2001).

Result: The date is converted to format yyyymmdd.

Parameter: 'DWHBFRQYHUVLRQ��GDWH!��VWHQFLO!��GHOLPLWHU!��

<date>... Source field from transfer or communications structure<stencil>... StencilD/d... DayM/m... MonthY/y... Year<delimiter>... Delimiter between the day, month and year

Example for variant 1: Date_conversion ( Date , \\\\�GG�PP , ’ ’ )

Parameter <delimiter> can stay INITIAL since yyyy, dd and mm are always at the samelocation.

Example for variant 2: Date_conversion ( Date , GP\ , � )

The date must always be specified in the given order of year, month and day. It does notmatter how many places these have (month and day 1 or 2-place, year 2 or 4-place).Parameter <delimiter> must be filled with a value.

• 7LPH�FRQYHUVLRQV�

− Date in calendar week: Determines the calendar week from a date in SAP format (yyyymmdd).The date must be available in the SAP-internal format. The calendar week is returned in theformat \\\\ZZ.

Parameter: 'DWH�!:HHN��GDWH!��



If the date is not available in SAP format, the date conversion function can be integratedinto the formula. For example:

Date->Week ( Date Conversion ( <date> , ’dd.mm.yy’ , ’’ ) )

First, the delivered date is converted into the SAP-internal format, with the calendar weekconversion to follow.

− Calendar week in date: Converting calendar week into the date of the first day of the week.Converts the first day of the week from the calendar week. The calendar week must beavailable in SAP-internal format \\\\ZZ. The first day of the week is returned in SAP-internal format \\\\PPGG.

Parameter: :HHN�!'DWH��ZHHN!��

• 6WULQJ�RSHUDWLRQV�

− &21&$7(1$7(: Fields I� and I� are concatenated and passed to the result field. AttributesI� and I� as well as the result field must have type &KDUDFWHU.

Parameter: &RQFDWHQDWH��I��I��

− 68%675,1*: A string is removed from a character string and passed to the result field. Avalue for type &KDUDFWHU is passed to the result field.

Parameter: 6XEVWULQJ��ILHOG!��RIIV!��OJ!��

<field> Source field<offs> Offset<lg> Length

− 7UDQVODWH�WR�XSSHU�FDVH: All lower case letters in a string are translated to upper case.

Parameter: ,Q8SSHUFDVH��ILHOG��

The Formula Editor provides you with the fields of the transfer structure (in the transfer rules) and thecommunications structure (in the update rules) that you can use in the formula. You can select formulaelements and operands. The Formula Editor only displays actively the pushbuttons which may beused at the current location in the formula. The permitted operands are highlighted. The formula isautomatically checked for accuracy when the values are entered.

You can also set expert mode, with which you can enter your formula directly without using theformula elements and operands. In this case there is no automatic syntax check. You have to start itmanually. We do not recommend this however, since too many errors arise here.

You can find more information by choosing in the Formula Editor.



8SGDWH�5RXWLQHV

8VH

You can use routines to define complex update rules for a key figure or characteristic.

Routines are ABAP programs that consist of a predefined global data declaration part and an ABAPform routine. The form routine contains all the functions of the ABAP programming.

You can use the following types of routines in the update:

• the start routine [Seite 207] -- this routine is executed exactly once at the beginning of theupdate program for a data package

• routines for updating key figures with and without a return table

• routines for updating key figures and their unit

• routines for updating characteristics

)XQFWLRQV

5RXWLQHV�IRU�.H\�)LJXUHV�ZLWKRXW�D�5HWXUQ�7DEOH�DQG�IRU�&KDUDFWHULVWLFV

The form routine has the following parameters:

• 021,725: means that there is user-defined monitoring

• &200B6758&785(: The routine of the record of the communications structure to be updated isstored in variable &200B6758&785(.

• 5(&25'B12: Variable 5(&25'B12 contains the number of the record of the transaction data tobe edited in the form of the communications structure.

• 5(&25'B$//: Variable 5(&25'B$// contains the number of records of the transaction data inthe form of the communications structure.

• 6285&(B6<67(0: Variable 6285&(B6<67(0 contains the technical name of the sourcesystem.

• 5(68/7: Variable 5(68/7 must be assigned the result of the computed key figure or computedcharacteristic.

• 5(7851&2'(: You can control how you write in the InfoCube with variable 5(7851&2'(. Thecomputed 5(68/7�value is only written to the data target if 5(7851&2'( is equal to 0.5(7851&2'(�not equal to 0 means that there was an error in the computation, i.e. the 5(68/7value is not updated in the data target.

• DERUW��If DERUW is not equal to 0, the entire update process is canceled.

In the following example, the loading process is canceled if the value for the InfoObjectAMOUNT is less than 0. In this case, the message ‘100’ of type ERROR (E) with themessage class ‘ZJH’ appears.

Messages of type ERROR also appear in the monitor when the status is displayed for theIDoc.

1. * if abort is not equal zero, the update process will be canceled

2. if comm_structure-amount < 0.

3. monitor-msgid = ‘ZJH’.

4. monitor-msgty = ‘E’.



5. monitor-msgno = ‘100’.

6. monitor-msgv1 = comm_structure-amount.

7. append monitor.

8. abort = 1.

9. exit.

10. else.

11. abort = 0.

12. endif.

13. * result value of the routine

14. result = comm_structure-amount.

There is also the option of specifying global declarations in rows 4 and 5 (tables or data)that can then be used with all additional routines that you create.

5RXWLQHV�IRU�.H\�)LJXUHV�ZLWK�8QLW�&DOFXODWLRQ

If you set the 5RXWLQH�ZLWK�XQLW�FDOFXODWLRQ flag, you also get the return parameter UNIT. In this respectyou can store the required unit of the key figure, such as DEM or ST.

5RXWLQHV�IRU�.H\�)LJXUHV�ZLWK�5HWXUQ�7DEOH

For routines with a return table, parameter RESULT is replaced with return table RESULT_TABLE.The return table has the same structure as the data target, but only the key figure (data field for ODSobjects for which the routine was created plus its characteristics (key fields for ODS objects) is filled.

Parameter ICUBE_VALUES also exists. The computed characteristic values are stored here. If youwant to fill return table RESULT_TABLE, it is easiest to copy structure ICUBE_VALUES to tableRESULT_TABLE as often as necessary and to then fill the corresponding key figure and adjust thecharacteristic values.

Also note the following special case: If you use a key figure routine with return table and currencytranslation, the currencies are NOT stored in structure ICUBE_VALUES since they are only computedonce the routine has been executed.

6WDUW�5RXWLQH

The start routine has only MONITOR, DATA_PACKAGE, RECORD_ALL, SOURCE_SYSTEM andABORT as parameters. DATA_PACKAGE is the entire data package. The start routine does not havea return value. It is for performing preliminary computations and storing them in a global data structureor table. You can access this structure or table in other routines.

6HH�DOVR�

Creating Update Routines [Seite 221]



&UHDWLQJ�8SGDWH�5RXWLQHV

3UHUHTXLVLWHV

You are in the update rules maintenance for your InfoProviders in the detail view of the key figure/datafield/attribute for which you want to create a routine.

3URFHGXUH

1. Choose 5RXWLQH�

2. Choose &UHDWH�URXWLQH�

The ABAP editor appears with the following source code:

1. PROGRAM UPDATE_ROUTINE.

2.

3. *$*$ begin of global - insert your declaration only below this line *-*

4. * TABLES:...

5. * DATA: ...

6. *$*$ end of global - insert your declaration only before this line *-*

7. *

8. FORM compute_characteristics

9. TABLES monitor structure rsmonitor "user defined monitoring

10. USING COMM_STRUCTURE LIKE /BIC/CS�LQIRVRXUFH!

11. RECORD_NO LIKE SY-TABIX

12. RECORD_ALL LIKE SY-TABIX

13. SOURCE_SYSTEM LIKE RSUPDSIMULH-LOGSYS

14. CHANGING RESULT LIKE /BIC/V�LQIRFXEH!T-�LQIRREMHFW!

15. RETURNCODE LIKE SY-SUBRC.

16. *

17. *$*$ begin of routine - insert your code only below this line *-*

18. * fill the internal table "MONITOR" to make monitor entries

19.

20. * result value of the routine

21. RESULT =.

22.

23. * if the returncode is not equal zero, the result will not be updated

24. RETURNCODE = 0.

25.

26. * if abort is not equal zero, the update process will be canceled

27.

28. ABORT = 0.

29. *$*$ end of routine - insert your code only before this line *-*



30. *

31. ENDFORM.

The EOXH�LWDOLFV�in the text, marked <>, are automatically replaced with the relevant objectname.

3. Insert your code under *$*$ begin of routine ... (line 17) and *$*$ end of routine... (line 29). In the field 5HVXOW� �(21), you can set the result of your update routine.

4. Check the syntax of your routine with the &KHFN function.

5. Save your entries. You end routine maintenance by leaving the editor.



&KDQJLQJ�8SGDWH�5XOHV

3UHUHTXLVLWHV

You have already created an update rule.

3URFHGXUH

1. Choose the relevant ,QIR3URYLGHU → the relevant 8SGDWH�UXOH→ ULJKW�PRXVH�EXWWRQ→ &KDQJHXSGDWH�UXOHV.

The existing update rules are displayed.

2. Select a key figure/data field by double-clicking on it, or by choosing 'HWDLO.

3. Change the rules for the InfoProvider in your

• Update type [Seite 208]

• Update method [Seite 210]

• Update routine [Seite 221]

4. Use the 9HUVLRQ�&RPSDULVRQ function to compare the modified update rules with the active updaterules.

5. Save and activate your entries.



7UDQVIHUULQJ�8SGDWH�5XOHV�IURP�D�7HPSODWH

8VH

You have the option of transferring update rules that already exist for one data target to another datatarget.

3UHUHTXLVLWHV

The update rules for both data targets refer to the same InfoSource.

)XQFWLRQV

If you want to create update rules for a data target, you can choose a template in the screen &UHDWHXSGDWH�UXOHV��,QLWLDO�VFUHHQ, for which update rules already exist. These update rules are copied for thecurrent data target and the specified InfoSource. InfoCubes are available as a template for InfoCubes,ODS objects for ODS objects and InfoObjects for InfoObjects.

The data targets can have different structures. The system determines automatically how theindividual rules are assigned.

You are able to subsequently adjust and change the copied update rules.



&XUUHQF\�7UDQVODWLRQ�LQ�WKH�8SGDWH

8VH

Currency translation in the update provides the option of translating data records from the sourcecurrency of the InfoSource into a target currency in the data target. If the currency of the data recordsto be transferred is the same as the currency of the target key figure/data field of the InfoCube/ODSobject, then no currency translation has to take place.

The currency translation in the update usually takes place using translation types previously defined inthe Administrator Workbench. Where necessary it can take place using user-defined subprograms(formulas and routines).

Depending on the type of currency, there are two types of key figures to distinguish between:

1. Key figures with a IL[HG�FXUUHQF\�(for example, DEM, USD)

With a fixed currency the currency is fixed to the amount. The key figure refers to thecorresponding currency (for example DM, US$), so that it does not have to be enteredspecially in the data record.

2. Key figures with a YDULDEOH�FXUUHQF\� (for example, foreign currency).

An InfoObject is referred to with a variable currency (in this case, ODOC_CURRCY, forexample).

6HH�DOVR�


)XQFWLRQV

:LWK�WKH�XSGDWH�RI�NH\�ILJXUHV��WKHUH�DUH�EDVLFDOO\�WZR�FDVHV�WR�GLVWLQJXLVK�EHWZHHQ�

1. For every key figure of an InfoCube (target key figure) there is a�FRUUHVSRQGLQJ�NH\�ILJXUH�LQ�WKH,QIR6RXUFH (source key figure). The same also applies for the data fields for an ODS object. Nocurrency translation takes place.

2. For the InfoCube target key figure there is QR corresponding source key figure in the InfoSource(the same also applies for data fields for ODS objects).

a. A source key figure of the VDPH�W\SH can be assigned to the target key figure (for example,sales revenue instead of sales quantity revenue).

• If the currencies of both of the key figures are the same, then no currency translationtakes place.

• If the currencies are different, then a translation can take place either using a currencytranslation type or by the simple assignment of a currency.

The following table provides an overview of possible combinations with GLIIHUHQWFXUUHQFLHV in the source and target key figures:

6RXUFH�NH\�ILJXUH�FXUUHQF\ 7DUJHW�NH\�ILJXUH�FXUUHQF\ &XUUHQF\�WUDQVODWLRQ��&7�

fix variable No CT

fix fix CT

variable fix CT

variable variable CT possible, but also simpleassignment



b. If there is QR corresponding source key figure of the same type, then you have to fill the keyfigure for the InfoCube from a URXWLQH.

• If the target key figure has a IL[HG�FXUUHQF\, then no currency translation is carried out.This means that you have to execute a required translation where necessary in theroutine.

• If the target key figure has a YDULDEOH FXUUHQF\, you have to also assign a variable sourcecurrency to the routine. Using the F4 Help you can select a currency from the variablecurrencies in the communication structure. You then have two options:

– You can assign the selected variable currency

– You select a currency translation type and a currency, into which you wish totranslate (‘To’ currency)

The ‘To’ currency is, by default, the target currency, if it appears in the communicationstructure.

6HH�DOVR�

Currency Translation Type [Extern]



$GGLWLRQDO�)XQFWLRQV�LQ�8SGDWH�5XOH�0DLQWHQDQFH

3HUVRQ�5HVSRQVLEOH

You have the option of specifying a person responsible for a specific update maintenance.

6RUWLQJ�5XOHV

You can sort the rules that control the calculation of key figure for routines. It makes sense to do this,for example, if the result of a routine is to be used for additional routines.

The key figures are calculated together with the particular characteristics that you entered in the listsequence.

You can sort rules by selecting one or more rules with the mouse, and then clicking with the left mousebutton on a key figure. You can insert the selected rule, or rules, into the rows by choosing 6RUW�

&KHFNLQJ�5XOHV

Via &KHFN�5XOHV��you can check whether you have correctly created a rule that belongs to an updaterule. If errors are determined during the check procedure, you receive an error message with a markerfor the particular maintenance dialog.

&KHFNLQJ

Via &KHFN��you can activate a check procedure for all rules belonging to an update rule. A statusdisplay with traffic light function follows.



6RXUFH�6\VWHP

'HILQLWLRQ

All systems that provide the SAP Business Information Warehouse with data are described as sourcesystems. These can be:

1. SAP source systems from Release 3.0D,

2. SAP Business Information Warehouse systems,

3. Flat files, through which Metadata is manually maintained, and transferred into BW via a fileinterface,

4. A data bank system into which data is loaded from a databank supported by SAP without the helpof an external extraction program.

5. External systems, where data and Metadata is transferred using staging BAPIs.

Use the &UHDWH�function in the source system tree of the Administrator Workbench to specify the typeof source system.

,QWHJUDWLRQ

DataSources are responsible for extracting and staging data from source systems. TheseDataSources subdivide the data that is provided by a source system into self-contained businessareas. In source systems, the DataSources are assigned to applications, for example HR (HumanResources). The advantage of this is that you are able to access specifically the data evaluation forthis application.

Data Provision

,QIR&XEHV�

2'6�2EMHFWV

%XVLQHVV�,QIRUPDWLRQ

:DUHKRXVH�6HUYHU

6WDJLQJ�(QJLQH


��

��

��

��

��

��

��


,QIR6RXUFH

Communication StructureCommunication Structure


'DWD6RXUFH(Duplicate)




By way of a Metadata comparison, the information that is needed for the extraction process, that is theBW-relevant properties of the DataSource, is replicated in the BW.



&RQQHFWLRQ�EHWZHHQ�6RXUFH�6\VWHPV�DQG�%:BW as a Data Warehouse is tightly networked with other systems. While there are several sourcesystems connected to it, it can also be used as a source system itself. In this case, we speak of DataMarts [Seite 261] .

Because changes to a system in the source system-BW network affect all connecting systems, theycannot be seen as isolated parts.

A connection between a source system and BW consists of a sequence of individual links and settingsthat are made for both systems involved.

• RFC connections

• ALE settings

− Partner profiles

− Port

− IDoc types

− IDoc segments

• BW settings

/RJLFDO�6\VWHP�1DPH

Because data is distributed between systems, it is necessary to clearly identify each system within anetwork. The “logical system” serves this purpose.

A logical system is an application system in which the applications work together on a common databasis. In SAP terms, the logical system is a client.

As the logical system name serves as unique identification for a system in the system network, twosystems cannot have the same name as long as they are directly or indirectly connected as a BW orsource system or to each other, or are planned to be connected as such.

Although we do not recommend that you connect test systems to productive systems, these can havethe same name. This makes copying productive systems to test systems a lot simpler.

You are only allowed to change the logical system name if the system is not connected to othersystems, as changing the name would render the connections to all connecting systems useless.

You can make the settings for the logical system name in the BW Customizing Implementation Guideunder %XVLQHVV�,QIRUPDWLRQ�:DUHKRXVH Å�&RQQHFWLRQV�WR�RWKHU�6\VWHPV�Å�*HQHUDO�&RQQHFWLRQ6HWWLQJV. In the source system, you will find the settings for the logical system in the ImplementationGuide under &URVV�$SSOLFDWLRQ�&RPSRQHQWV�Å�'LVWULEXWLRQ��$/(��Å�%DVLF�6HWWLQJV.



&UHDWLQJ�DQ�6$3�6RXUFH�6\VWHP

3UHUHTXLVLWHV

1. You have made the following settings in the BW Customizing Implementation Guide under%XVLQHVV�,QIRUPDWLRQ�:DUHKRXVH → &RQQHFWLRQV�WR�RWKHU�6\VWHPV.

− General connection settings,

− Connection between SAP systems and BW,

− Verify workflow customizing.

2. You have made the following settings in the implementation guide of the source system under thenode &URVV�$SSOLFDWLRQ�&RPSRQHQWV�→�'LVWULEXWLRQ��$/(��→�%DVLF�6HWWLQJV�

• Set up logical system

− Maintain logical system

− Assign logical system to the client

• Make workflow basic settings

The name you used for the source system (logical system) must be used again for thecreation of the source system in the Administrator Workbench for the SAP BusinessInformation Warehouse.

3. You have taken the server name from the source system under 7RROV → $GPLQLVWUDWLRQ�→�0RQLWRU

→�6\VWHP�0RQLWRULQJ�→�6HUYHU� It is displayed as follows:

6HUYHUB�6$36,'!B�LQVWDQFHQR�!

pswdf090_IDF_90

4. As a rule, no system changes are permitted in productive systems at all. Connecting a system asa source system to a BW or connecting a BW to a new source system will, however, meanchanges as far as the system change option is concerned. You will have therefore made sure thatthe following changes are permissible in the relevant clients of the system when you connect thesource system.

• Cross-client Customizing and Repository changes

In the BW Customizing Implementation Guide, select the relevant client under %XVLQHVV,QIRUPDWLRQ�:DUHKRXVH�→�&RQQHFWLRQV�WR�2WKHU�6\VWHPV�→�*HQHUDO�&RQQHFWLRQ�6HWWLQJV

→�$VVLJQ�/RJLFDO�6\VWHP�WR�&OLHQW, then choose *RWR�→�'HWDLO. Choose the entry&KDQJHV�WR�5HSRVLWRU\�DQG�&URVV�&OLHQW�&XVWRPL]LQJ�3HUPLWWHG in the field &KDQJHV�WR&URVV�&OLHQW�2EMHFWV�

In the source system, make this setting in the Implementation Guide under &URVV�DSSOLFDWLRQ�&RPSRQHQWV�→�'LVWULEXWLRQ�$/(��→�%DVLF�6HWWLQJV�→�6HW�8S�/RJLFDO�6\VWHP

→�$VVLJQ�/RJLFDO�6\VWHP�WR�&OLHQW.

• Changes to the software components local developments and Business InformationWarehouse.

You can set up the changeability with Transaction SE03 (Organizer Tools). Choose2UJDQL]HU�7RROV�→�$GPLQLVWUDWLRQ�→�6HW�8S�6\VWHP�&KDQJH�2SWLRQ, then ([HFXWH. Makethe settings in the subsequent screen.

• Changes in the customer name area

Again, you can set up the changeability for the customer name area with TransactionSE03.



• Changes to BW namespaces /BIC/ and /BI0/

Again, you can set up the changeability of the BW namespace with Transaction SE03.

3URFHGXUH

• Creating an SAP Source System Manually [Seite 233]

• Creating an SAP Source System (from Release 3.0E) Automatically [Seite 232]

5HVXOW

The ALE settings, which are needed for the communication between a BW System and an SAPSystem, are created in the background with the use of the created destinations. These settings aremade in BW as well as in the source system. The BW settings for the new connection are created inBW.

If the new SAP source system has been created, Metadata is requested automatically from the sourcesystem.



&UHDWLQJ�DQ�6$3�6RXUFH�6\VWHP�$XWRPDWLFDOO\

1. In the BW Administrator Workbench choose 6RXUFH�6\VWHP�7UHH�→�&RQWH[W�0HQX��ULJKW�PRXVH

EXWWRQ��→�&UHDWH�and choose the radio button for creating an external system.

2. Enter the information on the server name previously taken from the source system.

Application server: pswdf090

System ID: IDF

System number: 90

3. Enter a password for the background user in the source system and confirm this in the next inputrow. If the user already exists in the source system, enter the valid password.

4. Enter the password that you defined for the SAP BW background user in the BW CustomizingImplementation Guide under %XVLQHVV�,QIRUPDWLRQ�:DUHKRXVH�→�/LQNV�WR�2WKHU�6\VWHPV�→�/LQN

%HWZHHQ�6$3�6\VWHPV�DQG�%:�→�%DFNJURXQG�8VHU�IRU�/LQNV�WR�6$3�6\VWHPV, and confirm.

5. Choose &RS\� You get to the remote login in the source system.

6. Select the relevant clients and logon as system administrator. Make sure beforehand that youhave the authority to create users and RFC destinations.

The RFC destinations for BW and the background users are thus created automatically in thesource system. You can find additional information on the RFC destinations in the BasisDocumentation in the section 0DLQWDLQLQJ�5HPRYHG�'HVWLQDWLRQV.

Profile assignment for the user is also carried out automatically. If the user already exists inthe source system, check the accuracy of the profile [Extern] If the RFC destination alreadyexists in the source system, check its accuracy too. You can carry out an RFC destination testwith the function 7HVW�→�/LQNV and 7HVW�→�$XWKRUL]DWLRQV.

The RFC destination for the source system is now created automatically in BW with theinformation read in the source system.

You can find more detailed information under:

Creating an SAP Source System [Seite 230]



&UHDWLQJ�DQ�6$3�6RXUFH�6\VWHP�0DQXDOO\1. In the initial screen of the source system choose 7RROV�Å�$GPLQLVWUDWLRQ�Å�0DLQWDLQ�8VHUV�Å

8VHUV and create a background user with a password and the authorization profile S_BI-WX_RFC.

See also:

Authorization Profile for ALE Users [Extern]

2. Define the RFC destination parameters for the SAP source system in BW. To do this, choose7RROV�→�$GPLQLVWUDWLRQ�→�0DQDJHPHQW�→�1HWZRUN�→�5)&�'HVWLQDWLRQV�in BW.

Enter the information on the server name previously taken from the source system.

Application server: pswdf090

System ID: IDF

System number: 90

The destination name must correspond to the logical name of the source system that youentered for the process step 0DLQWDLQ�/RJLFDO�6\VWHP in the implementation guide of thesource system.

For user and password, enter the background user that you created in step 1.

3. Define the RFC destination parameters for the SAP Business Information Warehouse in thesource system. Select 7RROV�→�$GPLQLVWUDWLRQ�→�0DQDJHPHQW�→�1HWZRUN�→�5)&�'HVWLQDWLRQVhere in the source system.

Enter the information on the server name previously taken from the source system.

The destination name must correspond to the logical name of the BW system that youentered for %:�&XVWRPL]LQJ�,PSOHPHQWDWLRQ�*XLGH in the process step 1DPH�/RJLFDO6\VWHP. ALE communicates with the help of the SAP Business Information Warehousename that you defined. The defined name, therefore, represents an identification of theSAP Business Information Warehouse.

For the user and password, enter the background user that you defined in the BWCustomizing Implementation Guide under %XVLQHVV�,QIRUPDWLRQ�:DUHKRXVH�→�&RQQHFWLRQV�WR

RWKHU�6\VWHPV�→�&RQQHFWLRQ�EHWZHHQ�6$3�6\VWHPV�DQG�%:.

4. Test both RFC destinations with the functions 7HVW�→�&RQQHFWLRQ�and�7HVW�→�$XWKRUL]DWLRQ�

If an error occurs during the authorization check, the background user in this client andwith this password is not permitted.

If an error occurs in the connection test, it means there is a network problem.

5. In the BW Administrator Workbench choose 6RXUFH�6\VWHP�7UHH�→�5RRW�→�&RQWH[W�0HQX��ULJKW

PRXVH�EXWWRQ��→&UHDWH�and select the radio button for the manually creating an SAP sourcesystem.

6. Enter a description for the source system and the logical name of the source system that youentered for the process step 0DLQWDLQ�/RJLFDO�6\VWHP in the implementation guide of the sourcesystem.

You can find more detailed information under:




&UHDWLQJ�([WHUQDO�6\VWHPV

3UHUHTXLVLWHV




5. As a rule, no system changes are permitted in productive systems at all. Connecting a system asa source system to a BW or connecting a BW to a new source system will, however, meanchanges as far as the system change option is concerned. For the clients concerned in the BWsystem therefore, you have made sure that the following changes are permitted during the sourcesystem connection.






• Changes in the customer name range




3URFHGXUH

1. In the BW Administrator Workbench, choose�6RXUFH�V\VWHP�WUHH�→�&RQWH[W�PHQX��ULJKW�PRXVH

EXWWRQ��→�&UHDWH��and select the radio button for creating an external system.

2. Enter a name and a description.

3. For your extraction tool, maintain the destination that is to be referred to when loading data fromBW.

5HVXOW

When you use the created destinations, the ALE settings that are necessary for communicationbetween a BW system and an external system, are created in BW in the background. The BW settingsin BW are created to a new link.

6HH�DOVR�

Maintaining InfoSources (External System) [Seite 303]



&UHDWLQJ�)LOH�6\VWHPV

3UHUHTXLVLWHV



− Connection between flat files and BW,


6. As a rule, no system changes are permitted in productive systems at all. Connecting a system asa source system to a BW or connecting a BW to a new source system will, however, meanchanges as far as the system change option is concerned. For the clients concerned in the BWsystem therefore, you have made sure that the following changes are permitted during the sourcesystem connection.






• Changes in the customer name range




3URFHGXUH

1. In the BW Administrator Workbench, choose 6RXUFH�6\VWHP�7UHH�→�&RQWH[W�0HQX��ULJKW�PRXVH

EXWWRQ�→�&UHDWH,�and select the radio button to create a file system automatically.

2. Enter the technical name of your file system under 6RXUFH�V\VWHP and enter a description.

5HVXOW

In BW the ALE settings are created in the background that are necessary for communication betweena BW system and a file system. The BW settings in BW are created to a new connection.

6HH�DOVR�

Maintaining InfoSources (flat files) [Seite 289]



'DWD�([WUDFWLRQ�IURP�6$3�6RXUFH�6\VWHPV

3XUSRVH

Extractors belong to the data retrieval mechanisms in the SAP source system. An extractor can fill theextract structure of a DataSource with the data from the SAP source system datasets.

With a Metadata upload, the DataSource is replicated with its relevant properties in BW. Once thereyou can assign it to an InfoSource. The fields of a DataSource should be assigned to BW InfoObjects.

When you have specified the data flow in the BW Administrator Workbench by maintaining the transferrules, you can schedule an InfoPackage in the Scheduler. The data loading process is then triggeredto the source system by a request IDoc.

3URFHVV

There are application-specific extractors, each of which are hard-coded for the DataSource that wasdelivered with BW Business Content, and which fill the extract structure of the DataSource.

In addition, there are generic extractors, with which you can extract more data from the SAP sourcesystem and transfer it into BW. Only when you call up the generic extractor by naming the DataSourcedoes it know which data is to be extracted, and from which tables it should read it from and in whichstructure. This is how it fills different extract structures and DataSources.

You can run generic data extraction in the R/3 source system application areas such as LIS, CO-PA,FI-SL and HR. This is how LIS, for example, uses generic extraction to read info structures.DataSources are generated on the basis of these (individually) defined info structures. In the case ofgeneric data extraction from applications, we speak of customer-defined DataSources.

Independent of a particular application, you can generically extract master data or transaction datafrom any transparent table, database views or functional areas of the SAP Query. For this, you cangenerate user-specific DataSources. In this case, we speak of generic DataSources.

The DataSource data for these two types are read generically and transferred to BW. This is howgeneric extractors allow the extraction of data that cannot be made available within the framework ofBusiness Content.

You can find further information in the implementation guide to data extraction from SAP sourcesystems. You get there by choosing <RXU�6RXUFH�6\VWHP�Å�&RQWH[W�0HQX�(right mouse click)�Å&XVWRPL]LQJ�([WUDFWRUV in the BW Administrator Workbench – Modeling.

3OXJ�LQ�IRU�5��6\VWHPV

BW-specific source system functions, extractors and DataSources are delivered by so-called plug-ins.

Communication between the R/3 source system and the SAP Business InformationWarehouse is only possible if the appropriate plug-in is installed in the source system.



'DWD6RXUFH

'HILQLWLRQ

Data that logically belongs together is stored in the source system in the form ofDataSources.

A DataSource contains a number of fields in a flat structure used to transfer data intoBW (Extract Structure [Seite 243]). It also describes the properties of the extractorbelonging to it, as regards the data transfer into BW. During a Metadata upload, theproperties of the DataSource relevant to BW are replicated in BW.

There are four types of DataSource:

• DataSources for transaction data

• DataSources for master data

These can be:

− DataSources for attributes

− DataSources for texts

− DataSources for hierarchies

With the upgrade from 1.2B to 2.0 the InfoObjects are converted into DataSources. Themaster data DataSources are given the type-dependent suffix ‘_ATTR’, ‘_TEXT’ or‘<HCLASS>_HIER’.

,QWHJUDWLRQ

DataSources are used for extracting data from a source system and for transferringdata into BW. DataSources make the source system data available on request to BWin the form of the extract structure. Data is transferred from the source system intothe SAP Business Information Warehouse in the transfer structure [Seite 283]. In thetransfer rules maintenance, you determine how the fields of the transfer structure aretransferred into the InfoObjects of the communication structure [Seite 278]. You assignDataSources to InfoSources and fields to InfoObjects [Seite 242] in the transfer rulesmaintenance.



Data Staging

,QIR&XEHV�

2'6�2EMHFWV

%XVLQHVV�,QIRUPDWLRQ:DUHKRXVH�6HUYHU

6WDJLQJ�(QJLQH


��

��

��

��

��


,QIR6RXUFH



'DWD6RXUFH(Copy)




%:��DQG�%:��%�3OXJ�,Q

Compatibility between a BW 1.2B plug-in and a BW 2.0 is guaranteed. This meansthat you are able to use InfoSources from the BW 1.2B plug-in for transferring datainto a BW 2.0.



7UDQVIHUULQJ�%XVLQHVV�&RQWHQW�'DWD6RXUFHV�LQWR�$FWLYH9HUVLRQ

8VH

For R/3 plug-in PI 99(-A) the concept of the delivery version and the active version of BW objects forDataSources in the source system has been introduced. The DataSources delivered by SAP withBusiness Content are in the source system in the SAP delivery version (D version). If you want totransfer data from a source system into a BW using a Business Content DataSource, then you have tofirst transfer the data from the D version into the active version (A version). With a Metadata upload,the active version of the DataSource is finally replicated in BW.

Business Content DataSources of a source system are only available to you in BW for transferringdata, if you have transferred these in their active versions in the source system and then carried out aMetadata upload.

3URFHGXUH

In order to transfer and activate a DataSource delivered by SAP with Business Content, select yoursource system in the source system tree of the BW Administrator Workbench and select &XVWRPL]LQJ([WUDFWRUV�Å�%XVLQHVV�,QIRUPDWLRQ�:DUHKRXVH�Å�%XVLQHVV�&RQWHQW�'DWD6RXUFHV�$FWLYDWLQJ�6$3%XVLQHVV�&RQWHQW�Å�7UDQVIHU�%XVLQHVV�&RQWHQW�'DWD6RXUFHV�using the context menu (right mousebutton). For further information on this activity, see the documentation for customizing extractors.



0DLQWDLQLQJ�'DWD6RXUFHV

8VH

Source system DataSources are processed in the customizing for extractors. You get to customizingvia the context menu (right mouse button) for the relevant source system in the source system tree ofthe BW Administrator Workbench - Modeling.

Or you can go directly to the DataSource maintenance screen by choosing 0DLQWDLQLQJ�'DWD6RXUFH�LQ6RXUFH�6\VWHP from the context menu of the source system DataSource overview.

For further information on maintaining DataSources, choose 6XEVHTXHQW�3URFHVVLQJ�RI�'DWD6RXUFHVÅ�(GLW�'DWD6RXUFH in the extractor customizing screen.



$VVLJQLQJ�'DWD6RXUFHV�WR�,QIR6RXUFHV�DQG�)LHOGV�WR,QIR2EMHFWV

8VH

You carry out the assignment of a DataSource to an InfoSource in the BW transfer rules maintenance.

In the DataSource overview for a source system in the Administrator Workbench – Modeling, there isalso the additional option of assigning an unmapped DataSource to an InfoSource. To do this, usingthe context menu (right mouse button) of a DataSource, choose $VVLJQ�,QIR6RXUFH. If you use thisassignment option, you can

1. choose an InfoSource from a list containing InfoSources sorted according to the agreement oftheir technical names

2. create a new InfoSource

Assign several DataSources to one InfoSource, if you want to gather data from different sources into asingle InfoSource. This is used, for example, if data from different IBUs that logically belongs togetheris grouped together in BW.

The fields for a DataSource are assigned to InfoObjects in BW. This assignment takes place in thesame way in the transfer rules maintenance.

For Business Content DataSources, the assignment to InfoSources, as well as theassignment of fields to InfoObjects, is delivered by SAP.



([WUDFW�6WUXFWXUH

'HILQLWLRQ

In the extract structure, data from a DataSource is staged in the source system. The extract structurecontains the amount of fields that are offered by an extractor in the source system for the data loadingprocess.

You can edit and enhance DataSource extract structures in the source system. To do this, in the BWAdministrator Workbench choose *RWR�Å�0RGHOLQJ�Å�6RXUFH�6\VWHPV�Å�<RXU�6RXUFH�6\VWHP�Å&RQWH[W�0HQX��right mouse click��Å�&XVWRPL]LQJ�([WUDFWRUV�Å�6XEVHTXHQW�3URFHVVLQJ�RI'DWD6RXUFHV.



7UDQVIHU�6WUXFWXUH

'HILQLWLRQ

The transfer structure is the structure in which the data is transported from the source system into theSAP Business Information Warehouse.

It provides a selection of the extract structure fields for the source system.

8VH

The transfer structure provides BW with all the source system information available for a businessprocess.

An InfoSource in BW requires at least one DataSource for data extraction. DataSource data thatlogically belongs together is staged in an extract structure in an SAP source system.

In the transfer structure maintenance, you determine which extract structure [Seite 243] fields aretransferred to the BW. When you activate the transfer rules in BW, an identical transfer structure forBW is created in the source system from the extractor structure.

This data is transferred 1:1 from the transfer structure of the source system into the BW transferstructure, and is then transferred into the BW communication structure using the transfer rules.

A transfer structure always refers to a DataSource from a source system and an InfoSource in BW.

You get to the maintenance of the transfer structure using the InfoSource tree of the AdministratorWorkbench. The context menu of the source system belonging to an InfoSource provides you with themaintenance marker using the function 0DLQWDLQ�7UDQVIHU�5XOHV�



'HOWD�3URFHVV

'HILQLWLRQ

The delta process is a feature of the extractor and specifies how data is to betransferred. As a DataSource attribute, it specifies how the DataSource data ispassed on to the data target. From this you can derive, for example, for which data aDataSource is suited, and how the update and serialization are to be carried out.

8VH

The type of delta process affects the update into a data target. When you updatedata in an ODS object, you need to serialize it so that you can also overwrite it.According to the delta process, the system decides whether it is necessary toserialize by request or by data packet.

6WUXFWXUH

6$3�VRXUFH�V\VWHPV��5��%�%��&50��KDYH�GLIIHUHQW�GHOWD�SURFHVVHV�

1. Forming deltas with after, before and reverse images that are updated directly in the delta queue;an after image shows the status after the change, a before image the status before the changewith a negative sign and the reverse image also shows the negative sign next to the record whileindicating it for deletion. This serializes the delta packets. The delta process controls whetheradding or overwriting is permitted. In this case, adding and overwriting are permitted. This processsupports an update in an ODS object as well as in an InfoCube. (technical name of the deltaprocess in the system): ABR)

2. The extractor delivers additive deltas that are serialized by request. This serialization is necessarysince the extractor within a request delivers each key once, and otherwise changes in the non-keyfields are not copied over correctly. It only supports the addition of fields. It supports an update inan ODS object as well as in an InfoCube. This delta process is used by LIS DataSources.(technical name of the delta process in the system): ADD)

3. Forming deltas with after image, which are updated directly in the delta queue. This serializes databy packet since the same key can be copied more than once within a request. It does not supportthe direct update of data in an InfoCube. An ODS object must always be in operation when youupdate data in an InfoCube. For numeric key figures, for example, this process only supportsoverwriting and not adding, otherwise incorrect results would come about. It is used in FI-AP/ARfor transferring line items, while the variation of the process, where the extractor can also sendrecords with the deletion flag, is used in this capacity in BBP. (technical name of the delta processin the system): AIM/AIMD)

,QWHJUDWLRQ

The field 0RECORDMODE determines whether the records are added to oroverwritten. It determines how a record is updated in the delta process: A blankcharacter signifies an after image, ‘X’ a before image, ‘D’ deletes the record and ‘R’means a reverse image.

When you load flat files [Seite 292], you must select a suitable delta process from thetransfer structure maintenance screen, to make sure you use the correct update type.



7UDQVIHUULQJ�'DWD�LQ�;0/�)RUPDW

3XUSRVH

XML is a text-based, meta markup language that allows the description, exchange, display, andmanipulation of structured so that it can be used for a multitude of applications.

By integrating XML-formatted data into BW Data Staging, the IOH[LELOLW\�RI�%: is supported withregard to external data analysis. You can send data in XML format to BW by using the Internet logHTTP and then integrate it into the consolidated data basis with the available staging methods.

'DWD�7DUJHWV

6$3�%:

6HUYHU

,QIR6RXUFH

��

�� !��"#�$�%��&��

��'�(�� )��#��%��&�*�

+-,�./,!0 1�2�3/4�5

687�9��"&��!"��

�%�*�'�(�&:��!"#��9��"&��!��"&�

+;,�.#,!0 1�2�3/4�5

<-= � �<-= �� >�?A@>�?A@BACEDGF � �B9C D�F � �

HHH

I J ��I J � �

K�LNM�L*O!P�Q�R&SUT

The transfer of XML data to BW is suitable for regular BW services with OLPLWHG�DPRXQWV�RI�GDWD�IRUHDFK�FDOO. An example would be the transfer of document data. External mass data is transferred toBW in file format.

3URFHVV

The basis for the solution is the use of the SOAP Service provided with SAP Web Application Server6.10. By using this service you can transfer XML data, which are sufficient for the Simple ObjectAccess Protocol (SOAP), to RFC-capable function modules in the ABAP environment.

The BW Service API Delta Queue is used as an inbound queue for the reclassified data that wasparsed in SOAP Service and in ABAP fields.

For transferring document data in XML format, you generate a special DataSource (which has aninterface for delta queue services) in BW on the basis of a file DataSource. You generated a suitableRFC-capable function module for the XML DataSource. This runs the data update in the delta queue.In doing so, the XML data has to be assigned according to an XML schema definition, which is derivedfrom the definition of the file or XML DataSource.

Data transfer takes place in BW with a “push” into the delta queue of the generated DataSource.

As a rule, data transfer in BW takes place by using a data request, which is sent from BWto the source system (pull). In contrast, sending XML data to BW from the outside iscontrolled outside, and not by means of a data request from BW. You call this a datapush in BW.



For transferring larger amounts of data, the file DataSource is provided.

Transferring hierarchie data in XML format is not possible.

5HVXOW

After the push, the reclassified and document-type data that was parsed in the SOAP Service andABAP fields is stored in the delta queue. You collect the data here and can continue to update it byusing the InfoPackage delta request.



;0/�'DWD6RXUFH��%:�'DWD6RXUFH�ZLWK�62$3�&RQQHFWLRQ�

'HILQLWLRQ

A DataSource generated in BW on the basis of a file DataSource for transferring XML data to theSOAP standard.

8VH

With the help of the generated XML DataSource, you can transfer XML data into the BW delta queuein order to continue to update them from there into the data targets you want.

,QWHJUDWLRQ

)LOH�'DWD6RXUFH�DV�%DVLV

The starting point for the generation of the special XML DataSource is a file DataSource. Additionally,it does the following:

• characterizes the XML data in BW

An XML schema definition is derived from the definition of the file DataSource. According tothis definition, the XML data must be retrieved.

• supplies BW with larger amounts of data that should not be transferred into BW using the XMLinterface

You create the file DataSource using the definition of an InfoSource with flexible updating for a filesource system. Flexible updating is a prerequisite for both maintaining the delta process for theDataSource as well as writing the data into the delta queue of the DataSource.

The DataSource is generated with the transfer structure by activating the transfer rules.

;0/�'DWD6RXUFH

You generate an XML DataSource in the maintenance of the transfer rules of the file DataSource byusing $GGLWLRQDO�'DWD →�&UHDWH�%:�'DWD6RXUFH�ZLWK�62$3�&RQQHFWLRQ This has the followingproperties:

• It is generated in a new namespace (<xml-datasource> = 6A<file-datasource>).

• It has the BW system itself as the source system (myself connection)

• It is intended exclusively for loading delta records, since the inbound queue is the delta queue inBW.

• It has an interface for supplying the delta queue.

In doing so, the SAPI interface for supplying the delta queue is encapsulated by aDataSource-specific, RFC-capable function module, which is generated for this purpose forthe DataSource.

On the basis of the RFC-capability, the function module can be automatically addressed byusing one of the assigned HTTP handlers from SAP for supporting the SOAP log. The functionmodule then runs the data update in the delta queue.

The function module has the following properties:

Function group naming convention /BIC/QI<xml-datasource>

Function module naming convention /BIC/QI<xml-datasource>_RFC

Import parameter <xml-datasource>

Table parameter data



The delta queue has to be activated by an initialization without a data request before XMLdata can be transferred into BW.

• The XML DataSource extraction structure is suitably generated for the file DataSource transferstructure.

• The selectability of fields and the delta process are based on the file DataSource.

If you specify the additives delta update mode for the file DataSource, the delta process forthe ABR XML DataSource (After, Before, Reverse) is used. Otherwise, the AIM (After Image)delta process is used for the XML DataSource.

([WHUQDO�$SSOLFDWLRQ

�� "!�� !��# $��%��&�� %�&�'!�� ! ( �� !�� *)��+�','�� !��

%:

-/.�0+132/4657.�58.

9 ;: ��",'�� !*� �

< � = �','�� !��

>?��@3@7��

9 ;: � ,"A'@B� �C�

-/.�0D132 ECF�G+1H�570D0

I%58J*KL/MONP-/2�1Q2

H�R�I

S7T�U I

XML data is transferred by using a delta process push into the BW delta queue. You load largeramounts of data, however, by using a full upload into the BW file DataSource.



&UHDWLQJ�DQ�;0/�'DWD6RXUFH

8VH

You can transfer data to BW from external applications in XML format by using the Internet log HTTP.There you can continue to update into the desired data targets with BW staging methods. One of theXML DataSources generated in BW on the basis of a file DataSource is required for this purpose.

3UHUHTXLVLWHV

You have connected a file system to BW as the source system.

3URFHGXUH

You are in the 0RGHOLQJ InfoSource tree of the Administrator Workbench.

1. Choose ,QIR6RXUFHV → <RXU�$SSOLFDWLRQ�&RPSRQHQW → &RQWH[W�PHQX �ULJKW�PRXVH�FOLFN� →&UHDWH�,QIR6RXUFH...

2. Create an InfoSource with flexible updating.

You can also refer to the section Uploading Transaction Data from Flat Files [Seite 290].

Creating an InfoSource with flexible updating is necessary, since

a. the file DataSource, which you are using to generate the DataSource for the XML data, cannotbe created independently from an InfoSource and

b. data can only run in the delta queue if it is updated flexibly and if the delta processmaintenance for the file DataSource is only possible with flexible updating.

3. Assign the file system as the source system to the InfoSource after activating the communicationstructure.

In doing so, a file DataSource is generated with the same technical name as the InfoSourceand is assigned to the InfoSource. A proposal for the transfer structure and the transfer rulesis created automatically.

4. Change the transfer structure or the transfer rules where necessary.

The XML data has to be assigned according to an XML schema definition, which isderived from the defintion of the DataSource in BW.

5. Activate the transfer rules.

The transfer structure and the DataSource are likewise activated.

By activating the transfer rules, the %:�'DWD6RXUFH�ZLWK�62$3�&RQQHFWLRQ menu itembecomes active. This means that the creation of an XML DataSource is only possible afteractivating the file DataSource.

You cannot generate an XML DataSource if the file DataSource is not active or if the fileDataSource is in the SAP namespace. Activate the file DataSource or create an additionalDataSource with the prefix 6A by using the &UHDWH�'6 pushbutton in the transfer rulesmaintenance for the DataSource in the SAP namespace.

6. Choose in the InfoSource menu ([WUDV →�&UHDWH�%:�'DWD6RXUFH�ZLWK�62$3�&RQQHFWLRQ

The XML DataSource is then generated in ist own namespace (<xml-datasource> =6A<file-datasource>). The extraction structure is suitably generated for the fileDataSource transfer structure. The field selectability and the XML DataSource delta processare likewise based on the file DataSource. The new DataSource is replicated and is assignedin the Administrator Workbench source system tree to the myself BW System in the deltaqueue application component unter Business Information Warehouse.

For the XML DataSource the RFC-capable function module, which runs the data update in thedelta queue, is suitably generated for the extraction structure.



7. Assign the XML DataSource to the InfoSource.

You get to the transfer rules maintenance screen. The system automatically makes asuggestion for the transfer rules on the basis of the file DataSource.

8. Activate the transfer rules.

5HVXOW

The XML DataSource for transferring data in XML format into BW is available to you.

You activate the delta queue by first creating an InfoPackage for both the myself BW System and theInfoSource/XML DataSource combination then running an initialization without a data request.

From now on the XML data, which is sent to the SOAP Service, is updated in the delta queue.



/RDGLQJ�;0/�'DWD

3UHUHTXLVLWHV

You have created an XML DataSource.

The XML data is available according to the XML schema of the BW file or XML DataSource.

3URFHGXUH

1. To activate the delta queue, create an InfoPackage for your XML DataSource in order to initializewithout a data request.

a. Choose in the 0RGHOLQJ InfoSource tree of the Administrator Workbench ,QIR6RXUFHV�→�<RXU

$SSOLFDWLRQ�&RPSRQHQW�→�<RXU�,QIR6RXUFH�IRU�5HTXHVWLQJ�;0/�'DWD�→�P\VHOI�%:�6\VWHP

→�&UHDWH�,QIR3DFNDJH

b. Enter a description for your InfoPackage in the following dialog box. Select the XMLDataSource and confirm your entries.

c. Maintain the tabstrips. Choose the delta process initialization mode on the 8SGDWH�3DUDPHWHUVtabstrip and select ,QLWLDOL]DWLRQ�:LWKRXW�'DWD�7UDQVIHU.

d. Afterwards, schedule the InfoPackage.

You have now activated the delta queue. This means that the XML DataSource is available asan entry in the delta queue. Thus, it is available for loading XML data. You can check intransaction RSA7 whether or not the DataSource is available as an entry in the delta queue.

2. Send the data to be loaded in XML format using the HTTP port provided under the name/sap/bc/soap/rfc to the SAP Web Application Server SOAP Service.

You find the relevant HTTP port in the Web services maintenance in your BW system. Thereyou can check whether the SOAP service is active. For this, you need to choose *R�WR →�,&0

0RQLWR�in the services maintenance (transaction 6&,)). There, you choose *R�WR�→�6HUYLFHV�The port to be used and the status of the service are displayed in the table for the HTTP log. Ifthe service is deactivated, activate it by using *R�WR�→�6HUYLFH�→�$FWLYDWH�

You can find information about SAP Web Services in the SAP Web Application Serverdocumentation under :HE�$SSOLFDWLRQV�→�6$3�:HE�$SSOLFDWLRQ�6HUYHU�→�,QWHUQHW&RPPXQLFDWLRQ�)UDPHZRUN.

In contrast to BW Staging, loading data into the delta queue occurs by using a datapush into BW.

3. In the SOAP Service, the data is parsed and reclassified in ABAP fields.

You can also find information for reclassifying XML data in ABAP fields underhttp://ifr.sap.com in the ;0/ rubric in the document 6HULDOL]DWLRQ�IRU�$%$3�'DWD�LQ�;0/.

The BW server SOAP interface can ensure guaranteed delivery, since an XMLmessage is returned to the client whether successful or not. If the client has anerror or no message (for example, update termination when sending a successmessage), the client can send the data again.

However, it can then ensure the no guaranteed delivery only once function, sincethere is no reconciliation on a transaction-ID level. On this basis you candetermine that a data package was sent again “in error” and cannot be postedagain. The ODS update can, if the deltas with after-images (delta process AIM)are created, consistently deal with the data that is sent too often, as long as theserialization is secured. The serialization is the task of the client.



4. Afterwards, store the data in the delta queue.

The data is collected here. The delta queue as an inbound queue enables the data that wassent through a push into BW to be collected. In can then be further processed as a request inBW.

5. Load the data [Seite 350] periodically into PSA and in $SSOLFDWLRQ�RI�8SGDWH�5XOHV into the datatarget you want. By placing the data once in the delta queue, you continue to update using theknown staging methods for deltas.

We recommend that you do not load the data more frequently than once an hour fromthe delta queue.

a. Create an InfoPackage in the 0RGHOLQJ InfoSource tree of the Administrator Workbench under,QIR6RXUFHV�→�<RXU�$SSOLFDWLRQ�&RPSRQHQW�→�<RXU�,QIR6RXUFH�IRU�5HTXHVWLQJ�;0/�'DWD�→P\VHOI�%:�6\VWHP, or change the InfoPackage you used for initialization.

b. Maintain the InfoPackage and choose 8SGDWH�0RGH��'HOWD�8SGDWH from the 8SGDWH3DUDPHWHUV�tabstrip.

The selection of the update mode for the file DataSource (which you ran forthe 'DWD6RXUFH�7UDQVIHU�6WUXFWXUH tabstrip in the transfer rulesmaintenance) affects the delta process for the XML data.If you have chosen the update mode $GGLWLYH�'HOWD��2'6�DQG�,QIR&XEH�with the file DataSource, then the delta process is the ABR process forthe XML data. This means that the delta is created from after, before, andreverse images that have to be delivered from the XML data source.If you selected the update modi )XOO�8SORDG��2'6�DQG�,QIR&XEH� or 1HZ6WDWXV�IRU�&KDQJHG�5HFRUGV��2QO\�2'6�, the delta process is the AIMprocess for the XML data. This means that the delta is created from afterimages that have to be delivered from the XML data source.

c. Schedule the data request.

5HVXOW

The data is available in the data target for further consolidation or evaluation.



([DPSOH

0DUNHWSODFHV0DUNHWSODFHV

-DYD�6HUYLFHV-DYD�6HUYLFHV

ZZZZZZ

&RPPHUFLDO�/D\HU��[&%/

;0/�3DUVLQJ

2'6�2EMHFWV��

,QIR&XEHV�

,QIR2EMHFWV

36$

7UDQVIRUPDWLRQ

�;6/��

�� !#"��#��$�%�&��

��'��

��%� �� !"��

'HOWD�4XHXH

(*),+.-�/0(*1�2�3�465�1 %:�6HUYHU

([WHUQDO�

$SSOLFDWLRQV



7KH�6WUXFWXUH�RI�DQ�;0/�'RFXPHQWIn the following example, you see the SOAP-compliant body of an HTTP post request for transferringdata for the XML DataSource 6ATEST with the generated function module /BIC/QI6ATEST_RFC.

&RUUHFW�VWUXFWXUH�RI�DQ�;0/�GRFXPHQW�IRU�WUDQVIHUULQJ�GDWD�WR�%:�

%RG\�RI�DQ�;0/�'RFXPHQW ([SODQDWLRQV

<?xml version="1.0" ?> Marks the header.

<SOAP:Envelopexmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">

Marks the beginning of the SOAPturnover.

<SOAP:Body> Marks the beginning of the body ofdata.

<rfc:_-BIC_-QI6ATEST_RFC xmlns:rfc="urn:sap-com:document:sap:rfc:functions">

Calls the RFC-capable functionmodule /BIC/QI<Techn. Name ofXML DataSource>.

The / character mustbe replaced in theXML document by thecharacter string _- sothat it can be properlyreclassified. Therefore,there is the functionmodule name in theXML document _-BIC_-QI6ATEST_RFC

<DATASOURCE>6ATEST</DATASOURCE> Contains the technical name forthe XML DataSource

<DATA><ITEM>

<VENDOR>JOHN</VENDOR><MATERIAL>DETERGENT</MATERIAL><DATE>20010815</DATE><UNIT>KG</UNIT><AMOUNT>1.25</AMOUNT>

</ITEM><ITEM>

<VENDOR>DAVID</VENDOR><MATERIAL>DETERGENT</MATERIAL><DATE>20010816</DATE><UNIT>ML</UNIT><AMOUNT>125</AMOUNT>

</ITEM>

</DATA>

Contains the data in an XMLwrapper.

The data package is opened with<DATA> and ended with </DATA>.

The file only contains adata package in whichdifferent rows areincluded.

The rows are opened with <item>and closed with </item>.

The field names mustcorrespond to the XMLDataSource technicalnames.

</rfc:_-BIC_-QI60TEST_RFC> Ends the RFC-capable functionmodule /BIC/QI<Techn. Name ofXML DataSource>.

<SOAP:Body> Marks the end of the body of data.



</SOAP:Envelope> Marks the end of the SOAPenvelope.



0HWDGDWD�8SORDG�IRU�6$3�6\VWHPV

3XUSRVH

Data that describes the structure of data or Metaobjects is called Metadata. In BW there are, forexample, the following Metaobjects:

• InfoObjects

• InfoCubes

• ODS Objects

• Queries

• Update rules

• Transfer rules

• DataSources

In the R/3 source system, the DataSource is a Metaobject that is relevant to BW.

The Metadata from SAP source systems is independent of BW Metadata. There is no implicitassignment of objects using same names. Only the information necessary for data extraction is held inthe source system and replicated in BW using a Metadata upload to speed up reading. Theassignment of source system objects to BW objects takes place exclusively and centrally in BW.

��

��

��! "��#%$!� � ��'&(��*) � �+��,-/. � ��0��01

2 � � � � � )��*3+�+�#*4��5 � ��3 � ��,

��768� � )!�03��9��:+�+�0�� <;

=+.?>[email protected]�C@BEGFHE

=+.?>[email protected]�C@�2CIKJ�$L�

;M@�J�E��B@��N�N+N

=��7�7$�I�4HE �OJP@��$!$�4

=��7�7$�I�4HE �OJP@Q$�I�RA$

=��7�7$�I�4HE �OJP@�J I�FB@�SCETI�4

2 � � � � � )��*3+�+� $�:�5�� IQUV�0� � 3��*�0)!3��0)��%��

F1 F2 F4 ...

F1 F2 F3 ...$�� 3��*WT2 � � �

$�� 3��*WT2 � � �

$�� 3��*WT2 � � �

� � ��0��K2 � � �

$!�'UV�X�

SC�� *3�Y!��+�

� � )!�03��Z��:+��0�� [

\^]!_L`']�]�aL`Vbdc�b\fe�a�g+h+i�b a�jk`'g�h/l�g\fe�a�g+h+i�b a�jKa�g/g+i

F5 F6 F7 ...

F5 F8 F9 ...

F5 T1 T2 ...

H1 H2 H3...

� � )!�03��Z��:+��0�� ;

\^]!_L`']�]�aL`Vbdc�b\maKi�g�b ]!j�hn`Pg�hfl�g\maKi�g�b ]!j�hn`na�g�g�i

EG�L& � � � )��*3+�+�$!� � �� 3��0� � �82 � � �

EG�L& � > �'o �+3+�%��A�%�0�p� � )��0�q$!�PUL�%�rSC�� %3�Y��

ET�V& � � � )��%3��OsQET�V& � > �Po �+3+�X�

2 � � � � � )��*3+�+�

EG�L& � > �'o �+3+�%�

t��G� ��

��768� � )��%3��9��:+�+�%�� u[

Metadata that is required for communication between the SAP source system and BW or for the datatransfer is replicated in BW using a Metadata upload.

1. The properties of a DataSource that are required for communication or data transfer are replicatedin BW by a Metadata upload. The Metadata upload thus replicates the DataSources.

Replication of Metadata takes place when you activate the source system.

2. For some applications there is a mechanism that does not just replicate but creates Metadata inBW.

Activating the source system does not create Metadata.

No Business Content Metaobjects are activated, just Metaobjects that are not available inBusiness Content.



8VH

Metadata from a SAP source system is read in the source system using the function 5HSOLFDWH'DWD6RXUFHV�and replicated or created in the SAP Business Information Warehouse. When you createa SAP source system, an automatic Metadata upload is carried out.

You can request the Metadata for a DataSource, the Metadata for an application component, or all theMetadata of a source system:

• To replicate the Metadata of a DataSource, choose 6RXUFH�6\VWHP�7UHH�→�<RXU�6RXUFH�6\VWHPÅ�'DWD6RXUFH�2YHUYLHZ�Å�<RXU�$SSOLFDWLRQ�&RPSRQHQWV�Å�<RXU�'DWD6RXUFH�Å�&RQWH[W�0HQX�ULJKW�PRXVH�FOLFN��Å�5HSOLFDWH�'DWD6RXUFHV�in the BW Administrator Workbench.

• To replicate the Metadata from a source system into BW for an application component, choose6RXUFH�6\VWHP�7UHH�→�<RXU�6RXUFH�6\VWHP�→�'DWD6RXUFH�2YHUYLHZ�→�<RXU�$SSOLFDWLRQ

&RPSRQHQWV�→�&RQWH[W�0HQX��ULJKW�PRXVH�FOLFN��Å�5HSOLFDWH�'DWD6RXUFHV�in the BWAdministrator Workbench.

• To update all the Metadata of a source system, choose 6RXUFH�6\VWHP�7UHH�Å�<RXU�6RXUFH6\VWHP�Å�&RQWH[W�0HQX��ULJKW�PRXVH�FOLFN��Å�5HSOLFDWH�'DWD6RXUFHV in the BW AdministratorWorkbench.

After replicating you get a log that shows you the messages for this Metadata upload. Activities thatare necessary for transferring data from the source system into BW are brought to your attention inthis way.

0HWDGDWD�8SORDG�IROORZLQJ�DQ�8SJUDGH�IURP�%:��%�3OXJ�LQ�WR�%:��3OXJ�LQ

If a request is sent to the source system then a Metadata upload is required. The source system isdeactivated following a Metadata upload. You must then activate the source system in the sourcesystem tree of the BW Administrator Workbench. The relevant communication parameters betweenBW and the source system are matched upon activation and a Metadata upload is carried out. Whenthe source system is active again you can load data into BW.



8SGDWLQJ�0HWDGDWD�IRU�)ODW�)LOHV�RU�([WHUQDO�6\VWHPVFor the Metadata request, the SAP Business Information Warehouse Metadata interface providesBAPI functionality and online transactions for managing InfoSources for external systems.

8SGDWLQJ�0HWDGDWD�IRU�([WHUQDO�6\VWHPV

Technically, Metadata from external systems can be defined or updated manually, or using BusinessApplication Programming Interface functionality (BAPI functionality).

Access the BAPI interface with a third-party tool. Then the third-party extraction tool can automaticallyread the Metadata from the source system without a request from the Business InformationWarehouse, or define the Metadata in the third-party tool and transfer it into BW over the BAPIinterface.

To manually change the Metadata of an external system, enter the requested data in the transferstructure maintenance.

8SGDWLQJ�0HWDGDWD�IRU�)ODW�)LOHV

You can only manually define and update the Metadata for flat files. Enter the requested data in thetransfer structure maintenance.



&KHFN�6RXUFH�6\VWHP

8VH

The source system check for correct configuration includes the

• The RFC connection

• The ALE settings, and

• The BW settings

in relation to BW and source system.

Errors in the configuration are displayed in a log.

$FWLYLWLHV

To do this, choose 6RXUFH�6\VWHP�7UHH�→�<RXU�6RXUFH�6\VWHP�→�&RQWH[W�PHQX��ULJKW�PRXVH�EXWWRQ�

→�&KHFN in the BW Administrator Workbench - Modeling.

6HH�DOVR�

Connection between Source System and BW [Seite 229]



'DWD�0DUW�,QWHUIDFH

3XUSRVH

The data mart interface makes it possible to update data from one data target into another.

You have the following options:

• Data exchange of several BW Systems: The data-delivering system is then referred to as theVRXUFH�%:��the data-receiving system as the WDUJHW�%:� The individual Business InformationWarehouses arranged in such a way are called Data Marts. In this way, the InfoCubes for thesource BW are drawn up as source systems.

See Data Mart Interface Between Several Systems [Seite 262]

• Data exchange between BW Systems and APO Systems

See Data Mart Interface Between Several Systems [Seite 262]

• Data distribution within a BW System (Myself connection)

See Data Mart Interface in the Myself System [Seite 270]

'DWD�PDUWV�FDQ�KDYH�D�UDQJH�RI�IHDWXUHV�

• they save a subset of the data for a Data Warehouse in another database, and wherever possiblein a different location

• they are smaller units of a Data Warehouse

• they are stored intentionally as redundant segments of the (logical, global) overall system (DataWarehouse).

)XQFWLRQV

A Business Information Warehouse represents a source system for another Business InformationWarehouse by:

• offering InfoObjects and InfoSources in the form of Metadata

• retrieving extractors, transaction and master data, as well as texts and hierarchies.

In this way, the data targets for the source BW are presented as DataSources for the target BW. Thetransaction data is extracted from the fact tables of the relevant data target for the source BW. In thetarget BW you can also access the master data of all the InfoObjects that are contained in the datatarget. You can also create export DataSources for InfoObjects out of this context.

&RQVWUDLQWV

• Changes to the Metadata for the source system can only be made here by a regeneration of theexport DataSources.

• The GHOHWH function is not supported at this time.

• You can only generate an export DataSource from an InfoCube if:

− the InfoCube is activated

− the name of the InfoCube is at least one character shorter than the maximum length of aname, since the DataSource name is made up of the InfoCube name and a prefix.

6HH�DOVR�

Assigning a Source System to a Source System ID [Extern]



'DWD�0DUW�,QWHUIDFH�%HWZHHQ�6HYHUDO�6\VWHPV

8VH

The data mart interface can be used between two BW Systems or between an APO System and a BWSystem:

• to enable large amounts of data to be processed

• to increase the respective speeds of data transfer, logging and analysis.

• to achieve improved concision and maintenance of the individual Data Warehouses.

• to enable data separation relating to the task area, on the one hand, and to be able to performanalyses of the state of the entire dataset on the other.

• to make it possible to have fewer complexities when constructing and implementing a DataWarehouse.

• to construct hub and spoke scenarios in which a BW stands in the middle and the data fromdistributed systems runs together and is standardized.

,QWHJUDWLRQ

Data Marts are found in the maintenance and in the definition, the same as in the R/3 source system.Here too, you can group together data from one or more source systems in a BW, or continue to workin several BWs.

)XQFWLRQV

These functions can produce different architectures in a Data Warehouse landscape.

5HSOLFDWLQJ�$UFKLWHFWXUH�

If you select this architecture, the data for a BW server is available as source data and can be updatedin further target BWs.

$JJUHJDWLQJ�$UFKLWHFWXUH�

With aggregating architecture, data is grouped together from two or more BW servers, and is thenavailable for further processing.



Source System 1 Source System 3Source System 2



8VLQJ�WKH�'DWD�0DUW�,QWHUIDFH

3XUSRVH

If you want to define a Business Information Warehouse already in existence as a source system, thenaccess the functions of the Data Marts. With this procedure, a number of systems are connected toeach other. For the connection of the system to itself see Data Mart Interface in the Myself-System[Seite 270].

3URFHVV

7DUJHW�%:7DUJHW�%:6RXUFH�%:6RXUFH�%:

1. Generate Metadata 2. Copy Metadata3. Assign Source System4. Maintain InfoSource 5. Create InfoPackage

6. Load Data

�� ,Q�6RXUFH�%:

Before a BW can request data from another BW, it must have information about the structure of thedata to be requested. To do this, you have to upload the Metadata from the source BW into the targetBW.

You can generate an export DataSource for the respective data target in the source BW. This exportDataSource includes an extract structure, which contains all the characteristics and key figures of thedata target.

For InfoCubes/ODS Objects: See Generating the InfoCube Export DataSource [Seite 266]

For InfoObjects, see Generating the InfoCube Export DataSource [Seite 267].

�� ,Q�WKH�7DUJHW�%:

1. Define the Source System [Seite 230]. This is only necessary if the source system has not yetbeen created in the target BW.

2. If required, create an InfoSource (You can also allow the system to generate an InfoSource, referalso to point 4) and perhaps additional data targets as well.

3. Copy the metadata of your export data source from you source BW into your target BW. You cancopy all metadata in a source system using the source system tree, or you can choose to copyonly the metadata of your InfoSource via the InfoSource tree.

Also refer to Metadata Upload for SAP Systems [Seite 257].

• In the context menu of your InfoSource, choose $VVLJQ�'DWD6RXUFH if you only want tocopy the metadata for your InfoSource.

• Specify your source system.

• From the subsequent dialog window, select your DataSource.

4. Assign your InfoSource to your export DataSource using the context menu in the DataSource tree.

Also refer to Assigning DataSources to InfoSources and Fields to InfoObjects [Seite 242]

You can adopt the InfoSource suggested by the application. In this case, an InfoSource isgenerated or an InfoSource that you created is specified.



5. Create transfer rules for your InfoSource. This function can be found in the context menu in theDataSource tree and also in the InfoSource tree.

6. Go into the InfoSource tree, if you are not already there, and create an InfoPackage for yoursource BW under your InfoSource.

Also refer to Transferring Transaction Data for the Data Mart Interface [Seite 268] andTransferring Texts and Hierarchies for the Data Mart Interface [Seite 269].

If your InfoSource was generated by the system, it is possibly not yet displayed in theInfoSource tree. In this case, you need to display it using 6HWWLQJV�→ 'LVSOD\�*HQHUDWHG2EMHFWV in�the main menu.

7. Schedule the InfoPackage.

5HVXOW

You have loaded data from a Business Information Warehouse into an additional BW.



*HQHUDWLQJ�WKH�,QIR&XEH�([SRUW�'DWD6RXUFH

8VH

The export DataSource is needed to transfer data from a source BW into a target BW.

3UHUHTXLVLWHV

The source BW must be created and actively saved in the target BW as BW source system [Seite230]defined. The steps to be carried out correspond to those for the automatic creation of an R/3source system.

You must first check the data contents of the InfoProvider.

)XQFWLRQV

You can use the selected InfoProvider as an InfoSource for another system. The relevant exportDataSource is not displayed in the InfoSource tree of the source BW.

The Metadata of an export DataSource is generated as it exists in the source BW. This also includesthe procedure for external systems.

$FWLYLWLHV

1. Select the InfoProvider tree in the Administrator Workbench in the source BW.

2. Generate the export DataSource from the context menu of an InfoProvider.

The technical name of the export DataSource is derived from the number � together withthe name of the data target. Therefore, when you create an InfoProvider or a transactiondata InfoSource in the source BW, please make sure that the length of the technical nameof each object is no longer than 29 characters.

Technical name of an InfoCube: &23$

Technical name of the export InfoSource:��&23$



*HQHUDWLQJ�WKH�0DVWHU�'DWD�([SRUW�'DWD6RXUFH

8VH

The export DataSource is needed to transfer data from a source BW into a target BW.

You can generate an export DataSource for master data, and thus also for individual InfoObjects. Bydoing this all the Metadata is created that is required to extract master data from an InfoObject (forexample, all attributes and hierarchies that have been created for this InfoObject).

3UHUHTXLVLWHV

The source BW must be created and actively saved in the target BW as BW source system [Seite230]. defined. The steps to be carried out correspond to those for the automatic creation of an R/3source system.

The data content of the data target is activated.

)XQFWLRQV

You can use the selected DataSource as a DataSource for another system. The relevant exportDataSource is not displayed in the InfoSource tree of the source BW.

The Metadata of an export DataSource is generated as it exists in the source BW. This is the same forprocedures using external systems.

$FWLYLWLHV

3. Select the InfoSource tree in the Administrator Workbench in the source BW.

4. Generate the export DataSource from the context menu of a master data InfoCube.

The technical name of the export DataSource is called

8******M. for attributes (M stands for ’master data’)

8******T for texts.

8******H for hierarchies.

(The asterisks (*) stand for the source InfoObject.)

Therefore, when you create an InfoObject or a master data InfoSource in the source BW,please make sure that the length of the technical name of each object is no longer than 28characters.



7UDQVIHUULQJ�7UDQVDFWLRQ�'DWD�IRU�WKH�'DWD�0DUW�,QWHUIDFH

8VH

The transfer of transaction data is scheduled in the Scheduler [Seite 351]. It corresponds to the datatransfer for an R/3 System. The system reads the data while taking into account the specifieddimension-specific selections from the fact table of the delivered Business Information Warehouse.

'HOWD�3URFHVV

When transferring transaction data, requests can be used to determine a GHOWD.

The distinction is made between InfoCube and ODS objects.

• The InfoCube that is used as an export-DataSource is first initialized , meaning that the currentstatus is transferred into the target BW. When the next upload comes around only those requestswill then be transferred that have come in since the time of initialization. Different target systemscan also be supplied like this.

Only those requests are transferred that have been rolled up successfully in theaggregates. If no aggregates were used only those requests are transferred that are set to’qualitative OK’ in the InfoCube Administration [Seite 413] .

• For ODS objects the requests are used as the basis for determining delta, which are in the changelog of the ODS object. Only the change log requests which have arisen from reactivating the ODSobject data are transferred.

5HVWULFWLRQ�

It is only possible to make a selection per target system for the delta

You first make a selection using FRVW�FHQWHU�� and load deltas for this selection. At a latertime you also decide to load a GHOWD�IRU�FRVW�FHQWHU�� in parallel to WKH�FRVW�FHQWHU��GHOWDThe delta can only be requested wholly for both centers, meaning that it is then impossibleto separately execute deltas for the different selection.

6HH�DOVR�

Update Functions [Seite 368]

Procedure for R/3 Systems [Seite 352]



7UDQVIHUULQJ�7H[WV�DQG�+LHUDUFKLHV�IRU�WKH�'DWD�0DUW,QWHUIDFH

'HILQLWLRQ

The transfer of master data is scheduled in the Scheduler [Seite 351]. It corresponds to the datatransfer for an R/3 System.

If you want to load texts using the Scheduler, you must first create them in the source system.

When you load hierarchies, you get to the available hierarchyes from the 6HOHFW�+LHUDUFK\ tabstrip byusing the pushbutton $YDLODEOH�+LHUDUFKLHV�LQ�2/73. Select your hierarchy and schedule the loading.

6HH�DOVR�

Master Data Types: Attributes, Texts, and Hierarchies [Seite 94]



'DWD�0DUW�,QWHUIDFH�LQ�WKH�0\VHOI�6\VWHP

8VH

The data mart interface in the Myself System is used to connect the BW System to itself. This meansyou can update data from data targets into other data targets within the system.

)XQFWLRQV

You can import InfoCube data by InfoSource into BW again and, thereby, fill another InfoCube. Youcan carry out a data clean-up, for example, using transfer rules and update rules.

You can update data directly from ODS objects into other data targets, since the ODS data can beused directly as a DataSource in the same system.

ODS-ServerODS-Server

��

2'6�2EMHFW

��

! �"� !$#&% '� �

(*) �,+�-��. 0/

,QSXW�6FHQDULR�IRU�8SGDWLQJ�2'6�'DWD�LQWR�DQRWKHU�2'6�2EMHFW�

Updating ODS data into another ODS object makes it possible to track the status oforders, that is, which orders are open, delivered in part etc. The data about orders anddeliveries are in two separate ODS objects. In order to trace the status in reporting,update the data in another ODS object and merge the objects together.

Also refer to Implementation Scenario for ODS Objects [Seite 164].



,QIR6RXUFH-{}-

'HILQLWLRQ

In BW, an InfoSource describes the quantity of all the data available for a business transaction or atype of business transaction (for example, cost center accounting).

An InfoSource is a quantity of information that logically belongs together, summarized into a singleunit. InfoSources contain either transaction data or master data (attributes, texts and hierarchies).

An InfoSource is always a quantity of InfoObjects [Seite 28] that logically belong together. Thestructure in which these are stored is called a communication structure.

8VH

Data that logically belongs together is stored in the source systems as DataSources. A DataSource isan object that, at the request of BW, makes data available in one of its predetermined structures. Theproperties of a DataSource that are relevant to BW are copied into the BW system.

In the BW Transfer rules - Maintenance [Seite 285], individual DataSource fields are assigned to thecorresponding InfoObject of the InfoSource. You also determine here, which data is actuallytransferred from an extract structure of a DataSource to the communication of an InfoSource.

The transfer structure is used for the data transfer. The data is transferred 1:1 from the transferstructure [Seite 283] of the source system into the BW transfer structure.

,QWHJUDWLRQ

If fields that logically belong together exist in various source systems, they can be grouped togetherinto a single InfoSource in BW. The particular release of the source system is not important here.

Data Provider

,QIR&XEHV�

2'6�REMHFWV

%XVLQHVV�,QIRUPDWLRQ:DUHKRXVH�6HUYHU

6WDJLQJ�(QJLQH

Source system 1 Source system 2

��

8SGDWH�UXOHV8SGDWH�UXOHV

,QIR6RXUFH

Communications structureCommunications structure

Extract structureExtract structure Extract structureExtract structure'DWD6RXUFH

'DWD6RXUFH(Copy)

TransferstructureTransferstructure

Transfer structureTransfer structure Transfer structureTransfer structure

Transfer structureTransfer structure

If you are dealing with an InfoSource with flexible updating, then the data is loaded from thecommunication structure into the InfoCube with the aid of the update rules [Seite 201]. InfoSourceswith direct updating permit master data to be written directly (without update rules) into the masterdata tables.

InfoSources are listed in the InfoSource tree of the Administrator Workbench under an applicationcomponent.



,QIR6RXUFH�7\SHVThere are basically two types of InfoSources.

• InfoSources with flexible updating

• InfoSources with direct updating

In both cases uploaded data is transformed by the transfer rules, which have been created for thecurrent combination of InfoSource and source system and for each InfoObject of the communicationstructure. A data target can be defined by several InfoSources which in turn can be defined by severalsource systems.

An InfoSource for hierarchies can only be defined by one source system.

,QIR6RXUFHV�ZLWK�)OH[LEOH�8SGDWLQJ

For an InfoSource with flexible updating, the data from the communications structure is loaded into thedata targets (InfoCubes, ODS objects, master data) using update rules [Seite 201]. Several datatargets can be defined by one InfoSource. The InfoSource can contain transaction data as well asmaster data.

This function is not implemented for hierarchies.

Before Release 3.0A only transaction data could be updated flexibly and it was only possible to updatemaster data directly. Master data InfoSources were therefore distinguished from transaction dataInfoSources. This is no longer the case with Release BW 3.0A since both transaction data and masterdata can be updated flexibly. You therefore cannot immediately see if it the InfoSource handlestransaction data or master data with flexible updating. You should therefore specify which is the casewhen you define an InfoSource.

,QIR6RXUFH��,QIR6RXUFH��

2'6�2EMHFW

8SGDWH�5XOHV

��

��

2'

6�2

EMH

FWV

0DVWHU'DWD7DEOH

��

�7UDQVDFWLRQ�RU�0DVWHU�'DWD�

)OH[LEOH�8SGDWLQJ��'DWD�)ORZ

<RX�KDYH�WKH�IROORZLQJ�XSGDWH�RSWLRQV�

• The data from InfoSources with master data or transaction data can be stored directly in ODSobjects.



• You can then update from ODS objects into further ODS objects, InfoCubes or master data tablesusing update rules.

• It is also possible to update in InfoCubes or master data tables without having to switch betweenODS objects.

,QIR6RXUFHV�ZLWK�'LUHFW�8SGDWLQJ

Master data (characteristics with attributes, texts or hierarchies) of an InfoObject can be updateddirectly (without update rules, only using transfer rules) to the master data table with an InfoSourcewith direct updating. To do this you must assign it application components. The characteristic issubsequently displayed in the InfoSource tree in the Administrator Workbench. You are able to assignDataSources and source systems to the characteristic from here. You are also able to load masterdata, texts, and hierarchies for the characteristic.

In the following cases you are not able to use an InfoObject as an InfoSource with direct updating:

• The characteristic that you want to modify is characteristic 0SOURSYSTEM (source system ID).

• The characteristic has no master data, texts, or hierarchies. It is therefore impossible to load datafor the characteristic.

• The characteristic that you want to modify turns out to be a unit or a key figure.

To generate an export DataSource for a characteristic, the characteristic must also be an InfoSourcewith direct updating.



6FHQDULRV�IRU�)OH[LEOH�8SGDWLQJ

��$WWULEXWHV�DQG�WH[WV�DUH�GHOLYHUHG�WRJHWKHU�LQ�D�ILOH�

��

��

�� "!�#�$&%

')( ��*�+ ,�-.�/0��,��&� ��1��32�45�1��6��78�� 9

Your master data, attributes, and texts are available together in a flat file. You are updated by anInfoSource with flexible updating in additional InfoObjects. In doing so, texts and attributes can beseparated from each other in the communication structure.

Flexible updating is QRW necessary if:

• texts and attributes are available in separate files/DataSources. In this case, you can choosedirect updating if additional transformations using update rules are not necessary.

��$WWULEXWHV�DQG�WH[WV�FRPH�IURP�VHYHUDO�'DWD6RXUFHV�

��

��:�&�� "��6�:�� ;�&��

�� "!�#�$&% �=<&<.�>��3-.1�2&4��&��

? �62��/0-8��1��

? ��@�� 2&4A�2��62 ? -.&� *��

')( ��*�+ ,�-.�/0��,��&� ��1��32�45�1��6��78�� 9

This scenario is similar to the one described above, only slightly more complex. Your master datacomes from two different source systems and delivers attributes and texts in flat files. They aregrouped together in an InfoSource with flexible updating. Attributes and texts can be separated in thecommunication structure and are updated further in InfoObjects. The texts or attributes from bothsource systems lie in these InfoObjects.



��0DVWHU�GDWD�LQ�WKH�2'6�OD\HU�

,QIR6RXUFH�ZLWK�0DVWHU�'DWD�,QIR6RXUFH�ZLWK�0DVWHU�'DWD�

8SGDWH�5XOHV

�� 1�2�� )�*( )� � 1�5 �

�� 4��1 �� - � 2 � ��1�2 �

�� 1�2� ��

� �� 1�2 �

�� 1�2� ��

� 1�� 2

A master data InfoSource is updated to a master data ODS object with flexible updating. The data cannow be cleaned and consolidated in the ODS object before being re-read.

These cleaned objects can now be updated to further ODS Objects. The data can also be selectivelyupdated using routines in the update rules. This enables you to get views of selected areas.

A master data ODS object generally makes the following options available:

• It displays an additional level on which master data from the whole enterprise can be consolidated.

• ODS objects can be used as a validation table for checking the referential integrity [Seite 282] ofcharacteristic valuables in the update rules.

• It can serve as a central repository for master data, in which master data is consolidated fromvarious systems. They can then be forwarded to further BW systems using the Data Mart.



&UHDWLQJ�,QIR6RXUFHV��5��6RXUFH�6\VWHP�

8VDJH

Instead of creating a new InfoSource, you can copy one from the SAP Business Content [Seite 21].

3URFHGXUH

Select the InfoSource tree of the Administrator Workbench to create InfoSources for an R/3 sourcesystem. Using the context menu, choose &UHDWH�,QIR6RXUFH from the relevant application component.

1. Select the type [Seite 273]�

2. Under ,QIR6RXUFH� enter the technical name of the InfoSource, and then a description.

You can also use an existing InfoSource as a template.

3. Assign a source system to the InfoSource and confirm.

4. From the proposal list, select the DataSource from which transaction data is to be loaded.

You go automatically to the transfer structure maintenance.

The system will automatically offer you suitable transfer rules, but you can modify these.

5. Maintain the transfer structure [Seite 284]. Assign InfoObjects to the fields of the DataSource.

6. The communications structure [Seite 279] is adjusted automatically, but you can also include morefields. Activate your selection.

7. Maintain the transfer rules [Seite 285]

8. Activate the InfoSource.

5HVXOW

The InfoSource is now saved and active.



&RPPXQLFDWLRQ�6WUXFWXUH

'HILQLWLRQ

The communication structure is localized in the SAP Business InformationWarehouse and displays the structure of the InfoSource. It contains all of theInfoObjects belonging to the InfoSource of the SAP Business InformationWarehouse.

8VH

Data is updated in the data targets of this structure. In this way, the system alwaysaccesses the actively saved version of the communication structure.

In the transfer rules maintenance, you determine whether the communicationstructure is filled with fixed values from the transfer structure fields, or using a localconversion routine.

Conversion routines are ABAP programs that you can create yourself. The routinealways refers to just one InfoObject of the transfer structure.



0DLQWDLQLQJ�&RPPXQLFDWLRQV�6WUXFWXUHV�ZLWK�)OH[LEOH8SGDWLQJ

8VH

Assign the fields of a DataSource to the corresponding InfoObjects of the InfoSource. Although theDataSource contains source system fields that belong together, you can combine fields that logicallybelong together from several DataSources, from various source systems in the communicationstructure.

3UHUHTXLVLWHV

You have created an InfoSource with flexible updating.

3URFHGXUH

You can get to the maintenance of the communication structure using the InfoSource tree of theAdministrator Workbench.

1. Choose <RXU�$SSOLFDWLRQ�&RPSRQHQWV → <RXU�,QIR6RXUFH → &RQWH[W�PHQX �ULJKW�PRXVH�FOLFN� →&KDQJH.

• You can enter the required InfoObjects directly into the left-hand column of thecommunication structure. You can also select InfoObjects using F4 Help, or create newcharacteristics and key figures by using the toolbar.

• If you have already assigned a source system and a communication structure alreadyexists with transfer rules and transfer structure, then you are displayed the InfoObjectsfrom the transfer structure in the template. You can select InfoObjects and transfer orremove them from the template into the communication structure using the arrow.

2. You can also define that the referential integrity should be checked. You can set the InfoObjectsthat should be checked. A check against the master data ODS object, if it exists, always makessense. Alternatively you can check against the master data table.

Also refer to Checking for Referential Integrity [Seite 282].

In the InfoObject maintenance you can define the ODS object against which you want tocheck. See also Tabstrip: Master Data/Texts [Seite 56].

3. Check your entries and save.

You can only use the InfoObjects of the communication structure in the update rules if youhave activated your entries.

If a communication structure already existed in an active version, then the system alwaysreverts back to this when maintaining the update rules. The version of the communicationstructure, which was created by a simple save, is not used.

InfoObjects of the communication structure, which are used in the update rules or in thetransfer rules, cannot be removed from the communication structure.

If an InfoObject is used, the corresponding fields in the communication structuremaintenance are highlighted.

5HVXOW

You have determined InfoObjects that can be updated in the data targets.



0DLQWDLQLQJ�&RPPXQLFDWLRQV�6WUXFWXUHV�IRU�DQ�,QIR6RXUFHZLWK�'LUHFW�8SGDWLQJ

8VDJH

Assign the fields of a DataSource to the corresponding InfoObjects of the InfoSource. Although theDataSource contains source system fields that belong together, you can combine fields that logicallybelong together from several DataSources, from various source systems in the communicationstructure.

3UHUHTXLVLWHV

You have created an InfoSource with direct updating. You have assigned a source system and a datasource to it.

3URFHGXUH

After you have assigned the source system, you automatically go to the transfer structuremaintenance.

1. Maintain the transfer structure [Seite 284] and the transfer rules [Seite 285] in the lower half of thescreen.

In the upper half of the screen, you can view the communication structure. The systemautomatically generates this.

Depending on whether you have specified a DataSource for attributes or texts, thecommunication structure contains the attributes or text fields next to the correspondingInfoObject.

If you have entered a DataSource for hierarchies then the upper half of the screen(communication structure) is hidden.

2. Activate your settings.



&KHFN�IRU�5HIHUHQWLDO�,QWHJULW\

8VH

The check for referential integrity occurs for transaction and master data if they are flexibly updated.You determine the valid InfoObject values.

3UHUHTXLVLWHV

The check for referential integrity functions only in conjunction with the function (UURU�+DQGOLQJ on thescheduler tab page 8SGDWH�3DUDPHWHU.

See also Treating Data Records with Errors [Seite 375].

In order to use the check for referential integrity, you have to choose the option $OZD\V�8SGDWH�'DWD��. If you choose the option Do Not Update Data..., you override the check for referential integrity. This isvalid for master data (with flexible updating) as well as for transaction data.

)XQFWLRQV

The verification occurs after filling the communication structure and before filling the update rules.What is displayed in the InfoObject metadata is checked against the master data table (that means theSID table) or against another ODS object.

If you create an ODS object for checking the characteristic values in a characteristic, in the updaterules and in the transfer rules, the valid values for the characteristic are determined from the ODSobject and not from the master data.



7UDQVIHU�6WUXFWXUH

'HILQLWLRQ

The transfer structure is the structure in which the data is transported from the source system into theSAP Business Information Warehouse.

It provides a selection of the extract structure fields for the source system.

8VH

The transfer structure provides BW with all the source system information available for a businessprocess.

An InfoSource in BW requires at least one DataSource for data extraction. DataSource data thatlogically belongs together is staged in an extract structure in an SAP source system.

In the transfer structure maintenance, you determine which extract structure [Seite 243] fields aretransferred to the BW. When you activate the transfer rules in BW, an identical transfer structure forBW is created in the source system from the extractor structure.

This data is transferred 1:1 from the transfer structure of the source system into the BW transferstructure, and is then transferred into the BW communication structure using the transfer rules.

A transfer structure always refers to a DataSource from a source system and an InfoSource in BW.

You get to the maintenance of the transfer structure using the InfoSource tree of the AdministratorWorkbench. The context menu of the source system belonging to an InfoSource provides you with themaintenance marker using the function 0DLQWDLQ�7UDQVIHU�5XOHV�



0DLQWDLQLQJ�7UDQVIHU�6WUXFWXUHV

8VH

In the transfer structure maintenance, you specify which fields for a DataSource are to be transferredinto a communication structure.

3UHUHTXLVLWHV

You have created an InfoSource. You have maintained a communications structure.

A maintained communication structure is required for the procedure described in thefollowing. It is however also possible for you to create the InfoSource first, then maintainthe communication structure and finally assign the source system.

3URFHGXUH

1. Select a source system.

2. Select a DataSource that has already been connected using F4 Help or add a new DataSourceusing $VVLJQ�'DWD6RXUFH�

The fields for the DataSource are displayed in the right half of the tabstrip transfer structure.These are transferred to the left half in the transfer structure by default.

3. Maintain the transfer rules [Seite 285]



3URFHVVLQJ�7UDQVIHU�5XOHV

8VH

When you have maintained the transfer structure and the communication structure, you can use thetransfer rules to determine how the transfer structure fields are to be assigned to the communicationstructure InfoObjects. You can arrange for a 1:1 assignment. But you can also fill InfoObjects usingroutines or constants.

You need not assign InfoObjects to each field of the transfer structure. If you only need afield for entering a routine or for reading from the PSA, then you need not create anInfoObject.

But you must keep the following in mind: A conversion of key figures into SAP format isbased on the information of the InfoObject when you load from non-SAP systems. In thiscase you must assign the field an InfoObject. Otherwise wrong numbers might be loadedor the numbers might be displayed incorrectly in reporting.

3UHUHTXLVLWHV

Before you can maintain the transfer rules for an InfoSource, you must assign a source system to theInfoSource and have created a communication structure.

3URFHGXUH

1. You maintain the transfer rules using the InfoSource tree of the Administrator Workbench.

For InfoSources choose <RXU�$SSOLFDWLRQ�&RPSRQHQWV → <RXU�,QIR6RXUFH → &RQWH[W�PHQX

�ULJKW�PRXVH�FOLFN� → &KDQJH.

2. Select a transfer method.

The transfer structure is displayed in the right half with the selected DataSource fields.

With the help of the data elements, the system proposes InfoObjects that could be assigned tothe corresponding fields for the DataSource in the left column of the transfer structure

The fields for which the system cannot provide any proposals remain empty.

3. Using the &RQWH[W�0HQX��ULJKW�PRXVH�EXWWRQ� → (QWU\�2SWLRQV or F4 Help, you can selectInfoObjects that are to be assigned to the DataSource fields, or you can create an assignmentwith the help of the same data elements or field names.

It is not necessary to have assigned InfoObjects to all DataSources fields at this time. Usingthe transfer rules, you can also fill the InfoObjects for the communication structure with aconstant or from a routine.

4. In the left half of the screen, you will see the communication structure InfoObjects as well as thetransfer rules that the system proposes.

By selecting one row in both the left and the right-hand side, you can use the arrows to assignfields of the transfer structure to the InfoObjects of the communications structure.

Remove fields that are not required from the transfer structure. This improvesperformance, as otherwise data is extracted even though you have not selected it.

5. You can create a start routine [Seite 287] by loading data from the PSA.

This improves performance for example when you check if a certain request already exists inan ODS object and it is made consistent with the update rules.

6. You can enhance or modify the proposed transfer rules.

To do this, select a transfer rule type by clicking on the type symbol in the row you want:



• ,QIR2EMHFW��The fields are transferred from the transfer structure and are not modified.

Execute the function 'HIDXOW�WUDQVIHU�UXOHV to assign fields of the transfer structure tothose of the communication structure.

• &RQVWDQWV��An InfoObject is filled by a fixed value.

You could, for example, assign the fixed value US to the InfoObject 0COUNTRY.

• )RUPXOD: An InfoObject is filled with a value that is determined with a formula [Seite 217].

• 5RXWLQH� An InfoObject is filled from a local transfer routine.

Local transfer routines are ABAP programs that you can create, modify or transfer. Theroutine only affects the selected InfoObject in the relevant communication structure.

For an explanation of the procedure see Creating Transfer Routines [Seite 288].

7. Activate the transfer rules. Data can only be loaded from the source system in an activatedversion.

The status of the transfer rules should be displayed with a green or a yellow traffic light.

Since not all the fields of the transfer structure have to be transferred into the communicationstructure, you can, however, already activate the transfer rules with just one assigned field.The status is then displayed with a yellow traffic light.

A red traffic light indicates an error. The transfer rules cannot then be activated.

5HVXOW

You have ensured that the communication structure can be filled.



6WDUW�5RXWLQH�LQ�7UDQVIHU�5XOHV

8VH

You can create a start routine in the transfer rule maintenance. This start routine is executed for eachdata package once the data has been written to the PSA and before the transfer rules have beenexecuted. The entire data package in the transfer structure format is used as parameter.

)XQFWLRQV

You can change the data package by adding or deleting records.

If you add or delete records, this might not be detected by the error handling.

The start routine contains a return parameter that causes processing of the entire package to beterminated with an error message for values <> 0.

You can only create a start routine for transfer method PSA. The routine is not displayed ifyou switch the transfer method to IDoc.

For general information about routines see Update Routines [Seite 219].



&UHDWLQJ�7UDQVIHU�5RXWLQHV

3URFHGXUH

1. In the transfer rule maintenance screen choose &UHDWH�URXWLQH for the relevant InfoObject.

2. For the transfer rule choose 5RXWLQH�→ &UHDWH�in the dialog box.

3. Specify a name for the local transfer routine that you have created.

4. You have the option of using transfer structure fields in the routine. You can choose between

• No fields:

The routine does not use any source structure fields. Make this selection when youdetermine the user name from a system variable (SY-UNAME), for example.

• All fields:

The routine uses all source structure fields. In contrast to explicitly selecting all fields (seebelow), this option also includes fields that are added to the source structure later.

• Selected fields:

If you make this selection, you have to explicitly select the fields used. Also in the programeditor for implementing routines, only the selected fields are available to you in this case.

You need these settings, for example when using SAP RemoteCubes, so that you canalso determine the transfer structure fields for InfoObjects that are filled using transferroutines.

Choose 1H[W. You get to the transfer routine ABAP editor.

5. Create a local transfer routine or change an existing routine.

You can not delete the fields used in the routines from the transfer structure. They aredisplayed in the where-used list

For SAP RemoteCubes you may have to create an inversion routine for transaction data.




0DLQWDLQLQJ�,QIR6RXUFHV��)ODW�)LOHV�

3XUSRVH

You can load data from flat files (CSV or ASCII files) into BW.

You can load the following data types:

1. Transaction Data [Seite 290]

2. Master Data [Seite 294]

• Attributes

• Texts

3. Hierarchies [Seite 296]

3UHUHTXLVLWHV

Please note the following regarding Excel CSV files:

• Excel files use delimiters to separate fields. In the European version, the delimiter “;” is used. Youcan also use other delimiters. You must specify the delimiter used in the Scheduler.

• Fields that are not filled in an Excel CSV file are filled with a blank character in the case of fieldcharacters.

• If the delimiters have been used inconsistently in an Excel CSV file, the “wrong” delimiter is readas a character, and both fields are brought together and possibly cut short. The following fields arethen no longer in the correct order.

Please note the following regarding Excel CSV files, such as ASCII files:

• If your file contains headers that you do not want to load, enter how many headers should beignored during loading on the tabstrip ([WHUQDO�'DWD�3DUDPHWHUV in the Scheduler. This gives youthe option of keeping the column headers in your file.

• Depending on the conversion exit, either enter or do not enter a zero at the beginning.

• For entering the date, use as a rule the format ‘YYYYMMDD’ without internal delimiters.Depending on the conversion exit, you can also use other formats.

• If you upload data using IDocs, make note of the 1.000 byte limit per data record length. This limitdoes not apply for uploading data with the PSA.

1RWHV�RQ�8SORDGLQJ

• When you upload external data, you have the option of loading the data from any workstation intoBW. From a performance point of view, however, you should store the data onto an applicationserver and load it from there into BW. In this way, you can load the data in the background.

• If you want to upload a large amount of transaction data from a flat file using the IDoc loadingmethod, and if you have the option of specifying the file type of the flat file, you should create theflat file as an ASCII file. From a performance point of view, uploading the data from an ASCII file isthe most cost-effective method. Generating an ASCII file might mean a larger workload.



8SORDGLQJ�7UDQVDFWLRQ�'DWD�IURP�)ODW�)LOHV

3URFHGXUH

�� 'HILQLQJ�WKH�VRXUFH�V\VWHP�IURP�ZKLFK�\RX�ZDQW�WR�ORDG�GDWD

Choose 6RXUFH�6\VWHP�7UHH�→5RRW��VRXUFH�V\VWHP��→&RQWH[W�PHQX��ULJKW�PRXVH�EXWWRQ�

→&UHDWH�

With flat files, choose: )LOH�6\VWHP��0HWDGDWD�PDQXDO��'DWD�YLD�ILOH�LQWHUIDFH.

�� 'HILQLQJ�WKH�,QIR6RXUFH�IRU�ZKLFK�\RX�ZDQW�WR�ORDG�GDWD

Optional: Choose ,QIR6RXUFH�7UHH�→5RRW��,QIR6RXUFHV��→ &RQWH[W�0HQX��ULJKW�PRXVH

EXWWRQ��→ &UHDWH $SSOLFDWLRQ�&RPSRQHQW�

Choose ,QIR6RXUFH�7UHH →<RXU�$SSOLFDWLRQ�&RPSRQHQW → &RQWH[W�0HQX��ULJKW�PRXVH

EXWWRQ��→ &UHDWH�,QIR6RXUFH�→�)OH[LEOH�8SGDWLQJ�� and enter a name and a description.

�� 0DLQWDLQLQJ�WKH�FRPPXQLFDWLRQ�VWUXFWXUH��'HILQLQJ�WKH�ILHOGV�IRU�WKH�IODW�ILOHV�DV�,QIR2EMHFWVLQ�%:�

Specify an InfoObject for each column of your flat file.

You can either use existing InfoObjects or create new ones.

Please refer to



The columns sequence in your communication structure does QRW have to correspond tothe columns sequence in your flat files.

Activate the communication structure.

�� $VVLJQLQJ�WKH�VRXUFH�V\VWHP�WR�WKH�,QIR6RXUFH

Expand the 7UDQVIHU�VWUXFWXUH��7UDQVIHU�5XOHV in the lower half of your screen and select yoursource system.

A proposal for the DataSource, the transfer rules, and the transfer rules is createdautomatically.

�� 0DLQWDLQLQJ�WKH�WUDQVIHU�VWUXFWXUH��WUDQVIHU�UXOHV

Change the transfer structure or the transfer rules where necessary.

Pay particular attention here to the Features for Uploading Transaction Data from a Flat File[Seite 292]

The columns sequence in the transfer structure must correspond to the columns sequence inyour flat file. If you do not use the same sequence, the corresponding transfer structure is notfilled correctly.

Activate the transfer structure / transfer rules.

)XUWKHU�6WHSV�

Maintaining InfoCubes [Seite 110]


Maintaining InfoPackages [Seite 351]

Checking the Data Loaded into InfoCubes [Seite 117]



0DLQWDLQLQJ�7UDQVDFWLRQ�'DWD�,QIR6RXUFHV�XVLQJ�)ODW�)LOHV

3XUSRVH

If you want to load data from a flat file into BW, manually maintain the relevant transfer structure andtransfer rules in BW. There is no function for automatically uploading metadata.

3URFHVV

In the transfer structure maintenance, specify an InfoObject for every field of your flat file, making surethat the VHTXHQFH of the InfoObjects corresponds to the sequence of the columns in your flat file. Ifyou do not use the same sequence, the corresponding transfer structure will not be filled correctly.

For the flat file structure,

19980101;0001;23

the corresponding transfer structure could look like this:

0CALDAY

PRONR

PROPRICE

0CALDAY describes the date (01.01.1998) as an SAP time-characteristic, PRONRdescribes the product number (0001) as the characteristic, and PROPRICE describes theproduct price as the key figure.

Specify the GDWD�W\SHV according to the fields that you want to upload from the flat file.

If the data for your flat file was staged from an R/3 system then there are no problemswhen transferring data types into BW. Please note that you might not be able to load thedata types DEC and QUAN for flat files with external data. Specify type CHAR for thesedata types in the transfer structure. When you load, these are then converted into the datatype, which you specified in the maintenance of the relevant InfoObject in BW.

If you want to load an exchange rate from a flat file, the format must correspond to thetable TCURR.

You must select a suitable XSGDWH�PRGH from the transfer structure maintenance screen, to makesure you use the correct update type.

• Full Upload (ODS and InfoCube)

The DataSource does not support delta updates. With this procedure a file is always copied inits entirety. You can use this procedure for ODS objects and for InfoCubes.

• Latest status of changed records (ODS only)

The DataSource supports both full updates and delta updates. Every record to be loadeddefines new status for all key figures and characteristics. This procedure should only be usedwhen you load ODS objects.

• Additive Delta (ODS and InfoCube)

The DataSource supports both full updates and additive delta updates. The record to beloaded only provides the change in the key figure for key figures that can be added. You canuse this procedure for ODS objects and for InfoCubes.

([DPSOH�RI�ORDGLQJ�IODW�ILOHV�

The customer orders 100001 and 100002 are transferred to BW with a delta initialization.

Delta initialization:



'RFXPHQW1R�

'RFXPHQW,WHP

�� 2UGHU�4XDQWLW\ 8QLW�RI0HDVXUH

��

100001 10 200 Pieces

100001 20 150 Pieces

100002 10 250 Kg

After the delta initialization, the order quantity of the first item in customer order 100001 isreduced by 10% and the order quantity of the second item increased by 10%. There arethen two options for the file upload of the delta in an ODS Object.

1. Option: Delta process shows the latest status for modified records (applies to ODSObject only):

'RFXPHQW1R�

'RFXPHQW,WHP


��

100001 10 180 Pieces

100001 20 165 Pieces

CSV file:

100001;10;...;180;PCS;...

100001;20;...;165;PCS;...

2. Option: Delta process shows the additive delta (applies only to InfoCube/ODS object):

'RFXPHQW1R�

'RFXPHQW,WHP


��

100001 10 -20 Pieces

100001 20 15 Pieces

CSV file:

100001;10;...;-20;PCS;...

100001;20;...;+15;PCS;...

To make sure that the data is uploaded in the correct structure, you can look at it in the preview andsimulate the upload. See Preview and Simulation of Loading Data from Flat Files [Seite 302].

5HVXOW

You have maintained the metadata for the transaction data InfoSource and can now upload the datafrom the flat file.



8SORDGLQJ�0DVWHU�'DWD�IURP�)ODW�)LOHV

3URFHGXUH


Choose 6RXUFH�6\VWHP�7UHH�→ 5RRW��VRXUFH�V\VWHP��→ &RQWH[W�PHQX��ULJKW�PRXVH�EXWWRQ�

→ &UHDWH�





Choose ,QIR6RXUFH�WUHH → <RXU�DSSOLFDWLRQ�FRPSRQHQW → &RQWH[W�PHQX��ULJKW�PRXVH�EXWWRQ�

→ &UHDWH�,QIR6RXUFH�→�$WWULEXWHV��7H[WV��+LHUDUFKLHV

Choose an InfoObject from the proposal list, and specify a name and a description.


Choose ,QIR6RXUFH�WUHH → <RXU�DSSOLFDWLRQ�FRPSRQHQW → 2QH�RI�\RXU�,QIR6RXUFHV →&RQWH[W�PHQX��ULJKW�PRXVH�EXWWRQ� → $VVLJQ�VRXUFH�V\VWHP.

You are taken automatically to the transfer structure maintenance.

The system automatically generates, DataSources for the three different data types to whichyou can load data.

1. Attributes

2. Texts

3. Hierarchies (if the InfoObject has access to hierarchies)

The system automatically generates the transfer structure, the transfer rules, and thecommunication structure (for attributes and texts).


Either choose the DataSource to upload attributes or the DataSource to upload texts.

The system automatically generates for you a proposal for the data source, transfer structure,transfer rules and communication structure.

$WWULEXWHV

The proposal for uploading attributes displays which structure your flat file must have foruploading attributes, and contains at least the characteristic and the attributes assigned to it.Make sure that the sequence of the objects in the transfer structure corresponds to thesequence of the fields in the flat file.

The following fields can be required in a flat file for attributes:

/BIC/<ZYYYYY> Key for the compounded characteristic (if thecharacteristic exists)

/BIC/<ZXXXXX> Characteristic key

DATETO* CHAR 8 valid to – date (only for time-dependent master data)

DATEFROM* CHAR 8 valid from – date (only for time-dependent master data)

7H[WV

The proposal for uploading texts displays which structure your flat file must have for uploadingtexts for this characteristic. Ensure that the structure of your flat file corresponds to theproposed structure.



The following fields can be required in a flat file for texts:

LANGU CHAR 1 Language key (F for French, E for English)

/BIC/<ZYYYYY> Key for the compounded characteristic (if thecharacteristic exists)

/BIC/<ZXXXXX> Characteristic key

DATETO* CHAR 8 valid to – date (only for time-dependent master data)

DATEFROM* CHAR 8 valid from – date (only for time-dependent master data)

TXTSH CHAR 20 Short text

TXTMD CHAR 40 Medium-length text

TXTLG CHAR 60 Long text

The columns sequence in the transfer structure must correspond to the columnssequence in your flat file. If you do not use the same sequence, the correspondingtransfer structure will not be filled correctly.

Activate the transfer structure/transfer rules and the communication structure.

)XUWKHU�6WHSV�


5HVXOW

You have uploaded the master data for the corresponding characteristic. You can check the uploadeddata using the master data maintenance.



8SORDGLQJ�+LHUDUFKLHV�IURP�)ODW�)LOHV

3UHUHTXLVLWHV

If you want to load InfoObjects in the form of hierarchies, you have to activate theindicator ‘with hierarchies’ for each of the relevant InfoObjects in the InfoObjectmaintenance. Specify whether you want the whole hierarchy or the hierarchystructure to be time-dependent, and whether you want the hierarchy to containintervals.

3URFHGXUH



→&UHDWH�





Choose ,QIR6RXUFH�WUHH → <RXU�DSSOLFDWLRQ�FRPSRQHQW → &RQWH[W�PHQX��ULJKW�PRXVH�EXWWRQ�

→ &UHDWH�,QIR6RXUFH�→�$WWULEXWHV��7H[WV��+LHUDUFKLHV

Choose an InfoObject from the proposal list, and specify a name and a description.


Choose ,QIR6RXUFH�WUHH → <RXU�DSSOLFDWLRQ�FRPSRQHQW → 2QH�RI�\RXU�,QIR6RXUFHV →&RQWH[W�PHQX��ULJKW�PRXVH�EXWWRQ� → $VVLJQ�VRXUFH�V\VWHP. You are taken automatically tothe transfer structure maintenance.

The system generates automatically, DataSources for the three different data types to whichyou can load data.

• Attributes

• Texts

• Hierarchies (if the InfoObject has access to hierarchies)

The system generates automatically the transfer structure, the transfer rules, and thecommunication structure (for attributes and texts).


Choose the DataSource to be able to upload hierarchies.

The system generates automatically, a proposal for the DataSource and the transfer structure.This consists of an entry for the InfoObject, to which hierarchies are loaded.

�� 0DLQWDLQLQJ�WKH�+LHUDUFK\�

Choose +LHUDUFK\�0DLQWHQDQFH� and specify a technical name, and a description of thehierarchy.

The system generates automatically, a table with the following hierarchy format (for sortedhierarchies):

Description Field name Length Type

Node ID NODEID 8 NUMC

InfoObject name INFOOBJECT 30 CHAR

Node name NODENAME 32 CHAR



Catalog ID LINK 1 CHAR

Parent node PARENTID 8 NUMC

First subnode CHILDID 8 NUMC

Next node NEXTID 8 NUMC

Language key LANGU 1 CHAR

Description - short TXTSH 20 CHAR

Description - medium TXTMD 40 CHAR

Description - long TXTLG 60 CHAR

The system transfers the settings for the intervals and for time-dependency from theInfoObject maintenance. Depending on which settings you have defined in the InfoObjectmaintenance, further table fields can be generated from the system.

The YDOLG�IURP and YDOLG�WR field is filled if you select 7RWDO�+LHUDUFK\�7LPH�GHSHQGHQW�inthe InfoObject maintenance. The indicator WLPH�GHSHQGHQW is activated if you select the+LHUDUFK\�1RGHV�7LPH�GHSHQGHQW option in the InfoObject maintenance.


Depending on which settings you defined in the InfoObject maintenance, additional fieldscan be generated from the system. Note the detailed description for creating your flathierarchy files.

�>6HLWH��@$GGLWLRQDO�6WHSV�


5HVXOW

You have uploaded the hierarchy data for the corresponding characteristic.



6WUXFWXULQJ�D�)ODW�+LHUDUFK\�)LOH

3UHUHTXLVLWHV

You have created a sorted hierarchy and the system generates a structure with thefollowing hierarchy format.

Description Field name Length Type

Node ID NODEID 8 NUMC

InfoObject name INFOOBJECT 30 CHAR

Node name NODENAME 32 CHAR

Catalog ID LINK 1 CHAR

Parent node PARENTID 8 NUMC

First subnode CHILDID(*) 8 NUMC

Next node NEXTID(*) 8 NUMC

DATETO* 8 CHAR

DATEFROM* 8 CHAR

LEAFTO* 32 CHAR

LEAFFROM* 32 CHAR

Language key LANGU 1 CHAR

Description - short TXTSH 20 CHAR

Description - medium TXTMD 40 CHAR

Description - long TXTLG 60 CHAR

• The rows marked in green(*) are only generated automatically if a sorted hierarchy is being used.

• * The rows marked blue* are only automatically generated if you have created an InfoObject with atime-dependent hierarchy and/or intervals.

3URFHVV

The following table shows which data you should upload from the flat file.

NODEID NUMC 8 Specify the internal ID of the hierarchy nodewith zeros at the beginning.

In every hierarchy, there is precisely onenode with the NODEID ‘00000001’ and thePARENTID ‘00000000’.

INFOOBJECT CHAR 30 In the row INFOOBJECT, specify thename of the characteristic to whichthe hierarchy should be assigned.The master data for thischaracteristic is then used.Alternatively, you can include a textnode.

A text node always refers to anInfoObject for which data could not



be loaded. In BW, enter theInfoObject ‘OHIER_NODE’ as a textnode.

You can use text nodes if you need countryor city names for the evaluation criteria of ahierarchy.

NODENAME CHAR 32 For master data, enter the key of the masterdata table. Enter any name you choose fortext nodes.

LINK CHAR 1 With ‘normal’ nodes, leave the field empty.

If the node is a link node [Seite 180] that is,if the node is a child with two parent nodes,create two rows for the InfoObject. Thencreate a row and leave the field LINK empty.In the second row, create the InfoObject aschild of the second parent node with a newNODEID, but give it the same NODENAME.Also enter an ‘X’ in the LINK column.

If you enter the ‘X’, a link exists between thisnode and the second node by the samename. This means that the node has thesame subtree as the second node. If youchange the structure of the second node,the structure of the link node also changes.

PARENTID NUMC 8 Enter the NODEID for the first ‘parent node’with zeros at the beginning. Enter,“00000000“ if there is no parent node.

Define hierarchies in descending order, thatis, for example, the PARENTID should havea smaller ID number that the CHILDID.

CHILDID NUMC 8 Enter the NODEID for the first child nodewith zeros at the beginning. Enter,“00000000“ if there is no lower-level node.

NEXTID NUMC 8 Enter the NODEID for the first ‘next nodes’with zeros at the beginning. Enter,“00000000“ if there is no ‘next node’.

DATETO* CHAR 8 Valid–to nodes (are needed if the hierarchystructure is time-dependent).

DATEFROM* CHAR 8 Valid–to nodes (are needed if the hierarchystructure is time-dependent).

LEAFTO* CHAR 32 Upper limit of a hierarchy interval (needed ifthe hierarchy contains intervals).

LEAFFROM* CHAR 32 Upper limit of a hierarchy interval (needed ifthe hierarchy contains intervals).

LANGU CHAR 8 Enter the language ID (is required for textnodes). For example, F for French, E forEnglish, and so on.

TXTSH CHAR 8 Enter a short text. This is needed for textnodes, as no texts can be loaded for thesenodes.



TXTMD CHAR 32 Enter a medium text. This is needed for textnodes, as no texts can be loaded for thesenodes.

TXTLG CHAR 32 Enter a long text. This is needed for textnodes, as no texts can be loaded for thesenodes.

5HVXOW

You have created a flat file with a hierarchy, which you should save as a CSV orASCII file, and then load into BW.

6WUXFWXULQJ�D�6LPSOH�+LHUDUFK\�)LOH��([DPSOH�

NODEID INFOOBJECT

NODENAME

LINK

PARENTID

CHILDID

NEXTID LANGU

TXTSH

00000001

0HIER_NODE

EA 00000002

D Earth

00000002

MTCONT EU 00000001

00000003

00000003

MTCONT AS 00000001

00000004

00000004

MTCONT AF 00000001

00000005

00000005

0HIER_NODE

US 00000001

00000006

00000008

00000006

MTCONT NA 00000005

00000007

00000007

MTCONT SA 00000005

00000008

MTCONT AA 00000001

The file displayed above would correspond to the following hierarchy:



E arthEurope

Asia

A fr ica

N orth A m erica

South Am erica

An tarc tica

The names of the characteristic nodes (yellow triangles) are taken from the masterdata text table. The names of the text nodes (folders) are taken from the hierarchytable above. In this example, only the name ‘Earth’ was entered in the hierarchytable. This is why the NODENAME ‘US’ is displayed for the second text node.



3UHYLHZ�DQG�6LPXODWLRQ�RI�/RDGLQJ�'DWD�IURP�)ODW�)LOHV

8VH

Before you load data from a flat file, you can take look at the data in the preview. Thislets you check that the data is OK before you load it.

From the preview, you can run a simulation of the data loading process. This allowsyou to check the update process.

This function makes it easier for you to check that the structure of the CSV and ASCIIfiles you want to load is correct. It provides you with a better overview of data,particularly with hierarchies.

3UHUHTXLVLWHV

You have created and activated the transfer structure of the InfoSource. You havealso created and activated update rules.

)XQFWLRQV

3UHYLHZ

Once you have selected the file parameter information, the transfer structure isdisplayed in the preview, as it would appear after loading.

6LPXODWLRQ

The data loading process is simulated. Note that only the PSA transfer method issupported. With transaction data, the transfer rules and the update rules aresimulated, and you can look at the filled communication structure or the updatedInfoCube. With attributes and texts, the transfer rules are simulated, allowing you totake a look at the filled communication structure. With hierarchies, the hierarchy treeis displayed along with any error messages.

$FWLYLWLHV

1. Choose the 3UHYLHZ�pushbutton from the transfer structure maintenance of your InfoSource, .

2. Choose the file parameters for the preview, and then choose ([HFXWH. You get a preview of thetransfer structure for your file after the upload.

3. From the preview, you are then able to use the 6LPXODWH pushbutton to simulate the upload of thefile. If you want to simulate transaction data that can be updated in several InfoCubes or ODSobjects, you can select the data target that you want to update. With attributes, texts, andhierarchies, the simulation is simply started.



0DLQWDLQLQJ�,QIR6RXUFHV��([WHUQDO�6\VWHP�

You can also assign an external system to an InfoSource. The data would then beloaded from this system into BW, using staging BAPIs. To load data from an externalsystem, you have a range of extraction tools from third party providers at yourservice. For an extraction tool, you can maintain a destination, which is given whenyou load data from BW. The extraction tool loads the data from the external systemand transforms these into the relevant BW format.

When you load transaction data from an external system, you must make sure thatthe transfer structure is structured exactly like the data structure of the extraction tool.

When you load master data from an external system, you must make sure that thedata structure of the extraction tool is structured exactly like the transfer structureproposed by BW.

3URFHGXUH



→&UHDWH�

For an external system, choose: ([WHUQDO�V\VWHP��GDWD�DQG�0HWDGDWD�WUDQVIHU�XVLQJ�VWDJLQJ%$3,V.

(QWHU�D�QDPH�DQG�D�GHVFULSWLRQ��DQG�PDLQWDLQ�WKH�5)&�GHVWLQDWLRQ�IRU�\RXU�H[WUDFWLRQ�WRRO�


Maintaining the InfoSource and the subsequent process is identical to when you load datafrom a flat file. Choose a procedure according to data type:

• Uploading Transaction Data from Flat Files [Seite 290]

• Uploading Master Data from Flat Files [Seite 294]

• Uploading Hierarchies from Flat Files [Seite 296]



,QIR�3URYLGHUV

'HILQLWLRQ

Superordinate term for objects created in BEx queries or that can be run. InfoProvider are objects orviews that are relevant to reporting.

8VH

Different meta objects for the data basis are understood as InfoProviders. These objects can beuniformly considered from the view of a query definition as data providers and can also be accordinglyand uniformly reported by using their data. The type of data procurement, level of detail, or “proximity”for the OLTP system in the data flow diagram is thereby different from InfoProvider to InfoProvider.However, this makes no difference in reporting, where they appeared as objects that have data thatare suited for an evaluation by means of a BEx query.

6WUXFWXUH

Under the term InfoProvider you can find data targets for an object in which data physically existsalready.


• ODS Objects [Seite 160]

• InfoObjects [Seite 93] (Characteristics with attributes, texts, or hierarchies)

A characteristic is then an InfoProvider if it has master data and is assigned to an InfoArea. Ithas to be made explicitly in the InfoObject maintenance for the InfoProvider.

Objects that have no physical data storage, but a logical view instead, are also included in that, suchas:

• InfoSets [Seite 306]

• RemoteCubes [Seite 333]

• SAP RemoteCubes [Seite 331]

• Virtual InfoCube with Services [Seite 335]

• MultiProvider [Seite 338].

The following graphic offers an overview by using the BW objects for reporting. It also subdividesaccording to pure data targets (that have data) and InfoProviders (that only display logical views andno data). You can only access an InfoProvider from the BEx view. How the data is modeled is not ofinterest at the time.



��

��

��

��

� ��

� ��!�� "�$#&%'� �

()%�*+�,!.-0/��21�!�3'�2/

� ��'45�6�

789: ;<: =>?@ <78A@ <9BC@

789: ;<: =>?@ <78A@ <9BC@��DE4F��6�

��G�HI-J5 K0!L2�

�M%��'!.2��J'N�O�*P�0/��2/

QM!./��,% �2*L��$#M%��



,QIR6HW

'HILQLWLRQ

Name for a particular type of InfoProvider: An InfoSet describes data sources that are usually definedas joins [Extern] for ODS objects [Extern] or InfoObjects [Seite 28] (characteristics with master data). Atime-dependent join or temporal join is a join that contains an InfoObject that is a time-dependentcharacteristic.

An InfoSet is a semantic layer over the data sources and is not itself a data target [Seite 92].

Unlike the classic InfoSet, and InfoSet is a BW-specific view of data.

For more information see the following documentation: InfoProviders [Seite 304], Temporal Joins[Seite 321], Classic InfoSets [Seite 324].

8VH

In the BEx Query Designer [Extern] you compile reports (queries [Extern]) about activated InfoSets.

6WUXFWXUH

Every ODS object and every InfoObject that is a characteristic with master data can be included in ajoin. A join can contain objects of the same object type, or objects of different object types. Theindividual objects can appear in a join any number of times. Join conditions connect the objects in ajoin to one another (equal join-condition). A join condition determines the combination of records fromthe individual objects that are included in the resulting set.

,QWHJUDWLRQ

,QIR6HW�0DLQWHQDQFH�LQ�WKH�$GPLQLVWUDWRU�:RUNEHQFK

You create and edit InfoSets in the ,QIR6HW�%XLOGHU. See Creating InfoSets [Seite 308] and EditingInfoSets [Seite 309].

5HSRUWV�XVLQJ�,QIR6HWV

The BEx Query Designer supports the tabular (flat) display of queries. Use the 7DEOH 'LVSOD\pushbutton to activate this function.

For every InfoProvider that is included in a join there are two dimensions (key and attribute) in the BExQuery Designer. These dimensions contain the fields and attributes for the selected InfoSet.

If the InfoProvider is an InfoObject of the type characteristic, all of the characteristics listedin the attribute definition and all of the display attributes are assigned to the characteristic(and to the existing compounded characteristics) in the .H\ dimension:

• The display attributes are listed exclusively in the .H\ dimension.

• The independent characteristics are listed in both the .H\ and the $WWULEXWHdimensions.

If the InfoProvider is an ODS object, a field object with the property “exclusive attribute” isQRW listed in the directory tree of the InfoProvider.

If the join is a temporal join, there is an extra YDOLG�WLPH�LQWHUYDO dimension containing the twoInfoObjects (YDOLG�WR and YDOLG�IURP ) for the valid time-interval. Temporal joins also have a specialcharacteristic for making selections according to the valid time-interval.

For more information see Design: BEx Query Designer [Extern].


The usual transport method in the Business Information Warehouse is also applied to InfoSets, sincethey are repository objects.



For more information see Variants: Editing InfoSets [Seite 310].

'HILQLWLRQ�DQG�GHOLYHU\�RI�&RQWHQW

Business Content is defined and delivered in the usual way in the Business Information Warehouse.

InfoSets are delivered in a D-version, and have to be activated by the customer.



&UHDWLQJ�,QIR6HWV1. You are in the InfoProvider tree of the�0RGHOLQJ function area in the Administrator Workbench.

Choose the &UHDWH�,QIR6HW function from the context menu (right mouse-click) of the InfoAreain which you want to create an InfoSet. You get to the &UHDWH�,QIR6HW dialog box.

2. Type in the following information for your new InfoSet:

− technical name

− long description

− short description

3. In the 6WDUW�ZLWK�,QIR3URYLGHU section, you determine which InfoProvider you want to use to startdefining the InfoSet.

− Select one of the object types that the system offers you:

ODS object

InfoObject

− Choose an object.

If you want to choose an InfoObject, it must be a characteristic with master data. Thesystem provides you with the corresponding input help.

4. Choose 1H[W. You get to the &KDQJH�,QIR6HW screen.�For more information on editing InfoSetssee Editing InfoSets [Seite 309].

When you create an InfoSet, the system generates a corresponding entry for this InfoSetin the subtree of the InfoArea. The following functions are available from the context menu(right mouse-click) of this entry:

• &KDQJH

• 'HOHWH

• 2EMHFW�RYHUYLHZ

You can also use a special transaction to call the ,QIR6HW�%XLOGHU�if you want to create anew InfoSet.� For more information see Variants: Editing InfoSets [Seite 310].



(GLWLQJ�,QIR6HWV

3UHUHTXLVLWHV

Before you can get to the screen where you edit InfoSets, the following prerequisites have to be met:

• You have created a new InfoSet.

• You have selected the &KDQJH function from the context menu of an InfoSet entry in theInfoProvider tree of the 0RGHOLQJ function area in the Administrator Workbench.

• You have called the ,QIR6HW�%XLOGHU�transaction, and selected the &KDQJH function. For moreinformation see Variants: Editing InfoSets [Seite 310].

3URFHGXUH

1. You are in the &KDQJH�,QIR6HW screen.

Choose a layout for the InfoProvider tree:

InfoProviders Used

$OO�2'6�2EMHFWV

$OO�,QIR2EMHFWV

For more information on the screen layout, particularly the layout of the InfoProvider tree, seeScreen Layout: Changing InfoSets [Seite 313].

2. You define the InfoSet by inserting one or more InfoProviders into the join.

There are several ways of inserting an InfoProvider into the join control:

− From the InfoProvider tree:

• In the InfoProvider tree, double-click on the entry that corresponds to the InfoProvider thatyou want to add to the join control.

• Use the drag-and-drop function to move the InfoProvider into position.

− Choose the $GG�,QIR3URYLGHU function, to add a particular ODS object or a particularInfoObject independently of the current layout of the InfoProvider tree. You get to the dialogbox of the same name. Type in the data that the system asks you for.

If you know the technical name of the InfoProvider that you want to add, this method isquicker than switching the layout of the InfoProvider tree.

When this function is complete, the InfoProvider that you selected is displayed in the joincontrol.

For more information on the structure of the join control, see Join Control [Seite 315].

3. Define the join conditions.

For more information see Defining Join Conditions [Seite 319].

4. Save the InfoSet. The log is displayed in the area of the screen below the actual join control.

5. Activate the InfoSet. The system carries out a series of checks as the InfoSet is activated. Theresult of the activation process is displayed in a log in the area of the screen under the join control.

5HVXOW

Once an InfoSet is active, you are able to use it to help you define queries.



9DULDQWV��(GLWLQJ�,QIR6HWVThere are the following options for editing InfoSets:

1. Use transaction 56,6(7 to call the InfoSet Builder. You go to the (GLW�,QIR6HW��,QLWLDO�6FUHHQ.

2. Select the InfoSet that you want to edit. The input help function is available.

Click on the 'RFXPHQWV pushbutton on the pushbutton toolbar to branch to the screenwhere you edit the documents for this InfoSet.

Click on the 2EMHFW�&DWDORJ�(QWU\�pushbutton on the pushbutton toolbar to go to the'LVSOD\�2EMHFW�&DWDORJ�(QWU\ dialog box.

3. In the upper area of the screen, the following DGGLWLRQDO�IXQFWLRQV are available for editing theInfoSet that you have chosen:


7UHH�'LVSOD\ You get to the 'LVSOD\�,QIR6HW screen. Thesystem displays all the properties of the $�YHUVLRQ��DFWLYH��of the selected InfoSet in a treestructure.

• +HDGHU�GDWD

• InfoProvider and their fields

• OQ condition

• :KHUH condition

If no active version is available the display isempty.

9HUVLRQ�&RPSDULVRQ You determine the type of comparison in thedropdown box belonging to this pushbutton.

• 'LVSOD\�'LIIHUHQFHV�2QO\

• 'LVSOD\�$OO�3URSHUWLHV

Choose the versions that you want to compare.Depending on the available versions of theInfoSet that you selected, you have thefollowing version comparison options:

• $FWLYH�PRGLILHG�YHUVLRQ�meaning the A-version (active) and the M-version(modified).

• $FWLYH�&RQWHQW�YHUVLRQ meaning the A-version (active) and the D-version(delivered).

• 0RGLILHG�&RQWHQW�YHUVLRQ meaning the M-version (modified) and the D-version(delivered).

You get to the 'LVSOD\�,QIR6HW screen.Depending on which option you choose, thesystem displays in a tree structure either all ofthe differences that there are between the twoversions of the selected InfoSet, or all theproperties of both versions.

7UDQVSRUW�&RQQHFWLRQ�8VLQJ�$:% You use this function to transport an InfoSetinto another system.

You get to the $GPLQLVWUDWRU�:RUNEHQFK�



7UDQVSRUW�&RQQHFWLRQ�screen.

The system has already collected all the BWobjects that are needed to guarantee theconsistency of the target system.

:KHUH�8VHG�/LVW�8VLQJ�$:% You use this function to determine which BWobjects use the InfoSet that you have selected.

You get to the $GPLQLVWUDWRU�:RUNEHQFK�:KHUH�8VHG�/LVW�screen.

You are able to work out what would happen inthe system if you made changes to the InfoSet.This helps you to decide whether or not it issensible to make these changes at thisparticular point in time.

%XVLQHVV�&RQWHQW Instead of creating a new InfoSet, you cantransfer one of the InfoSets that are deliveredwith SAP Business Content [Seite 21].

4. There are the following HGLWLQJ�IXQFWLRQV to choose from:


Display You get to the 'LVSOD\�,QIR6HW screen.

Change You get to the &KDQJH�,QIR6HW screen.

&KHFN The system generates a message about thesuccess of the check, and writes the results tothe application log.

Activate The system generates a message about thesuccess of the activation process, and writesthe results to the application log.

Copy You get to the &RS\�,QIR6HW dialog box. Specifya name for the copy of the InfoSet.

Delete You get to the 'HOHWH�,QIR6HW dialog box.Answer yes or no when the system asks you toconfirm that you want to delete the selectedInfoSet.

Click on the &UHDWH pushbutton if you want to create a new InfoSet. You get to the&UHDWH�,QIR6HW dialog box. Type in the data that the system asks you for. Choose 1H[W.You get to the &KDQJH�,QIR6HW screen.

For more information see Editing InfoSets [Seite 309].

5. You use the following pushbuttons on the pushbutton toolbar to branch to the screens where youedit the InfoProviders:

,QIR2EMHFWV: You get to the (GLW�,QIR2EMHFWV��,QLWLDO�6FUHHQ.

2'6�REMHFWV: You get to the (GLW�2'6�2EMHFWV��,QLWLDO�6FUHHQ.

Click on the /RJV�pushbutton to get to the /RJ�6HOHFWLRQ dialog box.�Choose the InfoSetlogs that you want to see. You get to the /RJ�6HOHFWLRQ�screen� In the following areas, makeany restrictions that you want to make:

− Time restrictions

− Logs generated by (users, transaction codes, programs)

− Log classes



− Log generation

Choose ([HFXWH. You get to the /RJV�screen�



6FUHHQ�/D\RXW��&KDQJLQJ�,QIR6HWVThe &KDQJH�,QIR6HW screen has the following areas:

,QIR3URYLGHU�WUHH

On the left-hand side of the screen, all the InfoProviders that you are able to use in the InfoSetdefinition are displayed.

The following options in the table control how the InfoProvider tree is displayed:

,QIR3URYLGHU�WUHH :KDW�\RX�QHHG�WR�NQRZ

�5HODWHG�,QIR3URYLGHUV This tree contains those InfoProviders that canbe included in the join and for which you candefine a join condition for a join that existsalready in the InfoProvider.

• InfoObjects that are characteristics (withmaster data) and that are either alreadyincluded as InfoProviders in the join or areattributes of an InfoProvider in the join.

• ODS objects whose keys contain anInfoObject that is either included as anInfoProvider in the join already or that is anattribute of an InfoProvider in the join.

The 5HODWHG�,QIR3URYLGHUV�tree contains thefollowing objects in particular:

• InfoProviders that are available already inthe join, because each InfoProvider can beincluded in the join as many times as youlike.

• InfoProviders for which you can define ajoin condition with the first InfoProvider thatis chosen when the InfoSet is created.

All ODS Objects This tree contains all the ODS objects that areavailable in the BW system.

$OO�,QIR2EMHFWV This tree contains all the InfoObjects that arecharacteristics (with master data) available inthe BW system.

The system has a default layout for displaying the 5HODWHG�,QIR3URYLGHUV�tree.

We recommend that you use this default display.

The system is, however, able to store one of the alternative layouts in the personal settings.

Although in principle you can include in a join every ODS object and every InfoObject thatis a characteristic (with master data) you must remember that not every ODS object andnot every characteristic supports the definition of a join condition – as a prerequisite foractivating the InfoSet.

-RLQ�&RQWURO

On the right-hand side of the screen there is a join-control. You use the join-control to display theInfoProviders used and the relationships between them.

For more information see Join-Control [Seite 315].

$UHD�IRU�ORJV�DQG�WH[W�PDLQWHQDQFH



In the area underneath the join-control, logs and texts that you want to maintain are displayed as andwhen you require them.



-RLQ�&RQWURO

'HILQLWLRQ

An area of the screen belonging to the ,QIR6HW�%XLOGHU. The InfoProviders that are included in the joinare displayed in the join control.

8VH

You define join conditions in the join control. There have to be valid join conditions before the systemis able to activate the InfoSet.


6WUXFWXUH

'LVSOD\LQJ�DQ�,QIR3URYLGHU�LQ�WKH�-RLQ�&RQWURO

InfoProviders are displayed as a WDEOH in the join control. A symbol in the header indicates that anInfoObject is time-dependent.

Depending on the type of InfoProvider, the following information is displayed in the URZV of the table:

• for ODS objects: A field (a key field or a data field)

• for InfoObjects: The InfoObject itself, compounded characteristics, or an attribute

Since the fields for ODS objects and the attributes of InfoObjects are defined usingInfoObjects, each row ends with an InfoObject.

InfoObjects are described as follows in the FROXPQV of the table:

&ROXPQ ,QIRUPDWLRQ

8VH�ILHOG Field selection for an InfoSet: If there is a checkmark in this checkbox, the corresponding field orattribute from an InfoProvider is released for use inreporting. This means that it is available in the BExQuery Designer to be used for defining queries.

There is a check mark in this checkbox by default.

You can restrict the number of available fields orattributes from an InfoProvider by removing thischeck mark.

If an InfoObject has the property“exclusive attribute”, the checkbox forselecting this field object in the joincontrol is not ready for input. This isbecause the respective characteristiccan only be used as a display attributefor another characteristic.

In the BEx Query Designer these displayattributes are QRW available for the querydefinition in the InfoProvider directorytree (see Defining a New Query forOLAP Reporting [Extern]).

In order to add these field objects in



queries, you have to deactivate theproperty “exclusive attribute” in theInfoObject maintenance. (See Tabstrip:General [Seite 34]) This can influencethe performance of database access.

.H\�ILHOG��DGGLWLRQDO�ILHOG The symbol means

• a key field for ODS objects

• the InfoObject itself or a compoundedcharacteristic, for InfoObjects

The symbol means additional attributes, for time-dependent InfoObjects

• for the start of a valid time interval (YDOLG�IURP)

• for the end of a valid time interval (YDOLG�WR)

and for all InfoProviders

• Key dates

7HFKQLFDO�QDPH

Object type (represented by the correspondingsymbol)

Examples:

Characteristic

Key figure

Unit

Time-characteristic

'HVFULSWLRQ Long text description

Checkbox for temporal operands This column is filled only for D-type (date) fields orattributes from an InfoProvider and for time-characteristics, from which a key date or a timeinterval is derived.

If there is a checkmark in this checkbox, it meansthat the InfoObject is used as a temporal operand.

The checkbox is empty by default. If there is a checkmark in the checkbox, and a key date can bederived, the additional fields mentioned above areadded to the InfoProvider.

See Temporal Joins [Seite 321].

The following functions are available from the FRQWH[W�PHQX (right mouse-click) of an entry in a table:

• +LGH�WLPH�GHSHQGHQW�ILHOGV

If you hide the time-dependent attributes that belong to a time-dependent InfoObject, only theattributes that are not time-dependent are used in reporting. In the following situation, theInfoObject is treated as a time-dependent InfoObject within the InfoSet: This can affect howthe join is processed. For more information see Temporal Joins [Seite 321].

• 'HOHWH�REMHFW

You use this function to remove an object from the join control.

• /HIW�RXWHU�MRLQ

For more information on the left outer-join operator, see Defining Join Conditions [Seite 319].



'LVSOD\LQJ�-RLQ�&RQGLWLRQV�LQ�WKH�-RLQ�&RQWURO

A join condition is displayed as a line connecting exactly one InfoObject from a row in one object withexactly one InfoObject from a row in another object.


1DYLJDWLQJ�LQ�WKH�-RLQ�&RQWURO

/RFDWLRQ of the individual objects

You are able to position each ODS object and each InfoObject freely in the join control.

Position the cursor over the header of the object that you want to move, press the left mouse-button, and keeping the button pressed down, drag the object to its new position.

The positioning of the individual objects within the join control does QRW affect the way the joinis processed.

6L]H of the individual objects

Each time you click on the =RRP�LQ icon, the view is enlarged by 10%.

�Each time you click on the =RRP�RXW icon, the view is reduced by 10%.

�The�$XWR�DUUDQJH function arranges the objects automatically into an overview.

These functions are also available from the context menu of the join control.

1DYLJDWRU

You click on the +LGH�'LVSOD\ 1DYLJDWRU�function to get to the navigation help.

These functions are also available from the context menu of the join control.

The navigator is particularly useful if not all the objects are visible at the same time.

• If you want to change the section of the screen that is displayed, you move the red framein the navigator.

• If you want to change the size of the objects, you adjust the dimensions of the frame itself:

Reducing the frame has the same effect as the zoom-in function.

Enlarging the frame has the same effect as the zoom-out function.

&KDQJLQJ�WKH�GHVFULSWLRQV

The descriptive texts that are used in the metadata repository for the InfoProviders and their attributesare also used in the join control.

If you use InfoProviders or InfoObjects more than once as attributes in the join, it helps if you changethese descriptive texts for the purposes of the InfoSet. This enables you to identify the individualobjects more easily.

Choose the &KDQJH�'HVFULSWLRQ�function� An overview of all the texts is displayed beneath the joincontrol. You are able to change each of these texts.

The following functions are available:


$OO�2EMHFWV A selection of the texts for

• a single InfoProvider in the join

• all the objects in the join

7UDQVIHU Transfers the texts in the display in the join control.

*HW�$OO�2ULJLQDO�7H[WV Undoes the changes made to the texts.

If you click on the 7UDQVIHU function at this stage,



the system re-inserts the descriptions from themetadata repository.

'HOHWH

Select one or more objects that you want to delete from the join and click on the 'HOHWH function.

6DYLQJ�D�MRLQ�DV�D��MSJ�ILOH

Choose the 6DYH�DV�MSJ function to save your join definition as a graphic in the jpeg file format on aPC.

3ULQW

Choose the 3ULQW�function to print a copy of your join definition..



'HILQLQJ�-RLQ�&RQGLWLRQV

8VH

A join condition determines the combination of records from the individual objects that are included inthe resulting set.

Before an InfoSet can be activated, the join conditions have to be defined in such a way (as equal joincondition) that all the available objects are connected to one another either directly or indirectly.

Table 1 Table 2

x y

Equal Join Condition: T1-x T2-y

An equal join condition is fulfilled if the

value of the connected fields is equal.

The technical prerequisite for the validity of a join condition is the equality of both

of the connected InfoObjects with respect to their data type and their length.

Usually, however, only rows containing a common InfoObject or rows containing InfoObjects thatshare the same basic characteristic are connected to one another.

3URFHGXUH

There are various ways of defining join conditions:

8VLQJ�D�PRXVH�FOLFN

Position the cursor over a row in an InfoObject.

Press the left mouse-button and, keeping the left mouse-button pressed down, trace a line betweenthis row and a row in another object.

Providing that the join condition between the two rows that you have indicated is a valid join condition,the system confirms the join condition by displaying a connecting line between the two rows.

8VLQJ�WKH� �/LQN�0DLQWHQDQFH�SXVKEXWWRQ

You get to the /LQN�0DLQWHQDQFH dialog box.

In a tree structure on the left-hand side of the screen, all of the InfoProviders that are already includedin the join are displayed along with their fields or attributes. If you double-click on one of these fields orattributes, the system displays on the right-hand side of the screen all of the fields or attributes withwhich you are able to create a join condition.

In the 6HOHFWLRQ column, set one or more of the indicators for the fields or attributes for which you wantto create a join condition. The system generates valid join conditions between the fields or attributesthat you specify.

You use the 'HOHWH�/LQNV pushbutton to undo all of the join conditions.



You use the $OO�&KDUDFWHULVWLFV or the %DVLF�&KDUDFWHULVWLFV�2QO\ pushbutton to choose between thecorresponding display variants.

We recommend that you use the %DVLF�&KDUDFWHULVWLFV�2QO\ option. The $OO�&KDUDFWHULVWLFVsetting displays all of the technical options involved in a join. If you are not able to find ajoin condition on the basic characteristic level, then the $OO &KDUDFWHULVWLFV setting is useful,but this is an exceptional case.

When you have finished making your settings, click on the &RQWLQXH�icon.

We recommend this method, because the system searches for all the possible join conditions for anyfield or attribute that the user specifies, ensuring that the join conditions are defined without errors.

8VLQJ�WKH�FRQWH[W�PHQX�/HIW�2XWHU�-RLQ�±�,QQHU�-RLQ

Usually inner-join operators connect all the objects in a join to one another. You can also connect eachobject with any of the many other objects by using a left outer join operator.

If you want to use a left-outer join operator to connect an object, select the object and choose thecorresponding function from the context menu. The system displays all of the valid join conditions thatoriginate from this object. The connecting lines that represent these join conditions are labeled as OHIWRXWHU�MRLQV.

If you used a left outer join operator to connect two objects, you have to make sure that allon conditions are linked except for these two objects with the formulation of joinconditions.

Note that you cannot add an object, which you have already connected by using the leftouter join operator, to another object.

If you want to use an inner-join operator instead of the left-outer join operator, select the object thatyou want to connect, and choose the ,QQHU�-RLQ option from the context menu. Again the systemdisplays all the valid join conditions that originate from this object, and labels the connecting linesaccordingly.

5HVXOW

Once the join conditions have been defined in such a way as to connect all the available objects toone another, either directly or indirectly, the InfoSet is ready to be activated.

You click on the &KHFN�pushbutton in the pushbutton toolbar to find out if these preconditions forthe activation have been met.

For objects that are joined by a left-outer join operator, there is one extra condition thathas to be met, namely that all the other objects have to be connected to one anothereither directly or indirectly.



7HPSRUDO�-RLQ

'HILQLWLRQ

Join containing at least one time-dependent characteristic.

8VH

Time-dependency is assessed when the resulting set is determined. A time interval is assigned toeach record in the resulting set. The records are valid for the duration of the interval to which they areassigned (valid time interval).

If there are two time-dependent InfoObjects in a join, only combinations of InfoObject records thathave a common validity area are included in the resulting set. This also applies if there are more thantwo time-dependent InfoObjects in a join.

For example, a join contains the following time-dependent InfoObjects (in addition to otherobjects that are not time-dependent).

InfoObjects in the join Valid from Valid to

Cost center (0COSTCENTER) 01.01.2001 31.05.2001

Profit center (0PROFIT_CTR) 01.03.2001 31.07.2001

Where the two time-intervals overlap, meaning the validity area that the InfoObjects havein common, is known as the valid time-interval of the temporal join.

Temporal join Valid from Valid to

Valid time-interval 01.03.2001 31.05.2001

Note the different ways that the word WLPH�LQWHUYDO�is used:

• The time-interval for a time-dependent InfoObject describes the duration of time for whicha record in the InfoObject is valid.

The InfoObjects for the time-interval (YDOLG�IURP and YDOLG�WR) of a time-dependentInfoObject are visible in the join control. You set the indicator in the 8VH�)LHOGcolumn to make these fields available in the query definition process in the BExquery designer.

See Join-Control [Seite 315].

• The valid time-interval for a temporal join describes the period of time for which a record inthe resulting set of the join is valid.

The InfoObjects for the valid time-interval (YDOLG�IURP and YDOLG�WR) of a temporal joinare QRW visible in the join control. They are, however, available in the BEx querydesigner.

See InfoSets [Seite 306].

6WUXFWXUH

If you want to influence how the resulting set of a temporal join is determined, you designate within thetemporal join that the following fields or attributes of an InfoProvider are to be used as WHPSRUDORSHUDQGV.

• characteristics of the D (date field) data type



0DATEBIRTH date of birth

0ENTRYDATE date of entry

• time characteristics

0CALDAY calendar day

0CALMONTH calendar year/month

0FISCPER fiscal year/period

These fields and attributes from an InfoProvider have a checkbox in the last column of the join control[Seite 315]. If there is a checkmark in these checkboxes, it means that the field or attribute is used asa temporal operand.

This determines whether a key date or a time interval is generated:

Temporal operand Derivation

• Characteristic of data type D

• Time-characteristic

− 0CALDAY

Derivation of a key date

Time-characteristics describing a time-interval with astart date and an end date.

− 0CALWEEK

− 0CALMONTH

− 0CALQUARTER

− 0CALYEAR

− 0FISCPER

− 0FISCYEAR

Options:

• Derivation of a key date

• Derivation of a time-interval

If you put a checkmark in the checkbox next to thiskind of time-characteristic, the system takes you tothe ,QWHUSUHW�7LPH�&KDUDFWHULVWLF dialog box.

Choose a derivation type:

• Derivation of a key date

− XVH�ILUVW�GD\�DV�D�NH\�GDWH

− XVH�ODVW�GD\�DV�D�NH\�GDWH

− XVH�D�IL[HG�GD\�DV�D�NH\�GDWH (meaning aparticular day from the specified timeinterval)

• Derivation of a time-interval

− WUHDW�DV�DQ�LQWHUYDO (start and end date arederived from the value of the time-characteristic)

In accordance with whichever option you choose, thesystem adds extra attributes (extra fields) to therelevant InfoProvider. These fields contain either thederived key date (0CALDAY) or the start and enddates (0DATEFROM and 0DATETO).

The temporal operand influences the resulting set of a temporal join in different ways, depending onwhether a key date or a time-interval is derived from the temporal operand:

Derivation Effect on the resulting set

Derivation of a key date A record is included in the temporal join only if thekey date lies in the valid time-interval.

Derivation of a time-interval The InfoProvider concerned is treated as a time-dependent InfoObject: A record is included in theresulting set only if the derived time-interval has a



validity area in common with the other time-dependent objects.

Since a key date or a time-interval can be derived from a time-characteristic only once theresulting set has been read, the system checks the validity of the records again after thedata has been read from the database. As a result more data is read than ultimatelyappears as the query result. You must therefore think about the effect on the systemperformance before you use time-characteristics as temporal operands with derivations.

However, you are able to use as temporal operands InfoObjects with data type D and theInfoObject 0CALDAY as often as you like, because in this case the correspondingselection conditions are passed to the database directly.



&ODVVLF�,QIR6HW

'HILQLWLRQ

A Classic InfoSet gives you a view of a dataset that you report on using the InfoSet Query. TheClassic InfoSet determines which tables or fields within a table an InfoSet Query refers to.

8VH

In the Business Information Warehouse, InfoSets are used for InfoObjects (master data), ODS objects,and joins for these objects. the InfoSet Query allows you to carry out tabular (flat) reporting on thiskind of object and joins for this kind of object.



6HWWLQJ�XS�D�5ROH�IRU�WKH�,QIR6HW�4XHU\

8VH

To be able to create an InfoSet Query, the system administrator must set up a role for the work withthe InfoSet Query.

3URFHGXUH

1. A role has to be assigned specifically to a single SAP Query user group. This is because theInfoSet Query is derived from the SAP Query.

a. In the SAP Easy Access initial screen of the SAP Business Information Warehouse, choose%XVLQHVV�([SORUHU�→ ,QIR6HW�4XHU\ → 6HW�XS�UROHV�IRU�,QIR6HW�4XHU\�(RSQ10).�You get to atable containing the roles that are relevant for working with the InfoSet Query.

b. Choose the role you want, and use the $VVLJQ�8VHU�*URXS�function (second column in thetable) to assign a user group to the role, or to remove an existing assignment.

When you are assigning user groups, a dialog box appears asking you if you want tocreate a new user group, or use an existing one. Use the input help to choose from theavailable user groups. It is not possible to assign a user group to more than one role.

When you have assigned a user group successfully to a role, the name of this user groupappears in the third column of the table.

It is also possible to jump to the Query Builder from the SAP Easy Access SAP BusinessInformation Warehouse Menu by selecting the ,QIR6HW 4XHU\ entry from the roles in theuser menu.

2. Assign Classic InfoSets to the role. Use the $VVLJQ�&ODVVLF�,QIR6HWV function to do this (fifthcolumn in the table).

A screen containing all the available Classic InfoSets appears. Select the InfoSets that youwant to be able to use for defining queries within the role.

You are able to choose one of the selected Classic InfoSets as a standard Classic InfoSet(entry in the fourth column of the table). The standard Classic InfoSet is subsequently used asa template, if the components for maintaining InfoSet Queries are called using the menu entrymentioned above.

3. In the 0DLQWDLQ�5ROH transaction (PFCG) you assign the role you have set up to those users, whoare going to work with the InfoSet Query.

6HH�DOVR�

Process Classic InfoSets and Assign Roles [Seite 326]

Creating InfoSet Queries [Seite 329]



3URFHVVLQJ�&ODVVLF�,QIR6HWV�DQG�$VVLJQLQJ�5ROHV

8VH

Before you are able to work with the Classic InfoSet Query, Classic InfoSets must already be availableand assigned to particular roles.

3URFHGXUH

There are various ways of getting to the InfoSet maintenance screen:

• Choose %XVLQHVV�([SORUHU�→�,QIR6HW�4XHU\�→�0DLQWDLQ�&ODVVLF�,QIR6HWV (RSQ02) from the SAPEasy Access SAP Business Information Warehouse Menu.

• Or call up the Classic InfoSet maintenance function from the $GPLQLVWUDWRU�:RUNEHQFK context-dependently for ODS objects and InfoObjects.

The following deals primarily with BW-specific enhancements. You can find extensive notes for theInfoSet functions that are generally available in Basis in the SAP documentation for a SAP query.These notes also cover the BW Classic InfoSets.

'HILQH�D�&ODVVLF�,QIR6HW�

1. In the $GPLQLVWUDWRU�:RUNEHQFK�±�0RGHOLQJ, choose the &ODVVLF�,QIR6HWV function from the contextmenu belonging to the object that requires an Classic InfoSet. The Classic InfoSets that use thisparticular object are displayed on the right-hand side of the screen. The most important functions(&KDQJH, 'LVSOD\, 'HOHWH, and so on) from the basis transaction (RSQ02) are accessible via the&ODVVLF�,QIR6HW menu in the InfoSet Overview. To see if any queries already exist for an ClassicInfoSet, choose the 4XHU\�'LUHFWRU\ function. This lists all the queries that have already beencreated for a Classic InfoSet. The &ODVVLF�,QIR6HW�0DLQWHQDQFH entry takes you to the initial screenof the Classic InfoSet maintenance where all the available InfoSets are listed.

2. Choose one of the following functions to create a new Classic InfoSet for a particular object:

• Regenerate Standard InfoSets.

A Classic InfoSet containing all attributes is created for InfoObjects.

With ODS objects, the system generates a Classic InfoSet from the table containing activedata and a Classic InfoSet “new and active data combined”. If there is a more up-to-daterecord in the table containing the new data, this record is used in reporting instead of theactive record. You are able to modify the standard Classic InfoSet. Bear in mind that onlythe generated version can be used for the InfoSet Query.

• You have to define a Classic InfoSet manually, if you want to use joins. Specify a name in the7HFKQLFDO�1DPH field, and choose &UHDWH�1HZ�&ODVVLF�,QIR6HW.

The &ODVVLF�,QIR6HW�0DLQWHQDQFH screen appears The &ODVVLF�,QIR6HW��7LWOH�DQG�'DWD6RXUFH screen appears. Notice that the system has already identified the appropriatebasic master data table or ODS table as the data source.

If you want to use a Classic InfoSet for queries in a Web environment, you have to assignthe InfoSet to a user group. Do this in the &ODVVLF�,QIR6HW��7LWOH�DQG�'DWD�6RXUFH screen.To call this screen in the future, choose the *OREDO�3URSHUWLHV function from the *RWRmenu in the &ODVVLF�,QIR6HW�0DLQWHQDQFH�screen.

After you confirm you entries, you get to the -RLQ�'HILQLWLRQ. Determine the join conditions.

In the main screen of the &ODVVF�,QIR6HW�0DLQWHQDQFH, you:

• choose all the attributes you require,

• arrange these attributes into field groups,

• determine the fields that are going to contain extra information (characteristics and key figures, forexample) that was not contained originally in the InfoObjects or ODS objects.



Save your entries.

The 6HWWLQJV function in the &ODVVLF�,QIR6HW�0DLQWHQDQFH screen allows you to switch tousing DDIC names. You use this option when you are writing coding, defining upper andlower limits for a Classic InfoSet, or connecting additional tables, for example, and youhave to give the DDIC names rather than the technical names used in BW.

$VVLJQLQJ�&ODVVLF�,QIR6HW�WR�D�5ROH

• Once you have saved and generated the Classic InfoSet, assign it to one or more roles. Do this bychoosing the 5ROH�$VVLJQPHQW function in the Classic InfoSet overview. All the roles that havebeen set up for working with the InfoSet Query are displayed in a dialog box.

• The roles that the Classic InfoSet is already assigned to are flagged in the checkbox in the firstcolumn. Use the corresponding checkbox to:

− assign the Classic InfoSet to another one of the roles

− remove an existing assignment. Before you do this, make sure that there are no queries leftfor the InfoSet within this particular role.

5HVXOW

It is now possible to use the InfoSet in the Query Builder within the context of the role assigned to theClassic InfoSet.

6HH�DOVR�

Creating and Changing InfoSets [Extern] (SAP Query documentation)

Creating InfoSet Queries [Seite 329]

BW Homepage in the SAP Market place → 'RFXPHQWDWLRQ → 'RFXPHQWDWLRQ�(QKDQFHPHQWV → %:��%�,QIR6HW�4XHU\�±�6WHS�E\�6WHS��6WHS��



,QIR6HW�4XHU\InfoSet Query is a tool that is available with R/3 Basis Release 4.6C. It is also used in the BusinessInformation Warehouse (BW) for tabular (flat) reporting. Classic InfoSets provide the view for this data.

8VH

7KH�,QIR6HW�4XHU\�YHUVXV�WKH�%([�4XHU\

The BEx Query is intended for reporting with InfoCubes. In this process, functions such as thefollowing are supported: Reporting with InfoCubes and MultiCubes, using variables, navigation,displaying attributes and hierarchies, characteristic drilldown, Web reporting, currency translations,report/report interface (R/RI), and authorization checks. These functions are also available forreporting using ODS objects. However, there is a restriction in that you cannot report on more thanone ODS object at a time. The tool designed for this is the InfoSet Query.

The InfoSet Query is designed for reporting using flat data structures, that is InfoObjects, ODS objects,and ODS object joins. The following functions are supported for the InfoSet Query: Joins from severalmaster data tables and ODS objects, Web reporting, report/report interface (R/RI), and authorizationchecks. The authorization check in the InfoSet Query is simpler than the authorization check in theBEx query. The report is displayed either in the SAP List Viewer, or on the Web.

5HVWULFWLRQV

We recommend you do QRW use the InfoSet Query for reporting using InfoCubes. The InfoSet Querydoes QRW support the following functions: Navigation, hierarchies, delivery of Business Content,currency translation, variables, exception reporting, and interactive graphics on the Web.



&UHDWLQJ�,QIR6HW�4XHULHV

8VH

The InfoSet Query is designed for reporting on data stored in flat tables. It is particularly useful forreporting on joins for master data and joins for ODS objects.

3UHUHTXLVLWHV

You must take the following steps before you can create Infoset queries:

• Set up a Role for the InfoSet Query [Seite 325]

• Process Classic InfoSets and Assign Roles [Seite 326]

3URFHGXUH

'HILQH�WKH�,QIR6HW�4XHU\

1. Call the Query Builder. There are various ways of doing this:

• To call the Query Builder from the corresponding role menu or from the BEx Browser,double-click on the ,QIR6HW�4XHU\ entry in the menu that is created when you set up arole.

• Developers and testers of Classic InfoSets are able to call up the Query Builder directlyfrom the Classic InfoSet overview in the Administrator Workbench.

If several Classic InfoSets are assigned to a role, and one of them has been identified as astandard Classic InfoSet, this Classic InfoSet is used as a template when the query is calledup. To change the template, choose &UHDWH�1HZ�4XHU\�±�&ODVVLF�,QIR6HW�6HOHFWLRQ. Any of theClassic InfoSets that are assigned to the role can be the new template.

2. Define your query. The procedure is similar to the procedure for defining queries in the BExAnalyzer.

Transfer individual fields from the field groups you have selected in the Classic InfoSet into thepreview. To do this, use the drag and drop function, or highlight the relevant fields in the fieldlist.

Use either of these two methods to select any fields you want to use as filters. These fieldsare displayed in the 6HOHFWLRQV area of the screen (top right).

When you are preparing the query, only example data is displayed in the 3UHYLHZ. Whenyou choose the 2XWSXW or 5HIUHVK�function, the actual results are displayed on the samescreen.

3. Execute the query.

4. Choose from the following options:

• Ad hoc reporting.

You do not want to save the query for later. Save the Query Builder without saving.

• Reusable queries.

You want to save the query, because you want to work on it later, or use it as atemplate. Use either the 6DYH or the 6DYH�DV function to save the query.

In addition to the Classic InfoSets that you assigned to the role, you are also able touse the query as a template. It is not possible, however, to access the query fromother roles.

After you save the query, a second dialog box appears, asking you if you want to savethe query as a separate menu entry within the role. If you choose this option, you areable to start the query directly from the user menu or the BEx Browser. It is also



possible to use the 5ROH�0DLQWHQDQFH transaction (PFCG) to save this kind of roleentry.

Choose 0HQX�→�5HIUHVK to display the query.

If you want to change or delete the saved query, use the (GLW function from the contextmenu in the BEx Browser to call the maintenance tool for InfoSet Queries with thisquery as a template.

,QIR6HW�4XHU\�RQ�WKH�:HE

It is possible to publish each InfoSet Query on the Web. There are the following display options:

• MiniALV for creating MiniApps in the SAP Workplace

• MidiALV without selection options

• MidiALV with selection options

Both the MiniALV and the MidiALV allow you to switch between various selection/layout variants. Thepublishing screen for the data is adjusted individually using URL parameters.

The following prerequisites are necessary for security reasons:

• Releasing the query for the Web

• Specifying an authorization group for the corresponding Classic InfoSet

Make the required entries in the SAP Easy Access SAP Business Information Warehouse Menu%XVLQHVV�([SORUHU�→�,QIR6HW�4XHU\�→�$GPLQLVWUDWLRQ�IRU�:HE�5HSRUWLQJ.

6HH�DOVR�

ALV Grid Control in the Web [Extern]



6$3�5HPRWH&XEH

'HILQLWLRQ

An SAP RemoteCube is a RemoteCube that allows the definition of queries with direct access totransaction data in other SAP systems.

8VH

Use SAP RemoteCubes if:

• You need very up-to-date data from an SAP source system

• You only access a small amount of data from time to time

• Only a few users execute queries simultaneously on the database.

Do QRW use SAP RemoteCubes if:

• You request a large amount of data in the first query navigation step, and no appropriateaggregates are available in the source system

• A lot of users execute queries simultaneously

• You frequently access the same data

6WUXFWXUH

SAP RemoteCubes are defined based on an InfoSource with flexible updating. They copy thecharacteristics and key figures of the InfoSource. Master data and hierarchies are not read directly inthe source system. They are already replicated in BW when you execute a query.

,QWHJUDWLRQ

To be assigned to an SAP RemoteCube, a source system must meet the following requirements:

• The component BW BCT 2.0B (contained in PlugIn 2000) is installed.

• The Release status of the source system is at least 4.0B

• In BW, a source system ID has been created for the source system

• DataSources from the source system that are released for direct access are assigned to theInfoSource of the SAP RemoteCube. There are active transfer rules for these combinations.

6HH�DOVR�

Creating a SAP RemoteCube [Seite 332]



&UHDWLQJ�D�6$3�5HPRWH&XEH

3UHUHTXLVLWHV

• DataSources from the source system are assigned [Seite 242] to the InfoSource of the SAPRemoteCubes.

• Direct access must be permitted for the DataSources (in the DataSource maintenance).

• You must have defined and activated the transfer rules for this combination.

• In BW, a source system ID has been created for the source system. To do this choose 7RROV� →6RXUFH�6\VWHP�WR�6RXUFH�6\VWHP�,'�$VVLJQPHQW in the main menu.

3URFHGXUH

1. Choose the InfoSource tree or InfoProvider tree in the Administrator Workbench under 0RGHOLQJ�

2. In the context menu choose &UHDWH�,QIR&XEH.

3. Select 6$3�5HPRWH&XEH as InfoCube type and enter an InfoSource.

4. You can define if a unique source system is assigned to the InfoCube using an indicator.Otherwise you must select the source system in the relevant query. In this case the characteristic(0LOGSYS) is added to the InfoCube definition.

See also Characteristic Compounding with Source System ID [Extern].

5. In the next screen you can check the defined SAP RemoteCube and adjust it if necessary beforeactivation.

6. You can then assign source systems to the SAP RemoteCube. The source system assignmentsare local to the system and are not transported.

5HVXOW

The SAP RemoteCube can be used in Reporting in cases where it does not differ from the standardInfoCubes.



5HPRWH&XEH

'HILQLWLRQ

A RemoteCube is an InfoCube whose transaction data is not managed in the Business InformationWarehouse but externally. Only the structure of the RemoteCube is defined in BW. The data is readfor reporting using a BAPI from another system.

8VH

You can use a RemoteCube to carry out reporting using data in external systems without having tophysically store transaction data in BW. You can, for example, use a RemoteCube to include anexternal system from market data providers.

By doing this, you can reduce the administrative work on the BW side and also save memory space.

6WUXFWXUH

��

�� !"��

Source System

AdministratorWorkbench

#%$'&)(�*�+�&'&-,/.10)2�3546+)4

#%$'&)(�*�+�&'&-78*'9:354:;=<�>?(@35*BAC<46+D�35$'&�+FEG+4�H/+4

BAPI

OLAP ProzessorOLAP Prozessor

Data ManagerData Manager

Staging EngineStaging Engine

BAPI

�)�"IJ�� !��

When reporting using a RemoteCube, the Data Manager, instead of using a BasicCube filled withdata, calls the RemoteCube BAPI and transfers the parameters.

• Selection

• Characteristics

• Key figures

As a result, the external system transfers the requested data to the OLAP Processor.

,QWHJUDWLRQ

To report using a RemoteCube you have to carry out the following steps:

1. In BW, create a source system for the external system that you want to use.

2. Define the required InfoObjects.

3. Load the master data:

• Create a master data InfoSource for each characteristic

• Load texts and attributes



4. Define the RemoteCube

5. Define the queries based on the RemoteCube



9LUWXDO�,QIR&XEHV�ZLWK�6HUYLFHV

'HILQLWLRQ

A virtual InfoCube with services is an InfoCube that does not have its own physical data storage inBW. A XVHU�GHILQHG function module is used as DataSource. The properties of the DataSource canbe defined more precisely with a number of options. Depending on these properties, the DataManager provides services for converting the parameters and data.

8VH

A virtual InfoCube with services can be used if you want to display data from non-BW data sources inBW without having to copy the data to the BW structures. The data can be either local or remote. Youcan also change the data with your own calculations before passing it to the OLAP processor.

This function is used primarily in the SAP Strategic Enterprise Management (SEM) application.

6WUXFWXUH

You can specify the type of the InfoCube when you create it. If you choose 9LUWXDO�,QIR&XEH�ZLWK6HUYLFHV as the type, another pushbutton 'HWDLO appears. With this pushbutton you can open a furtherdialog box in which you can define the services.

1. Enter the name of a function module that should be used as the data source for the virtualInfoCube. There are different variants for the interface of this function module. One method fordefining the correct variant together with the description of the interfaces is given at the end of thisdocumentation.

2. The next step is to select some options for converting/simplifying selection conditions. You can dothis by selecting the option &RQYHUW�UHVWULFWLRQV. These conversions only change the transfer tablein the user-defined function module. The result of the query is not changed since the restrictionsthat are not processed by the function module are checked at a later time in the OLAP Processor.

Options:

− No restrictions: If this option is selected, no restrictions are passed to the InfoCube.

− Only global restrictions: If this option is selected, only global restrictions (FEMS = 0) arepassed to the function module. Other restrictions (FEMS > 0) which can be created forexample by restrictions on columns in queries are deleted.

− Simplify selections: This option is not available at the moment.

− Expand hierarchy restrictions: If this option is selected, restrictions on hierarchy nodes areconverted into the corresponding restrictions on the characteristic value.

3. Pack RFC: This option packs the parameter tables in BAPI format before calling the functionmodule and unpacks the data table that is returned from the function module after the call. Sincethis option only makes sense in connection with a Remote Function Call, you must define a logicalsystem that is used to determine the target system for the Remote Function Call when you selectthis option.

4. SID support: If the DataSource of the function module can handle SIDs, you should select thisoption. If this is not possible, the characteristic values are read from the DataSource and the DataManager determines the SIDs dynamically. In this case, restrictions on SID values areautomatically converted into the corresponding restrictions on the characteristic values if this ispossible.

5. With navigation attributes: If this option is selected, navigation attributes and restrictions onnavigation attributes are passed to the function module.If this option is not selected, the navigation attributes are read once the user-defined functionmodule has been executed in the Data Manager. In this case, the characteristics corresponding tothese attributes must have been selected in the query. Restrictions on the navigation attributes arenot passed to the function module in this case.



6. Internal format (key figures): In SAP systems a separate format is often used to display currencykey figures. The value in this internal format is different from the correct value in that the decimalplaces are shifted. You can determine the correct value in this internal representation with thecurrency tables.If this option is selected, this conversion is used for conversion in the OLAP processor.

'HSHQGHQFLHV

If you use a Remote Function Call, SID support must be switched off and the hierarchy restrictionsmust be expanded.

'HVFULSWLRQ�RI�WKH�,QWHUIDFHV�IRU�8VHU�'HILQHG�)XQFWLRQ�0RGXOHV

Variant 1:

IMPORTING

infocube TYPE rsinfoprov

EXPORTING

return TYPE bapiret2

TABLES

selection TYPE bapi6200sl

characteristics TYPE bapi6200fd

keyfigures TYPE bapi6200fd

data TYPE bapi6100da

EXCEPTIONS

communication_failure

system_failure

Variant 2:

IMPORTING

i_infoprov TYPE rsinfoprov

i_th_sfc TYPE rsdri_th_isfc

i_th_sfk TYPE rsdri_th_isfk

i_t_range TYPE rsdri_t_range

i_tx_rangetab TYPE rsdri_tx_rangetab

i_first_call TYPE rs_bool

i_packagesize TYPE i

EXPORTING

e_t_data TYPE standard table

e_end_of_data TYPE rs_bool

e_t_msg TYPE rs_t_msg

)XUWKHU�SDUDPHWHUV�IRU�YDULDQW��IRU�SDVVLQJ�KLHUDUFK\�UHVWULFWLRQV�LI�WKH\�ZHUH�QRW�H[SDQGHG�

If you restrict the hierarchy, an entry with field ’COMPOP’ = ’HI’ (for hierarchy) is created at thecorresponding location in table I_T_RANGE (for FEMS 0) or I_TX_RANGETAB (for FEMS > 0) andfield ’LOW’ contains a number with which you can read the corresponding hierarchy restriction fromtable I_TSX_HIER using field ’POSIT’. Table i_tsx_hier has the following type:

i_tsx_hier TYPE rsdri_tsx_hier

Variant 3:



IMPORTING

i_infoprov TYPE rsinfoprov

i_th_sfc TYPE rsdd_th_sfc

i_th_sfk TYPE rsdd_th_sfk

i_tsx_seldr TYPE rsdd_tsx_seldr

i_first_call TYPE rs_bool

i_packagesize TYPE i

EXPORTING

e_t_data TYPE standard table

e_end_of_data TYPE rs_bool

e_t_msg TYPE rs_t_msg

0HWKRG�IRU�GHWHUPLQLQJ�WKH�FRUUHFW�YDULDQW�IRU�WKH�LQWHUIDFH

The following list describes the procedure for determining the correct interface for the user-definedfunction module. Go through the list from top to bottom. The first appropriate case contains the variantto be used:

If 3DFN�5)&�is activated: Variant 1

If 6,'�6XSSRUW�is deactivated: Variant 2

Otherwise: Variant 3



0XOWL3URYLGHUV

'HILQLWLRQ

A MultiProvider is a special InfoProvider that combines data from a number of InfoProviders andmakes them available as a whole to reporting. The MultiProvider itself does not contain any data; itsdata comes exclusively from the InfoProviders it is based on.

InfoProviders and MultiProviders are the objects or views that are relevant for reporting.

8VH

A MultiProvider allows reporting using several InfoProviders.

InfoCube and InfoCube: You have an InfoProvider with actual data for a logically closedbusiness area and an equivalent InfoProvider with plan data. You can combine the twoInfoProviders into one MultiProvider so that you can compare the actual data with theplanned data of a query. In BW release 2.0B/2.1C, this combination of two InfoCubes wasstill called a MultiCube.

InfoCube and InfoObject: You have an InfoCube with your products and sales. Youcombine InfoObject 0PRODUCT. In this way you can display the "slow-moving items"since products that do not result in sales are also displayed. This is made possiblebecause a union operation is used to combine the tables (see below).

6WUXFWXUH

A MultiProvider can consist of different combinations of the following InfoProviders: InfoCube, ODSobject, InfoObject and InfoSet. The data from these objects can be combined in the MultiProvider witha union operation.

��

��

��

��

� �� !�"#$�%�'&)("�$�

*,+�-#.0/�13254'6)/87:9�2

#$�%��;<��=�;>�?�@�� A� B 8C��D(E�EF� ��&)("�E�

The union operation creates a union of the featured tables. That is, all values in these tables arecombined. As a comparison: InfoSets are created using joins. These only combine values that appearin both tables. In contrast to a union, joins build the intersection of the featured tables

As a comparison, see also InfoSet [Seite 306].



,QWHJUDWLRQ

MultiProviders only exist as a logical definition. The data is still saved in the InfoProviders it is basedon. A query generated from a MultiProvider is divided into several queries using the InfoProviders inquestion, which can be worked on in parallel.

In a MultiProvider, every characteristic in every InfoProvider involved should correspond to onecharacteristic or navigation attribute (as long as these are available). If it is not otherwise clear, youhave to define the InfoObject which the characteristic of the MultiProvider should be assigned to.

The MultiProvider contains the characteristic 0COUNTRY and an InfoProvider containsthe characteristic 0COUNTRY as well as the navigation attribute0CUSTOMER__0COUNTRY. In this case select exactly one of these InfoObjects in theassignment table.

Select a key figure contained in a MultiProvider from at least one of the InfoProviders involved. Ingeneral, exactly one of the InfoProviders provides the key figure. However, there are cases where it isbetter for the user to select from more than one InfoProvider:

If the key figure is 0SALES and it is stored redundantly in more than one InfoProvider (thatis, contained completely in all value combinations of the characteristics), you should selectfrom exactly one of the InfoProviders involved (otherwise the value would be incorrectlyadded in the MultiProvider for each occurrence).

However, if 0SALES is in a InfoProvider, for example as an actual value saved in anotherplan value, so that there is no overlapping in the data records (in other words: Sales isdivided disjunctively between several InfoProviders), then it makes sense to make aselection from several InfoProviders.

0XOWL3URYLGHUV�ZLWK�1RQ�FXPXODWLYH�9DOXHV

There is the following special situation for a MultiProvider in which one or more InfoCubes with non-cumulative key figures are included:

• The time dimension must be identical in all these non-cumulative InfoCubes (must be the same inall InfoObjects) and

• The MultiProvider must contain exactly this time dimension, that is the time characteristics of theMultiProvider are fixed.

See also Non-Cumulatives [Seite 73].



6WDJLQJ�6FHQDULRVStaging denotes the process in which data is supplied to a data warehouse. Various staging scenariosare possible in BW. Various scenarios are described below to help you decide when which methodsand which type of modeling are to be used. We will also consider where the data is located, in whichstructures it is found, and how it gets into reporting-enabled BW structures. From the special featuresof each scenario, you can see which one is then worth using.

A distinction is made below between staging scenarios with persistent data storage and stagingscenarios without persistent data storage. ‘Persistent’ means that the data loaded from the sourcesystem into the BW system is also saved after the transaction takes place. Non-persistent means thedata is re-created again and again, and is only stored in the BW system for the length of thetransaction.

Read more in:

Data Storage Properties [Seite 341]

Staging Scenarios with Persistent Data Storage [Seite 344]

Staging Scenarios without Persistent Data Storage [Seite 347]



'DWD�6WRUDJH�3URSHUWLHVIn the following, different types of data storage will be explained and their tasks in the staging processwill be displayed.

3HUVLVWHQW�6WDJLQJ�$UHD��36$�

'HILQLWLRQ

The Persistent Staging Area (PSA) is the input store for requested transaction data, master dataattributes, and texts from various source systems within the Business Information Warehouse.

8VH

The requested data is stored in an unchanged form in transparent, relational database tables in thetransfer structure. Consequently, they can also have errors if they already have errors in the sourcesystem. When loading flat files, the data does not remain completely unchanged, since they areadjusted by conversion routines if necessary (for example, the date format 31.21.1999 is converted to19991231 in order to ensure uniformity of data). You can also check the requests for quality,meaningfulness, sequence, and completeness.

The PSA delivers a simultaneous backup status for the ODS (until the overall staging process isconfirmed) and leads to improved loading performance by using the decoupling of the loading processfrom the further processing in BW.

The duration of the data storage in the PSA is medium-term, since it can still be used forreconstruction. However data storage when updating ODS objects is short-term.

2'6�2EMHFW

'HILQLWLRQ

An ODS object is an InfoProvider. It stores consolidated and adjusted transaction data by documentlevel. It describes a consolidated dataset from one or more InfoSources. This dataset can be analyzedwith a BEx query or an InfoSet query.

8VH

An ODS object contains key fields (for example, document number/item) and data fields that can alsocontain character fields (for example, order status, customer). The data from an ODS object can beupdated with a delta update into InfoCubes and/or other ODS objects in the same system or acrossdifferent systems.

Unlike multi-dimensional data storage using InfoCubes, the data in ODS objects is stored intransparent, flat database tables, whose granularity corresponds to that of the PSA. This type ofstorage is also suited for line items, which requires frequent overwriting.

You can also use the ODS object for delta enabling from currently delta-incapable DataSources byusing the change log. The combination of data from different processes, such as requests anddelivery, is likewise supported.

In contrast to the PSA, the storage can be made in adjusted and transformed form and is long-term incharacter.

,QIR&XEH

'HILQLWLRQ

An InfoCube is an InfoProvider. It describes a closed dataset (from the reporting view), for example, ofa business area and is the central object on which reports and analysis in BW are based. This datasetcan be evaluated using a BEx query.

For an InfoCube, this concerns

• a BasicCube that displays a large amount of relational tables in a star schema,



• a RemoteCube whose transaction data is not managed in the Business Information Warehousebut externally, or

• a MultiCube who displays a data view from several Basic or RemoteCubes

.

8VH

InfoCubes support the aggregated storage of loaded and consolidated data. They are distinguished bydata storage optimized for reading in fact and dimension tables (star schemas) in order to enablemulti-dimensional reporting (OLAP).

In contrast to ODS objects, the data fields in the BasicCube fact table cannot contain fields of the typeCHAR as key figures. Fields of the type CHAR are interpreted as keys. Another difference to ODSobjects is that the data here is not volatile.

5HPRWH&XEH

'HILQLWLRQ

A RemoteCube is an InfoProvider. It is an InfoCube with transaction data that is managed externally.Only the structure of the RemoteCube is defined in BW. The data is read for reporting using a BAPIfrom another system. With the help of a RemoteCube, you can carry out reporting using data inexternal systems without having to physically store transaction data in BW.

8VH

A RemoteCube can be used in special cases, for example, in market research data. When you start aquery with a RemoteCube, you trigger a data request with characteristic selections. The sourcestructure is dynamic and is determined by the selections. The external system transfers the requesteddata to the OLAP processor with the help of the BAPI.

A RemoteCube gives you the option of attaching external systems, structures in particular, which arenot relational (hierarchical databases). With this, you can use any reading tool that supports theinterface of an external system.

6$3�5HPRWH&XEH

'HILQLWLRQ

An SAP RemoteCube is an InfoProvider. It is a special RemoteCube that allows the definition ofqueries with direct access to transaction data in other SAP systems.

8VH

In contrast to other RemoteCubes, you do not need to program interfaces in the source system. Youuse the same extractors to select data in the source system, as you use for replicating data into BW.When you execute a query, every navigation step sends a request to the extractors of the assignedsource systems. Furthermore, the characteristic selection is transformed together with the selectionconditions for these characteristics according to the transfer rules for the transfer structure fields. Theyare passed on to the extractor in this form. The delivered data records go through the transfer rules inBW and are then filtered into the query again.

Since master data and hierarchies are not read directly by the source system, they need to be in BWalready when you execute a query.

0XOWL3URYLGHUV

'HILQLWLRQ

A MultiProvider is a special InfoProvider that combines data from a number of InfoProviders andmakes them available as a whole to reporting. The MultiProvider itself does not contain any data; itsdata comes exclusively from the InfoProviders it is based on.

It can consist of different combinations of the following InfoProviders: InfoCube, ODS object,InfoObject and InfoSet. The data from these objects can be combined in the MultiProvider with a unionoperation.



A MultiProvider allows reporting using several InfoProviders.

8VH

MultiProviders are used to increase the transparency and performance and to enable more flexibilitythrough more simple maintenance.

Example: Instead of creating plan and actual figures for an InfoCube, you create one InfoCube withplan figures and one with actual figures. This allows the integration of BW and APO.

MultiProviders form no joins, unlike what happens with InfoSets. Instead, they form a total quantity ofInfoProviders involved. From there, you determine the slow-moving items by using MultiProviders,since products creating no sales can also be displayed. If you were to used InfoSets in this case, onlythe products would be displayed that also exist for values.



6WDJLQJ�6FHQDULRV�ZLWK�3HUVLVWHQW�'DWD�6WRUDJHIn the following, staging scenarios are introduced, in which the data is stored on a medium-term basis.

��6WDQGDUG�6FHQDULR

'DWD�IORZ�

��

��! #"�$ %

&�('��)��*�� &+ ' ��)��*�� ,��-.� /0��1*2� �� -��/��3*.��

4 �65

� ��7(��/0� ��7��/0

�98;:�<=$�"�;>�?�%�"�@ A)B�C 8+DE:��"

8VDJH�

The process of using the standard scenario corresponds to the basic recommended procedure forstoring data in BW. In special cases, you can use the scenarios as described in the following.

��6WDJLQJ�ZLWK�2'6�2EMHFWV�ZLWKRXW�,QIR&XEHV

'DWD�IORZ�

��

��! #"�$ %

&+ ' ��)��*�� ,��-.� /0��1*2� �� -��/��3*.��

4 �65

� ��7(��/0� ��7��/0

�98;:�<=$�"�;>�?�%�"�@ ��

��F #"�$(%

8VDJH�

Use the staging process for storing data in an ODS object without InfoCubes, when the transactiondata is highly volatile and when there is a high demand for the changes made to reporting data, whichwas already loaded, to be permanently available. The status of documents must always be kept up-to-date. In turn, this requires the data, which is supported by the ODS object, to be overwritten.

This solution also makes it possible to use a second ODS object as storage for reporting.

As the ODS object data cannot be aggregated, this is not a good solution for reporting with mass data.



��6WDJLQJ�ZLWKRXW�2'6�2EMHFWV�ZLWK�,QIR&XEHV

'DWD�IORZ�

�� !�"��# � ��$�� %��

&'� ()��*�+� ��&��(��,�'��

-/./0

�!��1��()��1��()

.3254�687�9.5:�;�<�9!= >$?�@ 2�AB4#C�9

8VDJH�

Use a staging scenario without ODS levels if you can work without the advantages of an ODS object(cleansing, transforming, consolidating, integrating data from different processes, level of detail ofinformation, durability of the data). This applies in particular if the system already guarantees theintegrity of the data (CO-PA, General Ledger) and therefore works without saving the consolidateddata explicitly in BW, or if the data is extracted from a single source system.

��)XUWKHU�3URFHVVLQJ�IURP�,QIR&XEH�WR�,QIR&XEH

'DWD�IORZ�

�� !�"��# � ��$�� %��

�!��1��()��1��()

>$?�@ 2�AB4#C�9>$?�@ 2�AB4#C�9

8VDJH�

This scenario is also known as a data mart scenario and is characterized by the data flow fromInfoCube to InfoCube, which is possible within a BW System as well as between several systems.Data marts created like this offer better overview and maintenance of a dataset (snapshot) and allowyou to separate the data according to task area.

You can also use this scenario if you want to change an InfoCube after it has already been loaded withdata.

You are recommended to use a data mart scenario between two different BW Systems, if you areprocessing large amount of data. On the one hand it gives you better performance, on the other, theBWs remain more visible. In this way, you can separate the data according to task area. You alsohave the option of creating hub and spoke scenarios, which have a central BW where the data fromdistributed systems runs together and is standardized. This is where the data is made available fordata marts.



��2'6�6HUYHU�DQG�%:�6HUYHU

'DWD�IORZ�

��

>$?�@ 2�AB4#C�9�� . C� 9!7 <

8VDJH�

You have the option of using a BW server as the source BW and a BW server (target BW) forreporting. For this scenario, you need to use a BW server as the source BW, where the data iscleansed and updated in a complex process.

The source BW collects the data from the OLTP. It also cleanses and consolidates the data when it isupdated into ODS objects. There is a central data entry here, which is also an ODS server. As afurther process, the data is then replicated into the target BW in InfoCubes through the data martinterface. Reporting can take place once the master data has been uploaded.



6WDJLQJ�6FHQDULRV�ZLWKRXW�3HUVLVWHQW�'DWD�6WRUDJHIn the following, staging scenarios are introduced, in which the data is not stored on a long-term basis.

��6WDJLQJ�ZLWK�6$3�5HPRWH&XEHV

'DWD�IORZ�

�� )��# � ��$�� %��)��!��1��()��1��()

.3254�687�9.5:�;�<�9!=

.50*-�� 9!= 2!<�9�AB4#C�9

8VDJH�

SAP RemoteCubes are a suitable alternative to standard scenarios, if

• you need up-to-date availability of data from the SAP source system

• you only want to access small data sets sporadically, and replicating the data into BW would betoo time-consuming in comparison

• only a few users execute queries simultaneously in the requested dataset.

As long as a suitable extractor is available (you can check this in the tables RSOLTPSOURCE orROOSOURCE), an SAP RemoteCube query can replace a drill through in an SAP source system withthe help of the report/report interface. The data in both cases is real-time. However, a drill throughuses an OLTP report to present the data, whereas an SAP RemoteCube uses a BW report.

Restrictions:

• The source system must always be available.

• BW reporting in SAP RemoteCubes is an extra burden on the performance of the OLTP system.Performance is reduced even further when there are more users working on BW queries with SAPRemoteCubes and when the queries have a high level of aggregation.

• SAP RemoteCubes do not use update rules. The data to be presented in the query is takendirectly from the communication structure. You cannot add Business Logic with update rules.

• SAP RemoteCubes do not support navigation attributes.

• Master data and hierarchies must be replicated in BW.

You can also use RemoteCubes with a prototyping process with the generic extractor. You can alsoaccess external systems quickly and easily with the help of the DB link.

Since SAP RemoteCubes do not require persistent data storage in BW, changes to structures (extractstructure, transfer structure, transfer rules) in the entire staging process of the prototype phase can beperformed quickly.



��'DWD�0DUW�6FHQDULRV�ZLWK�6$3�5HPRWH&XEHV

'DWD�IORZ�

��

.50*-�� 9!= 2!<�9�AB4#C�9 � . C� 9�7�< >$?�@ 2�AB4#C�9��

8VDJH�

When you create a system landscape with several BW Systems, you have two alternatives fordistributing the transaction data: You can replicate the data beforehand, or only read it once it isrequested from the source system. You can use the SAP RemoteCubes for the second option. Therestrictions that apply when you use RemoteCubes with a SAP System are of little importance whenyou join two BW Systems. This can avoid the reduction of the source system (BW) performance,because suitable aggregates are used. The restrictions to system availability, navigation attributes,and master data still apply.

When you use a data mart scenario, it does not usually make sense to replicate data on documentlevel in all the connected BWs. Since users only rarely use the data on the connected BWs in detail,this purpose is well suited to the use of SAP RemoteCubes.



$GPLQLVWUDWLRQData Administration in the Business Information Warehouse comprises

• The load process supported by the Scheduler [Seite 350]

• Monitoring [Seite 377]

• Managing Data Targets [Seite 402]

• The Process Control [Seite 423].



6FKHGXOHU

'HILQLWLRQ

The Scheduler is the connecting link between the source systems and the SAP Business InformationWarehouse. Using the Scheduler you can determine when data (transaction data, master data, textsor hierarchies) is requested and updated and from which InfoSource, DataSource and source system.

The principle of the Scheduler goes back to the functionality of the SAP background jobs. The datarequest can be scheduled either straight away or with a background job and can be startedautomatically at a later point in time.

You get to the data request via the Scheduler in the Administration Workbench Modeling, by choosing,QIR6RXUFH�7UHH�→�<RXU�$SSOLFDWLRQ�&RPSRQHQW�→�<RXU�,QIR6RXUFHV�→�<RXU�6RXUFH�6\VWHP�→&RQWH[W�PHQX�(Right mouse button) →�&UHDWH�,QIR3DFNDJH�

8VH

Data is requested for a combination of application components, an InfoSource [Seite 271], aDataSource and a source system.

When requesting data, create a so-called InfoPackage [Seite 351] in the InfoSource tree in theAdministrator Workbench. In the InfoPackage, you set the conditions for the scheduling of the datarequest Therefore an InfoPackage is always assigned to just one InfoSource, one DataSource to thedata type that goes with it (transaction data, master data, texts, or only ever one hierarchy), and to onesource system.

If you create an InfoPackage, then this is saved with the current variant settings [Seite 372] asadministrative information.

,QWHJUDWLRQ

Data Provision

'DWD�7DUJHWV%XVLQHVV�,QIRUPDWLRQ

:DUHKRXVH�6HUYHU

6WDJLQJ�(QJLQH


��

��

��

��

��

��

��


,QIR6RXUFH


Extraction StructureExtraction Structure Extraction StructureExtraction Structure'DWD6RXUFH

'DWD6RXUFH

(Copy)Transfer StructureTransfer Structure



0RQLWRU0RQLWRU6FKHGXOHUData Request for DataSource

6FKHGXOHUData Request for DataSource

The Scheduler helps to load and update the data into the BW. You can check the BW loading andprocessing processes in the Administrator Workbench Monitor [Seite 378] . The data is available foranalysis after the BW processing process.



0DLQWDLQLQJ�,QIR3DFNDJHV

8VH

With the help of an InfoPackage, you determine the selection conditions in BW for the data requestfrom a source system.

InfoPackages have a connection to the BW transport system [Extern] and document management[Seite 479].

3UHUHTXLVLWHV

In this section, you can select the contents of the InfoPackages so that it can be scheduled. If you donot enter any specific selections, then all of the available data for the SAP Business InformationWarehouse DataSource will be requested from the source system. You only have to make a selectionwhen dealing with hierarchies. If you have previously selected a delta process then you only get theaffected delta for your selection. There is a maximum of one active delta selection for a combination ofInfoSource, DataSource and source system.

If you change already scheduled InfoPackages, your new selection is used in laterbackground jobs, for example, periodic runs. You have to create a new InfoPackage if youwant to continue to use the existing InfoPackage.

If you access an external system with the data request, you must make the data availablein special formats. You can find additional information about this in the sectionsMaintaining InfoSources (Flat Files) [Seite 289] and Maintaining InfoSources (ExternalSystem) [Seite 303].

3URFHGXUH

1. Highlight a source system in the InfoSource tree in the Administrator Workbench.

2. Choose &RQWH[W�PHQX��ULJKW�PRXVH�FOLFN��→�&UHDWH�,QIR3DFNDJH�and enter any alphanumeric ornumeric name for the InfoPackage.

Dialog box that follows will show you which source system you want to load data and to whichInfoSource. You will see the DataSources that are assigned to the InfoSource to which data isto be loaded.

3. Select a DataSource for which you want to load data into BW.

If the InfoPackage is scheduled, data is loaded into BW from the DataSource selected here.

Now go through the procedure for the relevant system:

Procedure for SAP Systems [Seite 352]

Procedure for Flat Files [Seite 353]

Procedure for External Systems with BAPI Functions [Seite 354]



3URFHGXUH�IRU�6$3�6\VWHPV,QIR3DFNDJH�ZLWK�7UDQVDFWLRQ�'DWD

1. Maintain the tabstrip: Select Data [Seite 357].

2. Maintain the tabstrip:Processing [Seite 363]

3. Maintain the tabstrip: Data Targets [Seite 366].

4. Maintain the tabstrip: Update Parameters [Seite 368].

5. Scheduling InfoPackages [Seite 355].

,QIR3DFNDJH�ZLWK�7H[WV�RU�0DVWHU�'DWD


2. Maintain the tabstrip: Processing [Seite 363]

3. With flexible updates, also maintain the tab strip Data Targets [Seite 366] for master data andtexts.



,QIR3DFNDJH�ZLWK�KLHUDUFKLHV

1. Maintain the tabstrip: Select Hierarchy [Seite 361].






3URFHGXUH�IRU�)ODW�)LOHV,QIR3DFNDJH�ZLWK�7UDQVDFWLRQ�'DWD

1. Maintain the tabstrip: External Data [Seite 370].

2. Determine the external data parameters.








2. Determine the external data parameters for InfoPackages with master data.



5. Also maintain the tab strip Data Targets [Seite 366] for master data and texts, when up-datingflexibly.





2. In the ‘External data parameters’ tabstrip, determine the number of file headers you want to ignoreduring the loading process.







3URFHGXUH�IRU�([WHUQDO�6\VWHPV�ZLWK�%$3,�)XQFWLRQV,QIR3DFNDJH�ZLWK�7UDQVDFWLRQ�'DWD


2. Maintain the tabstrip: External data parameters.

3. Make the corresponding BAPI-specific selections.







2. With an InfoPackage for master data, maintain the tabstrip: External data parameters.



5. Also maintain the tab strip Data Targets [Seite 366] for master data and texts, with flexibleupdates.











6FKHGXOLQJ�,QIR3DFNDJHV

8VH

Determine the trigger conditions for the InfoPackage on the Schedule tab strip.

Scheduled InfoPackages and InfoPackage groups are displayed with a clock icon in the AdministratorWorkbench. You can delete or change the scheduled InfoPackages and InfoPackage groups at anytime.

If you change already scheduled InfoPackages, your new selection is used in laterbackground jobs, for example, periodic runs. You must create a new InfoPackage if youwant to keep the existing InfoPackage, in order to continue using it in the background.

If you access an external system with the data request, you must make the data availablein special formats. You can find additional information about this in the sectionsMaintaining InfoSources (Flat Files) [Seite 289] and Maintaining InfoSources (ExternalSystem) [Seite 303].

3UHUHTXLVLWHV

You have defined the conditions for data request in the Scheduler tab strip.

3URFHGXUH

1. Select whether you want to start the batch load process immediately or later on.

Scheduling in the background is not possible for data requests from a client work station.You can find additional information about loading flat files under Maintaining InfoSources(Flat File) [Seite 289] and under Tabstrip: External Data [Seite 370].

If you wish to process the data request in the background, select the radio button 6WDUW�/DWHU�LQ%DWFK and define the required start time using the function 6FKHGXOLQJ�2SWLRQV. If a start timealready exists for this data request then a tick indicates this. You can also enter an end datefor the data request with a background job.

If you later schedule an InfoPackage in the Batch, the background request job runs untilall data is updated in BW. This is displayed with a corresponding indicator in the 6FKHGXOHtab strip.� The load process remains active until the data is up-dated.

2. If you want to trigger an event that is to be used in the event collector after it was processedsuccessfully or incorrectly, select: Subsequent Processing [Seite 448]. You can find additionalinformation about process control with the help of the event collector under Process Control [Seite423].

For controlling and monitoring BW processing, we recommend using process chains[Seite 424] as of Release 3.0A.

3. Select 6WDUW�in order to start or schedule data loading immediately.

5HVXOW

The load process is started either immediately or later in the background, depending on your settings.You can use the Monitor [Seite 378] to check whether the load process was successful or not.



6HOHFWLRQ�&ULWHULD�IRU�WKH�6WDUW�'DWH�ZKHQ�6FKHGXOLQJ�LQ�WKH�%DFNJURXQG�

The data request can be scheduled once or periodically. In this case, periodically means that youdetermine the loop in which the data is to be scheduled in the background job. You can, for example,select at once and periodically (hourly, daily or weekly, monthly, or other periods). The data requestcan also be controlled according to events.

2QH�RII�VFKHGXOLQJ�RI�WKH�GDWD�UHTXHVW

1. Select the radio button 6WDUW�'DWD�/RDG�,PPHGLDWHO\�or 6WDUW�/DWHU�LQ�%DWFK.�

− Using the function 6FKHGXOLQJ�2SWLRQV, you can define the required start date.

− Save your entry of the 6WDUW�'DWH�9DOXHV�

You now return to the start screen.

2. Start the job.

3HULRGLF�VFKHGXOLQJ�RI�WKH�GDWD�UHTXHVW

1. Select the function 6FKHGXOLQJ�2SWLRQV�and select the required start date values�

2. Set the indicator for ([HFXWH�-RE�3HULRGLFDOO\�and select a period using the function 3HULRG�9DOXHV�


You now return to the start screen.

4. Select the runtime of the periodic job by highlighting one of the radio buttons.

To prevent the system from endlessly requesting data you can limit the data request with anumerical entry in the field 7HUPLQDWH�$IWHU�;�5XQV. The number you enter here determinesafter how many runs the system should stop. This means that the data request for thisexample will be terminated after the period 1997005 to 1997006. The values of the period arederived from the difference between the 7R�9DOXH�and )URP�9DOXH��.

You can find out about further possibilities for defining a start date and how to proceed, in the basisdocument of the SAP Library in the section &RPSXWLQJ�&HQWHU�0DQDJHPHQW�→ %DFNJURXQG3URFHVVLQJ�in the R/3 library.



7DEVWULS��6HOHFW�'DWD

8VH

Determine the selection values for the InfoPackage in the 6HOHFW�'DWD�tab strip.

You can determine selection boundaries not only for InfoObjects mapped in the transfer structure, butalso for unmapped fields in the source system. The fields are displayed in the 7HFKQLFDO�1DPH�LQ6RXUFH�6\VWHP�'LVSOD\HG�column in the selection table. So that you can tell the difference betweenInfoObjects and fields when the selections are displayed, the fields are shown in brackets (forexample, with the initialization selection for source systems in the Scheduler).

You can enter the selection values either directly in the )URP�9DOXH�and if necessary the 7R�9DOXHfields, or you can use a variable for selection limit [Seite 359].

When using selection criteria, InfoObject or field data corresponding to the selection limit is requestedfrom the source system. With InfoObjects or fields for which no variable selections were determined,all available data is requested from the source system.

6HOHFWLRQ�/LPLWV�IRU�'DWD�IURP�)LOH��DQG�([WHUQDO��6\VWHPV�

It is also possible to determine selection criteria for data from files and external systems. Only recordsthat meet the selection criteria are loaded.

To determine field selections in the Scheduler, highlight them first in the transfer structuremaintenance in the column 6HOHFWLRQ and saves and activates the transfer structure.

By determining the selection criteria, you can carry out the functions $XWRPDWLF�'HOHWLRQ�and CheckingData Consistency of the Requests in the InfoCube [Seite 413] for data from files and external systems.

&RQYHUVLRQ�([LWV

When entering the selection, the conversion exits displayed in the selection table are executed in theOLTP and the results are temporarily saved in the BW. If a selection has already been converted, it isin the BW; if it is not yet in the BW, conversion takes place in the OLTP.

If conversion cannot take place in the OLTP, because the system cannot be accessed orthe OLTP conversion exit is not running properly, conversion takes place in the BW. If thisis not possible either, the &RQYHUVLRQ�([LW field is ignored, meaning that the selectionsmust be entered in an internal format. In this case, entering in external format will lead toerrors in the load process.

You can also deactivate the conversion exit generally with the corresponding pushbuttonon the 6HOHFW�'DWD�tab strip. Here, enter the selections in an internal format too.

$UFKLYH�6HOHFWLRQV

If you reload data from an archive file [Extern], select your archive file by using the pushbutton $UFKLYH6HOHFWLRQ.

1RWHV

• If a DataSource field with the field name LANGU or SPRAS is assigned to the InfoObject0LANGU, the field does not appear as a selection field in the Scheduler, despite being availablefor selection. In this case, the source system implicitly requests all languages from the languagevector active in BW.

• If time-dependent data is loaded, the time interval is determined in the Scheduler in the 8SGDWH3DUDPHWHU tab strip. Therefore, the DATETO, DATEFROM fields, as well as the fields assigned tothe InfoObjects 0DATETO and 0DATEFROM are not available as selection fields on the 6HOHFW'DWD�tab strip.



9DULDEOH�6HOHFWLRQ�&KDQJH�LQ�%DFNJURXQG�3URFHVVLQJ�

8VH

The entry column 7\SH��9DULDEOH� on the 6HOHFW�'DWD tab strip indicates a variable time frame in whichthe data should be requested. The variables are not replaced by concrete values until a request ismade. There are eight options:

9DULDEOH 'DWD�UHTXHVW 'HVFULSWLRQ

0 Yesterday (12am – 12am)

1 Last week (Monday-Sunday)

2 Last month (1. (first day - last day ofprevious month)

3 Last quarter (1. (first day - last day ofprevious quarter)

4 Last year (01. (January 1 – Dec 31 ofprevious year)

5 user time selection see below

6 ABAP Routines see below

7 OLAP variables see below

)XQFWLRQV

7LPH�VHOHFWLRQV�ZLWK�WKH�KHOS�RI�YDULDEOHV��WR��

The variables 0-4 only refer to date fields of the data type '$76.

XVHU�WLPH�VHOHFWLRQ

Type 5 gives you a free selection of all fields.

A further dialog box will appear when selecting this variable. In this dialog box you can freelylimit the values of the fields as well as determine the next period value and the number ofperiods until a repetition.

Enter the following selection values for an InfoPackage for variable 5:

6HOHFWLRQ�YDOXH (QWU\

From value 1 1997001

To value 1997002

From value 2 1997003

Number of periods 12

Period type 1

The first data is requested for the time span Jan. 1997 (1997001) to Feb. 1997 (1997002)inclusive.

The second data request, meaning the second period would then take place for the timespan March 1997 (1997003) to April 1997 (1997004) inclusive.

After the 12th run, the system starts counting from 1998001.



Such a period is only sensible if period type 1 (year/period-like) has been selected.

6HOHFWLRQ�YDOXH (QWU\

From value 1 10

To value 18

From value 2 20

Number of periods 5

Period type 0

The first data of the InfoPackage is requested from value 10 to 18. The second datarequest encompasses the values 20 - 28. As period type 0 has been selected, the requestis carried out with ongoing values (30-38; 40-48; 50-58; 60-68). After the 5th period,meaning after values 60-68 have been requested, the Scheduler starts over again with thevalues 10-18.

6HOHFWLRQV�XVLQJ�DQ�$%$3�URXWLQH

You can even create an ABAP program that restricts the InfoObject data or field data to be requested.To do this, select type 6 and confirm your selection. This brings you to a screen in which you enter aname for the ABAP routine. After entering the name you get to the Editor and can enter your owncoding. The ABAP routine has access to all selection fields and is the last to be processed in theruntime.

6HOHFWLRQV�E\�DQ�2/$3�YDULDEOH

By selecting and confirming type 7, you can use an OLAP variable as selections for requesting datafor an InfoObject. You can create variables by choosing %XVLQHVV�([SORUHU�Å�0DLQWDLQ�9DULDEOHV.

You can only use variables that do not use a replacement path or require manual entry orcompulsory entries.

You can display the selections for a certain variable by choosing &KHFN. The system displays theselections that would be determined with a data request.



7DEVWULS��6HOHFW�+LHUDUFK\

8VH

Use this tab strip to select the hierarchy that you want to load and make hierarchy-specific settings forthe load process.

)XQFWLRQV

The hierarchies for your DataSource InfoPackage are in the selection table.

There are three options to store a loaded hierarchy in BW.

• )XOO�8SGDWH

The hierarchy is stored under the selected or determined technical name in BW. A hierarchywith the same technical name in BW is overwritten if necessary.

• 6WRULQJ�WKH�+LHUDUFK\�DV�D�6XEWUHH�RI�D�7DUJHW�+LHUDUFK\

The loaded hierarchy is added to a tree that already exists in BW, the WDUJHW�KLHUDUFK\��as asubtree. The target hierarchy node, to which the root nodes of the VXEWUHH�KLHUDUFK\correspond, are called LQWHUIDFH�QRGHV. This is the node that refers to the same InfoObject inthe target and subtree hierarchies. It also has the same technical name.

There are two options to store subtree hierarchies in BW:

• 6XEWUHH�,QVHUW

The hierarchy is inserted in an existing hierarchy as a subtree, without nodes being deletedfrom the target hierarchy.

If a subtree is inserted for a second time, there will be two sets of each subtree hierarchynode amongst the interface nodes. The load process is terminated for this reason.

• 6XEWUHH�8SGDWH

The hierarchy is inserted in an existing hierarchy as a subtree, and the old subtree is replacedby the new one if required.

If a subtree update is executed again, all target hierarchy nodes that are found amongstthe interface nodes are deleted, before the new subtree is inserted amongst the interfacenodes.

You can find further information about inserting and updating subtrees in the Loading SubtreeHierarchies. [Seite 182] section.

$FWLYLWLHV

1. You can select whether a hierarchy should be loaded or whether it should be automaticallyactivated or designated for automatic activation after being successfully loaded.

If the selected hierarchy is used in an aggregate, it cannot be activated directly after beingloaded. It is designated for activation and activated when a hierarchy or attribute is nextchanged.

An inactive hierarchy cannot be used in queries.

2. To avoid overwriting an existing BW query when you load a new hierarchy which has the samename but which comes from a different source system, choose 5HQDPH�+LHUDUFK\�$IWHU�/RDGLQJand enter a new technical name. The hierarchy is stored under this new technical name and theoriginal technical name from the source system is not used.



Loading an SAP cost center hierarchy with the same name from different source systems.

3. When you want to load a hierarchy from an external system from a file via BAPI , you need firstlyto create a hierarchy header. This is because the file or the external system only delivers thestructure of the hierarchy. You cannot select the hierarchy for the load process until the hierarchyheader has been created.

6HH�DOVR�


4. When you create an InfoPackage for a hierarchy from the OLTP, the system displays hierarchiesmade available by a DataSource in the OLTP for selection. The system saves these entries andmakes them available in the selection table again, if you want to select hierarchies in thisInfoPackage once more. To display the latest OLTP hierarchy entries for the DataSource, refreshthe table using the $YDLODEOH�+LHUDUFKLHV�,Q�7KH�2/73�pushbutton.



7DEVWULS��3URFHVVLQJ

8VH

You can use this tabstrip to determine to where the data should be updated.

3UHUHTXLVLWHV

If you want to update the data using the PSA, you have set the transfer method to 36$ in the transferrules maintenance.

If you want to execute the data transfer with IDocs, you have set the transfer method to ,GRF�in thetransfer rules maintenance.

We recommend you use the PSA transfer method.

)XQFWLRQV

36$�7UDQVIHU�0HWKRG

Different options are available for data update when using the PSA transfer method. Upon selection,the balance between data security and performance for the loading process is weighed.

• 36$�DQG�'DWD�7DUJHWV�,QIR2EMHFWV�3DUDOOHO

This is a method to update data into the PSA and the data targets [Seite 92] with a high levelof performance. BW receives the data from the source system, writes it to the PSA, and startsthe update immediately, in parallel, in the corresponding data target.

For every data packet, a process is started to write the data from this data packet into thePSA. If the data is successfully updated in the PSA, a second parallel process is started. Inthis process, the transfer rules are used for the package data records, data is adopted by thecommunication structure and finally written to the data targets.

The maximum number of processes, which is set in the source system in customizingfor extractors, does not affect the number of processes in BW in a restrictive way.Therefore, many dialog processes in BW could be necessary for the loadingprocess. Make sure that enough dialog processes are available in the BW system.

If the data packet contains incorrect data records, you have several options allowingyou to continue working with the records in the request. You can specify how thesystem should react to incorrect data records You can find further information inthe section Treating Data Records with Errors [Seite 375].

You also have the option of correcting the data in the PSA [Seite 391] and updating itfrom there.

• 36$�DQG�WKHQ�LQWR�'DWD�7DUJHW�,QIR2EMHFW

With a VHULDO update of data in the PSA, and in the data targets, a process is still started perdata package that writes the data package to the PSA. When the data has been successfullyupdated to the PSA, the same process writes the data to the data targets afterwards.

Compared with a parallel data transfer, you have better control over the whole data flow with aserial update of data, because the BW carries it out using only one process per data packet. Amaximum of only so many dialog processes are necessary for each data request in the BWsystem. This corresponds to the settings you made in the customizing for the extractors in themaintenance of the control parameters.



If the data packet contains incorrect data records, you have several options allowingyou to continue working with the records in the request. You can find furtherinformation in the section Treating Data Records with Errors [Seite 375].

You also have the option of correcting the data in the PSA [Seite 391] and updating itfrom there.

• 2QO\�36$

Using this method, data is written to the PSA, and not updated any further. This updatemethod was only previously available for transaction data. You can now load master data andtexts exclusively into the PSA.

You have the advantage of having data stored safely in BW and having the PSA suitable as apersistent incoming data store for mass data as well. The respective setting for the maximumnumber of processes in the source system can also have a positive impact on the number ofprocesses in BW.

To further update the data automatically in the corresponding data target, wait until all the datapackets have arrived and been successfully updated in the PSA, select 8SGDWH�LQ�GDWD�WDUJHWfrom the 3URFHVVLQJ tab page when you schedule the InfoPackage in the Scheduler.

You can find additional information about the options to upload data from the PSA and into thedata targets under Type of Data Update [Seite 389] in the section 2QO\�36$�→�)XUWKHU3URFHVVLQJ�IURP�36$.

Handling Doubled Data Records [Seite 374] (only possible with the processing type2QO\�36$):

The system sets the 'DWD6RXUFH�7UDQVIHUV�'RXEOH�'DWD�5HFRUGV indicator for masterdata and text DataSources that transfer potentially double data records for a keyto the BW. The indicator ,JQRUH�'RXEOH�'DWD�5HFRUGV�is also set by default in thiscase.. In BW, the last data record of a request is updated for a particular key bydefault, when data records are transferred more than once. The remaining datarecords are ignored for this key in the same request. If the ,JQRUH�'RXEOH�'DWD5HFRUGV indicator is not set, double data records will cause an error. The errormessage is displayed in the monitor.

• Only Data Target/InfoObject

We recommend this method exclusively for loading from flat files or from data sources that arealways available. This is because the data is not always saved persistently into an incomingdata store. This saves hard disk space, although it leads to a loss of the following: datasecurity, an option to rebuild processes, and simulation options.

,'RF�7UDQVIHU�0HWKRG

The following options are available for data update when using the Idoc transfer method:

• $/(�LQERXQG�SURFHVVLQJ�DQG�GDWD�WDUJHW�,QIR2EMHFW

In this method, data is loaded in BW ALE inbound processing, and updated further into thedata targets directly.

• 2QO\�$/(�LQERXQG�SURFHVVLQJ

In this method, data is loaded in BW ALE inbound processing, but not updated further. Therequest appears in the monitor as incorrect. You can manually update the data further fromhere into the data targets.

1RWH

When you send too many data packages that are too small, too many monitor logs are written forthem. This has a negative effect on the monitor run time.



We recommend a data package size of 10,000 to 50,000 data records. With mass data (requests witha size of two to three million records), the data package size can be from 50,000 to 100,000 records.However, the required memory depends on not only the data package size setting, but also the widthof the transfer structure, the required memory of the affected extractor, and, for large data packages,the number of data records in the package.

6HH�DOVR:

Documentation for customizing extractors in the source system, especially the section&RQWURO�3DUDPHWHUV�IRU�'DWD�7UDQVIHU, is maintained under *HQHUDO�6HWWLQJV. You reachthe customizing for the extractors by using the source system tree in the AdministratorWorkbench – Modelling. Choose &XVWRPL]LQJ�([WUDFWRUV for your source system by usingthe context menu (right mouse click) or choose the transaction SBIW directly in yoursource system.

&RQVLVWHQF\�&KHFN�IRU�&KDUDFWHULVWLF�9DOXHV

When you set the &RQVLVWHQF\�&KHFN�IRU�&KDUDFWHULVWLF�9DOXHV�indicator, a check only takes place inthe update rules for two things: Firstly, for the loading of master data and transaction data, and also foractivating hierarchies after reading the data from PSA or IDoc. The InfoObject definition is checked.

The characteristic values are checked for

• the use of small characters,

• the use of special characters,

• the plausibility of date fields,

• the plausibility of time fields,

• the use of character values in the fields of the NUMC data type, and

• the correct observance of the ALPHA conversion routine

• .

.

Error messages are issued in the monitor.

You should always select this indicator with new data as well as non-SAP data during thetest phase. If it was good quality data (several data imports without incorrect values), theindicator for the productive area should be deactivated, because using this functionworsens load performance.



7DEVWULS��'DWD�7DUJHWV

Use this tab strip to determine to which InfoCubes or ODS objects, when updating flexibly, to whichInfoObject master data- or text table, the data for a data request is updated.

You can also get to the update rule maintenance from this screen, if the update rules have not beenactivated yet.

Via 0DLQWDLQ�'DWD�7DUJHW�&RQWHQWV , you can get to Data Target Management [Seite 402].

Use the pushbutton in the Automatic Similar/Same Request Deletion From the InfoCube [Seite 367]�todetermine the selection criteria to delete data from the InfoCube. After successfully loading the newrequest, deletion or cancellation is carried out automatically according to the selection criteria. You canonly cancel a request if no exception aggregation has been defined in the InfoCube or in the updaterules, and if all InfoObjects are updated cumulatively.



$XWRPDWLF�5HTXHVW�'HOHWLRQ�IURP�WKH�,QIR&XEH�ZKHQ/RDGLQJ

8VH

To make available the data that is to be scheduled with an InfoPackage only once in an InfoCube, youcan delete from the InfoCube requests with partially overlapping or similar selection conditions andrelevant deletion selections that are already available in the InfoCube

When loading new data into the InfoCube, the content is checked using the selection conditions for anInfoSource/DataSource/Source system combination to see if overlapping data has been loaded intothe InfoCube. In this way the data that has been loaded into the InfoCube is not analyzed. Instead, theselection conditions that you determined in the Scheduler for InfoObjects are compared.

This function reduces the dataset in BW to the size necessary for analysis and redundancies areavoided.

)XQFWLRQV

You select the variable deletion conditions for transaction data when scheduling the InfoPackage thatloads the new data.

With the pushbutton in the column $XWRPDWLF�'HOHWLRQ�RI�6LPLODU�6DPH�5HTXHVWV�IURP�,QIR&XEH in the'DWD�7DUJHWV tab strip, the dialog box 'HOHWLRQ�RI�UHTXHVWV�IURP�WKH�,QIR&XEH�DIWHU�8SGDWHappears.You can select basic delete conditions, delete restrictions with selection conditions, deleterestrictions according to date or other delete conditions. Another option for determining deleteconditions is creating a user routine for the InfoPackage and the InfoCube. In this routine you canexclude requests from deletion or plan additional requests for deletion.

After successfully loading the new request, deletion or cancellation is carried out automatically.

You can determine whether requests are cancelled with or without displaying a warning in theScheduler under the path 6FKHGXOHU�Å�7HVW�'HOHWLRQ�6HOHFWLRQV�DW�6WDUW�

Canceling a request is only possible if no exception aggregation has been defined in the InfoCube orin the update rules and all InfoObjects are updated with summation.



7DEVWULS��8SGDWH�3DUDPHWHUV

8VH

On the Update Rule Parameters tabstrip, specify the update mode, the type of update in the datatargets, error handling when loading and updating the data further, and time selection for time-dependent data.

8SGDWH�0RGH

The following update functions are available in the Scheduler:

)XOO�8SGDWH

A full update requests all data that corresponds to the selection criteria you determined in theScheduler.

In a certain period of time specified in the Scheduler, 100 000 data records areaccumulated. With a full update, all 100 000 data records are requested.

'HOWD�8SGDWH

Before you can request a delta update, you must first initialize the delta process.

A delta update requests only the data that has been accumulated since the last update, and addsthese to the database.

,QLWLDOL]LQJ�WKH�'HOWD�3URFHVV

For selection criteria that do not overlap, several initialization criteria are possible for initializing thedelta process when scheduling InfoPackages for transaction data from an SAP system. This gives youthe option of loading the relevant data for the delta process, step by step into the Business InformationWarehouse. For example, you can load the data into BW for cost center 1000 in the first step, and thedata for cost center 2000 in the second.

A Delta requested after several initializations, contains the sum of all the successful initial selectionsas a selection condition. This selection condition can then no longer be changed for the delta. In thisexample, data is loaded into BW for cost centers 1000 and 2000 with a delta.

The selections for initialization are made in the Scheduler on the tabstrip 6HOHFW�'DWD.

You can display all initializations for a DataSource in the Scheduler by choosing 6FKHGXOHU�Å,QLWLDOL]DWLRQ. You can see whether an initialization selection has been carried out and what status ofthe initialization has. If no data is found in the source system, the initialization is not carried out. Fromthis dialog box, you can also transfer initial selections into the Scheduler, and delete selectedinitializations again. Choosing the pushbutton ,QLWLDOL]DWLRQ�5HTXHVW�6WDWXV brings you to the Monitor,where you can check the data request.

For test purposes, you can initialize the delta process without transferring data. For this, the relevantindicator must be set on the tabstrip 8SGDWH�3DUDPHWHUV in the Scheduler. The initialization then runswithout you having to load any data.

It is possible to carry out more than one initialization of the delta process only forextractors that are available from the R/3 Plug-in PI 99(-A), that is, BW BCT 2.0Aextractors.

(UURU�+DQGOLQJ

The Error Handling [Seite 375] options give you the possibility to determine how the system behavesfor the following processing steps:

• Transfer rules



• Update rules

• Master data, text, and hierarchy update

• InfoCube update

• Referential integrity [Seite 282] of an InfoObject against master data tables or ODS objects on thecommunication structure level

7LPH�6HOHFWLRQ�)RU�7LPH�'HSHQGHQW�'DWD

Various options are available for the selection of time-dependent data that you want to load into theBW:

• fix time selection

• create a routine

• use variables

The active 'HOHWH�pushbutton shows you that a routine or variable was determined for the timeselection.

You can create variables by choosing %XVLQHVV�([SORUHU�→�0DLQWDLQ�9DULDEOHV. You canonly use variables that do not use a replacement path or require manual entry orcompulsory entries.

You can display the selections for a certain variable by choosing &KHFN. The systemdisplays the selections that would be determined with a data request.



7DEVWULS��([WHUQDO�'DWD

8VH

Use this tabstrip to determine from which file you load data.

$FWLYLWLHV

8. Specify whether the file from which you want to load data is stored on a workstation or on anapplication server.

For reasons of performance, we recommend that you store the data on an applicationserver and load it into BW from there. In this way, you can load the data in thebackground.

9. Select the data to be loaded using the value help of the )LOH�1DPH field or enter the file namedirectly, for example &��'DWHQ�86�.RVWHQ��FVY.

You can also create a routine to determine the name of your file. The active pushbutton 'HOHWHdisplays whether a routine has been created. If this pushbutton is inactive, the file name isdirectly interpreted in the )LOH�1DPH�field.

For files from an application server, the file name is included automatically in the selectionoptions (F4 help) after saving.

10. Determine whether the system should load the data from a control file.

A control file is an ASCII file that already contains the control commands required by theScheduler.

a. When the file is a control file, select the appropriate radio button. No further entries arerequired, and the entered data is automatically controlled.

b. If the file is not a control file, determine whether you want to load data from an ASCII file or aCSV file.

− When you load data from an ASCII file, the data is requested with a fixed data record length.

If you want to upload a large amount of transaction data from a flat file using the IDoctransfer method, and if you have the option of specifying the file type of the flat file, werecommend you create the flat file as an ASCII file. From a performance point of view,uploading the data from an ASCII file is the most suitable method. Generating an ASCIIfile might however mean a larger workload.

− When you load data from an Excel CSV file, determine the 'DWD�6HSDUDWRU and the (VFDSH&KDUDFWHU�

In the 'DWD�6HSDUDWRU�field, enter the data separator that your file uses to separate fields.

When the data separator is a part of the value, the system shows this in the file byenclosing the value in particular start and end characters. Enter these start and endcharacters in the (VFDSH�&KDUDFWHULVWLFV�field.

You have chosen the ; character as a separator. However, your file contains the value��.for a field. If you set ³ as the escape character, the value in the file must be ��³, so that �� is loaded into BW.

In a text editor (for example, Notepad) check the data separator and the escape charactercurrently being used in the file. These depend on the country version of the file you used.



When you select the +H[�indicator, you can specify the data separator and the escapecharacter in hexadecimal format. When you have entered the character for the dataseparator and the escape character, these are displayed as hexadecimal code, after theentries are checked. A 2 character entry for a data separator or an escape sign is alwaysinterpreted as a hexadecimal entry.

6HH�DOVR�

Maintaining InfoSources (flat files) [Seite 289]

In this section, particularly take the pre-requisites for loading from CSV and ASCII files intoconsideration.



9DULDQWV

8VDJH

The creation of InfoPackages and their display in the Administrator Workbench are dependent on thevariants.

A variant is user-defined grouping characteristic of the Scheduler. Every InfoPackage and everyInfoPackage group is assigned to a variant. There are no empty variants, which means you mustcreate a variant. The variant can be up to 12 characters in length and is case-sensitive. The systemonly recognises the variant when you have created and saved an InfoPackage (or an InfoPackagegroup) for the variant.

After saving a change in the Scheduler, the variant is also saved so that the variant is there for theuser when he/she next calls up the Scheduler.

You cannot delete a variant.

The variant &XVWRPHU is set as a global setting by the customer.

However, you can switch the variants or create a new one at any time in the Administrator Workbenchusing 6HWWLQJV�&KDQJH vDULDQW.

([DPSOH

You can use the user name as a variant or other names (of departments, for example)



0DLQWDLQLQJ�'DWD�7UDQVIHU�&RQWURO�3DUDPHWHUV�IRU'DWD6RXUFHV

8VH

In the BW Scheduler you have the option of determining control parameters for data transfer forindividual DataSources. You can do this by choosing 6FKHGXOHUÅ�'DWD6RXUFH��'HIDXOW�6HWWLQJV�IRU'DWD�WUDQVIHU. In this way you can, for example, update transaction data in larger data packets in thePSA. Smaller packets guarantee faster processing if you want to update master data in the dialog.

You can determine the size of the data package, the number or parallel processes for data transferand the frequency with which the status IDocs are sent, for every possible update method for OLTPdata sources.

You can determine the size of the data package as well as the frequency with which the Idocs are sentfor a file data source.

,QWHJUDWLRQ

2/73�'DWD�6RXUFHV

The settings you made in the Scheduler override the settings made in extractor-customizing for SAPsource systems for a particular DataSource and a particular update method.

For transferring data from an OLTP source system in general, maintain the control parameters for datatransfer in extractor-customizing. In extractor-customizing you get to the corresponding source systemin the source system tree of the BW Administrator Workbench by using the context menu. Choose%XVLQHVV�,QIRUPDWLRQ�:DUHKRXVH�Å�*HQHUDO�6HWWLQJV�Å�0DLQWDLQLQJ�&RQWURO�3DUDPHWHUV�IRU�'DWD7UDQVIHU�to display or to change the settings for data transfer on a source system level.

)LOH�'DWD6RXUFHV

Use those settings that you made in the Scheduler to control the setting that you made under%XVLQHVV�,QIRUPDWLRQ�Å�/LQNV�7R�2WKHU�6\VWHPV�Å�0DLQWDLQ�&RQWURO�3DUDPHWHUV�)RU�'DWD�7UDQVIHUfor a particular DataSource



+DQGOLQJ�'RXEOH�'DWD�5HFRUGV

8VH

In a request, DataSources can transfer several data records to the BW for a key of non-time-dependent- texts or -master data. If data records are transferred to the BW more than once within arequest, this could be due to the application. You should not see it as an error. The BW providesfunctions that can deal with such an ambiguity when handling double data records.

Here, the DataSource transfers the information about whether it has the potential to transfer doubledata records. This information is transferred to the scheduler when a new InfoPackage is created. Inthe scheduler, you have the option of determining how the system behaves with double data records.

3UHUHTXLVLWHV

• The DataSource transfers potential double data records.

• and non-time-dependent texts and master records are principally involved here.

)XQFWLRQV

If the above pre-requisites are satisfied, the BW system places the 'DWD6RXUFH�7UDQVIHUV�'RXEOH�'DWD5HFRUGV�indicator�on the Processing [Seite 363] tab strip.

The indicator ,JQRUH�'RXEOH�'DWD�5HFRUGV�is also set in this case by default. In BW, the last datarecord of a request is updated for a particular key by default, when data records are transferred morethan once. The remaining data records are ignored for this key in the same request.

To maintain consistency, ignoring double data records is only possible when the data isupdated serially. Serial updating is when data is firstly updated into the PSA andsubsequently, after being successfully written to the PSA, is updated to the InfoObjectmaster data- or text-table. This update method was only previously possible fortransaction data. You can also change the corresponding settings for master data andtexts in the scheduler. If a DataSource transfers potential double data records or if youmanually set the ,JQRUH�'RXEOH�'DWD�5HFRUGV�indicator, the 36$�2QO\�update isautomatically selected in the scheduler.

If the ,JQRUH�'RXEOH�'DWD�5HFRUGV indicator is not set, double data records will cause an error. Theerror message is displayed in the monitor.

Double data record recognition is connected with the characteristic key. It is thereforelogical that the DataSource should provide all characteristic key fields. If this is not thecase, for example when key fields were hidden from the extract structure, the system willnotify you when the transfer rules are activated.

$FWLYLWLHV

You can also determine how double data records within a request are handled in the scheduler,independently of whether the setting allowing these potential double data records to be delivered wasmade to the DataSource or not. This is useful when the setting was not made to the DataSource butwhen the system knows from other sources that double data records are in transfer ( when flat filesare loaded for example). You can then manually set the ,JQRUH�'RXEOH�'DWD�5HFRUGV�indicator in thescheduler.



7UHDWLQJ�'DWD�5HFRUGV�ZLWK�(UURUV

8VH

Using the (UURU�KDQGOLQJ function on the 8SGDWH�SDUDPHWHUV tab strip in the Scheduler, you have theoption of controlling the behavior of the BW system, should errors in data records [Extern] occur whenyou are loading data using the PSA.

The system checks for errors in data records:

• in the transfer rules

• in the update rules

• when data is updated into the master data-, text- or hierarchy tables.

• when data is updated to the InfoCube.

• when checking for referential integrity [Seite 282] within an InfoObject against the master datatables or ODS objects on a communication structure level.

)XQFWLRQV

Incorrect records arising in transfer rules, update rules, when updating to a data target, or whenchecking for referential integrity, are highlighted and returned to the error handler. The error handlerlocates the original PSA records and writes the corresponding log. This function is as yet unavailablefor updating to ODS objects.

You can control how the system responds to incorrect data records using the (UURU�+DQGOLQJ�functionon the 8SGDWH�3DUDPHWHU�tab strip in the Scheduler.

�$FWLYLWLHV

1. Select how the system should react to incorrect data records

a. No update, no Reporting (default)

If errors do occur, the update of the entire data packet is canceled. The request is notreleased for Reporting. The records check, however, continues.

b. Updating valid records, no Reporting (request red)

This option enables you to update valid data that is released for Reporting only after theAdministrator has checked the incorrect, not updated records, and has manually released therequest.

c. Updating valid records, Reporting possible

The valid records can be reported on immediately. Automatic follow-up actions are alsocarried out, such as adjusting the aggregates.

With option a) the incorrect records are marked in red in the PSA maintenance. You candisplay the relevant error messages amodally, edit the records, and update the requestmanually. If it was not possible to write into the PSA (hierarchy or transfer method IDoc)an application log is written instead.

With options b) and c) a new request that is only read into the PSA is formed from theincorrect records. Here, you can edit the records of the new request in the PSA, and startthe update manually.

If errors arise when an InfoCube is updated, new requests are generated for incorrectrecords for each InfoCube combination. Amongst these requests, the incorrect records arebooked in the PSA. These new requests entered the InfoCubes for which there wereincorrect records, as data targets. If,for example, a record was booked into two InfoCubesby mistake, a request is generated for this record, which contains both InfoCubes as data



targets. In the PSA tree, the requests appear as successfully booked in the PSA. Thesenew requests can then be triggered for a renewed update to the InfoCubes.

2. Specify after how many incorrect data records the load process should be terminated. You candisplay the errors arising up to that point in the PSA. If you do not enter after how many incorrectrecords, termination should occur, handling incorrect data records is not active. In this case, theupdate will terminate after the first error.

3. Select how the BW system should react when the number of data records received by the BW isnot the same as the number of data records updated in the BW.

There can be a difference between the number of received and booked records. This canoccur

• in the transfer rules

• in the update rules

• when updating

records are sorted, aggregated or added.

If you set the 1R�$JJUHJDWLRQ�3HUPLWWHG�indicator, the request is taken as incorrect if thenumber of received records is not the same as the number of updated records.

Independently of this indicator, an error arises when the number of selected records is notthe same as the number of records received in the BW.

5HVXOW

The Monitor directs the user to the relevant error case, and enables a direct navigation into the PSA,or the respective error request.

If you want to continue processing the incorrect data records in a program that you have writtenyourself, you can use the method GET_ERRORS of class CL_RSSM_ERROR_HANDLER. The use ofthis method is documented in the RS_ERRORLOG_EXAMPLE.

6HH�DOVR�

Checking and Changing Data Using PSA-APIs [Seite 392]



0RQLWRULQJ

8VH

In monitoring in the Administrator Workbench you have the option of overseeing and controlling thedata loading process as well as other types of data processing in the Business InformationWarehouse.

You can use the following tools and functions to do this:

• InfoPackage Groups [Seite 396]

With the help of InfoPackage groups you can collate data requests that logically belongtogether and schedule them using the scheduler.

• Persistent Staging Area (PSA) [Seite 387]

The PSA represents a BW input storage, where the requested data in saved unchanged to thesource system. You can check the data in the PSA and make changes if necessary.

• Monitor [Seite 378]

With the Monitor you can check the data loading process and data processing in BW andanalyze errors.

• Hierarchy/Attribute Realignment Run [Seite 399]

• Status Overview of ODS Objects [Seite 401]

• Status overview aggregates

You can find information on the status overview of aggregates in the Displaying an Aggregateand its Components [Seite 138]

You can find information on the different VHWWLQJV�in AWB monitoring in the Settings in theAdministrator Workbench [Extern] section.

You can find information on the possibility of displaying the data flow for BW objects in the Data FlowDisplay [Extern].



0RQLWRUData Retrieval

'DWD�7DUJHWV%XVLQHVV�,QIRUPDWLRQ

:DUHKRXVH�6HUYHU

6WDJLQJ�(QJLQH


� � <�9 ��4 9�;� � <�9 ��4 9�; � � <�9 ��4 9�;� � <�9 ��4 9�;


,QIR6RXUFH


Extraction StructureExtraction Structure Extraction StructureExtraction Structure'DWD6RXUFH

'DWD6RXUFH(Copy)




0RQLWRU0RQLWRU6FKHGXOHU

Data Requestfor DataSource

6FKHGXOHUData Request

for DataSource

'HILQLWLRQ

The Monitor is the monitoring tool of the Administrator Workbench.

8VH

Using the Monitor, you can keep an eye on the data request and data processing in the background ofthe Administrator Workbench. In the different levels of the detail display, you are shown the status ofthe data processing.

You can find the most important markers for localizing an error that was not logged by anerror message, under the menu option (QYLURQPHQW in the detail screen of the Monitor.Furthermore, the Wizard [Seite 386] will help you to localize errors.

The Monitor consists of 3 interfaces:

1. The Request Overview [Seite 381]

2. The Detail Screen [Seite 382]

3. The Selection Screen [Seite 380]

You get to the Monitor in the Administrator Workbench using *RWR�→�0RQLWRULQJ�→�0RQLWRU�

If you are in the modeling area of the Administrator Workbench, you get to the Monitor by selecting anode of a tree, and choosing 7RROV�→�0RQLWRU. All data requests for this node are selectedautomatically for the time set in the selection screen of the Monitor, if you do not want to make anyfurther selections.

Calling up the Monitor brings you to the request overview. In the selection screen, you determine howyou want to enter the Monitor. The overview tree is displayed by default.

6HH�DOVR�

Managing InfoCubes [Seite 403]



6HOHFWLRQ�6FUHHQIn the selection screen of the Monitor, you use the relevant radio button to determine how you wantthe request overview displayed.You can also use the various selection options to determine the datarequests that you want to check.

You get to the selection screen of the Monitor using 0RQLWRU�→�1HZ�6HOHFWLRQV. After you have madeyour selections, choose ([HFXWH to go back to the Monitor Request Overview [Seite 381].

7LPH�6HOHFWLRQ

You can choose any time period you like, in which the data request has taken place.

2WKHU�6HOHFWLRQV

You use selections to limit the data requests that you want to check. This gives you the option ofdisplaying, for example, just the data requests from certain source systems or for certain InfoCubes.

To determine selections, choose the relevant pushbuttons in the right-hand side of the screen, selectthe relevant rows, and choose &RQWLQXH.

You save the selections as selection variants, by choosing )XUWKHU�6HOHFWLRQV�→�7UDQVIHU. Enter atechnical name and a normal name. To store the variants as a standard selection, set the relevantindicator. Only a variant can be stored as a standard variant. Existing standard variants thereforebecome normal standard variants when you save a new standard variant.

If you have already saved selections, you can transfer them by choosing )XUWKHU�6HOHFWLRQV�→�&KRRVH

6HOHFWLRQV, or )XUWKHU�6HOHFWLRQV →�0HUJH�6HOHFWLRQV. Existing selections are overwritten when youmake new selections. When you merge selections, the merged variants are added to the existingselections.

You choose the standard selection or add the standard selection to the existing selection, by choosing)XUWKHU�6HOHFWLRQV�→�6WDQGDUG�VHOHFWLRQV. This variant allows you to quickly go to your most importantselection.

Restrict the data requests you have to check by using InfoCubes. You can then go to InfoCubeAdministration [Seite 403], by choosing *RWR�→�,QIR&XEH�FRQWHQW�in the maintenance dialog and viewthe InfoCube content from there.

You can remove the current selection by choosing )XUWKHU�6HOHFWLRQV�→�'HOHWH�DOO�6HOHFWLRQV.



5HTXHVW�2YHUYLHZThe overview of the data requests that are to be analyzed in the Monitor, is displayed by default in atree. Under 1HZ�6HOHFWLRQV, you can set which type of request overview you want displayed in thefuture when you go to the Monitor.

The following request overviews are available to you:

1. You can start your request with the 2YHUYLHZ�7UHH�selection.

Using 0RQLWRU�→�&RQILJXUH�7UHH you can use drag & drop to adjust the tree display to meetyour requirements.

By double-clicking on a leaf of the tree, you get to the Detail Screen [Seite 382] of the Monitorfor the corresponding request. The overview tree remains on top.

2. You can start your request with the 2YHUYLHZ�/LVW�selection. You receive the following information:

InfoPackage Application Component InfoSource

Source System Start day Start time Type of sourcesystem

Type of data End day End time User

Status Requested records Transfer records

You can define this list yourself using 6HWWLQJV�→ 0DLQWDLQ�2XWSXW�/LVW�

Double-clicking on the current data request and data processing brings you to the detailscreen.

3. You can start your request by selecting the 3ODQQLQJ�WDEOH. Choose /HJHQG to get furtherinformation on the Gantt chart (planning board). To get to the detail screen, choose ([HFXWH andclick on a request.



'HWDLO�6FUHHQ

'HWDLO�6FUHHQ��1HZ

You get to the new detail screen when you set the overview tree as the request overview.

The detail screen itself consists of three tabstrips:

• Header

The KHDGHU tabstrip delivers information on the sources and targets of data, rules used,runtime, a user’s name, and a user’s chosen settings.

Most of these information fields support navigation in the maintenance of the current objectusing a double-click, or a dialog box, which delivers additional information.

• Status

The VWDWXV tabstrip delivers information on both the technical and overall status of the request.You can change the overall status manually.

If errors occur with a request, the results of the Monitor Wizard’s analysis are displayed as along text on this tabstrip. You are offered the most effective check or action resulting from thisanalysis as a pushbutton directly under the text field. The Wizard’s step-by-step analysis isalso on this tabstrip.

• Detail

The GHWDLO tabstrip delivers information on the present Monitor detail screen (updated data,updated infos, Scheduler, all IDocs) as well as additional information sorted according to thedataflow in an overview tree.

The overview tree allows you to navigate with the current functions (IDoc or PSAmaintenance, simulated booking,...) using the context menu.

The logs on rebuilding, cancellation, and deletion are also integrated, as are the functions foractivating the ODS object data, and for the further update of the data in the data targets.

Technical information that cannot be displayed in the text of the Monitor detail tree, isdisplayed in the footer row when you select a node.

'HWDLO�6FUHHQ��2OG

You get to the old Monitor detail screen from the overview list or the planning table.

The detail monitor consists of two parts:

• Headers

• Detail display

+HDGHUV

These provide you with general information for this data request. A comparison between the runtimesof the current run and previous runs for the same InfoPackage is also carried out here.

You can receive further general information for this data request via the function +HDGHU�

'HWDLO�GLVSOD\

You can get a detail display over the tabstrips�8SGDWHG�,QIRV��8SGDWHG�'DWD��6FKHGXOHU� and $OO�,'RFV�They provide information on the current processing status of the data request.

When you request data, the request is first logged on the 6FKHGXOHU tabstrip. A request IDoc(RSRQST) is then sent to the ALE inbox of the source system.

You can find this IDoc again in the tabstrip $OO�,'RFV. All IDocs displayed here are provided with astatus number that characterizes the processing status of this IDoc from the ALE view. The IDocs ofthe BW ALE outbox and inbox are listed for the request as default values. You can, however, also listthe IDocs of the ALE outbox and inbox for the source system.



If the source system contains the request IDoc, it compiles the requested data and reports on itsactivities using Info IDocs, which are updated in BW and can then be seen in the tabstrip 8SGDWHG,QIRV. These Info IDocs have different status numbers that characterize the information sent. Amongother things, the Info IDocs contain information on data that is summarized into data packets with thehelp of the extractor in the source system.

The data compiled by the extractor in the source system is summarized into one or more data packets,and is dispatched to BW. You can find these data packets again, so long as the update has beenstarted in BW, in the tabstrip 8SGDWHG�'DWD.

The information for a data packet is arranged hierarchically and gets more detailed to the right, withevery click you make on the black arrow. On the first detail level, you can find the processing stepsthat are broken down into further individual log times. These log times are characterized using ‘callers’,and carry either a success message or an error message.

Each tabstrip offers you different options to execute additional actions with the displayed lines ofinformation: For this, choose one or more lines and click on one of the pushbuttons on the tabstrip.

With the pushbutton 0DLQWDLQ�'DWD� you can jump to�the IDoc maintenance for each IDoc, and displaythe technical structure of the IDoc. If there are IDocs on the $OO�,'RFV tabstrip that are flagged with ared traffic light [Seite 385], then you can process them manually with the 3URFHVV�,'RF�pushbutton.You can also simulate the update of data IDocs with the function 6LPXODWHG�SURFHVV.

Furthermore, you can display the corresponding messages with the pushbutton 0HVVDJHV.

Special feature Persistent Staging Area [Seite 387]

If you have chosen the requested InfoSource as a 36$�transfer method�in the transferrules, the data packets are not dispatched using IDocs, and therefore do not appear onthe $OO�,'RFV�tabstrip.

(UURU�/RJ

When you load master data, an error log of all the incorrect data records is created. You can call upthis log from the Monitor detail screen or the Monitor Wizard. The system checks master data forduplicated data records and overlapping time intervals, and to see whether lower-case letters havebeen used.

6WDWXV�1XPEHUV

Various numbers are used for logging and commentating on the data loading process.

1. Callers

Every monitor log time is assigned to a caller. This consists of a number that indicates whichprocessing status is being logged.

You can find out what the numbers signify with F4 Help.

2. Info Status

These statuses are there to characterize the information passed on toBW from the source system. They are logged on the tabstrip $OO�,'RFV.

You can find out what the numbers signify with F4 Help.

3. Warehouse IDoc Status

These statuses are valid for all IDocs that have been generated usingALE. They are logged on the tabstrip $OO�,'RFV.

You can find out what the numbers signify by choosing 7RROV�→�$%$3

:RUNEHQFK�→�2YHUYLHZ�→�'DWD�EURZVHU in BW. Enter the table name7('6� then choose 7DEOH�FRQWHQW and ([HFXWH.



7UDIILF�/LJKWVThe status of a data request is assessed in the Monitor by traffic lights at different levels of detail.

Red or yellow traffic lights indicate:

• /RZHVW�OHYHO�RI�GHWDLO (processing step):

Error message exists

• 0LGGOH�OHYHO�RI�GHWDLO�(data packet):

Processing not complete (first yellow, red after timeout)

• +LJKHU�OHYHO�RI�GHWDLO�(tabstrip):

− Updated Info and Updated data:

Number of data packets or data records reported does not match the actual number

− 6FKHGXOHU:

Data request has not been correctly transmitted

− $OO�,'RFV:

Some IDocs have not yet been successfully updated

• 2YHUDOO�YLHZ��UHTXHVW�VWDWXV��

Yellow: No data exists in the source system or update is not yet completed

Red: Error according to the level of detail.

This assessment means that an error is not visible on all levels of detail.

In general, you find out the meaning of a traffic light using the quick info for the traffic light.

In the selection screen and the detail screen of the Monitor, you can determine the time from which adata request should be considered invalid. The traffic light remains yellow for as long as a datarequest has not been completed. The traffic light is set to red if the time of the latest IDoc to have beenentered for this request is longer than the maximum set waiting time. To define the maximum waitingtime, select 6HWWLQJV�→�:DLWLQJ�7LPH�XQWLO�6WDWXV�LV�,QYDOLG�

Using 6HWWLQJV�→�7UDIILF�/LJKW�&RORU�IRU�8QVXFFHVVIXO�6HOHFWLRQ�you can determine the way in whichan unsuccessful data request is evaluated.

In the detail screen you can change the entire status of a data request by choosing 40�$FWLRQ.



:L]DUGThe Wizard provides you with support when you are analyzing an incorrect data request. You activatethe Wizard with the question mark in the standard toolbar of the Monitor detail screen.

The processing steps are displayed with status symbols in the dialog box for the Wizard. You can callup the meaning of the status icons by positioning the cursor on a processing step and choosing +HOS�

If you choose $QDO\]H, you get to a dialog window which gives you further information on the errorsituation. Here you can call up 'HWDLOV and, using the left pushbutton, branch to additional analysissteps as far as the latest error message and, if necessary, to the corresponding maintenance andoverview dialogs.

If there is a short dump in BW, you branch to the short dump overview for BW.

If the master data is blocked, you arrive in the master data maintenance in BW.

You can also schedule the Wizard in the background for the analysis of data requests. If you schedulethe Wizard periodically, all of the requests that have not yet been assessed are analyzed regularly. Inthe event of an error, it automatically notifies one or more of the people responsible by e-mail. You canjump from the e-mail directly to the detail screen of the monitor in order to execute an error analysis inthe dialog using the Wizard.

You carry out the scheduling for the Monitor Wizard and the maintenance of message recipients in %:&XVWRPL]LQJ�,PSOHPHQWDWLRQ�*XLGH�under %XVLQHVV�,QIRUPDWLRQ�:DUHKRXVH�Å�$XWRPDWHG�3URFHVVHVÅ�0RQLWRU�6HWWLQJV� You can also define message recipients in the monitor initial screen or detailscreen using 6HWWLQJV�Å�0DLQWDLQ�(UURU�1RWLILFDWLRQ�

You can determine whether the Wizard is started automatically every time the monitor detail screen iscalled up by using 6HWWLQJV�Å�$VVLVWDQW�'HIDXOW�6HWWLQJ�



3HUVLVWHQW�6WDJLQJ�$UHD

3XUSRVH

The Persistent Staging Area (PSA) is the input store for requested transaction data, master dataattributes, and texts from various source systems within the Business Information Warehouse. Therequested data is stored, unchanged, to the source system.

Request data is stored in the transfer structure format in transparent, relational database tables in theBusiness Information Warehouse. The data format remains unchanged, meaning that nosummarization or transformations take place, as is the case with InfoCubes.

When loading flat files, the data does not remain completely unchanged, since they areadjusted by conversion routines if necessary (for example, the date format 31.21.1999 isconverted to 19991231 in order to ensure uniformity of data).

You determine the transfer method 36$ in the transfer rules maintenance [Seite 285].

If you set the PSA when you are extracting data, you get improved performance if you use TRFCs forloading the data. The temporary storage facility in the PSA also allows you to check and change thedata before the update into data targets. In contrast to a data request with IDocs, a data request in thePSA also gives you various options for a further update [Seite 389] of the data in the data targets. Thepossible coupling of the loading process from the further processing in BW likewise contributes to animproved loading performance. The operative system is not debited if data errors first appear withfurther processing.

The PSA delivers the backup status for the ODS (until the total staging process is confirmed). Theduration of the data storage in the PSA is medium-term, since the data can still be used forreconstruction. However data storage when updating ODS objects is short-term.

A PSA is displayed for every InfoSource, in the PSA tree of the Administrator Workbench. You get tothe PSA tree in the Administrator Workbench using either 0RGHOLQJ or 0RQLWRULQJ. The requested datarecords appear, divided according to request, under the source system they belong to for anInfoSource in the PSA tree.

)XQFWLRQV

The data records in BW are transferred to the transfer structure when you load data with the transfermethod PSA. One TRFC is carried out per data packet. Data is written to the PSA table from thetransfer structure, and stored there. A transparent PSA table is created for every transfer structure thatis activated. The PSA tables each have the same structure as their respective transfer structures.They are also flagged with key fields for the request ID, the data packet number, and the data recordnumber.

Since the requested data is stored unchanged in the PSA, it can have errors if it already had errors inthe source system. If the requested data records have been written into the PSA table, you can checkthe data for the request and change incorrect data records [Seite 391].

Depending on the type of update, data is transferred from the PSA table into the communicationstructure using the transfer rules. From the communication structure, the data is finally updated in thecorresponding data target.

Using partitioning, you can separate the dataset of a PSA table into several smaller, physicallyindependent, and redundancy-free units. This separation can mean improved performance when youupdate data from the PSA. In the BW Customizing Implementation Guide, you determine from whichnumber of data records a partition is created, under %XVLQHVV�,QIRUPDWLRQ�:DUHKRXVH�→�&RQQHFWLRQV

WR�2WKHU�6\VWHPV�→�0DLQWDLQ�&RQWURO�3DUDPHWHUV�IRU�'DWD�7UDQVIHU� Only data records from acomplete request are stored in a partition. The specified value is a threshold value.

5HVWULFWLRQV

The number of fields is limited to a maximum of 255 when using TRFCs to transfer data. The length ofthe data record is limited to 1962 bytes when you use TRFCs.



Data transfer with IDocs cannot be used in connection with the PSA.



7\SHV�RI�'DWD�8SGDWH�ZLWK�36$

3UHUHTXLVLWHV

You have determined the transfer method 36$ in the transfer rules maintenance.

)XQFWLRQV

In contrast to a data request with IDocs, a data request in the PSA also gives you various options for afurther update of the data in the data targets. Upon selection, the balance between data security andperformance for the loading process is weighed.

If you create an InfoPackage in the BW Scheduler, determine the type of data update on the3URFHVVLQJ�tab page.

36$�DQG�'DWD�7DUJHWV��,QIR2EMHFWV�3DUDOOHO

This is a method to update data into the PSA and the data targets [Seite 92] with a high level ofperformance. BW receives the data from the source system, writes it to the PSA, and starts the updateimmediately, in parallel, in the corresponding data target.

For every data packet, a process is started to write the data from this data packet into the PSA. If thedata is successfully updated in the PSA, a second parallel process is started. In this process, thetransfer rules are used for the package data records, data is adopted by the communication structureand finally written to the data targets.

The maximum number of processes, which is set in the source system in customizing forextractors, does not affect the number of processes in BW in a restrictive way. Therefore,many dialog processes in BW could be necessary for the loading process. Make sure thatenough dialog processes are available in the BW system.

If the data packet contains incorrect data records, you have several options allowing youto continue working with the records in the request. You can specify how the systemshould react to incorrect data records You can find additional information about this in thesection Treating Data Records with Errors [Seite 375].

You also have the option of correcting the data in the PSA [Seite 391] and updating it fromthere.

36$�DQG�WKHQ�LQWR�'DWD�7DUJHW��,QIR2EMHFW

With a serial update of data in the PSA, and in the data targets, a process is still started per datapackage that writes the data package to the PSA. When the data has been successfully updated tothe PSA, the same process writes the data to the data targets afterwards.

Compared with a parallel data transfer, you have better control over the whole data flow with a serialupdate of data, because the BW carries it out using only one process per data packet. A maximum ofonly so many dialog processes are necessary for each data request in the BW system. Thiscorresponds to the settings you made in the customizing for the extractors in the maintenance of thecontrol parameters.

If the data packet contains incorrect data records, you have several options allowing youto continue working with the records in the request. You can find additional informationabout this in the section Treating Data Records with Errors [Seite 375].

You have the option of correcting the data in the PSA [Seite 391] and updating it fromthere.



2QO\�36$

Using this method, data is written to the PSA, and not updated any further.

You have the advantage of having data stored safely in BW and having the PSA suitable as apersistent incoming data store for mass data as well. The respective setting for the maximum numberof processes in the source system can also have a positive impact on the number of processes in BW.

)XUWKHU�8SGDWLQJ�IURP�WKH�36$

Several options are available to update the data from the PSA into the data targets.

• To immediately update the request data in the background, select the request in the PSA tree, andchoose &RQWH[W�PHQX��ULJKW�PRXVH�EXWWRQ��→�6WDUW�XSGDWH�LPPHGLDWHO\.

• To schedule a request update using the Scheduler, select the request in the PSA tree, and choose&RQWH[W�PHQX��ULJKW�PRXVH�EXWWRQ��→�6FKHGXOH�XSGDWH.

You get to the 6FKHGXOHU��36$�VXEVHTXHQW�XSGDWH�. Here you can determine the schedulingoptions for the background run. For transaction data, you can determine additional updateparameters, and choose in which InfoCubes or ODS Objects the data is updated.

• To further update the data automatically in the corresponding data target, wait until all the datapackets have arrived and been successfully updated in the PSA, select 8SGDWH�LQ�GDWD�WDUJHW fromthe 3URFHVVLQJ tab page when you schedule the InfoPackage in the Scheduler.

• To simulate the data update for a request using the Monitor, select the request in the PSA tree,and choose &RQWH[W�PHQX��ULJKW�PRXVH�EXWWRQ��→�6LPXODWH�&DQFHO�XSGDWH�

The Monitor detail screen appears. From the 'HWDLO�tab page, select one or more datapackets, and choose 6LPXODWH�XSGDWH. In the following screen, determine the simulationselections, and select ([HFXWH�VLPXODWLRQ. Enter the data records, for which you want tosimulate the update, and choose &RQWLQXH. You see the data in the communication structureformat. In the case of transaction data, you can change to the view for InfoCube data records.

3URFHVVLQJ�6HYHUDO�36$�5HTXHVWV�DW�2QFH

To process several PSA requests at once, select the PSA in the PSA tree, and choose &RQWH[W�0HQX

�ULJKW�PRXVH�EXWWRQ��→�3URFHVV�6HYHUDO�5HTXHVWV. You have the option of starting the update for theselected requests immediately, or of using the Scheduler to schedule them. The individual requestsare scheduled one after the other in the Scheduler. You can delete the selected requests collectivelyusing this function. You can also call detail information, the Monitor, or display the contents for thecorresponding data target.

During processing, a background run is started for every request. Make sure that enoughbackground runs are available.

2QO\�'DWD�7DUJHW��,QIR2EMHFW

We recommend this method exclusively for loading from flat files or from data sources that are alwaysavailable. This is because the data is not always saved persistently into an incoming data store. Thissaves hard disk space, although it leads to a loss of the following: data security, an option to rebuildprocesses, and simulation options.

6HH�DOVR�

Tabstrip: Processing [Seite 363]



&KHFNLQJ�DQG�&KDQJLQJ�'DWD

8VH

The PSA offers you the option of checking and changing data before you update it further from thePSA table in the communication structure and in the current data target.

You can check and change data records to

• Remove update errors.

If lower case letters or characters that are not permitted have been used in fields, you canremove this error in the PSA.

• Validate data.

For example, if, when matching data, it was discovered that a customer should have beengiven free delivery for particular products, but the delivery had in fact been billed, then youcan change the data record accordingly in the PSA.

3UHUHTXLVLWHV

You have determined the 36$ transfer method in the maintenance of the transfer rules for anInfoSource, and have already loaded data into the PSA.

3URFHGXUH

You have two options for checking and changing the data:

1. You can edit the data directly.

a. Select the request for which you want to check and change the data in the PSA tree of theAdministrator Workbench and select &RQWH[W�PHQX��ULJKW�PRXVH�EXWWRQ��→�(GLW�'DWD.

You get to a dialog box where you can choose which data packet and which data records forthis packet you want to edit.

b. When you have made your selections choose &RQWLQXH.

You get to the request data maintenance screen.

c. Select the records you want to edit, select &KDQJH� and enter the correct data. Save theedited data records.

2. Since the data is stored in a transparent database table in the dictionary, you can change the datausing ABAP programming with PSA-APIs [Seite 392]. Use the programming for a PSA-API withcomplex data checks or changes to the data that occur regularly.

5HVXOW

The corrected data is now available for continued updates. You can find information on update optionsfrom the PSA in the section Types of Data Update in the PSA [Seite 389] under 8SGDWLQJ�IURP�WKH36$.



&KHFNLQJ�DQG�&KDQJLQJ�'DWD�8VLQJ�36$�$3,V

8VH

To perform complex checks on data records, or to carry out particular changes to data recordsregularly, you can program for a PSA table with the help of the delivered function modules called PSA-APIs.

If you want to execute data validation with program support, select 7RROV�→�$%$3�:RUNEHQFK�→'HYHORSPHQW�→�$%$3�(GLWRU and create a program [Extern].

If you use transfer routines [Seite 285] or update routines [Seite 221] it may be necessary tosubsequently read data in the PSA table.

Employee bonuses are loaded into an InfoCube and sales figures for employees areloaded into a PSA table. If an employee’s bonus is to be calculated in the update routineand depending on his/her sales, the sales must be read from the PSA table.

3URFHGXUH

1. Call up the function module 5660B$3,B5(48(67B*(7�to get a list of requests with request IDfor a particular InfoSource of a particular type. You have the option of restricting request outputusing a time restriction and/or the transfer method.

You must know the request ID, as the request ID is the key that makes managing data recordsin the PSA possible.

2. With the request information received so far, and with the help of the function module, you can

− read RSAR_ODS_API_GET data records from the PSA table

− write RSAR_ODS_API_PUT changed data records in the PSA table.

56$5B2'6B$3,B*(7

You can call up the function module RSAR_ODS_API_GET with the list of request IDs given by thefunction module RSSM_API_REQUEST_GET. The function module RSAR_ODS_API_GET no longerrecognizes InfoSources on the interface, rather it recognizes the request IDs instead. With theparameter I_T_SELECTIONS, you can restrict reading data records in the PSA table with reference tothe fields of the transfer structure. In your program, the selections are filled and transferred to theparameter I_T_SELECTIONS.

The import parameter causes the function module to output the data records in the parameterE_T_DATA. Data output is unstructured, since the function module RSAR_ODS_API_GET worksgenerically, and therefore does not recognize the specific structure of the PSA. You can findinformation on the field in the PSA table using the parameter E_T_RSFIELDTXT.

56$5B2'6B$3,B387

After merging or checking and subsequently changing the data, you can write the altered data recordsinto the PSA table with the function module RSAR_ODS_API_PUT. To be able to write request datainto the table with the help of this function module, you have to enter the corresponding request ID.The parameter E_T_DATA contains the changed data records.

5HVXOW

The corrected data is now available for continued updates. You can find information on update optionsfrom the PSA in the section Types of Data Update in the PSA [Seite 389] under 8SGDWLQJ�IURP�WKH36$.



9HUVLRQLQJ

8VH

PSA tables are provided with a version if you make an incompatible change to the transfer structure(for example, length changes or the deletion of fields).

)HDWXUHV

When an incompatible change to the transfer structure has been established, a new version of thePSA, meaning a new PSA table, is created. Data is written to the new table when the next request isupdated.

The original table remains unchanged and is given a version. For every request that was written in theold table, you can also continue to use all of the PSA tree functions.

The appropriate format is used for reading data from a PSA table.

• If the request has been written to the PSA table before the change to the transfer structure, thenthe format of the transfer structure before the change is used.

• If the request has been written to the PSA table after the change to the transfer structure, then theformat of the changed transfer structure is used.

If you program against the function module RSAR_ODS_API_GET, you can determinethat the data be read from an old version into the structure of the current version using theparameter I_CURRENT_DATAFORMAT.



'HOHWLQJ�5HTXHVWV�IURP�WKH�36$

8VH

With this function you delete requests from the PSA. This reduces the volume of data in the PSA. It isa good idea to delete incorrect requests or deltas for a data target, to which you do not want to loadany more delta.

)XQFWLRQV

For a particular DataSource, you can specify day X or a date, to delete the requests, which wereloaded before this time. You can display a list of all the requests in the chosen PSA table to checkthis.

Since the change log is also stored as a PSA table, you can also use this function to delete change logrecords. You can find additional information under Deleting from the Change Log [Seite 174].

$FWLYLWLHV

1. Choose the PSA tree in the Administrator Workbench under 0RGHOLQJ�

2. In the source system context menu for your InfoSource or in your application component, choose'HOHWH�36$�'DWD�

3. In the screen that follows, choose the DataSource, from which you want to delete requests. Tohelp you do this, you can display a list of the requests.

4. Specify the number of days or a date, that you want to use as a cutoff point. All requests beforethis are deleted. You also have the option to specify whether you only want to delete successfullyupdated requests, or only incorrect requests, that are no longer updated in a data target (this isonly valid for transaction data).

5. Schedule the delete job.



,QIR3DFNDJH�*URXS

'HILQLWLRQ

An InfoPackage group is a collection of InfoPackages.

8VH

In order to summarize data requests which logically belong together from a business point of view, andto therefore simplify the request, you can collect data requests (meaning the InfoPackages) into anInfoPackage Group. You can schedule each of these groups in the Scheduler [Seite 350] . With thedata request, the Scheduler can access InfoPackage groups directly and thereby request more thanone InfoPackage at a time.

You can edit InfoPackage groups in the InfoSource tree of the Administrator Workbench modeling.You can find further information on this in the section Maintaining InfoPackage Groups [Seite 397].You can also get to the InfoPackage group tree in the Administrator Workbench monitoring.

In BW 3.0, automatic process control has been enhanced and improved significantly withthe concept of process chains. Controlling the loading process by using InfoPackagegroups is no longer enhanced, but continues to be supported. :H�UHFRPPHQG�WKDW�\RXRQO\�XVH�SURFHVV�FKDLQV�IRU�QHZO\�GHILQHG�EXQGOHV�RI�GDWD�UHTXHVWV�WKDW�EHORQJWRJHWKHU�



0DLQWDLQLQJ�,QIR3DFNDJH�*URXSV

3URFHGXUH

1. Go to the InfoSource tree in modeling of the Administrator Workbench and choose in the standardtoolbar of the right area of the screen 6KRZ�,QIR3DFNDJH�*URXS.

On the right-hand side of the screen, you will see the InfoPackage group tree.

2. Highlight a node of the InfoPackage group tree and create a new InfoPackage group using thecontext menu (right mouse click). This is always inserted underneath the highlighted node.

3. Select an InfoPackage (in the InfoSource tree in the middle area of the screen) that you want totransfer to the InfoPackage group and move it into the InfoPackage group you want by using drag& drop.

You can assign as many InfoPackages as you like to an InfoPackage group.

InfoPackages with the same selection conditions, same assignment for combination ofInfoSource / DataSource / source system and same data type (transaction data or masterdata) cannot be assigned to the same InfoPackage group.

Alternatively to the above procedure, you can also create an InfoPackage group in the monitoring viewof the Administrator Workbench. However, in this view it is not possible to insert InfoPackages into theInfoPackage Group.

5HVXOW

You have created an InfoPackage group and have inserted InfoPackages into the InfoPackage group.You can now schedule an InfoPackage group [Seite 398].



6FKHGXOLQJ�DQ�,QIR3DFNDJH�*URXS

3URFHGXUH

1. Choose 6KRZ�,QIR3DFNDJH�*URXSV in the InfoSource tree of the Administrator Workbench –Modeling, or choose the ,QIR3DFNDJHV view in 0RQLWRULQJ of the AWB.

2. Select an InfoPackage group from the InfoPackage group tree and choose 6FKHGXOH.

3. On the tabstrip�,QIR3DFNDJHV��number the InfoPackages that are assigned to the group accordingto the sequence in which the loading process is to be carried out.

4. For the InfoPackages, select whether you want the Monitor to run a check during the data updateto see if the first request from the list has been completely and correctly processed. Only then willthe request for which this indicator has been set be processed.

5. Define a fixed delay of one minute for the individual InfoPackages. The delay represents the waittime until the next request is carried out.

6. Schedule the InfoPackage group.

5HVXOW

The selected data from the bundled InfoPackages is loaded with respect to your settings in theInfoPackage group.



$GMXVWLQJ�&KDQJHV�WR�+LHUDUFKLHV�DQG�$WWULEXWHV

8VDJH

If hierarchies and attributes for characteristics have changed, then it is necessary to make structuralchanges to the aggregates in order to adjust the data accordingly.

With a structural change, DOO of the aggregates that are affected by the changes to thehierarchies and InfoObjects of DOO InfoCubes are adjusted. Under certain circumstances,this can take a very long time.

If an aggregate is only affected by a few changes, then it is adjusted, otherwise it is reconstructed.When you carry out the adjustments, the obsolete data records are read negatively whereas the newdata records are read positively.

Beyond a certain scale of adjustment, modifying the aggregate becomes more time-consuming thanreconstructing it. Because this threshold value depends on your system installations, you change thevalue yourself. To do this, choose %XVLQHVV�,QIRUPDWLRQ�:DUHKRXVH�Å�*HQHUDO�%:�6HWWLQJV�Å0DLQWDLQ�$JJUHJDWH�5HDOLJQPHQW�5XQ and make the settings you want there.

3URFHGXUH

0DQXDOO\�

1. Select $GPLQLVWUDWRU�:RUNEHQFK�Å�7RROV�Å+LHUDUFK\�$WWULEXWH�&KDQJHV�from the menu.

All the executed realignment runs are listed with detailed information in the following dialogbox.

All InfoObjects and hierarchies that are planned for structural change are selected by default.

2. If you only want to carry out the structural changes for individual InfoObjects and hierarchies,select the pushbutton ,QIR2EMHFW�/LVW and/or +LHUDUFK\�/LVW� and remove from the list thoseInfoObjects and hierarchies for which the changes should not be made.

3. You can now schedule a new structural change by entering the date and time, or you can chooseto execute immediately.

4. The status of the structural change is displayed in the upper section of the dialog box.

$XWRPDWLFDOO\�

You can also schedule the same function when directly carrying out a report [Extern], by specifying theprogram name RSDDS_AGGREGATES_MAINTAIN.

You can also create the program regularly as a background job as well as in a chain of events [Seite450].

The attributes for the characteristic 0MATERIAL are uploaded weekly. You can nowschedule the program so that it starts after loading. You can also use the InfoObject List0MATERIAL as a variant, so that only the changes to the material attributes are taken intoaccount and not others, which will be needed later.

You can use the pushbutton /RJ to display the messages for the changes you made manually as wellas automatically.

5HVXOW

The aggregates for BW contain the changed hierarchies and / or attributes.



The adjustment run can take quite some time. Reporting on the ‘old’ hierarchies /attributes is possible during the run.

6HH�DOVR�

Aggregates [Seite 126]



6WDWXV�2YHUYLHZ�RI�2'6�2EMHFWV

8VH

The status overview displays the loading, activation and update status of all the ODS Objects. You canget to the ODS Object display or administration screen directly from this overview.

)XQFWLRQV

The /RDGLQJ�6WDWXV column shows whether the data was loaded successfully in the ODS Object or iferrors occurred. If there are errors shown in the loading status (red traffic light), you can branchstraight to the function 0DQDJH�2'6�2EMHFW.

The $FWLYDWLRQ�6WDWXV column shows whether all data has been activated yet or not. If not, you canactivate it by choosing the pushbutton.

The column 8SGDWH�6WDWXV shows whether all the ODS Object data has updated in the data target yetor not. If not, you can update the data in the data target by choosing the pushbutton.

Moreover, it is possible to jump to the ODS Object display or maintenance screen from here. To dothis, select one or more ODS Objects and choose 'LVSOD\�(or double-click on the name) or 0DQDJH.

$FWLYLWLHV

Choose 0RQLWRULQJ → 6WDWXV�2YHUYLHZ�in the Administrator Workbench.



0DQDJLQJ�'DWD�7DUJHWV

8VH

You can display technical information about the contents of the data target with the 0DQDJH function inthe context menu of the data target in the InfoProvider tree. This gives you information on the requeststhat are already in the data target and allows you to reconstruct data targets.

3UHUHTXLVLWHV

The data target is saved and active and you already loaded data into your data target.

)XQFWLRQV

You can use the 0DQDJH function for:


• ODS objects [Seite 417]

• InfoObjects [Seite 422]



0DQDJLQJ�,QIR&XEHV

8VH

You can display technical information on the content of the InfoCube using the function 0DQDJH,QIR&XEH. You can carry out administrative tasks, such as constructing aggregates and deletion for anindividual InfoCube. You can influence the load and query performance by using the InfoCube contentmaintenance.

3UHUHTXLVLWHV

An active InfoCube is available.

)XQFWLRQV

The InfoCube is displayed in the top table. You only have to make one selection from severalInfoCubes if you got to the InfoCube management screen from the Scheduler or Monitor.

After you have selected an InfoCube from the table in the upper half of the screen, you can display theInfoCube contents by choosing &RQWHQWV in the toolbar. If you have not selected an InfoCube, you candisplay any number of dictionary tables relevant to InfoCube administration. Enter the table name inthe subsequent dialog box. &KDQJH�8SGDWH�5XOHV brings you to the maintenance screen for theupdate rules. 'HOHWH�&RQWHQWV removes the contents of the InfoCube. There is also the option ofdisplaying an application log and a process overview.

&RQWHQW�RI�WKH�,QIR&XEH

You can display the dimensions of an InfoCube with the InfoObjects that belong to them.

Using &XEH or )DFW�7DEOH��you can display the contents of the InfoCube and of the fact table, and alsodelete them if necessary.

3HUIRUPDQFH

Here you can find the options that allow you to affect not only the load performance but also the queryperformance. For information about this, read InfoCube Performance [Seite 410].

5HTXHVWV�LQ�WKH�,QIR&XEH

You get information on all requests that have run in the InfoCube and you can, where necessary,delete requests once again. For information about this, read Requests in the InfoCube [Seite 413].

5ROOLQJ�XS�WKH�,QIR&XEH

You can start rolling up the requests for aggregate construction immediately or in the background. Youcan display aggregates that already exist for the InfoCube and the logs that belong to them.

If activated aggregates exist for the InfoCube and you are loading new requests into the InfoCube, youalso have to roll up these in the aggregates. Only then are these new requests taken into accountwhen executing a query.

$XWRPDWLF�)XUWKHU�3URFHVVLQJ

You can make the following automatic settings for the further processing of InfoCubes:

• Set the quality status to OK

• Automatic roll-up

• Automatic compression

See Automatic Subsequent Processing [Seite 415].

5HFRQVWUXFWLQJ�WKH�,QIR&XEH

You can reconstruct an InfoCube from the requests that are already uploaded. You can use theserequests for reconstructing the current InfoCube or for constructing another InfoCube.



6HH�DOVR�

Scheduler [Seite 350]

Monitor [Seite 378]



,QIR&XEH�&RQWHQW

8VH

With this function you verify whether the data that you loaded in the InfoCube is freeof errors. You have the option of reporting on recently loaded requests.

With a few restrictions, you can execute queries on the InfoCube, by selectingnavigation attributes, characteristics and key figures of the InfoCube, which you wantto appear in the display. You can also specify characteristics and navigationattributes if necessary.

,QWHJUDWLRQ

The InfoCube content maintenance is divided up into 3 areas:

1. Restrictions for the characteristics and navigation attributes

2. Selecting the field of the characteristics and key figures for the output list

3. Additional options

If the InfoCube is too large, you must make a preselection of the characteristics,navigation attributes and key figures. You can only choose the selected objects, orspecify them for these restrictions.

)XQFWLRQV

Using the ,QIR&XEH�&RQWHQWV pushbutton you can display the contents of theInfoCube on the &RQWHQWV tabstrip.

)LHOG�VHOHFWLRQ�IRU�RXWSXW

You can use all characteristics, navigation attributes and key figures for the selection.You determine the characteristics and key figures that are to be displayed in theoutput list. Aggregation is carried out using the characteristics that you do not want inthe list.

'R�QRW�XVH�FRQYHUVLRQ

With this function you can check how the data is stored on the database. The data isdisplayed in the format which they take on the database.

The date is displayed on the database in the format 19991230 while it is displayed as12.30.1999 in BW (this depends on the settings made in the user master record).

A currency key figure has 2 decimal places on the database. Since some currencies havea different number of decimal points, the values are saved accordingly on the database.1000 lira would, for example, be saved as 10.00 lira, abut 1000 USD would be 1000.00USD.

The conversion is switched off by default.

8VH�0DWHULDOL]HG�$JJUHJDWHV

You determine whether defined aggregates are to be used for the InfoCube whenstaging the list output. If you choose 8VH�0DWHULDOL]HG�$JJUHJDWHV, the request is notexecuted directly on the fact table, but aggregate tables that you created are usedinstead and the performance is improved. You can also use this option to check theconsistency between the fact table and the aggregation table.



Deactivate this option if you want to check the data in the fact table.

8VLQJ�'DWDEDVH�$JJUHJDWLRQ

With this option you specify if you want all the records that agree in your key to begrouped together, or whether each record should be written separately.

Deactivate this option if you want to check individual records and the exact content ofthe database.

0D[LPXP�1XPEHU�RI�+LWV

With the 0D[LPXP�QXPEHU�RI�KLWV, you determine what maximum quantity of data isreturned. This is important if you have very large InfoCubes and want to avoid, forexample, millions of records being returned.

2XWSXWWLQJ�WKH�1XPEHU�RI�+LWV

If you have activated the option DB aggregation, several records are taken from thedatabase and brought together in one row of the list. If you choose the option µ2XWSXWQXPEHU�RI�KLWV¶ then an additional key figure is generated in the output list that showsfrom how many records the respective record has been taken, i.e. how many datarecords it took to produce the output record.

You can also use this option to determine how many records are in a particularselection condition in the InfoCube. Enter a selection condition, but do not select anycharacteristics or key figures. In the return list you then only get the column 5RZ&RXQW�with the number of hits and the number of entries that match this selectioncondition.

'LVSOD\LQJ�0RGLILHG�6WUXFWXUHV

When uploading master data these are initially stored in the modified version. Onlyafter activating the master data are these older entries replaced and the new onescan be used in the BEx Analyzer for Reporting. If you choose 0RGLILHG�VWUXFWXUHV,you can already check at this point how the data would look in Reporting onceactivated.

Using .H\�GDWH�IRU�WLPH�GHSHQGHQW�FKDUDFWHULVWLFV, you determine at which time youwant to read time-dependent master data. The current date is entered as default.

The attribute values for a characteristic are valid from 01.01.2000 until 06.01.2000, afterwhich time the attributes have new values. If you choose the key date between01.01.2000 and 06.01.2000, you get a different result in the list output than if you choosea later date.

'LVSOD\LQJ�WKH�64/�4XHU\

In support of the debugging function, you can display the SQL query, which isgenerated according to the field selection and restrictions, and sent to the database.The SQL query is displayed in an Editor.

'LVSOD\LQJ�5XQ�6FKHGXOH

For each query the database optimizer can decide on how it collects data. Tounderstand exactly what the database optimizer does, you can display the runschedule.



You can, for example, determine whether the database uses indices for procuring datawith a particular selection, or whether it reads the entire table.



7UDQVIHUULQJ�,QIR&XEH�&RQWHQWV

8VH

You can display the data in a list on the screen (select: return as list), or you can usethe option of transferring the data (characteristics, attributes, and key figures) toanother medium.

3URFHGXUH

1. Choose the data target:

• Store in a new DB table

If you choose this function, a new database table is generated in which the data is stored.The table format corresponds to the format, in which the data is displayed in the outputlist. There must not be any tables or structures with this name in either the ABAPdictionary or on the database. The new table has to be checked using the ABAPdictionary.

You can only store BasicCubes and aggregate tables as database tables

• Insert into an existing DB table

When you choose this function, the data is written into a database table that alreadyexists. The format of the table must correspond to the format of the selected data. As arule, you choose this function after you have created, and initially filled, a database tablefor this specific selection. You add current data to the data that is already stored in theexisting table.

• Store in file (workstation)

When you choose this function, a file, in which the data is stored, is generated on yourlocal PC. You have the option of opening the file with, for example, Microsoft Excel, Word,or Wordpad.

• Store in file (application server)

When you choose this function, a new file, in which the data is stored, is generated on theapplication server. This option is particularly useful with large quantities of data, since thistransfer method can also be run in the background. To run the transfer in the background,choose the pushbutton ([HFXWH�LQ�%DWFK.

2. Enter a name for the database table, or for the file, and choose ([HFXWH.

• If you have chosen a database table, this is created in the system, and the data is transferred.

• If you have chosen a file, use F4 Help in the selection screen to choose the path to where youwant to save the file. Specify the data format, and choose 7UDQVIHU.



6HOHFWLYH�'HOHWLRQ

8VH

Besides deleting entire requests, you also have the option of deleting data according to business-orientated aspects from the fact table. For example, you can delete the data for a cost center or of acustomer even if these are spread over several requests.

,QWHJUDWLRQ

If you delete data selectively from an InfoCube, the aggregate belonging to this InfoCube isautomatically deleted.

)XQFWLRQV

You receive a list of all InfoCube characteristics and can determine restrictions on thesecharacteristics. Fact table records that correspond to these restrictions are deleted.

Before you delete data from the InfoCube there are a series of options open to you:

5HFRQVWUXFWLQJ�$JJUHJDWHV

If you choose this option then all aggregates that existed before the selective deletion for the InfoCubeare reconstructed and activated.

'DWDEDVH�GHSHQGHQW�2SWLRQV

'HJUHH�RI�SDUDOOHOLVP�IRU�UHFRQVWUXFWLRQ��25$&/(�

When deleting, there are various strategies that are chosen automatically according to the specificrestrictions. Either (when few data records are to be deleted) the records are deleted directly by thedatabase, or (for many data records) a new database table is created with the remaining records.

You can enter here how many parallel processes are to be used in case 2 for reconstructing the table.

3DUDOOHOLVP�ZKHQ�5HFRQVWUXFWLQJ��,%0�

If you choose this function then parallel processes are used for reconstructing tables. The databasedecides how many processes are used.

6ZLWFK�RII�/RJJLQJ�ZKHQ�5HFRQVWUXFWLQJ��25$&/(�

If you carry out changes on the database then these are written in the log file. For reasons ofperformance you have the option of deactivating this log function, but you must execute a databaseback-up beforehand.

'LVSOD\�*HQHUDWHG�5HSRUW

The report generated when deleting is displayed as an output list. This option is only available fordebugging.

$FWLYLWLHV

In the tabstrip ,QIR&XEH�&RQWHQW, choose the pushbutton 6HOHFWLYH�'HOHWLRQ. In the selection screenthen choose the pushbutton 'HOHWLRQ�6HOHFWLRQV�



,QIR&XEH�3HUIRUPDQFH

8VH

Here you can find the options that allow you to affect not only the load performance but also the queryperformance.

)XQFWLRQV

'DWDEDVH�,QGH[HV

With an increasing number of data records in the InfoCube, not only the load but also the queryperformance can be reduced. This is attributed to the increasing demands on the system formaintaining indexes. The indexes that are created in the fact table for each dimension allow you toeasily find and select the data. You should not create indexes when initially loading data into theInfoCube. Create the indexes after you have created the InfoCube.

The indexes displayed are the secondary indexes of the F and E fact tables for the InfoCube. Theprimary indexes and those defined by the user are not displayed. The aggregates area deals with thecorresponding indexes of the fact table for all aggregates of an InfoCube.

&KHFNLQJ�,QGH[HV

Using the pushbutton &KHFN�LQGH[HV� you can check whether indexes already exist, and whetherthese existing indexes are of the correct type (bitmap indexes).

Yellow status display: There are indexes of the wrong category

Red status display: No indexes exist, or one or more indexes are faulty

You can also list missing indexes using transaction DB02, pushbutton 0LVVLQJ�,QGH[HV. If a lot ofindexes are missing, it can be useful to run the ABAP reports SAP_UPDATE_DBDIFF andSAP_INFOCUBE_INDEXES_REPAIR.

'HOHWLQJ�,QGH[HV

For delta uploads with a large quantity of data (more than a million records), you should not align thedatabase indexes of the InfoCube with every roll up, rather delete the indexes first, and thencompletely reconstruct them after rolling up.

5HSDLULQJ�,QGH[HV

Using this function you can create missing indexes or regenerate deleted indexes. Faulty indexes arecorrected.

$JJUHJDWH�7DEOH�,QGH[HV

Just as for the indexes of the fact table, you can maintain the indexes of the aggregation tables.Maintaining the indexes of the aggregation tables affects all the aggregation tables of the InfoCube.

If the InfoCube contains more than 50 million records, you should, as a rule, refrain fromdeleting and recreating indexes.

'DWDEDVH�6WDWLVWLFV

Database statistics are used by the system to optimize the query performance. You should keep thedatabase statistics up-to-date for this reason.

It is recommended that you always update the statistics if you have loaded more than a million newrecords in the InfoCube since the last update.

Using the pushbutton &KHFN�VWDWLVWLFV� you can check the InfoCube to see if statistics exist. If nostatistics exist yet, the status display changes to red. Using 5HFDOFXODWH�VWDWLVWLFV� you can add themissing InfoCube statistics in the background.



You can determine the percentage of InfoCube data, that is used for creating the statistics. Thepercentage is set to 10% by default. The larger the InfoCube, the smaller you should choose thepercentage, since the demand on the system for creating the statistics increases with the change insize.

For up to 10 million entries in the InfoCube, you should set the percentage of InfoCubedata used for creating the statistics to 100%.



&RPSUHVVLQJ�,QIR&XEHV

8VH

When you load data into the InfoCube, entire requests can be inserted at the same time. Each ofthese requests has its own request ID, which is included in the fact table in the packet dimension. Thismakes it possible to pay particular attention to individual requests. One advantage of the request IDconcept is that you can subsequently delete complete requests from the InfoCube.

However, the request ID concept can also cause the same data record (all characteristics agree, withthe exception of the request ID) to appear more than once in the fact table. This unnecessarilyincreases the volume of data, and reduces performance in Reporting, as the system has to aggregateusing the request ID every time you execute a query.

Using compressing, you can eliminate these disadvantages, and bring data from different requeststogether into one single request (request ID 0).

This function is critical, as the compressed data can no longer be deleted from theInfoCube using its request IDs. You must be absolutely certain that the data loaded intothe InfoCube is correct.

)XQFWLRQV

You can choose request IDs and release them to be compressed. You can schedule the functionimmediately or in the background, and link it to other events.

Compressing one request takes approx. 2.5 ms per data record.

With non-cumulative InfoCubes, compression has an additional effect on query performance. Also, themarker for non-cumulatives in non-cumulative InfoCubes is updated. This means that, on the whole,less data is read for a non-cumulative query, and the reply time is therefore reduced.

If you run the compression for a non-cumulative InfoCube, the summarization time (including the timeto update the markers) will be about 5 ms per data record.

If you are using an Oracle database as your BW database, you can also carry out a reportusing the relevant InfoCube while the compression is running. With other manufacturers’databases, you will see a warning if you try to carry out a report using an InfoCube whilethe compression is running. In this case you can only report on the relevant InfoCubewhen the compression has finished running.

If you want to avoid the InfoCube containing entries whose key figures are zero values (in reverseposting for example) you can run a zero-elimination at the same time as the compression. In this case,the entries, where all the key figures are equal to 0, are deleted from the fact table.

Zero-elimination is permitted only for InfoCubes, where exclusively key figures with theaggregation behavior ‘SUM’ appear. You are not permitted to run a zero-elimination withnon-cumulative values in particular.

$FWLYLWLHV

For performance reasons, and to save space on the memory, summarize a request as soon as youhave established that it is correct, and is no longer to be removed from the InfoCube.



5HTXHVWV�LQ�WKH�,QIR&XEH

8VH

All the requests that have run in the InfoCube are displayed. You can also delete requests. You canalso see whether the requests are scheduled for aggregation, whether they have been aggregatedalready, or whether they are scheduled for deletion.

Use the update date to limit the number of requests that are displayed.

You can also control the higher-level monitor status of a request individually for an InfoCube.

)XQFWLRQV

,QIR&XEH�6WDWXV

You can aggregate only those data packages that have the traffic light status ³JUHHQ´ (meaning datapackages with stored data).

The traffic light status “green” means that the process is still running.

The traffic light status “red” means that there are problems uploading data, and that these problemsare preventing a secure upload. These can be, for example, errors in defining the transfer structure.

Data packages with traffic light status “red” or “yellow” cannot be taken into considerationwhen executing a query. In this case, subsequent data packages with the traffic lightstatus “green” are also not used in the query, because the consistency of the data in aquery can no longer be guaranteed.

In certain cases it could make sense to set the InfoCube-specific request status from red to green.

You update requests with the initial load into two InfoCubes If the load process runssuccessfully for InfoCube 1, but is unsuccessful for InfoCube 2, then the higher-levelmonitor status for the affected requests is set to red. As a result, you are not able to usefor reporting, the requests that were loaded successfully into InfoCube 1. You can set therequest status for InfoCube 1 to “green” by clicking on the status symbol for the request.

You can reproduce the original monitor request status by clicking on the request status symbol andchoosing 'HOHWH�VWDWXV��EDFN�WR�UHTXHVW�VWDWXV.

If you delete or reconstruct a request, a log is automatically generated in the application log. You canlook at the log by selecting the request and choosing the $SSOLFDWLRQ�ORJ�pushbutton.

In Transaction SM50 you can monitor and manage all background jobs and batchprocesses.

'DWD�0DUW�6WDWXV�RI�,QIR&XEHV

If the InfoCube is used in other BW Systems, the Data Mart status for the InfoCube is displayed. Usethe corresponding pushbutton to manage the distribution of a request.

&KHFNLQJ�WKH�'DWD�&RQVLVWHQF\�RI�5HTXHVWV�LQ�WKH�,QIR&XEH

You can carry out a consistency check on the InfoCube requests, meaning you can look for overlapsin the data selections.

For individual requests in the InfoCube, the InfoObjects or fields of the source system are displayedalong with the request selection conditions in the 6HOHFWLRQ�FRQGLWLRQV�column. The data consistencycheck runs using the information in this column.

To start a check, select the requests that you want to check from the tabstrip 5HTXHVWV�LQ�WKH,QIR&XEH.



Choose the pushbutton &KHFN�'DWD�&RQVLVWHQF\. This brings you to a separate session, where youcan enter other requests you want to check.

By using the radio buttons on this screen, you can also determine whether you want to 'LVSOD\�(UURUV2QO\�(partial overlapping of the data selections) and/or &RPSOHWH�2YHUODSV�2QO\� If you have notchosen any requests from the table, then all requests are checked.

Start the check.

A report that can be run in batch is started, that compares every selected request with every otherrequest in the InfoCube, and generates an ABAP list. This list contains information on the status of theupdate, on overlaps with other requests, as well as information on the options for compressing,aggregating, or deleting the InfoCube data.

6FKHGXOLQJ�%DFNJURXQG�-REV

Choose 6HOHFWLRQ�to schedule the update of requests individually or as an event chain in thebackground. The 6XEVHTXHQW�3URFHVVLQJ�function allows you to specify the events that you want tocarry out once the process is complete. Choose 'HOHWH to trigger the background job or to delete itdirectly.

5HTXHVW�&KHFN

You can specify if you want the system to check that the request IDs actually exist in the InfoCube. Todo this choose (QYLURQPHQW��→�&RPSOHWH�&KHFN�RI�5HTXHVW�,'.�If the check is switched on, you canrefresh the request display. This checks if all the requests that have not been aggregated orcompressed still exist in the InfoCube. If they no longer exist, the entry is deleted.

This process can take quite some time.

/RJ�'LVSOD\

You can call application logs for the requests in the InfoCube. To do this, select the request you wantto analyze from the 5HTXHVWV tabstrip and choose (QYLURQPHQW�→�$SSOLFDWLRQ�/RJ from the mainmenu or choose the $SSOLFDWLRQ�/RJ pushbutton. All the logs that were written for this request aredisplayed. In the log display, you can analyze and access more detailed information on the logs ortheir respective messages. A navigation tree allows you to navigate among the messages. Themessages you have selected are displayed in a list.

You can also display short logs for certain actions of the InfoCube Administration on tabstrip3HUIRUPDQFH using &DOO�ORJ. It is possible to analyze the process of these actions by using the statusnotifications and messages for these logs. The creation and deletion of indices, reconstruction ofstatistics, and selective deletion from the InfoCube, as well as the aggregation, compression andreconstruction of the InfoCube are all supported by the log display. In the application log, you can alsocall logs for the short logs. To do this, choose $SSOLFDWLRQ�ORJ and enter the date and time of thelogging. You get this information from the short log.




8VH

If you would like to use the InfoCube as a data source for another InfoCube or an ODS object, it isrecommended that you make automatic settings to simplify further processing.

)XQFWLRQV

6HWWLQJ�WKH�TXDOLW\�VWDWXV�WR�2.

You can specify that the quality status of the data is automatically set to OK after is loaded in theInfoCube. This is the prerequisite for processing the requests further.

5ROO�XS

You can automatically roll up and transfer into the aggregate requests in the InfoCube with “greentraffic light status”, that is, with saved data quality.

Parallel data update in an InfoCube results in errors when automatically rolling up in theaggregates. The error is that not all data requests of the loading process are rolled up inthe aggregates. In this case, delete all aggregates for the InfoCube and create themagain.

To avoid this error, you can do one of the following:

− do not carry out the data load in parallel but update the data packets in serial, or

− do not automatically roll up when carrying out the data load in parallel and insteadcarry this out manually after loading has been successful, or

− use ,QIR&XEH�5ROO�8S in the event chain functionality on the tabstrip.

&RPSUHVVLQJ�WKH�,QIR&XEH

You can compress an InfoCube for technical reasons of memory space or reporting performance, bydeleting the request IDs.

This function is critical, as the compressed data can no longer be deleted from theInfoCube using its request IDs. You must be absolutely certain that the data loaded intothe InfoCube is correct. For information about this, read Compressing InfoCubes [Seite412].

$FWLYLWLHV

To switch on the automatic further processing, select Main�0HQX�→ (QYLURQPHQW�→ 5HTXHVW+DQGOLQJ�



5HVWUXFWXULQJ�,QIR&XEHV

8VH

With this function, you can fill an InfoCube with requests that have already been loaded into a BW, orinto another InfoCube. You can, therefore, create a new InfoCube in BW, and use data that hasalready been loaded successfully into the PSA or into the IDOCs to fill the new InfoCube.

,QWHJUDWLRQ

This function is particularly useful, if you are loading deltas, that is, data that you cannot request againfrom the source system.

3UHUHTXLVLWHV

You have created a new InfoCube with update rules. The update rules must refer to an InfoSource forwhich data has already been loaded.

)XQFWLRQV

You can select an InfoCube, an InfoSource, a time frame or a source system, where all the requeststhat have already been loaded for your selection are displayed. You can choose individual requests,and use them to reconstruct the InfoCube.

You can start loading or scheduling the InfoCube immediately in the background, or set it so that it istriggered by an event.

$FWLYLWLHV

In the InfoCube tree, choose the ,QIR&XEH that you want to fill → &RQWH[W�0HQX��ULJKW�PRXVH�EXWWRQ�

→ $GPLQLVWUDWH. Choose 5HFRQVWUXFW�→�6HOHFWLRQ, and, using the selection options, determine therequests that you want to use to reconstruct the InfoCube.

Select the corresponding requests from the list, and choose 5HFRQVWUXFW.



0DQDJLQJ�2'6�2EMHFWV

)XQFWLRQV

The ODS object is displayed in the top table. If you reached the administration screen from theScheduler or the Monitor, you only have to make one selection from the several ODS objects ondisplay.

From the top toolbar, choose &RQWHQWV to display the contents of the table for the active data in theODS object you have selected. &KDQJH�8SGDWH�5XOHV brings you to the maintenance screen for theupdate rules. 'HOHWH�&RQWHQWV removes the contents of the ODS object. There is also the option ofdisplaying an application log and a process overview.

7DEVWULS��&RQWHQWV

You can have the change log table displayed, or you can display the content of the newly loaded datatable (activation queue), or that of the active data (A table). You can also selectively delete requestsfrom the ODS object.

See ODS Object Contents [Seite 418].

7DEVWULS��5HTXHVWV

This tabstrip gives you information on all the requests that have been run in the ODS object. You canalso delete requests here or schedule when they are to be updated.Refer to Requests in an ODSObject [Seite 419].

7DEVWULS��5HFRQVWUXFWLRQ

Use this function to fill an ODS object with requests that have already been loaded into a BW system,or into another ODS object.

Refer to Reconstructing an ODS Object [Seite 421].


If you want to use an ODS object as a data source for another ODS object or InfoCube, the data mustbe of a reliable quality, and be set to active.

If you choose the main menu path (QYLURQPHQW�→ $XWRPDWLF�5HTXHVW�3URFHVVLQJ��the systemautomatically sets the quality status to OK after the data has been loaded into the ODS object. Thisoption must be switched on. There is also the option of activating and updating ODS dataautomatically. Data that has been given the quality status OK is transferred from the $FWLYDWLRQ�4XHXHinto the $FWLYH�GDWD table, and the change log is updated accordingly. The data is updated in the datatargets. If this is the first time that the data has been updated, an init. update will be carried outautomatically.

Activating several requests can run in parallel, because their package ID, request ID and recordnumber makes them unambiguous. This enables inserts.

These settings are also available when you are creating ODS objects. See Creating ODS Objects[Seite 167].



&RQWHQWV�RI�DQ�2'6�2EMHFW

8VH

This function checks that the data that you loaded into an ODS object does not contain errors. It canalso selectively delete requests from the ODS object.

)XQFWLRQV

On the &RQWHQWV�tabstrip, you see a list of the InfoObjects for the ODS object. Use this to checkwhether the data that you loaded into the ODS object is free of technical errors. If the table containsmore than 40 fields suitable for selection, you have to select the fields first. You can change thisselection at a later date in the main menu under 6HWWLQJV�→ )LHOGV�IRU�6HOHFWLRQ. Choose 6HWWLQJV�→8VHU�3DUDPHWHUV to set-up the table display so that all ODS object columns are shown and nothing ismissing.

Choose /RJV to view the logs for requests that have been deleted, activated, reconstructed, or added.

You can display the contents of the activation queue table by choosing 1HZ�'DWD� If this new data isactivated, the system deletes the activation queue and moves the data to the table containing activedata.

Choose $FWLYH�'DWD to view the contents of the table containing active data (A table).

Choose�&KDQJH�/RJ�to�display the change log table. This table contains the change log requests thatare created each time you activate data.

The table contents are displayed in the data browser. This enables the use of functions such asdownloading in various formats.

6HOHFWLYH�'HOHWLRQ

We recommend selective deletion only when individual fields need to be deleted from the request,because they have errors or are superfluous. When you only want to delete data for a particularorganizational unit that was loaded incorrectly, for example.

The data is only deleted from the active data table. Data in the activation queue and in thechange log remain unchanged. Additional data targets must be adjusted manually.

Procedure:

1. Choose the pushbutton 6HOHFWLYH.

2. Specify the fields to be deleted under 'HOHWH�6HOHFWLRQV in the subsequent dialog window.

3. Schedule the delete job.


Deleting Requests [Seite 419]

Deleting from the Change Log [Seite 174]



5HTXHVWV�LQ�DQ�2'6�REMHFW

8VH

This tabstrip gives you information on all the requests that have been run in the ODS object. You canalso delete requests here or schedule when they are to be updated.

)XQFWLRQV

Choose the 5HTXHVWV� tabstrip.

5HTXHVW�6WDWXV

The traffic light status “red” means that there are problems uploading data, and that these problemsare preventing a secure upload. These problems might be caused, for example, by errors in thedefinition of the transfer structure. Use the pushbutton in the 'LVSOD\�5HTXHVW column to jump to theMonitor, and locate the error.

Only requests with a “green” status can be activated and displayed in the query.

Data packets with traffic light status “red” or “yellow” cannot be taken into considerationwhen executing a BEx query. In this case, subsequent data packages with the traffic lightstatus “green” are also not used in the query, because the consistency of the data in aquery can no longer be guaranteed.

You can reset the original request status in the Monitor by clicking on the request status symbol in thecolumn 40�5HTXHVW�6WDWXV�DIWHU�8SGDWH, and selecting 'HOHWH�VWDWXV��UHWXUQ�WR�UHTXHVW�VWDWXV.

'DWD�0DUW�6WDWXV

If the ODS object is used as a data source in data marts, that is in other BW systems or the Myselfsystem, the data mart status for the ODS object is displayed. Use the corresponding pushbutton tomanage the distribution of a request.

/RJV

You are able to call up application logs for the requests in the ODS objects. To call up the applicationlogs, select the request you want to analyze from the 5HTXHVWV tabstrip, and choose (QYLURQPHQW�→$SSOLFDWLRQ�/RJ.

'HOHWLQJ�5HTXHVWV

This tabstrip gives you information on all the requests that have been run in the ODS object. You canalso delete requests here if you need to. You can only directly delete requests that have yet to beactivated. The system uses the Rollback for requests that have already been activated.

5ROOEDFN�RI�5HTXHVWV

With this function, you delete active requests from ODS objects. This allows you to delete incorrectrequests, since the system usually only recognizes errors in the data or in the update rules after therequest has been activated. In doing so, the request is deleted from both the table for active data aswell as the change log.

If the request was already updated to additional data targets, a cancellation request is generated fromthe change log when the request is deleted. This forwards the delete information to the data target towhich the request was already updated.

When you roll back incorrect requests, the BW system returns to the status it had before you bookedin the incorrect requests. This means that all requests that were updated after the incorrect requestare also deleted. You can rebook requests, that are available in the PSA, afterwards.

This function is automatically activated when 'HOHWH is chosen for activated requests.


Deleting Selectively from Fields [Seite 418]



Deleting from the Change Log [Seite 174]

6FKHGXOLQJ�%DFNJURXQG�-REV

Choose 6HOHFWLRQ�to schedule the update of requests individually or as an event chain in thebackground. The 6XEVHTXHQW�3URFHVVLQJ�function allows you to specify the events that you want tocarry out once the process is complete. Choose 'HOHWH to trigger the background job, or to delete itdirectly.

$FWLYDWH�5HTXHVWV

You can activate requests via . You can select whether the requests should be compressed to onerequest in the change log when activated (this request can be rolled back from the ODS object as awhole). You can also select whether the requests should be activated in serial.



5HFRQVWUXFWLQJ�DQ�2'6�REMHFW

8VH

Use this function to fill an ODS object with requests that have already been loaded into a BW system,or into another ODS object.

)XQFWLRQV

Choose the 5HFRQVWUXFW�tabstrip. Reconstructing the ODS object gives you data from the change log,so that you can load deltas into the reconstructed ODS object.

Choose 6HOHFWLRQ to restrict the display of the request for an ODS object, an InfoCube, an InfoSource,or a source system. All the requests that have already been loaded for your selection are displayedhere. You are able to select individual requests, and use them to reconstruct the ODS object. To dothis, choose 5HFRQVWUXFW�$GG.

You can either start loading the ODS object immediately, or schedule the load as a background job / tobe triggered by an event.

In 6XEVHTXHQW�3URFHVVLQJ��specify the events that you want to carry out once the process is complete.

If you select more than one request for reconstruction, you must deactivate the functionsfor automatic activation and automatic update.

You can reconstruct the ODS objects using process chains [Seite 424].



0DQDJLQJ�,QIR2EMHFWV

)XQFWLRQV

7DEVWULS��&RQWHQWV

You can display the contents of the table containing the newly loaded data.

7DEVWULS��5HTXHVWV

You get information on all requests that have run in the InfoObject and you can delete theadministrative information about these requests. You cannot delete data from the InfoObject here, asfor the ODS object or InfoCube.

7DEVWULS��5HFRQVWUXFWLRQ

With this function, you can fill an InfoObject with requests that have already been loaded into BW orinto another InfoObject.



3URFHVV�&RQWURO

3XUSRVH

The BW background processing system supports job or process scheduling for specified times,calendar days and after specific predecessor jobs in the Administrator Workbench. It also supportsevent-controlled job and process scheduling. You can use event-controlled processing to triggerprocesses in BW.

3URFHVV

The following options are available for process control or process automation:

1. You can control several interconnected processes using process chains [Seite 424]. A processchain is a sequence of processes that wait in the background for an event. Some of theseprocesses trigger a separate event that starts other processes in turn.

2. You can control processes in BW with events that you have determined using 7RROV�→�&&06�→-REV�→�0DLQWDLQ�HYHQWV. An event is a signal to background controlling that a particular situationhas arisen in the system. Background processing then starts all processes that have been waitingfor this event.

You can also activate events created in this way so that they depend on the success of oneprocess to trigger subsequent processes. The subsequent processing [Seite 448] functionallows you to do this.

3. In addition to controlling using individual events, you can determine event collectors [Seite 449]that have to be processed before a process is triggered.

You can find further information on event processing in Basis documentation under the sectionThe Event Concept and Event Processing [Extern].

Events, event collectors and process chains are only valid in the background processingsystem. You can only start background jobs with an event.

In BW 3.0, automatic process control has been enhanced and improved significantly withthe concept of process chains. Process control using post-processing events and eventcollectors is not functionally enhanced but it is still supported. This likewise applies to theInfoPackage groups [Seite 396]. :H�UHFRPPHQG�WKDW�\RX�RQO\�XVH�SURFHVV�FKDLQV�IRUVFKHGXOHV�RI�FRQQHFWHG�SURFHVVHV�WKDW�PXVW�EH�UH�GHILQHG�



3URFHVV�&KDLQV

'HILQLWLRQ

A process chain is a sequence of processes [Seite 427] that wait in the background for an event.Some of these processes trigger a separate event that can start other processes in turn.

8VH

In an operating BW system there are a multitude of processes in addition to the loading process thatoccur regularly.

'DWD�7DUJHW

$GPLQLVWUDWLRQ

6WDUW

/RDG�LQWR�36$

/RDG�LQWR�2'6

$FWLYDWH

2'6�'DWD

%XLOG�,QGH[HV

%XLOG�'%

6WDWLVWLFV

5ROO�8S

$JJUHJDWH

'HOHWH

,QGH[HV

'DWD�/RDG

0RQLWRU

/RDG�LQWR�,QIR&XEH

If you use process chains, you can

• DXWRPDWH the complex schedules in BW with the help of the event-controlled processing,

• YLVXDOL]H the schedule by using network applications, and

• FHQWUDOO\�FRQWURO�DQG�PRQLWRU the processes.

Fundamental principals of the process chain concept are:

• Openness

The abstract meaning of a process as any schedule with a defined beginning and end enablesopenness with regard to the type of process that can be integrated into a process chain. Thus,the principle of openness is realized so that user-defined programs and processes can beimplemented. In addition, you can include process chains in other process chains, so-calledmeta chains. In doing so you have the option of integrating process chains from the BWsystem, in which the meta chain is found, or from other BW systems. In this context, local orremote process chains are concerned.

• Security

Using process chains offers a high amount of schedule security, which is based on theprincipals of background management:

− Processes are scheduled before your run and can be monitored with the standard batchmonitor.

6HH�DOVR� Process Chain Logs [Seite 446]



− You start subsequent processes by using background events.

− Short dumps and terminations are recognized and handled respectively.

• Responsibility

The subsequent process is responsible for getting all the information from the predecessorsthat is needed for a correct run. This enables the integration of new process types withouthaving to be suitable for the existing types.

You can call up process chain maintenance centrally from the BW Administrator Workbench using 3URFHVV�&KDLQ�0DLQWHQDQFH�in the toolbar. Use the corresponding pushbutton to access process chainmanagement from the maintenance dialogs in the BW-supported processes.

6WUXFWXUH

A process chain consists of a start process, individual application processes and the so-calledcollection processes.

Define the start of your process chain with the start process [Seite 428]. All other chain processes arescheduled to wait for an event.

The application processes [Seite 429] are the actual processes. BW supports process types of thefollowing categories:

• Load process and post processing processes

• Data target administration processes,

• Other BW processes

as well as ABAP programs and processes you have implemented.

You also have the option to include process chains as processes themselves in another processchain. In doing so, you determine whether you are dealing with a ORFDO�SURFHVV�FKDLQ or a UHPRWHSURFHVV�FKDLQ� A local process chain comes from processes that are scheduled in the BW systemitself. It is scheduled as a process in the same BW system. A remote process chain calls a processchain that needs to be run by using a destination in another system. After terminating the processchain in another system, this is confirmed in the BW system and terminates the remote process chainthere.

Collection processes [Seite 437] are treated differently by the process chain maintenance. They allowseveral chain strings to be combined to form one individual string. In this way, they replace multi-fieldscheduling of the actual work processes.

Processes are connected via events that start a successor process after being triggered by apredecessor process.

,QWHJUDWLRQ

A process chain is a BW object with a transport system [Extern] and a connection to the BW documentmanagement [Seite 479].

If you use process chains, the automatically integrated processes are ignored and have tobe implemented by using the process chain. If you schedule a specific process in a chain,you support the automatic insertion of additional, relevant standard processes with theconsideration of such automatic actions.

For example, if you have selected the processing types 2QO\�36$ and 6XEVHTXHQWO\�LQ'DWD�7DUJHWV in the InfoPackage from the tab page 3URFHVVLQJ, the further processing intothe data target does QRW automatically happen. Instead, it only happens if the process8SGDWH�36$ is scheduled in the respective process chain after the loading process. Thus,the process chain maintenance supports the automation in this case. In this way, yougenerate a process variant for updating from the PSA in the chain when inserting theloading process with the process type 2QO\�36$ automatically into a chain.



3URFHVVHV

'HILQLWLRQ

A process in the context of BW process chains is a procedure inside of or external to an SAP systemwith a defined beginning and end.

A distinction is made between a start process, an application process and a collection process.

8VH

In order to automate runs in BW, processes are brought together in so-called process chains. Theprocesses are scheduled in the background. Each process can trigger one or more events, that triggerother processes in turn.

6WUXFWXUH

A process is characterized by

• the process type

The process type is the kind of process, for example load process. The process type decideswhich tasks the process has and which properties it has in the maintenance.

The process type is set in the RSPROCESSTYPES view.

• the process variants

The process variant is the name of the process Within the process chain context, it displaysthe configuration of a process of a particular type set at the time of definition. A variant is onlyconsistently defined together with the process type. A process can have various variants. Withthe load process for example, the name of the InfoPackage is the name of the process variant.

The user defines the process variant at the time when the process is scheduled. With someprocess types, the variants are determined internally and are stored as GUIDs.

• the process instance

The process instance is the characteristic value of the process It contains the most importantinformation that the process, or subsequent processes want(s) to communicate. In the loadprocess, this would be the name of the request for example. If the process is ended, theinstance is transferred to the process chain management and saved. The logs for the processare stored under the process instance.

The instance is determined by the process itself at run time, and is determined consistently,independent of time or system.



6WDUW�3URFHVV

'HILQLWLRQ

You can use the start process to define the start of a process chain.

8VH

The background control options are available to GLUHFWO\�VFKHGXOH the start process. You can start thestart process immediately , that is when activating the process chain, for a specified time, or after aparticular event. When you activate the process chain, the start process is scheduled in thebackground as defined in your selections.

You can also trigger the start of a process chain YLD�D�PHWD�FKDLQ� A meta chain is created when aprocess chain, to which you set this start condition, is fixed to another process chain. The processchain is started directly by this meta chain.

When you start the start process via a meta chain, it is not scheduled after you activatedthe related process chain. The process is only started when the meta chain, to which it islinked, is running.

The remaining chain processes, that is the application processes and the collection processes, arescheduled to wait for an event.

The start process has the following special features:

• Only the start process can be scheduled without a predecessor process.

• The start process can not be the successor of another process.

• Only one start process is allowed for each process chain.

• One start process can only be used in an individual process chain.



$SSOLFDWLRQ�3URFHVVHV

'HILQLWLRQ

Application processes are processes that are automated in the process chain maintenance. Theyrepresent BW activities typically executed in the operative use of BW.

7KH�DSSOLFDWLRQ�SURFHVVHV�VXSSRUWHG�E\�WKH�SURFHVV�FKDLQ�PDLQWHQDQFH�DUH�

3URFHVV�&DWHJRU\ $SSOLFDWLRQ�SURFHVV�W\SH

Loading process and postprocessing • Data loading process

You can find further information aboutthe data loading process underScheduler [Seite 350])

• Reconstructing/updating PSA

See also: Types of Data Update withPSA [Seite 389] and sections about theregeneration of data targets in the DataTargets Administrationdocumentation/SAPIrExtHelp/IWB_EXTHLP.asp?_LOIO=C2A28B3B9EA21341E10000000A11402F [Seite 402]

• Saving hierarchies

• Updating ODS Data [Seite 172](subsequent updating)

• Exporting data to external systems

• Deleting Overlapping requests from AnInfoCube [Seite 367]

Data target administration • Delete Index [Seite 410]

• Constructing indexes

• Constructing database statistics

• Initial Filling of New Aggregates [Seite 141]

• Rolling up Filled Aggregates [Seite 144]

• Compressing InfoCubes [Seite 412]

• Activating ODS Data [Seite 172]

• Deleting data target contents in full

Other BW processes • Attribute Change Run [Seite 399]

• Adjusting time-dependent aggregates

• Deleting Requests from the PSA [Seite395]

General services • ABAP Program [Seite 432]

• Process Chain [Seite 424] local

• Process chain remote

• Processes You Have Implemented [Seite434]

You can call up documentation for a process type in the BW system by marking the process type inthe overview tree and choosing F1. The tree is located in the left-hand screen area of the process



chain maintenance. You can also add a process to the dialog window in which the variant is fixedbefore choosing )XUWKHU�+HOS�



5HPRWH�3URFHVV�&KDLQ

'HILQLWLRQ

Process chains can be scheduled as processes in additional process chains, which are also calledmeta chains. In this case, a remote process chain is a local process in the BW system called. Thissystem calls up a process chain that needs to be run by using a destination in another BW system.The remote process transfers the communication with the other system and synchronously starts theexecuted process chain. After terminating the process chain in another BW system, this is confirmedfor the meta chain in the BW system called.

3UHUHTXLVLWHV

Before you can run a process chain in another BW system, you have to execute the following steps:

• Define the process chain, which needs to be run, in the BW system to be called.

• Maintain a destination for the BW system to be run.

• Maintain a destination, which is displayed back in your BW system, in the BW system to be calledup.

8VH

With the help of the remote process chains, you can then schedule process chains from other BWsystems in a chain in the BW system called.

,QWHJUDWLRQ

In addition to remote process chains, you can also schedule local process chains as processes in ameta chain. A local process chain consists of processes that are scheduled in the same BW system asthe meta chain. You schedule it as a process in the same BW system as the meta chain.



$%$3�3URJUDPV

'HILQLWLRQ

Within the context of BW process chain maintenance, an ABAP program is a process type.

8VH

Use the $%$3�3URJUDP�process type if you want to use a simple, independent program in a chain orif you want to use a program scheduled by a user or another program in the background. You thenhave the option to schedule a program of your choice (ABAP report) in the process chainmanagement, with or without SURJUDP�variants.

The scheduling options are as follows:

• Synchronous, local

Specify the program name and variant under 3URJUDP�WR�EH�&DOOHG�8S�→�3URJUDP�� Theprogram is started when the event for the predecessor process was triggered.

The program is executed in the background on the same server on which the process chain isscheduled. The process chain waits until the program has finished before it continues with anypossible successors.

• asynchronous

Choose this option when your program is asynchronous.

An asynchronous process is also called a distributed process. Distributed processes arecharacterized as having different work processes involved in specific tasks. A program isasynchronous when it does not end the task which it started itself. In an asynchronousprocess, the process chain maintenance does not equate the end of the process with the endof the background process. The process status remains DFWLYH�

In asynchronous processes, successor events are not automatically triggered.You need to call the remote-enabled RSPC_ABAP_FINISH function module at the end of yourprogram to signify the real end of your process. The process is then highlighted as completedand the successor events are triggered.

Inform the function module of the SURFHVV�variant, with which your program is scheduled. Todo this, you need to either hardcode the process variant in the program or transfer theSURFHVV�variant in a SURJUDP�variant You need the following lines in your program to do this:

PARAMETERS variant TYPE rspc_variant.

The process chain management does not recognize when your program terminates.

Therefore, when you re-start the chain, it will also terminate since the old run was notyet completed. To avoid this, you need to manually set the process to WHUPLQDWHG inthe chain log view in the process monitor (3URFHVV�tab strip). Do this prior to startingagain.

− Asynchronous, local

Choose this option when you want to start a program scheduled in the background. Theprogram must be scheduled to wait for a background event. Enter the event and, ifnecessary, the parameter under 3URJUDP�WR�&DOO�→�6FKHGXOHG�3URJUDP�

This option allows you to execute a program on a different server in the same system.

− Asynchronous, destination

In this option, you must schedule the program to be called up on the target server to waitfor an event.

Under &DOOHG�)URP��enter the 'HVWLQDWLRQ�for the target system and enter the event and, ifnecessary, the parameter via 3URJUDP�WR�%H�&DOOHG�8S�→�6FKHGXOHG�3URJUDP�



This option is only available for target systems as of service API 3.0A.

We recommend that you write a local program, in which you synchronously call up aremote-enabled function module in the target system. Then choose the option6\QFKURQRXV��/RFDO� This allows you to monitor your process with the process chainmaintenance.

You can write logs without much effort by issuing success messages. These protocols are displayedvia the context menu for a process in the process chain maintenance log view. Choose 'LVSOD\

0HVVDJHV→�7DE�6WULS�%DWFK�

Error messages terminate the job. Therefore, write your logs as success messages.

,QWHJUDWLRQ

We recommend you model more complex processes not covered by BW process types usingImplementing Your Own Process Type [Seite 434] .



,PSOHPHQWLQJ�<RXU�2ZQ�3URFHVV�7\SH

3XUSRVH

If you:

• write your own application log to be displayed in the 3URFHVV�tab strip for the Logs for a Process inthe Process Chain Maintenance [Seite 446], or:

• if you have implemented your own monitor, or

• have implemented a Customizing interface that goes beyond the parameters of a program, or

• want to access preceding chain processes in your program,

we recommend that you implement your own process type.

3UHUHTXLVLWHV

You need to have a good knowledge of the ABAP object-orientated language enhancement - ABAPObjects [Extern].

3URFHVV

• IN the BW system menu, choose 7RROV�→�$%$3�:RUNEHQFK�→�'HYHORSPHQW�→�&ODVV�%XLOGHU

You can find additional information about the Class Builder in the SAP Web ApplicationServer documentation under %&��$%$3�:RUNEHQFK�→�$%$3�:RUNEHQFK��7RROV�→�ClassBuilder [Extern].

7KH�IROORZLQJ�,)B563&B �LQWHUIDFHV�DUH�DYDLODEOH�

Interface IF_RSPC_* 'HVFULSWLRQ

EXECUTE Executes the process.

This interface is the main interface used toimplement your own process type and is theonly process chain maintenance interface thatis obligatory.

GET_INFO Transfers the information for a process to thesuccessor.

GET_LOG Returns the log for a variant and an instance tothe process chain maintenance, either as a titleand text or as a list of messages

MAINTAIN Enables process variants to be created andmaintained in the process chain maintenance.It also determines the header information for avariant so that it can be displayed in theprocess chain maintenance.

GET_VARIANT Provides value help (F4) for variants.

You need to implement this interface and/orinterface IF_RSPC_MAINTAIN, in order to beable to add process variants to a chain.

GET_DEFAULT_CHAIN Gives the default chain for a process. You cansuggest, for each variant to be scheduled,which additional process it would make senseto schedule before or after the process.



CHECK Consistency check at scheduling time for theprocess/chain

You can carry out a check to determine:

• the consistency of a process

• dependencies on RWKHU�processes in theVDPH�chain and

• dependencies on RWKHU�processes in RWKHUchains.

GET_STATUS We recommend you implement this interfacefor distributed processes. Distributedprocesses, such as the loading process, arecharacterized as having different workprocesses involved in specific tasks.

The interface allows you to request the statusof the instance in the process chainmaintenance(for distributed processes whenfollow-on events are not sent). Therefore, thesystem can also recognize terminations evenfor distributed processes.

CALL_MONITOR Calls up the process monitor from the log viewin the process chain maintenance.

TRANSPORT Returns TLOGO entry.

CONTEXT_MENU Adds some functions to the context menu for aprocess in the process chain maintenance.

You can find further documentation for the IF_RSPC_* interfaces under 7RROV�→�$%$3

:RUNEHQFK�→�'HYHORSPHQW�→�&ODVV�%XLOGHU in the BW system. For 2EMHFW�7\SH��enter theinterface name and choose display. You can access the documentation in the subsequentscreen using the -XPS�menu.

$Q�2YHUYLHZ�RI�WKH�,QWHUIDFHV�

;;75$163257

;;&217(;7B0(18

;;&$//B021,725

;;;*(7B67$786

;;&+(&.

;;��

;;*(7B9$5,$17

;;0$,17$,1

;;;*(7B/2*

;;;*(7B,1)2

;;(;(&87(

2SWLRQDO$OWHUQD�

WLYH

2EOLJD�

WRU\

/RJ

9LHZ

5XQWLPH0DLQWHQ

�DQFH

,QWHUIDFHV�,PSOHPHQWDWLRQ�LV��0HWKRG�&DOOHG�8S�IRU��



• Enter the process type under 6HWWLQJV�→�0DLQWDLQ�3URFHVV�7\SHV (RSPROCESSTYPES view) inprocess chain maintenance..

− Then choose (GLW�→�1HZ�(QWULHV, allocate the technical name, short and long description forthe process type, enter the name of your class for 2EMHFW�7\SH�1DPH, and choose ABAP-OOClass as the 2EMHFW�7\SH�

− Determine 3RVVLEOH�(YHQWV�

− Determine whether the process FDQ�EH UHVWDUWHG��through which icons (Id) it is represented,whether the variant name is determined internally, and whether an individual mail handling isimplemented for the process type.

− Assign the process type to a process category.

− Enter a number for the position where your process type is to be displayed within a processcategory in process chain maintenance.

− If necessary, assign a documentation type and a docu. object to the process type. The docuobject can be called up via F1 in the process chain maintenance overview tree.

• If using the service class CL_RSPC_APPL_LOG, enter your process type as a sub-object to the logobject BW_PROCESS.

5HVXOW

Your process is available in the process chain maintenance of the process category you assigned.



&ROOHFWLRQ�3URFHVV

'HILQLWLRQ

A collection process collects several chain strings to form one string in the process chainmaintenance.

8VH

Process chain management handles collection processes in a particular way. The system makes thevariant names consistent and guarantees that all processes of the same name that have beenscheduled more than once, trigger the same event. This enables the several chain strings to becollected to form one and also makes multiple-scheduling of the actual application processesunnecessary.

The following collection processes are available in the process chain maintenance:

• And Process (Last)

This process does not start before all events of the predecessor processes, that is includingthe ODVW�event, that it has waited for, have been successfully triggered.

Use this collection process when you want to combine processes and when further processingis dependent on all these predecessors.

• Or Process (Every)

The application process starts HYHU\�WLPH a predecessor process event has been successfullytriggered.

Use this collection process when you want to avoid multi-scheduling the actual applicationprocess.

• XOR Process (First)

The application process starts when the�ILUVW event in one of the predecessor processes hasbeen successfully triggered .

Use this collection process when you want to process processes in parallel and schedulefurther independent processes after these ones.

Owing to the time components, the collection processes do not display logical gates in thenormal sense, because the system cannot distinguish between whether a 0 entry (QRHYHQW�UHFHLYHG), means that the event was QHYHU�UHFHLYHG or whether it has QRW�EHHQUHFHLYHG�\HW. The reason for this is that the checks do not run continuously but only takeplace when the event is received.



3URFHVV�&KDLQ�0DLQWHQDQFH

8VH

Process chain management automates runs in BW.

3UHUHTXLVLWHV

If you want to include a load process in a process chain, you need to have already created anInfoPackage in the Scheduler.

)XQFWLRQV

You can check and monitor the chains in the process chain maintenance.

You can call up process chain maintenance using the pushbutton in the modeling, monitoring andReporting Agent AWB function areas toolbar.

You can also maintain a process chain directly out of the maintenance dialog from a supportedprocess. You then create a variant for the latest process, assign a description for the process chain,maintain additional associated process variants, and then create the links.

In the left-hand area of the screen, different process types are available according to processcategories to be transferred into your process chain.

In the right-hand area of the screen, the current view of the process chain maintenance is displayed.Different views, which you get by using the *R�WR�menu, facilitate chain management. Define theprocess chain and schedule individual processes in �3ODQ�9LHZ. You can use drag and drop toinclude the processes to be scheduled in the chain, beginning with the general start process. You canalso then create links. Before you activate the chain, check for errors in the &KHFN�9LHZ� When youactivate the process chain, start the chain run according to the start process selections. You can callup the process monitor and display the logs for a process chain run in the /RJ�9LHZ.

By using the /HJHQG for a process chain maintenance view, you can call up information regardingthe status of the processes and links.

$GGLWLRQDO�)XQFWLRQV�LQ�3URFHVV�&KDLQ�0DLQWHQDQFH

&RQWH[W�0HQX

If you select a process or a link with by left-clicking the mouse, you can call up different functions byusing the context menu (right-click mouse). The functions offered by using the context menu dependon whether you are in the plan, checking, or log view and whether there any process chains arealready running. You can find additional information regarding the respective functions in the sectionsCreating Process Chains [Seite 440] and Process Chain Logs [Seite 446].

3ULQW�DQG�6DYH

By using the 3URFHVV�&KDLQ menu, you have the option to save or print the process chain as a picture.

9LHZ�0HQX�)XQFWLRQV

Rotate With this function you can switch betweenvertical and horizontal views.

Navigator With this function you hide or show thenavigator (which is able to be positioned) in theright-hand area of the process chainmaintenance screen. It gives you an overviewof your process chain that is being processed.It also enables you to enlarge or reduce theview by moving the mouse.

Enlarge With this function you enlarge your processchain view by about ten percent.



Reduce With this function you reduce your processchain view by about ten percent.

Adjust With this function you adjust the process chainview to the size of the right-hand screen area.

Detailed VAiew With this function you get to the detailed viewfor process chain maintenance. The processtype, variant technical name, and the variantdescription are displayed here for a process.Important elements from the worklist that wassaved in the variant are listed, for example,when updating PSA information for the dataloading process and the data target.

A collation process is displayed several timesin the detailed view. The multiple display helpsto visualize that a MRE is started for eachSURFHVV and for each HYHQW triggered by theprocess.

Simplified View With this function you get to the simplified viewfor process chain maintenance. Only processtypes and variant descriptions are displayed fora process here.

Additional Chains With this function you also display additionalchains in the process chain maintenance forcurrent process chains.

If you link processes of two chains vertically,the processes are added to a chain of anotherchain, and the superfluous chain is deleted.

If you display several chains, the system asksyou with each action which chain you want tochoose for the action. For example, if you havedisplayed several chains and want to removeone chain from the view and are executing thefunction, you are asked to choose the chainsthat need to be removed.

If you save or activate, all the chains displayedare saved or activated respectively.

Other Chains With this function you display another chaininstead of the current process chain.

Remove from View With this function you remove a process chainfrom a view. If you only had one chain in theview, then the existing process chains fortransferring into the maintenance view areoffered.



&UHDWLQJ�D�3URFHVV�&KDLQ

3UHUHTXLVLWHV

If you want to include a load process in the process chain, you need to have already created anInfoPackage. You cannot load flat file data from a client workstation in the background. For thisreason, you have stored your data on an application server.

&UHDWLQJ�D�3URFHVV�&KDLQ

You have the option to create a process chain directly in the process chain maintenance or by using amaintenance dialog for a process:

&UHDWLQJ�D�3URFHVV�&KDLQ�'LUHFWO\�LQ�WKH�3URFHVV�&KDLQ�0DLQWHQDQFH

They are found in the BW Administrator Workbench.

1. Choose �3URFHVV�&KDLQ�0DLQWHQDQFH�in the AWB toolbar.

The Process Chain Selection�dialog window appears.

2. Choose &UHDWH�

3. Enter the technical name and a description of the chain and confirm your entry.

The $GG�6WDUW�3URFHVV dialog window appears.

4. Create a variant for a start process.

a. Choose whether you want to schedule the chain directly or start it by using a meta chain onthe 0DLQWDLQ�6WDUW�3URFHVV�screen.

b. If you schedule the chain directly, enter the start date value for the chain under &KDQJH6HOHFWLRQV and save your entries.

The 0DLQWDLQ�6WDUW�3URFHVV�screen appears again.

c. Save your entries. Then go back and confirm your entries in the $GG�6WDUW�3URFHVV dialogwindow.

The process chain maintenance �3ODQ�9LHZ�appears�

The various process categories with the application and collection processes are displayed inthe left-hand area of the screen. In the right-hand side, the process chain is displayed.

5. Add the relevant processes into your process chain with drag and drop.

If you insert a process that is linked with additional processes into the chain, therespective process variants are generated and automatically inserted into the processchain. These variants are suggestions and can be changed and removed from the chain.Your chain is checked in the checking view and during activation. This is indicated for youwhen necessary.

&UHDWLQJ�D�3URFHVV�&KDLQ�8VLQJ�WKH�0DLQWHQDQFH�'LDORJ�IRU�D�3URFHVV�

You are in the maintenance dialog of a process that is to be included in a process chain.

1. Choose the 3URFHVV�&KDLQ�0DLQWHQDQFH�pushbutton and create a process variant.

2. Save the variant and go back.

A dialog window appears in which you can enter a technical name and a description of thechain to be created.

3. Confirm your entries.

The $GG�6WDUW�3URFHVV dialog window appears.

4. Create a variant for a start process.



a. Choose whether you want to schedule the chain directly or start it by using a meta chain onthe 0DLQWDLQ�6WDUW�3URFHVV�screen.

b. If you schedule the chain directly, enter the start date value for the chain under &KDQJH6HOHFWLRQV and save your entries.

The 0DLQWDLQ�6WDUW�3URFHVV�screen appears again.

c. Save your entries. Then go back and confirm your entries in the $GG�6WDUW�3URFHVV dialogwindow.

The process chain maintenance �3ODQ�9LHZ�appears�

The various process categories with the application and collection processes are displayed inthe left-hand area of the screen. In the right-hand side, the process chain is displayed.

If you insert a process that is linked with additional processes into the chain, therespective process variants are generated and automatically inserted into the processchain. These variants are suggestions and can be changed and removed from the chain.Your chain is checked in the checking view and during activation. This is indicated for youwhen necessary.

5. Add the additional processes that are relevant into your process chain with drag and drop.

$GGLWLRQDO�3URFHVV�6WHSV�:KHQ�&UHDWLQJ�D�3URFHVV�&KDLQ

6. Select a process variant when adding the processes, or create a new variant. For collectionprocesses, the system makes sure the variants are consistent.

Different functions are available for the processes by using the context menu:

&RQWH[W�0HQX�(QWU\�IRU�D�3URFHVV )XQFWLRQ�,QIRUPDWLRQ

Maintain Variants Except for the collation process variants, youcan change all process variants with thisfunction.

Exchange Variants You can exchange the variants for an existingor newly created variant.

Display Scheduled Jobs After you activated the process chain, you candisplay the scheduled jobs with this function.

Display All Jobs After at least one run of the process chain, youcan also display the jobs, with which thisprocess was run, for a specific process next tothe scheduled jobs. You arrive at the joboverview and can call up the relevant job log.



Maintain Message You can also send messages to a chainapplication process depending on the successof the completion.

1. For this you create an additional processvariant of type 6HQG�0HVVDJH for aprocess by using the context menu.

2. If you maintain a message, first enterwhether the message needs to be sentwith successfully completed processes orwith processes completed with errors.Then choose &RQWLQXH.

3. You then arrive at a window in which youcan select or create a process variant.

4. If you create a new process variant, editthe document that needs to be sent andmaintain a receiver list.

5. Save your process variant and go back.

The message process variant is now assignedto your application process. If you send themessage, the status information as well as theprocess log is sent along as well, if necessary.

Wait Time Enter how long the process needs to wait (inseconds) after the preceding, triggered eventuntil it is run.

This function debugs the process execution.You can capture the process by using thetransaction SM37 (-RE�2YHUYLHZ) or SM50(3URFHVV�2YHUYLHZ).

Remove Process With this function you remove a process from aprocess chain.

7. Connect the processes through events by holding down the left mouse button.

By using the context menu for a link, you can display the event or remove the link again.

8. If required, specify whether the event is to be triggered after successful or incorrect termination ofthe predecessor process.

9. Assign a display component to the process chain using $WWULEXWH�→�'LVSOD\�&RPSRQHQWV�

10. Maintain additional process chain attributes [Seite 444] if necessary.

11. Check your process chain in the �&KHFNLQJ�9LHZ and correct the chain if necessary.

The /HJHQG describes the meanings of the different colors for processes and links.

By using the context menu for a process you can display the messages delivered by thecheck.

12. Save your process chain if it does not contain any errors.

5HVXOW

Your process chain can be activated. The chain starts after activation in accordance with the startprocess selections. The chain run starts directly after activation, if you scheduled the start process



directly and chose ,PPHGLDWHO\�as the start date value. In the /RJ�9LHZ��you can allow the reportsfor the chain runs to be displayed.

6HH�DOVR�

Process Chain Log [Seite 446]



3URFHVV�&KDLQ�$WWULEXWHVA process chain has the following attributes:

3URFHVV�&KDLQ�→�$WWULEXWH�→�� ,QIRUPDWLRQ

Name

( 5HQDPH)

You can change the name of the processchain.

Display Components

( )

Display components serve as the evaluationcriterion in the process chain maintenance.Accessing the chain you want is made easierby assigning the process chains to displaycomponents.

To create a new display component, choose$VVLJQ�'LVSOD\�&RPSRQHQWV in the input helpwindow and assign a technical name anddescription for the display component in thewindow that follows, 'LVSOD\�*URXSLQJ.

Documents

( )

See Documents [Seite 479]

Last Changed by

( )

Displays the technical attributes of the processchain:

• when and by whom it was last changed

• when and by whom it was last activated

• object directory entry

3ROOLQJ�)ODJ With this indicator you can control the behaviorof the main process when you have distributedprocesses. Distributed processes, such as theloading process, are thus characterized ashaving different work processes involved inspecific tasks.

With the polling flag you determine whether themain process needs to be kept as long as theactual process has ended.

By selecting the indicator,

− a high level of process security isguaranteed, and

− external scheduling tools can beprovided with the status of thedistributed processes.

However, the resource use of thesystem is increased and abackground process is morenecessary.



0RQLWRULQJ With the indicator in the dialog box 5HPRYH&KDLQ�IURP�$XWRPDWLF�0RQLWRULQJ"��you canspecify that a process chain be removed fromthe automatic monitoring with CCMS.

The automatic process chain monitoring isswitched on with CCMS by default.

You can find additional information about theCCMS context 3URFHVV�&KDLQV in the sectionBW Monitor in CCMS [Extern].



3URFHVV�&KDLQ�/RJ

8VH

You can check the process chain runs in the process chain maintenance /RJ�9LHZ�

)XQFWLRQV

If you go to the log view, you need to choose a time frame first. You need to display this time frame forthe chain runs. Then choose a run for which you want to call up the log. You arrive at the log view forthis run.

By using the /HJHQG, you get information regarding the status of the processes and the links.

You can display processes, which have not been run yet, in the log view for a processchain. This depends on whether or not the chain has been changed since the last run. Ifyou have not changed the chain since the run that needs to be checked, then theprocesses that have not been run are displayed in gray in the log view for this run. Also,the link for such processes is marked with dashes if the event has not yet been triggered.However, if the chain has been changed since the run that needs to be checked, then theprocesses that have not yet been run and the events that have not yet been triggered arenot displayed at all in the log view for this run.

Start

Load Data

Update PSA

Build Index

Start

Load Data

Update PSA

Log View for Running the Process Chain X If

This Was Changed Since the Beginning of the Run

Log View for Running the Process Chain X

Changing the Process Chain X in X‘

Start

Delete Index

Load Data

Update PSA

Build Index

By using 'LVSOD\�0HVVDJHV in the context menu for a process, you can call up the log. The logs aredisplayed in the following dialog box for the tab pages &KDLQ, %DWFK, and 3URFHVV.

• The tab page &KDLQ contains information regarding the start and end of the process as well as thecreated instance.

• The log for the job is displayed for the tab page %DWFK in the SAP List Viewer Grid Control. Youarrive at the job overview for your job by using the pushbutton %DWFK�0RQLWRU.

• The tab page 3URFHVV contains the process-based messages.•

This tab page is then displayed if the process type writes its own log or if the interfacesIF_RSPC_GET_LOG and IF_RSPC_CALL_MONITOR are implemented for the process type.



The option of using 3URFHVV�0RQLWRU to go to this monitor exists with processes (the loadingprocess, for example) that have a special monitor attached.

If you want to call up another log for this chain, choose *R�WR�→�2WKHU�/RJ or in the process chainmaintenance toolbar.

6HH�DOVR�

Process Chain Attributes [Seite 444] → Section: 0RQLWRULQJ.



6XEVHTXHQW�3URFHVVLQJ

8VH

With particular BW processes, you can trigger an event using subsequent processing following thesuccessful or incorrect work down of an event. The following processes are supported:

• Load data

• Compressing data

• Aggregating data

• Deleting requests

• Reconstructing InfoCubes

• Structuring statistics for an InfoCube

• Structuring an index for an InfoCube

• Deleting indexes

• Selective deletion of data

You can start subsequent processes on the basis of this kind of event. After the event has beenactivated, background controlling starts all processes that are waiting for this event. Use the6HOHFWLRQV�pushbutton in the maintenance dialogs in the supported processes to determine whether a(successor) process should react to an event that was determined in the subsequent processing of apredecessor process.

3UHUHTXLVLWHV

You must have already created the events that you want to use for controlling processes using 7RROV

→�&&06�→�-REV�→�0DLQWDLQ�HYHQW.

)XQFWLRQV

In the VXEVHTXHQW�SURFHVVLQJ for a process, you determine whether an event is triggered following thisprocess. Here you determine which successful or unsuccessful event is to be triggered if the processhas been completed successfully or incorrectly. You can schedule processes that are to be triggereddependent on a completed process in the background in the current maintenance dialog, waiting forsuch an event.

Besides triggering an event, you also have an additional option in the scheduler for subsequentprocessing.�A user exit in the form of a Business Add-In is also available to you. You fill it with usercoding.

In BW 3.0, automatic process control has been enhanced and improved significantly withthe concept of process chains. Process control using post-processing events and eventcollectors is not functionally enhanced but it is still supported. :H�UHFRPPHQG�WKDW�\RXRQO\�XVH�SURFHVV�FKDLQV�IRU�VFKHGXOHV�RI�FRQQHFWHG�SURFHVVHV�WKDW�PXVW�EH�UH�GHILQHG�



(YHQW�&ROOHFWRU

'HILQLWLRQ

An event collector is a quantity of several events that have been successfully completed independentlyof each other to which background processing should respond.

The event collector corresponds to the AND process and the process chain maintenance. If anapplication process is scheduled via an event collector, it starts when all events for the precedingprocess were successfully triggered.

In order to clarify the difference between a process chain and an event chain as AND-Collection Process [Seite 437] ,event chains were renamed as event collectors.

8VH

You can collect events for an event collector in the Administrator Workbench. If all the eventscontained in a chain have been activated and the chain has thus been successfully processed, then asuccessful event is triggered that has been previously determined in the subsequent processing of theevent collector.

You can trigger processes by activating this event. Event collectors are used to control processes inBW.

,QWHJUDWLRQ

Events triggered by event collectors can be used as a trigger for a process chain. Furthermore, it ispossible to combine event collectors with process chains by their own programming. Thus, it isgenerally possible to integrate event collectors in process chains.

In BW 3.0, automatic process control has been enhanced and improved significantly withthe concept of process chains. Process control using post-processing events and eventcollectors is not functionally enhanced but it is still supported. :H�UHFRPPHQG�WKDW�\RXRQO\�XVH�SURFHVV�FKDLQV�IRU�VFKHGXOHV�RI�FRQQHFWHG�SURFHVVHV�WKDW�PXVW�EH�UH�GHILQHG�



&UHDWLQJ�DQ�(YHQW�&ROOHFWRU

8VH

Event collectors are used to control processes in BW.

9RUDXVVHW]XQJHQ

You have determined the events that you want to use in an event collection and in the subsequentprocessing of the event collection under 7RROV�→�&&06�→�-REV�→�0DLQWDLQ�HYHQW.

3URFHGXUH

1. Select 7RROV�Å�(YHQW�&ROOHFWRU in the Administrator Workbench.

2. Enter a description for the event collection and select &UHDWH�HYHQW�FKDLQ.

3. Select the events that should form the event collector and determine whether an event should beconsidered as successful or incorrect. If necessary enter parameters for the events of the chain.

If you determine an event as ‘incorrect’ and this event is activated, then the unsuccessfulsubsequent processing event is triggered for the whole collector.

4. Enter a time frame in which an event collector must be successfully processed so that asuccessful event is triggered.

5. Select VXEVHTXHQW�SURFHVVLQJ and then an event for the successful case as well as an event forthe case where incorrect events have been triggered in the event collector.

6. Save the event collector

5HVXOW

The event collector is available to you for process controlling in BW.



6FKHGXOLQJ�WKH�(YHQW�&ROOHFWRU

3URFHGXUH

1. Select 7RROV�→�(YHQW�&ROOHFWRU in the Administrator Workbench.

2. Select an event collector.

3. To schedule the event collector, choose 6WDUW.

5HVXOW

The event collector is processed in the background.

A job is scheduled for every event in the chain. The job waits for the event and checks whether allother events in the chain were processed. The collector is successfully processed if all successfulevents contained in the collector are triggered, and no unsuccessful event was triggered. A successfulevent is then triggered that was previously determined in the Subsequent Processing [Seite 448]of theevent collector.

Make sure that there are enough background processes available because parallelprocesses run with event collector processing.

If an incorrect event was triggered in the collector, the unsuccessful event of the subsequentprocessing is also triggered for the collector, and the collection of events is restarted.

When you determine a time frame in which an event collector must be successfully processed, and thetime frame is exceeded, the collector ends and is restarted the next day at a fixed time.



(GLWLQJ�DQ�(YHQW�&ROOHFWRU

3UHUHTXLVLWHV

You have already created an event collector.

3URFHGXUH

1. Select 7RROV�→�(YHQW�&ROOHFWRU in the Administrator Workbench.

2. Select an event collector.

&KDQJLQJ�WKH�(YHQW�&ROOHFWRU

You can change any entry you made when you created the event collector.

If there is a certain event you no longer want to use in an event collector, select it and choose 5HPRYH(YHQW�IURP�&ROOHFWRU.

&RS\LQJ�DQ�(YHQW�&ROOHFWRU

If you want to use an existing event collector as the basis for a new event collector, copy the originalevent collector, give the copy a description, make any relevant changes to the collector and save it.



5HSRUWLQJ�$JHQW

'HILQLWLRQ

The Reporting Agent is a tool used to schedule reporting functions in the background.

The following functions are available:

• Evaluating exceptions

• Printing queries

• Pre-calculating Web templates

• Pre-calculating characteristic variables of type SUH�FDOFXODWHG�YDOXH�VHWV�

8VH

1. You make VHWWLQJV for the specified reporting functions.

2. You assign the individual settings to VFKHGXOLQJ�SDFNHWV for background processing.

3. You schedule the scheduling packet.

6WUXFWXUH

The Reporting Agent interface consists of two tree structures:

• The left-hand tree gives you an overview of the available objects as well as the settings that havealready been made. To give you a better overview, you can filter according to Queries withsettings in the ([FHSWLRQV�and 3ULQW functions.

• The right-hand tree gives you an overview of the scheduling package and manages thebackground processing.

6HH�DOVR�

Define Exceptions Setting [Seite 454] and Exception Reporting [Extern]

Defining the Print Setting [Seite 461]

Defining a Web Templates Setting [Seite 469]

Defining the Setting Value Set [Seite 475]



'HILQLQJ�([FHSWLRQV�6HWWLQJ

8VH

The Reporting Agent gives you the option of pre-calculating exceptions in the background. If anexception threshold value is exceeded or not reached, the system will trigger the follow-up action youhave selected. The following follow-up actions are available to inform one or more responsible peopleabout the variance:

• send a message

• Make an entry in the Alert Monitor

3UHUHTXLVLWHV

You have defined a query containing at least one exception in the BEx Analyzer.

You can find additional information under Define Exceptions [Extern].

3URFHGXUH

1. You are in the 5HSRUWLQJ�$JHQW� function area of the Administrator Workbench. Choose:RUNEHQFK�([FHSWLRQV in the navigation window of the Administrator Workbench.

2. Navigate to the required query in the left 5HSRUWLQJ�$JHQW�6FKHGXOHU�tree.

3. You have the following options to create a new setting:

− Using the context menu, choose 1HZ�3DFNDJH�

− Select &UHDWH�1HZ�6HWWLQJ.

The “1HZ�5HSRUWLQJ�$JHQW�6HWWLQJ” screen then appears. The names of the InfoProvider andthe selected query are already installed on the *HQHUDO tab strip.

To copy a setting, choose 0DLQWDLQ using the context menu for the setting. The 5HSRUWLQJ

$JHQW�6HWWLQJ screen then appears. Choose �&RS\ The “1HZ�5HSRUWLQJ�$JHQW�6HWWLQJ”screen then appears.

4. Enter a technical name and a description.

5. Set the characteristic for ([FHSWLRQ�5HSRUWLQJ�on the *HQHUDO�tab strip under the group heading6HWWLQJV�)RU�

6. The system adds Tab Strip: Exception Reporting [Seite 456].

D�� From the $YDLODEOH�2EMHFWV tree, choose the exception you want to process in the background,and, using drag-and-drop, assign it to the ([FHSWLRQV node in the 6HOHFWHG�2EMHFWV tree.

E�� Choose the interval or threshold value for this exception that you want to check in abackground run, and, using drag-and-drop, drag it to the right-hand tree under the exceptionyou chose.

F�� Assign a follow-up action to the intervals or the threshold value you have chosen. Either drag 6HQG�0HVVDJH�or $OHUW�0RQLWRU�(QWU\ with drag-and-drop under the corresponding

interval.

By double clicking on the assigned follow-up action, you reach the 3URSHUWLHV screen area.Change the settings that are available for the selected follow-up action type.

You can find more information under:

Edit Follow-Up Action: Send Message [Seite 457]

Edit Follow-Up Action: Alert Monitor Entry [Seite 460]



G�� From the $YDLODEOH�2EMHFWV tree, choose the exceptions you want to process in thebackground, and, using drag-and-drop, assign them to the 'ULOOGRZQ�&KDUDFWHULVWLFV node inthe 6HOHFWHG�2EMHFWV tree.

Note that the way the characteristics are arranged is important here, since an exceptionalways occurs in a particular cell context.

�� Choose $FWLYDWH�

5HVXOW

Once you have defined the Reporting Agent settings, you have to assign them to a schedulingpackage for the background run.

For more information see Editing Scheduling Package [Seite 476].



7DEVWULS��([FHSWLRQ�5HSRUWLQJ

'HILQLWLRQ

The ([FHSWLRQ�5HSRUWLQJ tabstrip on the 1HZ�5HSRUWLQJ�$JHQW�6HWWLQJ screen displays all objects thathave been selected and are available for background processing.

8VH

On the ([FHSWLRQ�5HSRUWLQJ� tabstrip, you can select exceptions, follow up actions and characteristics,which are to be added to background processing.

6WUXFWXUH

The ([FHSWLRQ�5HSRUWLQJ tabstrip consists of the $YDLODEOH�2EMHFWV and the 6HOHFWHG�2EMHFWV treestructures, with the following functions:

7UHH�6WUXFWXUH :KDW�\RX�QHHG�WR�NQRZ

Available objects The objects you choose for background processingare displayed here.

Exceptions Displayed are:

([FHSWLRQV�of the selected query.

The intervals belonging to the query are alsolisted, along with threshold values and theirnotification priorities.

Follow-up actions You can select:

send a message

The recipient is informed by mail of thenumber of exceptions that have been found.

Make an entry in the Alert Monitor

The exceptions that are found are logged ina table (exception log), and displayed in theMonitor. The recordings are bundledtogether in the form of simple drilldowns(views)

You can find additional information underException Display: Alert Monitor [Extern].

Characteristics Displayed are:

Characteristics of the selected query.

It does not matter whether thesecharacteristics have been moved to an axis,or have been defined as free characteristics,in the query definition.

Selected Objects The objects you select for background processingare collected here.



(GLW�)ROORZ�8S�$FWLRQ��6HQG�0HVVDJH

8VH

In order to notify one or more people responsible by using a mail when a threshold value for anexception is not reached, you can edit the properties of the follow-up action 6HQG�0HVVDJH in thetabstrip ([FHSWLRQ�5HSRUWLQJ.

3UHUHTXLVLWHV

You have already selected an exception and assigned it the follow-up action 6HQG�0HVVDJH.

You can find additional information under Defining the Exceptions Settings [Seite 454].

3URFHGXUH

Double clicking on the assigned follow-up action shows the 3URSHUWLHV screen area. The functionsdescribed further below enable you to do the following:

• create the document contents

• determine one or more recipients of the message in which you specify either SAP or externaladdresses

&UHDWH�'RFXPHQW�&RQWHQWV�DQG�,QVHUW�$WWDFKPHQWV

1. Choose (GLW�'RFXPHQW. You arrive at the screen &KDQJH�'RFXPHQW.

2. Enter a title.

3. Enter a text for the tabstrip 'RFXPHQW�&RQWHQWV. At the time of the send, the system appends thereporting agent event for this message.

In addition to the usual functions for editing text, the following functions are available:

By using /RDG�/RFDO�)LOH�you can insert the contents of a file.

By using 6DYH�DV�/RFDO�)LOH�you can save your message locally.

4. By using &UHDWH�$WWDFKPHQW you arrive at the dialog box 2SHQ. Choose the file that you want toadd as an attachment. In the screen &KDQJH�'RFXPHQW the system adds the tabstrip $WWDFKPHQWV.

If attachments, in which you choose $WWDFKPHQWV in the screen area 3URSHUWLHV for thetabstrip ([FHSWLRQ�5HSRUWLQJ, have already been created for a message, you can displaythem. You get to the 'RFXPHQW screen. The attachments are run in the lower screen areafrom the tabstrip 'RFXPHQW�&RQWHQWV. You can edit attachments from the tabstrip$WWDFKPHQWV. In order to get to the change view, choose &KDQJH�

5. Choose the tabstrip $WWDFKPHQWV.

The attachments with the following properties are run from the tabstrip $WWDFKPHQWV:

7\SH 'HVFULSWLRQ 6L]H 7\SH

Symbol for Labeling theFile Type

Document Title File Name Extension(MIME [Extern]Type)

The following functions for editing are available:

$SSOLFDWLRQ )XQFWLRQ :KDW�\RX�QHHG�WR�NQRZ

Add attachment Choose ,PSRUW�$WWDFKPHQW

or &UHDWH�$WWDFKPHQW.

You get to the 2SHQ dialog box.Choose the file that you want toadd as an attachment.

Save attachment locally Choose ([SRUW�$WWDFKPHQW. You arrive at the dialog box



6DYH�DV.

Edit attachment Choose &KDQJH�$WWDFKPHQW� The document is opened withthe respective PC application ina separate window.

Save and close the document inthe PC application. Save thedocument afterwards in the SAPsystem.

Choose 6WRUH�$WWDFKPHQW.

Choose &UHDWH�/LQN�IRU$WWDFKPHQW.

You can find additionalinformation in thedocumentation for SAPBusiness Workplace underAttachments to a Document[Extern] and Appending anAttachment to a Document[Extern].

Delete one or more attachments Select the respective entries inthe list of attachments. Choose

'HOHWH.

Confirm with the confirmationprompt.

6HOHFW�0HVVDJH�5HFLSLHQW

Each recipient has a message for the selected reporting agent setting.

Select the recipient type and the individual recipients:

7\SH�RI�UHFLSLHQW 3URFHGXUH

Role Choose 5ROHV. You get to the 5ROHV dialogbox.

Select and transfer the roles you want into theleft-hand area of the screen. Choose &RQWLQXH.

Result: The message is sent to everyoneassigned to the role that you specified.

Individual recipients Choose 5HFLSLHQW�/LVW. You arrive at thescreen 6HQG�ZLWK�1RWH.

If you want, you can enter in the upper area of thescreen a title and note for the recipient(s).

Enter a recipient in the lower area of the screenon the tabstrip 5HFLSLHQW.

In most cases, the system supplementsthe recipient type. The following recipienttypes might be of interest:

− Internet address

− SAP logon name

If you use SAP Business Workplace,additional recipient types are available(see Address Type [Extern]).

As a user of the SAP Business Workplace, youhave additional setting options for the send[Extern]:

You can decide whether you want themessage to be sent in one of thefollowing ways:



([SUHVV�PDLO

Send as a copy

Send as a blind copy

For more information, see SendAttributes [Extern].

If you have entered at least one recipient,you can use to create a distribution list[Extern]. (See also Creating a DistributionList [Extern].) Afterwards, your personaldistribution list [Extern] is available forselection by using the input help for thefield 5HFLSLHQW.

If you have inserted a distribution list intothe recipient list, and you want to deleteone in the individual recipient addresses,select the entry and choose �'HOHWH(QWU\.

You can find additional information underEditing a Distribution List [Extern].

By using 6XEPLWWHG�$JDLQ�WR�WKH5HFLSLHQW��you arrive at the dialog box&UHDWH�5HVXEPLVVLRQ�IRU�� You can findadditional information under Resubmittinga Document [Extern] and Creating aResubmission [Extern].

Use the tabstrip 6HQGHU�2SWLRQV tochoose your settings in the areas

• *HQHUDO�$WWULEXWHV

• Send Status

For more information, see DistributionList and Send Information [Extern].

If you send the message to a user of the SAP Business Workplace, it is placed in the SAPOffice Inbox. You can find more information under SAPconnect [Extern].

Otherwise, the message arrives in the mailbox of the respective mailing client.



(GLWLQJ�WKH�)ROORZ�8S�$FWLRQ��$OHUW�0RQLWRU�(QWU\

8VH

To inform one or more interested parties that an exception, whose threshold values have beenexceeded, has been logged in the exception log and can be displayed in the Alert Monitor [Extern], onthe ([FHSWLRQ�5HSRUWLQJ�tabstrip, select the alert recipient.

3UHUHTXLVLWHV

You have already selected an exception and assigned it to the follow-up action $OHUW�0RQLWRU�(QWU\�.

For further information, see Defining the Exceptions Setting [Seite 454] and Tabstrip: ExceptionReporting [Seite 456].

3URFHGXUH

By double clicking on the assigned follow-up action, you reach the 3URSHUWLHV screen area.

Select the recipient of the alert:

7\SH�RI�UHFLSLHQW 3URFHGXUH 5HVXOW

All SAP users Set the indicator for $OO�6$38VHUV

The Alert Monitor entry isdisplayed for all SAP users.

Assigned users of a role Choose 5ROHV� You get tothe 6HOHFW�5ROHV�dialog box.

Select and transfer the rolesthat you want to use into theleft-hand area of the screen.Choose &RQWLQXH�

The Alert Monitor entry isdisplayed for everyone assignedto the role that you specified.

Individual SAP users Choose 5HFLSLHQW�/LVW� Youget to the 6HOHFW�5HFLSLHQWdialog box.

Select and transfer the requiredSAP users into the left-handarea of the screen. Choose &RQWLQXH�

The Alert Monitor entry isdisplayed for the selectedrecipient.



'HILQLQJ�WKH�3ULQW�6HWWLQJ

8VH

You can not only evaluate a query online, but also print it in the background.

The Reporting Agent gives you the option to display the query data as a Report Agent setting forprinting in the background You can set as many Report Agent settings as you want for a query.

3UHUHTXLVLWHV

You have defined a query in the Business Explorer Analyzer that you now want to print in thebackground.

To print, key figures related to the query must be in the structures. Change the Querydefinition appropriately if you want to print a query that uses a key figure as a filter.

You can only schedule queries with entered variables for background printing if therequired variable entry/entries have been saved as query variants [Extern]

3URFHGXUH

1. You are in the 5HSRUWLQJ�$JHQW� function area of the Administrator Workbench. Choose 3ULQW�LQ%DFNJURXQG in the navigation window of the Administrator Workbench.

2. Navigate to the required query in the left 5HSRUWLQJ�$JHQW�6FKHGXOHU�tree.




The “1HZ�5HSRUWLQJ�$JHQW�6HWWLQJ” screen then appears. The names of the InfoProvider andthe selected query are already installed on the *HQHUDO tab strip.


5. Set the characteristic for 3ULQW�LQ�%DFNJURXQG�on the *HQHUDO�tab strip under the group heading6HWWLQJV�)RU� The system adds the 3ULQW�6HWWLQJV�DQG�3ULQW�/D\RXW�tab strips.

6. Choose the 3ULQW�6HWWLQJV�tabstrip. Define the print settings that you want to make. You can findadditional information under Tab Page: Print Settings [Seite 463].

�� Choose the 3ULQW�/D\RXW tab strip. Decide how you want to set the following print areas:

− Cover sheet

− Page header

− Table header

− Table

− Page footer

− Last page

You can find additional information under Tab Page:Print Settings [Seite 465].

8. Choose $FWLYDWH�

5HVXOW





7DEVWULS��3ULQW�6HWWLQJV

'HILQLWLRQ

The 3ULQW�6HWWLQJV�tab strip on the 1HZ�5HSRUWLQJ�$JHQW�6HWWLQJV screen displays all objects that areavailable for the print layout and the corresponding print areas.

8VH

If you want to print a query in the background, and have created a new Reporting Agent setting to dothis, determine how the query is displayed on the 3ULQW�6HWWLQJV tabstrip. .

6WUXFWXUH

3ULQW�6HWWLQJV :KDW�\RX�QHHG�WR�NQRZ

Title The system adopts the description that you enteredfor the new Reporting Agent setting.

You can enter a new title when you want todistinguish between several print outs for the samequery.

Suppressing repeated texts When you set this indicator, identical characteristicvalues are printed once, and not repeated in everyrow.

Suppressing zeros When you set the indicator, cells containing a zerovalue (0.00) are left empty. When all cells in a rowhave a zero value, this row is not printed.

Using colors When you set this indicator, all ABAP listed colorsare used.

Do not print lines When you set this indicator, the query is printedwithout lines.

Currencies/units position The following display options for currencies and unitsare possible:

• Left (of the amount)

• Right (of the amount)

• No Display

+/- position The following positions are possible:

• before the value -123.45

• after the value 123.45-

• in parentheses (123.45)

The default setting is EHIRUH�WKH�YDOXH��

Result position The following result positions are possible:

• bottom/right

• top/left

Pages You specify here the number of rows and columnsyou want each page to have under the 3DJHV�groupheader.

You can set the 0D[LPXP�3DJH�1XPEHU�for the printout to avoid printing a lot of pages unnecessarily ifyou accidentally choose the wrong print settings.When you do not want to restrict the number ofpages that are printed, enter a � here.



Page margins You can specify the required width of the marginsunder the 3DJH�0DUJLQV�group header.

• The upper and the lower margin conformto rows.

• The left and the right margin conform tocharacters.

Print format With large numbers of columns, it is not possible toprint all the columns on one page. The columns aretherefore printed on several pages. You are able tospecify the order in which the pages are printed –horizontally or vertically.��

�

�

�

�

�

�

�

�

� �

�

�

�

�

�

�

�� ! �"�#�$��%�"�

We recommend horizontal printing for performancereasons since the print data is only read once.

,QWHJUDWLRQ

When you have made the print settings you want to use, choose the tabstrip 3ULQW�/D\RXW. Here, youdetermine which characteristics and key figures you want to use in the print output, and how you wantthem to be displayed.

6HH�DOVR�

Defining the Print Layout [Seite 465]



'HILQLQJ�WKH�3ULQW�/D\RXW

8VH

On the 3ULQW�/D\RXW tab strip, you can determine how the InfoObjects in the query are displayed on theprint-out.

The 3ULQW�/D\RXW tabstrip consists of the following areas:

$YDLODEOH�REMHFWV 3ULQW�DUHDV

All Query InfoObjects are displayed:

Key Figures

Characteristics

The following areas are displayed for you to model:

• Cover sheet

• Page header

• Table header

• Table

• Page footer

• Last page

'HILQLQJ�WKH�OD\RXW�RI�FRYHU�VKHHWV��ILQDO�SDJHV��SDJH�KHDGHUV��DQGSDJH�IRRWHUV�

1. Choose the print area you want to use.

2. A double-click takes you to the Editor. Here, you determine how you want to set-up your chosenprint area:

− Enter text

− insert margins or separators

− insert variables of the query

The variables are subdivided into:

− General text variables (text elements of the query and print details such as date of printing orpage number)

− Special variables (attributes)

− Characteristics

− Selection parameters (variables and filter values)

Depending on what settings you made in the query definition, you may not be able to useof all types of text variables.


No headers or footers are printed on the cover sheet and the final page.

If you do not make any settings for headers and footers, the print title, the date, and thetime of printing, are printed in the header by default. The page number appears in thefooter.

If you want to print a header or footer, delete all the rows from the header or footer. Saveyour entries.

'HWHUPLQLQJ�KRZ�,QIR2EMHFWV�DUH�GLVSOD\HG

Query InfoObjects are displayed in the table by default. The key figures appear in the columns, andthe characteristics appear in the rows of the table.



You can determine how each of the individual InfoObjects are displayed:

1. Choose the 7DEOH�node as print area.

2. Choose 'LVSOD\��!�&KDQJH from the toolbar.

3. You can:

− arrange the InfoObjects into the sequence you want using drag-and-drop.

− drag the InfoObjects that you do not want to display in the drilldown, that is in the table, to theleft-hand side of the screen, and drop them under $YDLODEOH�2EMHFWV�

− drag characteristics into the cover sheet, page header, or table header areas. If thecharacteristic value changes, a new cover sheet, and a new page header or table header, arecreated.

You can make additional settings for every InfoObject:

1. Choose the InfoObject required. Choose using the context menu 3URSHUWLHV� Selection fields forthis InfoObject are shown on the right-hand side of the screen.

You can also get to the selection fields by double-clicking on the InfoObject.

2. Define the settings that you want to make. There are different options for characteristics and keyfigures:

&KDUDFWHULVWLFV

7$%675,3�',63/$< 0HDQLQJ

Layout The following options are available:

• 1R�GLVSOD\

• Key and text (default setting)

• WH[W

• .H\

• 7H[W�DQG�NH\

• /RQJ�WH[W

• 0HGLXP�WH[W

Automatic column width This function is switched on by default. Automatic column widthis set at max. 60 characters for titles, and max.32 characters forkeys.

If you switch this function off, the field &ROXPQZLGWK that is filled manually, appears in the field&ROXPQ�� (or &ROXPQ��).

We recommend

− that you choose the automatic column width functionfor keys

− that, with characteristics with hierarchies, enter acolumn width manually.



Totals row The following options are available:

• 'R�QRW�VXSSUHVV�WRWDOV (default setting)

• Suppress (un-)conditional totals

• 6XSSUHVV�FRQGLWLRQDO�WRWDOV��If there is only onecharacteristic value for a characteristic, then no totalsappear. This would only repeat the characteristic value.

Column 1 The name of the key figure appears by default as the title. Youcan also enter another title.

You can choose between the following settings:

• $OLJQ�OHIW

• &HQWHU

• $OLJQ�ULJKW

If you want the column to be printed on more than just the firstpage of the query, choose RQ�HYHU\�SDJH.

Column 2 If you selected both options for display, that is .H\�and 7H[W,there are actually two columns within the column for thecharacteristic. So for the second display option, you canchoose:

• the alignment, and

• the RQ�HYHU\�SDJH function.

7$%675,3�+,(5$5&+< 0HDQLQJ

Active hierarchy If you choose DFWLYH�KLHUDUFK\, the characteristic values aredrilled down by hierarchy (indicated by *). Otherwise, they aredisplayed as a list.

Hierarchy Select the hierarchy you want to use.

Version Choose the version of the hierarchy you want to use (if it isavailable).

Key date Choose the key date for the hierarchy that you want to use (ifyou are working with a time-dependent hierarchy).

Level Specify the drilldown level that you want to use.

$WWULEXWHV

If a characteristic has attributes, then you can choose them for the print-out as described underFKDUDFWHULVWLFV and display them.

You can select as many attributes as you want for the print characteristics you chose. However, thenumber of attributes should not be too large, so that data columns can still fit on the page.

If you select too many columns to be printed on every page, it can mean that there is no room for adata column on the page. The query can then no longer be printed.

Whether the first column with the characteristics and attributes is too wide for the print-out, dependson:

• the number of columns on each page

• the column width of the individual columns

• the page width set up over the page margins



If you want to display the attributes of the characteristic but not the characteristic itself inthe print-out, select the characteristic as a printing characteristic and select .H\ as thedisplay and � as the column width. The characteristic is then a printing characteristic, butis not displayed in the printed query.

.H\�)LJXUHV

7$%675,3�',63/$< 0HDQLQJ

Automatic column width see FKDUDFWHULVWLFV above.

column on new page If you select FROXPQ�RQ�QHZ�SDJH, a page break isinserted and the key figure appears on a new page.

Column 1 see FKDUDFWHULVWLFV above.



'HILQLQJ�D�:HE�7HPSODWHV�6HWWLQJ

8VH

The Reporting Agent gives you the option to pre-calculate Web templates, that is HTML documentswith BW specific place holders, in the background. If you call up a Web Report that is constructed onthe basis of a pre-calculated Web Template in the Web Browser, you can access pre-calculated datawithout having to execute an OLAP query. This means that access time is considerably reduced andstrain on the application server is relieved.

However, please note that the pre-calculated Web Templates are static and do not allow OLAPnavigation.

3UHUHTXLVLWHV

• You have defined a Web template.

You can find more information under:

Web Templates [Extern]

Creating Web Applications with the BEx Web Application Designer [Extern]

• You have created a control query if necessary.

You can find further information under Control Query for Web Template-Pre-Calculation [Seite474].

3URFHGXUH

1. You are in the 5HSRUWLQJ�$JHQW� function area of the Administrator Workbench. Choose :HEWHPSODWHV in the navigation window of the Administrator Workbench. You can see available rolesas well as the workbooks and Web templates assigned to them in the left-hand 5HSRUWLQJ�$JHQW6FKHGXOHU�tree.

2. Navigate to the required Web Template.




The “1HZ�5HSRUWLQJ�$JHQW�6HWWLQJ” dialog box then appears.


5. You are on the 3DUDPHWHU�tab strip. The Web Template and its ID (the technical name) isdisplayed as general parameters.

Select from the &DOFXODWLQJ�group header what the system is to pre-calculate.

3UH�FDOFXODWH ,QIRUPDWLRQ

Data Accessing pre-calculated data leads to a markedimprovement in performance: The data is nolonger requested from the OLAP processor, andonly the HTML pages must be generated.

We particularly recommend when having complexqueries with

• complex selection criteria

• TopN conditions

• calculated indicators

that you pre-calculate the data.



HTML pages:

• HTML for Web Browsers

• HTML for Pocket IEs

The Reporting Agent supports various deviceclasses. You can pre-calculate HTML documentsfor Web Browsers and mobile devices.

When managing the HTML(+\SHU7H[W�7UDQVIHU3URWRFRO)-Documents and the MIME(0XOWLSXUSRVH,QWHUQHW�0DLO�([WHQVLRQV) objects that belong tothem, the BW uses the SAP Document andContent Management Service (ContentManagement Framework).

Excel

You can also select several options.

6. You have the option to determine additional parameters under the 3DUDPHWHUL]DWLRQ�group header.

3DUDPHWHU ,QIRUPDWLRQ

Control Query If you want to use a query as a control query, enter the query name or select the queryusing the value help.

(If you GR�QRW specify a control query, the Web template is pre-calculatedwithout further parameterization.)

Variant If the control query contains entry-ready mandatory variables, you need to assign avariant.

Language Choose the language(s), for which you want to calculate the data.

&DOFXODWH�GDWD�IRU�DOO�LQVWDOOHG�ODQJXDJHV�

2QO\�FDOFXODWH�GDWD�IRU�ORJRQ�ODQJXDJH�

Variable pre-assignment

To pre-assign variables, you can enter strings in URL syntax in the 3DUDPHWHU�6WULQJtable in the lower screen area.

You must attach the following sequence, for example, to theURL:&var_name_1=myInVar&Var_value_low_ext_1=LowVal&var_value_high_ext_1=HighVal.

Further information is available under Pre-assigning Variables for WebReports [Extern].

In the 9DULDEOH�5HFRUG�field determine the sequence in which the strings are to beprocessed.

A variable record is analogous to a query variant. For each variable record,the system evaluates the template and creates an HTML file or a datarecord in the data storage.

If the URL is longer than the table field provided, you can continue writing the string onthe next row in the table. In the 1U��field, specify an index of those rows belonging to avariable record.

Rows 1 – 4 belong to the parameter string of a YDULDEOH�UHFRUG��: Theparameter string;



begins with: …&var_name_1=myIntVar in row nr. 1

continues with: &var_value_low_ext_1 in row nr. 2

continues with: =LowVal&var_value_high in row nr. 3

closes with: _ext_1=HighVal in row nr. 4.

In the following rows, a YDULDEOH�UHFRUG��begins as row number 1 with anew parameter string.

7. Select the 3UHYLHZ�tab strip.

− When you use a control query and want to have this displayed, set the &RQWURO�4XHU\�indicatorand choose 'LVSOD\�

− When you want to display a Web template, set the 7HPSODWH�indicator and choose 'LVSOD\�

A preview window is shown in the right-hand screen area of the tab strip.

8. Save your setting.

9. Choose $FWLYDWH�

5HVXOW



Once the background run has finished, HTML pages, EXCEL files, and the pre-calculated data for theWeb template is available for you to use.

Further information about accessing pre-calculated data or HTML pages when calling upWeb templates can be found under Parameter DATA_MODE [Seite 472].

You can also access pre-calculated HTML pages via Web folder.

You can store pre-calculated HTML pages locally using the document storage WebDAVService [Extern] in the content management framework. This is a simple procedure.(Restricted) offline reporting is thus possible.

You can find further information about the WebDAV service under Using External Tools[Extern] .

See also:

WebDAV [Extern](:RUOG�:LGH�:HE�'LVWULEXWHG�$XWKRULQJ�DQG�9HUVLRQLQJ)



3DUDPHWHU�'$7$B02'(

'HILQLWLRQ

The optional parameter DATA_MODE determines the data mode when Web templates are called up:This parameter mode determines whether the system is to access HTML pages or data pre-calculatedin the background. If the parameter is QRW specified, requests are always sent to the OLAP processorand the latest data is read.

8VH

To call up a Web template with a particular data mode, enhance the URL generated by the BEx WebApplication Designer with the parameter DATA_MODE. Next, assign the required value to it.

http://your AppServer:yourPort/SAP/BW/Bex?

CMD=LDOC&TEMPLATE_ID=yourTemplate'$7$B02'( 6725('

You can find additional information under Call Up a Web Template [Extern] and Call UpParameterized Web Templates [Extern].

6WUXFWXUH

'DWD�PRGH ,QIRUPDWLRQ

DATA_MODE=NEW When you add the parameter DATA_MODE=NEWto the URL, the system uses the latest data.

The system does the same thing when theparameter is not set.

DATA_MODE=STORED When you add the parameterDATA_MODE=STORED to the URL, the systemonly accesses pre-calculated data.

An error message is displayed, if no data exists.

Note that you must pre-assign thevariables in STORED mode via the URL.If you use a query with variables, youmust add the very same string that youalso used as parameter string with theReporting Agent Setting to the URL.

To do this, you can write a small cockpitapplication, in which you combine theURL with the help of a HTML-<form> tagor a Java Script function from theselection list entry values.

You can find additional informationunder Using Formulas [Extern] andUsing JavaScript Functions [Extern].

Selection lists can be filled from acontrol query.

Also refer to: Control Query For WebTemplate Precalculation [Seite 474]



DATA_MODE= HYBRID When you add the parameterDATA_MODE=HYBRID to the URL, the system willuse pre-calculated data as long as it is available forthe corresponding Data Provider.

If there isn’t any pre-calculated data, the systemrequests data from the OLAP processor as in theNEW mode.

DATA_MODE=STATIC When you add the parameterDATA_MODE=STATIC to the URL, the system onlyaccesses pre-calculated HTML pages.

An error message is displayed if no data exists.

DATA_MODE=STATIC_HYBRID When you add the parameterDATA_MODE=STATIC_HYBRID to the URL, thesystem uses pre-calculated HTML pages as long asthey are available for the corresponding DataProvider.

If no pre-calculated HTML pages exist, the systemwill search for pre-calculated data as in the STOREDmode.

If again there isn’t any pre-calculated data, thesystem requests data from the OLAP processor as inthe NEW mode.



&RQWURO�4XHU\�IRU�3UH�FDOFXODWLQJ�:HE�7HPSODWHV

'HILQLWLRQ

The control query is a help query that you execute before you execute the queries in the Webtemplate. You use the result to parameterize the Web template.

8VH

You can specify a control query as important information in the Reporting Agent Settings for a WebTemplate. When you specify a control query, the system does not pre-calculate the Web templateitself, but a number of filtered views from the Web template.

We particularly recommend this procedure when you want to calculate several Web templates thatonly distinguished by their filter values in one go.

Using a control query particularly allows you to formulate complex selection criteria for the data to bepre-calculated.

Example: Pre-calculate only the TOP50 customers whose data is frequently requested.

6WUXFWXUH

A very basic query is particularly suitable as a control query. It contains exactly those characteristics inthe drilldown in the rows according to which the Web template is filtered. Every row in the tabledelivered by a control query, subsequently serves as a dynamic filter for the Web template views.

The respective combination of characteristic values is used as a filter for the Webtemplate Data Provider [Extern] for each table row. The background run produces pre-calculated data records, actually one data record for each table row that delivers a controlquery.

If a characteristic does not appear in a view, the filter value is ignored.

In addition, you automatically get only those filter value combinations, for which data exists in theInfoCube that was used to define the control query.

([DPSOH

A typical application for this approach of pre-calculating a Web template is found in cockpitapplications, since they are mainly controlled through selection lists and real OLAP navigation is notnecessary.



'HILQLQJ�WKH�9DOXH�6HW�6HWWLQJ

8VH

The Reporting Agent enables you to fill SUH�FDOFXODWHG�YDOXH�VHW�variables with values for characteristicvalues in the background. Further to this, the pre-calculated value sets are available as variablevalues in BEx queries.

The following cases are typical applications of the execution of pre-calculated value sets:

• when analyzing target groups since you can specify a fixed value.

• when complex selections are involved such as with a TopN inquiry, used to strongly improvequery performance.

• in place of variables that are filled from a query event ( Replacement from a query event).

3UHUHTXLVLWHV

The query must contain the characteristic that is the placeholder for the variables.

3URFHGXUH

1. You are in the 5HSRUWLQJ�$JHQW� function area of the Administrator Workbench. Choose 9DOXH6HWV in the navigation window of the Administrator Workbench.

2. You can see the available characteristics as well as the Report Agent settings that areassigned to them. You have the following options for creating a new setting:

− Select the required characteristic and choose 1HZ�6HWWLQJV�using the context menu. The “1HZ5HSRUWLQJ�$JHQW�6HWWLQJ” dialog box then appears. The name of the selected characteristic isalready pre-installed on the 3DUDPHWHU�tab page under the *HQHUDO�group heading.

− Select &UHDWH�1HZ�6HWWLQJ. The “1HZ�5HSRUWLQJ�$JHQW�6HWWLQJ” dialog box then appears.Enter the name of the characteristic for which you want to create the variables. You do this onthe 3DUDPHWHU tab page under the group-heading *HQHUDO�

3. Specify a technical name and a description for the Reporting Agent setting.

4. You only need to enter one parameter on the 3DUDPHWHU�tab page: the query, whose result is to besaved as a pre-calculated value set.� The input help function is available.

5. Save active . The system returns the value set and the table as a result under the *HQHUDWHG9DOXH�6HWV�group heading

A value set pre-calculated in the background exactly corresponds to a data bank table anddisplays the 3UH�FDOFXODWHG�9DOXH�6HW�variable value for the selected characteristic.

5HVXOW

After you have defined the Reporting Agent setting, you must assign this to a scheduling package andschedule the package as a job.


The pre-calculated value set appears in the query definition as a variable that has already been filledwith data for the selected characteristic. This results from the background run.



3URFHVVLQJ�WKH�6FKHGXOLQJ�3DFNDJH

8VH


You can combine several Reporting Agents in one scheduling package. These settings are pre-calculated in a single job later.

The procedure consists of the following steps:

1. Create a new scheduling package as long as you have not created one before or if you do notwant to use an existing scheduling package.

2. Assign Reporting Agent settings

3. Schedule a package as a Job

The procedure is completely the same for all function areas for the Reporting Agent settings. Specialfeatures in the individual function areas will be referred to later.

3UHUHTXLVLWHV

You have defined and actively saved one or more Reporting Agent settings.

&UHDWLQJ�D�6FKHGXOLQJ�3DFNDJH

You are on the $GPLQLVWUDWRU�:RUNEHQFK��5HSRUWLQJ�$JHQW�screen in the same function area in whichyou defined your Reporting Agent settings.

1. Select &KDQJH�in the right-hand 6FKHGXOLQJ�3DFNDJH tree in the Reporting Agent scheduler.


− Select a node , and select &UHDWH�1HZ�3DFNDJH�using the context menu.

− Select &UHDWH�1HZ�3DFNDJH.

The &UHDWH�6FKHGXOLQJ�3DFNDJH dialog box then appears.


If the Reporting Agent setting comes from the print function area, you can decide whetherthe print parameter for printing in the background should be a part of the schedulingpackage or not.

The indicator 1R�3ULQW�3DUDPHWHU�is not set by default: The print parameters are part of thescheduling package and must be specified for it. As Reporting Agent scheduling packagesare transport objects, every time you change the printing parameters you need to create atransport request.

If you set the 1R�3ULQWLQJ�3DUDPHWHUV�LQGLFDWRU��the printing parameters are QRW�part of thescheduling package: They need to be entered when scheduling. If you change the printingparameters, you do not need to change the scheduling package.

If you want to set or to remove the 1R�3ULQW�3DUDPHWHUV� indicator for a schedulingpackage that has already been created, select &KDQJH��and also 5HQDPH�via thecontext menu for the respective scheduling package. The &KDLQ�6FKHGXOLQJ�3DFNDJHdialog box appears. Change the setting that you want to change.

To display or maintain the print parameters, you can select a scheduling package usingthe context menu:

• in the &KDQJH��'LVSOD\�3ULQW�3DUDPHWHUV�view.

• in the &KDQJH��0DLQWDLQ�3ULQW�3DUDPHWHUV�view.




$VVLJQLQJ�5HSRUWLQJ�$JHQW�6HWWLQJV

1. Select the setting that you want to schedule in the left 5HSRUWLQJ�$JHQW�6HWWLQJV�tree in theReporting Agent Scheduler.

2. Use drag and drop to assign the setting to the corresponding scheduling package in the right-handtree.

If the selected Reporting Agent setting from the ([FHSWLRQV�or 3ULQW�function areas relatesto a query with variables, you must select a YDULDQW of the query so that the schedulingpackage can be scheduled.

i. You are in the view &KDQJH�in the right-hand tree of the Reporting Agent Scheduler.From the scheduling package context menu, choose $VVLJQ�9DULDQWV The 9DULDQW�&DWDORJ.dialog window appears.

ii. Select the variant you want and choose 6HOHFW� The system adds the selected variantsin the right tree in the Reporting Agent Scheduler in the 9DULDQW�column.

iii. If you want to create a new variant for the required query or if you want to change variantsalready created, you have the option to process the variants in both the left and right-handtree in the 5HSRUWLQJ�$JHQW�6FKHGXOHU�

iv. Select 0DLQWDLQ�9DULDQWV�via the context menu of the Reporting Agent setting. You the seea screen on which you can process the variants for the selected query ( &UHDWH��

'LVSOD\�� &KDQJH).

v. Select the required variants as described above.

vi. Choose 1H[W.

6FKHGXOH�D�SDFNDJH�DV�D�-RE

1. In the right-hand tree of the Reporting Agent Scheduler, select the scheduling packet you want touse.

2. Choose using the context menu 6FKHGXOH� The &KDQJH�-RE�5$��QDPH�RI�WKH�VFKHGXOLQJ�SDFNHW�screen then appears

3. Specify the execution target.

4. Via 6WDUW�&RQGLWLRQ on the &KDQJH�-RE�5$�VFKHGXOLQJ�SDFNDJH�QDPH��screen, you get to the6WDUW�7LPH�dialog window. Enter the data that the system asks you for.

If you want the system to execute the job periodically, set the indicator to ([HFXWH�-RE3HULRGLFDOO\ and specify the repetition period for the job via 3HULRG�9DOXHV.

You can limit the factory or annual calendar start time via 5HVWULFWLRQV.

You can only execute a scheduled job after releasing it. Users need the correspondingauthorizations for the background run in order to do this.

You can find additional information in the documentation for the Computing CenterManagement System under Schedule Background Jobs [Extern].

The following functions are available in the right-hand screen area in the Reporting Agent Scheduler:


-RE�2YHUYLHZ You get to the $OSKDEHWLFDO�-RE�2YHUYLHZ�screen.Listed are the status of the scheduled jobs:

• planned



• released

• ready

• active

• finished

• cancelled

3URFHVV�2YHUYLHZ The 6$3�6HUYHU�screen then appears.

You can you find out about the current processesand possible execution targets here.

In the ([FHSWLRQV�function area:

$OHUW�0RQLWRU�3UHYLHZ�

The entries in the Alert Monitor are displayed.

You reach the default view using 6FKHGXOLQJ3DFNDJH�

in the :HE�7HPSODWHV�function area.

'RFXPHQW�2YHUYLHZ

The 'RFXPHQW�2YHUYLHZ�screen displaying thepre-calculated BW Web Reporting HTMLdocuments appears.

The tree structure is constructed as follows:

There is an index for each 6FKHGXOLQJ�3DFNDJH�

In this index, the background run MREV�that havejust been executed are displayed in individualindexes in turn.

In each job index, there is an individual index foreach device class that includes Web templatesgenerated and saved as HTML pages duringbackground processing.

• 3,(�for the device class Pocket IE.

Each PIE index contains a 'RFXPHQWVindex with the calculated HTML pages.

• :::�for the Web Browser device class.

Each WWW index contains an index foreach 6HWWLQJ.

Under which there are the followingindexes:

• 'RFXPHQWV�with the calculated HTMLpages.

• ,FRQV�with links that lead to thesymbols,

• -DYD�6FULSW�with the files that may berequired to fill the selection lists,

• 6W\OH�6KHHWV�with links that lead tothe style sheets,

The respective document links are in theindex file for all filter values and variables.



'RFXPHQWV

8VH

With BW objects, you can add, link to, and search through one or more documents in various formats,versions, and languages.

,QWHJUDWLRQ

An overview of the components

�� ! "�#�$�� %'&()�*��,+�"-.��"�#�(�

%'��/��+�+ �.�� 0+12+(�*��3��% ��4 �#��/�5�#�(�

� %�67��8 ��9�� -;:��-

<.= � �>�#�� 4#?

@ 1�A�� -;:��-

8 ��9��$��B�-.�� /CD�(-"E�� "�#�$�� %'&()�*��,+��"-.��"�#��F�� >�9�G��&�� 4

<>��.�&��.� ?

��+��,+ �(H +��9�

I�6�J�=K<.I��C 4 ��&��$6�-9�:��#&��- ? �L��M��N�� 4 ��$��%'&�O�P��,+��5-.��"�#��

��Q��-9�C�+��-

An overview of the objects

��+��,+ �(H +��9��I�62J�=K<*%'&�O�*��,+�>-.��"�!:��$��.� ?

��R*R*R

8 ��9�� -;:��-

A*�� 9� 8 ��Q��ST%�� 8VU

��9��-"�N� 4SPW�X�Y�Z U

�2��.��Q�/+��

[�\^]`_/a!bdcèf�g�b`h�ikj`l^mn�lpo�eNa!_/\f�q�r

[�\^]`_/a!bdcèf�g�b`h�ikj`l^ms j`t.ikc`lu�v�w�x

x`g/o�a,bdc/ef�g�b`h�ikj`l^my#ldz{g�r2h�|pj}T~��(r(�

xpg/oa!bpcèf�g/b/h/ikj`ldmw�c�m;j`t.a,cè}P��p�^�`�

x`g/o�a,bdc/ef�g�b`h�ikj`l^my#ldz{g�r2h/|`j}T~��(r(�

8 ��9��>��2��.�

��

R*RPR

�� -;:��-

You can create one or more documents for a BW object.



BW uses the content model of the Knowledge Provider to manage these documents. There is adifference between

• the ORJLFDO�GRFXPHQW that is linked to the BW object by its attributes (for example, object type andobject name).

• and the SK\VLFDO�GRFXPHQW, which�is an individual value (version) belonging to a particular logicaldocument, and whose attributes (for example, language and format) are meta-descriptions of theindividual files.

The individual files can be stored on a SAP database or – using a HTTP interface – on an externalcontent server.

3UHUHTXLVLWHV

Give users the authorization to display or edit documents. See Authorizations for Documents [Extern].

For more information on the settings that you need to make before you start a project, see BWDocument Management [Seite 485].

)XQFWLRQV

1. You can add documents for metadata, master data, and transaction data. There are threecorresponding GRFXPHQW�FODVVHV.

The following overview shows you the BW objects that you can choose from, and thecorresponding document classes (with a typical example).

%:�2EMHFW 'RFXPHQW�&ODVV

0HWDGDWD

• InfoCube

• InfoObject

• InfoSet

• ODS Object

• Aggregates

• Update Rule

• InfoSource

• InfoPackage

• Reporting Agent Scheduling Packet

• Reporting Agent Settings

• Query (including variables, structures,restricted and calculated key figures).

0(7$

− Documentation

− Explanations (“characteristic ABCmeans ...”)

− History/changes

0DVWHU�GDWD

• Characteristic value

0$67

− Screens for personnel numbers

− Descriptions and technicalspecifications of materials

− Original documents for order forms

− Documentation for version(target/actual budget)

7UDQVDFWLRQ�GDWD

• Combination of characteristic values

75$1



You can also determine the following attributesof a document:

• InfoProvider

• Query

• Key figure

Comments on variouscharacteristic values (“Sales formaterial 4711 in Germany werepoor in May, because ...”, “In Maythe following key figures wereinteresting: Delivery quantity –Explanation ..., Outstandingpayments - ...”)

2. You can create documents in different IRUPDWV, for example:

− Text (.TXT)

− HTML

− MS Word (.DOC)

− MS Power Point (.PPT)

− MS Excel (.XLS)

− GIF

− JPG

3. You can manage documents in different ODQJXDJHV, by

a. creating a document in a source language

b. editing a document online or checking-it out of the system to edit it offline

c. creating a target-language version of a document that you have edited and saved online orchecked-out to edit offline and checked-in again

Since the logon language is an attribute of the physical document, the system gets the rightdocument for the language in which you logged on to the system.

The system checks the language first. If there are documents in several languages, thenewest document in the logon language is displayed. If there is no document available in thelogon language, the newest version of all the documents is displayed.

4. You can set links between documents that have been written in formats that support hyperlinks.

See Setting Hyperlinks between Documents [Seite 482].

5. There are various VHDUFK�RSWLRQV:

− by text strings in the documents

− by properties and attributes



+\SHUOLQNV�WR�'RFXPHQWV

'HILQLWLRQ

Link a document belonging to any document class to a second document without physically attachingit. Both documents need to have been created in a format that supports hyperlinks, for example,HTML, WORD, or EXCEL.

8VH

There are the following types of link:

1. You need the following information if you want to create a link from outside of the BW system to adocument belonging to a BW object:

• the server (meaning the SAP Web application server, not the ITS)

• the port

• the name of the document that you want to link to

From this information, you get the following URL:

'RFXPHQW�FODVV 85/

Metadata http://<Server>:Port/SAP/BW/DOC/META/FLDMETA/<Name of the document>

Master data http://<Server>:Port/SAP/BW/DOC/MAST/FLDMAST/<Name of the document>

Transaction data http://<Server>:Port/SAP/BW/DOC/TRAN/FLDTRAN/<Name of the document >

Make sure that the name of the document is unique within the document class.

2. You can use relative links to link documents that belong to one and the same document class.

To link to document 2, add the HTML code to document 1 according to the followingpattern:

<a href = "Name of document 2"> Text </a>

3. You can use this method of modifying the HTML code to link documents that do not belong to thesame document class.

For example, if you want to link document 1 to document 2 and document 1 belongs to theMETA document class and document 2 belongs to the TRAN document class, add theHTML code to document 1 as follows:

<a href = "../../TRAN/FLDTRAN/"Name of document 2"> Text </a>



6HDUFKHV�LQ�'RFXPHQWV

3UHUHTXLVLWHV

If you want to be able to search in documents, set the TREX search machine to index the documentsregularly.

5HVWULFWLRQV�RQ�6HDUFKHV�DQG�,QGH[HV

• You are able to search and index only in the languages belonging to the Latin 1 group, and thedouble-byte languages Japanese, Chinese, Korean, and Taiwanese.

• Searches and indexes do QRW work for EBSTIC character records, with AS/400 machines, forexample.

• TRex can be installed only on the Windows NT and Windows 2000 platforms.

6HDUFKHV�LQ�*HQHUDWHG�'RFXPHQWV

If you want to be able to search in generated documents for metadata, you first need to create agenerated version of the documents.

We recommend that from time to time (weekly, for example) you generate the documentsin the background, and check them in as hidden documents. This enables you to runsearches. Note, however, that using this method and depending on the time thedocuments are generated, the documents will not be quite up-to-date.

�$OWDYLVWD��6\QWD[�LQ�)XOO�7H[W�6HDUFKHV

You can use the Altavista-syntax search to run full-text searches in the documents from any documentclass.

)XQFWLRQ 6\QWD[ :KDW�\RX�QHHG�WR�NQRZ

Search by sentences �...� If you want to find a particular sentence, typethe sentence, in inverted commas, in thesearch string field.

� Includes words in the search

� Excludes words from the search

Including and excluding wordsfrom the search

For example, to search for a recipe for spaghettibolagnese without meat, type in:

+ recipe + spaghetti sauce - meat

Asterix as a wildcard You can extend the search by putting anasterix at the end of your search term. Thesystem finds all the words that contain yoursearch term in the first letters.

$1' Finds all the documents that contain the wordsor sentence fragments that you specify.

25 Finds all the documents that contain at leastone of the search terms you have specified.

Permitted logical operators

$1'�127 Excludes from the search any documents thatyou are not interested in.



An isolated NOT is not a valid operator in theAltavista syntax search.

1($5 The context search looks for your search termwithin a radius of “search term plus 10 words”.

For example, to find all the documents in which thewords VSRUW and IRRWEDOO appear near one another,type:

Sport NEAR Football

�� Use brackets to combine Boolean operators.



'RFXPHQW�0DQDJHPHQW�LQ�%:

8VH

In the 'RFXPHQWV function area of the Administrator Workbench, you choose the $GPLQLVWUDWLRQfunction to

• determine the storage type as a physical storage medium for the documents that you want tocreate.

• put documents (including online documentation for metadata objects) in the queue for indexing,and schedule the processing of this queue as a regular job, so that the documents are included inthe search.

• check whether the properties for the documents for transaction data have been generated fromthe characteristics that they were supposed to be generated from.

,QWHJUDWLRQ

Document management applies to documents from all the document classes. Functions that youneed, or that are useful

• at the start of a project

• after the BW system has been upgraded

• and during a project

are available in document management.

)XQFWLRQV

Tabstrip: Content Repository [Seite 486]

Tabstrip: Indexes for Searches [Seite 488]

Tabstrip: Generic Properties [Seite 491]



7DEVWULS��&RQWHQW�5HSRVLWRU\

'HILQLWLRQ

The storage type for documents is the physical means of storing the documents. The default storagecategory is the SAP database. On the &RQWHQW�5HSRVLWRU\ tabstrip in the data management area, youcan change the storage category for the documents that you want to create and that belong to aparticular document class.

8VH

Depending on the requirements of you application, we recommend that you decide, before you start aproject, which is the best storage category to use.

• SAP database (R/3 database)

Administration effort: Minimal

Access times: With large numbers of documents, and individual users, accessing thedocuments (over the Net) is slower than if you use a HTTP content server.

• HTTP Content Server

Administration effort: High

Access time: The HTTP content server can be implemented in stages, and the cachingmethod means that you can access documents quickly, even if there is a large number ofdocuments, and lots of different users.

You are able to change the content repository only if there are QR�GRFXPHQWV�LQ�WKHVHOHFWHG�GRFXPHQW�FODVV.

If documents do exist, you will no longer be able to access them, once you change thestorage category.

If, for example, you want to be able to transfer these documents to the HTTP contentserver, you have to first move the documents from the SAP database to the HTTP contentserver. In this case, contact your SAP consultant, or SAP directly.

6WUXFWXUH

The settings for each document class are displayed on the &RQWHQW�5HSRVLWRU\ tabstrip:

• Storing documents for metadata

• Storing documents for master data

• Storing documents for transaction data

The system shows you the settings for the following fields:

)LHOG :KDW�\RX�QHHG�WR�NQRZ

Content Repository [Extern] You use the &RQWHQW�5HSRVLWRU\�0DLQWHQDQFH pushbutton to get to the&KDQJH &RQWHQW�5HSRVLWRULHV��'HWDLO� This is part of the contentmanagement framework. You choose between 6LPSOH�$GPLQLVWUDWLRQ and)XOO�$GPLQLVWUDWLRQ.

For the %XVLQHVV�,QIRUPDWLRQ�:DUHKRXVH�document area, there is aselection list with the following storage categories.

• +773�&RQWHQW�6HUYHU

• 5��GDWDEDVH

• RFC archive



• Structure repository

Only the first two types are valid for the Business Information Warehouse

You use the %DFN pushbutton to get to the &KDQJH�&RQWHQW5HSRVLWRULHV��2YHUYLHZ�screen.

Storage category In this field, the system displays the selected storage category, R/3database, or HTTP content server.

If you want to change the storage category, click on the &RQWHQW5HSRVLWRU\�0DLQWHQDQFH pushbutton.

Number of logical documents

Number of physical documents

For more information on logical and physical documents, see Documents[Seite 479].



7DEVWULS��,QGH[HV�IRU�6HDUFKHV

'HILQLWLRQ

On the ,QGH[HV�IRU�6HDUFKHV tabstrip, there are various functions that you use in documentmanagement to enable you to check and change the status of the index and the index-job.

8VH

The following preconditions must be met before you are able to search in the documents belonging toBW objects:

1. The index must be switched on.

2. The program for indexing (RSTIRIDX) must run as a regular job.

If a document has been placed in the index queue and has been processed by this queue, it isincluded in the search.

6WUXFWXUH

The following fields and functions are on the ,QGH[HV�IRU�6HDUFKHV tabstrip:

)LHOG :KDW�\RX�QHHG�WR�NQRZ

TREX installed correctly yes/no

Index status on/off

If the index is ‘off’, change the setting in the ,QGH[�6WDWXV dropdown box to‘on’.

This ensures that new, deleted, and modified documents are included inthe index queue.

,QGH[�MREV

Status of the index-job scheduled/not scheduled

Execution date Date and time that the index-job is scheduled to run.

6FKHGXOH�LQGH[�MRE You get to the 6WDUW�'DWH�9DOXHV dialog box.

Specify that you want the program for indexing to run as a regular job.

This ensures that the index queue is processed regularly, All the wordscontained in the documents are included in the index.

We recommend that you schedule the job to run daily (forexample, alongside loading jobs for BW).

-RE�RYHUYLHZ�,QGH[

You get to the 6LPSOH�-RE�6HOHFWLRQ�screen.

)XUWKHU�)XQFWLRQV

*HQHUDWLQJGRFXPHQWDWLRQ�IRUPHWDGDWD

You get to the &UHDWLQJ�DQG�&KHFNLQJ�LQ�0HWDGDWD�'RFXPHQWDWLRQ�IURPWKH�5HSRVLWRU\�screen.

Select the object types (TLOGO) for which you want to generatedocumentation.

• all (*)

• single values

• an interval (using input help)



• multiple selection (using )

The program takes a while to run, sop we recommend thatyou

• restrict the selection

• schedule the program to run as a background job (3URJUDP��!([HFXWH�LQ�WKH�%DFNJURXQG).

Choose ([HFXWH. The system generates the online documentation forthe BW objects that you selected, and puts them in the index queue.

Since online documentation is always generated dynamically,this is the only way that it can be indexed, and that you areable to access the search function.

5H�LQGH[�DOOGRFXPHQWV

You get to the 5H�LQGH[�D�&ODVV�RU�D�'RFXPHQW�$UHD screen.

You can re-index DOO of the documents in a document class, and not justthe documents that are in the index queue. The result of the re-indexingprocess is similar to that of a re-initialization process.

This is necessary, for example, if you have edited documentswithout having the index switched on.

We recommend that you re-index after the BW system hasbeen upgraded to BW Release 3.0, because until this pointthe search function has not been available for documents formetadata.

0RQLWRULQJ�WKHLQGH[HG�GRFXPHQWV

You get to the .352�,06��0RQLWRULQJ�screen.

0RQLWRULQJ�WDEVWULS

Use the input help to select a document class.

Choose the 5HIUHVK�function.

The system uses the traffic light colors ( and ) to show youwhether or not the following settings are available in each of the documentareas:

− Index possible

− Auto-index

− DocArea activated

The system displays the DWWULEXWHV�WKDW�FDQ�EH�LQGH[HG, the YDOLG�LQGH[�FDWHJRU\�DWWULEXWHV, and the LQGH[�FDWHJRU\ in tables of the same name.

7RROV tabstrip

You need specialist knowledge to use this function.

,QGH[�'H�LQGH[: You use the 7ULJJHU�SURFHVV function to either start theindex queue immediately or schedule it to run in the background. You geta report on the GH�LQGH[LQJ�RI�GRFXPHQWV�WKDW�KDYH�EHHQ�FKHFNHG�LQ�

Under the header 6LQJOH�$FWLRQV, you are able to select individualdocuments that you want to either add or remove from the index.

Under the header 0DVV�$FWLRQV, you are able to re-index a whole class ora whole document area (restricted to the selected language).



Under the header ([WUDV, you are able to

• use the 7HVW�VHDUFK function to find documents

• use the 3UREOHP�FDVHV function to display documents with whichthere are problems

• use the ,QGH[HG�GRFXPHQWV function to find out which documentshave been indexed already

• use the 6FKHGXOHG�'RFXPHQWV�function to find out whichdocuments are still in the index queue.

Under the header ,QIRUPDWLRQ�DERXW, you can

• use the input help to select a document area, and click on the 'RF$UHD function to get information about the

− document classes, such as whether or not they can be indexed

− and the index categories that belong to the document class thatyou selected

• use the input help to select an index category, and click on the ,QGH[�FDWHJRU\ function to get information about the

− available language indexes

− attributes that can be indexed

− document classes, and whether or not they can be indexed



7DEVWULS��*HQHULF�3URSHUWLHV

'HILQLWLRQ

Using the *HQHULF�3URSHUWLHV tabstrip in document management, you can check the characteristicsthat you want to use as properties of documents for transaction data, to see if document propertieshave been generated from them already.

6WUXFWXUH

In the table, you can see the characteristics that are document properties, along with their generationstatus.

If there are still errors that occurred during the generation process, click on the *HQHUDWH'RFXPHQW�3URSHUWLHV function to regenerate the characteristics.

,QWHJUDWLRQ

In the PDLQWHQDQFH�VFUHHQV�IRU�FKDUDFWHULVWLFV, you have to set the “Characteristic is a documentproperty” indicator for all the characteristics that you want to use as properties of documents fortransaction data.

When the characteristics are activated, the system generates the document properties from thesecharacteristics, and inserts them as instance-attributes for the document classes for transaction data(BW_PH_TRAN and BW_LO_TRAN).

You can look at these attributes and document classes in the GRFXPHQW�PRGHOLQJZRUNEHQFK in the BW (Business Information Warehouse ) document area.

When it creates them, the system writes the document properties to a transport request. This is fortechnical reasons. You must write the document properties to a separate transport request that you donot transport. It is enough to transport the characteristics with the “Characteristic is a documentproperty” setting.

When you have transported the characteristics, you must generate the document properties in thetarget system.

The generation process does QRW run automatically in the after-import handling of thecharacteristics. The system tells the database that the generation process has not startedyet. The process that generates the document properties is triggered the first time you callthe document management in the target system.



3URFHVVLQJ�'RFXPHQWV�LQ�WKH�$:%�'RFXPHQWV�9LHZ1. You are in the 'RFXPHQWV function area of the Administrator Workbench. On the left-hand side of

the screen, the data types for which you are able to process documents are displayed:

− Metadata

− Master data

− Transaction data

On the right-hand side of the screen, the document class that has been processed mostrecently and the most recently made selection are displayed by default.

1. You use the 6KRZ�PH�GRFXPHQWV�IURP�function to display the available documents.

All the available attributes have the default value “*”, meaning that the system searchesthrough all of the values.

We recommend that you UHVWULFW�WKH�VHOHFWLRQ before you display the documents. Youcan use specific attributes as search criteria, or you can search the documents for aparticular text string.

• For more information on DWWULEXWHV, see

− Documents for Metadata [Seite 494]

− Documents for Master Data [Seite 497]

− Documents for Transaction Data [Seite 498]

Note the following when navigating in the display screens for documentsbelonging to transaction data objects:

You use the 6HWWLQJV�function to restrict the number of characteristics thatare displayed. You get to the &KDQJH�8VHU�6HWWLQJV�dialog box. Choose2QO\�2IIHU�WKH�&KDUDFWHULVWLFV�IURP�WKH�,QIR3URYLGHU or 2IIHU�$OO&KDUDFWHULVWLFV.

• If you want to search for documents containing a particular WH[W, type into the input fieldlabeled FRQWDLQLQJ�WKH�IROORZLQJ�WH[W, the text that you want to search for.

If you have used attributes of the object to restrict the search, the system searches fordocuments that match the selection that you made in the fields DQG the text that youspecified.

For more information on restricting a search, and other special features of the searchfunction, including the Altavista full-text syntax search, see Searches in Documents[Seite 483].

Do not activate the 6KRZ�PH�GRFXPHQWV�IURP�function, until you have finished making DOOyour restrictions and changes in the display screen.

3. The system shows you a list of documents for the BW objects that you selected.

The difference between this list and the list of documents on the 'RFXPHQWV screen, is thatthis list has an extra column containing the names of the objects for which each of thedocuments has been created.

If all of the documents in the list belong to the same object, this 2EMHFW�1DPH column isnot displayed.



Just as in the 'RFXPHQWV screen, there are various functions available. You access thesefunctions

− using the pushbuttons in the toolbar for the list of documents

− from the context menu (right-mouse click on each document separately)

When you create a document, only the fields for which you have made a selection arefilled with default values on the /RJLFDO�'RFXPHQW�3URSHUWLHV tabstrip. You are, however,able to make further restrictions.

For more information see Processing Documents in the Documents Screen [Seite 499].



'RFXPHQWV�IRU�0HWDGDWD

'HILQLWLRQ

You use the attributes REMHFW�W\SH and REMHFW�QDPH to assign one or more documents to a metadataobject.

The following table gives examples of the technical names that the system works with:

2EMHFW�7\SH 2EMHFW�1DPH

CUBE 0ABC_C01

IOBJ 0COSTCENTER

8VH

The user can choose a document that he or she wants to display in the online documentation.

See Documents as Online-Documentation [Seite 495].

,QWHJUDWLRQ

In the Administrator Workbench, there are various ways of editing a document for a single metadataobject.

• In either the 0RGHOLQJ or the 0RQLWRULQJ function area, you can

− select a BW object, and call up the maintenance screens for this object by following the path7RROV��!�'LVSOD\�'RFXPHQWV.

− branch to the object maintenance screens, and use the 'RFXPHQWV pushbutton to call themaintenance screens for the documents belonging to this object.

See Processing Documents in the Documents Screen [Seite 499].

• In the 'RFXPHQWV function area, you can search for a BW object, and create a new document forthe object, or edit an existing one.

See Processing Documents in the AWB Documents View [Seite 492].



'RFXPHQWV�DV�2QOLQH�'RFXPHQWDWLRQ

'HILQLWLRQ

Online documentation for a BW object is a document that has been generated for a particularmetadata object. This document can contain a text written by the user.

8VH

Online documentation is usually displayed as F1 Help for the object to which it is assigned.

Online documentation is displayed in the following situations:

• In the 'RFXPHQWV screen, you choose the 'LVSOD\�'RFXPHQWDWLRQ�pushbutton. The F1 Help isdisplayed in the Web browser.

• In the Administrator Workbench, you open the F1 Help for a BW object. You get to the 'RFXPHQWV

screen. You click on the 'LVSOD\�'RFXPHQWDWLRQ�pushbutton to display the F1 Help in the Webbrowser.

• You select a BW object from the metadata repository. The online documentation is displayedunder the header 'RFXPHQWDWLRQ.

• You open a BW Web query in a Web browser. You can display the online documentation for acharacteristic by selecting the appropriate option from the context menu (right mouse-click) or byfollowing the menu path *RWR��!�'RFXPHQWV.

6WUXFWXUH

The online documentation for a BW object is made up of the following parts:

1. The first part contains general information about the object, such as

• the type (with symbol) and name of the object

• the date the object was created

• the technical name of the object

• system

• description (short)

• description (long)

2. The GRFXPHQWDWLRQ part contains the following text:

• If the user has created a text document or an HTML document for the object, and designated thistext as online documentation, the system displays this text

• If the user has not written any online documentation, the system displays the Business Contentdocumentation.

• If there is no Business Content documentation for the object, the system does not display a text.

If there are links to RWKHU�GRFXPHQWV, these links are displayed.

3. The third part contains links to the online documentation of dependent objects.

For a characteristic, this would be, for example:

− Objects with which the characteristic is compounded

− Display attributes

− Navigation attributes

Under $GGLWLRQDO�2EMHFWV, for example:



− Objects from which the characteristic receives data (transfer rules, for example)

− Objects from which the characteristic is used

The links are generated dynamically from the metadata repository, and are therefore alwaysup-to-date, even if the data model is changed.



'RFXPHQWV�IRU�0DVWHU�'DWD

'HILQLWLRQ

You use the attributes FKDUDFWHULVWLF and FKDUDFWHULVWLF�YDOXH to assign one or more documents to amaster data object.

,QWHJUDWLRQ

You maintain documents for master data objects in the same way that you maintain documents formetadata objects (with the exception of the option of displaying documents as online documentation).

For more information, see Documents for Metadata [Seite 494].



'RFXPHQWV�IRU�7UDQVDFWLRQ�'DWD

'HILQLWLRQ

You can assign one or more documents to the transaction data in an InfoProvider.

Some default attributes are provided:

• As search criteria for transaction data in the 'RFXPHQWV function area of the AdministratorWorkbench

See Processing Documents in the AWB Documents View [Seite 492]

• As logical document properties whenever you create a document

See Creating Documents [Seite 502]

In addition to the attributes listed in the Documents [Seite 479] section:

• InfoProvider

• query

• and key figure

the characteristics designated as properties of documents are also displayed (and sortedalphabetically).

You must activate any characteristics you want the system to display in the maintenancescreens for transaction data documents. Do this in the maintenance screens forcharacteristics on the Tabstrip: General [Seite 34]. (A characteristic is a property of adocument.)

,QWHJUDWLRQ

You maintain documents for transaction data – with regards to the specific properties of the documentclass – in the same way that you maintain documents for metadata objects.

For more information, see Documents for Metadata [Seite 494].



3URFHVVLQJ�'RFXPHQWV�LQ�WKH�'RFXPHQWV�6FUHHQ1. You are in the 0RGHOLQJ or 0RQLWRULQJ functional area of the Administrator Workbench.

Choose the object tree and the object for which you want to create one or more documents.

2. Choose 7RROV��!�'LVSOD\�'RFXPHQWV.

3. The documents are maintained in a separate window. On the 'RFXPHQWV screen, the followingfunctions are available as pushbuttons on the toolbar:

)XQFWLRQ 3XVKEXWWRQ ,QIRUPDWLRQ

Display online documentation 'LVSOD\�'RFXPHQWDWLRQ See Documents as Online-Documentation [Seite 495]

Create a new document &UHDWH See Creating Documents [Seite502]

Import a file and store it as anew document

,PSRUW See Importing Documents [Seite504]

Display Documents in the WebBrowser

'LVSOD\�'RFXPHQWV�RQ�WKH:HE

Loads all the existingdocuments for the selectedobject in the system into aseparate browser window.There you can display andchange the documents. It islikewise possible to create anew document for the selectedobject.

See Creating Documents[Extern]

'LVSOD\ See context menu 'LVSOD\

(GLW See context menu 'HWDLO, view3UHYLHZ, pushbutton (GLW'RFXPHQWV

([SRUW See Exporting Documents[Seite 505]

3URSHUWLHV See context menu 3URSHUWLHV

'HWDLO See context menu 'HWDLO

'HOHWH See context menu 'HOHWH

Sort list of documents inascending order

6RUW�$VFHQGLQJ

Sort list of documents indescending order

6RUW�'HVFHQGLQJ

6HDUFK

Determine filter criteria Set / Delete filter

3ULQW

4. The following functions are available from the context menu (right-mouse click) of each of thedocuments:

)XQFWLRQ ,QIRUPDWLRQ 6SHFLDO�)XQFWLRQV

Preview Displays the contents of the document in the lower part of the screen.



Display Loads the document into a separate window in the application, in which itwas written.

There are various different views foryou to choose from.

You use the %DFN�and )RUZDUG pushbuttons and the 9LHZdropdown box to switch between thedifferent views.

Preview

Displays the contents of thedocument in the lower partof the screen.

Edit Document

The application, in which thedocument was written, isopened. Make any changesthat you want to make.

When you save thedocument, you decidewhether you want tooverwrite the old version, orcreate a new version.

When you close theapplication, the document ischecked-in automatically.

If you want to edit a HTMLdocument, choose the (GLWZLWK�0LFURVRIW�)URQW3DJHoption from the InternetExplorer. In the HTMLeditor, make any changesthat you want to make.

The system does not check-in the document until youhave closed the InternetExplorer.

'LVSOD\

Properties

displays all the documentproperties in an ALV gridcontrol.

In addition to the functions that youare familiar with from the 3UHYLHZ,there are also the following:

6DYH

'LVSOD\��&KDQJH

8QGR

Versions

displays in an ALV gridcontrol, all the physicaldocuments (versions) for alogical document.

Detail

Where-used list

shows a where-used list inthe ALV grid control.

You can display the 3URSHUWLHVfor each of the versions (see3URSHUWLHV from the context menu).

In the ALV grid control, you can usethe standard functions (sort, find, setfilter, print, view, export, and chooselayout).

For more information see 8VHU'RFXPHQWDWLRQ.



Used objects

shows in the ALV gridcontrol a list of the objectsused.

Properties Displays the properties on the following tab strips:

General

Name, description,language, created by, lastchanged by.

+LGGHQ checkbox A hidden document is a documentthat is displayed in the maintenancescreens, but not in Web reporting.

Logical document properties (logicalproperties of a document)

for metadata:

object name, object type

Online documentation In the change mode, you determinethe status of the documents bychoosing \HV or QR from thedropdown menu. You can choose<HV only for a document.

Technical information:

Logical document

Physical document

Detail information

Delete Deletes the selected documentalong with all physical documents.



&UHDWLQJ�'RFXPHQWV

3UHUHTXLVLWHV

You are in the maintenance screens for documents

• in the 'RFXPHQWV function area of the Administrator Workbench

• on the 'RFXPHQWV screen for a BW object

3URFHGXUH

1. Choose &UHDWH� You get to the &UHDWH�1HZ�'RFXPHQW dialog box.

2. Type the required data onto the tabstrips.

7DEVWULS :KDW�\RX�QHHG�WR�NQRZ

General The GRFXPHQW�FODVV (doc.-class) is pre-set.

BW: Physical class metadata

BW: Physical class master data

BW: Physical class transaction data

1DPH: Specify a technical name.

The name must be unique for all the documents in a documentclass.

'HVFULSWLRQ

This description appears as a link-text in Web reporting.

0,0(�W\SH: 6LPSOH�WH[W is the default.

Clicking on the ( ... ) pushbutton next to the input field displays allthe available MIME types.

The internet standards for the names of applications are listed under0,0(�7\SH, and a description of each application is given under7H[W.

You determine the valid types in the document managementsection of the Administrator Workbench.

Select the MIME type that you want to use, and choose 2..

Log.Doc.Property Logical document properties are

for metadata:

object name

object type

online documentation yes/no

for transaction data:

characteristic



characteristic value

Web document type

for transaction data:

InfoProvider

query

key figure

various characteristics (depending on the InfoProvider)

The particular BW object that you have chosen, or the extent to which youhave restricted the number of BW objects in the selection, determines if andhow many of the fields are filled with default values.

Input help is available for these input fields. Fields that have dependentfields must be filled.

For example, you are not able to open the input help for theFKDUDFWHULVWLF�YDOXH field, until you have selected acharacteristic.

Technical information 'RFXPHQW�FODVV

/RJLFDO�GRFXPHQW�FODVV

You are not required to make any entries.

3. You choose the 6WDUW�(GLWRU�function to begin editing the document. The application opensaccording to the MIME type that you have selected.


5. Close the application.



,PSRUWLQJ�'RFXPHQWV

8VH

If you have a file that you have created in any other application outside of the BW system, and youwant to use this file as a document for a BW object, you can import the file into the documentmanagement section of the BW system.

3UHUHTXLVLWHV

You are in the maintenance screens for documents



3URFHGXUH

1. Choose the ,PSRUW�function. This takes you to the 2SHQ dialog box.

2. Type in the required data (file name, format, storage location).

3. Choose 2SHQ. You get to the &UHDWH�1HZ�'RFXPHQW dialog box.

4. On the *HQHUDO tabstrip, QDPH, ILOH�QDPH, and 0,0(�W\SH are given already.

You can change the (technical) name, and give a description.

Choose the /RJLFDO�'RFXPHQW�3URSHUWLHV tabstrip.

If you have jumped directly to the document maintenance screen from a particular BWobject, the logical document properties are given already.

If, however, you have gone to the document maintenance screen from the 'RFXPHQWVfunction area of the Administrator Workbench, and have QRW yet restricted the selection toone particular BW object, you must fill out the required fields on the /RJLFDO�'RFXPHQW3URSHUWLHV tabstrip. Input help is available for some of the fields (for example, object typefor metadata objects).


5HVXOW

When the file has been imported successfully, the system tells you that the new document has beensaved. You can see the entry for your document in the list of documents.



([SRUWLQJ�'RFXPHQWV

3UHUHTXLVLWHV

You are in the maintenance screens for documents.



3URFHGXUH

You click on the (GLW pushbutton to call the ([SRUW function.

There are the following options. The one you choose depends on what you want to do with thedocument.

([SRUWLQJ�D�FRS\�RI�D�GRFXPHQW

�� You choose the ([SRUW�DV�&RS\ option if you want to make a copy of the document and store in onyour hard drive.

This takes you to the 6DYH�DV dialog box.



The file with the copy of the document is stored in the location that you specify.

([SRUWLQJ�D�ORFNHG�GRFXPHQW

1. If you want to check-out a document and process it locally, choose the ([SRUW�ZLWK�/RFN function.

This takes you to the 6DYH�DV dialog box.



The document is stored in the location that you specify, and you are able to process it locally.

4. When you check-out a document, the following changes occur in the Administrator Workbench:

The name of the user, who has checked-out the document is displayed in the 3URFHVVHG�%\column of the document list.

Now, when you click on the (GLW pushbutton, you are able to call the ,PSRUW�9HUVLRQ and5HPRYH�/RFN functions in addition to the ([SRUW�DV�&RS\ function:

5. You choose the ,PSRUW�9HUVLRQ function if you want to import the document that you checked-outpreviously. This takes you to the 2SHQ dialog box.

a. Type in the required data (file name, format, storage location).

b. Choose 2SHQ. You are taken to the &UHDWH�'RFXPHQW�9HUVLRQ dialog box.

c. If you want to RYHUZULWH�WKH�ROG�YHUVLRQ, put a checkmark in the appropriate checkbox.

Otherwise, the system creates a new version.

The system suggests the attributes of the old version and their values as the defaultvalues for the new version. You are able to change these values, if you want to.

The default value for the /DQJXDJH attribute is *HUPDQ. If you want to change thelanguage, use the input help for this field, and select a different language from theODQJXDJH�NH\.

d. Save your entries.



6. If you do QRW want to copy over the document that you have edited locally, choose the 5HPRYH/RFN option.

The document in the BW system retains the status it had before the export.



7UDQVODWLQJ�D�7H[W�IRU�%:�2EMHFWV

8VH

In the 7UDQVODWLRQ function area in the Administrator Workbench, you can translate short and long textsfor objects of the Business Information Warehouse.

The worklist automatically includes the following objects for object translation.

• the sub-objects for this object

For example with a query

• InfoObjects (characteristics and indicators)

• pre-defined InfoProvider structures

• objects connected with this object

For example, those workbooks in a query in which the query is inserted.

3URFHGXUH

1. In the main menu of the SAP Business Information Warehouse select %:�$GPLQLVWUDWLRQ ->$GPLQLVWUDWRU�:RUNEHQFK�

2. Select the 7UDQVDFWLRQ�function area using the corresponding pushbutton in the left-handnavigation window or by -XPS��!�7UDQVODWLRQ

The procedure in steps 3 to 6 correspond fully to the procedure when transferringBusiness Content (steps 3 to 6). You can find further information under Transfer BusinessContent [Seite 21] .

3. If you want to assign source systems, select $VVLJQPHQW�6RXUFH�6\VWHP. The 6HOHFW�6RXUFH6\VWHP�DV�'HIDXOW�dialog window appears.

4. Change the required settings in the *URXSLQJ�selection list and the &ROOHFWLRQ�0RGH�

5. Select the object type you want to translate in the Administrator Workbench navigation window.

You can include all objects that are positioned before or after the selected object in thedata flow via *URXSLQJ��Therefore, you can translate a structured source system scenariowith InfoSources, InfoCubes up to Queries and Workbooks all together, for example.

6. Choose the object(s) you want to translate in the central screen area and add them to the right-hand &ROOHFWHG�2EMHFWV�screen area by drag and drop.

The system displays the selected object(s) and all dependent objects in the &ROOHFWHG�2EMHFWVscreen area.

Only activated objects are translated, meaning objects in the A version, as only theseobjects are transported. When you have changed the object texts, you must activate theseobjects EHIRUH�WUDQVODWLRQ�

7. Choose �7UDQVODWH The 'HIDXOW�6HWWLQJV dialog box appears.

Choose the source and target language on the /DQJXDJHV tab strip.



Choose your default settings on the 6KRUW�7H[W�(GLWRU��/RQJ�7H[W�(GLWRU�and :RUN�/LVW�tabstrips

You can restore the standard default values using 'HIDXOW�9DOXHV�

Confirm your entries with &RS\.

You can find additional information under Default Settings for the Short Text Editor [Extern],Default Settings for the Long Text Editor [Extern], Default Settings for the Worklist [Extern].

8. The :RUNOLVW��/LVW�screen appears. Open the /RJLFDO�2EMHFWV�hierarchy node. A list of all objects tobe translated appears.

9. 7UDQVODWLRQ�6WDWXV allows you to view the translation status of the individual objects. The statusof individual objects is indicated with the following colors:

• red (“new text”): The text has yet to be translated (or only with blank characters).

• blue: (“correct text”): The text has been translated and is consistent with the correspondingproposal in the proposal pool.

• yellow (“unaccepted text”): The translation of the source text does not match the proposal from theproposal pool, meaning the translation may have to be re-edited.

10. You can translate your worklist in the following way:

• one object after the other in sequence using 6HTXHQWLDO�3URFHVVLQJ�

• selected individual objects by double-clicking the selected object.

11. The /RJLFDO�2EMHFWV�7UDQVODWLRQ�screen appears.

Process the short and long texts. The system makes a 7UDQVODWLRQ�$VVLVWDQW�availabledepending on the processing status.

Save your translation.

The system displays the number of translated, modified, and new texts next to therespective object in the worklist.

For more information see Editing A Worklist [Extern].

5HVXOW

The translated texts are now in the Business Information Warehouse.



6WHS�%\�6WHS�,QVWUXFWLRQV

:DUHKRXVH�0DQDJHPHQW

Creating an SAP Source System Manually [Seite 233]

Creating an SAP Source System Automatically [Seite 232]


Transferring Business Content DataSources into Active Version [Seite 240]

Creating External Systems [Seite 235]

Creating File Systems [Seite 236]

Updating Metadata for Flat Files or External Systems [Seite 259]

Creating InfoSources (R/3 Source System) [Seite 277]

Communication Structures for an InfoSource [Seite 279]

Maintaining Transfer Structures [Seite 284]

Maintaining Transfer Rules [Seite 285]

Maintaining InfoSources (External System) [Seite 303]

Creating Communication Structures [Seite 279]

Processing Transfer Rules (Creating Transfer Structures) [Seite 285]



Editing InfoObjects [Seite 89]

Assigning a Source System to a Source System ID [Extern]

Creating and Changing Master Data [Seite 96]

Deleting Master Data at Single Record Level [Seite 100]

Activating Master Data and Texts [Seite 102]

Maintaining Time-Dependent Master Data [Seite 97]



Creating InfoCubes [Seite 110] / Creating ODS Objects [Seite 167]

Checking the Data Loaded into InfoCubes [Seite 117]

Using the SAP Demo Cube [Extern]

Creating a Start Routine [Seite 207]


Changing Update Rules [Seite 223]

Creating Update Routines [Seite 221]


Maintaining InfoPackage Groups [Seite 397]

Scheduling InfoPackages [Seite 355]

Scheduling an InfoPackage Group [Seite 398]

Procedure for SAP Systems [Seite 352]

Procedure for Flat Files [Seite 353]

Procedure for External Systems with BAPI Functions [Seite 354]

Creating Hierarchies [Seite 184]

Loading Hierarchies [Seite 181]

Activating Hierarchies [Seite 191]

Copying Hierarchies [Seite 190]

Maintaining Hierarchy Versions [Seite 194]

Editing Aggregates [Seite 133]

Creating the First Aggregate for an InfoCube [Seite 137]


Creating Currency Translation Types [Extern]

Editing Currency Translation Types [Extern]

Uploading Transaction Data from Flat Files [Seite 290]

Uploading Master Data from Flat Files [Seite 294]


Maintaining the InfoObject Catalog [Seite 30]

3URFHVV�&RQWURO

Creating an Event Collector [Seite 450]



Editing an Event Collector [Seite 452]

Scheduling the Event Collector [Seite 451]

Creating a Process Chain [Seite 440]

3HUVLVWHQW�6WDJLQJ�$UHD

Checking and Changing Data [Seite 391]

Checking and Changing Data Using PSA-APIs [Seite 392]

Using the Data Mart Interface [Seite 264]

Transport Connection: Transporting Objects [Extern]

Transporting Roles and BEx Objects [Extern]

Installing Business Content [Seite 21]

Translating a Text for BW Objects [Seite 507]

Searching for Metadata [Seite 15]

Displaying Graphics [Seite 16]

Creating BW Documentation [Extern]

Setting up Authorizations with Role Maintenance [Extern]

Authorization Check when Executing a Query [Extern]

Setting up Reporting Authorizations [Extern]

Manually Maintaining Reporting Authorizations [Extern]

Creating a Copy of the BW [Extern]

Creating a Copy of an SAP Source System [Extern]

Editing Sender/Receiver Assignment to the R/RI in BW [Extern]

Evaluating Exceptions in the Background [Seite 454]

Printing in the Background [Seite 461]

Defining the Print Layout [Seite 465]

5HSRUWLQJ

Step-By-Step Instructions in Reporting [Extern]