topic Re: views in Application Development and Automation Discussions

views

Former Member — Fri, 28 Mar 2008 09:19:54 GMT

what r the types of views? what is the maintenance view?

Re: views

Former Member — Fri, 28 Mar 2008 09:22:29 GMT

Check out these relaated threads

Re: views

Former Member — Fri, 28 Mar 2008 09:23:05 GMT

hi ,

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

regards,

venkat

Re: views

Former Member — Fri, 28 Mar 2008 09:24:35 GMT

hi,

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2cceb190-0201-0010-be88-acdbeb2ad65f

http://help.sap.com/saphelp_nw04s/helpdata/en/ea/cf9441026aae5fe10000000a1550b0/frameset.htm

http://help.sap.com/saphelp_nw04/helpdata/en/bb/db029f4a3011d189490000e8323c4f/frameset.htm

pankaj

Re: views

Former Member — Fri, 28 Mar 2008 09:26:40 GMT

These are different types of views:

1) Database views

2) Projection views

3) Help views

4) Maintenance views

Maintenance View ( SE54 )

Reward if useful

regards

ravikanth

Re: views

Former Member — Fri, 28 Mar 2008 09:27:52 GMT

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.

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 )

If its useful reward points

Re: views

Former Member — Fri, 28 Mar 2008 09:30:47 GMT

hi,

Data for an application object is often distributed on several database tables. Database systems

therefore provide you with a way of defining application-specific views on data in several tables. These

are called views.

Data from several tables can be combined in a meaningful way using a view (join). You can also hide

information that is of no interest to you (projection) or only display those data records that satisfy certain

conditions (selection).

The data of a view can be displayed exactly like the data of a table in the extended table maintenance.

DataBase Views.

A database view is defined in the ABAP Dictionary and automatically created on the database during

activation. Accesses to a database view are passed directly to the database from the database interface.

The database software performs the data selection.

If the definition of a database view is changed in the ABAP Dictionary, the view created on the database

must be adjusted to this change. Since a view does not contain any data, this adjustment is made by

deleting the old view definition and creating the view again in the ABAP Dictionary with its new definition.

The maintenance status defines whether you can only read with the view or whether you can also write

with it. If a database view was defined with more than one table, this view must be read only.

The data read with a database view can be buffered. View data is buffered analogously to tables. The

technical settings of a database view control whether the view data may be buffered and how this should

be done. The same settings (buffering types) can be used here as for table buffering. The buffered view

data is invalidated when the data in one of the base tables of the view changes.

You can include entire tables in database views. In this case all the fields of the included table become

fields of the view (whereby you can explicitly exclude certain fields). If new fields are included in the table

or existing fields are deleted, the view is automatically adjusted to this change. A new or deleted field is

therefore automatically included in the view or deleted from it.

If an append structure is added to a table included in a view, the fields added with the append structure

are automatically included in the view.

To include a table in a view, you must enter the character '*' in field View field in the view maintenance,

the name of the table to be included in the field Table and the character '*' again in the field Field name.

Maintainance Views.

Data that is distributed on more than one table often forms a logical unit, called an application object.

You should be able to display, change and create the data of such an application object together. Users

usually are not interested in the technical implementation of the application object, such as the

distribution of the data on several tables.

You can maintain complex application objects in a simple way using a maintenance view. The data is

automatically distributed on the underlying database tables.

All the tables used in a maintenance view must be linked with a foreign key. This means that the join

conditions are always derived from the foreign key in the maintenance view. You cannot enter the join

conditions directly as in a database view.

A maintenance interface with which the data of the view can be displayed, changed and created must be

generated from the definition of a maintenance view in the ABAP Dictionary.

When the maintenance interface is created, function modules that distribute the data maintained with the

view on the underlying tables are automatically generated.

The maintenance interface is generated with the Transaction Generate Table View (Transaction SE54)

or from the view maintenance screen with Environment -> Tab.maint.generator.

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

included in the view.

Maintenance views implement an outer join.

Hope this helps, Do reward.

Re: views

Former Member — Fri, 28 Mar 2008 09:33:15 GMT

hi,

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

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.

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.

reward if found useful.

Re: views

Former Member — Fri, 28 Mar 2008 09:40:56 GMT

Hi,

R/3 System offers following types of views:

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

Maintenance Views

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.

Regards,

Bhaskar