Search help multiple selection of search results

[Former Member]

Hi,

I have a search help (SE11) and it is correctly integrated in my WDP4A application using 'automatic' search help integration. Unfortunately multiple selection of search results does not seem to be supported (the ok button greys out when >1 result is selected). Is there a standard way to link a search help to an attribute in a 0..n value node, so that at runtime a new context element is created for each selected search result? Or do I have to recreate the search help from scratch to get this behaviour (OVS)?

If the latter is true, then why is it even possible to select multiple search results?

Kind regards,

Jeroen

[Former Member]

Hallo Jeroen,

OVS standard configuration does not allow you to select more than one configuration, You need to specify that explicitely on Phase-0 of OVS using the set_configuration method.

see

[|]

[http://wiki.sdn.sap.com/wiki/display/WDABAP/InputhelpofObjectValueSelectioninWDABAP|http://wiki.sdn.sap.com/wiki/display/WDABAP/InputhelpofObjectValueSelectioninWDABAP]

[http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70cee684-ccbb-2c10-3c94-91e806e5f7ac?quicklink=index&overridelayout=true|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70cee684-ccbb-2c10-3c94-91e806e5f7ac?quicklink=index&overridelayout=true]

[Former Member]

Thanks for the references!

[Former Member]

Hi Baskaran,

The references are very helpful, but I still have a question. Is there a way to make the OVS initialize itself as if I configured the relevant context attribute as "Automatic" Input Help Mode? In other words, I want OVS to use a search help from SE11, and I will implement what needs to be done with selected search results in the OVS event handler. I was hoping for a parameter "SEARCH_HELP" in the ovs_callback_object->set_configuration method...

Regrds

Jeroen

[Former Member]

As far as i know there is no search_help parameter. If your selection fields are based on a data_element with search help then that will be reused when the selection screen is brought up.

See this [http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/707f0d73-94f0-2d10-97a2-a3776e2118d8?quicklink=index&overridelayout=true|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/707f0d73-94f0-2d10-97a2-a3776e2118d8?quicklink=index&overridelayout=true]

[Former Member]

<>

[Former Member]

Hi,

I will use a concrete example: data_element TPLNR with collective search help IFLM, which includes 15 search helps (IFLMA, IFLMC, IFLMH, IFLMI,...)

Scenario 1: I want to offer the 15 search helps that are included in IFLM in my Web Dynpro app. I want the user select exactly 1 search result. This is easily accomplishable by just defining a context element of data_element TPLNR and setting the input help mode to 'automatic'. The Web Dynpro environment generates a search help containing all the 15 search helps of IFLM.

Scenario 2: exactly the same as scenario 1, except that I want the user to be able to select more than one search result. For this, it seems I need OVS to have a callback method allowing me to write the logic to handle the multiple selected search results. But, if I understood correctly, with OVS I cannot integrate existing search helps (in this case IFLM) (1). Moreover, it seems to me that in the OVS pattern, I can only define one structure for input parameters (2). So I have to rewrite the IFLMA, IFLMC, IFLMH, IFLMI, ... parameters and logic myself in OVS callback method (1) and I can only offer 1 of the 15 search helps (2)?

regards

Jeroen

[Former Member]

i think for your scenario freely_programmed input help is not an bad idea.

[http://wiki.sdn.sap.com/wiki/display/WDABAP/Freelyprogrammedinputhelp|http://wiki.sdn.sap.com/wiki/display/WDABAP/Freelyprogrammedinputhelp]

[http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/50fd6096-a4b6-2d10-bfa8-bbd9001e0d0e?quicklink=index&overridelayout=true|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/50fd6096-a4b6-2d10-bfa8-bbd9001e0d0e?quicklink=index&overridelayout=true]