Post Activities after BW Installation Release 3.5

Transcription

Post Activities
after BW Installation
Release 3.5
Roland Kramer
SAP Switzerland
Page 1
Post Activities BW Release 3.5
Contents:
z Technical settings for BW
z BW basis customizing
z Enabling the BW Application
z BW basis tuning
z Tips & tricks
© SAP AG 2003, Setup BW 3.5, Roland Kramer / 2
Page 2
Post Activities BW Release 3.5: Unit Objectives
After completing this unit, you will be able to:
z Proceed with technical BW-specific tasks after the
standard installation
z Understand the necessary technical jobs and tasks
for supporting the BW application
z Do the Basis Customizing for the BW application
z Prepare the data loading for the BW application
z Set up and tune the productive usage of the BW
system
Page 3
Post Activities BW Release 3.5: Business Scenario
z You are a technical basis BW consultant and have to
set up the BW system for its productive use. You will
therefore have to understand the tasks reqired in
addition compared to R/3 in order to successfully
enable the BW core application.
In addition, you should get familiar with the BW
Basis Customizing which enables the BW
application people to achieve a faster go live of the
productive usage.
So it also good to know how to set up and implement
some basis tuning settings at an early stage, check
them and finalize them at a later stage.
Page 4
Technical Background of the BW Server 3.5
BW 3.5 technology
dev.class from 6.40
ABAP basis 6.40
Kernel 6.40/WAS
Server 3.5
Ken documentation
BC 3.5.1 BC 3.5.2 BC 3.5.3
BW Add-On 3.5
GUI 6.40C4
final version
Front-end
IGS 6.40
Web Reporting
This graphic show you the used components together with BW 3.5 and it is devided in the
modules server 3.5, Front-end and web Reporting.
Page 5
BW - Post Activities Basis - 1
Check the Basis tools tp, R3trans, Kernel, etc.
Perform a client copy and set the default client in the default
profile and restart your SAP system, otherwise you cannot
work in the client 000 due BW system restrictions.
(login/system_client = <client>).
Check your Installation with SM21, SM28.
Check your code pages with SE38 => RSCPINST
(not for UNICODE).
Run transaction STMS and check the transport tool
z
At least one virtual system and one transport layer
z
Check parameter NBUFORM and set it to 1 in the transport profile
z
Insert parameter NO_IMPORT_ALL = 1 to the transport profile
Set the initial screen for the BW system with SSM2

For the BW system: RS00

For the SEM system: UG00
Check note for more details
Page 6
BW Post Activities – Oracle Database
Apply Note 192658 - basis parameter for BW systems
Check Note 180605 - parameter for BW with Oracle
For Release 9.2.x see Note 632556
For Release 10.1.x see Note 830576
Check Note 702728 for export/import buffer settings
Check Note 480710 for table buffer settings
Check Note 565075 - Recommendations for BW systems with
Oracle 8.1.x (Foundation Note)
Apply the latest patch for the Oracle 9.2 database
Install the latest OUI (10.1.0.4.0 bundled with patch 9.2.0.7.0)
Install the latest main patch (9.2.0.7.0) and merge corrections
Install the latest interim patch (Note 695080) with OPatch version
1.0.0.0.53 or higher (Note 306408) with the actual Perl version from
ActivePerl (5.8.0.806)
Note 640910: Problems when using OPatch
Note 719928: OPatch problems after installation of Oracle 9.2.0.x
Note 629588: Current versions of OPatch and OUI
Note 539921: Current patch set for Oracle 9.2.0
Note 755629: KKO merge fix for Oracle 9.2.0.5
Note 828483: ORA-00600: [KCOAPL_BLKCHK]
Note 834100: Merge fix for Oracle 9.2.0.6
Note 896903: Optimizer Merge Fix for 9.2.0.7
Note 720886: Oracle 10g: Integration in the SAP environment (Q1/2005)
Note 819829: Oracle Database 10g: Instant Client 10.x on Unix
Page 7
BW – Additional Scripts and Tasks for ORACLE
Note 519448 - performance problems when deactivating aggregates

@cat_index.sql
Note 565416 - performance during Oracle dictionary accesses is slow

@catspace_sap_bw.sql
Î check with Note 871455 and refer to Note 762962
Note 650796 - Collecting Note: ORA-00980

@sap_indexes_views.sql
Note 519407 - performance problems in deactivating aggregates

@fixfor_bug2264056.sql
Note 558746 - Better Oracle Data Dictionary BW performance

@558764_DDIC.sql
Note 762962 - Performance on DBA_SEGMENTS with Oracle 9i

