views

[Former Member]

explain the diferent views and need to create each view

[Former Member]

there are 4 type of views

hi,

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2cceb190-0201-0010-be88-acdbeb2a...

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2cceb190-0201-0010-be88-acdbeb2a...

http://help.sap.com/saphelp_nw04s/helpdata/en/ea/cf9441026aae5fe10000000a1550b0/frameset.htm

http://help.sap.com/saphelp_nw04/helpdata/en/bb/db029f4a3011d189490000e8323c4f/frameset.htm

pankaj

Hi

The followings are different types of views:

Database View (SE11)

Database views are implement an inner join, that is, only records of the primary table (selected via the join operation) for which the corresponding records of the secondary tables also exist are fetched. Inconsistencies between primary and secondary table could, therefore, lead to a reduced selection set.

In database views, the join conditions can be formulated using equality relationships between any base fields. In the other types of view, they must be taken from existing foreign keys. That is, tables can only be collected in a maintenance or help view if they are linked to one another via foreign keys.

Help View ( SE54)

Help views are used to output additional information when the online help system is called.

When the F4 button is pressed for a screen field, a check is first made on whether a matchcode is defined for this field. If this is not the case, the help view is displayed in which the check table of the field is the primary table. Thus, for each table no more than one help view can be created, that is, a table can only be primary table in at most one help view.

Projection View

Projection views are used to suppress or mask certain fields in a table (projection), thus minimizing the number of interfaces. This means that only the data that is actually required is exchanged when the database is accessed.

A projection view can draw upon only one table. Selection conditions cannot be specified for projection views.

Maintenance View ( SE54 )

Maintenance views enable a business-oriented approach to looking at data, while at the same time, making it possible to maintain the data involved. Data from several tables can be summarized in a maintenance view and maintained collectively via this view. That is, the data is entered via the view and then distributed to the underlying tables by the system.

If its useful reward points

Edited by: saslove sap on Apr 7, 2008 8:56 AM

Edited by: saslove sap on Apr 7, 2008 8:57 AM

[prasanth_kasturi]

Data about an application object is often distributed on several tables. By defining a view, you can define an application-dependent view that combines this data. The structure of such a view is defined by specifying the tables and fields used in the view. Fields that are not required can be hidden, thereby minimizing interfaces. A view can be used in ABAP programs for data selection.

The data of a view is derived from one or more tables, but not stored physically. The simplest form of deriving data is to mask out one or more fields from a base table (projection) or to include only certain entries of a base table in the view (selection). More complicated views can comprise several base tables, the individual tables being linked with a relational join operation. See also Join, Projection and Selection.

The base tables of the view must be selected in the first step of a view definition. In the second step, these tables must be linked by defining the join conditions. It is also possible to use the join condition from a foreign key defined between the tables (see Foreign Key Relationship and Join Condition). In the third step, you must select the fields of the base tables to be used in the view. Selection conditions that restrict the records in the view can be formulated in the fourth step.

Four different view types are supported. These differ in the way in which the view is implemented and in the methods permitted for accessing the view data.

Database views are implemented with an equivalent view on the database.

Projection views are used to hide fields of a table (only projection).

Help views can be used as selection method in search helps.

Maintenance views permit you to maintain the data distributed on several tables for one application object at one time.

Database views implement an inner join. The other view types implement an outer join (see Inner and Outer Join).

The join conditions for database views can be formulated using equality relationships between any base fields. The join conditions for the other view types must be obtained from existing foreign keys. Tables therefore can only be combined in a maintenance view or help view if they are linked to one another with foreign keys.

The maintenance status defines whether you can only read data with the view or whether you can also insert and change data with it.

database view refer

http://help.sap.com/saphelp_nw70/helpdata/en/cf/21ecab446011d189700000e8322d00/frameset.htm

projection view

http://help.sap.com/saphelp_nw70/helpdata/en/cf/21ed20446011d189700000e8322d00/frameset.htm

maintenance view

http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ed2d446011d189700000e8322d00/frameset.htm

helpview

http://help.sap.com/saphelp_nw70/helpdata/en/cf/21ecd2446011d189700000e8322d00/content.htm

[Former Member]

Hi,

There are four separate, types of views:

Database view

- defined just as a table is defined within the database

- one or more related tables may be used

- only transparent tables may be used

Help view

- accessed from within transactions

- accessed only from within SAP Help

- Open SQL and Native SQL cannot access

- only 1:1 and 1:C relationships are possible

Projection view

- allows suppression of some fields within transparent table displays

Maintenance view

- enables table maintenance via SM30

- allows specific customizing transactions

A view is like a table but lacking content – it is a virtual table. A view is a definition based upon the relationship between one or several tables using the permitted relational database operations (i.e., select, join or projections). Using a view permits restricting or limiting the access to information by areas, employees, plants, etc. It permits authorized users a 'snap-shot' of the data within their functional area (finance (FI) or production planning (PP)).

A view reduces the need to create new tables with only the specific data for each application ( FI , SD , PP, etc.). A view reduces redundancy of tables (which are costly to maintain) and is a preferred method for relating specific modules of business applications which may be logically separated.

Many views are generated automatically. The names of many of the views delivered with R/3 begin with the letter V and usually contain the name of the primary table, such as VZZB.

Reward if Helpful

Jagadish