how to check your bw system before go-live

7/23/2019 How to Check Your BW System Before Go-Live

1/17

How to

Check your BW system before

Go-LiveBUSINESS INFORMATION WAREHOUSE

ASAP How to Paper

Applicable Releases: BW 2.0B, 2.1C

July 2001

SAP (SAP America, Inc. and SAP AG) assumes no responsibility for errors or omissions in these materials.

These materials are provided as is without a warranty of any kind, either express or implied, including but not limited to, the impliedwarranties of merchantability, fitness for a particular purpose, or non-infringement.

SAP shall not be liable for damages of any kind including without limitation direct, special, indirect, or consequential damages thatmay result from the use of these materials.

SAP does not warrant the accuracy or completeness of the information, text, graphics, links or other items contained within thesematerials. SAP has no control over the information that you may access through the use of hot links contained in these materialsand does not endorse your use of third party web pages nor provide any warranty whatsoever relating to third party web pages.


2/17

HOWTOCHECKYOUR BW SYSTEMBEFORE GO-LIVE

1 Business Scenario

A customer is getting ready to Go-Live with their BW system. They would like to check the system

to make sure that some important settings have been maintained.

2 The Result

Use the following checklist as a guide to check your BW system prior to going into production. Thischecklist is designed to give you an overview of some common settings that need to be maintainedbut are sometimes overlooked and is not inclusive. Several other sources of information areavailable including the BW ASAP Methodology, and Going Live checks performed by the TCCgroup.

3 The Step By Step Solution

1. Transfer global settings. GotoAdministrator Workbench ->Modeling -> Source Systems.

Select an R/3 source system ->right-click and choose Transferglobal settings.

2001 SAP AMERICA, INC. AND SAP AG


3/17


Select Currencies and choose atransfer mode.

Simulation - The transfer ofCustomizing tables/exchange ratesis simulated. No data is updated.

Update tables - The Customizingtables/exchange rates are collectedfrom the source system. The newentries are updated on thedatabase.

Rebuild tables - The Customizingtables/exchange rates are collectedfrom the source system. The tablesare rebuilt, old data is deleted.

Then Execute.

Repeat these steps for Units ofmeasurement, Fiscal year variants,and Factory calendar for each R/3source system in BW.



4/17


2. Transfer exchange rates. GotoAdministrator Workbench ->Modeling -> Source Systems.Select an R/3 source system ->right-click and choose Transfer

exchange rates.

Maintain Exchange rates and thetransfer mode.

Simulation - The transfer ofCustomizing tables/exchange ratesis simulated. No data is updated.

Update exchange rates - TheCustomizing tables/exchange ratesare collected from the sourcesystem. The new entries areupdated on the database.

Transfer exchange rates again -The Customizing tables/exchangerates are collected from the sourcesystem. The tables are rebuilt, olddata is deleted.

Then Execute.

Repeat these steps for each R/3source system in BW.



5/17


3. Maintain the permitted extracharacters. Goto -> SAP EasyAccess Menu -> SAP menu ->BW Administration -> PermittedCharacters. Another path is

transaction SPRO -> SAPReference IMG -> BWCustomizing ImplementationGuide -> Business InformationWarehouse -> General BWSettings -> Maintain permittedextra characters, or usetransaction RSKC.

4. Release the BW functionmodules that are required forweb reporting. This step is for

system security purposes and isdone by your TechnicalAdministrator. The functionmodules that must be releasedare listed to the right.

WEBQUERY (for BEx web queries - WebRFC)

RSBB_WWW_BROWSER_GATE (Browser)

RSBB_WWW_BROWSER_TREE (Browser)

RSBB_WWW_NODES_READ (Browser)RSBB_WWW_NODES_SEARCH (Browser)

RSBB_WWW_TITLEBAR (Browser)

WWW_ALV_CALL (InfoSet web queries)

WWW_ALV_SELSCREEN (InfoSet web queries)

FLOW_LOGIC_ALV_CALL (InfoSet web queries)

From the SAP Easy Access menu,choose SAP menu ->Tools ->

Business Engineer -> BWCustomizing (transaction SPRO)-> SAP Reference IMG -> BusinessInformation Warehouse ->Reporting-relevant Settings -> WebReporting -> Releasing theFunction Module for Web Reporting-> select Internet Release from themenu -> Function Modules.Release.

