views

[Former Member]

(Q) There are four types of views namely

Projection view, Database view, Help view and Maintenance view.

Only the first two can be used in the ABAP program.

In which situations the rest two can be used?

I would like to award more points you. Pls send me the answers.

Thanks & Regards,

veni.

[Former Member]

hui krishna,

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

All the tables included in a help view must be linked with foreign keys. Only foreign keys that have certain attributes can be used here

A help view implements an outer join

-

---

Maintenance views enable a business-oriented view on data, while at the same time, making it possible to maintain the data involved. Data from several tables can be combined in a maintenance view and maintained collectively with this view. That is, the data is entered with the view and then distributed to the underlying tables by the system.

A standardized table maintenance transaction is provided for this (SM30), permitting you to maintain the data from the base tables of a view at one time. The data can often also be maintained with customizing transactions.

Database view

- defined just as a table is defined within the database

- one or more related tables may be used

- only transparent tables may be used

Help view

- accessed from within transactions

- accessed only from within SAP Help

- Open SQL and Native SQL cannot access

- only 1:1 and 1:C relationships are possible

Projection view

- allows suppression of some fields within transparent table displays

Maintenance view

- enables table maintenance via SM30

- allows specific customizing transactions

<b>Hope this is helpful, Do reward points.</b>

Message was edited by:

Runal Singh

[Former Member]

Hai krishna,

Help Views

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.

All the tables included in a help view must be linked with foreign keys. Only foreign keys that have certain attributes can be used here (see Restrictions for Maintenance and Help Views). The first table to be inserted in the help view is called the primary table of the help view. The tables added to this primary table with foreign keys are called secondary tables.



The functionality of a help view has changed significantly between Release 3.0 and Release 4.0. In Release 3.0, a help view was automatically displayed for the input help (F4 help) for all the fields that were checked against the primary table of the help view. This is no longer the case in Release 4.0.

As of Release 4.0, you must explicitly create a search help that must be linked with the fields for which it is offered (see Linking Search Helps with Screen Fields).

Existing help views are automatically migrated to search helps when you upgrade to a release higher than 4.0.



A help view implements an outer join, i.e. all the contents of the primary table of the help view are always displayed. You therefore should not formulate a selection condition for fields in one of the secondary tables of the help view. If records of these secondary tables cannot be read as a result of this selection condition, the contents of the corresponding fields of the secondary table are displayed with initial value.

Creating Help Views

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 Copy. The secondary table involved in such a foreign key is included in the view. The join conditions derived from the foreign keys (see Foreign Key Relationship and Join Condition) are displayed.

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

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

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

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

9.Choose Active.
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.

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.

hope this will clear ur doubt

reward for useful answers

Regards,

sunil kairam

[Former Member]

Hi,

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.

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

Regards,

[Former Member]

hui krishna,

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

All the tables included in a help view must be linked with foreign keys. Only foreign keys that have certain attributes can be used here

A help view implements an outer join

-

---

Maintenance views enable a business-oriented view on data, while at the same time, making it possible to maintain the data involved. Data from several tables can be combined in a maintenance view and maintained collectively with this view. That is, the data is entered with the view and then distributed to the underlying tables by the system.

A standardized table maintenance transaction is provided for this (SM30), permitting you to maintain the data from the base tables of a view at one time. The data can often also be maintained with customizing transactions.

Database view

- defined just as a table is defined within the database

- one or more related tables may be used

- only transparent tables may be used

Help view

- accessed from within transactions

- accessed only from within SAP Help

- Open SQL and Native SQL cannot access

- only 1:1 and 1:C relationships are possible

Projection view

- allows suppression of some fields within transparent table displays

Maintenance view

- enables table maintenance via SM30

- allows specific customizing transactions

<b>Hope this is helpful, Do reward points.</b>

Message was edited by:

Runal Singh