i00 bb configguide en de

7/30/2019 I00 BB ConfigGuide en De

http://slidepdf.com/reader/full/i00-bb-configguide-en-de 1/17

SAP BW 3.5

November 2004

English

I00: Essential Information

for SAP Best Practices for BI

SAP AGNeurottstr. 1669190 Walldorf Germany



SAP Best Practices Essential Information for SAP Best Practices for BI

Copyright

© Copyright 2004 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without

the express permission of SAP AG. The information contained herein may be changed without prior notice.

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

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

IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®, AS/400®,OS/390®, OS/400®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®,Netfinity®, Tivoli®, Informix and Informix® Dynamic Server™ are trademarks of IBM Corporation in USAand/or other countries.

ORACLE® is a registered trademark of ORACLE Corporation.

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

Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®,MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.

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.

MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, and other SAP products and services mentioned herein aswell as their respective logos are trademarks or registered trademarks of SAP AG in Germany and inseveral other countries all over the world. All other product and service names mentioned are thetrademarks of their respective companies. Data contained in this document serves information purposesonly. National product specifications may vary.

© SAP AG of 17




Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include fieldnames, screen titles, pushbuttons as well as menu names, paths andoptions.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT Names of elements in the system. These include report names,program names, transaction codes, table names, and individual keywords of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths,messages, source code, names of variables and parameters as well asnames of installation, upgrade and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the

ENTER key.

Example text Exact user entry. These are words or characters that you enter in thesystem exactly as they appear in the documentation.

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

© SAP AG of 17




Content

Essential Information for SAP Best Practices for BI........................................................................5

1 Target Group............................................................................................................................ 5

2 Purpose and Content................................................................................................................5

3 SAP Best Practices for BI......................................................................................................... 6

.3.1 Building Blocks..................................................................................................................6

.3.2 Document Types and Content......................................................................................... .6

4 Working with SAP Best Practices for BI................................................................................... 7

.4.1 Release Levels................................................................................................................. 7

.4.2 SAP Notes for BW............................................................................................................ 8

.4.3 Additional SAP Notes for the SAP Best Practices for BI Solution.....................................9

.4.4 Business Content ........................................................................................................... 104.4.1 Working with ODS Objects........................................................................................10

4.4.2 Working with DataSources........................................................................................13

4.4.3 Working with Persistent Staging Area (PSA).............................................................14

.4.5 Administration.................................................................................................................15

4.5.1 Transfer Business Content DataSources..................................................................15

4.5.2 Activating Transfer Rules .........................................................................................15

4.5.3 Warning Messages....................................................................................................16

4.5.4 Scheduler.................................................................................................................. 16

4.5.5 Loading Master Data / Texts / Hierarchies................................................................ 17

© SAP AG of 17




Essential Information for SAP Best Practicesfor BI

1 Target GroupThis document is intended for SAP Channel Partners, consultants and system administratorswho are involved in an SAP Best Practices for BI installation.

2 Purpose and Content

The purpose of this document is to provide the essential information you need for the installationof SAP Best Practices for BI scenarios and building blocks as well as information on how to usethe relevant documentation. Specifically, this document contains a number of “tips and tricks” onhow to handle the most common problems that arise during the installation. Also, SAP Notes thathave to be implemented before starting the installation in SAP BW are listed here.

The main sections of this document:

1. Introduce the concept of SAP Best Practices for BI installations and provide anoverview of the building block approach and a general idea of the installation processusing building blocks.

2. Show you how to use the documentation delivered with SAP Best Practices BI.

3. Highlight which SAP Notes you need to install for a specific solution.The activities described in this section are a prerequisite of any installationprocedure!

4. Provide explanations and support for the most common errors and mistakes that canoccur during the installation.

Procedure

Read the documentation of the building block Essential Information for SAP Best Practices for BI before starting with the installation of SAP BW business scenarios.

Important information:

Almost all SAP Best Practices versions consist of two components: One documentation CD thatcontains the business and technical documentation needed to set up the SAP Best Practicespreconfigured scenarios and one configuration CD which contains the preconfiguration settingsneeded for automated system setup.

