re-enable the screen

[Former Member]

In ABAP transactions if we enter wrong input in the screen fields then error message is displayed(Assume I have coded exception handling), then screen fields are disabled. We cannot change entered input or cannot enter new input.What my doubt is, Is there any way to re-enable the screen for new entry or to rectify the entries. If so please provide me a example and where to place the logic in prog ( I mean in which event PBO or PAI). Thanks in advance.Waiting for answers from Mods and techies.....

[Former Member]

In ABAP transactions if we enter wrong input in the screen fields then error message is displayed(Assume I have coded exception handling), then screen fields are disabled. We cannot change entered input or cannot enter new input.What my doubt is, Is there any way to re-enable the screen for new entry or to rectify the entries. If so please provide me a example and where to place the logic in prog ( I mean in which event PBO or PAI). Thanks in advance.Waiting for answers from Mods and techies.....

[Former Member]

In PAI event write the logic,

FIELD <fieldname> module M1.

double click on M1 and it will create a module in your program.write your exception handling in the module.this will re-enable that particular field if there is a wrong entry.

If you want validation over a range of fields, write:

Chain

Field1

Field2

Field3

Module M1.

EndChain

[Former Member]

Hi,

use field and chain for the enabling the field if user enters wrong ones.

for example.

in pbo of the screen .

field field name module name.

the above statement is used for for single field and module cossisitts of the condition on which u r throughing the errror.

chain

field1

field2

modulename.

endchain.

chain is used for bulk field like if u want check the chain of fields then use it.

Plzz reward points if it helps.

[Former Member]

ABAP handles messages in different ways depending on where you issue the error message and what type of error message you display.

In your case, you are doing something obviously wrong because in a standard PBO if error messages are issued, then fields become available for input.

In your PBO you should use CHAIN, FIELD, MODULE and ENDCHAIN statements to handle your error checking, coupled with the ON INPUT and ON REQUEST clauses for the MODULE statements. If module Check_My_InField issued an error message, and that error message was type E, then all other fields on the screen would be disabled, and My_Infield would be ready for input so that it's value can be changed.

By specifying more than one field you can then group fields together so that if an error message is output, then these fields alone will be made available for input. In this "processing chain", if any of the modules output an error message then all of the fields, specified for any Module statement in the Chain block will be made ready for input.

Read the topic on managing user input in the Abappers Knowledge Corner. This specifies the action of the message statement in the various events of an ABAP report or program module.

Chaitanya.