diff between elementary & collective serach help?

[Former Member]

frends tell me diff between elementary & collective serach help?

[Former Member]

Hi Rajareddy.....

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.

An elementary search help defines the standard flow of an input help.

A collective search help combines several elementary search helps. The user can thus choose one of several alternative search paths with a collective search help.

When you define a collective search help, you only have to specify the search helps that are to be combined in the collective search help. In the input help, the values are transported between the elementary search help selected by the user and the input template using the collective search help. This is why a collective search help also has an interface for transporting the values.

Also see:

http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ee38446011d189700000e8322d00/frameset.htm

http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ee45446011d189700000e8322d00/frameset.htm

Reward points if useful......

Suresh......

[Former Member]

Hi raja,

An elementary search help defines the standard flow of an input help. You can define the following components of this flow in the search help:

where does the data displayed in the hit list come from (selection method)

what information should be displayed in the dialog box for value selection and in the hit list (search help parameters)

what field contents can be taken into account for hit list selections and which values in the hit list can be returned to the screen fields (search help parameters)

what dialog steps should be executed in the input help (dialog behavior)

chk this for more details:

http://help.sap.com/saphelp_erp2005/helpdata/en/cf/21ee38446011d189700000e8322d00/frameset.htm

A collective search help combines several elementary search helps. The user can thus choose one of several alternative search paths with a collective search help.

When you define a collective search help, you only have to specify the search helps that are to be combined in the collective search help. In the input help, the values are transported between the elementary search help selected by the user and the input template using the collective search help. This is why a collective search help also has an interface for transporting the values.

chk this for more details:

http://help.sap.com/saphelp_erp2005/helpdata/en/cf/21ee38446011d189700000e8322d00/frameset.htm

regards,

keerthi

[Former Member]

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

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

3)An elementary search help defines the standard flow of an input help.

4) A collective search help combines several elementary search helps. The user can thus choose one of several alternative search paths with a collective search help.

5)A collective search help comprises several elementary search helps. It combines all the search paths that are meaningful for a field.

6)Both elementary search helps and other search helps can be included in a collective search help. If other collective search helps are contained in a collective search help, they are expanded to the level of the elementary search helps when the input help is called.

http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ee38446011d189700000e8322d00/content.htm

http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ee45446011d189700000e8322d00/content.htm

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.

A collective search help combines several elementary search helps. The user can thus choose one of several alternative search paths with a collective search help.

Elimentary search help is a single search help and you will not see any more TAB's in the search help you will see only one dialog screen or directly the data.

In the case of collective search help you will have collection of search helps in to one search help. Dialogs of each search will be available as one TAB in the search help for that field. You include search helps which are similar into one collective search and use that for your field.

sri

[Former Member]

Elementary Search Help SCUSTOM_BOOK

This elementary search help should enable you to search for the customer number using existing customer bookings. The flight data for the booking (flight number, date of flight, city of departure, city of arrival) and the name of the customer should be used for the search here. This data is distributed on the tables SBOOK (bookings), SCUSTOM (name) and SPFLI (cities of departure and arrival). The following graphic shows the relationship between the relevant tables, that is the existing foreign key relationships.

In this case a database view SCUS_BOOK must be created on these three tables (see Example for Views) as selection method. The tables in the view (join) are linked as defined by the existing foreign key relationships (see Foreign Key Relationship and Join Condition).

In the dialog box for restricting values, the user should be able to restrict the search for booking data with the carrier ID, customer name, city of departure and city of arrival The flight date and of course the customer number should also be displayed in the hit list. Fields CARRID, FLDATE, CUSTOMID, NAME, CITYFROM and CITYTO of view SCUS_BOOK must be included in the elementary search help as parameters of the search help.

The parameter CUSTOMID is declared to be an import parameter. All the parameters of the search help are export parameters.

Collective Search Help SCUSTOM

The two elementary search helps are now included in the collective search help. You must now allocate the parameters of the elementary search helps to the parameters of the collective search help.

The parameter ID of the collective search help is marked as an import parameter. All the parameters are export parameters. The values can thus be copied from the hit list to the screen template.

this makes good idea about your question.