topic Re: View in Application Development and Automation Discussions

View

Former Member — Fri, 10 Aug 2007 05:35:14 GMT

What is View? Types of View? Purpose of View?

Re: View

Former Member — Fri, 10 Aug 2007 05:40:25 GMT

HI,

Here are the Types of views

Database Views:

http://help.sap.com/saphelp_webas620/helpdata/en/cf/21ecab446011d189700000e8322d00/content.htm

Projection View:

http://help.sap.com/saphelp_webas620/helpdata/en/cf/21ecc5446011d189700000e8322d00/frameset.htm

Help Views:

http://help.sap.com/saphelp_webas620/helpdata/en/cf/21ecd2446011d189700000e8322d00/frameset.htm

Maintenance Views:

http://help.sap.com/saphelp_webas620/helpdata/en/cf/21ecdf446011d189700000e8322d00/frameset.htm

Regards

Sudheer

Re: View

Former Member — Fri, 10 Aug 2007 05:41:09 GMT

A view is a logical view on one or more tables, that is, a view is not actually physically stored, instead being derived from one or more other tables.

In the simplest case, this derivation process can involve simply suppressing the display of one or more fields from a table (projection) or transferring only certain records from a table to the view (selection). More complicated views can be assembled from several tables, with individual tables being linked using the relational join operation.

Use

Logical views for the application permitting direct access to the data can be generated with the definition of view. The structure of such a view is defined by specifying the tables and fields involved in the view.

types of view:

PROJECTION VIEW

DATABASE VIEW

HELP VIEW

MAINTENANCE VIEW

Regards

Debjani

Rewards point for helpful answer

Re: View

Former Member — Fri, 28 Mar 2008 09:30:16 GMT

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

Re: View

Former Member — Fri, 28 Mar 2008 09:35:49 GMT

hi,

Data for an application object is often distributed on several database tables. Database systems

therefore provide you with a way of defining application-specific views on data in several tables. These

are called views.

Data from several tables can be combined in a meaningful way using a view (join). You can also hide

information that is of no interest to you (projection) or only display those data records that satisfy certain

conditions (selection).

The data of a view can be displayed exactly like the data of a table in the extended table maintenance.

DataBase Views.

A database view is defined in the ABAP Dictionary and automatically created on the database during

activation. Accesses to a database view are passed directly to the database from the database interface.

The database software performs the data selection.

If the definition of a database view is changed in the ABAP Dictionary, the view created on the database

must be adjusted to this change. Since a view does not contain any data, this adjustment is made by

deleting the old view definition and creating the view again in the ABAP Dictionary with its new definition.

The maintenance status defines whether you can only read with the view or whether you can also write

with it. If a database view was defined with more than one table, this view must be read only.

The data read with a database view can be buffered. View data is buffered analogously to tables. The

technical settings of a database view control whether the view data may be buffered and how this should

be done. The same settings (buffering types) can be used here as for table buffering. The buffered view

data is invalidated when the data in one of the base tables of the view changes.

You can include entire tables in database views. In this case all the fields of the included table become

fields of the view (whereby you can explicitly exclude certain fields). If new fields are included in the table

or existing fields are deleted, the view is automatically adjusted to this change. A new or deleted field is

therefore automatically included in the view or deleted from it.

If an append structure is added to a table included in a view, the fields added with the append structure

are automatically included in the view.

To include a table in a view, you must enter the character '*' in field View field in the view maintenance,

the name of the table to be included in the field Table and the character '*' again in the field Field name.

Maintainance Views.

Data that is distributed on more than one table often forms a logical unit, called an application object.

You should be able to display, change and create the data of such an application object together. Users

usually are not interested in the technical implementation of the application object, such as the

distribution of the data on several tables.

You can maintain complex application objects in a simple way using a maintenance view. The data is

automatically distributed on the underlying database tables.

All the tables used in a maintenance view must be linked with a foreign key. This means that the join

conditions are always derived from the foreign key in the maintenance view. You cannot enter the join

conditions directly as in a database view.

A maintenance interface with which the data of the view can be displayed, changed and created must be

generated from the definition of a maintenance view in the ABAP Dictionary.

When the maintenance interface is created, function modules that distribute the data maintained with the

view on the underlying tables are automatically generated.

The maintenance interface is generated with the Transaction Generate Table View (Transaction SE54)

or from the view maintenance screen with Environment -> Tab.maint.generator.

Database views implement an inner join. You only get those records which have an entry in all the tables

included in the view.

Maintenance views implement an outer join.

Help View.

A help view is defined analogously to a maintenance view. Help views can only be used as selection

methods in search helps. Since the R/3 System cannot pass the selection directly to the database using

a help view, it must generate its own access routines. The database view should therefore be used as

selection method in preference to the help view.

It is customary to start the name of help views with the prefix `H_`. Views beginning with the prefixes

`H_Y` or `H_Z` therefore lie in the customer namespace.

Hope this helps, Do reward.