topic Re: CALL SCREEN error in Application Development and Automation Discussions

CALL SCREEN error

Former Member — Wed, 04 Feb 2009 11:50:52 GMT

Hii,

when i am calling another screen through call screen statement from pbo of one screen then control doesn't go to pbo of called screen. thanks .

Re: CALL SCREEN error

Former Member — Wed, 04 Feb 2009 11:54:21 GMT

Hi,

Try calling the screen in PAI after an event.

Best regards,

Prashant

Re: CALL SCREEN error

Former Member — Wed, 04 Feb 2009 11:54:27 GMT

Hi,

what is the use oof calling the next screen from the PBO of first screen . call it from the PAi of first screen or call the second scren directly.

Regards

Mudit

Re: CALL SCREEN error

Former Member — Wed, 04 Feb 2009 11:54:55 GMT

Hi,

What exactly are you trying to do? You said you are using call screen in the pbo of another screen, that is the first screen is never displayed, then maybe make the second screen as the initial screen and do any processing that needs to be done in the pbo of this screen as user does not perform any function on the first screen. What exactly is the error message that you receive?

Regards,

Sachin

Re: CALL SCREEN error

Former Member — Wed, 04 Feb 2009 11:54:55 GMT

Hi Rishav,

What Call Screen does is:

Calling a single screen is a special case of embedding a screen sequence. If you want to prevent the called screen from covering the current screen completely, you can use the CALL SCREEN statement with the STARTING AT and ENDING AT

CALL SCREEN 1000.

CALL SCREEN 1000 STARTING AT 10 10 ENDING AT 20 20.

hope it helps you

Regrds

Mansi

Re: CALL SCREEN error

Former Member — Wed, 04 Feb 2009 11:57:31 GMT

Hi,

call screen screen-number .

Try giving options like starting at (col1) (line1)

ending at (col2) (line2)

Re: CALL SCREEN error

former_member195383 — Wed, 04 Feb 2009 11:58:24 GMT

1st of all there is no point in putting the call screen statement in the PBO of another screen. If you want the other screen, even before the 1st screen comes, then why should you put the 1st screen .

Directly keep the 2nd screen.

or in main program you can handle the occurance of screen 1 or screen 2, by using the call screen statement, putting the desired condition.

like...

if <condition1>

call screen '2000'.

elseif <condition2>

call screen '3000'.

endif.

Or put in in PAI of the first screen, if your requirement is such that after entering some value in the 1st screen, the second screen should appear.

Re: CALL SCREEN error

Former Member — Wed, 04 Feb 2009 11:58:42 GMT

Hi Rishav

I think you havent given the next screen option in the first screen.

If your first screen number is 100 and second screen number is 200.

In the attributes of the first screen ,give the next screen as 200.

I think tis will work

Regards

Menon

Re: CALL SCREEN error

Former Member — Wed, 04 Feb 2009 12:04:58 GMT

sorry instead of pai , by mistake i have written it pbo. actually when i am calling other screen trough call screen statement form pai of one screen then pai of another screen doesn't get executed .

Re: CALL SCREEN error

Former Member — Wed, 04 Feb 2009 12:08:23 GMT

Hi,

call the screen from the PAI of the First Screen.

Because any event get trigred from PAI

Like:


  ok_code = sy-ucomm.
  CASE: ok_code.
    WHEN 'NEWL'.       " call next screen
          CALL SCREEN '9003'.

   ENDCASE.

Hope it will help you

Thanks

Arun Kayal

Re: CALL SCREEN error

former_member195383 — Wed, 04 Feb 2009 12:08:51 GMT

check if the screen that you are calling is active or not. If not activate the same, and try.

Also paste the piece of code where you are writing the call screen statement.

Re: CALL SCREEN error

Former Member — Wed, 04 Feb 2009 12:12:50 GMT

iam calling in thru same manner but when when we press any button display error "enter hexadecimal input : odd number of digit".

Re: CALL SCREEN error

former_member195383 — Wed, 04 Feb 2009 12:13:53 GMT

if you are calling screen '100' .

use

call screen '0100'.

Re: CALL SCREEN error

Former Member — Wed, 04 Feb 2009 12:18:33 GMT

than

check

Sy-ucomm in debugging mode.

I think in case you are passing the name and the name that you have created on button is different

Hope it will solve your problem

Thanks

Arun kayal

Re: CALL SCREEN error

Former Member — Wed, 04 Feb 2009 12:19:28 GMT

than

check

Sy-ucomm in debugging mode.

I think in case you are passing the name and the name that you have created on button is different

Hope it will solve your problem

Thanks

Arun Kayal

Re: CALL SCREEN error

Former Member — Wed, 04 Feb 2009 12:22:28 GMT

Hi Rishav,


enter hexadecimal input : odd number of digit".

This message is displayed before it goes in the PAI of the second screen, then check if there is an input field on the second screen which has some invalid data.

regards,

Advait

Re: CALL SCREEN error

RaymondGiuseppi — Wed, 04 Feb 2009 12:22:54 GMT

Resum

- You execute the CALL SCREEN in one module of the PAI logic of first screen, not in PBO

- Then the PBO of the second screen is executed just before the second screen get displayed

- The data input check of the second screen must be in its PAI logic, not in PBO

Regards

Re: CALL SCREEN error

Former Member — Wed, 04 Feb 2009 15:11:34 GMT

check the case statement

In case tatement with when

pass the button name in CAPITAL letter

i think you can check it also...


case sy-ucomm

when'NEW'   "check  it should be in capital letter 
                   " if you found in debbuging that the field name and button anemis same
                   " check the field name in your program it should be in CAPS.........

Call screen '9001'
endcase.

Hope it will solve the problem

Re: CALL SCREEN error

Former Member — Fri, 06 Feb 2009 11:08:53 GMT

Problem is solved . Thanks