Views

[Former Member]

How can we create Help Views?

[Former Member]

Hello,

Have a look at this Thraead

If useful reward

Vasanth

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

Go thru this link plzz

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

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

1.Go to se11

2. select view radiobutton and give a name

3. Create

4. select type of view you want to create. Such as database view.

5. give short description

6. give a table name such as mara

7. press the pushbutton relationship. here you will find all the tables which are allowed to create view with mara.

8. select one or mane tables.

8 copy

9.save , check and activate.

Reward points for useful Answers

Regards

Anji

[Former Member]

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.

reward points if it is usefull ....

Girish

[Former Member]

Search Helps

The input help (F4 help) is a standard function of the R/3 System. The user can display the list of all possible input values for a screen

field with the input help. The possible input values can be enhanced with further information. This is meaningful especially when the field

requires the input of a formal key.

Standard Input Help Process

A user calls an input help with the following steps (some steps can be omitted, depending on the definition of the input help):

The user starts the input help to display the possible input values for a field (search field) in a screen template.

The system offers the user a number of possible search paths. The user selects one of these search paths. Each search path offers a

number of restrictions to limit the number of possible input values. These values are offered in a Dialog box for value restriction when

the search path is selected.

The user enters restrictions if required and then starts the search.

Function of a Search Help

This standard process can be completely defined by creating a search help in the ABAP Dictionary. This search help only has to be

assigned to the screen fields in which they should be available (see Attaching Search Helps to Screen Fields).

There are two types of search help:

Elementary search helps describe a search path. The elementary search help must define where the data of the hit list should be read

from (selection method), how the exchange of values between the screen template and selection method is implemented (interface of

the search help) and how the online input help should be defined (online behavior of the search help).

Collective search helps combine several elementary search helps. A collective search help thus can offer several alternative search paths.

All of the product names here are trademarks of their respective companies. The site

www.allsaplinks.com no way affiliated with SAP AG. We have made every effort for the content

integrity. Information used on this site is at your own risk.

regards

pradeep