However, SAP Best Practices for Business Intelligence - V1.35 does NOT make use of automated installation procedures, therefore no preconfiguration settings are delivered and noconfiguration CD is needed. The configuration guides on the SAP Best Practices for BusinessIntelligence documentation CD describe how to configure the system MANUALLY in order to getthe SAP Best Practices business scenarios up and running.

© SAP AG of 17




Thus, making use of the SAP Best Practices for Business Intelligence documentation CD youhave all you need to set up the SAP Best Practices business scenarios.

3 SAP Best Practices for BI

With SAP Best Practices, SAP offers a time and cost-saving methodology for implementing SAPsolutions.

SAP Channel Partners can benefit from this methodology by using SAP Best Practices for their own customers or as a solid base for developing their own vertical solutions. Comprehensivedocumentation is provided for all installation activities.

.3.1 Building Blocks

Definition

Building blocks are reusable units of preconfiguration or documentation that you can combine toinstall an SAP business scenario or solution. The building block concept offers substantialbenefits to SAP Channel Partners involved in the development, distribution, and sales of SAPsolutions for the SMB market. You can use the building block installations as the basis for your own vertical solutions. Similar to a construction kit, you can assemble building blocks flexibly toset up business scenarios. Using building blocks for installing business content means reducingredundancies, because you can use a generic building block in different solutions.

In the past the configuration content was component-focussed. You had to import theconfiguration of an entire system, whereas you can now select blocks of scenario-orientedconfiguration. The reusability of building blocks accelerates and facilitates the installationbecause you need no longer import the settings of an entire system but can build upon separateconfiguration blocks. As a consequence, development and maintenance costs are minimized,because redundant development is reduced.

Building Block Characteristics

A building block is not characterized by the amount of preconfiguration it covers but by itsreusability as a complete configuration entity in the installation of one or more solutions. With thebuilding block approach, you can therefore classify both entire solutions and minor specificconfiguration packages as building blocks, depending on their ability to feature as configurationunits in different solutions.

.3.2 Document Types and Content

Purpose

To set up an SAP Best Practices scenario, you have to install a number of building blocks in apredefined sequence. For each building block, there are documents describing the preparationand installation procedures for a stand-alone building block or scenario. The installationdocumentation for a scenario thus comes in the form of a number of individual documents thatare delivered together with their associated building block.

Therefore, the individual installation documents cannot normally be used on their own and it isimportant that you read the documentation carefully in the correct order .

The following table gives you an overview of the documentation delivered with SAP BestPractices.

© SAP AG of 17




Document Type Purpose File Format

ScenarioDescription

Briefly describes the content and process flow of a scenarioand shows its benefits

HTML

Building Block Description

Briefly describes the content of a building block and lists itsfunctions and benefits

HTML

ScenarioInstallationGuide

The Scenario Installation Guide tells you which buildingblocks you need to install for a specific scenario and whichsequence you should apply in the installation process. It isthe documentation backbone for installing an SAP BestPractices business scenario. It does not give you detailedinstructions on how to install a specific building block butmay contain scenario-specific configuration data. Alwaysrefer to the Scenario Installation Guide before you startinstalling a building block according to the detailedprocedures in the Building Block Configuration Guide of that building block.

MS Word

Building Block

ConfigurationGuide

For each building block, there is a Building Block

Configuration Guide that describes in detail how to install thebuilding block.

MS Word

BusinessProcessProcedure

End user documentation providing detailed application-focused descriptions of individual business processes andbusiness processes of a business scenario

MS Word

4 Working with SAP Best Practices for BI

This section contains a number of “tips and tricks” how to handle the most common problems thatarise during installation. Also SAP Notes that have to be implemented before starting theinstallation in SAP BW are listed here.

.4.1 Release Levels

The SAP Best Practices scenarios have been tested on an environment with different systemlandscape components on certain release levels and support package levels specified in thefollowing sections.

If the release and support package levels do not match the indicated levels, errors might occur. Also the documentation is based on the menu paths and transaction views as they appear in thegiven system environment.

Therefore we recommend to stick to the release and support package levels prerequisites givenbelow for each involved system. After the installation you can upgrade to the latest release andsupport packages.

© SAP AG of 17




mySAP.comApplicationComponent

SoftwareComponent

Release Level Highest SupportPackage

