Summary

In this chapter, we loaded the data described in Chapter 1 into the characteristics and InfoCube we created in Chapter 2. Figure 3.2 shows the many ways in which data can flow into a destination in BW. In this chapter, we followed the path linked via solid lines. The rest of this book will discuss the other paths.

Figure 3.2. DATA FLOW

graphics/03fig01b.gif

Key Terms

Term Description
Source system A source system is a protocol that enables BW to know where to find data and how to extract those data. When the source system is a non-SAP system, such as a flat file or a third-party tool, the maximum number of characters allowed for the technical name is 10. When the source system is an SAP system, either R/3 or BW, its technical name matches its logical system name. The maximum number of characters allowed for the technical name is 32.
Application component Application components are used to organize InfoSources. They are analogous to the InfoAreas in InfoCubes. The maximum number of characters allowed for the technical name is 32.
InfoSource An InfoSource is a structure in which InfoObjects are logically grouped together. InfoCubes and characteristics interface with InfoSources to get source system data. The maximum number of characters allowed for the technical name is 32.
Communication structure The communication structure serves as the structure in the InfoSource.
DataSource

A DataSource is not only a structure in which source system fields are logically grouped together, but also an object that contains ETTL-related information. Four types of DataSources exist:

  • DataSources for transaction data
  • DataSources for characteristic attributes
  • DataSources for characteristic texts
  • DataSources for characteristic hierarchies

The maximum number of characters allowed for the DataSources technical name is 32.

Transfer structure A transfer structure maps DataSource fields to InfoSource InfoObjects.
Transfer rule Transfer rules specify how DataSource fields map to InfoSource InfoObjects.
InfoPackage An InfoPackage specifies when and how to load data from a given source system. BW generates a 30-digit code starting with ZPAK as an InfoPackage's technical name.
Update rule An update rule specifies how data will be updated into a target. The data target can be an InfoCube or an ODS object. If the update rule is applied to data from an InfoSource, its technical name will match the InfoSource's technical name. If the update rule is applied to data from an ODS object, its technical name will match the ODS object's technical name prefixed with number 8.
BW Scheduler BW Scheduler specifies when to load data. It relies on the same techniques used for scheduling R/3 background jobs.
BW Monitor BW Monitor displays data load status and provides assistance in troubleshooting if errors occur.

Next…

We will check the loaded transaction data.

Part I. Guided Tours

Business Scenario and SAP BW

Creating an InfoCube

Loading Data into the InfoCube

Checking Data Quality

Creating Queries and Workbooks

Managing User Authorization

Part II. Advanced Topics

InfoCube Design

Aggregates and Multi-Cubes

Operational Data Store (ODS)

Business Content

Generic R/3 Data Extraction

Data Maintenance

Performance Tuning

Object Transport

Appendix A. BW Implementation Methodology

Object Transport

Appendix B. SAP Basis Overview

Object Transport

Appendix C. Glossary

Appendix D. Bibliography



SAP Bw. A Step-By-Step Guide
Sap Bw: a Step By Step Guide for Bw 2.0
ISBN: B000LZM8CM
EAN: N/A
Year: 2002
Pages: 106

Flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net