topic Re: different views in Application Development and Automation Discussions

different views

Former Member — Fri, 15 Feb 2008 04:57:48 GMT

hi experts,

we have 4 types of views.

1. database view

2.projection view

3.maintanance view

4.help view

i want to know the difference among them. can anyone plz help me to know abt individual view, and the difference among them. give me the data abt each view, n the difference among them.

thanks in advance for ur responce.

Re: different views

Former Member — Fri, 15 Feb 2008 05:02:38 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.

Re: different views

Former Member — Fri, 15 Feb 2008 05:03:44 GMT

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 )

View are improves perfromance in the following aspects

1. If you want to use more than two table in 'JOIN' condition better to use Views . It will improves performance of a program

2. If you want to use mutiple FOR ALL ENTRIES clause, better to club all SELECT statement in a view.

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&;

Re: different views

Former Member — Fri, 15 Feb 2008 05:04:17 GMT

Hi.

Check this link.

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

Regards.

Jay

Re: different views

Former Member — Fri, 15 Feb 2008 05:04:44 GMT

Different Types of Views

1. Database View

Creating a Database View Locate the document in its SAP Library structure

Procedure

1. Enter an explanatory short text in the field Short text.

You can for example find the view at a later time using this short text.

2. Define the tables to be included in the view in the Tables field of the Tables/Join conditions tab page.

Keep in mind that you can only include transparent tables in a database view.

3. Link the tables with

join conditions.

If there are suitable foreign keys between the tables, you should copy the join conditions from these foreign keys (see Structure link Foreign Key Relationships and Join Conditions).

Place the cursor on a table name and choose Relationships. All foreign keys to other tables defined for this table are displayed. Select the foreign keys and choose This graphic is explained in the accompanying textCopy. The join condition is now derived from the definitions in the foreign key.

If you only want to see the foreign key relationship existing between two tables, you must first select these two tables (click on the first column of the input area Tables) and then choose Relationships.

4. On the View fields tab page, select the fields that you want to copy to the view.

Choose Table fields. All the tables contained in the view are displayed in a dialog box. Select a table. All the fields contained in this table are displayed. You can copy fields by selecting them in the first column and choosing This graphic is explained in the accompanying textCopy.

You can also include an entire table in the view (see Includes in Database Views).

5. On the Selection conditions tab page, you can (optionally) formulate restrictions for the data records to be displayed with the view (see

Maintaining Selection Conditions for Views).

The selection conditions define the data records that can be selected with the view.

6. With Goto ® Technical settings, you can (optionally) maintain the technical settings of the database view.

You can define whether and how the database view should be buffered here. Proceed as for the technical settings of a table (see Structure link Maintaining Technical Settings). Note that only the settings for buffering can be maintained for database views.

7. On the Maintenance status tab page, select the

maintenance status of the database view.

If the view contains more than one table, the maintenance status read only cannot be altered.

8. Save your entries. You are asked to assign the view a development class.

You can change this development class later with Goto ® Object directory entry.

9. Choose This graphic is explained in the accompanying text.

Result

When a database view is activated, the corresponding view is also automatically created in the database if the base tables of the view were already created there.

At activation, a log is written; it can be displayed with Utilities ® Activation log. If errors or warnings occurring when the view was activated, they are displayed directly in the activation log.

If the base tables are not yet created in the database, this is recorded in the activation log. The view is nevertheless activated in the ABAP Dictionary. In this case you can create the relevant view on the database later with the database utility.

Other Options

Create documentation: You can create information about using the view with Goto
® Documentation. This documentation is also output for example when you print the view. Change data element of a view field: Select the Mod (Modify) column in the View fields tab page. The Data element field is now ready for input. You can enter a data element that refers to the same domain as the data element of the assigned table field here. Cancel the Mod flag if you want to use the data element of the assigned table field again.
Display view data: With Utilities
® Contents you can determine which data can be selected with the view. Display create statement: With Extras
® CREATE statement you can display how the view was created in the database. The statement that was executed when the version of the view currently being edited was created in the database is displayed. Check the definition of the view in the database: With Utilities
® Database object ® Check you can determine whether the definition of the view in the database is consistent with the active version of the view. With Utilities ® Database object ® Display you can display the definition of the view in the database. Check the runtime object of the view: With Utilities

