View....

[Former Member]

1) wat are the differences between database view, maintainance view, Projection view, help view? pls give the exact differences.....

[Former Member]

Hi,

have a look at this.

4 type of views

database

maintainance

help

projection view

check this link as well

(https://forums.sdn.sap.com/click.jspa?searchID=9904886&messageID=4885135)

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

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

Database views should be created if want to select logically connected data from different tables simultaneously.

Database views implement an inner join.

Application programs can access the data of a database view using the database interface. (Just as we write select queries on database tables, we can write them for views as well.)

Includes in Database Views

An entire table can be included in a database view. In this case all the fields of the included table will become fields of the view (whereby you can explicitly exclude certain fields).

To include one of the tables in the view, enter character * in field View field, the name of the table to be included in field Table and character * again in field Field name on the View fields tab page of the maintenance screen of the view.

You can also exclude individual fields of an included table. If you do not want to include a field of the included table in the view, enter - in field View field, the name of the included table in field Table and the name of the field to be excluded in field Field name.

Inserts with Database Views

If a database view contains only one single table, data can be inserted in this table with the view .

You have the following options for the contents of the table fields not contained in the view:

If the field is defined on the database with NOT NULL as initial value, the field is filled with the corresponding initial value.

If the field is defined on the database as NOT NULL without initial value, an insert is not possible. This results in a database error.

If the field is not defined on the database as NOT NULL, there will be a NULL value in this field.

A maintenance view permits you to maintain the data of an application object together.

The maintenance status determines which accesses to the data of the underlying tables are possible with the maintenance view.

Read only: Data can only be read through the view.

Read, change, delete, insert: Data of the tables contained in the view can be

changed, deleted, and inserted through the view.

Read and change: Existing view entries can be changed. However, records

cannot be deleted or inserted.

Read and change (time-dependent views): Only entries whose non-time

dependent part of the key is the same as that of existing entries may be

inserted.

Maintenance View ( SE54 )

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

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.

Creating maintenance View:

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

Reward Points if helpful.

Regards

Sandeep Reddy

[Former Member]

Hi Ajanta,

Check this info about views.

Views

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.

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 .

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.

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.

Check

Check below link also.

http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ec5d446011d189700000e8322d00/content.htm

Hope this is helpful to you. If you need further information, revert back.

Reward all the helpful answers.

Regards

Nagaraj T

[Former Member]

Hi,

In the ABAP-DDIC, we have the following views type:

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

Please check the following documents about views (database.. maintenance..)

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

Regards

Kiran Sure

[Former Member]

Definition of View:-

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

According to the requirement there are 4 views that are supported by SAP.

They are 1) Database views 2)Projection View 3) Help View 4) Maintenance View

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

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

3) Help View:- 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.

4) Maintenance View:- Maintenance views offer easy ways to maintain complex application objects.

Data distributed on several tables often forms a logical unit,it can also be called as an application object.

user will be able to display, modify and create the data of such an application object together.

A maintenance view permits user to maintain the data of an application object together. The data

in the maintenance view 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.

Hope this will give u a clear idea.

cheers,

[Former Member]

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.

Reward if it useful.

Lakshmi.

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

pls reward if helpful .

Regards .

Rajyalakshmi