Application Development 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: 

Error Message, user exits, and editing disabled problem.

Former Member
0 Kudos

HEllo I recently had an assignment where I have to create a user exit with an error message. I had no problems with the error message but after an error occurs, with this line:

<b> MESSAGE ID 'ZSD' TYPE 'W' NUMBER '002'.</b>

the fields have become disabled and there seems to be no way to enable the fields for changing. Is there a way to fix this. Thanks people and take care!

1 ACCEPTED SOLUTION

RichHeilman
Developer Advocate
Developer Advocate
0 Kudos

Oh, TYPE E, when issuing an error message, all fields are disabled unless you tie it to a field or group of fields. This is commonly done by using the CHAIN...ENDCHAIN statements in the PAI of the screen. Do you have access to this? I assume that you are issueing the message from within a MODULE, right? You are probably calling this module in the PAI flow logic of the screen. You will need to do something like this.

Here P_BUKRS is the screen field and CHECK_BUKRS is the module where you are checking the value and issuing the error message. Using the CHAIN, you can tie other fields to the check so that they are also enabled when the error message is issued.

CHAIN.

field p_bukrs module check_bukrs.

ENDCHAIN.

Regards,

Rich Heilman

8 REPLIES 8

Former Member
0 Kudos

sorry i mean the line is

MESSAGE ID 'ZSD' TYPE '<b>E</b>' NUMBER '002'.

RichHeilman
Developer Advocate
Developer Advocate
0 Kudos

This is a warning message and you need to "Enter" thru it. Once you hit enter after the message is displayed, do your fields become enabled again?

Regards,

Rich Heilman

0 Kudos

Sorry that was a type. What I meant to put was <b>E</b> not <b>W</b>

RichHeilman
Developer Advocate
Developer Advocate
0 Kudos

Oh, TYPE E, when issuing an error message, all fields are disabled unless you tie it to a field or group of fields. This is commonly done by using the CHAIN...ENDCHAIN statements in the PAI of the screen. Do you have access to this? I assume that you are issueing the message from within a MODULE, right? You are probably calling this module in the PAI flow logic of the screen. You will need to do something like this.

Here P_BUKRS is the screen field and CHECK_BUKRS is the module where you are checking the value and issuing the error message. Using the CHAIN, you can tie other fields to the check so that they are also enabled when the error message is issued.

CHAIN.

field p_bukrs module check_bukrs.

ENDCHAIN.

Regards,

Rich Heilman

0 Kudos

Im issueing the message in a user exit (im assuming imbedded in a module). Unfortunatley I dont have access to the main abap program since its a sap standard one.

0 Kudos

Then I'm not sure how you are going to handle it. Maybe issuing a message type 'I' would help you out. This could stop the processing and the user may be able to change the data on the screen to satisfy the condition. Give it a try.

Regards,

Rich Heilman

0 Kudos

Can you please let us know what the user exit is?

0 Kudos

sorry im not familiar with User Exits but I think this is it <b>FUNCTION exit_saplito0_002</b>