maintenance veiw

[Former Member]

when i go making maintnence veiw it always happens that the total no of feilds which i have selected in veiw feilds tab will not appear on maitenence output scren.

what is the reason behind that.

moreover as per cndition all the feilds excpt primary feild can be updated but some other feilds also do not accept changes.

->what is basic difference between databse veiw and maintenance veiw.is it so that database veiw can be meant only for transarent tbles

which are linked to each other or indepent to each other.

[Former Member]

when i go making maintnence veiw it always happens that the total no of feilds which i have selected in veiw feilds tab will not appear on maitenence output scren.

what is the reason behind that.

moreover as per cndition all the feilds excpt primary feild can be updated but some other feilds also do not accept changes.

->what is basic difference between databse veiw and maintenance veiw.is it so that database veiw can be meant only for transarent tbles

which are linked to each other or indepent to each other.

[Former Member]

What is the Different Types and Usage of Views

This is often asked in an interview about the types of views:

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.

step by step creation of Maintenance view:

With the help of the table maintenance generator, you are able to maintain the ENTRIES of the table in SM30 transaction.

It can be set in transaction SE11 - Tools - Table maintenance generator.

Table maintanance Generator is used to manually input values using transaction sm30

follow below steps

1) go to se11 check table maintanance check box under attributes tab

2) utilities-table maintanance Generator-> create function group and assign it under

function group input box. Also assign authorization group default &NC& .

3) select standard recording routine radio in table table mainitainence generator to move table

contents to quality and production by assigning it to request.

4) select maintaience type as single step.

5) maintainence screen as system generated numbers this dialog box appears when you click on create button

6) save and activate table

One step, two step in Table Maintenance Generator

Single step: Only overview screen is created i.e. the Table Maintenance Program will have only one screen where you can add, delete or edit records.

Two step: Two screens namely the overview screen and Single screen are created. The user can see the key fields in the first screen and can further go on to edit further details.

SM30 is used for table maintenance(addition or deletion of records),

For all the tables in SE11 for which Table maintenance is selected , they can be maintained in SM30

Sm30 is used to maintain the table ,i.e to delete ,insert or modify the field values and all..

It creates the maintenance screen for u for the aprticular table as the maintenance is not allowed for the table..

In the SE11 delivery and maintenance tab, keep the maintenance allowed..

Then come to the SM30 and then enter the table name and press maintain..,

Give the authorization group if necessary and give the function group and then select maintenance type as one step and give the screen numbers as system specified..

Then create,,,

Then u will able to see the maintenance view for the table in which u can able to insert and delete the table values...

We use SM30 transaction for entering values into any DB table.

First we create a table in SE11 and create the table maintenance generator for that Table using (utilities-> table maintenance generator) and create it.

Then it will create a View.

After that from SM30, enter the table name and Maintain, create new entries, change the existing entries for that table.

Reward points if it is useful....

Girish

[Former Member]

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.

Pls refer

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

for similar FAQs

Cheers,

vasavi.

kindly rewrd if helpful.

[Former Member]

hi,

View Types

Four different view types are supported. These differ in the way in which the view is implemented and in the methods permitted for accessing the view data .

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

Maintenance views permit you to maintain the data distributed on several tables for one application object at one time.

Database Views

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.

Projection Views

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

For the above diagram, fields F3 and F4 are irrelevant, and therefore hidden from the projection view of the table.

Maintenance Views

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.

Maintenance Status

The maintenance status of a view controls whether data records can also be changed or inserted in the tables contained in the view.

The maintenance status can be defined as follows:

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.

Help Views

Help view is created if a view with outer join is needed as selection method of a search help.

Help views are used exclusively for search helps.

A conventional database view selects data from the database using an inner join.

For a help view however, data is selected using a left outer join.

Eg-> Suppose table SCARR (Airline master table) has AA – American airlines

AB – Air Berlin

AC- Air Canada as three entries.

Table SPFLI (Flight schedule) has entries corresponding only to airlines AA (American airlines) and AB (Air Berlin).

Now if a database view were to be used as a selection method for a search help for airlines, we would only get AA and AB as possible entries because the database view implements an inner join…….If however, we were to use a help view as the selection method here, we would get AA,AB and AC as possible entries because a help view would implement a left outer join.

Restrictions for Maintenance and Help Views

There are some restrictions for selecting the secondary tables of a maintenance view or help view. The secondary tables have to be in an N:1 dependency to the primary table or directly preceding secondary table. This ensures that there is at most one dependent record in each of the secondary tables for a data record in the primary table.

Append Views

Append views are used for enhancements of database views of the SAP standard.

With an append view, fields of the base tables of the view can be included in the view without modifications. This is analogous to enhancing a table with an append structure.

An append view is assigned to exactly one database view. More than one append view can be created for a database view.

The append technique described can only be used for database views. With an append view, only new fields from the base tables contained in the view can be inserted in the view. You cannot insert new tables in the view or modify the join conditions or selection conditions of the view.

Regards,

sreelakshmi

[Former Member]

Hi,

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

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 .

<![endif]>

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,

vineela

[Former Member]

Database View - This is inner join view of one or more tables

Maintenance View - Helps in creating maintaining data of the application object. The data can be distributed among several tables

DATABASE VIEW:

The database view is combining several fields of two or more tables into single table.

For example: Consider three tables T1,T2 and T3.

Fields of T1 are F1,F2 and F3.

Fields of T2 are F1,F5.

By using a Database view u can combine the fields of both T1 and T2 provided primary and foreign key relation is maintained between the two tables and final view can have fields like

F1,F2,F3,F5.

PROJECTION VIEW:

First will say the difference between projection and database view which is nothing but for projection view, view is maintained only in one table but in database view, view is maintained between 2 or more tables. Here single table view is not allowed

For projection view, view is maintained within a single table.

For example,if Table T1 has fields F1,F2,F3,F4,F5.