Hi!
So have a look at routines in include MV45AFZB. There you will find lot of structures, were you field should be available (otherwise field won't be able to edit after error message).
Check for flags US_DIALOG... - otherwise it might be an update out of document flow and no-one can react on your message.
Might be helpful to clear field before raising message - than you won't end in endless loop of 'user hits enter' - 'error message'.
Regards,
Christian
Hi 'SR',
to bo honest: sounds like your making a big mess (don't worry, I don't tell anyone).
Never raise messages in PBO - PAI is correct place.
SAP designed a lot of routines (e.g. FORM USEREXIT_CHECK_VBAK USING US_DIALOG.), in which you can check and raise errors. There is no need to modify dynpro and add new chain ... module ... commands.
My check looks like this (zzubz is append field, displayed in customer screen):
IF vbak-zzubz NE space AND t180-trtyp EQ charh. CLEAR vbak-zzubz. MESSAGE e074(zpu2main). ENDIF.
Pretty simple, but fully functional.
If you need help to find right place, tell your fields you need to check!
Regards,
Christian
Add a comment