Tcodes: RSDDV, RSADMIN
BI Accelerator is a separate server which runs on TREX (Text Retrieval Extraction). The BI-Accelerator is a an addition to SAP BW 7 version and is now becoming obsolete with the advent of HANA.
BIA serves the purpose of putting some of the data in the memory whereas HANA puts all the data in memory.
Many companies have opted for BIA when it was launched and it has given impressive performance with typical improvement factors between 10 and 100.
Long running Sales/AR/Finance queries have improved drastically when the cubes on which they are based are indexed on BIA. Continue reading “SAP Netweaver BI Accelerator”
This post provides guidelines for managing space in the SAP BW Production environment in general. It describes these guidelines in the context of generic business intelligence goals, principles, and architecture.
Principles of Data Warehousing Data Retention:
Data warehouses exist to serve as the “information memory” of an enterprise. Data warehouses record all the critical business transactions conducted by an enterprise, so decision makers and business strategists can leverage the information to meet their goals and objectives.
The Value of Historical Information:
The business intelligence team must ensure that information captured in the data warehouse supports both the current, known requirements for analyses, but also supports the future, unknown requirements.
Low level, historical transaction data captures information about past behavior of the enterprise that no other source of information provides. When we delete this data, we eliminate forever the ability of the enterprise to leverage the knowledge contained in the raw data. If we summarize data and delete the original details, we eliminate forever the ability to produce alternate summaries of that data. Continue reading “BW Data Retention / Archival and Space Management Guidelines”
SAP BW Modeling:
Multiproviders must always be used as a base for the query.
Every MultiProvider includes a characteristic called InfoProvider (0INFOPROV) in the data package dimension.
Queries can filter on this characteristic to restrict access to one or more specific underlying InfoProviders.
If your MultiProvider definition includes a large number of underlying InfoProviders (such as one per year, one per division, etc.) you can improve query performance by dynamically filtering on the 0INFOPROV characteristic.
A customer exit variable provides a flexible way to Continue reading “BW Development Standards Part 3: Data Modeling in Multiproviders and Infocubes”
Navigational attributes are discussed a lot of times in BW. They have an advantage as these attributes can be used for navigation in a query. However there are lot many more advantages of navigational attributes. I will discuss today one such scenario where navigational attributes has saved a week’s time. Continue reading “When to use Navigational Attribute in SAP BW”
Semantic groups can be set in DTP in the extraction tab. These are the fields from the source which are available for selection as semantic keys.
The BW system while doing the loads will Continue reading “DTP Performance Improvement: Semantic Groups”