SAPCONSOLE create own error screen

[former_member182371]

Hi,

i´ve just read Rich Heilman´s weblog "

Implementing Bell Signal Functionality in Sapconsole Transactions

".
in my report i use SAP standard error screen '0999' by means of FM 'CALL_MESSAGE_SCREEN'.
i want to implement bell signal functionality in my error screen.

Can i do it with SAP standard screen or do i have to create my own error screen?.

What do i have to consider when creating an own error screen?.

Best regards.

[former_member182371 · Accepted solution]

Hi Rich,

i guessed so, but is it correcto the way to create the new dynpro?

in SAP HELP doc "MOBILE DATA ENTRY" it says literally:

Defining a Screen

Use

You can either create a new screen or copy an existing one.

Procedure

1. To create a new screen, enter the program SAPLXLRF in the screen painter.

2. To copy a screen, proceed as follows:

• Enter the program SAPLLMOB and a screen number.

• Choose Element List and delete the last field, the "OK_CODE".

• Choose Subscreen in the tab page Attributes in Screen type.

• Save your data entries as a local object under the development class "$tmp".

Regards.

[RichHeilman · Accepted solution]

THe programs which calls the message screen, this is a custom program right?

Regards,

Rich Heilman

[RichHeilman · Accepted solution]

I'm not sure that I would be following those directions. They look as if these are instructions for creating new screens the standard processing.

I would suggest creating a new screen in your custom program directly, or creating a function module with a new screen, then call the function module, simular to what you were doing before with the CALL_MESSAGE_SCREEN function module.

Regards,

Rich Heilman

[former_member182371]

Hi,

Yes, it´s the one i referred to in my former post.

Z_MB1C_501.

Regards.

[Former Member]

Hi Calsadillo & Rich!

The Solution from Rich is a clean solution.

I looked back into my notes after reading this chain and realized in the requirement i was involved we donot want to Display Any Error Message, the user scans a Material, if it is invalid BEEP and put the cursor back to the same field,if valid display material details and proceed.

For your requirement i think Rich is correct.Pl ignore my earlier response and proceed with Rich's direction.Hope you must have resolved it by now.

Good Luck

-Gisk

[former_member182371]

Hi,

after considering the question hat i finally intend to do is to create a new screen 9999 as a copy of screen 2999.

in order to do the copy i´ve been reading the documentation of SAP HELP and in SE51 i'd need to do thus:

From

Program SAPLLMOB

Nº dynpro 2999

to

Program SAPLXLRF

Nº dynpro 9999

and i would save it in a $tmp transport request.

is this correct?

Best regards.

[RichHeilman]

I think that you will want to assign a package/development class which is tied to a transport layer. $TMP is the local development class, which means that the object will not be transportable.

Regards,

Rich Heilman

[former_member182371]

Hi,

(in terms of standard screens) the logical screen i´m working with is 0999 and the physical screen is 2999.

Can i add a new field (notify_bell_signal) in standard screen 2999 without modifying the standard?

if so, How?

Best regards.

[RichHeilman]

No, I think you will have to register the object in order to modify it.

Regards,

Rich Heilman

[Former Member]

Hi calsadillo ,

Is that a requirement to have the Bell Signal in your Error Message Screen.

Ideally you would implement it in the Screen(PBO/PAI) from where you call the message Screen and not in the error message screen.Upon validation of a particular input field, if there is any error you display the 0999 screen with OK Button and on return you will hear the bell sound and you have to code to put the cursor back to the error field.

Pl refer to SAP Note# 371838 OR use Rich's Weblog.

See, even if you try to modify the Error Screen it is not going to help because the user has to come back to the calling screen to fix the error.I think you might have to re-consider your requirement again.

Thank You

Gisk

[RichHeilman]

Well, the way I have implemented at my company, is the bell signal is fired when the error message screen is thrown. This way it notifies the user to look at the screen and view the error message. Have the Bell signal when the user comes back from the message screen is a little too late.

In all of my custom transactions for RF, I have a screen 9999 which is used as the message screen, it contains 7 lines for the error message to reside in with a BACK button and of course the NOTIFY_BELL_SIGNAL field beside the button at the button. Anytime there is an error, this screen is used. The bell signal comes exactly when the error message screen is seen.

REgards,

Rich Heilman

[RichHeilman]

I guess you could copy that function module into a "Z" function and put the NOTIFY_BELL_SIGNAL field on that screen. It should work.

REgards,

RIch Heilman