05-10-2006 6:50 AM
When I send error messages it disables the back, exit and cancel button.
How can I enable them?
05-10-2006 6:52 AM
If the buttons are on standard tool bar, that's not possible.
Have u custom made your back/exit/cancel buttons?
Can send the code you are writing?
05-10-2006 6:55 AM
I did not do any customization. My code for sending the message if this:
Message eXXXX with 'Error message'
And then it disables the button. I just want to display the error to prevent the user from entering a value that is already existing in the table.
05-10-2006 6:59 AM
Hi,
When you specify an error message the program terminates at that point.
Hence you may not be able to set the GUI status for that.
Regards,
ramana
05-10-2006 7:02 AM
05-10-2006 7:05 AM
Use popup window to notify errors...
CALL SCREEN '1100' AS WINDOW STARTING AT 10 10.
<i>OR</i>
CALL FUNCTION 'POPUP_TO_CONFIRM'
EXPORTING
TITLEBAR = 'Test '
text_question = 'Error message'
DISPLAY_CANCEL_BUTTON = ' '
.
Regards
ramana
05-10-2006 7:07 AM
u can use status or information message instaed.
if u want to exit at that point, use status and info message
and write
leave to screen 0.
05-10-2006 7:07 AM
Best way in dialog programming is :
FIELD f1 module m_f1 on request.
module m_f1.
if...
message e....
endif. .
endmodule.
or, if you want a group of fields to be open for input, use chain-endchain.
Please reward points if you feel the answers helped..
05-10-2006 7:56 AM
05-10-2006 7:57 AM
05-10-2006 6:52 AM
HI
GOOD
CAN YOU GIVE ME SOME MORE DETAILS ABOUT YOUR REQUIREMENT AND THE ERROR THAT YOUR ARE FACING WITH.
THANKS
MRUTYUN
05-10-2006 6:56 AM
Hi Adrian,
If u are using a module pool screen, u can use the CHAIN
FIELD <FIELD NAME> MODULE <MODULE NAME>
ENDCHAIN
construct to get rid of ur problem, please read the related documentation.
05-10-2006 7:00 AM
Vijay's answer is definitely the answer as that's the way you should give errors in Dialog.
But I am still surprised how standard toolbar's buttons get de-activated on error message.
Normally, all fields on screen are deactivated if you do not use FIELD ... MODULE construct for giving errors.
Can you tell is this standard SAP transaction, or your own?