The complexity of the objects in this design leads to the challenge of maintaining up-to-date andaccurate data in all the BW data tables. However, loading data into the BW is accomplished byusing InfoPackages. InfoPackages are tools for organizing data requests that are extracted fromthe source system and are loaded into the BW system. With the progress of BW project thenumber of info packages increases emphasizing the importance of good performance of eachinfo package. Although the DBMS underlying the BW system is monitored by the standardsoftware’s for the R/3 functionality but this leaves a gap between the table spaces and tablenames as they appear at the DBMS level and the BW application level entities to which theseobjects belong. To bridge this gap, the new BW functionality for R/3 includes reports that placeDBMS objects in a BW context. These reports allow the user to take an object at the DBMS leveland associate it with its application-level entity.In case of any problem in order to enable the administrator to identify the problem theInfoPackages are organized on the basis of the object to which they are transporting data- Infocube, ODS or Master Data. The overall request status for the object is displayed, and an alarm istriggered if any Info Package run from any Info Source fails. In this way, the administrator is ableto locate the exact position where a failure is going to impact the users and the BW system. Also,for InfoCubes, Master Data and the ODS to give an overview of the history of requests for thesystem, the progress of the last N requests through each stage of extraction and load isdisplayed, and for any failures, the step that failed is displayed. The performance of requests canbe monitored by display of performance statistics for each stage of extraction and load in the formof graphs.
4.0 Building SAP BW into multi-tier architecture model in BusinessServices
Being implemented on top of SAP Web Application Services SAP’s BW provides a multi-tier architecture (figure shown below), along with a complete software development environment,system management tools and additional functionalities such as currency conversion or security.Although it is closely related to SAP R/3, SAP BW is a completely separate software packagewhich comes with automated extraction and loading facilities.
Components of BW architecture
SAP BW is based on integrated metadata concept with metadata being managed by metadataservices. SAP’s BW has following layers:
Extraction, Loading and Transformation (ELT) services layer.
Storage services layer, with services for storing and archiving information.
Analysis and access services layer, which provides access to the information stored inSAP BW.
Presentation services layer, which offers different options for presenting information toend users.
Figure: Multi-tier Architectural Pattern