® Runtime object ® Check you can determine whether the definition of the view in the ABAP Dictionary maintenance screen is identical to the specifications in the runtime object of the view. With Utilities ® Runtime object ® Display you can display the runtime object of the view.

2. Projection View

Creating Projection Views Locate the document in its SAP Library structure

Procedure

1. Enter an explanatory short text in the field Short text.

You can for example find the view at a later time using this short text.

2. Enter a table name in the field Base table.

A projection view always contains exactly one table.

3. Select the fields of the base table that you want to include in the view.

Choose Table fields. The fields of the table are now displayed in a dialog box. You can copy fields by selecting them in the first column and choosing This graphic is explained in the accompanying textCopy.

4. Save your entries.

You are asked to assign the view a development class. You can change this development class later with Goto ® Object directory entry.

5. Choose This graphic is explained in the accompanying text.

Result

The help view is activated. At activation, a log is written; it can be displayed with Utilities ® Activation log. If errors or warnings occurring when the view was activated, they are displayed directly in the activation log.

Other Options

Create documentation: You can create information about using the view with Goto
® Documentation. This documentation is output for example when you print the view. Change data element of a view field: Select column Mod (modification) for the particular view field. The Data element field is now ready for input. You can enter a data element that refers to the same domain as the data element of the assigned table field here. Cancel the Mod flag if you want to use the data element of the assigned table field again.
Change maintenance status: The
maintenance status determines how you can access the view data from ABAP programs (read only, read and change). Choose Extras ® Maintenance status. A dialog box appears in which you can select the maintenance status of the view. Check functions: With Utilities

3. Maintainence View

Maintenance View Locate the document in its SAP Library structure

Definition

Related data in several tables can be maintained together in a maintenance view.

Structure

A maintenance view has the samee key as its primary table. To ensure that the system can write the records inserted in a maintenance view correctly into the tables in the view, put all key fields of the primary table in a maintenance view.

Each entry in the primary table can have at most one dependent data record in the secondry table. The only exceptions are the text tables of tables in the view which have the additional key field Language. The system puts the logon language in the language field during the table maintenance. You cannot put the language field in the view explicitly.

You can maintain text table entries in other languages with the translation function in transaction SM30.

Caution

You must regenerate the maintenance dialog if you change the definition of a table/view with a generated maintenance dialog, e.g. add or remove fields, or change the maintenance attribute or a selection condition.

Maintenance Attributes

You can assign a maintenance attribute P to individual fields in the maintenance view definition in the Dictionary (SE11). It can be R (read only), H (hidden), or S (subset).

R (readonly)

A field flagged R is not ready for input by the user on the screen. When a new data record is created, it must be filled automatically in the background. To fill a field automatically in the background, create a routine for an event.

H (hidden)

A field flagged H is not displayed on the screen. This field must also be filled in the background by a routine at an event.

The system writes R and H fields to the database like all other fields when a new data record is saved.

S (subset)

A field flagged S restricts the work area.

The system only shows data records for which this subset field has the specified value. This restriction of the work area remains effective when you create new data records.

View Variant

You can define any number of view variants for an existing view. The view variants do not have their own generated maintenance dialogs, they use the base view. The view variants can differ from their base view by different selection conditions and a different field selection.

4. Help View

Creating Help Views Locate the document in its SAP Library structure

Procedure

1. Enter an explanatory short text in the field Short text.

You can for example find the view at a later time using this short text.

2. Enter the primary table of the view under Tables in the Tables/Join conditions tab page.

Only tables that are linked with the primary table (indirectly) with a foreign key can be included in the view.

3. Save your entries.

You are asked to assign the help view a development class. You can change this development class later with Extras ® Object directory entry.

4. If required, include more tables in the view. In a help view you can only include tables that are linked to one another with foreign keys.

Position the cursor on the primary table and choose Relationships. All existing foreign key relationships of the primary table are displayed. Select the foreign keys and choose This graphic is explained in the accompanying textCopy. The secondary table involved in such a foreign key is included in the view. The join conditions derived from the foreign keys (see Structure link Foreign Key Relationship and Join Condition) are displayed.

You can also include tables that are linked with a foreign key to one of the secondary tables already included. To do this, place the cursor on the secondary table and choose Relationships. Then proceed as described above.

For maintenance and help views, there are certain restrictions on the foreign keys with which the tables can be included in the view (see Restrictions for Maintenance and Help Views). The foreign keys violating these conditions are displayed at the end of the list under the header Relationships with unsuitable cardinality.