@762962_DBA_SEGMENTS.sql
The scripts can be found under http://service.sap.com/swcenter-3pmain
Æ oracle Æ other Æ scripts, or find the script in the mentioned Note.
Description
To ensure data consistency and read consistency in an Oracle database system, Oracle uses
rollback segments. Up to now, the sizes, numbers, storage parameters and so on of these
rollback segments (which, in an SAP system, are usually in the PSAPROLL of the tablespace
mentioned) had to be configured manually, depending on the system requirements. In
addition, the instance had to be informed of the existing rollback segments using the
'rollback_segments' profile parameter. For particularly long-running transactions, you could
assign a particularly large rollback segment to a certain transaction. To avoid ORA-1555
(snapshot-too-old) error messages, you could try changing the number or the size of rollback
segments. However, this did not mean that you could never prevent ORA-1555 error
messages with certainty.
With Oracle9I, the Oracle server can now manage rollback segments completely
automatically. This feature is called 'Automatic Undo Management', or 'AUM' for short, while
the new rollback segments are now called 'Undo segments'. A database instance that
activated AUM runs in 'Automatic Undo Management mode'.
A special tablespace called Undo Tablespace (LMTS, Autoallocate) is created for AUM. When
you activate this tablespace, a specific 'Undo segments' number is created automatically in it
(initial 10). These have the new 'TYPE2 UNDO' segment type as opposed to 'ROLLBACK' as
a segment type of rollback segments. The segment names of these Undo segments are also
created automatically ('_SYSSMU$').
Four new profile parameters were imported in Oracle9I for AUM: undo_management,
undo_tablespace, undo_retention, undo_suppress_errors . With 'undo_management'
(MANUAL or AUTO), you can switch between manual and automatic Undo Management
modes. 'undo_tablespace' specifies the active Undo tablespace.
Page 8
Parameters from Note 632556 (init<SID>.ora) 9.2.0
_b_tree_bitmap_plans
= false
_optim_peek_user_binds
= false
_eliminate_common_subexpr
= false
compatible
= 9.2.0.x.y (the exact Release)
db_block_checksum
= FALSE
db_cache_size
= xxxM
db_file_multiblock_read_count
= 32
hash_join_enabled
= true
open_cursors
= 800
optimizer_features_enable
= 9.2.0
optimizer_max_permutations
= 2000
parallel_threads_per_cpu
=1
pga_aggregate_target
= 20 % of Main Memory
star_transformation_enabled
= true
sga_max_size
= xxxxxM or G
timed_statistics
= true
transaction_auditing
= false
workarea_size_policy
= auto
Note 554112: Important Changes in Oracle9i
- sqlplus /nlolog substitutes svrmgrl
- „connect / as sysdba“ substitutes „connect internal“
- 'analyze table ... validate structure online;' does not lock table
- spfile (server parameter file)
Note 598678: Oracle 9i: New functions (composite SAP Note)
Note 601157: Oracle9i: Server parameter File (sp-file)
Note 600141: Oracle9i: Automatic UNDO Management (AUM)
Note 617416: Oracle9i: Dynamic SGA
Note 619876: Oracle9i: Automatic PGA Tuning
Note 683075: Oracle9i: Default Temporary Tablespace
Note 706625: Oracle9i: locally-managed system tablespace
Note 647697: BRSPACE - New tool for Oracle database administration
Note 646681: Reorganizing tables with BRSPACE
Note 669902: Oracle9i: Setting the National Character Set to UTF8
Note 539922: Installing the ORACLE client software 9.2.X for UNIX
Page 9
Parameters from Note 192658
rsdb/obj/buffersize
= 131072 (about 128 MB)
rsdb/obj/max_objects
= 20000
rsdb/obj/large_object_size
= 16384 (about 16 MB)
abap/buffersize
= 400
rtbb/buffer_length
= 100000 (see Note 480710)
rtbb/max_tables
= 2000
rdisp/max_wprun_time
= 3600
gw/cpic_timeout
= 60
dbs/ora/array_buf_size
= 1000000 (about 1 MB)
rsdb/esm/buffersize_kb
= 131072
rsdb/esm/max_objects
= 20000
rsdb/esm/large_object_size
= 16384
rsdb/esm/mutex_n
=0
Export/import buffer
As this buffer is used a lot in BW systems, the export/import buffer should be set to at least
10MB. If you work with large hierarchies, this buffer may even need to be increased
considerably. You should be able to store at least 5000 objects in the buffer. The buffer should
be set to a higher value than recommended for BW 2.x systems
Program buffer (abap/buffersize)
The program buffer should be between 200 and 400 MB, depending on the amount of main
memory available. Unlike in R/3 systems, a higher number of programm buffer swaps is less
important in BW systems and is often unavoidable because the reusability of information
stored in the program buffer is significantly less. While the response time of R/3 transactions is
only around several hundred milliseconds, the response times of BW queries is seconds. You
can only improve performance by milliseconds by tuning the program buffer. If the main
memory available is limited, the extended memory should be increased. However, the
program buffer should not be set lower than 200MB. If sufficient main memory is available,
the program buffer in BW 2.X/3.X systems should be set to at least 300MB.
Extended Memory
BW users require significantly more Extended Memory than R/3 users. The size of the
extended memory is related to the available main memory but should not be lower than 512
MB.
Single Record buffer
BW 2.x & 3.x: The buffer should be set as recommended for R/3 4.6 systems (see Note
103747). Limits for BW 2.x: See Note 414220 for the values for parameters rttb/max_tables,
rtbb/buffer_length. Certain limits must not be exceeded under any circumstances. Limits for
BW 3.x: See Note 480710.
Page 10
Check Consistency with Tables TSORA and TAORA
See Note 552911
and 502989 for
details.
Additional Information are also found in Note 33814: Warnings of inconsistencies
between database & R/3 DDIC
Reason and Prerequisites
There has been a reduction in the number of tablespaces to be created since the shipment of
products based on Basis 6.10 (in other words, since BW 3.0A). Essentially, the following
changes are involved:
There is no longer a split between index and data tablespace
The tablespace names for SAP data contain the SAPsystemNAME
The tablespace set (= number of tablespaces) was reduced. Therefore, only the following
tablespaces are created:
PSAPsystem, PSAPROLL, PSAPTEMP for the database dictionary, temporary data and
rollback segments
PSAP<SAPsystemNAME><RELEASE> for tables of previous exchange tablespaces
PSAP<SAPsystemNAME>USR for user-specific tables
PSAP<SAPsystemNAME> for all remaining tables
Solution
If you want to create BW-specific or other additional tablespaces, no division should be made
between the index and data tablespace, in accordance with the new conventions, and the
SAPsystemNAME should be included in the tablespace name. The following BW tablespaces
are created as a result:PSAP<SAPsystemNAME>ODS, PSAP<SAPsystemNAME>FACT and
PSAP<SAPsystemNAME>DIM.
Page 11
Which Type of Support Package to use with BI 3.5
WP-PI 6.00 is
Integrated in the
Basis PI (PIB)
Up to 6.40 Base
System every R/3
based system needs
the R/3 PI
This is also valid for ERP2004
Dependencies of Support Packages
R/3 PI
2004.1
ECC
5.0
BI BC
3.5.x
SEM
4.0
FIN
3.0
XI
3.0
SAP SPAM/SAINT 6.40
BI 3.5 is part of the
Netweaver 04 Stack
The SAP PIB is
integrated with the
Netweaver Stack
New with Basis 6.40
is the integration of
the other PI’s like
WP-PI in the Basis PI
SAP_BI 3.5
Net
SAP PIB 2005_1_640
Weaver
SAP_ABA, 6.40
04
SAP_BASIS, 6.40
SAP
KW
7.0
SAP Kernel 6.40
SAP ECC (ECC = ERP Central Component) as replacement of SAP R/3 Enterprise
Compared to SAP R/3 Enterprise, in SAP ECC there are architectural changes with respect to
Enterprise Services Architecture, enhanced usability and new developed functionality, like the
new general ledger
SAP ECC 5.00 is the central component of mySAP ERP 2004 (ECC = ERP Central
Component)
Making full use of SAP NetWeaver
Page 12
Import Support Package stack for BW 3.5
Apply the newest SPAM/SAINT update from SAPNet (6.40/0019)
Apply the SAP Basis support stack for 6.40
Î 16
Apply the SAP application support stack for 6.40
Î 16
Apply the SAP BW support stack for 3.5
Î 16
Apply the SAP BW support stack for 3.5.3
Î8
Apply the PIB 2005_1_640 stack (PIB)
Î 6*
* PIB 2005_1_640 is mandatory for the installation of Stack 14 or higher
Check the latest correction for the actual Stack with the BI Homepage
http://service.sap.com/bi Î SAP BI 3.5
Check with Note 672651: OCS: Known problems with support
packages in basis rel. 6.40
SPAM/SAINT Update
Latest Information for SAP Web AS Release 6.40
SPAM/SAINT Update Version 6.40/0019:
Developments and adjustments in the SPAM/SAINT functionality which is necessary for the
upgrade to SAP ERP 2005.
Improved behavior and handling if modifications have to be adjusted.
Improved and more consistent user interface if errors occur during the preparation phases
CHECK_REQUIREMENTS, TEST_IMPORT, OBJECTS_LOCKED_?,
ADDON_CONFLICTS_?.
Redesign of internal queue calculator functions.
The steps during a queue calculation are logged now. This log can be used to get details
about the recent queue calculation or to derive reasons why the queue calculation does not
lead to the desired result or fails at all.
Assured compatibility to new versions of the SAPCAR utility (in function 'Load from Frontend').
Fixed a potential problem with too long tp parameters.
Fixed a potential problem of the codepage conversion into special codepages during upload of
OCS Packages.
Fix of a serious error in the Support Package queue calculation of the Add-On Installation Tool
(SAINT). This error was introduced with SAINT version 0016 (see note 672652).
Page 13
Suggested Patches/PI Installation Queue
Install PI_BASIS 2005_1_640 according to note 821148 and all
available support packages (4), before applying Stack 14.
password
install 6AD13FA7C9
password
delta
6AD13FA8C9
Update BI_CONT 3.5.2 according to note 717812 and all available
support packages (3), password A9C99F62C5
Update BI_CONT 3.5.3 according to note 774933 and all available
support packages
2DCFC710F5
(installation)
2DCFC70CF5
(delta upgrade of 351)
2DCFC71D8D
(delta upgrade of 352)
Update FINBASIS 300 and SEM-BW 400 according to note 614927
and the latest available support packages (currently 5), password
FINBASIS 200: FB4DE2C9B4, SEM-BW 350: no password
The XI Infrastructure Plug In 3.00 is included in the
PI_BASIS_2004_1_640 and higher. No additional tasks to do.
To install
BI_CONT 3.5.2, you need to install SAP_BW 3.5.2 Support Package 02. To install BI_CONT
3.5.2 Support Package 01, SAP_BW 3.5 Support Package 03 is required. To install BI_CONT
3.5.2 Support Package 02, SAP_BW 3.5 Support Package 04 is required.
BI_CONT 3.5.1, you must first install SAP_BW 3.5 Support Package 01.
To use:
BI_CONT 3.5.2, we recommend that you install SAP_BW 3.5 Support Package 03 or higher
as of Support Package 01.
Most of the BI Content objects are 'pure' and specific Content objects such as InfoCubes,
update rules, queries, InfoSources, transfer rules, roles and so on. These objects are delivered
in the "D" version and may, during installation (transfer to the "A" - active - version), be
compared with the corresponding objects that were active in the customer system at the time
of the upgrade. The customer decides whether he/she wants to overwrite the old version,
continue to use it or only transfer the changes. Therefore, during the Content release upgrade,
you do not have to carry out regression tests in most areas.
In the last BI_CONT releases, however, function modules were also delivered in some
scenarios. Since the ABAP objects do not have any versioning and the new, changed version
overwrites the old version, customers that use the relevant Content areas have to carry out
regression tests after the upgrade. The list of InfoProviders affected by the changes to the
function modules are added to these notes.
Page 14
More Post Activities for SAP and Oracle Fixes
Check for your support package stack of BW 3.5 the additional
Notes for Correction. Use Transaction SNOTE to implement the
correction (Example with BW 3.5 Patches).
After SP12 for BW 3.5, Note 763340
The current configuration (sp-stack)
Please check at: http://service.sap.com/sp-stacks
Check the interim patches for Oracle 9.2.0.5.0 or higher
Note 539921: Current patch set for Oracle 9.2.0
Note 755629: KKO merge fix for Oracle 9.2.0.5
Note 577365: BW: SQL statement runs indef., ORA-01436 (>=Oracle 9.2.0.2)
For problems with the tools unzip, perl and OPatch see notes:
Note 306408: OPatch: Oracle tool for patch installation
Note 640910: Problems when using OPatch
Summary Notes / SAPBWNEWS Notes
Please note: If SAP detects any problems that might occur after the application of the support
package, we will immediately provide a note on how to avoid or fix the problem. This
information will also be provided in the SAPBWNEWS-note. Thus, when applying a SAP BW
3.5 support package , we recommend to subscribe to this note (see below) in order to get all
the info available on this support package.
Note 695423 contains additional important and necessary information about importing support
packages for BW 3.5, which do not refer to a special support package, such as a required
level patch for the Basis system, for example, or obligatory requirements when importing
support packages as well as information about problems that are actually caused by other
systems but can affect your BW 3.5 system.
This note subject to regular changes. We therefore urgently recommend that you refer to this
note before you import the support package or that you subscribe to this note (see note
487366).
Page 15
BW 3.5 - Applying Front-End Patches
Get the front-end updates for the front-end 6.40 from
http://service.sap.com /patches
http://service.sap.com/patches
Installing Packages using the Logon Script - Use

Since the front-end software is normally installed on a large number of computers, SAPsetup
allows you to automate this task as well as take advantage of SMS integration.

By inserting a command line into the logon scripts of the computers on which the front-end
software is to be installed, you can start a package installation each time the user logs on.
Procedure

