Shulou(Shulou.com)05/31 Report--

Today, I will talk to you about what preparations need to be made for the implementation of SAP BW on HANA. Many people may not know much about it. In order to make you understand better, the editor has summarized the following contents for you. I hope you can get something according to this article.

Running SAP Business Information data Warehouse (BW) on SAP HANA is mainly concerned with using a version of BW software as its main database and optimizing for HANA platform. Although BW supports other databases, using BW on HANA does not actually require other databases.

In fact, implementing SAP BW on HANA can help companies take advantage of the speed and performance of HANA. However, the first key issue that CIO and the technical team need to ensure is that the data and technical components in existing BW systems have been properly cleaned, deleted, archived, or simply cleansed. This has three special advantages:

Enjoy memory computing at a lower cost

Reduce downtime required to implement HANA-based BW

The new BW based on the HANA system contains only the data needed for analysis.

Before starting the migration project, the IT team needs to take some steps to clean up the obsolete data left in BW. They also need to archive and delete data that is no longer needed, and migrate less frequently used data to other servers with lower configurations, so that they can still be accessed when needed. Here are ten important tasks that need to be prepared before implementation.

Removes data from the persistent staging area (PSA). Now that the data has been loaded into the data store object, it is necessary to delete the data from the PSA, and the data will be useless after the subsequent deployment to HANA to implement BW.

Delete aggregated data. Aggregate data is the sum data in BW, which is the result data stored temporarily in order to improve the performance of the report. Because the data processing power of BW in HANA will be greatly enhanced, these aggregated data (summed values) are no longer needed and can be deleted directly.

Delete statistics. The BW system stores statistical data cubes for system tuning. These unwanted data can be discarded using the transaction code RSDDSTAT.

Delete obsolete objects. Using the transaction code RSZDELETE, you can view object information, such as log files, unused business exploration queries, and templates that have not been used for a long time.

Delete the data transfer processing (DTP) object. In the process of data transmission in BW, the system uses a technical object called "DTP". Refer to the SAP Note numbers "1139396" and "1106393" for information about DTP objects and how to clean up DTP objects.

Clean up intermediate documents (IDocs) for transactional remote function calls (tRFC) queries and archives. TRFC and IDoc are used in the transfer of data from BW to SAP ERP central components or other systems, and the transfer is of no other use, at least for archiving. Outdated tRFC should be cleaned up.

Migrate old data to adjacent storage (NLS). Old historical data is not used frequently, but it is still needed. We can migrate this data to a smaller server, NLS. This reduces the need to store data in memory, optimizes system performance, and reduces the cost of computing associated data in memory in HANA. Users who use HANA BW can still query this part of the data in NLS.

Clean up unused DSO, InfoCube, and status data. The data in these objects is used by BW to improve system performance and output reports faster. The useless data designed by these objects should be cleaned up before SAP BW is deployed in HANA.

Eliminate outdated and unwanted master data. Collating outdated master data is also an important step. See SAP Note "1370848" for more information, including the practice of deleting useless master data.

Delete dimension entries that are not used in InfoCube. Use the transaction code "RSDDCVER_DIM_UNUSED" to clean up unused dimension entries in InfoCube. Doing so reduces the total footprint of deploying BW on HANA, thereby reducing the data transfer time required for migration.

CIO and their team can follow these steps to prepare for BW in advance before migrating to HANA BW.

After reading the above, do you have any further understanding of what preparations should be made to implement SAP BW on HANA? If you want to know more knowledge or related content, please follow the industry information channel, thank you for your support.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.