5. On the View fields tab page, select the fields that you want to copy to the view. The key fields of the primary table were automatically copied to the view as proposals.

Choose Table fields. All the tables contained in the view are listed in a dialog box. Select a table. The fields of the table are now displayed in a dialog box. Select the required fields in the first column and choose This graphic is explained in the accompanying textCopy.

6. On the Selection conditions tab page, you can (optionally) formulate restrictions for the data records to be displayed with the view (see

Maintaining Selection Conditions for Views).

The selection conditions define the data records that can be selected with the view.

7. Choose This graphic is explained in the accompanying text.

Result

The view is now activated. At activation, a log is written; it can be displayed with Utilities ® Activation log. If errors or warnings occurring when the view was activated, they are displayed directly in the activation log.

Other Options

Create documentation: You can create information about using the view with Goto
® Documentation. This documentation is output for example when you print the view. Change data element of a view field: Select column Mod (modification) for the view field. The Data element field is now ready for input. Enter the new data element there. You can enter a data element that refers to the same domain as the data element of the assigned table field here. Cancel the Mod flag if you want to use the data element of the assigned table field again.
Check functions: With Extras

® Runtime object ® Check you can determine whether the definition of the view in the ABAP Dictionary maintenance screen is identical to the definitions in the runtime object of the view. With Extras ® Runtime object ® Display you can display the runtime object of the view.

Regards,

Re: different views

Former Member — Fri, 15 Feb 2008 05:05:19 GMT

Hi,

Database View: You can create this view on transparent table. It supports all the three operations like Selection, Projection & Join

Projection View: This type allows you to suppress some fields from the transparent table. This view is defined only with relational operator projection.

Help View: These views are exclusively used by the SAP help system. All relational operators are supported. These views are generated when the user presses F4 function key on the field on selection screen. You can see these views only with SAP help and not with open SQL statements.

Maintenance View: This type of view enables the maintenance of a group of related tables using SM30 Transaction, which is for extended table maintenance.

Regards,

Bhaskar

Re: different views

Former Member — Fri, 15 Feb 2008 05:06:37 GMT

refer to this link

Thanks

Krushna

Re: different views

sreelatha_gullapalli — Fri, 15 Feb 2008 05:17:08 GMT

why we need view is:

1)A view is a virtual table which gets data from different tables and displays on a single screen actually in real time every time we require data from different tables in such case we create a view and we call that view in the program.

2) Z tables are required when there is no table of a particular field according to my client requirement then we go for ztabls

3) Both are same in new versions se16n which is used for data browser

Database Views

A database view is defined in the ABAP Dictionary as a logical view on one or more tables. A database view is automatically created in the underlying database when it is activated.

Re: different views

Former Member — Fri, 15 Feb 2008 05:31:14 GMT

Hi Dude,

DB View:

The database view is the only type of view in SAP that is physically created at the database level. In other words, the underlying database system also directly recognises the view, apart from SAP. Therefore, database views must be created over transparent tables.

With the database view, all three of the relational operations (projection, selection, and join) can be used.

Database views can be buffered just like transparent tables. In the technical settings you can decide whether to have buffering off, or on with type single record, generic, or full.

Can be built over many tables

Data can be updated if the view is built over a single table

Data updates can use open SQL or Native SQL

Updates are more efficient than using

a Projection View

Fields in the view can be named differently from the fields in the underlying table(s)

Can be buffered

The projection view is a logical view. In this context, the word “logical” means that the view exists within the ABAP Dictionary but is not recognised by the underlying database system.

Projection views must be defined over a single transparent table.

The only relational operation that is valid for a projection view is projection.

Must be built over a single table

Data can be updated

Data updates must use open SQL

Updates are less efficient than using a Database View

Fields in the view must be named the same as the fields in the

underlying table

Can’t be buffered

Help Views: Help views can be used as selection methods for Search Helps. (see chapter 1.10.x). It might be necessary to create a Help View if you are trying to accomplish an outer join (see section 2.12.11), since database views only create inner joins.

Maintenance Views: These views permit maintenance of base table data. Transactions SM30 and SE54 are provided for working with maintenance views.

Regards,

Lakshmanan

Re: different views

Former Member — Fri, 15 Feb 2008 07:07:54 GMT

thank u very much for ur answres