topic Re: views in Application Development and Automation Discussions

views

Former Member — Mon, 07 May 2007 05:14:46 GMT

what is the use of maintanence view plz explain exact diff in breif.

Re: views

Former Member — Mon, 07 May 2007 05:15:50 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.

Please have a look at below link. It will help you.

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

for more detailed info look on:

http://www.sap-img.com/abap/what-is-the-different-types-and-usage-of-views.htm

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/abap+dictionary&;

Reward points if useful

Regards

Anji

Re: views

Former Member — Mon, 07 May 2007 05:25:33 GMT

Hi,

Maintenance views offer easy ways to maintain complex application objects.

Data distributed on several tables often forms a logical unit, for example an application object, for the user. You want to be able to display, modify and create the data of such an application object together. Normally the user is not interested in the technical implementation of the application object, that is in the distribution of the data on several tables.

A maintenance view permits you to maintain the data of an application object together. The data is automatically distributed in the underlying database tables. The maintenance status determines which accesses to the data of the underlying tables are possible with the maintenance view.

database view

Data about an application object is often distributed on several database tables. A database view provides an application-specific view on such distributed data.

Database views are defined in the ABAP Dictionary. A database view is automatically created in the underlying database when it is activated.

Application programs can access the data of a database view using the database interface. You can access the data in ABAP programs with both OPEN SQL and NATIVE SQL. However, the data is actually selected in the database. Since the join operation is executed in the database in this case, you can minimize the number of database accesses in this way. Database views implement an inner join

projection view

Projection views are used to hide fields of a table. This can minimize interfaces; for example when you access the database, you only read and write the field contents actually needed.

A projection view contains exactly one table. You cannot define selection conditions for projection views.

There is no corresponding object in the database for a projection view. The R/3 System maps the access to a projection view to the corresponding access to its base table. You can also access pooled tables and cluster tables with a projection view.

help views

Help views are used if a view with an outer join is needed as selection method in a search help.

You have to create a help view if a view with outer join is needed as selection method of a search help.

The selection method of a search help is either a table or a view. If you have to select data from several tables for the search help, you should generally use a database view as selection method. However, a database view always implements an inner join. If you need a view with outer join for the data selection, you have to use a help view as selection method.

Rgds,

Prajith

Re: views

Former Member — Mon, 07 May 2007 05:26:47 GMT

Hi Manjula,

<b>Maintenance View ( SE54 )</b>

<b>plz reward points if helpful or if it solves ur query.</b>

Thanks

Chinmay

Re: views

Former Member — Mon, 07 May 2007 05:29:06 GMT

Hi Manjula,

The set of data that can be selected with a view greatly depends on whether the view implements an

inner join or an outer join.

n With an inner join, you only get those records which have an entry in all the tables included in the

view. With an outer join, on the other hand, those records that do not have a corresponding entry in

some of the tables included in the view are also selected.

n The hit list found with an inner join can therefore be a subset of the hit list found with an outer join.

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

tables included in the view.

n Maintenance views implement an outer join.

Maintenance views may not be used as the selection method for search helps. Normally a database

view is used. However, you should note that database views (in the R/3 System) are always created

with an inner join. As a result, only those values having an entry in each of the tables involved are

offered in the input help. Sometimes the values should be determined with an outer join. In this case

you should choose a help view as the selection method

Regards,

Jayant

Re: views

Former Member — Mon, 07 May 2007 05:30:59 GMT

Hi Manjula,

The followings are different types of views:

- Database View (SE11)

- Help View ( SE54)

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

- Projection View

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

- Maintenance View ( SE54 )

Please have a look at below link. It will help you.

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

for more detailed info look on:

http://www.sap-img.com/abap/what-is-the-different-types-and-usage-of-views.htm

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/abap+dictionary&;

View is nothing but a logical table.....

no data will be stored in a view.

when u retrieve data from a view it internally retrieves from the database tables only...

but depending on the requirement u need to create a view..

For ex:

if u have a table with 300 fields.. and u need only 10 fields among them in the present scenario..then we need to create a projection view for that table with those 10 fields..

there are 4 type of views:

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.

Reward points if helpful.

Regards,

Hemant

Re: views

Former Member — Mon, 07 May 2007 05:33:36 GMT

In this view the changes affect to the table too