02-04-2009 11:50 AM
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 .
02-04-2009 11:54 AM
Hi,
Try calling the screen in PAI after an event.
Best regards,
Prashant
02-04-2009 11:54 AM
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
02-04-2009 11:54 AM
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
02-04-2009 12:04 PM
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 .
02-04-2009 12:08 PM
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.
02-04-2009 11:54 AM
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
02-04-2009 11:57 AM
Hi,
call screen screen-number .
Try giving options like starting at (col1) (line1)
ending at (col2) (line2)
02-04-2009 11:58 AM
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.
02-04-2009 11:58 AM
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
02-04-2009 12:08 PM
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
02-04-2009 12:12 PM
iam calling in thru same manner but when when we press any button display error "enter hexadecimal input : odd number of digit".
02-04-2009 12:13 PM
02-04-2009 12:19 PM
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
02-04-2009 12:22 PM
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
02-04-2009 3:11 PM
Or
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
02-06-2009 11:08 AM
02-04-2009 12:18 PM
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
02-04-2009 12:22 PM
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