SAP Business Warehouse (BW) Control Requirements to Ensure a High Level of Confidence in BW Data

SAP Business Warehouse (BW) Control Requirements to Ensure a High Level of Confidence in BW Data

This post give more details of best practice we are doing to test or provide Quality Assurance for SAP BW/BI in our company. This give more details of the controls required in the BW to ensure there is a that the data is both complete and accurate. These types of controls will ensure that the reports that are developed and distributed throughout the organization are reliable . IT is responsible for the control environment within the new Business Warehouse, and Enterprise Reporting has a significant reliance on this function. This document includes some ideas for effective control procedures for consideration by the IT Enterprise Data group.

Data Transfers
Every time a data source is created or populated the following checks must be done:
* Verify that the number of records in the destination table is correct given the number of records in the source table(s) / view(s).
* Verify that the hash total, (random summation of amounts), for 2 fields in the destination table is accurate versus the source table(s) / view(s). Ideally, fields whose values have a large variation and fields that are frequently used should be chosen.
* BW logging should be reviewed to ensure there were no errors in the transfer. IT should propose an action plan for how each type of error will be addressed with signoff required by business.

Notes:
* The processes should run at the time the data is loaded so that errors can be identified before the data is used.
* The process should be automated to minimize human effort and error.
* If, after following this process, data errors are encountered in BW an investigation should be done to determine what further controls are necessary.

Data Views
Every time a view of the data is created the following minimum testing must be done:
* Verify that the number of records in the destination view is correct given the number of records in the source table(s) / view(s).
* Verify that the hash total for all fields in the destination view is accurate versus the source table(s) / view(s).
* Verify that all fields appear to be populated completely without any obvious errors.

Notes:
* Once the view is in production it will be assumed that it will continue to operate correctly.
* If, after following this process, data errors are encountered in BW an investigation should be done to determine what further controls are necessary.