Regarding data dictionary views

[Former Member]

Hi all,

I have a query regarding views.

1)can we include the fields of a structure into a view?

2)what are the prerequisites to create view?

3)is it necessary for all the tables to have the forign key relationship among them which r being included in a view?

4)how to identify the base tables and secondary tables to include in a view?

Awaitning your response.

Thanks in advance!!!

[Former Member]

We have 4 types of Views:

1) Database views

2) Projection views

3) Help views

4) Maintenance views

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.

a database view is implemented in the database, a database view may only contain transparent tables.

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

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

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

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 alco not contain the data physicaly, you can look at the VIEWS in se11 byselecting the View. there you can not see the data for that view, but if you write a select statment the data retrived by the corresponding tables and will be displayed, but In the DATABASE view, when you write a select statment, it wil have the buffer facility, so the data will be stored in the buffers. so no view can contain the data physicaly

regards,

rewards point.

[Former Member]

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.

Also check this link for more information.

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

Hope this will help.

Regards,

rewards point.

[Former Member]

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.

Creating Database View:

http://help.sap.com/saphelp_nw2004s/helpdata/en/cf/21ed06446011d189700000e8322d00/content.htm

Creating Projection View:

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

Creating Help View:

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

Creating maintenance View:

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

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

There are lot many links in SDN as well as in google where u can get as much information as u want , so plzz check those things before posting.

if u hav any doubts then u can ask furthere.

regards,

rewards point

[Former Member]

Hello jyothi,

1. yes, we can include the fileds of structure into a view

2. views can't store the data, but can access the data from one or more tables at a time. so the prerequisites r from what tables u want to access the data, u have to identify.

Regards

Venkata prasad

[varma_narayana]

Hi Jyoti,,

1)can we include the fields of a structure into a view?

No.. Views can only include fields from Tables..

2)what are the prerequisites to create view?

When there is no Suitable view exists.

When you want to Avoid writing the Joins

3)is it necessary for all the tables to have the forign key relationship among them which r being included in a view?

To Create Database view .. Foreign key Relation is not must.

To Create Maintenance view .. Foreign key Relation is must.

4)how to identify the base tables and secondary tables to include in a view?

While Creating a view (Database / Maintenance view ) You can Click on the Relationships button to find out these tables.

<b>Reward if Helpful</b>

[Former Member]

1.No we can not include the fields of a structure into a view.

2.Tables should have at least one common field

3. It is necessary for all the tables to have the forign key relationship among them which r being included in a view.

[Former Member]

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.