Note: The local web browser must

be set to accept "per session"cookies; otherwise, the user willget "Invalid Session" error messagewhen starting the BEx Browser forthe Web. The local web browsermust also support the execution of

JavaScript.



6/17


5. Check the read mode forqueries.

For a query, the OLAP processorcan read the data from the facttable in one of three ways:

Reading all of the data

When executing the query in theBusiness Explorer all of the facttable data that is needed for allpossible navigational steps in thequery, is read in the main memoryarea of the OLAP processor.

Therefore, all new navigationalstates are aggregated andcalculated from the data of the

main memory.Reading the data on demand

The OLAP processor only requeststhe corresponding fact table datathat is needed for eachnavigational state of the query inthe Business Explorer. Therefore,new data is read for eachnavigational step. The mostsuitable aggregate table is usedand, if possible, already

aggregated on the database. Thedata for identical navigationalstates are buffered in the OLAPprocessor.

Reading on demand whenexpanding the hierarchy

When reading data on demand (2),the data for the entire - meaningcompletely expanded - hierarchy isrequested for a hierarchydrilldown. For the read on demand

when expanding the hierarchy (3),the data is aggregated by thedatabase along the hierarchy andis sent to the start level of thehierarchy (highest node) in theOLAP processor. When expanding ahierarchy node, the children of thenode are then respectively read ondemand.



7/17


In general, the reading of data ondemand (2) provides much betterperformance than reading all thedata (1). This read mode shouldespecially be considered for

queries with many, freecharacteristics. A query thatcontains two or more freecharacteristics from differentdimensions (e.g. 'Customer' and'Product'), will probably only beefficiently executable in this mode,as the aggregates can only beoptimally used when reading thedata on demand.For large hierarchies, aggregatesshould be created on the middle

level of the hierarchy and the startlevel of the query should besmaller or the same as thisaggregate level. For queries aboutsuch large hierarchies, the read ondemand when expanding thehierarchy method (3) should beset.

Execute transaction RSRT andenter =RMRP into the OK field.

After choosing Return, the readmode of your queries is the readmode recommended by SAP.



8/17


6. Switch off all system traces.Execute transaction ST01.

Trace status should be set toTrace switched off.

Check trace tool. Goto transactionRSRTRACE. Verify there are nousers activated for logging. Userscan be removed by selecting theUser -> select Deactivate user.



9/17


Check BW Reporting AuthorizationCheck Log. Goto transaction RSSM-> Authorizaton Check Log. Selecta user to remove -> Remove Userfrom List.

7. Check number ranges foraggregates.

When you activate an aggregate, a number isgenerated from number range objectRSDDAGCUBE. When you first activate theaggregate, this number range has no intervalassigned. If you activate the aggregatemanually, the interval is created. The activationprocess in the after-import method after thetransport is generally executed in client '000'.For technical reasons it is not possible to create number range interval in a client other than theBW client.

Execute programRSDDK_AGGR_CREATE_INTERVAL_20B in transaction SA38.

Otherwise, you must eithermanually activate the firstaggregate in a new system or youmust create an interval for the

number range object in NumberRange Object Maintenance(Transaction SNUM). The rangemust be defined as follows:

No = '01'; From number ='100000'; To number = '199999';Current number ='0'.



10/17


Note that you must create theinterval in the client in which theBW is operating.

Check Indexes and DB statistics foreach InfoCube. Goto transactionRSA11 -> select an InfoCube ->right-click and choose Manage ->select Performance tab. Indicescan be deleted before the loadprocess by using Delete indexesand recreated after the loading isfinished with Repair indexes. Thisaccelerates the data loading.However, simultaneous readprocesses to a cube are negativelyinfluenced as they slow downdramatically. Therefore, thismethod should only be used if noread processes take place duringthe data loading. Statisticsinformation can be automaticallyupdated after the load process isfinished following the sameprocess used for indices. This isgenerally recommended. Only ifvery little data is loaded (in

comparison to the quantity of thatwhich already exists), then thisoption should be avoided. Theseprocesses should be runautomatically on a scheduledbasis.

