topic Re: search help for input fields in a screen in Application Development and Automation Discussions

search help for input fields in a screen

Former Member — Wed, 25 Apr 2007 16:10:05 GMT

Hi,

Pls help me

how to set search help property for the I/O fields in screen in se80?

1. do we want to add any property for search help in the property window?

2.do we want to create a MODULE PROCESS ON VALUE REQUEST ?

PLS tell me how to set search for the I/O field in se80?pls tell me the process?

****************************************************************************************

i want to set the search help for more I/O fields in se80 but all the fields belongs to the same table?

can i create a single search for all these fields and use that for all the I/O fields ?

elementary search help or collective search help?

thanks & regards in advance,

vsnl.

Re: search help for input fields in a screen

Former Member — Wed, 25 Apr 2007 16:24:48 GMT

You can create Elementary search help for the individual fields using their master tables and assign them in the attributes of the repective fields.

there is an attribute for each field SEARCH HELP, so you can assign

search for the search helps for the key fields like Customer, vendor, Plant etc

already there are some standard search helps for them you can use them

You can also use the fun module

Process_on_value_request for the fields.

reward points if useful

regards,

Anji

Re: search help for input fields in a screen

Former Member — Wed, 25 Apr 2007 16:28:04 GMT

Hi,

You need to specify the matchcode-object for the corresponding field. the other way is use the FM 'HELP_VALUES_GET_NO_DD_NAME' or 'HELP_VALUES_GET_WITH_DD_TABLE' based on the requirement.

Re: search help for input fields in a screen

sreeramkumar_madisetty — Wed, 25 Apr 2007 16:34:36 GMT

By creating the elementary search help and giving that in the Field's attributes, you can create the search help for that fields.

For many of the Standard Fields like Material Number,Plant etc SAP built-in will gives the search help.

You can also use the below FM to get the same.

Process_on_value_request .

Regards,

Sreeram

Re: search help for input fields in a screen

Former Member — Wed, 25 Apr 2007 17:10:12 GMT

Hi,

Input Help on the Screen

Within the Screen Painter, you can define two types of input help:

1. The FIELD statement with one of the additions VALUES or SELECT.

2. Linking a search help directly to a screen field.

If you link a search help directly to a screen field, it overrides the additions of the FIELD

statement. However, the input check [Page 581] functions of the FIELD statement remain

unaffected.

Input Help in Flow Logic

The following input help methods are obsolete and should not be used. They are still supported

for compatibility reasons.

In the screen flow logic, you can specify a value list for a screen field <f> as follows:

FIELD <f> VALUES (<val1>, <val2>,...).

The value list contains a series of single values <vali>. The NOT and BETWEEN additions for the

input check [Page 581] are not appropriate for input help.

You can also create a value list by accessing a database table as follows:

FIELD <f> SELECT *

FROM <dbtab>

WHERE <k1> = <f1> AND <k2> = <f2> AND...

In the WHERE condition, the fields of the primary key <ki> of the database table <dbtab> are

checked against the screen fields <fi>. The WHENEVER addition, used with input checks [Page

581], is not necessary for input help.

If you have used a ABAP Dictionary reference for field <f>, the selection and the hit list formatting

may be affected by any check table attached to the field.

Attaching a Search Help

Search helps from the ABAP Dictionary can be attached to a screen field [Ext.]. To do this, enter

the name of the search help in the corresponding field in the attributes of the screen field in the

Screen Painter. This assigns the first parameter of the search help to the screen field. It is only

possible to place a value from the hit list onto the screen.

Input help on a screen.

REPORT DEMO_DYNPRO_F4_HELP_DYNPRO MESSAGE-ID AT.

DATA: CARRIER(3) TYPE C,

CONNECTION(4) TYPE C.

CALL SCREEN 100.

MODULE CANCEL INPUT.

LEAVE PROGRAM.

ENDMODULE.

The next screen (statically defined) for screen 100 is itself. It has the following layout:

602 April 2001

Cancel

Airline

Flight number

Screen field with search help

Input help in the flow logic

The input fields have been adopted from the program fields CARRIER and

CONNECTION. The function code of the pushbutton is CANCEL, with function type

E. The search help DEMO_F4_DE with the search help parameter CARRID is

assigned to the screen field CARRIER. The search help uses the database table

SCARR.

The screen flow logic is as follows:

PROCESS BEFORE OUTPUT.

PROCESS AFTER INPUT.

MODULE CANCEL AT EXIT-COMMAND.

FIELD CARRIER VALUES ('AA', 'LH').

FIELD CONNECTION SELECT *

FROM SPFLI

WHERE CARRID = CARRIER

AND CONNID = CONNECTION.

When the user chooses the input help for the individual fields, the following input

help is displayed:

For the Airline field, the search help displays the names of the airlines and places the airline

code in the input field for the chosen line. If the airline code is not one of those listed in the

VALUES list of the screen flow logic, the input check triggers an error message in the PAI

event. So the search help overrides the VALUES addition for the input help, but not for the

input checks. This is therefore not an appropriate place to use the VALUE addition.

For the Flight number field, the flow logic displays the selected entries from the database

table SPFLI and places the selected line in the input field.

Regards,

Bhaskar