diff between maintence and database views

[Former Member]

pls answer now,its urgent

[Former Member]

- 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.

- 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.

[Former Member]

Hi

Database Views

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 (see Inner and Outer Join).

If the database view only contains a single table, the maintenance status can be used to determine if data records can also be inserted with the view. If the database view contains more than one table, you can only read the data.

Database views should be created if want to select logically connected data from different tables simultaneously. Selection with a database view is generally faster than access to individual tables. When selecting with views, you should also ensure that there are suitable indexes on the tables contained in the view.

Maintenance View:

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.

All the tables in a maintenance view must be linked with foreign keys, that is the join conditions for maintenance views are always derived from the foreign key You cannot directly enter the join conditions as for database views.

There are some restrictions for the attributes of the foreign keys with which the tables in a maintenance view can be linked

A standardized table maintenance transaction is provided (SM30), permitting you to maintain the data from the base tables of a maintenance view together.

Maintenance mechanisms, like screens and processing programs, must be created from the view definition with the transaction Generate Table View (SE54). This makes it possible to create easy-to-use maintenance interfaces in a simple manner.

If it is helpful rewards points

Reagards

Pratap.M

[Former Member]

hi,

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.

Hope this helps, Do reward.

[Former Member]

Hi,

Updating more than one database tables by using database view is not possible.

Whereas it is possible by using maintenance view.

Reward me if it is useful.

[Former Member]

Hi ,

View - A view is a virtual table containing fields from one or more tables. A virtual table that does not contain any data, but instead provides an application-oriented view of one or more ABAP Dictionary tables.

Different Types of View:

1)Maintenance

2)Database – It is on more than two tables.

3)Projection – It is only on one table.

4)Help

Database view:

View type in ABAP Dictionary.

Database views are defined in the ABAP Dictionary and automatically created in the underlying database when activated.

Maintenance View:

View type in ABAP Dictionary.

You can use a maintenance view to maintain data, which is distributed over several tables, at the same time.

Regards,

Thasneem

reward if useful

[Former Member]

hi,

A view can be tailored to the needs of a specific application, making it possible to directly access specific data. The structure of such a view is defined by specifying the tables and fields to be contained in the virtual table.

A view can be used to summarize data which is distributed among several tables. In addition, superfluous fields can be suppressed, keeping interfaces to a minimum.

A view relates logically to one or more tables. That is, the data of a view is not actually physically stored. The data of a view is instead derived from one or more other tables.

1.Enter the name of the view in the initial screen of the ABAP/4 Dictionary.

Select object class Views and click on the Create pushbutton. A dialog box appears,in which the user must choose the type of the view. Select the type Database view.

2.Enter a short explanatory text in the field Short text.

3.In Tables, enter the tables (base tables) which are to be included in the view.

4.Link the included tables via join conditions.

5.Select the fields which are to be included in the view.

6.Formulate the selection conditions.

7.Save entries. Assign the view a development class.

8.Activate the view via View  Activate.

SM30 Maintain data in maintenance views

[Former Member]

Data base views for selecting the data from DB table.

Maintanance views for used in the MPP applications.

Data base views are only read only, but maintance views are read/write/change/delete.

In maintanance view the joins are auto generated.

[Former Member]

Pls refer

http://www.sourceveda.com/page3.htm

for similar FAQs

[Former Member]

hi,

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.

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.