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
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

display information and remain in same screen

Former Member

‎02-03-2005 11:58 AM

0 Kudos

Hi friends,

i have to make hard error message to informational and control should be on the same screen. this is related to standard sales order screen there is already one user exit is there i have to modify that accordingly.

regards

s.rao

3 REPLIES 3

christian_wohlfahrt
Active Contributor

‎02-03-2005 12:59 PM

0 Kudos

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

Former Member
In response to christian_wohlfahrt

‎02-04-2005 6:41 AM

0 Kudos

Hi christian,

thanx for ur response i forgot to tell u onething that the whole validations were written in PBO now in specific times it is validating and in sometimes system is raising error. actually what i did is i kept those all fields in chain endchain and i have taken whole thing to PAI. Now it is working for my concern but lots of other validations are getting spoiled. Is there any possibility that i can keep that in PBO itself and i can popup that information message and allow user to reenter values in same screen ??

Regards

SR

christian_wohlfahrt
Active Contributor

‎02-04-2005 8:47 AM

0 Kudos

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