Creating Views in R/3

Table of contents:

Creating Views in R 3

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 graphics/create1.gif.

SCREEN 11.3

graphics/11fig03.gif

Step 2. Select the Database view option, and then click graphics/choose.gif.

 

 

SCREEN 11.4

graphics/11fig04.gif

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 graphics/save.gif, or simply click graphics/localobject1.gif to assign the object to $TMP. Click graphics/localobject1.gif to continue.

 

 

SCREEN 11.5

graphics/11fig05.gif

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 graphics/save.gif to save the view definition.
 

SCREEN 11.6

graphics/11fig06.gif

Step 5. Click graphics/check.gif to check the view definition. If it is valid, click graphics/generate.gif to generate the view.

 

 

SCREEN 11.7

graphics/11fig07.gif

Step 6. To display the data selected by this view, select the Display data option on the Utilities menu.

 

 

SCREEN 11.8

graphics/11fig08.gif

Step 7. Click graphics/clock.gif to display the data.
 

SCREEN 11.9

graphics/11fig09.gif

Result

The result, which is shown in Screen 11.10, has two entries.

SCREEN 11.10

graphics/11fig10.gif

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

graphics/11fig11.gif

Screen 11.12 shows the data selected by this view, which consists of two entries as well.

SCREEN 11.12

graphics/11fig12.gif

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



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