Insert the following command line (both the path and either the package name or unique
package identifier must be used):
y
\\<server>\<shared folder>\setup\sapsetup.exe /p:“<package name>“ or
y
\\<server>\<shared folder>\setup\sapsetup.exe /p:“<unique package identifier>“

The unique package identifier is automatically generated when you create a package. It
cannot be altered. Run SAPAdmin and select the package to see its unique package
identifier. It is better to use the unique package identifier rather than the name, because the
name need not be unique and can be changed.

Starting this command line for the very first time on a computer, SAPsetup will install the
specified package.

Starting the same command line again on the next logon, SAPsetup checks whether the
installed package is still up-to-date. If the installation server has been updated by a front-end
patch since the last logon, SAPsetup will re-install the updated components. The front-end
software (especially SAP GUI) should not be running at the same time because program files
in use could cause a reboot.
Page 16
Overview of SPs in BW 3.5 with SPAM
SPAM 640/0016: bug fix in the support package browser;
all relevant support packages are displayed now.
Support Package Manager - SPAM
The Support Package Manager is a user-friendly tool for importing Support Packages. The
Support Package Manager ensures the complete import of Support Packages, protects
customer modifications, and resolves conflicts with add-ons. It ensures that Support Packages
are imported in the correct order even when you implement several Support Packages at the
same time.
SAP Add-On Installation Tool - SAINT
The Add-On Installation Tool helps to simplify the installation and upgrade procedure of addons. You can implement add-ons in a similar way to Support Packages. You can also use this
tool to install Best practices for mySAP.com (formely known as Preconfigured systems).
It's possible now to extend an Add-on installation queue with further Support Packages.
Meets special requisites to allow for a successful application of the BW Support Package
SAPKW35003.
Bug fix in the Support Package browser; all relevant Support Packages are displayed now.
The status during the import of a Support Package or Add-on installation queue is displayed
correctly in all cases, even if the OCS tool is called without the necessary authorizations.
Improved performance of the queue calculation.
Bug fix in the update procedure of the Note Assistant data during the import of a Support
Package queue.
Page 17
Applying the Latest Support Packages and BW 3.5.2
Page 18
Overview R3 and BASIS_640 Plug-In
Get information from http://service.sap.com/r3-plug-in
SAP R/3 Plug-In
The SAP R/3 Plug-In is an interface which enables the exchange of data between one or
several SAP R/3 systems and other SAP components. The SAP R/3 Plug-In supplies the SAP
components with transaction data and master data in real time. It also makes it possible to use
SAP components like SAP APO or SAP CRM together with certain industry-specific
components. All industry-specific components based on SAP R/3 4.6B or higher SAP R/3
releases require an SAP R/3 Plug-In. The SAP R/3 Plug-In is an add-on to SAP R/3.
SAP Basis Plug-In
The SAP Basis Plug-In is a new software component which was introduced to deliver BW
Service API technology, CRM Middleware, Supply Chain Event Manager and also Financial
Basis functionality to SAP components in order to create a connection to these systems. The
SAP Basis Plug-In is an add-on which can be installed on a SAP Web Application Server or
any other product which is based on SAP_BASIS 620 and SAP_ABA 620 or higher.
The release and maintenance strategy of the SAP Basis Plug-In follows the strategy of the
SAP R/3 Plug-In.
Shipment
The release strategy of the SAP Basis Plug-In generally follows that of the SAP R/3 Plug-In.
Beginning in 2003, SAP plans to ship only one release of PI and PI_BASIS per year.
The SAP Basis Plug-In will be shipped together with the SAP R/3 Plug-In on request to
customers who have a valid SAP license at the date of delivery. The SAP Basis Plug-In and
the SAP R/3 Plug-In will also be part of all SAP solution and SAP component deliveries if they
require the SAP R/3 Plug-In and the SAP Basis Plug-In. This means that if you order a SAP
component or SAP solution, you will also receive the appropriate SAP Basis Plug-In and SAP
R/3 Plug-in.
Page 19
BW 3.5 - Post Activities Basis - 2

Run transaction SGEN to generate the ABAP load the first time

Check the settings (SPRO) with the BW Standard IMG

Check system Change Option in SE06 and SCC4

Uncheck for the following tables with DB20 the automatic recreation
of the database Statistics on Oracle: DD01L, DD02L, DD03L, DD04L
and DD40L (see also Note 556764).

Uncheck also for the BW monitoring tables the Database Statistics
on Oracle to have better performance when you reload the RSA1
Overview RSLDTDONE, RSREQDONE, RSMONFACT,
RSMONNEWPROT, RSMONICTAB, RSMONICDP
(for RSMONMESS, RSSELDONE, RSREQICODS see Note 729402)

Note 620361: performance data laden/Admin. data target, many requests

Note 601612: P11: Manage: Slow formatting due to large Oracle IN list

Note 685602: P18:Manage:Full table scans with very large data targets

Note 647855: Correction: Deadlocks during load processes

Note 729402: P21:AWB:Performance during building and searching …
this best Practice may not help with tables with more than 1000000
records or with Oracle 10g.
You have a data target with a large number of requests. Since certain information of all
requests is required in a data target with the above-described actions, a relatively large
number of entries must be read and processed in different tables. As a result, the processing
times become longer and longer.
Solution
The situation can be alleviated to some extent by tuning. According to note 48230, some of the
database statements can be accelerated by parameter changes. See also note 601612. In
Oracle systems, an improvement may be possible by deleting the statistics on tables
RSSELDONE, RSLDTDONE, RSREQDONE (by switching to the rule-based optimizer for
these tables with the recommended Oracle parameter setting optimizer_mode = choose).
However, this can also have negative effects when you access these tables. In addition, if the
tables continue to grow (by loading further requests), the runtime may deteriorate.
Affected Tables:
RSEUINC, RSLDTDONE, RSMONFACT, RSMONICDP, RSMONICTAB, RSMONMESS,
RSMONNEWPROT, RSREQDONE, RSREQICODS, RSSELDONE, RSMONICDP
You can also use the program RSANAORA (SE38) to remove all statistics for this tables.
Please use the program only for the deletion of the statistics and not for the creation of
statistics in BW.
Check the notes for the tables RSICCONT and RSMONICDP and make sure to have the
latest support packages and notes in the system.
For the Detailed View of the Monitoring Items check the Notes 775393 and 761734 when you
access the tables EDIDC and EDID4.
Page 20
Maintaining the Settings in Table DBSTATC
In addition to the entire database hanging, an excessively low shared_pool_size may also
result in an extremely poor performance with accesses to DD03L, DD04L and DD40L. These
are automatically executed with a RULE hint and are therefore prone to shared_pool_size
problems. If accessing these three tables results in poor performance, enlarge
shared_pool_size to considerably more than 400 MB (800 MB, for example).
If the performance is very poor when you access these tables, check whether you can solve
the problem by deleting the statistics on the tables and deleting their corresponding shadow
tables.
sqlplus "sapr3/<passwd> as sysdba"
SQL> analyze table sapr3.DD03L delete statistics;
SQL> analyze table sapr3."DD03L~" delete statistics;
SQL> analyze table sapr3.DD04L delete statistics;
SQL> analyze table sapr3."DD04L~" delete statistics;
If you are unsure about whether each statistic was created using the dbms_stats package, we
would advise you to also delete the statistics using dms_stats.
SQL> exec dbms_stats.delete_table_stats ('SAPR3', 'DD03L');
SQL> exec dbms_stats.delete_table_stats ('SAPR3', 'DD03L~');
SQL> exec dbms_stats.delete_table_stats ('SAPR3', 'DD04L');
SQL> exec dbms_stats.delete_table_stats ('SAPR3', 'DD04L~');
You can execute the following statement to ensure the extent to which statistics were actually
deleted:
SQL> SELECT last_analyzed FROM dba_tables WHERE table_name in ('DDO3L', 'DD03L~',
'DD04L', 'DD04L~') AND last_analyzed IS NOT NULL;
This should not return a value.
Page 21
Some more tasks and job’s for BW basis tables
Check for intensively increasing Basis tables, see Note 706478

Note 195157 for Application log tables: BALHDR, BALHDRP, BALM,
BALMP, BALDAT, BALC, BAL_INDX
(delete Application log entries with transaction SLG2)

Note 40088 for IDoc tables: EDIDS, EDIDC, EDIDOC, EDI30C, EDI40
Note 761734 Performance IDoc search in the BW loading monitor
(Table EDIDC)
Note 775393 Correction: Performance reading EDID4 in the monitor
(Table EDID4)
The is a slow Performance when creating the Charts for the Offline Webreporting.
To Improve the Performance the following Actions where taken:
y Note 589899: Deleting unusable entries in table RSIXWWW (Report
RSRA_CLUSTER_TABLE_REORG) and update the Statistics on that Table (EI) with
DB20. This Cluster Table helds the Information of the Webcomponents.
y For Table RSODLOIOTM create two missing Indexes: RSODLOIOTM~P08 and
RSODLOIOTM~P09 and updated exact Statistics for that Table (C) with DB20.
y Checked the Settings for Table RSODLOIOFO (ok).
y Add an additional entry to Table RSADMIN (RSDRH_BUFFER_SIZE = 1200) to increase
the Hierachie Buffer.
y Add the Parameter zcsa/table_buffer_area to = 120000000 or higher
Right at the Moment the runtime of the Job came down from ~18‘000 Seconds to 5‘000
Seconds, thats almost four times better.
Page 22

