Running SAP Business Information Warehouse (BW) on SAP HANA refers to using a certain version of BW software with...
HANA as its primary database, optimized for the HANA platform. Although BW supports other databases, using BW on HANA means that no other databases are required.
Indeed, implementing SAP BW on HANA can help companies take advantage of HANA's speed and performance. However, it's critical that CIOs and their teams first ensure that the data and technical objects residing in the existing BW are cleaned up, pruned, archived or simply purged. Doing so offers three distinct advantages:
- a lower cost of using in-memory computing;
- reduced downtime required for implementing BW on HANA; and
- a new BW on HANA system that contains only the data required for analytics.
Before beginning the migration project, IT teams will need to take several concerted steps to clean the obsolete data residing in BW. They'll also need to archive and delete data that is no longer required, and move lesser-used data to a different and smaller server to ensure it is still available when needed. Here are 10 steps related to that important preimplementation work.
- Remove data from the Persistent Staging Area (PSA): Since the data is already loaded to data store objects (DSOs), it makes sense to remove it from PSA, which will no longer be used after implementing BW on HANA.
- Delete aggregates: Aggregates sum up the numbers in BW to improve report performance. Due to the data processing prowess of BW on HANA, these aggregates (summations) are no longer required, and can be deleted.
- Delete statistical cube data: The BW system saves statistical cube data for system tuning. Use transaction code RSDDSTAT to get rid of this unwanted data.
- Remove obsolete objects: Use transaction code RSZDELETE to gain insight into objects, such as log files, unused Business Explorer queries and templates that haven't been used in a long time and are no longer required.
- Remove Data Transfer Process (DTP) objects: During data transfer in BW, the system uses a technical object called a DTP. It contains data log files and temporary data storage objects. Refer to SAP Notes 1139396 and 1106393, which contain useful information about DTP objects, as well as programs to help with DTP cleanup.
- Clean Transactional Remote Function Call (tRFC) queues and archive intermediate documents (IDocs): tRFCs and IDocs previously in use to transfer data to and from BW to SAP ERP Central Component or other systems are either no longer required or can be archived (IDocs). The obsolete tRFCs can be purged.
- Migrate old data to near-line storage (NLS): Older, historical data that isn't as frequently used, but is still needed, can be migrated to NLS on a smaller server. Doing so will eliminate the need to store this data in memory, thus ensuring optimum system performance, while reducing the usage costs associated with in-memory computing in HANA. Users employing BW on HANA can still query this data on NLS.
- Get rid of unused DSOs, InfoCubes and staging: Data in these objects are used by BW to improve system performance for quicker reporting. The unused data from these objects can be removed before implementing SAP BW on HANA.
- Eliminate obsolete and unwanted master data: Pruning obsolete master data is also an important step. Refer to SAP Note 1370848 for more information on best practices for deleting unwanted master data.
- Delete unused dimension entries in InfoCubes: Use transaction code RSDDCVER_DIM_UNUSED to clean unused dimension entries from the InfoCubes. Doing so will reduce the size of BW on HANA, thereby reducing the required migration time.
CIOs and their teams can start taking several of the above data housekeeping steps in BW much earlier than the actual migration to BW on HANA.
Take a look at BW and SAP S/4HANA data warehousing software for HANA
Data Services and Business Warehouse are a powerful pair -- with some downsides
Should you choose HANA or Business Warehouse?
Dig Deeper on SAP Business Warehouse
Related Q&A from Jawad Akhtar
Replenishment strategies, lot sizes, safety stock, reorder point planning and replenishment lead time are five factors in ERP that can ensure ... Continue Reading
S/4HANA public cloud provides a less disruptive route to digital transformation than some options -- including the on-premises S/4 -- and smoother ... Continue Reading
These nine key components of SAP MDG help ensure regulatory, legal, environmental and financial compliance of your master data and improve ... Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.