topic Re: Validate a screen entry through message in Application Development and Automation Discussions

Validate a screen entry through message

Former Member — Mon, 24 Nov 2008 05:03:53 GMT

Moderator message: do NOT offer points

Dear experts,

I have designed one screen containing 10 entries of 10 different fields.

One entry is for amount . I want that amount to be less than 1000.00 and if it is not so it should give message.

My logic is working fine..but the only problem is that when I make a wrong entry , it should allow me to corrrect it there and there only..

now with message type E , it disables all the fields and other entries are also to be entered again...

and with message type W and I , it is taking that as a right entry.

So which message type should I use ? Or any other alternative ?

<<text removed>>

Edited by: Matt on Nov 24, 2008 11:21 AM

Re: Validate a screen entry through message

kesavadas_thekkillath — Mon, 24 Nov 2008 05:05:19 GMT

at selection-screen on <screen field>.

do your validation here.

Re: Validate a screen entry through message

Former Member — Mon, 24 Nov 2008 05:11:57 GMT

Hi,

You can use field checks in the PAI of the screen.

The syntax is Field <fieldname> Module <check module name>. In the module you write the code to check the field and give the message with Type 'E' ie., type error then you can modify the individual field.

If that is an internal table field you can use it within LOOP and ENDLOOP.

Regards

Thabitha.

Re: Validate a screen entry through message

Former Member — Mon, 24 Nov 2008 05:19:34 GMT

If you want all the fields to be input enabled use

CHAIN

field fnam module mname on input/request

when you use FIELD key word the system delays the transfer of the values from screen to program until the checks have been validated.

ENDCHAIN.

for further help go through the KEY word documentaion.

regards

Ramchander Rao.K

Edited by: ramchander krishnamraju on Nov 24, 2008 6:23 AM

Re: Validate a screen entry through message

Former Member — Mon, 24 Nov 2008 05:20:43 GMT

Use Message Type W or S and then write a STOP statement after it.

The control will remain on your Selection Screen and you will be able to make the required changes.

Re: Validate a screen entry through message

Former Member — Mon, 24 Nov 2008 05:57:22 GMT

Hi,

My suggestion is you can go with message type 'E'. Check the following code:

tables: vbak, vbap.

parameters: vbeln like vbak-vbeln,

netwr like vbak-netwr. " Currency field

at selection-screen on netwr.

if netwr > 1000.

message e000(00) with 'Enter less than or equal 1000.'.

endif.

start-of-selection.

write: vbeln, netwr.

Regards,

Bhaskar

Re: Validate a screen entry through message

Former Member — Mon, 24 Nov 2008 06:07:51 GMT

Hi,

In the PAI of that screen you can use CHAIN...ENDCHAIN or simply in the Module USER_COMMAND of that screen once user presses ENTER or whatever you can validate it there so once 1st field is validated it will validate 2nd and so on and in order to make the fields Editable when some Invalidation happens in that case use FM

CALL FUNCTION 'MESSAGE_TEXT_BUILD'

EXPORTING

msgid = g_msgid

msgnr = g_msgno

msgv1 = g_msgv1

IMPORTING

message_text_output = g_message.

which will extract the message text based on the message class and message no,and since you validating in the manner i mentioned above it will behave like an ERROR message but will allow you to edit.

Re: Validate a screen entry through message

Former Member — Mon, 24 Nov 2008 06:38:55 GMT

For validating single field:

In PAI

field <field1> module check_field1.

" if in module u thro message of type E or W after validating. The field field1 will remain available for input.

For validating multiple fields:

In PAI

chain.

field <field1>.

field <field2>.

field <field3>.

module check_fields.

endchain.

" if in module u thro message of type E or W after validating. The all the fields mentioned within chain endchain will remain available for input.

For validating fields in Table control:

In PAI

loop at itab.

Use any of above two methods

endloop.