8. Maintain the extraction settingsfor each source system. In R/3source system goto transactionSBIW -> General Settings ->Maintain Control Parameters forData Transfer.



11/17


1. Source System

Enter the logical system of yoursource client and assign the controlparameters you selected to it.

You can find further information onthe source client in the sourcesystem by choosing the transactionSCC4.



12/17


2. Maximum Size of the DataPacket

When you transfer data into BW,the individual data records are sentin packets of variable size. You can

use these parameters to controlhow large a typical data packet likethis is. If no entry was maintainedthen the data is transferred with adefault setting of 10,000 kBytesper data packet. The memoryrequirement not only depends onthe settings of the data packet, butalso on the size of the transferstructure and the memoryrequirement of the relevantextractor.

3. Maximum Number of Lines in aData Packet.

Upper-limit for the number ofrecords per data packet.

The default setting is 'Max. lines' =100000.

The maximum main memory spacerequirement per data packet is

aroundmemory requirement = 2 * 'Max.lines' * 1000 Byte, meaning 200MByte with the default setting.

4. Frequency

The specified frequencydetermines the number of IDocsthat an Info IDoc is to be sent to, orhow many data IDocs an Info Idocdescribes.

Frequency 1 is set by default. Thismeans that an Info Idoc followsevery data Idoc. In general, youshould select a frequency between5 and 10 but no higher than 20.

The bigger the data IDoc packet,the lower the frequency setting



13/17


should be. In this way, when youupload you can obtain informationon the respective data loading inrelatively short spaces of time.

With the help of every Info IDoc,

you can check the BW monitor tosee if there are any errors in theloading process. If there are none,then the traffic light in the monitorwill be green. The Info IDocscontain information such aswhether the respective data IDocswere uploaded correctly.

5. Maximum number of parallelprocesses for the data transfer.

An entry in this field is onlyrelevant from release 3.1I onwards.Enter a number larger than 0. Themaximum number of parallelprocesses is set by default at 2.

The ideal parameter selectiondepends on the configuration ofthe application server, which youuse for transferring data. Gototransaction OS06 and use Countvalue as a maximum.

6. Batch job target system

Enter the name of the applicationserver on which the extraction jobis to be processed. To determinethe name of the application server,choose Tools -> Administration ->Monitor -> System monitoring ->Server. The name of theapplication server is displayed inthe column Host name.



14/17


Save the entry.

9. Maintain the Flat File sourcesystem settings. In BW, gototransaction SPRO -> SAPReference IMG -> Business

Information Warehouse -> Linksto Other Systems -> MaintainControl Parameters for the datatransfer.

1. Maximum size of data packets

For data transfer into BW, theindividual data records are sent inpackets of variable size. You usethese parameters to control how

large such a data packet typicallyis. If no entry is maintained, thedata is transferred with a standardsetting of 10,000 kbyte per datapacket. The memory requirementdepends not only on the setting fordata packet size, but also on thewidth of the transfer structure, andthe memory requirement of therelevant extractor.

2. FrequencyWith the specified frequency, youdetemine after how many dataIDocs an Info IDoc is sent, or howmany data IDocs are described byan Info IDoc.

The frequency is set to 1 bydefault. This means that an Info



15/17


IDoc follows every data IDoc.Generally, choose a frequency ofbetween 5 and 10, but not greaterthan 20.

The larger the packet size of a data

IDoc, the lower you must set thefrequency. In this way you ensurethat, when loading data, youreceive information on the currentdata load status at relatively shortintervals.

In the BW Monitor you can useeach Info IDoc to see whether theloading process is running withouterrors. If this is the case for all thedata IDocs in an Info IDoc, then the

traffic light in the Monitor is green.One of the things the Info IDocscontain information on, is whetherthe current data IDocs have beenloaded correctly.

Save the settings.



16/17


10. Schedule the realignment runto be executed periodically. InBW, goto Tools -> ApplyHierarchy/Attribute Change...

Choose Selection and thenmaintain the start time. SelectSave.



17/17


A variant can also be set up.Select maintain variant icon.

Enter a variant and select Create.

Maintain the parameters. SelectEnter. Choose the Selection icon toschedule.


how to check your bw system before go-live

Documents