How to Search Help ?

[Former Member]

I have a java webdynpro screen with a few input fields that need a search help. There are a lot of threads regarding to this topic and everyone has different information and links to many other threads.

Could anyone please tell me what is the best/fastest/easiest way to do it?

I am not talking about "Simple Value Selector" neither Extended Value Selector". I need a implement/use a search help like the ones in R/3 when you run transaction SE16 and enter values in the input fields using F4.

One time I had one running where I did not need any coding at all, everything was done on the attributes of the field, but I do not recall how to do it anymore. The problem with it was that it just displayed one column and I needed it two, the column with the value itself and a second column with the text. What I need this time is the two columns.

Thanks in advance,

Diego.

[Former Member]

Diego,

Short answer: there is no built-in solution in WD Java, roll your own.

Medium size answer: "Short answer" + it will be hard to resemble R/3 functionality.

1. Use either OVS or custom component that is run as pop-over window.

2. Either try to play with BAPI_HELPVALUES_GET and related RFMs to develope generic solution, or use per-use-case RFMs (probably custom) and OVS.

3. If this is possible, develope own RFM that simplifies BAPI_HELPVALUES_GET and adopt it (make friendly) to WD.

P.S. I did some work to implement generic mechanism using BAPI_HELPVALUES_GET. However, I postpone this task. Bad for me -- seems to be excellent commercial component.

Valery Silaev

EPAM Systems

http://www.NetWeaverTeam.com

[diego_gaudenzi]

Hi Valery,

Could you please give me more info regarding to "Use either OVS or custom component that is run as pop-over window" ?

I will also try the BAPI option you mention.

Regards,

Diego.

[Former Member]

Diego,

1. You can try OVS over content nodes. Create your context (most probably dynamically) according to metadata available with BAPI_HELPVALUES_GET_SEARCHHELP. Then attach OVS extension with custom IWDOVSNotificationListener that performs search for help values using BAPI_HELPVALUES_GET.

2. You may proceed with the very same BAPI_HELPVALUES_GET_SEARCHHELP / BAPI_HELPVALUES_GET pair but inside your custom component. Next instead of OVS you may add Button / Link2Action near every field and invoke your custom component in pop-over window (read about IWDWindowManager API in NWDS help)

3. You may use existing BAPIs (for example, BAPI_COMPANYCODE_GETLIST) or create own RFMs to provide value help. Then just use OVS with BAPI as described in WebDynpro tutorial on SDN.

Actually, I tried (or 'am trying' first approach. However besides search help challenges I've faced a lot of limitations from OVS component. Btw, here is blog post by <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.sdn.businesscard.sdnbusinesscard?u=5%2bhlk9c3p0q%3d">thomas Jung</a> that I find very useful for this task: <a href="/people/thomas.jung3/blog/2004/11/01/bsp-value-input-help-popups-version-20-part-2">BSP Value Input Help Popups Version 2.0</a>. Also he is talking about BSP, number of techniques is applicable to WD Java. Sure, certain "translation" is required. And you are even in worse position: BSP is "inside" R/3 and may utilize all the ABAP power while WD Java has only narrow Adaptive RFC / JCo window

Valery Silaev

EPAM Systems

http://www.NetWeaverTeam.com