First we need to create two views: one for master data and one for texts.
Note
Views are ABAP dictionary objects. They are used to display data from multiple tables with specified table join conditions.
Work Instructions
Step 1.To create a view for the master data, run transaction SE11, enter a name for the object, select the Views option in the Dictionary objects block, and then click .
SCREEN 11.3
Step 2. Select the Database view option, and then click .
SCREEN 11.4
Step 3. The view needs to be included in a development class in order to be transported to other R/3 systems. In our example, we create views as local objects. Enter $TMP as the development class name and click the , or simply click to assign the object to $TMP. Click to continue.
SCREEN 11.5
Note
A development class groups logically related objects, such as the objects that make up an accounting application. $TMP is a temporary local development class. Objects in $TMP cannot be transported into other systems.
See ABAP documents for more information on $TMP and non-$TMP development classes.
Step 4. This view consists of only one table, LFM1 (Vendor master record purchasing organization data). Enter the names of the fields from which we will extract data (see Table 11.1).
Click to save the view definition.
SCREEN 11.6
Step 5. Click to check the view definition. If it is valid, click to generate the view.
SCREEN 11.7
Step 6. To display the data selected by this view, select the Display data option on the Utilities menu.
SCREEN 11.8
Step 7. Click to display the data.
SCREEN 11.9
Result
The result, which is shown in Screen 11.10, has two entries.
SCREEN 11.10
We use the same procedure to create a view for the text data (see Screen 11.11). This view consists of data from two tables, LFM1 (Vendor master record purchasing organization data) and LFA1 (Vendor master general section). The text data come from the LFA1 table.
SCREEN 11.11
Screen 11.12 shows the data selected by this view, which consists of two entries as well.
SCREEN 11.12
Now we have created two views, one for master data and one for texts. Next, we will create DataSources using these two views.
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