ABAP REPORTS: SAP BW Business Intillengence

Before loading transaction data in SAP BW, we need to load the reference data. Reference data is master data, texts, hierarchies, and other configuration-specific data that is used across all analytical applications in SAP BW. Having master data in SAP BW first speeds up the InfoCube population process. This is because SID tables for master data are created during master data loading, and these SIDs are used in InfoCube dimensions as pointers for master data.

To load master data in SAP BW, you do not need to. run any statistical update procedures.The order in which you load reference data in SAP BW is very important, and shall be like mentioned below:

Master Data

Texts

Hierarchies

The actual disk space used by reference data tables in SAP BW will be almost the same as in SAP R/3.In a multi-language SAP BW environment, only the TEXT elements are stored in multiple languages. The basic master data attributes are only stored once.

Quality of master data for SAP BW is important. We have to make sure you load only the data that we really need from SAP R/3 in SAP BW. When SAP BW requests master data from SAP R/3, it pulls all master data records, including those that are marked as delete or obsolete. This may cause problems when loading master records.

When you delete master data from SAP R/3 OLTP, it is "marked for deletion" instead of "physical deletion" to preserve transaction data integrity. The reason that SAP R/3 does not physically delete master data from its database is that some transaction records may have references to "to be deleted" master data records.

SAP BW provides a mechanism to identify permitted characters beyond typical text and numbers, as shown in figure below. There you identify characters that will be acceptable in SAP BW. This is a quick fix to acknowledge invalid data, but you need to simply exclude such data sets at the data source level, SAP R/3.