SAP BW SAP_BASIS 640 0004 SAPKB64004

SAP_ABA 640 0004 SAPKA64004

SAP_BW 350 0004 SAPKW35004

PI_BASIS 2004_1_640 0004 SAPKIPYI64

BI_CONT 352 0002 SAPKIBIEP2

SAP SCM SCM 410 0001 SAPKY41001

SAP_BW 350 0003 SAPKW35003

SAP_BASIS 640 0003 SAPKB64003

SAP_ABA 640 0003 SAPKA64003SAP R/3Enterprise

SAP_BASIS 620 0034 SAPKB62034


SAP_APPL 470 0017 SAPKH47017

PI 2004_1_470 0001 SAPKIPZI51

PI_BASIS 2004_1_620 0003 SAPKIPYI53

SAP CRM SAP_BASIS 620 0032 SAPKB62032


BBPCRM 400 0003 SAPKU40003

PI_BASIS 2003_1_620 0005 SAPKIPYH55

.4.2 SAP Notes for BW

The following notes may have to be implemented. Check if the symptoms described for each noteare given in your system landscape:

SAPNote #

SupportPackage

Description / Symptom Component

0316923 - Administrator Workbench cannot be startedThe program terminates with the message that

you are only authorized to work in client ... (Brain

009).

BW-SYS

0093821 - Problems after new installation of a BW system.Error message: The SAP Business InformationWarehouse <Logical System name> is alreadyconnected to the source system. A multipleconnection is not possible

BW-WHM-DST-SRC

0580926 - No texts for product, vendor, product category inthe BW

SRM-BW

© SAP AG of 17




0356018 - Activate the standard transport system in BW BW-SYS

640903 Dialog box when you create an Infopackage BW-WHM-DST

658343 Error RSAU 461 when you activate the updaterules

BW-WHM-DST-UPD

641300 Termination in the "Data flow display" BW-WHM-AWB650570 P16:Content: Objects found despite deactivated

BCBW-WHM

587934 Extension of extraction structure MC02M_0SCL SRM-EBP-INT

683312 After Support Package: Cannot read queue data BC-BW

BW Service API

660239 Transfer rule: Enable 'long field names' BW-WHM-DST-TRS

750322 BW: Problems when storing master data 0PLANT BW-BCT-ISR

738395 Error when loading material master data into BW BW-BCT-LO-MD-MM

769915 RSAR 196: The InfoObject & contains the non-alpha-conform

BW-WHM-DST-TRS

570861 Checking the size between subscreens andelements

BC-FES-GUI

.4.3 Additional SAP Notes for the SAP Best Practices for BISolution

UseSome problems in the installation of SAP Best Practices scenarios may become known only after the shipment of an SAP Best Practices version.

Should this be the case, you can find SAP Notes containing the information on problems, bugfixes, etc. that became known after the shipment.

Procedure

Before you start the installation process, check the latest version of the SAP Note for your solution to obtain updates and corrections of the Best Practices documentation and configurationactivities.

Check the following table to find the appropriate SAP Note for your solution:

Solution SAP Note No.

SAP Best Practices for BI V1.33 729354

SAP Best Practices for BI V1.35 780380

If errors occur during the installation process, proceed as follows:

© SAP AG of 17




• Make sure that you have installed the SAP Notes mentioned in this document

• Log on to the Service Marketplace and search for appropriate SAP Notes.

If you cannot find a solution for the problem this way, open a customer message specifying thecomponent SV-SMB-AIO-BP-BI.

.4.4 Business Content

4.4.1 Working with ODS Objects

Use

This section provides general information about ODS objects in SAP BW.Further information can be found on the SAP help site on the internet (Select Administrator

Workbench ModelingDataTargets ODS Objects).

ODS Objects

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.

