How to and what to check in your BW system before GO-Live
Before going to production your BW system ,please check the below things….
Steps
Transfer
global settings. Goto Administrator Workbench -> Modeling ->
Source Systems. Select an R/3 source system -> right-click and choose
Transfer global settings.
Select Currencies and choose a transfer mode.
Simulation - The transfer of Customizing tables/exchange rates is simulated. No data is updated.
Update
tables - The Customizing tables/exchange rates are collected from the
source system. The new entries are updated on the database.
Rebuild
tables - The Customizing tables/exchange rates are collected from the
source system. The tables are rebuilt, old data is deleted.
Then Execute.
Repeat these steps for Units of measurement, Fiscal year variants, and Factory calendar for each R/3 source system in BW.
Transfer
exchange rates. Goto Administrator Workbench -> Modeling ->
Source Systems. Select an R/3 source system -> right-click and choose
Transfer exchange rates.
Maintain Exchange rates and the transfer mode.
Simulation - The transfer of Customizing tables/exchange rates is simulated. No data is updated.
Update
exchange rates - The Customizing tables/exchange rates are collected
from the source system. The new entries are updated on the database.
Transfer
exchange rates again - The Customizing tables/exchange rates are
collected from the source system. The tables are rebuilt, old data is
deleted.
Then Execute.
Repeat these steps for each R/3 source system in BW.
<!--[if !supportLists]-->1. <!--[endif]-->Check the read mode for queries.
For a query, the OLAP processor can read the data from the fact table in one of three ways:
Reading all of the data
When
executing the query in the Business Explorer all of the fact table data
that is needed for all possible navigational steps in the query, is
read in the main memory area of the OLAP processor. Therefore, all new
navigational states are aggregated and calculated from the data of the
main memory.
Reading the data on demand
The
OLAP processor only requests the corresponding fact table data that is
needed for each navigational state of the query in the Business
Explorer. Therefore, new data is read for each navigational step. The
most suitable aggregate table is used and, if possible, already
aggregated on the database. The data for identical navigational states
are buffered in the OLAP processor.
Reading on demand when expanding the hierarchy
When
reading data on demand (2), the data for the entire - meaning
completely expanded - hierarchy is requested for a hierarchy drilldown.
For the read on demand when expanding the hierarchy (3), the data is
aggregated by the database along the hierarchy and is sent to the start
level of the hierarchy (highest node) in the OLAP processor. When
expanding a hierarchy node, the children of the node are then
respectively read on demand.
considered for queries with many, free
characteristics. A query that contains two or more free characteristics
from different dimensions (e.g. 'Customer' and 'Product'), will probably
only be efficiently executable in this mode, as the aggregates can only
be optimally used when reading the data on demand.
For large hierarchies, aggregates should be created on the middle level of the hierarchy and the start level of the query should be smaller or the same as this aggregate level. For queries about such large hierarchies, the read on demand when expanding the hierarchy method (3) should be set.
<!--[if !supportLists]-->1. <!--[endif]-->Maintain
the extraction settings for each source system. In R/3 source system
goto transaction SBIW -> General Settings -> Maintain Control
Parameters for Data Transfer.
1. Source System
Enter the logical system of your source client and assign the control parameters you selected to it.
You can find further information on the source client in the source system by choosing the transaction SCC4.
2. Maximum Size of the Data Packet
When
you transfer data into BW, the individual data records are sent in
packets of variable size. You can use these parameters to control how
large a typical data packet like this is. If no entry was maintained
then the data is transferred with a default setting of 10,000 kBytes per
data packet. The memory requirement not only depends on the settings of
the data packet, but also on the size of the transfer structure and the
memory requirement of the relevant extractor.
3. Maximum Number of Lines in a Data Packet.
Upper-limit for the number of records per data packet.
The default setting is 'Max. lines' = 100000.
The maximum main memory space requirement per data packet is aroundmemory requirement = 2 * 'Max. lines' *
1000 Byte, meaning 200 MByte with the default setting.
4. Frequency
The
specified frequency determines the number of IDocs that an Info IDoc is
to be sent to, or how many data IDocs an Info Idoc describes.
Frequency
1 is set by default. This means that an Info Idoc follows every data
Idoc. In general, you should select a frequency between 5 and 10 but no
higher than 20. The bigger the data IDoc packet, the lower the frequency
setting should be. In this way, when you upload you can obtain
information on the respective data loading in relatively short spaces of
time.
With
the help of every Info IDoc, you can check the BW monitor to see if
there are any errors in the loading process. If there are none, then the
traffic light in the monitor will be green. The Info IDocs contain
information such as whether the respective data IDocs were uploaded
correctly. So many more settings we need to do ..wl try to upload the document for this..
This stuff is basically collected directly from SAP..
No comments:
Post a Comment