Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
Help view is created mainly as a selection method for a search help. You can join multiple tables in a help view.
The selection criteria for a search help will have to be passed through the input parameters and default values. You can also specify parameter ids in the default values column.
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.
VIEW is nothing but IMAGINARY TABLE. It contains the data during runtime only.
Tyeps of VIEWS ARE
Database view
Projection View
Maintenance view
Help view
Search help- Using this We can create for the field for the interner search purpose only. If user presses the F4 KEY he can search the values which are present in that particular field.
View are nothing but a join of one or more tables. Based on your join condition, the records are displayed in the form of a table. This improves performance too, and avoids spending more time on figuring out the how to write the select query for a join.
But Views have only INNER JOINS.
Search help: can also be created by you to have the F4 help for any particular field. You can use MATCHCODE OBJECT clause in parameters or select-options to display your F4 help.
Bluesky
