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.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Search help exit issue

Former Member
0 Likes
563

Hi,

I've got two screenfields from two different structures.

One is a key field and the other one is the description of the key.

I'd like to create a search help which populates BOTH fields.

These are the two screen fields:

PARAMETERS:pa_utxt3  LIKE ls_db1-low VISIBLE LENGTH 30 MODIF

ID q3x.

PARAMETERS pa_dbke3 LIKE ls_db1-dbkey

             MATCHCODE OBJECT z_sls_dbkey.

I use a search help exit because I need some SELECTs for building the F4-screen.

The exit has following settings:

*"  TABLES

*"      SHLP_TAB TYPE  SHLP_DESCT

*"      RECORD_TAB STRUCTURE  SEAHLPRES

*"  CHANGING

*"     VALUE(SHLP) TYPE  SHLP_DESCR

*"     VALUE(CALLCONTROL) LIKE  DDSHF4CTRL STRUCTURE  DDSHF4CTRL

Firstly, in CALLCONTROL-STEP = 'SELECT' I build my source tab.


The last thing I do in this callcontrol-step is to execute following function code in order to show the F4-screen:

     CALL FUNCTION 'F4UT_RESULTS_MAP'

       TABLES

         shlp_tab          = shlp_tab

         record_tab        = record_tab

         source_tab        = lt_dbkey      "My source tab whom I built with some SELECTs

       CHANGING

         shlp              = SHLP

         callcontrol       = CALLCONTROL

       EXCEPTIONS

         ILLEGAL_STRUCTURE = 1

         OTHERS            = 2.

So my question is:

In event callcontrol-step = 'RETURN',  in which table can I find the F4-entry which was double-clicked by the user?

Because, afterwards I'd like to use this entry to populate the screen fields with function DYNP_UPDATE_FIELDS.

Thanks in advance!

BR,

Mehmet

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
511

Hi Mehmet,

I know, bad news, but it's more easier than you think.

You forgot to tell the people out there that you have these two sel. screen fields two times in the same sel.screen.

Because you used the SAME structures as TYPE for these four fields in total the search help couldn't differentiate between them.

So the solution was to copy the structure and use this copied structure for the 2nd dbkey and description fields. The first dbkey and description fields get the original structure as TYPE.

I hope this helps you and others!

Hi Mehmet,

I know, bad news, but it's more easier than you think.

You forgot to tell the people out there that you have these two sel. screen fields two times in the same sel.screen.

Because you used the SAME structures as TYPE for these four fields in total the search help couldn't differentiate between them.

So the solution was to copy the structure and use this copied structure for the 2nd dbkey and description fields. The first dbkey and description fields get the original structure as TYPE.

I hope this helps you and others!

1 REPLY 1
Read only

Former Member
0 Likes
512

Hi Mehmet,

I know, bad news, but it's more easier than you think.

You forgot to tell the people out there that you have these two sel. screen fields two times in the same sel.screen.

Because you used the SAME structures as TYPE for these four fields in total the search help couldn't differentiate between them.

So the solution was to copy the structure and use this copied structure for the 2nd dbkey and description fields. The first dbkey and description fields get the original structure as TYPE.

I hope this helps you and others!