Check note 124375 for the right IDoc Segment for the type
BWINST. Also see notes 538052 and 668536.

In the OLTP system use the transaction SBIW to generate the
data sources for the R/3 system (BCT activation in the R/3
system).

Perform the meta data upload on the BW system (RSA1).

Check the PI 200X.Y and data source replication (meta data
upload) with transaction SAINT and SBIW on the R/3 and BW
system in the AWB.

Fill the repository cache. Go to RSA1 => Extras => Repository
Cache (DB).

Create a development class (SE80) for your modification and
assign it to a transport layer (STMS), otherwise your repairs and
requests are not transportable.

If you are using data marts make sure that you also installed the
BC for data marts; see note 335658 for details.

Activate the BEx history function with RS_PERS_ACTIVATE.
Solution

If an R/3 type destination has entered neither a host nor a system number, a logon is executed within the current
system for the RFC system. A real logon is not executed if neither a client nor a user is specified. These are the
default settings for this destination.

You can change these settings as follows:

Entering host and system number:
y Advantages: This ensures that a special server is being used
y Disadvantages: When you copy or relocate the BW system, you must also adjust the destination (otherwise,
errors occur during extraction or activation of ODS objects because the corresponding functions are carried out
on the old server. For more information, see note 524554.

Error RG102, in particular, may occur if you use an incorrect destination when you activate DataMart export
DataSources.

Entering the client:
y This is absolutely necessary if you are entering a user (see below) because, otherwise, errors occur during the
import postprocessing.
y This is necessary if you want to connect a client other than the BW standard client to the same BW system as
a source system, as of BW 3.5. For more information, see notes 609167 and 522569.
y If you only enter the client but not the user or the server, error RSBM 035 may occur during the transport if
export DataSources are generated here.

Entering a user:
y Advantages: The remote functions are carried out by your selected user (BW background user, for example).
Since the current user is not used, it does not have to have the S_BI-WX_RFC and S_BI-WHM_RFC profiles.
y Disadvantages: The entered user must have the S_BI-WX_RFC and S_BI-WHM_RFC profiles because the
destination is used to call both the source system and BW.

It must also be a dialog user, otherwise, remote interactive functions cannot be performed (such as displaying logs
and so on). For more information, see note 161570.

In addition, you must also maintain the client because a user always only exists in connection with a client.
Page 23
Checking Transfer Parameters in General
SAP
SAPBW
BWsystem
system
Flatfile
loading
PI_BASIS_640
PI_BASIS_640
Transaction SBIW
Transaction
RSCUSTV6
PI-2004.1
PI-2004.1
PI_BASIS_6x
PI_BASIS_6x
Transaction SBIW
SAP
SAPR/3
R/3system
system
The size of a partition in PSA tables is determined by a Customizing parameter which
specifies the minimum number of records in a partition.If this parameter is set too low, a great
many small partitions are created on the database, thus using considerable disk space.The
parameter "partition size" can be changed using transaction "RCUSTV6". If the parameter is
reserved with the value 0, the DEFAULT value 1,000,000 should be taken as a threshold
value. However, due to a program error, the value 0 caused a partition per request,
irrespective of how many entries the request has.
Solution
As of 2.0B patch 20/2.1C patch 13, the minimum number of records in a partition is set to one
million.This means that when parameter "Partition size" is less than 1, 000, 000, the figure is
automatically rounded up to 1,000.000. There is a report for the existing PSA tables called
"SAP_PSA_PARTITION_COMPRESS".This writes all data to a partition, drops the remaining
partitions and adjusts the management tables. The program is not used for the reorganization
or partitioning again of very large PSA tables, rather it is exclusively suitable for a case of a lot
of very small partitions in a PSA table which results in a large cut.
Caution:
If the value for the partition size is already 1,000,000, this error is caused by a common space
phenomenon. You can then correct the error by increasing the tablespace. Even if the
PSAPODSD still shows a lot of free space, this might be fragmented in a way that the
nextextent of the partition to be created / extended will not fit into the biggest free space area.
This is the case if the following applies: 1. > 2. with
1. select next_extent from dba_tab_partitions where partition_name = '<part_name>';
2. select max(BYTES) from dba_free_space where tablespace_name = 'PSAPODSD';
However, if after an 'alter tablespace PSAPODSD coalesce;' 1. > 2. is still valid, you need to
extend the tablespace.
Page 24
Setting the Threshold Value for the PSA Partition RSCUSTV6
10
Size of each PSA partition,
value in number of records
Where? Enterprise IMG (transaction SPRO)
Business Information Warehouse > Links to Other
systems > Maintain Control parameters for the Data
Transfer
Frequency with which status IDocs are sent
With this frequency you determine according to how many data-IDocs an Info-IDoc is to be
sent, or how many data-IDocs are described by one Info-IDoc.
Dependencies
Info-IDocs contain, among other things, information on whether the respective data IDocs
have been uploaded correctly.
Using each Info IDoc, you can see in the monitor whether the load process is running free of
errors. If this is the case for all data IDocs described in an Info IDoc, then the traffic light in the
monitor is green.
Standard settings
Frequency 1 means, for example, that there is an Info IDoc for every data IDoc. In general,
you should choose a frequency between 5 and 10 but not greater than 20.
Recommendation
The larger the packet size for a data IDoc, the smaller you should set the frequency. By doing
this, you make it possible to get information on the respective data load status in relatively
short time periods when uploading data. Here, you can set the number of records at which a
new partition is generated. This value is set to 1.000.000 records as standard.
Note that the Data will be physically deleted after the last Request in the Partition get the
delete Flag from the deletion out of RSA1 Î delete PSA Data. In the first step the data is not
visible anymore for the User, the second step is to delete the data in the Database. With the
last Request the delete command is send to the Database.
Page 25
Checking Transfer Parameters from ODS to Cube
Î RSCUSTA2
(Note 629987 and
554521)
3600
If empty these are
the default values.
ODS Object - Customizing
In ODS object customizing you can define the number of dialog processes, the number of
records activated by one dialog process, and the maximum waiting time of the background job
which extracts the data from the Activation Queue. These settings are valid for all standard
ODS objects in the system.
No. of Par. Proc. and Min. No. Data Recs.
It’s not possible to give general recommendations on how to configure the above parameters.
If you have enough hardware capacity you can increase the number of parallel work
processes which activate the data and increase the number of records for each process. You
should keep in mind that this can influence other jobs running at the same time on your
machine. Please note that these ODS object settings are valid for all ODS objects.
Wait Time in Sec.
The Wait Time specifies how long the batch job, which extracts the data from the Activation
Queue, waits for an answer from each dialog process. This guarantees that the extraction job
does not run “forever” if one of the activation processes fails. On the other hand it is possible
to control the maximum runtime of a dialog process. A wait time which is too short results in an
ODS Data Activation failure although the dialog processes ran successfully. Setting a too long
wait time means that the background process waits too long before an error message is sent
and time is lost for reacting to the problem.
Recommendation: Because of other parallel jobs that run on the system it is possible that the
runtime of such a dialog process may differ. Therefore we recommend setting the waiting time
higher then the observed runtime of one dialog process especially if there is a high load on the
server during the ODS Data Activation.
Server Group
Here you can specify the server group to be used for parallel data activation in ODS objects.
Several dialog processes can be activated. You need to have already created the server
group using transaction SM59.
Page 26
Checking OLAP Cache Parameters in BW 3.5
SAP
SAPBW
BWsystem
system
Transaction
RSCUSTV14
Note 791065
Transaction
RSRCACHE
Previously, cluster tables and flat files were available as media for the cache to make data
persistent in the following modes
y Main memory cache with swapping
y Persistent cache at application server level
y Persistent cache across application server
This was enhanced with a third 'transparent table with BLOB (binary large object)' mode. With
large result sets, this can improve the performance compared with the cluster table because
fewer database operations have to be executed. With smaller result sets, the cluster table may
be an advantage because BLOB field cause database in a sided way a larger maintenance
effort.
To be able to select the optimum persistence medium, the query attributes were enhanced in
transaction RSRT, that is, the medium can now be defined systematically for each query. The
persistence mode maintained in the Customizing cache is still only the default value if a
persistence medium was not defined explicitly on the query. Furthermore, in the same way as
the read and cache mode, the persistence mode was included in the Customizing transaction
'Attributes for InfoProviders' (BW -> Reporting-relevant settings -> General Reporting settings > Attributes for InfoProviders) as the default value for new queries to be created for the
provider.
The monitoring transaction for the query cache (RSRCACHE) was also enhanced accordingly
as part of this enhancement.
Page 27
Checking HTTP Cache Parameters in BW 3.5
Transaction
SMICM
OTR buffer: The online text repository buffer is available as of kernel Release 6.10. Here texts
are saved that are used in BSP for example.
CUA buffer: The runtime objects of the GUI interface are stored in the CUA buffer. These are
saved on the database in the tables D345T, D346T and D342L.
Symptom
The EXPORT_BUFFER_NO_MEMORY runtime error occurs. The following messages appear
in the syslog:
y Invalid parameter ObjTooLar transferred to the database interface.
y Runtime error "EXPORT_BUFFER_NO_MEMORY" occurred.
Increase the buffer in question so that the object to be exported fits into the buffer. Set the
buffer size to five times the size of the object size that was issued in the short dump or to the
maximum size of the object to be expected.
Page 28
Control Parameters for Data Transfer R/3 - BW
Size
max. Lines
Frequency
Max. Proc.
10000 – 50000
up to 100000
5 – 20
3 up to …
20000
50000
10
3
10000
10000
10
2
See Note 130253: Notes on uploading transaction data into BW
Keep the number of data IDocs low. We recommend an IDoc size of between 10000 (Informix)
and 50000 (Oracle, MS SQL Server).
To upload from a file, maintain this value using Transaction RSCUSTV6.
To upload from an R/3 system, maintain this value in R/3 Customizing (SBIW -> General
settings -> Control parameters for data transfer). In addition, set the value for Max.Perc. so
that it matches the number of batch processes in the system.
Page 29
Reconfiguring the SAP Workload for BW
rdisp/wp_no_dia = 12
rdisp/wp_no_btc = 5
rdisp/wp_no_vb = 5
Î1
rdisp/wp_no_vb2 = 2
Î0
rdisp/wp_no_enq = 1
rdisp/wp_no_spo = 1
BW does not need any wp_no_vb2 at all and it is enough to have
only one wp_no_vb. Also check this for SEM-based systems.
Provide enough work processes (wp_no_dia) if you wish to load
data in parallel from the ODS layer into the Cubes.
It is not necessary either to define day/night instances, because
the work processes will be needed for normal load during daytime
and for data load in the nighttime.
For more details, check note 39412: How many work processes to
configure.
UPD (update):
y Number of update servers: Update must occur on at least one server.
y Releases 2.1 and 2.2:
Only configurations with one update server are supported. The name of this server is
defined by the system parameter rdisp/vbname. At least one UPD process must run on
this server.
In Releases 2.1 and 2.2 several update servers should be used only if absolutely
necessary (performance).
The parameter rdisp/vbname defines where the update requests must be sent for every
server. At least one update process must run on each of update servers. Also refer to Note
7209.
y The following applies to Release 3.0:
Several update servers are permissible. There must be at least one update process
running somewhere in the system. The assignment is not carried out via rdisp/vbname, but
dynamically.
y If several code pages are used at the same time in one system, there are further
restrictions (see notes under key word "MNLS").
UP2 (update U2 - as of Release 3.0):
y If there are UP2 processes in the system, U2 update (update low priority) is only possible
in these processes; the UPD processes are then reserved for U1 (update high priority).
y If there are no UP2 processes, the UPD processes take over both U1 and U2.
y Hence, UP2 processes do not have to exist. However, delays can occur for the U1 update
if there are no UP2 processes. If you decide to configure UP2 on an instance, we
recommend to define at least TWO UP2 on such an instance.
Page 30
Post Activities - Maintaining Profiles with RZ10
Internet Communication Framework (ICM) parameter
icm/host_name_full = <fully qualified name>
You use this parameter to specify the fully qualified host name of the host on which the ICM is
running. If this parameter is not set, the system queries the system for the host name. With
several host names, this parameter can override this value.
SAPLOCALHOSTFULL = <fully qualified name>
General timeouts:
icm/keep_alive_timeout
3600
This parameter refers to the "keep-alive-feature" of HTTP1.1
rdisp/plugin_auto_logout
3600
The user context is closed only after this time interval
icm/server_port_: PROT=<xxxx>,PORT=<xxxx>,TIMEOUT=3600
Defines keep_alive_timeout per port binding
Further Information:
Note 622629: Procedure when timeouts occur in BW Web Reporting
Note 622130: Timeout problems in BW Web Applications
Note 538405: Composite SAP Note on the SAP Web Dispatcher
Page 31
BW 3.5 - Transport of BW Metadata
New objects are stored locally (no development class, i.e. $TMP) and no
transport request is required.
Collect objects for transport: all objects must be assigned to a
development class. A transport request has to be created and all objects
are written to it. The development class has to be transported as well.
If you change objects with a development class (i.e. which were
transported sometimes) you will automatically be prompted for a
transport request (standard).
Exception: BEx objects (Query, Variable, Structures, ...) are written to
a special request, which has to be created in the AWB:
Releasing the object changeability (see Note 337950 for details):
This setting is only intended for systems in production or test systems that are set to not
changeable. It is not suitable for development systems. For this reason, this setting is only
effective if at least one of the conditions given under 'Cause and prerequisites' is met.
Call the transport connection of the Administrator Workbench (/nrsa1) and choose 'Object
changeability'. To display the function, you may have to enlarge the window or press the arrow
fields at the edge of the windows.
In the following dialog box you can select the object types you want to be changeable,
although the system is set to not changeable. These objects are not connected to the transport
system, i.e. no transport dialog boxes are displayed. This only applies, however, if the
preconditions mentioned under 'Cause and prerequisites' are met.
First, after releasing an object type, only objects can be changed that are original, i.e. that
were created in that system . This prevents changes to objects that were imported into the
system. Changes to those objects risk to be overwritten during a new transport.
Via the context menu (right mouse button), you can set all objects to changeable (even the
ones imported into the system), although this setting is not recommended for the abovementioned reasons.
Object types with dependences
If you want to edit InfoPackageGroups (ISIG), the InfoPackages (ISIP) should also be set to
changeable.
If you want to edit InfoSpokes (SPOK), the Open Hub Destinations (DEST) should also be set
to changeable.
Page 32
BW 3.5 – Maintaining the Source System Mapping
Restore and activate the ”MyBW system“ connection to itself. This
avoids activation errors for ODS objects.
Either meta data replication or activation of the R/3 source system
which is connected to BW.
Correct settings in table RSLOGSYSMAP for original source and
target system
BWTCLNT001
BWQCLNT001
BWPCLNT001
BWTCLNT001 BWQCLNT001
BWTCLNT001 BWPCLNT001
DEVCLNT001 QUACLNT001
DEVCLNT001 PRDCLNT001
Maintaining DataSources
To maintain a DataSource, select it and choose Maintain DataSource. The following editing options are
available:
Selection
When scheduling a data request in the BW Scheduler, you can enter the selection criteria for the data
transfer. For example, you may want to determine that data requests are only to apply to data from the
previous month.
If you set the indicator Selection for a field within the extract structure, the data for this field is transferred in
correspondence with the selection criteria of the Scheduler.
Hide field
You should set this indicator to exclude an extract structure field from the data transfer. As a result of your
action, the field is no longer made available in BW when setting the transfer rules and generating the
transfer structure.
Inversion
Reverse postings are possible for customer-defined key figures. For this reason, inversion is only possible
for certain transaction data DataSources. These include DataSources that have a field that is indicated as
an inversion field, for example, the field update mode in the DataSource 0FI_AP_3. If this field has a value,
then the data records are interpreted as reverse records in BW.
Set the indicator Inversion if you want to carry out a reverse posting for a customer-defined field (key figure).
The value of the key figure is then transferred in inverted form (multiplied by –1) into BW.
Field only known in exit
You can enhance data by extending the extract structure for a DataSource using fields in append structures.
The indicator Field Only Known in Exit is set for fields of an append structure. In other words, by default
these fields are not passed onto the extractor from the field list and selection table.
Deselect the indicator Field Only Known in Exit to enable the BW Service API to pass on the field of the
append structure to the extractor together with the fields of the delivered extract structures in the field list
and selection table.
Page 33
Transport Strategy for BW 3.x
4
OLAP BW
systems
BWTCLNT001
6
BD1
BQ1
000,066
000,066
001
3
DataSources
BWQCLNT001
001
5
1
DataSources
OLTP R/3
systems
DataSources
DataSources
RQ1
RD1
2
000, 001
000, 001
066
066
DEVCLNT100
QASCLNT100
100
100
transporting DataSources

Select the DataSources you want to transport from the test system into the productive system.
Next, choose transport. Enter a development class and a transport request. Otherwise the
DataSources cannot be transported.
transport strategy for BW 3.x
1. Collect the data sources on the R/3 system
2. transport the data sources to the next R/3 system
3. Replicate the data sources to the assigned BW system
4. Collect the BW objects accorting the following order:
- only necessary objects (info objects, cube structure)
- data flow before it (info sources, transfer structure, updating rules)
- data flow thereafter (only queries checked)
5. Replicate from the target R/3 system to the assigned BW system.
6. transport them in the right order to the next BW system. Ensure that you released the
transport before you collect new objects to another request to prevent blocked objects.
Page 34
BW 3.5 - Transport Route Configuration
OLAP BW
systems
BW Patches
Enhancements
BWTCLNT001
Enhancements
BWT
000,066
001
Enhancements
BWQ
BW Patches
BWQCLNT001
000,066
001
BWP
BW Patches
BWPCLNT001
000,066
001
ALE (TRFC)
OLTP R/3
systems
Add on Patches
PI 2004.1
Modifications
Modifications
000, 001
DEVCLNT100
Add on Patches
PI 2004.1
000, 001
PRD
Add On Patches
PI 2004.1
066
066
100
Modifications
QAS
DEV
QASCLNT100
100
000, 001
066
PRDCLNT100
100
With this overview chart the differences between the OLAP and OLTP system are explained.
You also see the client concepts between BW and R/3.
Page 35
BW 3.5 – Checking the Repository Cache
Usage
The Repository Cache (DB) saves data on the properties of Metaobjects and the relationship
between these objects in database tables, when you first collect objects with the object
browser. When you recall objects that are already collected, the time it takes to access data is
reduced considerably.
The Repository Cache (DB) is activated by default with the functions transport Connection,
Install Business Content, Where-used List and Object Browser. You can change this setting
under Extras à Repository Cache (DB).
Do not use
The Repository Cache is not used when reading data. Meaning, data is read directly from the
database tables of the objects. However, the results of a query are written to the cache and
the main memory. When accessed again, the data is not re-collected, rather it is first saved to
the main memory then referred to in the cache tables on the database.
Rate of hits: displays the statistics of the current transaction
Display table size:displays table statistics.
Run-time of the collector modules: displays run-time statistics.
Filling (delivery objects): enables you to manually fill the Repository Cache in the background.
Filling (active objects): enables you to manually fill the Repository Cache in the background.
Deleting (delivery objects): enables you to manually delete the Repository Cache.
Deleting (active objects): enables you to manually delete the Repository Cache.
Page 36
Activating the BEx History (RS_PERS_ACTIVATE)
Symptom
The <param name="USE_PERSONALIZATION" value="X"> parameter was set in the
TEMPLATE PROPERTIES of a BW Web template, but the personalization is not applied,
however, the variable screen therefore appears when you call the Web Application.
Solution
1. Activate the personalization using the RS_PERS_ACTIVATE report (see note 744009, which
contains further information on RS_PERS_ACTIVATE).
2. There is no personalization for the user who calls the Web Application. A personalization can
be created using the "Personalize Web template" context menu entry. However, this entry is
only displayed in the context menu if the MENU_PERSONALIZE parameter is defined with the
value "E" or "X" in the TEMPLATE PROPERTIES of the Web template or in the URL of the
Web Application. Note that a personalization is user-specific, that is user "A" cannot call the
personalized navigational state of a Web Application of user "B".
When you call the RS_PERS_ACTIVATE report (for one-time activation of variable
personalization, BEx history, WebReport personalization or conversion of InfoObject values),
the two checkboxes for variable personalization and BEx history are filled incorrectly with initial
values. This means that, even though the variable personalization (for example) has already
been activated, the relevant checkbox is not still selected by the system for the next call if the
BEx history has not yet been activated (the reverse is also true).
However, this has no effect on functionality, since all checkboxes that are selected are checked
and the activation steps required for the text are performed in each case. In addition, the
information output after a successful activation step clearly indicates that activation has been
successful.
Page 37
Running the Alpha Conversion if Needed
It is maybe necessary to run the Alpha conversion (transaction RSMDCNVEXIT) after you
activated SAP Demo Business content.
Anyway it is a good consistency check for your data
Page 38

Install the HTML help for BW with SR13
Check the read mode for the queries. Go to transaction RSRT and
type RMRP in the OK field. When you hit <Return> the SAP
suggested Read Modus (on demand in nav./expanding hier.) is set.
For more details see note 329136.
Check that the Vector Graphic Rendering (VML) extension is
available for your Microsoft Internet Explorer IE 5 or higher. It is
used in the AWB for displaying network plans.
Check that the BW Add-On for BW 3.0B is installed. Some ActiveX
controls are used when displaying process chains.
For better performance switch off the bitmap graphic in the
Monitor (RSMON Î Settings Î Background Picture ÎChoose
screen, none).
Check the monitoring settings in the customizing guide (SPRO).
Activate background dispatching with RZ21.
If you have problems with the communication between the BEx
Analyzer and the server, check note 312503 and 211365 for more
details (different ways of connection BEx/GUI).
Use transaction SE38 Î RSFTP005, RSHTTP05
parameter Î abap/hostname_for_sapgui = nsbi0092.bie.sap.corp

Cause and prerequisites
Since Release 2.0A, the exchange of Workbooks between BW server and frontend runs via
SAPGUI component sapftp. The BW server requires a corresponding "RFC destination" in
order to call up this component. This could for example be maintained using Transaction
SM59. Actually, the RFC destinations for sapftp should be created automatically; however,
due to a program error in basis release 4.6C this sometimes is not the case.
Solution
Execute report RSFTP005. This report checks the RFC destinations for sapftp. If it contains
errors, an automatic creation is attempted.
Note: If the BW system has several application servers, the correct host name must be
specified in the profile of the instance profile in each case (Transaction RZ10). See also Notes
124562 and 211365.
If this does not solve the problem, Note 313325 provides further information for error analysis.
If the problem has to be investigated by the support an FTP-trace is required.
Set the correct host name in the profile of each instance.This is the particular name with which
the application server can be reached by the Sapgui (therefore from the user PC).
Set the profile parameter "abap/hostname_for_sapgui". For example:
abap/hostname_for_sapgui=osshost1.wdf.sap-ag.de
Page 39
BW 3.5 - Setting the default Read Mode
Standard settings
In this activity you set the following properties for InfoProviders and queries:
Read mode:
You can set the read mode for a query on an InfoProvider. For more information about the
three possible read modi see the field help in the dialog box for choosing the read mode.
You create new queries with a default read mode. You can set this per InfoProvider using the
Customizing function.
For new queries the read mode is determined as follows:
y If you have already set a read mode for the relevant InfoProvider using this function, then
this read mode is used.
y If no default read mode has been set for the relevant InfoProvider, the read mode is set to
'Subsequently read by hierarchy'.
Cache mode:
You can set the global cache mode for a query. You can choose between three modi:
y Active: The cross-transactional cache is active for the selected InfoProvider (default value).
When the memory allocated for caching has been used up, the excess data is removed,
that is, deleted from it. When requesting a query afterwards, the result needs to be read
from the InfoProvider (from the database) once again.
y Inactive: The cross-transactional cache is not active for the selected InfoProvider.
y Persistently Active: The cross-transactional cache is active for the selected InfoProvider.
When the cache memory is used up, the excess data is written to a background cache (file
or cluster table), and can be loaded into the cache memory again when making another
request.
Page 40
Activating BW Data Sources for the BW Statistics
Select TCT* for
the Statistics. See
Note 309955 for
more details on
BW Statistics.
Application component hierarchy
To create a same-level or subordinate node for a particular node, place the cursor over this
node and click on Object → Create Node. You can also create subordinate nodes by choosing
Object → Create Children.
To reposition a node or subtree, do the following: Select the node you want to reposition (by
positioning the cursor over it and choosing Select Subtree), position the cursor on the node
onto which the selected node is to be positioned. Then, choose the button Reposition.
If you select a node with the cursor and choose Set Segment, this node is displayed with its
subnodes. You can goto the super-ordinate nodes for this subtree via the appropriate links in
the row above the subtree.
All DataSources for which a valid (assigned) application component could not be found are
placed under the node NODESNOTCONNECTED. The node and its sub-nodes are only built
at transaction runtime and refreshed when the display is saved.
NODESNOTCONNECTED is not persistently saved to the database. For this reason, it is not
transferred in a particular status into other systems due to the transport of the application
component hierarchy .
Note: Hierarchy nodes created under NODESNOTCONNECTED are lost when a save is
carried out. After saving, the system only displays nodes under NODESNOTCONNECTED
that were moved under this node with DataSources.
A DataSource hangs under an application component X. You transfer a new application
component hierarchy from Business Content that does not contain application component X.
The result is that thus application component is automatically placed under the node
NODESNOTCONNECTED.
Page 41
Installing the BC for Data Marts (Note 335658)
Solution
Export DataSources are technical DataSources.It is not required to display them at the surface
in the MYSELF system.The update from an ODS object or an InfoCube is always made via the
InfoSource and update rules.The DataSource and the transfer rules are generated in the
background.It does not make sense to change the definition in the MYSELF system.
However, the generated export DataSources can be displayed by activating the 'Display of
generated ODS objects' via menu 'Settings' in the AWB. In addition, application component
'DM' or 'DM-IO' must have been transferred from the Business Content.
Page 42
Checking the Session Manager Settings (Table SSM_CUST)
Solution
When a composite activity group menu is recreated as of Release 4.6D ("Menu" tab: "Import
menu" pushbutton -> "Reimport" pushbutton in the following dialog box), the system creates a
new folder in the first hierarchy level for each of the single roles contained in the composite
activity group; this new folder contains the corresponding menu. The text for each folder
consists of either the technical name or the short text ("Description" input field below the
technical name) for the corresponding single role. You must determine which of the two
alternatives is effective BEFORE you create the composite activity group menu using the
pushbutton for activating and deactivating the technical transaction names (symbol:
magnifying glass). If the technical names display is active (minus sign in the magnifying glass
symbol), the system loads the technical role names (otherwise it loads the short texts). The
technical names are always used for single roles without short texts.
It is not possible to automatically switch between the technical name and the short text after
the composite activity group menu has been created. As with all other folder texts, however,
you can make manual changes and carry out translations.
If you do not want the additional folders when creating the menu, you can deactivate the
function by setting the COLL_READ_LEVEL_1 switch in the Customizing table SSM_CUST to
OFF
Page 43
Checking the Logon Groups with SMLG
1. An attempt is made to start two instances with the same operating system but a
different kernel patch
2. Kernels are exchanged on one or several instances with an operating system that
differs from the one of the central instance without restarting the central instance.

The consequence is that the patch level of the instances does no longer correspond to the
patch level of the status area, and the dispatcher therefore ends with the above error.

The following error will occur nevertheless because the status still contains the old value:
*** ERROR => platform patchno is 164 [dpxxdisp.c 11173]
*** ERROR => but my patchno is 170 [dpxxdisp.c 11174]
Solution

for 1. Upgrade the kernel to the same patch level on all R/3 system instances with the same
operating system.

for 2. The following alternatives are available:
a; Restart the system to have the message server determine the new patch level
automatically.
b; Enter the new patch number in the message server status area which previously contained
the old patch level:
- Transaction SMLG
- Goto -> System Diagnosis -> Message server status area
- Enter new patch level.
You should now be able to start the instance without the patchno error.
Page 44
Online Help Path settings with SR13
Setting Variants for Help (SAP Library)
This activity defines the setting variants that the user can choose for the help display.
A setting variant is defined by
y the help type used (HtmlHelpFile, PlainHtmlFile, PlainHtmlHttp, DynamicHelp)
y the place where the help files are stored: server and/or path
y the language version of the help files.
The setting variants are always valid for a specific frontend platform and a specific area. You
must define a variant as system setting (default value) for each combination of platform and
area.
The area defines the application area of the SAP Knowledge Warehouse where the contents
to be displayed originate. The area IWBHELP (Documentation) contains the online
documentation delivered to all customers (SAP Library). All customers can define setting
variants for this area. Customers using the SAP Knowledge Warehouse can also define
setting variants for the IWBTRAIN (Training) area if they want to display contents of this area
in the online help.
You want to provide users at Windows 98 frontend PCs with the SAP Library in HTML Help
format in different languages and store the help files on a file server.
On tabstrip HtmlHelpFile define several setting variants for platform WN32 and area
IWBHELP. Mark one of them as the default system value.
You want to provide users at Motif frontends with the online help created in a Knowledge
Warehouse system in the Training area in English.
On the DynamicHelp tabstrip define a setting variant for platform MF and area IWBTRAIN and
mark it as the default setting. Enter the Web Server of the Knowledge Warehouse as server.
Page 45
Checklist for Connecting BW - R/3
Checklist
where, what
1.
Define user <SID>_ALEBW in BW and R/3
(Make sure you have the right permissions)
R/3, BW Î SU01
2.
Define logical system names (<SID>CLNT<client>)
R/3, BW Î BD54
3.
Check ALE communication (e.g. SWU3)
R/3, BW Î SALE
4.
Check RFC connection (with remote Logon)
R/3, BW Î SM59
5.
Define new source system (manually)
(this is automatically starting a meta data upload)
BW
6.
Customizing settings of the R/3 system
(Do this before the first Data load starts)
R/3, BW Î SBIW, RSA1
7.
Check/transfer of global settings
(Use this Function as a Simulation to check)
R/3, BW Î RSA1
8.
Activate the necessary BC Data sources
9.
Perform the meta data upload on the BW system
Î RSA1
The checklist for connection R/3 to BW helps you to identify the necessary steps and critial
actions during the connection process. Use the check list also to analyze existing Source
system connections to analyze error situtations.
Page 46
BW 3.5 - Check the ALE User for Extraction
z
Transaction SU01
z
OLAP BW system
S_BI-WHM_RFC
S_BI-WHM_SPC
z
OLTP R/3 system
S_BI-WX_RFC
S_BI-WX_RFCA
z
For the remote
logon test, keep the
user as a dialog
user, and switch it
back to CPIC or
system user (Note
511475).
z
You will need
SAP_ALL only for the
connection.
Symptom
You cannot schedule or perform any batch jobs with the BW or source system background
user.
The error RSPC 065 occurs in the process chains:"Job could not be scheduled, termination
with return code 8„
The user type is
y "CPIC" up to 4.6B
y "Communication" as of 4.6C
This user type may not execute or start any batch jobs, irrespective of the user authorizations.
Solution
Set the type of background user to
y "Background" up to 4.6B
y "system" as of 4.6C
This user type corresponds to the "Communication" type and may also perform background
functions.
Through the Customizing, the BW user is automatically created by mistake as a
communication user
Page 47
Checking the Basic Customizing Settings – Page 1
Update Mode for Master Data
Definition
When updating transaction data or master data attributes, you have a choice of two types of
update. With the first, you can update data records only if the corresponding master data
already exists. With the second, you can always update data records.
If master data does not exist in the system, the corresponding entries are created.
In the case of transaction data, you can set the update parameters in the scheduler. With
master data, you make the settings in this transaction.
Example
You have the InfoObject MATERIAL, which has the navigation attribute COLOR. You want to
create a new entry in the master data maintenance: MATERIAL 4711 with the color RED. The
value RED is not yet available in the master data table of the navigation attribute COLOR.
Activities
At this point you can determine how the system should react in such a case:
Check master data: The new data record is only entered if the value RED of the navigation
attribute COLOR already exists in the system.
Create master data: Data records are basically updated. Navigation attribute values that do
not exist are created.
Page 48
Checking the Basic Customizing Settings – Page 2
Change source system name after transport
Activities
In order to be able to transfer those source system-related settings that you created in the test
system into the productive system at a later date, you have to assign a corresponding source
system name in the productive system to the source system name of the test system.
Activities
In the productive system maintain the table 'RSLOGSYSMAP' with the help of the view
'V_RSLOGSYSMAP' and enter the logical name of the source system in the test system as
'Original Source system' and the logical name of the source system in the productive system
as 'Target Source system'.
This maintenance is necessary because it makes the correct source system reference
possible for the InfoSources to be transported. This source system reference is ,however,
indispensible for activating the transfer structure.
Example
Test BW with source system AAA. Productive BW with source system BBB, where source
system AAA corresponds to source system BBB.
You want to transfer the transfer structure settings that you made in the test system for source
system AAA into the productive system and use them for source system BBB.
You make the following entry in RSLOGSYSMAP in the target BW:
y Original Source system: AAA, Target Source system: BBB
Page 49
Checking the Monitor Settings in Detail in SPRO
The default is seven hours.
This value may be decreased
for special purposes.
Plan this Job daily!
Set Traffic Light Waiting Time
Here you can set the maximum length of time the system is to wait until a request is given the
status red in the Monitor. This setting applies system wide.
Set Traffic Light Color
Here you set the traffic light colors that are used in the monitor
to show that no data has been loaded from the source system.
A data request fails if there is no data in the source system for this particular request.
Page 50
Activating Background Dispatching with RZ21
Schedule Monitor Assistant in Background
The monitor assistant can run in the background and analyzes all the requests. Should it
discover an error, it automatically informs one or more of the peolple responsible.
Activities
Schedule the monitor assistant in the background. As a repeat frequency, select how often
you intend to load data.
Example: You want to load new data on a daily basis. Schedule the assistant to daily.
Recommendation
The assistant investigates all new requests that were started after a certain date. Create a
variant for the monitor assistant and enter this date.
Further notes
If you are dealing with an upgrade system, and you chose a date in the past, the first run time
can possibly take a long time.
Page 51
Basis Customizing Settings in BW 3.5
Î RSA1 Î Global Settings
Î RSADMIN
(Notes 410952,
784891 and 122679)
Symptom
You receive the error message when trying to connect a source system to the Admininistrator
Workbench:
"No entry for BW_USER in table RSADMIN exists" (message number RSAR 059).
The SAP BW (Business Information Warehouse) user for ALE communication entered in the
RSADMINA table field "BW User ALE" during Auto-ID configuration, has insufficient
authorizations.
In table RSADMINA, the BW user is not maintained for ALE.
Solution
Maintain the entry using the following path:
Call Administrator workbench (transaction RSA1).
From the 'Settings' menu, select Global Settings'.
If an entry already exists in the field "BW user for ALE", delete this.
Enter the correct names for the BW users in this field.
Add the profile S_BI-WX_RFC to the authorizations of the SAP BW user for ALE
communication.
Save the entry.
You must restart the Administrator Workbench (RSA1) now.
The source system can now be linked without errors.
Page 52
Basic Customizing Settings – Details 1
Î RSCUSTV7
Page 53
Î RSCUSTV8
(Note 646402 and
653469)
Î RSRCACHE
Î RSCUSTV14
(Note 683194)
Parallel processes used for collecting the data from the Activation Queue (Oracle only):
As of BW3.0B SP17 / BW3.10 SP01 the parameter ORA_PARALLEL_DEGREE of table
RSADMIN defines the number of parallel database processes collecting the data from the
Activation Queue Table. Details can be found in notes 629987 and 671943.
Previously, cluster tables and flat files were available as media for the cache to make data
persistent in the following modes
y Main memory cache with swapping
y Persistent cache at application server level
y Persistent cache across application server
This was enhanced with a third 'transparent table with BLOB (binary large object)' mode. With
large result sets, this can improve the performance compared with the cluster table because
fewer database operations have to be executed. With smaller result sets, the cluster table may
be an advantage because BLOB field cause database in a sided way a larger maintenance
effort.
To be able to select the optimum persistence medium, the query attributes were enhanced in
transaction RSRT, that is, the medium can now be defined systematically for each query. The
persistence mode maintained in the Customizing cache is still only the default value if a
persistence medium was not defined explicitly on the query. Furthermore, in the same way as
the read and cache mode, the persistence mode was included in the Customizing transaction
'Attributes for InfoProviders' (BW -> Reporting-relevant settings -> General Reporting settings > Attributes for InfoProviders) as the default value for new queries to be created for the
provider.
The monitoring transaction for the query cache (RSRCACHE) was also enhanced accordingly
as part of this enhancement.
Page 54
Î RSCUSTV9
Î RSADMIN
Page 55
Î RSCUSTV15
Î RSCUSTV16
HTTP is the standard log for the SAP Web Application Server. All URLs are generated with
the HTTP prefix within the BW system. For example, URLs are generated and used for the
BEx Web Application Designer, BEx Query Designer, BEx Browser or BW Web Item Role
Menu.
You can use the following description to change the standard log from HTTP to HTTPS.
For the Customizing of the standard log, you require BW 3.0A Support Package 8 (see note
452632) or BW 3.0B Support Package 1 (see note 458722).
Solution
You can maintain the standard log via the Customizing (transaction SPRO)/SAP Reference
IMG/BW Customizing Implementation Guide/Business Information Warehouse/Reportingrelevant settings/Web-based settings/Web log (HTTP/HTTPS). Alternatively, you can call
transaction RSCUSTV15.
All URLs are generated with HTTPS if you specify HTTPS as a Web log.
HTTP or HTTPS are permitted values. HTTP is the default value.
A prerequisite for the log HTTPS is that the SAP Web Application Server is configured
accordingly (see configuration in the IMG under SAP Web Application Server).
Page 56
ÎTable
RSADMINSV
(Note 642989)
3.5/02
ÎSE38
RSIWBH01
(Note 620892)
HTTP is the standard log for the SAP Web Application Server. All URLs are generated with
the HTTP prefix within the BW system. For example, URLs are generated and used for the
BEx Web Application Designer, BEx Query Designer, BEx Browser or BW Web Item Role
Menu.
You can use the following description to change the standard log from HTTP to HTTPS.
For the Customizing of the standard log, you require BW 3.0A Support Package 8 (see note
452632) or BW 3.0B Support Package 1 (see note 458722).
Solution
You can maintain the standard log via the Customizing (transaction SPRO)/SAP Reference
IMG/BW Customizing Implementation Guide/Business Information Warehouse/Reportingrelevant settings/Web-based settings/Web log (HTTP/HTTPS). Alternatively, you can call
transaction RSCUSTV15.
All URLs are generated with HTTPS if you specify HTTPS as a Web log.
HTTP or HTTPS are permitted values. HTTP is the default value.
A prerequisite for the log HTTPS is that the SAP Web Application Server is configured
accordingly (see configuration in the IMG under SAP Web Application Server).
Page 57
Some Notes for improving Performance (Oracle)
Note 129252: Oracle DB Statistics for BW Tables
Note 157918: BW DB02 shows "missing indexes"
Note 323090: Performance problems due to degenerated indexes
Note 590370: Too many uncompressed request (f table partitions)
Note 449891: Temporary database objects in BW 3.x
Note 547464: Nologging Option when creating indexes
Note 541538: FAQ: Reorganizations/Fragmentations
Note 628590: Activating table monitoring using "-f monit" option
Note 550784: Changing the buffer of InfoObject tables
Note 402469: Additional indexes on Master Data Tables
Note 383325: How to manually create a bitmap index
Note 589899: Deleting unusable entries in table RSZIXWWW
Note 883843: BW instances can no longer be started
Note 598678: Oracle9i: New functions (composite SAP Note)
You may also check regularly the latest Notes for the Program SAP_DROP_TMPTABLES
Check also for Table DBDIFF the Function Module RSDDTMPTAB_CLEANUP for cleanup old
temporary table entries. In conjunction you can also use the Program SAP_UPDATE_DBDIFF
to clean the table DBDIFF. You may run /$sync before.
Use the Program RSRA_CLUSTER_TABLE_REORG to clean entries in Table RSIXWWW.
See Note for more details.
Details from Note 883843 to clean Nametab entries (the latest Version from
SAP_DROP_TMPTABLES may also clean this entries):
y select count (*) from ddntt where tabname like '/BI0/030%';
y DELETE FROM DDNTT WHERE TABNAME LIKE '/BI0/03%';
y select count (*) from ddntf where tabname like '/BI0/030%';
y DELETE FROM DDNTF WHERE TABNAME LIKE '/BI0/03%';
Page 58
Hints (for Oracle) for Table RSADMIN
Note 555030: Deactivating BW-initiated DB statistics

DB_STATISTICS = OFF
Note 535986: monitoring for BW fact tables on Oracle

ORA_MONITORING = OFF
Note 351163: create ORACLE DB Statistics via DBMS_STATS

ORA_DBMS_STATS = 0, 1, 2…
Note 639253: Incorr. data after compression with zero elim. and

COMPNOMERGE = X
Note 544521: Controlling the PARALLEL degree parameter (Aggr.)

ORA_PARALLEL_DEGREE: 0, 1, 2.. 3.. 4...
Note 534630: Parallel processing of Change Run

CR_MAXWP = <amount of work processes>

CR_RFCGROUP = <Name of the RFC- server group> (optional)
Note 644039: Performance during attribute realignment run after …

ORA_CHANGERUN_MODE = PARALLEL
Note 584216: RSADMIN parameter for hierarchy table buffer size

RSDRH_BUFFER_SIZE = <amount of entries in buffer>
More interesting RSADMIN Parameters:
Note 561961:
Deactivating/activating usage of fact table view
y USE_FACTVIEW = FALSE, TRUE, NEVER
Note 559524:
Alpha: Parallel processing of the ODS converter
y ALPHA_ODS_PARALLEL = X
y COUNT_PROCESSES = Value (1/CPU per process)
Note 592600:
BW: Switching off open-SQL with RSADMIN-Parameter
y SWITCH_OFF_OPENSQL = X
Note 583202:
Realignment run and condensing (see note 534630)
y CHANGERUN_CONDENSE = X
Note 738245:
Automatic compilation of formulas
y RSFO_COMPILER_OFF = X
Note 796697:
DBIF_NTAB_TABLE_NOT_FOUND dump in BW with /BI0/030* tables
y RSDRS_EXECUTE_GC = X
Note 803507:
RSM 831 when you delete an InfoSource
y NEW_MD_IS_DEL_CHECK = X
Note 854092:
During initial aggregate fill a COMMIT is eventually needed
y BW_AGGRFILL_INTRABLOCK_COMMIT = X
Note 856221:
Deletion of entire cache with BLOB and Cluster table
y RSR_CACHE_STORAGE_LOOP_COUNT = 10
Note 613701:
Problems with Compression on BW3.x and Oracle
Page 59
Hints (for Oracle) for Table RSADMIN
Note 595251: Performance DataMart: Deactivation of TRFC send in BW

SAPI_SYNC = X
Note 514907: Processing complex queries (DataMart, and so on)

SPLIT_DATAMART_TABL_THRES = <amount of Tables>

SPLIT_QUERY_TABL_THRES = <amount of Tables>
Note 536223: Activating master data with navigation attributes

SPLIT_SX_TABL_THRES = <amount of Tables>
Note 751218: Control over number of work processes in multi cubes

MULTICUBE_WP_LIMIT = <the maximum no. of wp used for the multic.>
Note 750033: INITRANS parameter for InfoCube secondary indexes

ORA_CUBEINDEX_INITRANS = 20, increase until no deadlock anymore
Note 831234: Deadlock ORA-00060 during parallel loading in BW ODS

ORA_ODS_TABLE_INITRANS = 20, increase until no deadlock anymore
Note 840553: BW Oracle: TRUNCATE slower than DELETE

ORA_TABTRUNCATE_MINIMUM = 1000
Note 919870 - Using NTEs with Oracle

ORA_ENABLE_NTE = X
You can maintain entries in Table RSADMIN with the program
SAP_RSADMIN_MAINTAIN. The table is buffered, so you should validate the table
buffer with $tab.
More interesting RSADMIN Parameters:
Note 756805:
Performance in update rules (Reactivate Transfer Rules after correction)
y RSAU_OPTIMIZE_OFF = X
Note 709141:
Problems accessing SEM-BPS planning folders & BEx workbooks
y REUSE_XL_INSTANCE = DISABLE
Note 744555:
Settings for materializing SID restrictions
y DBIF_EQSID_THRES = 20
Note 792435:
Selective deletion: Using temporary tables
y BW_SELDEL_PERC_THRES = 50
Note 805981:
Long OLAP time in the CHECK or CHECK_NODE_..form
y CHECK_GEN_NEW = X
Note 801399:
Const. sel. on the structure item in queries with 2 struc
y CONSTSEL_NEW = X
Note 823654:
Long runtimes in the form: adjust_input_for_multicube
y ADJUST_NEW = X
Note 825396:
Performance in reports with many selections
Page 60
Post Activities BW Release 3.5: Unit Summary
You should now be able to:
z Proceed with technical BW-specific tasks after the
standard installation
z Understand the necessary technical jobs and tasks
for supporting the BW application
z Do the Basis Customizing for the BW application
z Prepare the data loading for the BW application
z Set up and tune the productive usage of the BW
system
Page 61