An ODS object contains key fields (for example, document number/item) and data fields that canalso contain character fields (for example, order status, customer) as key figures. The data froman ODS object can be updated with a delta update into InfoCubes and/or other ODS objects or master data tables (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.

The cumulative update of key figures is supported for ODS objects, just as it is with InfoCubes,

but with 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 notapply solely to numeric fields such as order quantity, but also to non-numeric fields such asgoods receiver, status, and delivery date. To map these changes in the BW ODS objects, therelevant fields in the ODS objects must also be overwritten and set to the current value.

Every ODS object is represented on the database by three transparent tables:

Active data: A table containing the active data (A table)

Activation queue: For saving ODS data records that are to be updated but that have not yetbeen activated. The data is deleted after the records have been activated.

Change log: For updating delta from the ODS Object into other data targets, such as ODSObjects or InfoCubes for example.

An exception is the transactional ODS object, which is only made up of the activedata table.

© SAP AG of 17

http://help.sap.com/saphelp_bw30b/helpdata/en/ad/6b023b6069d22ee10000000a11402f/frameset.htm

http://help.sap.com/saphelp_bw30b/helpdata/en/ad/6b023b6069d22ee10000000a11402f/frameset.htm




Activating Data in the ODS Object

Use

Before you can use an ODS object as a data source for another ODS object or InfoCube, youhave to make sure that the data is of good quality, and that it is active in the system. You can only

activate the data if you have not switched on the option for the automatic processing of therequest in the ODS Object Maintenance or Administration. However, we recommend using thisautomatic postprocessing restrictively.

To simplify the process, we further recommend using process chains. By using process chains,you also ensure that a process ends before the ones that follow are initiated. If you do not want touse process chains, proceed as described below.

Functions

The data is written when activating the active data in the table, which is where the data is thenavailable for reporting. During activation, the requests are sorted according to their logical keys.This ensures that the data is updated in the active data table in the correct request sequence.

With an activation session, packages (from several PSA requests) are created that can beactivated in parallel. However, several activation runs cannot run in parallel. Instead, they have tobe triggered in sequence. However, this is only relevant for automatic activation. With manualactivation, the pushbutton for activation is available again only if the previous activation run iscompleted.

Manual Activation:

Either choose using the context menu ( right mouse-click ) on the ODS Object → Activate ODS

Object, or choose Activate ODS Data on the Requests tab in the administration. The inactiverequests are displayed, enabling you to activate them. Only activated requests are updated inother 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 requestafter being activated. These are then updated individually to additional data targets.Otherwise, all requests activated in this process are compressed into a change logrequest. Only this request can be completely rolled back from the ODS object. This hasbeen possible since release 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 aseries. Otherwise, data is activated in the separated dialog processes in parallel.

If an activation process is canceled, you are also unable to activate the followingrequests. Most importantly, you have to repeat the canceled activation until it issuccessful.

© SAP AG of 17




Updating the ODS Object Data in Data Targets

From the context menu for your ODS object, choose Update ODS Data in Data Targets. Selectthe update method. You arrive in the scheduler. There you can update the ODS data by using theexport InfoSource. This export InfoSource is automatically generated with the activation of theODS object together with the transfer rules.

This generated export InfoSource can not be edited, which means thatthe transfer rules cannot be changed, and Only Data Targets is set asthe processing type. Loading using the PSA is also unavailable.

Manual changes might cause the following problems:

• The next time the ODS object is activated, the transfer rules are overwritten.

• The rules cannot be transported. Modifications would have to be maintained in

the target system for the transport.

• The transfer rules are deleted when the ODS object is deleted.

When updating ODS object data in additional data targets (ODS objects such as InfoCubes),there are three options. With all three options, you can transfer deltas afterwards.

1. Full Update:

The connected data target is filled with the active data from the ODS object. They are transferredas a request, which creates a new request number. With this type of update, you can also specifyselection criteria for the ODS object data.

2. Init Update:

The connected data target is filled with the active data from the ODS object. All of the followingdata is transferred with the delta. The request numbers remain supported. Thus, this option ismore transparent than the full update.

3. Fill Data Targets with Init/Deltas; Rebuild:

The connected data target is filled with the change log data. The request numbers remainsupported. This option is available if there are data targets that are already supplied from theODS object and are connected to new data targets.

The exact updating procedure has two different cases:

1. there are still no data targets that are provided with deltas from the ODS object

2. there are already data targets that are provided with deltas from the ODS object, andthere are new data targets that are not yet provided with init/delta

1. Case:

Choose, from the Context menu for the ODS object → Update ODS data in data targets. Youhave the choice between an init and a full update.

Or:

Choose the Reconstruct/Add button from the Reconstruct tabstrip in the administration of theconnected data target. Thus, the data target is filled initally with init/deltas.

2. Case:

© SAP AG of 17




Choose, from the Context menu for the ODS object → Update ODS data in data targets. An

information message appears, stating "In ODS object ... there are no new deltas to be updated".Confirm this message with Enter so that you can choose between

• a full update,

• an init update,

• and filling data targets initially with init/deltas.

When you make your selection, the system displays a data target selection for reconstructionfrom the ODS object with just the new data targets that can also be connected to the ODS object.By selecting the data targets and Enter , the data target reconstruction begins. In doing so, thesedata targets can also be provided with deltas from the ODS object later.

Or:

Choose the Reconstruct/Add button from the Reconstruct tabstrip in the administration of theconnected data target. Thus, the data target is filled initally with init/deltas.

4.4.2 Working with DataSources

Definition

Data that logically belongs together is stored in the source system in the form of DataSources.

A DataSource contains a number of fields in a flat structure used to transfer data into BW (ExtractStructure). It also describes the properties of the extractor belonging to it, as regards the datatransfer into BW. During a Metadata upload, the properties of the DataSource relevant to BW arereplicated in BW.

There are four types of DataSource:

• DataSources for transaction data

• DataSources for master data

These can be:

o DataSources for attributes

o DataSources for texts

o DataSources for hierarchies

Integration

DataSources are used for extracting data from a source system and for transferring data into theBW. DataSources make the source system data available on request to the BW in the form of theextract structure. Data is transferred from the source system into the SAP Business Information

Warehouse in the Transfer Structure. In the transfer rules maintenance, you determine how thefields of the transfer structure are transferred into the InfoObjects of the CommunicationStructure. You assign DataSources to InfoSources and fields to InfoObjects in the transfer rulesmaintenance.

© SAP AG of 17




Assigning DataSources to InfoSources and Fields to InfoObjects

Use

You carry out the assignment of a DataSource to an InfoSource in the BW transfer rulesmaintenance.

In the DataSource overview for a source system in the Administrator Workbench – Modeling,there is also the additional option of assigning an unmapped DataSource to an InfoSource. To dothis, choose a right mouse click on the DataSource and choose Assign InfoSource from thecontext menu. If you use this assignment option, you can

• Choose an InfoSource from a list containing InfoSources sorted according to the

agreement of their technical names

• Create a new InfoSource

Assign several DataSources to one InfoSource, if you want to gather data from different sourcesinto a single InfoSource. This is used, for example, if data from different IBUs that logicallybelongs together is grouped together in BW.

The fields for a DataSource are assigned to InfoObjects in BW. This assignment takes place inthe same way in the transfer rules maintenance.

For Business Content DataSources, the assignment to InfoSources, as well asthe assignment of fields to InfoObjects, is delivered by SAP.

4.4.3 Working with Persistent Staging Area (PSA)

Definition

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.

Use

The requested data is stored in an unchanged form in transparent, relational database tables inthe transfer structure. Consequently, they can also have errors if they already have errors in thesource system. When loading flat files, the data does not remain completely unchanged, sincethey are adjusted by conversion routines if necessary (for example, the date format 31.21.1999 isconverted to 19991231 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 loadingprocess from the further processing in BW.

The duration of the data storage in the PSA is medium-term, since it can still be used for reconstruction. However data storage when updating ODS objects is short-term.

© SAP AG of 17




.4.5 Administration

4.5.1 Transfer Business Content DataSources

Use

To use DataSources in the SAP BW System, it is necessary to transfer them from the relevantsource systems. Within this section you find all DataSources which should be transferred for allBuilding Blocks where SAP R/3 is involved.

Procedure

1. Transfer the DataSources from the relevant SAP R/3 Source System using transactionRSA13 in your BW system.

2. On the Administrator Workbench: Modeling screen choose a right mouse click on your R/3 Source System. From the context menu choose Customizing for the Extractors.

3. Choose Business Content DataSources Transfer Business Content DataSources.

Relevant DataSources

Application Component Relevant DataSources

SAP R/3 (SAP Application Components) All DataSources

SAP R/3 - IO (SAP Application Component Master Data) All DataSources

LO – IO All DataSources

FI – IO All DataSources

SD – IO All DataSources

MM - IO All DataSources

PI_BASIS 0CA_GD 0CA_GD-IO All DataSources

4.5.2 Activating Transfer Rules

Use

When you have maintained the transfer structure and the communication structure, you can usethe transfer rules to determine how the transfer structure fields are to be assigned to thecommunication structure InfoObjects. You can arrange for a 1:1 assignment. But you can also fillInfoObjects using routines or constants.

Prerequisites

Before you can maintain the transfer rules for an InfoSource, you must assign a source system tothe InfoSource and have created a communication structure.

© SAP AG of 17




Procedure

You have to activate the transfer rules. Data can only be loaded from the source system in anactivated version. The status of the transfer rules should be displayed with a green or a yellowtraffic 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. Thestatus is then displayed with a yellow traffic light.

A red traffic light indicates an error. The transfer rules cannot then be activated.

If the transfer rules cannot be activated it is possible to use the following workaround:

1. Choose the necessary InfoSource.

2. Right mouse click, choose Change Transfer Rules.

3. In the field Transfer Methode change the transfer method from PSA to IDOC.

4. Choose Save.

5. Afterwards mark PSA again. Choose Activate.

Result

The Transfer Rules have been activated now.

4.5.3 Warning Messages

When you transfer Business Content DataSources or activate business content, warningmessages may be displayed. These warning messages can be ignored, if they refer to objectsthat are not relevant for the scenario installation.

4.5.4 Scheduler

Definition

The scheduler is the connecting link between the source systems and the SAP BusinessInformation Warehouse. Using the scheduler you can determine when and from whichInfoSource, DataSource, and source system, data (transaction data, master data, texts or hierarchies) is requested and updated.

The principle behind the scheduler relates to the functions of SAP background jobs. The datarequest can be scheduled either straight away or it can be scheduled with a background job andstarted automatically at a later point in time.

You get to the data request via the Scheduler in the Administration Workbench Modeling, bychoosing InfoSource Tree → Your Application Component → Your InfoSources → Your Source

System → Context Menu (right mouse button) → Create InfoPackage.

Use

Data is requested for a combination of application components, an InfoSource, a DataSource,and a source system.

© SAP AG of 17




When requesting data, create an InfoPackage in the InfoSource tree in the Administrator Workbench. In the InfoPackage, you set the conditions for the scheduling of the data request.Therefore an InfoPackage is always assigned to just one InfoSource, one DataSource to the datatype that goes with it (transaction data, master data, texts, or only ever one hierarchy), and to onesource system.

When creating an InfoPackage, this is saved with the current Variant Settings as administrative

information.

Integration

The scheduler helps to load and update the data into the BW system. You can check the BWloading and processing processes in the Administrator Workbench Monitor. The data is availablefor analysis after the BW processing process.

Scheduling Data Upload Periodically

To create an InfoPackage in order to load transaction data refer to the section Loading Transaction Data in any building block configuration guide.

To schedule a perodical data upload create an InfoPackage in order to upload transaction data.

On the Schedule tab of the Scheduler (Maintain InfoPackage) screen carry out the followingsteps:

1. Choose the radio button Start Later in Background .

2. In the Start time dialog box choose Date/Time.

3. Enter the Scheduled start date and time.

4. Choose Period values.

5. In the Period Values dialog box choose the preferred time interval and choose Save.

6. In the Start time dialog box choose Periodic job and then choose Save.

7. In the Periodic Processing screen area, enter the number of runs after which you want to

cancel the job or choose Do not cancel job.You can subsequently change the scheduling by choosing the Scheduling Options button.

4.5.5 Loading Master Data / Texts / Hierarchies

Use

For loading the Master Data it is necessary to select the relevant DataSources for Master DataCharacteristics.

To do this, look for the InfoCube.

1. From the context menu choose InfoSource Overview .

You see the status of all InfoSources related to this InfoCube.

2. To upload the relevant data choose Expand Tree to this InfoSource.

3. Then load master data attributes/ texts hierarchies for the InfoSources (for someInfoSources only texts or master data are available).

With the monitor you can check the data loading process and data processing in BW and analyzeerrors.

© SAP AG of 17

i00 bb configguide en de

Documents